From: Todd Berman <tberman@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-core] proposal: make gentoo-core publicly read-only
Date: 27 Jun 2003 17:37:58 -0400 [thread overview]
Message-ID: <1056749877.9103.5.camel@phaze> (raw)
In-Reply-To: <1056746975.1164.31.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1650 bytes --]
On Fri, 2003-06-27 at 16:49, Alec Berryman wrote:
> Currently, -dev isn't a developer list; most of the e-mail is users'
> suggestions discussed by other users and the occasional dev, as well as
> the occasional mis-post targeted for -user. Perhaps in the future, if
> -core would be accessible to the community that drive it, -dev could be
> the buffer zone between the final work of the developers and the user
> community. Right now, there's a feeling that the developers are
> shutting themselves in an ivory tower. That's not good for community.
> Gentoo's social contract has always said it will not "hide its
> problems", but has continued to keep its core development decisions
> closed.
Just as a quick point of reference, I have been a gentoo developer for
~3 months or so, maybe a bit less. You want to know how I became a
gentoo developer?
It had nothing to do with finding the keys to the fabled tower, or
making the right friends, and had everything to do with being willing to
give a bit of my time and energy to serve something that is needed in
gentoo. All I did was make a couple small proposals here about some
general stuff, and then offer to maintain the sendmail ebuild. Thats it,
no hocus-pocus, no magic words, no secret rites, not even a special
handshake. (Man, did I feel gypped!)
My point is just this, you want access to -core, become a developer, its
part of the territory.
And I might be going out on a limb here, but I'm pretty sure that many
other non-profit Linux distributions have non-open lists. In fact, I
would be very surprised if any Linux distributions don't.
--Todd
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-27 21:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 19:21 [gentoo-dev] proposal: make gentoo-core publicly read-only Matthew Kennedy
2003-06-27 19:47 ` [gentoo-dev] Re: [gentoo-core] " Jon Portnoy
2003-06-27 20:49 ` Alec Berryman
2003-06-27 21:37 ` Todd Berman [this message]
2003-06-28 16:26 ` Daniel Armyr
2003-06-28 17:13 ` Martin Schlemmer
2003-06-28 18:35 ` [gentoo-dev] " Cyrik
2003-06-28 22:40 ` Martin Schlemmer
2003-06-29 13:12 ` Paul de Vrieze
2003-07-02 5:42 ` [gentoo-dev] Re: Public Relations, was: " Paul
2003-07-02 11:29 ` [gentoo-dev] Re: Public Relations Alastair Tse
2003-07-02 16:02 ` Daniel Armyr
2003-07-02 16:24 ` Aron Griffis
2003-07-02 11:35 ` [gentoo-dev] Re: Public Relations, was: Re: [gentoo-core] proposal: make gentoo-core publicly read-only Stewart Honsberger
2003-07-02 12:18 ` Alastair Tse
2003-07-02 13:45 ` Brian Jackson
2003-07-02 16:03 ` donnie berkholz
2003-06-29 23:27 ` [gentoo-dev] " Matthew Kennedy
2003-06-28 23:42 ` Stewart Honsberger
2003-06-29 23:25 ` Matthew Kennedy
2003-06-27 21:50 ` [gentoo-dev] " Stroller
2003-06-28 7:35 ` Paul de Vrieze
2003-06-28 11:19 ` Svyatogor
2003-06-28 16:02 ` Ned Ludd
2003-06-29 12:50 ` Paul de Vrieze
2003-06-28 2:26 ` Michael Kohl
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=1056749877.9103.5.camel@phaze \
--to=tberman@gentoo.org \
--cc=gentoo-dev@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