In general our O2A software is open source, free of charge and may be re-used in other contexts. Our software is administrated in the gitlab.awi.de repository and you can also find examples on github.com also. To foster and streamline software development we want to have one central managed code basis. All splitted branches for new features and bug fixes shall be finally merged into the central master branch aligned with Gitflow. The agile software development process for each O2A component is managed in 2-weekly sprints with jira-software.awi.de following SCRUM-based principles.
...
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
Copyright 2010-2020- Alfred Wegener Institute, Helmholtz Centre for Polar and Marine Research Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
...
As the software development process is aligned to SCRUM, each O2A component or product has it's own product owner. The product owner is responsible for vision, wishes and requirements and maximizing the value of the software product for the community. This targeted view is merged and harmonized in the O2A strategic leader group. The members of the leader group have decades of experiences in natural science, research data management, information technology and software development.
Info | ||
---|---|---|
| ||
Do you have ideas improving an O2A component? We are happy if you contact us by o2a-support@awi.de. |
Contributions to O2A are very welcome. We mainly distinguish three types of contributions:
The contribution process should look like this:
Info | ||
---|---|---|
| ||
Do you like to contribute? Send us a mail o2a-support@awi.de and describe how you like to contribute. |
Info | ||
---|---|---|
| ||
You don't like to contribute but use O2A? Have a look to our public available application programming interfaces (API) here https://spaces.awi.de/x/_F2VEg. |
Our software development follows some simple rules as best practices. Use the following topics and tasks as guideline and checklist.
Our software development follows simple rules as best practices. Use the following topics and tasks as guideline and checklist.
README.md
markdown file in its root directory describing the project (see template below)..gitignore
file in its root directory defining files to exclude or to force inclusion.Code Block | ||||
---|---|---|---|---|
| ||||
# Name of the project and repository content * Short description of the project and repository content. * Provide relative links to demonstrators in this repository. * Provide an overview of the architecture and relation to other projects. * Use [diagrams.net](https://diagrams.net) for your sketches and provide a editable link here. ## Getting started * Describe how to start with this project. ### Prerequisites * Describe requirements to fulfill before starting. ### Installing * Describe how to install required software and this software. ## Tests * Describe how to test this software. ## Deployment * Describe how to deploy this software including required prerequisites and configuration. ## Contributing * Describe how to contribute to this project. At best you link to general [documentation](https://spaces.awi.de/x/bu7FEw) and improve it if necessary. ## Versioning * Describe shortly the versioning approach. ## Authors * List the authors and emails here. ## License We have a BSD-3-Clause license and refer to [documentation](https://spaces.awi.de/x/bu7FEw). ## Acknowledgments * Any acknowledgements? ## Notes * Any additional notes? |
...
...