Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Alec Warner <antarus@g.o>
Subject: Re: Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
Date: Tue, 5 Apr 2011 03:58:05 -0700
On Mon, Apr 4, 2011 at 9:26 PM, Jeroen Roovers <jer@g.o> wrote:
> On Sun, 27 Mar 2011 23:28:05 +0200
> René 'Necoro' Neumann <lists@...> wrote:
>
>> Am 27.03.2011 22:44, schrieb Rich Freeman:
>> Well, but you need some way of communicate that certain packages are
>> w/o a proper maintainer. Why else should someone step up? I, for
>> instance, was quite surprised about the list of m-n packages and
>> seeing that quite some packages I use are on that list. I would never
>> had a look at it without this thread (or are users nowadays supposed
>> to check metadata.xml on a regular basis?).
>
> I remember distinctly that I once publicly proposed to change
> <http://packages.gentoo.org/> to actually interpret packages'
> <metadata.xml> and displaying its formatted contents on every
> <http://packages.gentoo.org/package/CAT/PKG> page (notably because the
> site mentioned and still mentions the last committer at the top of the
> page, with his or her Gentoo e-mail alias/handle plainly visible, so at
> the time I envisioned it to prevent people from addressing the
> wrong developers). <metadata.xml> is a mere link on every page and
> doesn't invite anyone to dig deeper, when it could be put to better
> use. Our bugzilla database already has proper descriptions for every
> alias we use, so we could reuse that information to improve
> packages.g.o.


http://www.gentoo.org/proj/en/qa/treecleaners/maintainer-needed.xml

?

>
> (Only, I cannot now find any trace of such a discussion at all, or even
> the bug report I am quite certain I would have filed about this.)
>
>
>     jer
>
>


Replies:
Re: Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
-- Jeroen Roovers
References:
Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
-- Jeremy Olexa
Re: Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
-- Nirbheek Chauhan
Re: Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
-- Jeremy Olexa
Re: Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
-- Nirbheek Chauhan
Re: Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
-- Alec Warner
Re: Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
-- Nirbheek Chauhan
Re: Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
-- Rich Freeman
Re: Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
-- René 'Necoro' Neumann
Re: Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
-- Jeroen Roovers
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
Next by thread:
Re: Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
Previous by date:
Re: Re: python-namespaces.eclass
Next by date:
Re: Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.