...

This section describes aspects of collaboration in terms of metadata and data content, offered services as well as detailed software development of O2A components.

Index

• Content in O2A
• Responsibility
• Contributing
• Software development

Anchor
content content

Content

...

Info
icon false
Would you like to manage your data flows with O2A? We are happy if you contact us by o2a-support@awi.de.

Anchor
responsibility responsibility

Responsibility

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
icon false
Do you have ideas improving an O2A component? We are happy if you contact us by o2a-support@awi.de.

Anchor
contributing contributing

Contributing

Contributions to O2A are very welcome. We mainly distinguish three types of contributions:

• feedback - We heartily invite you to give us feedback and describe what you like to have and makes your life easier. Our product owner will check your feedback, map and prioritize it into our goals to improve the software continuously.
• significant contributions - You are missing some major part in O2A and want to contribute within a project-context? One way is to negotiate a project-membership with financed effort for the desired feature in mind. On the other hand we are willing to integrate a developer for efforts about at least 3 person months (including training period, development, unit tests, review and integration tests).
• join the team - The preferred way is to join the development team permanently! This option makes sense if you are willing to contribute at least 10-20% working time for at least one year. Focus is on contributions for the community as defined by the product owner. The developer gets a thematic training period, attends and contributes to SCRUM meetings and feels responsible for the product.

The contribution process should look like this:

1. Provide a draft for extensions or changes (max. 2 pages). The draft should cover the contribution type, strategic impact, the value for the community (also who is the community) and a rough effort estimate. It should be as concrete as possible.
2. Get in contact with us o2a-support@awi.de.
3. We will decide if and how we can integrate your contribution. This covers also an estimation for the technical impact and effort for core functionality or extensions.
4. We get in touch with you and discuss the approach.

Info
icon false
Do you like to contribute? Send us a mail o2a-support@awi.de and describe how you like to contribute.

Info
icon false
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.