The Enhanced User Groups design proposal has been updated to incorporate feedback received (mostly offlist, alas) on the previous iteration.
The major changes from the previous version are:
* Added a "Description" field to groups. This is primarily so each group can include instructions on how to request addition to the group (since Beaker won't initially be offering the ability for users to request membership of groups) * Added the ability to add group members that can *only* submit jobs (without being able to modify that group's jobs). This better supports an approach where a single automated service submits jobs on behalf of multiple users and groups. * Added a missing use case covering modification of a group's details (the display name and description) * Changed the name of the "group-manage" subcommand to "group-modify" * Clarified several limitations of LDAP-based groups * Documented the planned upgrade strategy (i.e. all existing groups are considered to allow shared job management, with no owners. The administrators of the Beaker installation will need to explicitly grant a member ownership access in order to enable self-management of an existing group.
Current version of the proposal: http://beaker-project.org/dev/proposals/enhanced-user-groups.html
All changes from previous version: http://git.beaker-project.org/cgit/beaker-project.org/commit/?id=98a0014b058...
Regards, Nick.
beaker-devel@lists.fedorahosted.org