Changes between Version 30 and Version 31 of GEC14Agenda/IMDesignTopics


Ignore:
Timestamp:
07/02/12 14:54:43 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC14Agenda/IMDesignTopics

    v30 v31  
    7070 * Next steps, during Spiral 5 [[BR]]
    7171
    72  * For more information, audit {http://groups.geni.net/geni/wiki/GIMIv1.0Tutorial  GIMI v1.0 tutorial]  [[BR]]
     72 * For more information, audit [http://groups.geni.net/geni/wiki/GIMIv1.0Tutorial  GIMI v1.0 tutorial]  [[BR]]
    7373
    7474
     
    111111 * Next steps, during Spiral 5 [[BR]]
    112112
    113  * For more information, audit {http://groups.geni.net/geni/wiki/GEMINITutorial  GEMINI v1.0 tutorial]  [[BR]]
     113 * For more information, audit [http://groups.geni.net/geni/wiki/GEMINITutorial  GEMINI v1.0 tutorial]  [[BR]]
    114114
    115115
     
    339339
    340340Goals
    341  * Working and supported v1.0 GIMI tools should be readily available to users of ExoGENI racks   (who is lead?)  [[BR]]
    342  * Working and supported v1.0 GEMINI tools should be readily available to users of InstaGENI racks (and ProtoGENI/Emulab clusters)  (who is lead?)  [[BR]]
    343  * Tutorial for GIMI tool set must be kept up-to-date, so that users can teach themselves  (who is lead?)  [[BR]]
    344  * Tutorial for GEMINI tool set must be kept up-to-date, so that users can teach themselves  (who is lead?)  [[BR]]
    345  * Bugs must be gathered, tracked and fixed by GIMI team;  final acceptance test will be performed by the GPO  (who is lead?)  [[BR]]
    346  * Bugs must be gathered, tracked and fixed by GEMINI team;  final acceptance test will be performed by the GPO   (who is lead?) [[BR]]
    347  * Feature requests must be gathered, tracked and evaluated by GIMI team  (who is lead?)  [[BR]]
    348  * Feature requests must be gathered, tracked and evaluated by GEMINI team  (who is lead?)  [[BR]]
    349 
    350  * v1.1 of GIMI tools must be released by GEC15, including bug fixes and new features, fully tested and ready for day-to-day use  (who is lead?)   [[BR]]
    351  * v1.1 of GEMINI tools must be released by GEC15, including bug fixes and new features, fully tested and ready for day-to-day use  (who is lead?)   [[BR]]
    352 
    353  * User Worksapce should be readily available to users, with bug fixes and new features.  (Jeanne Ohren)  [[BR]]
    354  * XML messaging service should provide agreed-upon features, and be reliably operational  (who is lead?)    [[BR]]
    355  * iRODS archive service should provide agreed-upon features, and be reliably operational  (who is lead?)  [[BR]]
    356  * IREEL analysis and presentation service should provide agreed-upon features, and be reliably operational  (who is lead?)  [[BR]]
    357  * INSTOOLS portal-to-GUIs service should provide agreed-upon features, and be reliably operational  (who is lead?)   [[BR]]
    358  * Unified Network Information Service (UNIS) should provide agreed-upon features, and be reliably operational  (who is lead?)  [[BR]]
     341 * Both GIMI and GEMINI tools should be available to Users during this period  [[BR]]
     342  * Bug tracking system, plus periodic bug fixes   (who are leads?)  [[BR]]
     343  * Acceptance testing by the GPO (Jeanne Ohren)  [[BR]]
     344
     345 * Both GIMI and GEMINI must provide a high level of support to Users  [[BR]]
     346  * Tutorials must be kept up-to-date and operational, so that Users can teach themselves. (who are leads?)  [[BR]]
     347  * Instructions must be continuously refined, to make the tools easier to use. (who are leads?)  [[BR]]
     348  * Requested tool extensions must be gathered from users, based upon their experience. (who are leads?)  [[BR]]
     349  * Users with advanced requirements must be found, better identify gaps in the tools.  How? (who are leads?)  [[BR]]
     350  * Tool extensions must be proposed by the teams, and reviewed with the users.  How? (who are leads?)  [[BR]]
     351  * A list of tool extensions needs to be developed for inclusion into v1.1, due at GEC15. (who are leads?)  [[BR]]
     352
     353 * Persistent multi-user services must be reliably available to all Users  [[BR]]
     354  * User Worksapce   (Jeanne Ohren)  [[BR]]
     355  * XML messaging service  (who is lead?)    [[BR]]
     356  * iRODS archive service   (who is lead?)  [[BR]]
     357  * IREEL analysis and presentation service    (who is lead?)  [[BR]]
     358  * INSTOOLS portal-to-GUIs service   (who is lead?)   [[BR]]
     359  * Unified Network Information Service (UNIS)   (who is lead?)  [[BR]]
    359360
    360361