From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.3/8.13.3) with ESMTP id j2BIZl7k002475 for ; Fri, 11 Mar 2005 18:35:48 GMT Received: from smtp.nuvox.net ([64.89.70.9] helo=smtp03.gnvlscdb.sys.nuvox.net) by smtp.gentoo.org with esmtp (Exim 4.43) id 1D9ozC-0006LN-9f for gentoo-dev@robin.gentoo.org; Fri, 11 Mar 2005 18:35:46 +0000 Received: from cgianelloni.nuvox.net (216.215.202.4.nw.nuvox.net [216.215.202.4]) by smtp03.gnvlscdb.sys.nuvox.net (8.12.11/8.12.11) with SMTP id j2BIZU8R032300 for ; Fri, 11 Mar 2005 13:35:30 -0500 Received: by cgianelloni.nuvox.net (sSMTP sendmail emulation); Fri, 11 Mar 2005 13:39:45 -0500 Subject: Re: [gentoo-dev] GLEP system worthwhile? From: Chris Gianelloni To: gentoo-dev@robin.gentoo.org In-Reply-To: <4231D807.6030805@gentoo.org> References: <20050311143951.GA27199@dst.grantgoodyear.org> <4231BE29.2020408@gentoo.org> <20050311155822.3c0e1ddf@snowdrop> <4231C2D5.7000705@gentoo.org> <1110560759.21812.113.camel@cgianelloni.nuvox.net> <4231D807.6030805@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-WO4/kMd/7euIh7Y4odpp" Organization: Gentoo Linux Date: Fri, 11 Mar 2005 13:39:44 -0500 Message-Id: <1110566384.21812.119.camel@cgianelloni.nuvox.net> Precedence: bulk List-Post: , , List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-To: gentoo-dev@gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 X-Archives-Salt: 4e6f2004-cb5d-4e56-9c6c-9783050ae241 X-Archives-Hash: f1b9d96733252b0d0f997673ef32aa78 --=-WO4/kMd/7euIh7Y4odpp Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2005-03-11 at 17:40 +0000, Ian Leitch wrote: > Yes, but: >=20 > 1) The revision has to go through one of 2 GLEP editors, what's wrong > with letting a dev do this themselves. I agree with genone on letting > devs have CVS access. Pkus it's not obvious on the GLEP main page which > GLEPs have been updated and require votes. I could agree with this only if there were something in place that keeps a new GLEP from being posted until it meets the proper layout. I don't want to see completely worthless entries that are still a work in progress. I would like it to at least be somewhat complete before I spend time looking through them. I'm thinking something like a barrier to entry, but not for editing. Give the GLEP authors and a group of people accepted by the author access to edit the GLEP. > 2) Voting is done on -dev, I can't think of a worse place to conduct a > vote. We need a web interface to count and clearly display votes for > each revision. I agree with you here. Voting over a mailing list just isn't very efficient. Perhaps a login-restricted web page? How about an app on toucan? "vote glep19 yes" or something equally as insane... --=20 Chris Gianelloni Release Engineering - Strategic Lead/QA Manager Games - Developer Gentoo Linux --=-WO4/kMd/7euIh7Y4odpp Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQBCMeXwkT4lNIS36YERAgroAKCfzugKqt8cVluk/tsjjB3mDnnbhwCbBvnE FZCWPeOJeg0RpIpmsSa9lAw= =gy2a -----END PGP SIGNATURE----- --=-WO4/kMd/7euIh7Y4odpp-- -- gentoo-dev@gentoo.org mailing list