...
The COmanage service offering isn't going to be available in the short-term. There is some interest in it, but there are questions around where it would be housed and what would the service model would be.
The initial emphasis will be on getting collaboration infrastructure working for LIGO and iPlant.
...
Michael Gettes was the original developer an and set up a mockup instance. That was a great proof of concept.
There was an attempt to develop a downloadable COmanage instance, a VM. This became a sys admin challenge rather than a collab solution. Too It became too big a problem for the available resources, and was shelved for the time being.
Today the focus is on solutions that groups like LIGO can stand up and manage themselves at their own institutions.
...
Random participant - generally just access the applications
Collaboration admin ("Collabmin") - can invite a new participant
COmanage admin - can initiate provision a new collaboration environment
Details on the roles and their capabilities are found here:
...
Discussion (led by Heather)
Q: Is the work that has been described on target? Is it the kind of thing you are looking for?
...
Suggestion: On the COmanage reference architecture diagram, add an area for domain apps.
Researchers Researchers want to get their science done. They want it to be efficient and quick.
StevenC: In some areas, outside the hard sciences, the domain apps are not as big a concern.
At SMMthe last Internet2 Spring Member Meeting, there was a presentation from Pepperdine showing a method of creating a front door to Google Apps and other applications. http://www.internet2.edu/presentations/spring10/20100427-googleapps-gautsch.pdf
...
Q: Should COmanage handle administration of grant research in addition to the research itself? Should we connect to Fast LaneFastLane?
Comment: There are fears about identities leaking out. As always, solid authenticiation and authorization is crucial.
...