COmanage Developers List

[Heather Flanagan <>]

Hi folks -

As we're moving forward with comanage, a few nifty questions have  
come up both in specific for one of our use-cases (OOI) and in  
general for comanage.


1 - Does OOI want to run comanage internally, or do they want to be  
able to go somewhere for this?
** I suggest that any VO that wants to use comanage should have at  
least one of their institutions hosting the service.  I think there  
would be issues in terms of branding of the service and resources  
being used at an institution not part of the VO that makes the  
hosting model less than ideal.  Other thoughts?

2 - Given the interest in Confluence as one of the possible wikis,  
what do we need from Altassian to roll Confluence in to the appliance  
that is comanage?
** My biggest worry here is what kind of blessings would we need to  
roll Confluence in to a virtual appliance?  How would the licensing  
work?

3 - Given that comanage is targeting researchers, how do we need to  
handle the security issues for the data?  (See FISMA)
** One take on this is that the hosting institution needs to handle  
security, but we may be ready/willing/able to do more in this area.   
It's certainly something to talk about!  What do you all think?


In general, I think most of our discussions will be electronic in  
nature.  I will be setting up a once-a-month meeting for at least the  
core comanage developers just to go over in person (or dial in) where  
we are and perhaps do a demo of the current state of affairs.

Heather Flanagan
Director, System Administration