Alan Coopersmith wrote: > michelle olson wrote: > >> Collective: Roles >> ---------------------------------------------------------------------- >> >> User Group: User, User with ssh key, Admin, Leader, Member >> Project: Admin, Leader, Member >> Working Committee: Admin, Leader, Member >> >> This assumes the following changes: >> -Communities migrate to Projects >> -User Groups migrate to their new collective >> -We add Member as a role within Projects >> -We migrate Contributors to Leaders >> -We migrate Core Contributors to Members >> > > This seems backwards to me - Core Contributors should become Project Leaders, > and Contributors should become Project Members. Member has a vote, so that is why CCs would migrate to Members. Contributors have no vote, so they would migrate to Project Leaders. Does this make sense? 'Member' as defined in our meetings and in the Constitution is a voting contributor. > I'm not sure what the > difference between Admin & Leader is for a Project - what privileges does > each get? Admin is the person who sets up the Project pages initially. Leader has edit privs and SCM privs. > We certainly don't want the current webapp bug of > "Leader" = "Web Page Editor", since many projects will want members be able > to edit web pages without granting them other leadership privileges. > OK, then we need to make that distinction somewhere, so Alan knows about the change. I think the change would be to add another role (committer, or something), to differentiate between Leader.
Thanks, Michelle
