incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache OpenOffice.org Community > Changes integrate the forums into the AOOo project
Date Thu, 06 Oct 2011 06:18:00 GMT
Space: Apache OpenOffice.org Community (https://cwiki.apache.org/confluence/display/OOOUSERS)
Page: Changes integrate the forums into the AOOo project (https://cwiki.apache.org/confluence/display/OOOUSERS/Changes+integrate+the+forums+into+the+AOOo+project)


Edited by Peter Roelofsen:
---------------------------------------------------------------------
h1. Changes to integrate the forums into the AOOo project


h2. 1. Community

The forum community divides in:

* Site Admins
* Forum Admins
* Moderators
* Volunteers

Volunteers are registered users of the forum(s) with a post count of over 200 (or another
lower limit), who visit and post regularly to answer questions, report spam and in general
show commitment to the forum(s), as opposed to regular registered users who may never post
at all or post infrequently, or mostly post to ask questions. Volunteers can vote on forum
policy decisions - in the forums - just like moderators and administrators. Moderators and
administrators of nl forums also get the volunteer rank for the English forum, regardless
of how often they post there. A volunteer may lose that rank after long inactivity (but will
be restored on his/her return).

{color:#ff0000}{_}CONFLICT: At the current form of the message board, a Volunteer has a binding
vote (see comment below). In the ASF world, committer votes are usually non-binding. To keep
the binding vote, every volunteer must join the PMC, which is not the usual case in the ASF
world. In ASF world, after getting committership you earn PMC-ship. (grobmeier)_{color}

{color:#ff0000}{_}We're talking at cross purposes here. Volunteers etc vote in the forum -
where else could they vote in the past? They can continue to vote in the forum, where their
vote will be taken seriously, but they can't vote in the PMC if they aren't committers. (Peter
Roelofsen)_{color}

Admins are persons with access to the underlying forum code and who work with the phpBB admin
control panel.
Moderators are maintainers of the board, they have access to the moderator panel, removing
spam, marking topics as Solved or Issue, editing topic titles to make them more meaningful
or removing all caps, warning people who seriously misbehave, but not applying censorship
except in case of very explicit language.

The following  proposal was compiled from a lengthy discussion on the EN and ES forums by
FJCC [http://user.services.openoffice.org/en/forum/viewtopic.php?f=90&t=43901&start=180#p204949].
It contains the contributions of several forum members, including Apache Observers.

h2. Proposal
*A.* Forum governance will be discussed in a publicly readable forum. Write access will be
limited to those with at least 10 posts. The previous governance forum will become read only
with access limited to Volunteers, Moderators and Admins. This is to protect the personal
information that was posted on that forum.
*B.* The Forum Issues section will remain private with access limited to Volunteers, Moderators
and Admins and will be used only to discuss user behavior or similarly sensitive topics
*C.* Forum admins must sign the ICLA. They will interact with the Apache Infra group and should
be official project members. At least one Moderator, who will sign the ICLA, or Admin on every
NL forum will commit to reporting forum status to the Project as determined by the PPMC
*D.* Moderators and Volunteers will keep their current functions and will be created through
the traditional process of nomination and lazy consensus on the forum.
*E.* Any Apache member can request Apache Observer status and thereby gain read and write
access to all forums, including Forum Issues, and have read access to the logs. Apache Observers
will not have the capability to edit, delete or move posts or perform administrative functions.
*F.* Any decisions made by the PPMC with respect to the forums or the forum members will be
posted on the Site Governance forum or, in the case of a sensitive topic, on the Forum Issues
forum.
*G.* The new Terms of Use will be similar to the current ToU, particularly the clause that
"You hereby grant to the Host and all Users a royalty-free, perpetual, irrevocable, worldwide,
non-exclusive and fully sub-licensable right and license under Your intellectual property
rights to reproduce, modify, adapt, publish, translate, create derivative works from, distribute,
perform, display and use Your Submissions (in whole or part) and to incorporate them in other
works in any form, media, or technology now known or later developed, all subject to the obligation
to retain any copyright notices included in Your Submissions. All Users, the Host, and their
sublicensees are responsible for any modifications they make to the Submissions of others."
*H.* Should the ASF decide to terminate its support of the forums, it will grant a period
of at least 90 days for the transfer of the contents and structure of the forums to another
host as decided by the Administrators, Moderators and Volunteers.
*I.* While the forums operate within the Apache podling/project they will have the same domain/URL
as before the transfer.

{color:#ff0000}{_}CONFLICT: Are all current volunteers eligible for the PMC? This would lead
to add 70 persons to the PMC immediately. (grobmeier)_{color}

h2. 2. Technical changes

The forum is maintained via private subboards currently.

*Proposal #1:*
The private boards are put to read only.
A new public board "site governance" is established to discuss forum related tasks. The messages
are sent automatically to a readonly mailinglist name "forum-sitegovernance@".
A new private board "private xxx" is established to discuss sensitive tasks, like for example
user behavior. The messages are sent automatically to "private@" with a specific tag \[OOODEV:forum\].

Change your notification preferences: https://cwiki.apache.org/confluence/users/viewnotifications.action
   

Mime
View raw message