public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeroen Roovers <jer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in  dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
Date: Tue, 5 Apr 2011 06:26:09 +0200	[thread overview]
Message-ID: <20110405062609.3db9d48d@epia.jer-c2.orkz.net> (raw)
In-Reply-To: <4D8FABE5.4010006@necoro.eu>

On Sun, 27 Mar 2011 23:28:05 +0200
René 'Necoro' Neumann <lists@necoro.eu> 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.

(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



  reply	other threads:[~2011-04-05  4:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110326055210.E906D20054@flycatcher.gentoo.org>
2011-03-27  4:45 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml Jeremy Olexa
2011-03-27  7:47   ` Nirbheek Chauhan
2011-03-27 10:29     ` Markos Chandras
2011-03-27  9:39       ` Nirbheek Chauhan
2011-03-27 13:04         ` Treeclean all maintainer-needed packages, was: " Chí-Thanh Christopher Nguyễn
2011-03-27 15:37         ` Ryan Hill
2011-03-27 13:30     ` Jeremy Olexa
2011-03-27 13:43       ` Nirbheek Chauhan
2011-03-27 19:17         ` Alec Warner
2011-03-27 19:40           ` Nirbheek Chauhan
2011-03-27 20:17             ` Alec Warner
2011-03-27 21:25               ` Nirbheek Chauhan
2011-03-27 23:34                 ` Ryan Hill
2011-03-28  1:59                   ` Donnie Berkholz
2011-03-27 20:44             ` Rich Freeman
2011-03-27 21:09               ` Nirbheek Chauhan
2011-03-28  1:58                 ` Donnie Berkholz
2011-03-27 21:28               ` René 'Necoro' Neumann
2011-04-05  4:26                 ` Jeroen Roovers [this message]
2011-04-05 10:58                   ` Alec Warner
2011-04-05 15:08                     ` Jeroen Roovers
2011-04-18 17:56                   ` Andreas K. Huettel
2011-03-27 13:44       ` Rich Freeman
2011-03-27 14:54         ` Tomáš Chvátal
2011-03-27 16:18           ` Rich Freeman
2011-03-27 14:08       ` Maintainership offering; was: " René 'Necoro' Neumann
2011-03-27 19:05         ` Jeremy Olexa
2011-03-27 20:20       ` Proxy maintainership of app-misc/pwsafe, was " Christopher Head
2011-03-27 20:47         ` Nirbheek Chauhan
2011-03-27 20:55           ` René 'Necoro' Neumann
2011-03-27 20:55           ` David Abbott
2011-03-27 21:32             ` Nirbheek Chauhan
2011-03-29 17:50       ` Dirkjan Ochtman
2011-03-29 13:33     ` 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=20110405062609.3db9d48d@epia.jer-c2.orkz.net \
    --to=jer@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