From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path:
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 20D43198005
for ; Wed, 20 Mar 2013 17:13:06 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 972A9E072C;
Wed, 20 Mar 2013 17:13:03 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
(using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id D0E82E0616
for ; Wed, 20 Mar 2013 17:13:02 +0000 (UTC)
Received: by smtp.gentoo.org (Postfix, from userid 617)
id EDE8733D3D4; Wed, 20 Mar 2013 17:13:01 +0000 (UTC)
Date: Wed, 20 Mar 2013 17:13:01 +0000
From: Sven Vermeulen
To: gentoo-doc@lists.gentoo.org
Subject: [gentoo-doc] [RFC] GDP policy updates
Message-ID: <20130320171301.GA2851@gentoo.org>
Mail-Followup-To: gentoo-doc@gentoo.org
Precedence: bulk
List-Post:
List-Help:
List-Unsubscribe:
List-Subscribe:
List-Id: Gentoo Linux mail
X-BeenThere: gentoo-doc@lists.gentoo.org
Reply-to: gentoo-doc@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Archives-Salt: 5de2ae29-935e-4621-98a2-8ed1144182e1
X-Archives-Hash: b994df6a62940986dda68eb3b58b0777
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 @@
If the 2.5 version is used, the tag can be either <license /> or
-<license version="2.5" />. In either case should the comment be
+<license version="2.5" />. In either case must the comment be
updated to refer to the correct version URL.
@@ -200,9 +200,7 @@
Every bug reported on bugs.gentoo.org
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
-metadoc.xml file, if
-applicable.
+this using a comment on the bug.
@@ -377,9 +375,10 @@
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.