Wave Groups would be analogous to Email groups. Essentially a proxy for a number of different users.
Essentially if you want to send a wave to the sales team you wouldn't include everyones address in the wave, rather you would simply add [email protected] and it would appear in each sales group members inbox. James On Sat, Nov 27, 2010 at 11:30 AM, Michael MacFadden < [email protected]> wrote: > Tad, > > Can you expand on exactly what the group functionality is? Is is just > a permissions scheme? Is it a new kind of model element (like a peer > to wavelet). I think the roles you define make sense, but I am > missing the bigger picture of what this functionality is all about. > > ~Michael > > On Nov 26, 4: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]<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.
