Skip to Content.
Sympa Menu

comanage-dev - Re: [comanage-dev] scenarios for video #2

Subject: COmanage Developers List

List archive

Re: [comanage-dev] scenarios for video #2


Chronological Thread 
  • From: "Michael R. Gettes" <>
  • To: Scotty Logan <>
  • Cc: Ken Klingenstein <>,
  • Subject: Re: [comanage-dev] scenarios for video #2
  • Date: Thu, 28 Aug 2008 18:08:23 -0400

On Aug 28, 2008, at 17:57, Scotty Logan wrote:

On Aug 22, 2008, at 5:11 PM, Ken Klingenstein wrote:
1. collabmin adds user from alphabets global to a particular subgroup, removes another. voiceover talks about the permissions so granted, removed (e.g. this user can now access the subgroup wiki, will be on the committee email list, can access new parts of the cvs)

<pedantic>we should be careful about maintaining the distinction between group membership and permissions / entitlements</pendantic>

2. collabmin allows users from one subcommittee permission to read but not write on another groups wiki space. (pointing out it can be done either at the comanage or the wiki layer, and pros/cons). do we want to show that we can expire this permission automatically at a certain date? (can we?)

None of the tools we're deploying support external permissions. Of the wikis I've seen, Confluence seems to have the best grasp of permissions management, but it's still internal. The collabmin can create groups and add members to them in Grouper, but to use those groups they have to go into Confluence and grant permissions on spaces to those groups.

if you consider something like Sympa MLM then you could provide
a tool supporting external permissions.

/mrg



Archive powered by MHonArc 2.6.16.

Top of Page