public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Evan Read <eread@freeshell.org>
To: Jeremiah Mahler <jmahler@pacbell.net>
Cc: gentoo-dev@gentoo.org, mpickers@optusnet.com.au
Subject: Re: [gentoo-dev] State of Developement
Date: Tue, 27 Aug 2002 01:38:14 +0000	[thread overview]
Message-ID: <20020827013814.GA13465@SDF.LONESTAR.ORG> (raw)
In-Reply-To: <20020826180102.GA7111@jackpot.localdomain>

On Mon, Aug 26, 2002 at 11:01:02AM -0700, Jeremiah Mahler wrote:

> > re: where to focus on, thats not my domain, however documentation is ALWAYS 
> > appreciated (developers hate documenting things ;).  As for the new ebuilds, 
> > you can submit them to bugzilla, just dont expect them to be added to the 
> > system before 1.4 is released.
> > 
> Q: Can I help, can I help
> A: Sure, you can take out the trash and scrub the toilets.

And what the problem? If you don't like the way the developers dish out 
duties on their OS, don't use it. Developing ebuilds that might make a 
release that isn't coming out in the next month sounds generous to me.

 
> > > 	I havent checked, but is gentoo-core still closed?
> > yes, it is.
> > 
> Ivory tower?

Their prerogative.

> As a user of Gentoo, I feel like a child whose parent has to double
> check everything I do. And in the same way that the child 
> becomes frustrated with their parent because they place no trust
> in the child, I am frustrated with Gentoo because it places no
> trust in the users.

Maybe you should maintain a large collection of ebuilds outside of their 
tree or maybe maintain your own stable branch of Gentoo to _build_ the 
trust instead complaining that you can be trusted with no proof (I assume 
what you have written here is all you have communicated to the 
developers).
 
> Among all the distributions I am familiar with, Gentoo is,
> in my opinion, the best as far as placing trust in it's users.
> But Gentoo is also, in my opinion, far from what I imagine as ideal.
> 

So they don't trust you, and they trust you? As far as I am concerned, 
until you have CVS commit access, they don't trust you.  But that is ok.  
Because I implicitly trust them.  Well, I am not sure I do, hence Gentoo 
runs in VMWare for me).  I want them to save me from myself. gentoo-core 
can't break!


At the end of the day, it is their project.  They ask you to submit bug 
reports (with patches if you like) and to test. To do all the things a 
developer does.  They just tell you they would like to look at the quality 
of your submissions before they are commited.

Why aren't you thanking God that is the case? You should be afraid to ask 
for commit access on a source tree (which I assume gentoo-core would 
imply).

Read this: 
http://www.onlamp.com/pub/a/bsd/2002/01/31/Big_Scary_Daemons.html


Thanks.

-- 
Evan Read
http://eread.freeshell.org

"The future comes 60 minutes an hour no matter who you are or what you 
do." 
	The Screwtape Letters - C.S. Lewis


      parent reply	other threads:[~2002-08-27  1:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-26  6:43 [gentoo-dev] State of Developement Paul
2002-08-26  7:21 ` Henti Smith
2002-08-26 10:52 ` Preston A. Elder
2002-08-26 18:01   ` Jeremiah Mahler
2002-08-26 19:28     ` Grant Goodyear
2002-08-26 21:38       ` Dominik Westner
2002-08-26 22:24       ` George Shapovalov
2002-08-27  0:56         ` Daniel Mettler
2002-08-27  3:45           ` George Shapovalov
2002-08-27 14:35             ` [gentoo-dev] 1.4beta compliment, complaint, question, suggestion Fuper
2002-08-27 15:20               ` mike
2002-08-27 20:26               ` Karl Trygve Kalleberg
2002-08-27  2:12         ` [gentoo-dev] State of Developement Evan Read
2002-08-27  1:38     ` Evan Read [this message]

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=20020827013814.GA13465@SDF.LONESTAR.ORG \
    --to=eread@freeshell.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=jmahler@pacbell.net \
    --cc=mpickers@optusnet.com.au \
    /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