From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32339 invoked by uid 1002); 28 Jun 2003 02:30:07 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 15118 invoked from network); 28 Jun 2003 02:30:07 -0000 Date: Sat, 28 Jun 2003 10:26:02 +0800 From: Michael Kohl To: gentoo-dev@gentoo.org Message-Id: <20030628102602.4120bb6b.citizen428@cargal.org> In-Reply-To: <87r85fba2o.fsf@killr.ath.cx> References: <87r85fba2o.fsf@killr.ath.cx> X-Mailer: Sylpheed version 0.9.0claws (GTK+ 1.2.10; i686-pc-linux-gnu) X-Operating-System: Gentoo Linux Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="=.SzQEPP30Q)OqK6" Subject: Re: [gentoo-dev] proposal: make gentoo-core publicly read-only X-Archives-Salt: b41d5e54-03ab-4ae9-b7a9-c4d28dab762b X-Archives-Hash: e349c3b0c89f0386aa01506298aa9acf --=.SzQEPP30Q)OqK6 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Fri, 27 Jun 2003 14:21:35 -0500 Matthew Kennedy 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 --=.SzQEPP30Q)OqK6 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+/Py93i2RopDKCeMRAnyrAJ9hfg9Qf6nl31j4veBIHKlCIm34MQCggtZY A6R0nsAt9oZtsh7LSFuI4LA= =EGBy -----END PGP SIGNATURE----- --=.SzQEPP30Q)OqK6--