On Thu, 9 Jul 2009, Peter Tribble wrote:
On Thu, Jul 9, 2009 at 7:41 PM, Jim Walker<[email protected]> wrote:
At the OGB meeting today we discussed the planned user roles and
privileges[1]. There were several concerns raised.
Others with follow-up with there concerns, but I would like to
request the reasoning behind the decision to use the "Developer"
and "Affiliate" term instead of the "Contributor" term in the
Project and User Group collectives.
Unless there is good reason for adding these new terms, I think the
term "Contributor" should be used consistently across all collectives
to reduce confusion and eliminating the possibility of community
members interpreting that the role terminology implies different
status or capabilities. The current model especially impacts community
members that contribute to multiple collect types.
Cheers,
Jim
[1] http://opensolaris.org/os/community/web/transition-roles-collectives/
I have two key concerns:
1. Whatever roles apply on the website should be completely independent
of governance. Neither should imply the other. Therefore connecting the
ability to do operations on the website with ones' constitutional voting rights
is a mistake. (I note that the current auth app separates electoral
responsibilities
from website responsibilities - something that the above document doesn't make
clear.)
2. Similarly, standing within a collective should be independent of
website editing
rights. Collectives may wish to designate a small group of people (who
may simply
have an administrative role) to edit the website. Other models are possible.
I agree with Peter here. For example, we have many contributors to the
security community, but I am not sure we want each & every one to have
authorization to edit the webpages. We currently have not extended
that right to all of our contributors.
Valerie
--
Valerie Fenwick, http://blogs.sun.com/bubbva/ @bubbva
Solaris Security Technologies, Developer, Sun Microsystems, Inc.
17 Network Circle, Menlo Park, CA, 94025.
_______________________________________________
website-discuss mailing list
[email protected]
