public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dylan Carlson <absinthe@gentoo.org>
To: "Todd Wright" <wylie@geekasylum.org>, <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Is there a process for marking ebuilds stable?
Date: Tue, 15 Apr 2003 01:41:37 -0400	[thread overview]
Message-ID: <200304150141.37543.absinthe@gentoo.org> (raw)
In-Reply-To: <001001c302f3$e4c9ba40$fc911ecb@geekasylum.org>

On Monday 14 April 2003 10:08 pm, Todd Wright wrote:
>  I had a lot of trouble getting the dev team to place my unmodified
> hercules-2.17.1 ebuild in the portage tree, despite the fact that I am
> involved with the hercules development team. The gentoo developers seem
> to have a 'we know better than you' attitude.

That's a bit presumptuous, and offhand rude...

Ultimately the the Gentoo developer who commits the ebuild is responsible 
for the ebuild, not you.  Towards this, we appreciate ebuild submissions 
from users and outside developers, however: every ebuild has to go through 
a minimal QA process.  

We're not going to immediately commit an ebuild because someone tells us 
that they're associated with the dev team of that particular package.  It 
has to be tested just like everything else.  

If you're not happy with that, you have options:  

(x) you can host the ebuild on your website, and point interested parties 
to it until we test it and put it in the tree...

(y) you can switch to another distribution which I can almost guarantee 
will move slower than we do...

(z) you can wait patiently while we do the best we can to satisfy all of 
these requests and maintaining quality control.  

Remember, this is open source development.   You need to check your 
expectations a little.  The world doesn't move just because you snap your 
fingers and demand that it does.  

Cheers,
Dylan Carlson

Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F
Key fingerprint = 3AEA DE38 FE42 15A6 C0E2 730E 3D04 BCC1 708E 165F

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-04-15  5:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15  2:08 [gentoo-dev] Is there a process for marking ebuilds stable? Todd Wright
2003-04-15  2:30 ` Jon Portnoy
2003-04-15  5:41 ` Dylan Carlson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-13 22:25 Brad Laue
2003-04-13 23:00 ` Rainer Groesslinger
2003-04-13 23:07   ` Rainer Groesslinger
2003-04-13 23:07   ` Jon Portnoy
2003-04-14  9:31     ` Rainer Groesslinger
2003-04-14  7:32   ` Fredrik Jagenheim
2003-04-14  9:00     ` Michael Kohl
2003-04-14 11:04       ` Fredrik Jagenheim
2003-04-14 16:29         ` Mikael Andersson
2003-04-14 20:31           ` Alec Berryman
2003-04-14 21:48             ` Brad Laue
2003-04-14 21:58               ` Alec Berryman
2003-04-15 11:07                 ` Mikael Andersson
2003-04-14 22:03           ` Brad Laue
2003-04-14 15:07     ` Brad Laue
2003-04-14 19:39       ` C. Brewer
2003-04-15  6:21         ` Abhishek Amit
2003-04-15  9:09           ` Fredrik Jagenheim
2003-04-16  0:34           ` C. Brewer
2003-04-15 13:53         ` Brad Laue

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=200304150141.37543.absinthe@gentoo.org \
    --to=absinthe@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=wylie@geekasylum.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