From: Richard Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] metdata.dtd should require <herd/>
Date: Thu, 24 Dec 2009 07:37:26 -0500 [thread overview]
Message-ID: <4B336086.2000108@gentoo.org> (raw)
In-Reply-To: <55e0be1b0912231036q533f43ccx2425383804da561@mail.gmail.com>
On 12/23/2009 01:36 PM, Paul de Vrieze wrote:
>
> Perhaps we should create a schema to validate the file. XMLSchema (or
> any of the other standards) allows for much more flexibility in
> specifying these things. Btw. I did not design the metadata DTD for
> order to be significant. The only priority is that maintainer goes
> before herd, that's all.
>
I think we should definitely have some way of designating which should
be the contact for bugs. I've had some bugs sit around for a while
without being noticed because they were assigned to the herd the package
is in, and not to me personally, and I don't generally work with that
herd, and the project associated with the herd doesn't generally
maintain the package.
I'm sure there are many cases where a similar situation exists.
Another way to handle this is at least CC EVERYBODY in the metadata in
new bugs, and not assume that copying the project will get all the
maintainers.
next prev parent reply other threads:[~2009-12-24 14:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 11:56 [gentoo-dev] irregular metdata.xml check Thilo Bangert
2009-12-07 12:13 ` Ulrich Mueller
2009-12-07 13:20 ` Thilo Bangert
2009-12-07 17:04 ` Hans de Graaff
2009-12-07 20:20 ` Thilo Bangert
2009-12-15 15:19 ` [gentoo-dev] metdata.dtd should require <herd/> Peter Volkov
2009-12-15 17:16 ` Alex Alexander
2009-12-15 17:27 ` Mike Frysinger
2009-12-15 17:48 ` [gentoo-dev] " Jonathan Callen
2009-12-16 6:49 ` [gentoo-dev] " Rémi Cardona
2009-12-23 18:36 ` Paul de Vrieze
2009-12-24 12:37 ` Richard Freeman [this message]
2009-12-24 16:12 ` Jeroen Roovers
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=4B336086.2000108@gentoo.org \
--to=rich0@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