What?
| Info |
|---|
| SIG-Greenhouse was formally closed as a SIG in 2018 but these pages are maintained for information. If you are interested in finding out how you can benefit from the work of the SIG, please visit the Commons Conservancy website, a programme conservancy created to meet the aims and objectives of software and other projects looking for a sustainable home. |
This space is for information relating to the "TERENA GÉANT Greenhouse " discussionSIG.
The TERENA community produces a wide range of software outputs to support its goals. Some of these develop in to fully fledged services, some disappear, and others happily exist and are well supported on social-coding sites such as github. At various points in the life of a software project different support mechanisms are needed - whether this is promotion, hosting, colaborative tools or adminstrative support. TERENA already provides a home for many of the tools that the community uses, providing contractual arrangements, administration or infrastructure support for PEER, Confusa and Djangora to name just a few.
We'd like to look at how we are offering this support, how software projects can request support, and how we promote these software tools more generally to see if a more coordinated offering could be beneficial. At the moment this is just a discussion and requirements gathering process, but we'd love to hear your input and ideas. Initial discussion will draw on the open space session held at TNC2013. It is important to note that this is not currently a formal TERENA activity and no budget has been set for this work
GÉANT Special Interest Groups (SIGs) are established under the auspices of GÉANT in order to create an open forum where experts from its community exchange information, knowledge, ideas and best practices about specific technical or other areas of business relevant to the research and education networking community.
The aims of the Greenhouse SIG are:
- Supporting open source software projects that have the required level of maturity to join an appropriate software conservancy provided by a third party.
- Working with GÉANT to define an MoU for interactions with third party software conservancy organisations, including issues regarding cost for participation in such conservancies.
- Supporting open source projects in creating models for project governance and organisation via template documentation.
- Encouraging good practice in software development via best practice recommendations for code quality.
To sign-up to the mailing list, please visit:
httphttps://wwwlists.terenageant.org/mailinglists.php?list=greenhouse@terena.org.
Recent space activity
| Recently Updated | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Space contributors
| Contributors | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Why Greenhouse?
'Greenhouse' started out as a play on words as we didn't want to use the word 'conservancy' (conservancy - conservatory - greenhouse), as GÉANT is not looking to provide the sort of features one might expect from a full software conservancy but something more lightweight. The word has stuck as it seems a good way of describing the intentions here - to provide the infrastructure for software projects to grow successfully within the community.
The proposed achievements and KPIs for the first year
- Agree MoU with NLnet for Commons Conservancy.
- Create list of Open Source products produced by NRENs and in use with service dependency.
- Work with 2 projects on Commons Conservancy model.
- Work with projects on recommended software quality processes and run some tests.
- Create document promoting contributions to software projects to GA.
Useful Resources
Facts
2016 is the first year of the Greenhouse SIG. The Charter was approved at the TTC meeting in November 2015.
Steering Committee
- Guido Aben
- Glenn Wearen
- Leif Johansson
- Andrea Biancini
- Rogier Spoor
- Nicole Harris
Aims
The main topics covered by the new SIG would include, but would not be limited to:
- Supporting open source software projects that have the required level of maturity to join an appropriate software conservancy provided by a third party.
- Working with GÉANT to define an MoU for interactions with third party software conservancy organisations, including issues regarding cost for participation in such conservancies.
- Supporting open source projects in creating models for project governance and organisation via template documentation.
- Encouraging good practice in software development via best practice recommendations for code quality.