The following characteristics have been defined for the Greenhouse work, which clearly differentiates the offer from other options available to open software projects. These are expanded in more detail below.
- Trusted intermediary;
- Known jurisdiction;
- Light-touch;
- Community appropriate;
- Socialised.
It will be important to develop the TERENA Greenhouse offer along these principles to ensure it is fulfilling the community requirements. In order to evaluate the role of the Greenhouse, a range of different existing Software Conservancy models have been looked at, include Apache, Eclipse, Apereo, Free Software Foundation, and OpenAFS.
Trusted Intermediary.
In speaking to the projects that are interested in the Greenhouse, the most cited reason for TERENA to take on the role is that is already a known and trusted entity. TERENA also has the experience of managing contracts and funding for small-scale projects so can quickly understand the needs and requirements of the projects. As an intermediary, it is easier for potential funders to trust TERENA to effectively manage funds and often easier for organisations to be able to pass funding to an established legal entity such as TERENA rather than to the software developers themselves.
Known jurisdiction.
One of the most cited problems with using existing software conservancy approaches is that there are no conservancies based in Europe. EU and US law are different enough for this to cause problems not only for the projects but also for potential sponsors of the project. TERENA’s legal set-up within the Netherlands makes it an ideal organisation to take on such a role.
Light-touch.
The Greenhouse has been scoped as a lightweight supporting function for open-source software projects. It has no intention of becoming or offering the services of a full-scale Software Conservancy organisation, but rather to act as a broker for projects to ensure they can interact efficiently with potential funders and promote their projects to the community. The overheads and requirements of organisations such as Apache have been cited as a barrier-to-entry for small-scale software projects interested in finding a structure ‘home’.
The Greenhouse does not seek to offer code-audits or any other governance or control of the projects – success will be based on the socialization of the code discussed below. We do recognise that some projects may need or desire this route, so it is proposed that the TERENA Greenhouse works closely with the GEANT Software Support work areas and promotes that as a suitable route for projects seeking more robust hosting, testing and auditing. Discussions are already underway with GEANT to establish how this could be managed and supported.
Community Appropriate.
In general, software conservancy approaches tend to start around the needs of one specific piece or set of software and then expand to provide support for other similar initiatives. This creates a strong sense of community within the conservancy and around the software, but this can itself then be alienating for projects wishing to participate. Governance models also tend to follow the same path, with the Apache membership model cited as an example of why projects do not wish to use the Apache framework. TERENA is well placed to build on its own existing community whilst providing a central offer, which negates the need for each software project to try and replicate the efforts.
Socialised.
The socialisation aspect of the Greenhouse has two separate strands.
The Greenhouse will not offer any hosting for projects but will rely on github for code management and support. This has several benefits – it broadens the potential visibility of the projects, it provides a readily accessible platform in order to achieve rapid feedback and development and it gives potential clients a quick and clear overview of who is engaging with the project and how it is being developed and improved.
The other socialisation aspect is in terms of promoting the projects themselves. Most of our projects only get exposure within the direct community they are developed within – such as TCS or REFEDS – but have applicability and use cases beyond these environments. The TERENA Greenhouse project will develop a simple but effective website to promote the projects and clearly explain their funding models and customer base. It could be viewed as a “Net+” site for open source projects. (http://www.internet2.edu/netplus/).