public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sven Vermeulen <swift@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Documentation linkage or location
Date: Fri, 24 Oct 2003 10:45:18 +0200	[thread overview]
Message-ID: <20031024084518.GB1422@gentoo.org> (raw)
In-Reply-To: <49627.141.166.208.137.1066928961.squirrel@spidermail.richmond.edu>

[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]

On Thu, Oct 23, 2003 at 01:09:21PM -0400, donnie berkholz wrote:
> My understanding of the Project Doc Editor's role is that he has authority
> to review and commit changes of docs in that project. Am I
> misunderstanding that role?

The Project Doc Editor is the developer who will take on bugreports
on the documentation of his (or her) project in case technical changes are
needed. He is a full member of the documentation team, but doesn't have to do
documentation editing for other documents (although he is free to do so).

When a patch is created, independent of who made the patch and why, it must
be reviewed by a second person (a gentoo developer) to check for
inconsistencies, other errors and such. This reviewing step is mandatory
unless:
	- the patch must be applied asap because the current documentation
	  breaks systems
	- the patch is to fix grammatical issues or typos

In some cases, this means a one-man job (if the bugreport already has a
patch, then he (or she) can review the patch and commit); in most cases you
write up a patch and attach it to the bugreport. One of our editors will then
verify the patch and state (as a comment on the bugreport) that the patch is
fine (or something with the same meaning :)

The documentation team works by the documentation policy [1], although a new
change [2] on that policy which removes some difficulties is waiting.

Wkr,
	Sven Vermeulen

[1] http://www.gentoo.org/doc/en/doc-policy.xml
[2] http://emu.gentoo.org/~swift/doc-policy.html

-- 
 ^__^   And Larry saw that it was Good.
 (oo)                                      Sven Vermeulen
 (__)   http://www.gentoo.org              Gentoo Documentation Project

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-10-24  8:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-23  7:30 [gentoo-dev] Documentation linkage or location Sven Vermeulen
2003-10-23  7:38 ` Robin H. Johnson
2003-10-23  9:49   ` Sven Vermeulen
2003-10-23  8:51 ` Paul de Vrieze
2003-10-23  9:52 ` Donnie Berkholz
2003-10-23 13:33   ` Sven Vermeulen
2003-10-23 17:09     ` donnie berkholz
2003-10-24  8:45       ` Sven Vermeulen [this message]

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=20031024084518.GB1422@gentoo.org \
    --to=swift@gentoo.org \
    --cc=gentoo-dev@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