It has been recognised that different products or projects will have very different needs from a software conservancy organisation like the TERENA Greenhouse. The following Product Needs Assessment is a starter requirements gathering exercise for projects to better understand how we can help provide support.
- FUNDING AND FINANCES
| OpenConext response |
---|
How is the project currently funded? Do you receive money from individual organisations or from grants (e.g. GN3) | The project is funded by SURFnet. No money or grants sought or received. |
---|
How do you intend to fund the project in the future? Would you expect the Greenhouse to collect funds from organisations or other funding sources? Are there any barriers to this? | N.A. Project will be funded by SURFnet in the future too. |
---|
Would you like the Greenhouse to pay individual developers or other staff for you? | No |
---|
Would you like the Greenhouse to pay other bills for you, e.g. hosting costs, promotional materials etc. | No |
---|
What costs are currently associated with the project? | We are not sure. |
---|
2. LEGAL AGREEMENTS | OpenConext response |
---|
Do you have any contracts or consortium agreement arrangements for people to pay money in to the project? Would you require something like this in the future, are there any specific requirements around this and would you be happy using a generic framework proposed by the Greenhouse? | No, No, No, Yes |
---|
Do you need the Greenhouse to manage contracts for staff such as developers? | No |
---|
Do you need the Greenhouse to act as a home / signing authority for other purposes (e.g. domain registration, home address etc). | No |
---|
Would you like to run your project yourself but need support in getting advice for writing agreements and managing contracts? | No |
---|
What are the current licensing / IPR arrangements for the product? | https://www.openconext.org/about/licenses |
---|
3. TECHNICAL REQUIREMENTS | OpenConext response |
---|
Do you need the Greenhouse to offer any hosting for project software (wiki, bug tracker, mailing lists etc)? | No |
---|
Do you need the Greenhouse to help you source good developers / software houses? | Yes, would be helpfull |
---|
Would you like to use a central Greenhouse helpdesk manager? | No |
---|
4. PROMOTION AND COORDINATION | OpenConext response |
---|
Would you like the Greenhouse to offer any central staffing support such as project manager, contract manager, or PR and Comms? | No |
---|
5. CURRENT USAGE AND REQUIREMENTS | OpenConext response |
---|
Please provide some information about the current and potential user base for the product | 1 million users in the Netherlands with a potential for world domination. See https://www.openconext.org/showcases |
---|
How many people currently work on the project and what is the expectation for the future in terms of involvement and funding? | 28, see https://github.com/orgs/OpenConext/people |
---|
| |
---|
6. POSITIONING WITHIN THE GREENHOUSE | OpenConext response |
---|
Would you be happy for your project to be listed with features on a Greenhouse promotional website? | YES! |
---|
Are you happy that your project will sit within a framework of other projects being offered similar services? | Yes |
---|
Are you happy that the project must first be accepted by the Greenhouse Steering Committee and will have an incubation period of assessment? | Fine |
---|
Are you willing to commit a certain percentage of project funding to the central Greenhouse function? | No |
---|