You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Plan

This section describes the plan to move the greenhouse concept forward.

 

Aim of this project: define a model to sustain the software developed by the GEANT association as a whole (including its members and/or associated peers worldwide).

 

greenhouse-plan

 

 

 

Activity NameDescriptionCommentStart MonthEnd MonthStatus
1. Concept Definition

Explore approaches to sustain software produced in the context of a collaboration where no model is already in place.

Assigned to: Nicole

The idea of the Greenhouse has been discussed for a while.

All the background work done is available on this wiki space:

Differentiating the TERENA Greenhouse

 

Oct 2013Nov 2014DONE
2. InitiationGather requirements and the options to implement the greenhouse    
   2.1 Needs assessment

Document list of requirements for different products.

Assigned to: Nicole

Update 210115: SimpleSAMLphp and Filesender have completed the product needs assessment and Surfnet have promised to complete.  Initial sounding call with Apereo undertaken.

Output: Assess a select number of key products.

Informal conversation with some R&E projects is ongoing for some time. Possible tools to asses: Open Conext, File Sender, Simple SAMLphp, MediaMosa, (TCS software?)

See also:

Product Needs Assessment

12 Feb 201520 Jan 2015IN PROGRESS
   2.2 Gather info on models to implement the greenhouse

Short list of possible approaches  that match the core requirements identified in 2.1.

Assigned to: Alessandra

 

 

Output: a matrix on the wiki with possible approaches.

Possible existing organisations to interview are: NLLab, OSS Watch, Apereo.

This task can start in parallel with 2.1 as some of the aspects are known. See also:

Software Sustainability Within the TERENA Community

Differentiating the TERENA Greenhouse

20 Feb 201527 Feb 2015NOT STARTED
   2.3 Document to present the most suitable options

Prepare a document to present a short list of options and their risks/benefits.

Assigned to: Licia

Output: short document with recommendations on the approach to implement23 Feb 201531 March 2015NOT STARTED
3.  Select most suitable modelSelect the approach to implement.To be discussed by the management31 March 201514 April 2015NOT STARTED
4. Execution

Implement the selected model.

Assigned to: TBD

Output: light weighted execution plan to assing resources

 

TNC could be a good opportunity to gather some feedback if a proof-of-concept were available.

15 April 2015End JunNOT STARTED
      

 

 

  • No labels