COmanage Developers List

Here are some notes + thoughts related to the CO service effort 
discussed on last friday's CO conference call. These are intended as 
a strawman. I'm trying to provoke some email-based discussion before 
the call, and see if we can get consensus on basic questions 
surrounding definitions + goals before we get on the phone tomorrow. 
Get out your red pens, and make comments and suggestions on these 
starting points

... and I'm sure I've forgotten a multitude of points... pls add them

The goal is to deploy a CO service as a "Pre-Production Pilot".

Definition -- "Pre-Production Pilot". The pilot will run on I2's 
supported VM infrastructure; the contents of the VMs will be backed 
up. Initially, the service will only be offered to short term 
projects with explicit termination dates (eg planning an upcoming 
meeting); the service will NOT be offered to groups with an ongoing 
mission (eg AMSAC).

Over some period of time, multiple groups will use the CO service 
(often in parallel). The service MUST support the ability to run 
multiple COs in parallel, in isolation from one another . The service 
MAY support some method for capturing the data held within the 
applications when a group shuts down its use of the CO service.

During the "Pre-Production Pilot" phase, there will be regular 
(bi-monthly?) reviews of operational issues. The CO developers and 
the I2 operations team will attend these reviews.

Functionality:

-- what is the process for vetting requests for new CO instances ?

-- the CO super admin can create a CO environment for a new group, 
and delegate the mgmt of the new instance to the CO leaders

-- the CO leaders have access to a collabmin intereface. They can 
enable applications for use by CO members, create and manage groups, 
invite others to be members of the CO, manage permissions within the 
applications

-- CO members can accept invitations, access a dashboard of some sort 
providing an overview of activity within the CO and the available 
applications and resources, directly access an application supporting 
the work of the CO