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] RFC: Project proposal -- maintainer-wanted
Date: Wed, 20 May 2009 02:35:44 +0300	[thread overview]
Message-ID: <1242776144.30374.15.camel@localhost> (raw)
In-Reply-To: <1242325462.4014.0@NeddySeagoon>

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

On Thu, 2009-05-14 at 19:24 +0100, Roy Bamford wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 2009.05.14 01:32, Mart Raudsepp wrote:
> > Hello,
> > 
> [snip]
> 
> > 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.
> > 
> [snip]
> > 
> > Discuss! :)
> > 
> > Mart Raudsepp
> > Gentoo Developer
> > Mail: leio@gentoo.org
> > Weblog: http://planet.gentoo.org/developers/leio
> > 
> 
> Mart, 
> 
> I'm against for many of the reasons AllanJB outlined. There is no point 
> in adding more unmaintained packages to the tree. Over time, the 
> average quality of the tree will suffer.

I have not proposed adding unmaintained packages to the tree. I have
proposed adding packages to the tree that are maintained. The
maintainer-wanted team maintains them actively until a specific team is
interested in taking over.
Based on other replies to the thread, it seems no-one believes that a
special team could add only so many packages that they are capable of
maintaining in good quality.
Also it has been brought up many times that if there is a popular
package not yet in the tree, there will be someone to add and maintain
it. But that doesn't seem to be the case when looking at existing
maintainer-wanted bugs. Also by having a team for this, the whole team
is accountable. If a maintainer-wanted ebuild is added by this team, it
is done as a team - if the person in the team most interested in it is
busy otherwise, the team will still take care of its bugs and quality
and bumps.

> We could use user contributed ebuilds attached to bugs as a way to 
> bring Sunrise to the contributors attention just by posting a comment 
> to the bug. If the contributor follows up, we get another user 
> maintained ebuild in Sunrise, which is good, as the current developers 
> don't have to do all the work. We already know some Sunrise 
> contributors become developers so perhaps we can use this as a way to 
> attract more contributors (both users and developers).

Meanwhile there is no-one to add packages that are wanted by many users
to the official tree. This project is meant as a remedy for that. The
proposal also lists various ways for actually finding out what packages
are the ones most beneficial to have in the official tree - as opposed
to unknown quality attachment in bugzilla, sunrise overlay, other
overlays or requests in bug entries without an attached ebuild - as to
be able to inflict as much good for the distribution as possible, given
the teams current capacity.


-- 
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 --]

  parent reply	other threads:[~2009-05-19 23:35 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 [this message]
2009-05-17 18:08 ` [gentoo-dev] " Ryan Hill
2009-05-19 23:42   ` Mart Raudsepp
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=1242776144.30374.15.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