| 1 |
jer 07/11/01 19:47:17 |
| 2 |
|
| 3 |
Modified: index.xml |
| 4 |
Log: |
| 5 |
Added chapter about participation. Set maximum textwidth. |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.30 xml/htdocs/proj/en/ops/index.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/ops/index.xml?rev=1.30&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/ops/index.xml?rev=1.30&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/ops/index.xml?r1=1.29&r2=1.30 |
| 13 |
|
| 14 |
Index: index.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/ops/index.xml,v |
| 17 |
retrieving revision 1.29 |
| 18 |
retrieving revision 1.30 |
| 19 |
diff -u -r1.29 -r1.30 |
| 20 |
--- index.xml 24 Oct 2007 07:02:02 -0000 1.29 |
| 21 |
+++ index.xml 1 Nov 2007 19:47:17 -0000 1.30 |
| 22 |
@@ -6,24 +6,30 @@ |
| 23 |
<project> |
| 24 |
<name>ops</name> |
| 25 |
<longname>The #gentoo Operators Project</longname> |
| 26 |
-<date>2007-10-24</date> |
| 27 |
+<date>2007-11-01</date> |
| 28 |
<author title="Author"> |
| 29 |
<mail link="jer" /> |
| 30 |
</author> |
| 31 |
|
| 32 |
<description> |
| 33 |
-The #gentoo Operators project describes the tasks and policies carried out by the operators of the #gentoo channel on the Freenode network. |
| 34 |
+The #gentoo Operators project describes the tasks and policies carried out by |
| 35 |
+the operators of the #gentoo channel on the Freenode network. |
| 36 |
</description> |
| 37 |
|
| 38 |
<longdescription> |
| 39 |
<p> |
| 40 |
-The #gentoo Operators project describes the tasks and policies carried out by the operators (ops) of the #gentoo channel on the Freenode network. Among other things, it aims to clarify the way #gentoo is run and by whom, who to address to resolve conflicts between channel ops and other channel users. |
| 41 |
+The #gentoo Operators project describes the tasks and policies carried out by |
| 42 |
+the operators (ops) of the #gentoo channel on the Freenode network. Among other |
| 43 |
+things, it aims to clarify the way #gentoo is run and by whom, who to address to |
| 44 |
+resolve conflicts between channel ops and other channel users. |
| 45 |
</p> |
| 46 |
</longdescription> |
| 47 |
|
| 48 |
<goals> |
| 49 |
<p> |
| 50 |
-The goal of the #gentoo operators project is to clarify how #gentoo is maintained. Most of the communication about actual channel management takes place on IRC, and this project aims to describe who do it and how we do it. |
| 51 |
+The goal of the #gentoo operators project is to clarify how #gentoo is |
| 52 |
+maintained. Most of the communication about actual channel management takes |
| 53 |
+place on IRC, and this project aims to describe who do it and how we do it. |
| 54 |
</p> |
| 55 |
</goals> |
| 56 |
|
| 57 |
@@ -68,12 +74,43 @@ |
| 58 |
<body> |
| 59 |
|
| 60 |
<table> |
| 61 |
- <tr><th>Task</th><th>Description</th></tr> |
| 62 |
- <tr><ti>Chanserv access levels</ti><ti>Chanserv access levels determine who gets which privileges in #gentoo (and #gentoo-ops).</ti></tr> |
| 63 |
- <tr><ti>Channel etiquette management</ti><ti>#gentoo has a language policy that the ops uphold. Furthermore, the channel's topic is <e>Gentoo Linux support</e> and it is not a "chat" channel — ops may direct users to other channels that are more appropriate when a discussion has little or nothing to do with Gentoo Linux support.</ti></tr> |
| 64 |
- <tr><ti>Abuse management</ti><ti>When a user abuses #gentoo, he gets warned, muted (+q), banned or banforwarded. Conflicts are resolved in #gentoo-ops. Bans may normally only be unset by the banner — she has a responsibility to set reasonable bans.</ti></tr> |
| 65 |
- <tr><ti>Topic updates</ti><ti>When many users come to the channel having the same technical issue with Gentoo, the channel's topic is updated with references to bot FAQs or web page URLs.</ti></tr> |
| 66 |
- <tr><ti>Bot FAQs</ti><ti>#gentoo has three official ircbots: jeeves, mzbot and Naamah. While the latter only serves to kick users who paste more than a few lines in rapid succession (flood protection), the former two respond to simple commands and may offer information that is regularly updated by the ops.</ti></tr> |
| 67 |
+ <tr><th>Task</th> |
| 68 |
+ <th>Description</th> |
| 69 |
+ </tr> |
| 70 |
+ <tr> |
| 71 |
+ <ti>Chanserv access levels</ti> |
| 72 |
+ <ti>Chanserv access levels determine who gets which privileges |
| 73 |
+ in #gentoo (and #gentoo-ops).</ti> |
| 74 |
+ </tr> |
| 75 |
+ <tr> |
| 76 |
+ <ti>Channel etiquette management</ti> |
| 77 |
+ <ti>#gentoo has a language policy that the ops uphold. |
| 78 |
+ Furthermore, the channel's topic is <e>Gentoo Linux support</e> |
| 79 |
+ and it is not a "chat" channel — ops may direct users to |
| 80 |
+ other channels that are more appropriate when a discussion has |
| 81 |
+ little or nothing to do with Gentoo Linux support.</ti> |
| 82 |
+ </tr> |
| 83 |
+ <tr> |
| 84 |
+ <ti>Abuse management</ti> |
| 85 |
+ <ti>When a user abuses #gentoo, he gets warned, muted (+q), |
| 86 |
+ banned or banforwarded. Conflicts are resolved in #gentoo-ops. |
| 87 |
+ Bans may normally only be unset by the banner — she has a |
| 88 |
+ responsibility to set reasonable bans.</ti> |
| 89 |
+ </tr> |
| 90 |
+ <tr> |
| 91 |
+ <ti>Topic updates</ti> |
| 92 |
+ <ti>When many users come to the channel having the same |
| 93 |
+ technical issue with Gentoo, the channel's topic is updated with |
| 94 |
+ references to bot FAQs or web page URLs.</ti> |
| 95 |
+ </tr> |
| 96 |
+ <tr> |
| 97 |
+ <ti>Bot FAQs</ti> |
| 98 |
+ <ti>#gentoo has three official ircbots: jeeves, mzbot and |
| 99 |
+ Naamah. While the latter only serves to kick users who paste |
| 100 |
+ more than a few lines in rapid succession (flood protection), |
| 101 |
+ the former two respond to simple commands and may offer |
| 102 |
+ information that is regularly updated by the ops.</ti> |
| 103 |
+ </tr> |
| 104 |
</table> |
| 105 |
|
| 106 |
</body> |
| 107 |
@@ -84,17 +121,54 @@ |
| 108 |
<title>Channel management</title> |
| 109 |
<section> |
| 110 |
<body> |
| 111 |
-<p>Compared to most IRC channels on Freenode and indeed on other IRC networks, #gentoo has a very strict policy and this policy is enforced as strictly as possible. #gentoo is the focal point of many support enquiries and can be very busy at times. Because of the ~1000 users that chat (and lurk) in #gentoo, making it one of the largest channels on the Freenode network, and perhaps also because of the mild animosity that any Linux distribution causes among users of other Linux distributions, it is also the focal point of spammers, pranksters, and trolls.</p> |
| 112 |
-<p>The policy set up to manage #gentoo is therefore very straightforward and simple:</p> |
| 113 |
+<p>Compared to most IRC channels on Freenode and indeed on other IRC networks, |
| 114 |
+#gentoo has a very strict policy and this policy is enforced as strictly as |
| 115 |
+possible. #gentoo is the focal point of many support enquiries and can be very |
| 116 |
+busy at times. Because of the ~1000 users that chat (and lurk) in #gentoo, |
| 117 |
+making it one of the largest channels on the Freenode network, and perhaps also |
| 118 |
+because of the mild animosity that any Linux distribution causes among users of |
| 119 |
+other Linux distributions, it is also the focal point of spammers, pranksters, |
| 120 |
+and trolls.</p> |
| 121 |
+<p>The policy set up to manage #gentoo is therefore very straightforward and |
| 122 |
+simple:</p> |
| 123 |
<ul> |
| 124 |
-<li>The topic of the channel is Gentoo Linux support. Off topic chat, even mild flamewars about program X versus program Y, will usually be met with a request to take the discussion elsewhere, and consequent muting (+q) or banishment if users persist.</li> |
| 125 |
-<li>Discussion of #gentoo management is off topic. The appropriate place to discuss matters of #gentoo policy and its enforcement is #gentoo-ops, the userrel project or the ops mailing list (and not #gentoo — it's just too busy for that).</li> |
| 126 |
-<li>Because of the varied nature of Gentoo users and the varied environments in which they might use #gentoo, the channel has a strict language policy, meaning that anything you wouldn't dare say to your proverbial grandmother, you shouldn't say in #gentoo.</li> |
| 127 |
+ <li>The topic of the channel is Gentoo Linux support. Off topic chat, |
| 128 |
+ even mild flamewars about program X versus program Y, will usually be |
| 129 |
+ met with a request to take the discussion elsewhere, and consequent |
| 130 |
+ muting (+q) or banishment if users persist.</li> |
| 131 |
+ <li>Discussion of #gentoo management is off topic. The appropriate place |
| 132 |
+ to discuss matters of #gentoo policy and its enforcement is #gentoo-ops, |
| 133 |
+ the userrel project or the ops mailing list (and not #gentoo — |
| 134 |
+ it's just too busy for that).</li> |
| 135 |
+ <li>Because of the varied nature of Gentoo users and the varied |
| 136 |
+ environments in which they might use #gentoo, the channel has a strict |
| 137 |
+ language policy, meaning that anything you wouldn't dare say to your |
| 138 |
+ proverbial grandmother, you shouldn't say in #gentoo.</li> |
| 139 |
</ul> |
| 140 |
</body> |
| 141 |
</section> |
| 142 |
</extrachapter> |
| 143 |
|
| 144 |
+<extrachapter> |
| 145 |
+<title>Participating</title> |
| 146 |
+<section> |
| 147 |
+<body> |
| 148 |
+<p>Both Gentoo developers and users can become #gentoo ops. The selection |
| 149 |
+process basically works as in any other Gentoo project: if you put in the work, |
| 150 |
+helping users in #gentoo, you are certain to get noticed and may get asked to |
| 151 |
+join the team.</p> |
| 152 |
+<p>Operator status in #gentoo is not intended as status symbol: operators are |
| 153 |
+given privileges only to effectively uphold service standards in #gentoo. |
| 154 |
+Regular contributors are given AUTOVOICE (level 10), so they have voice in the |
| 155 |
+channel even when the channel mode mutes other users. Regular contributors who |
| 156 |
+are interested in maintaining channel security may be given CMDOP (level 20) to |
| 157 |
+"op up" when needed. All operators (level 20 and above) are listed in this |
| 158 |
+document.</p> |
| 159 |
+<p>Operator status shall be removed after a period of inactivity (not using |
| 160 |
+level 20 privileges for a good while (say a couple of months).</p> |
| 161 |
+</body> |
| 162 |
+</section> |
| 163 |
+</extrachapter> |
| 164 |
|
| 165 |
<extrachapter position="bottom"> |
| 166 |
<title>How to contact us</title> |
| 167 |
@@ -103,7 +177,8 @@ |
| 168 |
<body> |
| 169 |
|
| 170 |
<p> |
| 171 |
-To send e-mail to the #gentoo operators team, point your favourite e-mail client to ops@g.o. |
| 172 |
+To send e-mail to the #gentoo operators team, point your favourite e-mail |
| 173 |
+client to ops@g.o. |
| 174 |
</p> |
| 175 |
|
| 176 |
</body> |
| 177 |
@@ -113,7 +188,9 @@ |
| 178 |
<title>On Freenode</title> |
| 179 |
<body> |
| 180 |
<p> |
| 181 |
-/join #gentoo-ops if you want to chat directly with #gentoo operators. Also, any urgent issues with regard to #gentoo channel management (abuse, pointers to important bugs that affect many users) should be brought to our attention there. |
| 182 |
+/join #gentoo-ops if you want to chat directly with #gentoo operators. Also, any |
| 183 |
+urgent issues with regard to #gentoo channel management (abuse, pointers to |
| 184 |
+important bugs that affect many users) should be brought to our attention there. |
| 185 |
</p> |
| 186 |
</body> |
| 187 |
</section> |
| 188 |
|
| 189 |
|
| 190 |
|
| 191 |
-- |
| 192 |
gentoo-commits@g.o mailing list |
Archives