Since Wave is not going to be a purely Google endeavor, I think it should be something other than Google Groups, though we definitely want to have some easy import/export features. Groups should be like individual participants in that servers hold the group lists for all groups in their domain ([email protected] would be some sort of list of addresses stored on acme.com, but could contain users from any domain).
Random side note: you can be in a wave in a group and as an individual participant at the same time, but your individual status overrides your group status, so individuals can be upgraded or downgraded while the group's general settings remain the same. On Nov 26, 2:21 pm, Vega <[email protected]> wrote: > That would be really important addition to wiab. By the way, how do > you intend to implement the groups functionality in wiab? Is it > related to google groups? > > On Nov 26, 7:38 pm, 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]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
