From: Sven Vermeulen <swift@gentoo.org>
To: gentoo-doc@lists.gentoo.org
Subject: [gentoo-doc] [RFC] GDP policy updates
Date: Wed, 20 Mar 2013 17:13:01 +0000 [thread overview]
Message-ID: <20130320171301.GA2851@gentoo.org> (raw)
Hi guys,
I'd like to suggest a few changes on our GDP policy, namely:
- updating the license comment if you use a different license should be
mandatory (hence switch from "should" to "must")
Reason: I think this is a "typo" as "must" fits more in the idea of that
paragraph.
- drop using metadoc.xml for registering long outstanding bugs
Reason: it was a nice idea, but never truely used
- have project lead (or delegated person) "decide" on the recruitment
process / progress
Reason: we already dropped the time frame windows in the past, but wasn't
really clear who then decides that a phase can go through or not. So make
it explicit that it is the lead (or a delegated person)
- drop mandatory gdp quiz, make it recommended
Reason: we already have a contribution period where the recruit sends in
contributions or patches; the knowledge on the GuideXML, as far as needed
for the tasks the recruit wants to do, should be apparent from the
contributions.
The quiz requires more knowledge than we might expect from most
documentation developers (not in the past, but given the resources at hand
right now, it makes sense to remove the mandatory requirement).
Below is the suggested change on the policy.
Comments are of course welcome (otherwise I wouldn't mail to the mailinglist
:-P)
Wkr,
Sven Vermeulen
Index: doc-policy.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gdp/doc/doc-policy.xml,v
retrieving revision 1.27
diff -u -B -r1.27 doc-policy.xml
--- doc-policy.xml 29 Nov 2011 19:01:23 -0000 1.27
+++ doc-policy.xml 20 Mar 2013 17:04:40 -0000
@@ -186,7 +186,7 @@
<p>
If the 2.5 version is used, the tag can be either <c><license /></c> or
-<c><license version="2.5" /></c>. In either case should the comment be
+<c><license version="2.5" /></c>. In either case must the comment be
updated to refer to the correct version URL.
</p>
@@ -200,9 +200,7 @@
Every bug reported on <uri link="http://bugs.gentoo.org">bugs.gentoo.org</uri>
should be handled as fast as possible. If a bug cannot be handled
in a timely fashion, the reporter of that bug should be informed about
-this using a comment on the bug, and the bug should be registered in the
-<uri link="/proj/en/gdp/doc/metadoc-guide.xml">metadoc.xml</uri> file, if
-applicable.
+this using a comment on the bug.
</p>
<p>
@@ -377,9 +375,10 @@
<p>
If you feel that you have shown sufficient amount of contributions, contact
-the project lead of the Gentoo Documentation Project. He will ask you for your
-coordinates and other information, and then arrange for the next phase to be
-started.
+the project lead of the Gentoo Documentation Project who will review the
+contributions and the timeframe (or delegate this towards another GDP member).
+He will ask you for your coordinates and other information, and
+then arrange for the next phase to be started.
</p>
</body>
@@ -403,22 +402,20 @@
</p>
<p>
-During this period, the recruit:
+During this period, the recruit: is advised to learn about Gentoo's inner workings.
+This is required as he or she will be asked later on to answer Gentoo's <uri
+link="/proj/en/devrel/quiz/staff-quiz.txt">Staffing Quiz</uri>.
</p>
-<ul>
- <li>
- is advised to learn about Gentoo's inner workings.
- This is required as he or she will be asked later on to answer Gentoo's <uri
- link="/proj/en/devrel/quiz/staff-quiz.txt">Staffing Quiz</uri>.
- </li>
- <li>
- will be asked to fill in the <uri
- link="/proj/en/gdp/doc/doc-quiz.xml">Gentoo Documentation Project
- Quiz</uri>. He or she needs to successfully pass this entire quiz
- (all questions) before we can continue with the next Phase.
- </li>
-</ul>
+<p>
+It is also recommended, but not automatically required, to fill in the <uri
+link="/proj/en/gdp/doc/doc-quiz.xml">Gentoo Documentation Project Quiz</uri>.
+This will assist the recruit in learning more about how the Gentoo Documentation
+Project documentation works. If at a later time the Gentoo Documentation Project
+lead feels that the recruit (or by then editor or author) shows insufficient
+knowledge on this, he might ask the recruit (or by then editor or author) to
+work on the quiz after all.
+</p>
</body>
</section>
@@ -441,9 +438,9 @@
<p>
If the recruit is already a Gentoo Developer, the same recruitment process is
-followed, but the staffing quiz is not necessary anymore. However, the <uri
+followed, but of course the staffing quiz is not necessary anymore. The <uri
link="/proj/en/gdp/doc/doc-quiz.xml">Gentoo Documentation Project Quiz</uri> is
-still mandatory.
+still recommended.
</p>
</body>
next reply other threads:[~2013-03-20 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 17:13 Sven Vermeulen [this message]
2013-03-20 18:17 ` [gentoo-doc] [RFC] GDP policy updates Tobias Heinlein
2013-03-21 18:13 ` Chema Alonso
2013-03-21 23:26 ` Joshua Saddler
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=20130320171301.GA2851@gentoo.org \
--to=swift@gentoo.org \
--cc=gentoo-doc@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