public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stefan Schweizer <genstef@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: packages going into the tree with non-gentoo maintainers
Date: Sun, 03 Sep 2006 13:57:10 +0200	[thread overview]
Message-ID: <edeg01$4a2$1@sea.gmane.org> (raw)
In-Reply-To: 20060903112049.29f5026e@c1358217.kevquinn.com

Kevin F. Quinn wrote:
> I don't think it's a good idea for devs to be putting stuff into the
> tree without taking responsibility for it.  
sure I can put myself in there but it will help no one because I cannot test
the thing. Furthermore I am actually part of maintainer-needed and commit
fixes there. I am also on the maintainer-needed email alias.

Also maintainer-needed makes obvious to everyone that they do not have to
ask me to fix sth. or take over the package -> less communication overhead.

> I would expect that either 
> the herd is set appropriately (which means either the committer be a
> member of the herd, or the herd explicitly agree to be proxy), 
which is the case here.

> or the 
> committer be listed as a maintainer email address along with whoever is
> being proxied.  
the committer in this case has no interest in maintaining the thing. And for
proxying it does not matter who is proxying.

> Further I believe bugs against such packages should be 
> assigned to the @gentoo.org address (proxy maintainer if there is one,
> herd otherwise), and CC'ed to the proxied maintainer address.

this does not allow the actual maintainer to close the bug and causes a lot
of bugspam for a person who does not care about it and should be only
contacted in the end to commit fixes/patches/bumps.

Regards,
Stefan

-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-09-03 12:01 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-03  9:20 [gentoo-dev] packages going into the tree with non-gentoo maintainers Kevin F. Quinn
2006-09-03 10:12 ` Carsten Lohrke
2006-09-03 11:57 ` Stefan Schweizer [this message]
2006-09-03 12:51   ` [gentoo-dev] " Bryan Ãstergaard
2006-09-03 14:36     ` [gentoo-dev] " Stefan Schweizer
2006-09-06 23:35       ` Andrej Kacian
2006-09-07  2:09       ` Carsten Lohrke
2006-09-07  2:37         ` Stephen P. Becker
2006-09-07  3:10           ` Brian Harring
2006-09-07 11:29             ` Stephen P. Becker
2006-09-07 11:48               ` Jakub Moc
2006-09-07 13:25                 ` Carsten Lohrke
2006-09-07 14:42                   ` Simon Stelling
2006-09-07 14:51                     ` Jakub Moc
2006-09-07 15:07                       ` Simon Stelling
2006-09-07 15:22                       ` Carsten Lohrke
2006-09-07 15:16                     ` Kevin F. Quinn
     [not found]                     ` <200609071726.54054.carlo@gentoo.org>
2006-09-07 15:37                       ` Jakub Moc
2006-09-07  3:13         ` Alec Warner
2006-09-07 11:09           ` Simon Stelling
2006-09-07  3:22         ` Luca Barbato
2006-09-07  5:58           ` [gentoo-dev] " Stefan Schweizer
2006-09-07 11:08             ` Carsten Lohrke
2006-09-07  9:11         ` [gentoo-dev] " Stuart Herbert
2006-09-07 10:17           ` Danny van Dyk
2006-09-07 10:21             ` Jon Portnoy
2006-09-07 11:05           ` Carsten Lohrke
2006-09-07 11:25         ` Diego 'Flameeyes' Pettenò
2006-09-07 13:26           ` Carsten Lohrke
2006-09-03 13:20   ` [gentoo-dev] " Kevin F. Quinn
2006-09-03 14:11     ` [gentoo-dev] " Stefan Schweizer
2006-09-03 13:55   ` [gentoo-dev] " Paul de Vrieze
2006-09-03 14:22     ` [gentoo-dev] " Stefan Schweizer
2006-09-03 18:46       ` Kevin F. Quinn
2006-09-03 23:54         ` [gentoo-dev] " Ryan Hill
2006-09-04  7:20           ` Kevin F. Quinn
2006-09-07  3:10       ` [gentoo-dev] " Mike Frysinger
2006-09-07  3:02 ` [gentoo-dev] " Mike Frysinger

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='edeg01$4a2$1@sea.gmane.org' \
    --to=genstef@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