| 1 |
<?xml version="1.0" encoding="utf-8" ?>
|
| 2 |
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
| 3 |
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
|
| 4 |
<!--
|
| 5 |
This HTML is auto-generated. DO NOT EDIT THIS FILE! If you are writing a new
|
| 6 |
PEP, see http://www.python.org/peps/pep-0001.html for instructions and links
|
| 7 |
to templates. DO NOT USE THIS HTML FILE AS YOUR TEMPLATE!
|
| 8 |
-->
|
| 9 |
<head>
|
| 10 |
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
| 11 |
<meta name="generator" content="Docutils 0.3.7: http://docutils.sourceforge.net/" />
|
| 12 |
<title>GLEP 38 -- Status of forum moderators in the Gentoo project</title>
|
| 13 |
<link rel="stylesheet" href="tools/glep.css" type="text/css" />
|
| 14 |
</head>
|
| 15 |
<body bgcolor="white">
|
| 16 |
<table class="navigation" cellpadding="0" cellspacing="0"
|
| 17 |
width="100%" border="0">
|
| 18 |
<tr><td class="navicon" width="150" height="35">
|
| 19 |
<a href="http://www.gentoo.org/" title="Gentoo Linux Home Page">
|
| 20 |
<img src="http://www.gentoo.org/images/gentoo-new.gif" alt="[Gentoo]"
|
| 21 |
border="0" width="150" height="35" /></a></td>
|
| 22 |
<td class="textlinks" align="left">
|
| 23 |
[<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>]
|
| 24 |
[<b><a href="http://www.gentoo.org/proj/en/glep">GLEP Index</a></b>]
|
| 25 |
[<b><a href="./glep-0038.txt">GLEP Source</a></b>]
|
| 26 |
</td></tr></table>
|
| 27 |
<table class="rfc2822 docutils field-list" frame="void" rules="none">
|
| 28 |
<col class="field-name" />
|
| 29 |
<col class="field-body" />
|
| 30 |
<tbody valign="top">
|
| 31 |
<tr class="field"><th class="field-name">GLEP:</th><td class="field-body">38</td>
|
| 32 |
</tr>
|
| 33 |
<tr class="field"><th class="field-name">Title:</th><td class="field-body">Status of forum moderators in the Gentoo project</td>
|
| 34 |
</tr>
|
| 35 |
<tr class="field"><th class="field-name">Version:</th><td class="field-body">1.1</td>
|
| 36 |
</tr>
|
| 37 |
<tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference" href="http://www.gentoo.org/cgi-bin/viewcvs/xml/htdocs/proj/en/glep/glep-0038.txt?cvsroot=gentoo">2005/06/24 21:32:46</a></td>
|
| 38 |
</tr>
|
| 39 |
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Christian Hartmann <christian.hartmann at email.de>,
|
| 40 |
Wernfried Haas <w.haas at xover.htu.tuwien.ac.at>.</td>
|
| 41 |
</tr>
|
| 42 |
<tr class="field"><th class="field-name">Status:</th><td class="field-body">Draft</td>
|
| 43 |
</tr>
|
| 44 |
<tr class="field"><th class="field-name">Type:</th><td class="field-body">Informational</td>
|
| 45 |
</tr>
|
| 46 |
<tr class="field"><th class="field-name">Content-Type:</th><td class="field-body"><a class="reference" href="glep-0012.html">text/x-rst</a></td>
|
| 47 |
</tr>
|
| 48 |
<tr class="field"><th class="field-name">Created:</th><td class="field-body">06-May-2005</td>
|
| 49 |
</tr>
|
| 50 |
<tr class="field"><th class="field-name">Post-History:</th><td class="field-body">17-Jun-2005</td>
|
| 51 |
</tr>
|
| 52 |
</tbody>
|
| 53 |
</table>
|
| 54 |
<hr />
|
| 55 |
<div class="contents topic" id="contents">
|
| 56 |
<p class="topic-title first"><a name="contents">Contents</a></p>
|
| 57 |
<ul class="simple">
|
| 58 |
<li><a class="reference" href="#abstract" id="id11" name="id11">Abstract</a></li>
|
| 59 |
<li><a class="reference" href="#motivation" id="id12" name="id12">Motivation</a></li>
|
| 60 |
<li><a class="reference" href="#specification" id="id13" name="id13">Specification</a></li>
|
| 61 |
<li><a class="reference" href="#rationale" id="id14" name="id14">Rationale</a></li>
|
| 62 |
<li><a class="reference" href="#backwards-compatibility" id="id15" name="id15">Backwards Compatibility</a></li>
|
| 63 |
<li><a class="reference" href="#reference-implementation" id="id16" name="id16">Reference Implementation</a></li>
|
| 64 |
<li><a class="reference" href="#id1" id="id17" name="id17">References</a></li>
|
| 65 |
<li><a class="reference" href="#copyright" id="id18" name="id18">Copyright</a></li>
|
| 66 |
</ul>
|
| 67 |
</div>
|
| 68 |
<div class="section" id="abstract">
|
| 69 |
<h1><a class="toc-backref" href="#id11" name="abstract">Abstract</a></h1>
|
| 70 |
<p>Global moderators and site admins should also go through the mentoring process
|
| 71 |
and become official Gentoo staff.</p>
|
| 72 |
</div>
|
| 73 |
<div class="section" id="motivation">
|
| 74 |
<h1><a class="toc-backref" href="#id12" name="motivation">Motivation</a></h1>
|
| 75 |
<p>At the time of writing the forums are apart from the recruiting process and
|
| 76 |
people helping out there are not made an official part of Gentoo. This GLEP
|
| 77 |
aims on creating and establishing a recruitment and mentoring process for
|
| 78 |
moderators and site admins of forums.gentoo.org. By doing this we hopefully
|
| 79 |
achieve a (even) better moderation quality and stop the complaints about
|
| 80 |
moderators not being staff. Moderators and site admins do not need cvs
|
| 81 |
access.</p>
|
| 82 |
<p>Moderators and site admins are doing a hard job for the community as well as all
|
| 83 |
the other projects do but they get no voice in the gentoo internals. Recent events
|
| 84 |
such as the election of trustees or the new metastructure poll are effectively
|
| 85 |
affecting the forums, so the wish to be part of the decision as an equal member
|
| 86 |
is present among the moderators.</p>
|
| 87 |
<p>Moderators are often a contact person between users and developers, so we
|
| 88 |
should try to improve the communication between these two groups of people. As
|
| 89 |
moderators are pretty much exposed to the public (forums users, but also used
|
| 90 |
as contact person for requests that should go to the PR department or the
|
| 91 |
trustees) they need to have some knowledge about Gentoo's internal structure
|
| 92 |
as well as contact to the other developers.</p>
|
| 93 |
<p>The current training process for new moderators works pretty well even though
|
| 94 |
there are no official guidelines how to do it. As part of this proposal a more
|
| 95 |
detailed procedure for the training process will be established to make it
|
| 96 |
more reproducable. It also gives us the possibility to document the things
|
| 97 |
happening already today in the current training process.</p>
|
| 98 |
<p>The status of the Gentoo Forums has been undefined for quite some time. Since
|
| 99 |
it is using the gentoo.org domain it should be considered an official project.
|
| 100 |
People working on an official project should be developers or staff following Gentoo's
|
| 101 |
general policy. At the moment the persons with direct access to the database
|
| 102 |
are developers. Being moderator could be considered an improved forums rank
|
| 103 |
that does not have impact on Gentoo's infrastructure, but since moderators and
|
| 104 |
administrators are able to delete, move and edit posts on the forum willingly,
|
| 105 |
their level of access should be considered developer like. Many users may not
|
| 106 |
be aware of the difference between moderators and developers, so the actions of a
|
| 107 |
moderator may represent Gentoo Linux to them anyway.</p>
|
| 108 |
</div>
|
| 109 |
<div class="section" id="specification">
|
| 110 |
<h1><a class="toc-backref" href="#id13" name="specification">Specification</a></h1>
|
| 111 |
<p>To obtain a certain kind of quality assurance and to (create and) ensure that
|
| 112 |
upcoming moderators know about the forums guidelines a document and processes
|
| 113 |
will have to be created and established that the recruits need to follow.
|
| 114 |
This document (called <a class="reference" href="http://curtis119.no-ip.org/forum-guide.xml">Moderators handbook/FAQ</a> <a class="footnote-reference" href="#id2" id="id3" name="id3">[1]</a>) will include the moderation guidelines
|
| 115 |
as they are currently available in the moderators forum plus a FAQ that was created as
|
| 116 |
a possible candidate for a forums-quiz. The guidelines and the FAQ should help the
|
| 117 |
moderator to get some general information about how to moderate the forums.</p>
|
| 118 |
<p>Suggested procedure for becoming global moderator:
|
| 119 |
Existing moderators can suggest a user to become a moderator. The ability of the new
|
| 120 |
moderator to deal with people in a kind way and to detect misplaced posts, etc usually
|
| 121 |
also has been reviewed by the other moderators already since they can read his
|
| 122 |
previous posts and suggestions in the forums feedback threads.
|
| 123 |
If he accepts, he will become moderator on the forums. A bug will be filed on b.g.o
|
| 124 |
containing information about the new moderator. Afterwards he must answer the staff
|
| 125 |
quiz that will be revisited by devrel. The quiz then will be send to <a class="reference" href="mailto:recruiters@g.o">recruiters@g.o</a> for
|
| 126 |
revision.</p>
|
| 127 |
<p>The first month is supposed to be a test period, if the moderator
|
| 128 |
does not do anything in that time or messes up in another way, he will be
|
| 129 |
restored to his old user status. The mentor(s) and everyone of the forums team
|
| 130 |
are encouraged to help the new moderator if he is unsure how to deal with a
|
| 131 |
situation.</p>
|
| 132 |
</div>
|
| 133 |
<div class="section" id="rationale">
|
| 134 |
<h1><a class="toc-backref" href="#id14" name="rationale">Rationale</a></h1>
|
| 135 |
<p>The process of aquiring new developers seems to work for the rest of Gentoo
|
| 136 |
Linux quite well. A mentoring system has been chosen since new moderators were
|
| 137 |
mentored unofficially by the other moderators anyway. This means more or less
|
| 138 |
writing down things that have been done already.
|
| 139 |
It was discussed to add a forums-specific quiz to the process of aquiring new
|
| 140 |
moderators.
|
| 141 |
Devrel's standing on that is that it is up to the moderators how a new moderator is
|
| 142 |
chosen. Since the old process worked fine so far and some people among the moderators
|
| 143 |
didn't exactly like the idea of a quiz, we chose not to make one. A document containing the
|
| 144 |
questions collected for the quiz in form of a FAQ together with the moderation
|
| 145 |
guidelines seems to be a more feasible approach. The new moderators are supposed to
|
| 146 |
read the FAQ as well as they had to take a quiz, so they will learn the information
|
| 147 |
given in this document.</p>
|
| 148 |
</div>
|
| 149 |
<div class="section" id="backwards-compatibility">
|
| 150 |
<h1><a class="toc-backref" href="#id15" name="backwards-compatibility">Backwards Compatibility</a></h1>
|
| 151 |
<p>Most moderators are currently not staff members. Becoming a staff member is not mandatory
|
| 152 |
for existing moderators. If they want to become a staff member they need to take the
|
| 153 |
staff quiz. If they don't they just stay in their position as moderator without
|
| 154 |
becoming a staff member.</p>
|
| 155 |
<p>Moderators who are currently inactive (Bodhisattva status) should be
|
| 156 |
considered as old moderators in case they come back. New moderators should
|
| 157 |
have to go through the mentoring process in any case as stated above.</p>
|
| 158 |
<p>Moderators in national forums: In our internal discussion it turned out that not
|
| 159 |
all moderators in the national forums are able to speak english well, which
|
| 160 |
would be a requirement to become a staff member. We decided that it would
|
| 161 |
counter productive to make it mandatory for them. Becoming a staff member is
|
| 162 |
optional for these moderators.</p>
|
| 163 |
<p>As a side effect of the discussion about the glep among the moderators
|
| 164 |
as well as in discussions with other developers and devrel, it turned
|
| 165 |
out that the forums have never been assigned to a toplevel project in the
|
| 166 |
general organization of the Gentoo project. Forums don't really seem to fit
|
| 167 |
into one of the current categories as they are related to the infrastructure
|
| 168 |
and the documentation project. We suggest putting it in the other category
|
| 169 |
or making a separate one for the forums.</p>
|
| 170 |
</div>
|
| 171 |
<div class="section" id="reference-implementation">
|
| 172 |
<h1><a class="toc-backref" href="#id16" name="reference-implementation">Reference Implementation</a></h1>
|
| 173 |
<ul class="simple">
|
| 174 |
<li><a class="reference" href="http://curtis119.no-ip.org/forum-guide.xml">Moderators handbook/FAQ</a> <a class="footnote-reference" href="#id2" id="id4" name="id4">[1]</a></li>
|
| 175 |
<li><a class="reference" href="http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=1&chap=2">Becoming a developer</a> <a class="footnote-reference" href="#id5" id="id6" name="id6">[2]</a></li>
|
| 176 |
<li><a class="reference" href="http://www.gentoo.org/proj/en/devrel/quiz/staff-quiz.txt">Staff quiz</a> <a class="footnote-reference" href="#id7" id="id8" name="id8">[3]</a></li>
|
| 177 |
<li><a class="reference" href="http://thread.gmane.org/gmane.linux.gentoo.devel/28985">Thread on gentoo-dev</a> <a class="footnote-reference" href="#id9" id="id10" name="id10">[4]</a></li>
|
| 178 |
</ul>
|
| 179 |
</div>
|
| 180 |
<div class="section" id="id1">
|
| 181 |
<h1><a class="toc-backref" href="#id17" name="id1">References</a></h1>
|
| 182 |
<table class="docutils footnote" frame="void" id="id2" rules="none">
|
| 183 |
<colgroup><col class="label" /><col /></colgroup>
|
| 184 |
<tbody valign="top">
|
| 185 |
<tr><td class="label"><a name="id2">[1]</a></td><td><em>(<a class="fn-backref" href="#id3">1</a>, <a class="fn-backref" href="#id4">2</a>)</em> <a class="reference" href="http://curtis119.no-ip.org/forum-guide.xml">http://curtis119.no-ip.org/forum-guide.xml</a></td></tr>
|
| 186 |
</tbody>
|
| 187 |
</table>
|
| 188 |
<table class="docutils footnote" frame="void" id="id5" rules="none">
|
| 189 |
<colgroup><col class="label" /><col /></colgroup>
|
| 190 |
<tbody valign="top">
|
| 191 |
<tr><td class="label"><a class="fn-backref" href="#id6" name="id5">[2]</a></td><td><a class="reference" href="http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=1&chap=2">http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=1&chap=2</a></td></tr>
|
| 192 |
</tbody>
|
| 193 |
</table>
|
| 194 |
<table class="docutils footnote" frame="void" id="id7" rules="none">
|
| 195 |
<colgroup><col class="label" /><col /></colgroup>
|
| 196 |
<tbody valign="top">
|
| 197 |
<tr><td class="label"><a class="fn-backref" href="#id8" name="id7">[3]</a></td><td><a class="reference" href="http://www.gentoo.org/proj/en/devrel/quiz/staff-quiz.txt">http://www.gentoo.org/proj/en/devrel/quiz/staff-quiz.txt</a></td></tr>
|
| 198 |
</tbody>
|
| 199 |
</table>
|
| 200 |
<table class="docutils footnote" frame="void" id="id9" rules="none">
|
| 201 |
<colgroup><col class="label" /><col /></colgroup>
|
| 202 |
<tbody valign="top">
|
| 203 |
<tr><td class="label"><a class="fn-backref" href="#id10" name="id9">[4]</a></td><td><a class="reference" href="http://thread.gmane.org/gmane.linux.gentoo.devel/28985">http://thread.gmane.org/gmane.linux.gentoo.devel/28985</a></td></tr>
|
| 204 |
</tbody>
|
| 205 |
</table>
|
| 206 |
</div>
|
| 207 |
<div class="section" id="copyright">
|
| 208 |
<h1><a class="toc-backref" href="#id18" name="copyright">Copyright</a></h1>
|
| 209 |
<p>This document has been placed in the public domain.</p>
|
| 210 |
</div>
|
| 211 |
|
| 212 |
</div>
|
| 213 |
<hr class="docutils footer" />
|
| 214 |
<div class="footer">
|
| 215 |
<a class="reference" href="glep-0038.txt">View document source</a>.
|
| 216 |
Generated on: 2005-06-24 21:32 UTC.
|
| 217 |
Generated by <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source.
|
| 218 |
</div>
|
| 219 |
</body>
|
| 220 |
</html>
|
| 221 |
|
Parent Directory
| 
Revision Log
