Gentoo Archives: gentoo-dev

From: Alec Warner <antarus@g.o>
To: gentoo-dev@l.g.o
Cc: Jeroen Roovers <jer@g.o>
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
Date: Tue, 05 Apr 2011 10:58:55
Message-Id: BANLkTimhJur3r3D+tmzB8-ayLJoasetarg@mail.gmail.com
In Reply to: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml by Jeroen Roovers
1 On Mon, Apr 4, 2011 at 9:26 PM, Jeroen Roovers <jer@g.o> wrote:
2 > On Sun, 27 Mar 2011 23:28:05 +0200
3 > René 'Necoro' Neumann <lists@××××××.eu> wrote:
4 >
5 >> Am 27.03.2011 22:44, schrieb Rich Freeman:
6 >> Well, but you need some way of communicate that certain packages are
7 >> w/o a proper maintainer. Why else should someone step up? I, for
8 >> instance, was quite surprised about the list of m-n packages and
9 >> seeing that quite some packages I use are on that list. I would never
10 >> had a look at it without this thread (or are users nowadays supposed
11 >> to check metadata.xml on a regular basis?).
12 >
13 > I remember distinctly that I once publicly proposed to change
14 > <http://packages.gentoo.org/> to actually interpret packages'
15 > <metadata.xml> and displaying its formatted contents on every
16 > <http://packages.gentoo.org/package/CAT/PKG> page (notably because the
17 > site mentioned and still mentions the last committer at the top of the
18 > page, with his or her Gentoo e-mail alias/handle plainly visible, so at
19 > the time I envisioned it to prevent people from addressing the
20 > wrong developers). <metadata.xml> is a mere link on every page and
21 > doesn't invite anyone to dig deeper, when it could be put to better
22 > use. Our bugzilla database already has proper descriptions for every
23 > alias we use, so we could reuse that information to improve
24 > packages.g.o.
25
26
27 http://www.gentoo.org/proj/en/qa/treecleaners/maintainer-needed.xml
28
29 ?
30
31 >
32 > (Only, I cannot now find any trace of such a discussion at all, or even
33 > the bug report I am quite certain I would have filed about this.)
34 >
35 >
36 >     jer
37 >
38 >

Replies