Alan Burlison wrote:
If we go forward with the new website roles as described in the
transition-roles-collectives document above, we will be forced to perform a
formal CG vote anytime we wish to grant someone website edit rights
(Contributor) or admin rights (Core Contributor). Not only will this
unreasonably delay granting website access rights by at least 72 hours[1],
it is likely to cause people to be given Constitutional roles they don't
merit or want. Which is the opposite of what we want in terms of
ease-of-use and a well qualified electorate.
No, only the creation of Core Contributors requires CG and OGB involvement.
Contributors can edit web pages in Hub, and they can be created in Auth by
the existing Core Contributors of a Community. I've explained that several
times already.
But in practice the same voting process is used for Contributors as Core
Contributors by most CGs. Which I think should be expanded to all CGs since
the Contributor role is permanent per the constitution. If CGs add
Contributor designations add hoc it only makes the situation worse.
Having website management for CGs require Core Contributor and OGB involvement
every time a CG wants to give someone edit or admin rights is an unnecessary
waste of time by the people who already are the most busy.
Why can't two new CG access right roles be added to allow CGs to operate
the same as Projects and User Groups?
Cheers,
Jim
[1] ARTICLE VIII - http://opensolaris.org/os/community/ogb/governance/
_______________________________________________
website-discuss mailing list
[email protected]
