comanage-dev - domestication & groups
Subject: COmanage Developers List
List archive
- From: Tom Barton <>
- To: comanage-dev <>
- Subject: domestication & groups
- Date: Wed, 25 Feb 2009 15:25:29 -0600
Some of my U Chicago colleagues & I have been discussing what it will take to make a successful integration of sympa, confluence, and exchange calendaring, by which we mean not having to visit each one to reflect the same change to some real-world group.
We've come to recognize that part of the problem is that a person wanting to reflect a change might not know to go to a "console" specifically designed for that. Instead, they may be in sympa, or confluence, or outlook, and we want to either find a way to lead them easily from there to that common console, or just capture the change they make in one place and automatically reflect it elsewhere.
Please focus for the moment only on confluence. And let's rule out the case in which groups are provisioned into confluence's local store. So confluence is using groups residing outside it (ldap or grouper directly, say). What should happen when the user goes to the group-admin screen in confluence?
Tom
- domestication & groups, Tom Barton, 02/25/2009
- Re: [comanage-dev] domestication & groups, Scotty Logan, 02/25/2009
- Re: [comanage-dev] domestication & groups, Steven_Carmody, 02/25/2009
- Re: [comanage-dev] domestication & groups, Digant C Kasundra, 02/26/2009
Archive powered by MHonArc 2.6.16.