Thanks for starting this off Tad. I too think adding groups support is an important feature to work on, perhaps in the new year after our initial WIAB task list<https://sites.google.com/a/waveprotocol.org/wave-protocol/code/wave-in-a-box-task-list?pli=1>is complete.
I've refrained from responding earlier because groups and access control are complex issues and I wanted to have time to think deeply about your proposals. Some of the Googlers here have a lot of knowledge from implementing groups and (some) access control in Google Wave which I hope can inform WIABs implementation. I'm not suggesting WIAB should do exactly the same thing, but we learned some important things which it would be unfortunate to need to re-learn the hard way. In particular, Google Wave's very simple roles system arose because defining robust access control in Wave is very difficult. We never reached a design that we were happy with, though we have ideas about what an appropriate design might look like. I'm glad that in future messages you've separated the concerns of groups from those of wavelet access control. They are clearly related, but they are also relatively independent. IMO groups support is both more valuable as a product feature and easier to implement (and educational), so I'd suggest focussing on that first. Keep access control in mind, but I think we'll get rapidly confused if we try to do everything at once. I'll respond to a few of the smaller comments in these threads now. However, groups is definitely something that warrants a thorough design before we write too much code. Email is unfortunately a poor medium for iterating on designs, so I propose using either a Wave or a Google Doc. A. On 26 November 2010 12:38, Tad Glines <[email protected]> wrote: > I'm working on adding group support to WiaB and also looking at the issue > of wavelet permissions. > > As a starting point I want to propose some group and wavelet roles and > solicit feedback. > > For groups the roles I'm proposing are: > > - Reader > - May read waves on which the group is a participant. > - Contributor > - Includes Reader capabilities > - May submit deltas to wavelets for which group is a participant. > The delta author must be the submitter. > - Manager > - Includes Contributor capabilities > - May add/remove members to/from the group and modify the role of > existing members, but only if: > - The member is self > - The member is NOT a manager > - The member is NOT an owner > - Owner > - Includes Manager capabilities > - May add/remove members to/from the group and modify the role of > existing members, but only if: > - The member is self > - The member is NOT an owner. > > For wavelets the roles I'm proposing are: > > > > - Reader > - May read wavelet content > - Contributor > - Includes Reader capabilities > - May add new wavelet content. In the context of a conversation > wavelet, this implies adding new blips. > - May edit own content. In the context of a conversation this > implies editing or deleting own blips. > - Editor > - Includes Contributor capabilities > - May add/edit/delete any content. > - Manager > - Includes Editor capabilities > - May add/remove participants and modify the roles of any exiting > participant if: > - Participant is self > - Participant is NOT a Manager > - Participant is NOT an Owner > - Owner > - Includes Manager capabilities > - May add/remove participants and modify the roles of any exiting > participant if: > - Participant is self > - Participant is NOT an Owner > > For both groups and wavelets the creator would be granted the owner role. > > -Tad > > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
