...
- NLnet will offer a lightweight conservancy model to mature software projects that want to manage financial contributions to the project.
- Projects will be broadly self-governing, with each project appointing a Software Advisory Council (SACs) to take on the role of a Board for the project.
- The Commons Conservancy is license agnostic, but requires projects to be open source and for software licenses and contributions to be appropriately managed.
- Each project has a dedicated sub-fund and can spend this on activities to ensure the development of the project.
- Between 5%-8% of project funds is allocated to NLnet for supporting this function. This in turn is channeled into the
Further details can be found in this introductory document.
The Greenhouse SIG will help project decide if they have reached the level of maturity needed for participation in the Conservancy and support the set up of SACs for projects. The Greenhouse will also help promote software usage and contributions to the project.
As not all projects have the same focus and requirements, a small set of charters for SACs are proposed with slightly differing set-ups and processes. Some proposed examples are below.
Please note that the Filesender name is used purely for example in this document to make for easier reading - these documents do not currently reflect any processes or approaches within the Filesender project.