COmanage Developers List

["Michael R. Gettes" <>]

See inline...

On Feb 20, 2009, at 15:00, Steve Olshansky wrote:

> Q: Will any of the apps in the alpha package be domesticated in  
> terms of groups?
>
> A: Sympa yes, Drupal and Confluence not yet clear.

Maybe the definition of "domesticated" is too complex if this is not  
yet clear?

> Q: if we have interface specs and infrastructure for app  
> integration, what other capabilities will be required for true  
> "domestication"? What other packaging, or what will need to be  
> assumed about an app for integration with COmanage? E.g. config file  
> location(s), web services hooks, etc.?
>
> A: Unclear at this point -- this may be a fairly long way out. We  
> can play a role in terms of providing a spec for how apps could and  
> should behave, and COmanage can certainly help a non-technical  
> manager administer their systems. A consistent GUI (dashboard) for  
> managing multiple key elements of collaborative apps (e.g. groups)  
> is itself a big win.
>
> It was suggested that recording the characteristics that an app  
> should possess (best practices) in order to be "easy to domesticate"  
> as a guide for developers would be useful, e.g. externalizing AuthN,  
> ability to use LDAP for groups management, APIs for external  
> privilege management, etc. Also noting known apps that meet these  
> criteria, or at least have capabilities that make them amenable for  
> integration with COmanage (e.g. Sympa and Confluence), would be  
> useful for reference.

!!!!!!!!!!!!!!!!!

> Q: Would Kuali be domesticate-able as it currently exists?
>
> A: Apparently not...

Kuali what?  Rice?  probably not.  Student?  Why not?  The only items
I see missing from Kuali Student for Authn/Z are bulk operations and
a clear definition of version control.  I have communicated these issues
to Kuali Student.

I have other observations and comments but I will wait a bit.

/mrg