From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Maintainer's guides?
Date: Mon, 28 Nov 2005 11:39:08 +0100 [thread overview]
Message-ID: <200511281139.16339.pauldv@gentoo.org> (raw)
In-Reply-To: <200511271843.01552@enterprise.flameeyes.is-a-geek.org>
[-- Attachment #1: Type: text/plain, Size: 2539 bytes --]
On Sunday 27 November 2005 18:43, Diego 'Flameeyes' Pettenò wrote:
> On Thursday 24 November 2005 12:31, Diego 'Flameeyes' Pettenò wrote:
> > What I'm waiting for now are comments if someone has ideas where to
> > put guides that does not belong directly to an existant project. And
> > if someone wants to join the effort of documenting maintenance
> > process for his packages, it would be helpful, too.
>
> Trying not to let this idea die, as I still think it might be good in
> the long run, especially if there's a way to get them collected in a
> single place. Right now the main problem is that they are spread across
> projects (at least video/sound projects).
>
> Possible solutions I thought of:
>
> 1) have every herd controlled by a project, so that the maintainers'
> guides can be committed there; it would be difficult to find the
> maintainer's guide for a package this way;
> 2) have a single repository for maintainers' guides that does not
> belong to other projects;
> 3) have a single repository for *every* maintainers' guide.
>
> The problem with 1 and 2 is that the maintainers' guides would be
> difficult to locate in the mess of projects. The problem of 3 is that
> we have already complex maintainers' guides such as xine's and the one
> spyderous wrote for X11 herd, that might be difficult to fit in a
> single organization..
>
I agree with you. Although it is straightforward to provide a reverse
mapping from packages to herds to projects, that currently doesn't exist.
> To solve 1's and 2's problem, the solution could be adding a
> <maintainerguide> tag to metadata.xml, that carries the URL to the
> maintainer's guide for the package. It would also make simpler, for
> example, the case where a single guide is used for more than one
> package (see always xine's).
In any way I like the idea to add a tag to the metadata.xml files. I would
however want to do it differently. I'd like to propose a general <doc>
tag with the usual attributes (version/deprange, language) and as new
attributes a "src" and a "kind" attribute. For your case it would then
be:
<doc xml:lang="en_EN" src="/proj/en/audio/xine-maint.xml"
kind="maintainerguide"/>
This way other gentoo (and other) documentation could be linked to the
package.
Paul
ps. We might even link to external (upstream) documentation, and have
packages.gentoo.org provide that info.
--
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2005-11-28 10:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 0:01 [gentoo-dev] Maintainer's guides? Diego 'Flameeyes' Pettenò
2005-11-24 11:31 ` Diego 'Flameeyes' Pettenò
2005-11-24 13:51 ` Grant Goodyear
2005-11-24 14:08 ` Diego 'Flameeyes' Pettenò
2005-11-24 19:50 ` Ciaran McCreesh
2005-11-24 19:58 ` Diego 'Flameeyes' Pettenò
2005-11-24 20:25 ` Ciaran McCreesh
2005-11-24 20:38 ` Diego 'Flameeyes' Pettenò
2005-11-24 20:47 ` Grobian
2005-11-27 17:43 ` Diego 'Flameeyes' Pettenò
2005-11-27 19:27 ` Donnie Berkholz
2005-11-27 19:59 ` Diego 'Flameeyes' Pettenò
2005-11-28 10:39 ` Paul de Vrieze [this message]
2005-11-28 10:55 ` Diego 'Flameeyes' Pettenò
2005-11-28 11:20 ` Paul de Vrieze
2005-11-28 11:28 ` Diego 'Flameeyes' Pettenò
2005-11-28 15:47 ` Jan Kundrát
2005-11-28 16:01 ` Diego 'Flameeyes' Pettenò
2005-11-28 20:01 ` Curtis Napier
2005-11-28 22:10 ` Jan Kundrát
2005-11-30 14:33 ` Diego 'Flameeyes' Pettenò
2005-12-18 11:51 ` pclouds
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=200511281139.16339.pauldv@gentoo.org \
--to=pauldv@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