From: "Jeroen Roovers (jer)" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/ops: index.xml
Date: Mon, 08 Oct 2007 22:37:49 +0000 [thread overview]
Message-ID: <E1If1ET-0001Mv-TW@stork.gentoo.org> (raw)
jer 07/10/08 22:37:49
Modified: index.xml
Log:
Add list of tasks.
Revision Changes Path
1.13 xml/htdocs/proj/en/ops/index.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/ops/index.xml?rev=1.13&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/ops/index.xml?rev=1.13&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/ops/index.xml?r1=1.12&r2=1.13
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/ops/index.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- index.xml 8 Oct 2007 21:49:22 -0000 1.12
+++ index.xml 8 Oct 2007 22:37:49 -0000 1.13
@@ -4,7 +4,7 @@
<!DOCTYPE project SYSTEM "/dtd/project.dtd">
<project>
-<name>Ops</name>
+<name>#gentoo Ops</name>
<longname>The #gentoo Operators Project</longname>
<date>2007-10-08</date>
@@ -18,8 +18,14 @@
</p>
</longdescription>
-<dev role="Member">jer</dev>
<dev role="Member">blackace</dev>
+<dev role="Member">jer</dev>
+
+<!--<goals>
+<p>
+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.
+</p>
+</goals>-->
<extrachapter>
<title>List of #gentoo Operators</title>
@@ -55,6 +61,24 @@
</section>
</extrachapter>
+<extrachapter>
+<title>Tasks of the Ops Team</title>
+<section>
+<body>
+
+<table>
+ <tr><th>Task</th><th>Description</th></tr>
+ <tr><ti>Chanserv Access Levels</ti><ti>Chanserv access levels determine who gets which privileges in #gentoo (and #gentoo-ops).</ti></tr>
+ <tr><ti>Channel etiquette management</ti><ti>#gentoo has a language policy that the ops uphold. Furthermore, it's topic is Gentoo Linux support 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>
+ <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>
+ <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>
+ <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>
+</table>
+
+</body>
+</section>
+</extrachapter>
+
<extrachapter position="bottom">
<title>How to contact us</title>
<section>
--
gentoo-commits@gentoo.org mailing list
next reply other threads:[~2007-10-08 22:47 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 22:37 Jeroen Roovers (jer) [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-09-20 12:55 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/ops: index.xml Alex Legler (a3li)
2013-08-30 15:57 Jeroen Roovers (jer)
2009-08-20 19:34 Jeroen Roovers (jer)
2009-08-20 19:26 Jeroen Roovers (jer)
2008-12-03 23:58 Nicholas D. Wolfwood (blackace)
2008-10-01 3:24 Nicholas D. Wolfwood (blackace)
2008-03-31 15:45 Jeroen Roovers (jer)
2008-03-31 15:18 Jeroen Roovers (jer)
2008-02-13 0:30 Jeroen Roovers (jer)
2008-02-13 0:25 Jeroen Roovers (jer)
2008-02-13 0:24 Jeroen Roovers (jer)
2007-11-02 10:53 Jeroen Roovers (jer)
2007-11-02 5:42 Nicholas D. Wolfwood (blackace)
2007-11-02 5:38 Nicholas D. Wolfwood (blackace)
2007-11-01 19:47 Jeroen Roovers (jer)
2007-10-24 7:02 Jeroen Roovers (jer)
2007-10-24 4:12 Jeroen Roovers (jer)
2007-10-15 18:08 Jeroen Roovers (jer)
2007-10-11 3:34 Jeroen Roovers (jer)
2007-10-11 2:56 Jeroen Roovers (jer)
2007-10-10 17:16 Jeroen Roovers (jer)
2007-10-09 7:47 Jeroen Roovers (jer)
2007-10-09 1:13 Jeroen Roovers (jer)
2007-10-09 0:43 Jeroen Roovers (jer)
2007-10-09 0:29 Jeroen Roovers (jer)
2007-10-08 23:56 Jeroen Roovers (jer)
2007-10-08 23:54 Jeroen Roovers (jer)
2007-10-08 23:50 Jeroen Roovers (jer)
2007-10-08 22:57 Jeroen Roovers (jer)
2007-10-08 22:53 Jeroen Roovers (jer)
2007-10-08 22:47 Jeroen Roovers (jer)
2007-10-08 21:49 Jeroen Roovers (jer)
2007-10-08 21:48 Jeroen Roovers (jer)
2007-10-08 21:38 Jeroen Roovers (jer)
2007-10-08 21:36 Jeroen Roovers (jer)
2007-10-08 21:29 Jeroen Roovers (jer)
2007-10-08 21:22 Jeroen Roovers (jer)
2007-10-08 21:02 Jeroen Roovers (jer)
2007-10-08 20:55 Jeroen Roovers (jer)
2007-10-08 20:30 Jeroen Roovers (jer)
2007-10-08 19:36 Jeroen Roovers (jer)
2007-10-08 19:20 Jeroen Roovers (jer)
2007-10-08 18:38 Jeroen Roovers (jer)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1If1ET-0001Mv-TW@stork.gentoo.org \
--to=jer@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox