Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel
titlePlan

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).

 

Gliffy Diagram
namegreenhouse-plan

 

 

Detailed project plan: 

...

Detailed project plan: 

Project Management Phases

PHASEDESCRIPTIONCOMMENTASSIGNED TOSTART DATEEND DATESTATUS
1. Pre-project (preparation)

 

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

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

NH10/201311/2014
Status
colourGreen
titleCOMPLETE
2. InitiationGather requirements and the options to implement the greenhouse     
2.1 Needs assessment

Document list of requirements for different products.

 

Output: Assess a select number of key products.

Possible tools to asses: Open Conext, File Sender, Simple SAMLphp, MediaMosa, (TCS software?)

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

See also:

Product Needs Assessment

NH12 Feb 201520 Feb 2015
Status
colourGreen
titleCOMPLETE
2.2 Gathering info on models to implement the greenhouse

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

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

Update 090415: Uploaded preliminary (draft) document (Greenhouse Possible Approches v0.1.docx) based on the product needs assessment completed so far.

AS20 Feb 201527 Feb 2015

Status
colourGreen
titleCOMPLETE

2.3 Presenting the most suitable optionsPrepare a document to present a short list of options and their risks/benefits.Output: short document with recommendations on the approach to implementLF

 23 Feb 2015

 

Planned for 15 May 2015

First version Delivered 26 May 2015

There was a presnetation at the TAC where support was received from NORDUNET, AARNET and I2.

Status
colourGreen
titleCOMPLETE
3.  Selection      
Select most suitable modelSelect the approach to implement

The preliminary work carried out in the previous step resulted in recommending to partner with an exiting company which would effectively operate the greenhouse framework.  A presentation was given at the TAC meeting during TNC.

 

Management17 Aug 2015

PID sent to the Amsterdam MT.

The PID was presented to the PMO on 25th of Aug.

Status
colourGreen
titleCOMPLETE
4. Execution

 

 

    
Phase 1 - Mid Sep- End Nov
  1.  Organise a workshop in Amsterdam to present a possible model to implement the greenhouse

 

Output: workshop report with communty feedback

 

LF30 Sep 201530 Sep 2015
Status
colourGreen
titlecomplete
 2. Incude feedback from the workshop and start the testing phase fo the Greenhouse with the FileSender team External work - LF to gather the feedback1 Oct 2015 TBC after the workshop30 Oct 2015
Status
titleNot Started
 3. Provide evaluation report from Fliesender experience and proposal for permanent greenhouse structure. Output: report 1 Nov 201530 Nov 2015
Status
titleNot Started
5. Closing Phase 1
 Output: MoU witht NLNet