public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: Re: packages going into the tree with non-gentoo maintainers
Date: Wed, 06 Sep 2006 23:13:12 -0400	[thread overview]
Message-ID: <44FF8E48.3030109@gentoo.org> (raw)
In-Reply-To: <200609070409.55884.carlo@gentoo.org>

Carsten Lohrke wrote:
> On Sunday 03 September 2006 16:36, Stefan Schweizer wrote:
>> I am not adding stuff. I am fixing existing packages. And I am taking
>> responsibility.
> 
> How wonderful this sort of "maintenance" is you can read here:
> 
> https://bugs.gentoo.org/show_bug.cgi?id=146626
> 
> Am I the only one who has a problem with this?
> 
> 
> Carsten

I would agree on principle, however this is NOT the correct venue for
this.  If you have an issue with another developer; you don't go
complain on a public ML; you TALK to the developer.  If you can't work
it out, you talk to your project lead.  If THEY can't work it out, you
talk to the ombudsman, and so forth.  Everyone knows the policy and yet
no one follows it.  I don't want to see this thread continue; you know
what you have to do.[1]

[1] http://www.gentoo.org/proj/en/devrel/policy.xml
-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-09-07  3:18 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 ` [gentoo-dev] " Stefan Schweizer
2006-09-03 12:51   ` 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 [this message]
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=44FF8E48.3030109@gentoo.org \
    --to=antarus@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