(Engagement Goal) Engaging with OSS Projects
Please provide a description of the activity.
Make sustainable commitment to some OSS projects that are important to you. Contributions can take several forms, from direct funding (i.e. money) to resources allocation (e.g. people, servers, infrastructure, communication..), as long as they benefit the project or ecosystem in a sustainable and efficient way.
In this activity, the contributions are supposed to bring a substantial, long-term improvement to the OSS project: e.g. a developer or team who develop a much-wanted new feature, infrastructure assets or servers for a new service, take-over the maintenance of a widely used branch.
Includes #8 (closed)
Why it is relevant to undertake this activity, What needs it addresses. What are the efforts expected. How much will it cost? What resources do we need? What RoI can be gained?
Question: How can I assess if the activity is acquired? How will progress be measured. What are the objectives? What are the KPIs? Suggest verification point.
Benefits: ensuring developments are integrated in the stable version Cost: committing time to projects
Add KPI description here
Technologies, tools and products concerned by this activity.
List tools relevant or concerned by the activity here
Hints and best practices. Collected from GGI participants.
Add recommendations here
Links to resources in the Resource Center
Add links to resources here