From: Michael Kohl <citizen428@cargal.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] proposal: make gentoo-core publicly read-only
Date: Sat, 28 Jun 2003 10:26:02 +0800 [thread overview]
Message-ID: <20030628102602.4120bb6b.citizen428@cargal.org> (raw)
In-Reply-To: <87r85fba2o.fsf@killr.ath.cx>
[-- Attachment #1: Type: text/plain, Size: 1939 bytes --]
On Fri, 27 Jun 2003 14:21:35 -0500
Matthew Kennedy <mkennedy@gentoo.org> wrote:
> I personally feel that it may be a good time to reconsider making
> gentoo-core a publicly read-only list. Several users I know (some
> personally) are irate that we appear to be a "behind-closed-doors"
> project. Yes, this stems from the recent fork announcement.
Actually I somehow doubt that most of the people who cry really loud at
the moment would even bother to read -core if it was made read-only.
> I hope that we can open -core as a publicly read-only list to involve
> our community more. We owe this much to our user-base in my opinion.
> For these reasons, I have CC'd this to -dev.
Up until now I've always been in favor of making -core world readable.
But after the proposal of the new managment structure I think that
publicly available summaries of the last week (which the project leaders
have to do as far as my understanding goes) are enough (considered they
are not to briefly), as they give us users willing to help an indication
what is going on, what already has been discussed, why it has (not) been
dismissed etc., while still assuring devs have the privacy they
sometimes need.
Also I think that a read-only -core will increase the noise ratio on
-dev again, as some people may want to immediately react when a
proposal is made they don't like, and I'll bet that -dev will be the
place where this mails go. So I suspect we'll end up with a number of
postings to -dev which would have never been necessary because the dev
team votes against this proposal in the end. This kind of situation can
be avoided by a weekly status update.
So personally, I _really_ want to know _some of the things_ discussed
on -core, but I'm not really assured that a publicly available -core is
the best solution.
Michael
--
www.cargal.org
GnuPG-key-ID: 0x90CA09E3
Jabber-ID: citizen428 [at] cargal [dot] org
Registered Linux User #278726
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-06-28 2:30 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
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 [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=20030628102602.4120bb6b.citizen428@cargal.org \
--to=citizen428@cargal.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