public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: RFC: Project proposal -- maintainer-wanted
Date: Wed, 20 May 2009 02:42:19 +0300	[thread overview]
Message-ID: <1242776539.30374.23.camel@localhost> (raw)
In-Reply-To: <20090517120849.3115ce38@halo.dirtyepic.sk.ca>

[-- Attachment #1: Type: text/plain, Size: 2700 bytes --]

On Sun, 2009-05-17 at 12:08 -0600, Ryan Hill wrote:
> On Thu, 14 May 2009 03:32:12 +0300
> Mart Raudsepp <leio@gentoo.org> wrote:
> 
> > Project maintainer-wanted
> > =========================
> > 
> > Abstract:
> > There are currently quite some package requests (over 3000) languishing
> > on bugzilla waiting for a developer or team to get interested and
> > package it in the official gentoo-x86 portage tree. However in quite
> > some cases that might not happen for quite a while even with very
> > popular packages desired by users. The purpose of the maintainer-wanted
> > project is to get as many of such packages to the official tree as
> > possible as a stopgap solution.
> 
> Actually, I'm working on a "get the crap out of the tree" project that is
> pretty much the exact opposite of this. ;)

I don't think it opposes it much, maybe only 2-5% of maintainer-needed
packages.
Popular packages aren't crap. Their packaging ease might be, but
obviously people want to use those if they are popular, hence we can't
dub them really "crap".
We could say those packages are "crap" that get building bugs filed by
tinderbox runs from Patrick, Diego and other such people, while no-one
else has cared. The maintainer-wanted project would not be interested in
any such packages. Those are obviously dead applications/libraries that
are in no way popular and very beneficial to carry in the official tree.

> But, things I like:
> 
> - metrics for package popularity (can we do gentoo-stats already?)

Yeah, that'd be cool. Some other metrics ideas I brought out that can be
used for this projects purposes while there is no gentoo-stats.

> - encouraging teams and maintainers to take an interest in unmaintained
>   packages

It being a project/team making it more likely it doesn't degrade over
time when there is no dedicated team maintaining this. Maybe we could
make it so that when a package maintained by someone specific
(individual or team) that was taken over from maintainer-wanted would
drop back to maintainer-wanted team instead of maintainer-needed herd,
as the latter currently has technically no members.

> - keeping track of maintainer-wanted/needed packages through categorization,
>   etc.
> - proxy-maintainers
> 
> These things I think would benefit both projects, as well as several others.
> 
> I would actually rather see our overall package count dropping than growing,
> but if we're adding quality, maintained stuff and tossing out the garbage then
> I guess that's an improvement too.

Indeed.

-- 
Mart Raudsepp
Gentoo Developer
Mail: leio@gentoo.org
Weblog: http://planet.gentoo.org/developers/leio

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-05-19 23:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-14  0:32 [gentoo-dev] RFC: Project proposal -- maintainer-wanted Mart Raudsepp
2009-05-14  1:24 ` Gokdeniz Karadag
2009-05-14  1:27 ` AllenJB
2009-05-14 14:44   ` Richard Freeman
2009-05-15  7:43     ` Thilo Bangert
2009-05-15 10:04       ` Marijn Schouten (hkBst)
2009-05-15 10:44         ` Daniel Pielmeier
2009-05-15 12:24           ` [gentoo-dev] " Duncan
2009-05-19 23:24             ` Mart Raudsepp
2009-05-15 10:25       ` [gentoo-dev] " Richard Freeman
2009-05-19 23:51         ` Mart Raudsepp
2009-05-20  0:55           ` [gentoo-dev] " Duncan
2009-06-01 23:17             ` Mart Raudsepp
2009-05-14  1:47 ` [gentoo-dev] " Jeremy Olexa
2009-05-14  5:41   ` [gentoo-dev] " Duncan
2009-05-14  5:54     ` Patrick Lauer
2009-05-14 12:49       ` Alexander Færøy
2009-05-14 14:13         ` Nirbheek Chauhan
2009-05-14  9:09   ` Christian Faulhammer
2009-05-14 10:12   ` [gentoo-dev] " Mart Raudsepp
2009-05-14 17:06     ` Thomas Sachau
2009-05-14  6:53 ` Pacho Ramos
2009-05-14 11:02 ` Markos Chandras
2009-05-14 14:23   ` Mart Raudsepp
2009-05-14 14:50     ` Richard Freeman
2009-05-19 23:54       ` Mart Raudsepp
2009-05-20 15:36         ` Richard Freeman
2009-06-01 21:19           ` Mart Raudsepp
2009-05-14 18:24 ` Roy Bamford
2009-05-14 18:48   ` Thomas Sachau
2009-05-17  9:00     ` Tobias Scherbaum
2009-05-19 23:35   ` Mart Raudsepp
2009-05-17 18:08 ` [gentoo-dev] " Ryan Hill
2009-05-19 23:42   ` Mart Raudsepp [this message]
2009-05-28  7:55 ` [gentoo-dev] " Peter Volkov
2009-06-01 21:24   ` Mart Raudsepp

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=1242776539.30374.23.camel@localhost \
    --to=leio@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