...

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

overview

• which components exists, what is the focus of a component
• how each component is integrated with others
• what I have to do, what does the system by itself
• links to sub-chapters
• → check information and clearness of component descriptions

Different models

• scientific requirements / feedback
• extensions

Formal contracts for contributions

• merges with other existing contracts?
• merges with project contracts
• responsiblity for content → chief editor concept, proxy per project/institution - content standards

c) usage of components

b) software as a service - SLA

a) software development

→ RK: ask Antonia for MOSAiC

Content

The content in O2A can be distinct in metadata and data.

...

Info
icon false
Do you have ideas improving an O2A component? We are happy if you contact us by o2a-support@awi.de.

Contributing

Organisation of contributions, how to 

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). - how to integrate contributions, who is responsible for external / integrated functions / compatibility / list of API users (what about API breaks?)
• 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. - how to control contributions - distributed leaders with other opinions - also deadlines for external parties - setup contracts for collaboration?
• → RK mit Dirk Barbi sprechen zu Contributions

The contribution process should look like this:

...