On Thu, Dec 2, 2010 at 5:17 PM, Alex North <[email protected]> wrote:
> I think this is rather too complex for wavelet permissions. In particular, > I think it's counter-productive that only Managers and above can add > participants. Sharing a wavelet is fundamentally valuable so in a linear > hierachy like this I think it should appear around editor or contributor. > This implies the Manager role is redundant. > > Perhaps some use cases describing some typical collaboration scenarios > would help settle this list. It's also not clear that a linear hierachy is > the right model, as opposed to orthogonal capabilities, though it does have > the advantage of being simple. > At the time I thought of those roles I hadn't yet worked out a capabilities model that could be used to represent those roles as well as others. What's in the groups notes wavelet is more thought out but still needs work. -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.
