From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from parrot.gentoo.org (lists.gentoo.org [156.56.111.196]) by robin.gentoo.org (8.13.3/8.13.3) with ESMTP id j2BKwtM2031132 for ; Fri, 11 Mar 2005 20:58:56 GMT Received: (qmail 25008 invoked by uid 89); 11 Mar 2005 20:58:52 +0000 Received: (qmail 10717 invoked from network); 11 Mar 2005 20:58:52 +0000 Received: from smtp.gentoo.org (134.68.220.30) by lists.gentoo.org with AES256-SHA encrypted SMTP; 11 Mar 2005 20:58:52 +0000 Received: from 81-178-209-222.dsl.pipex.com ([81.178.209.222]) by smtp.gentoo.org with esmtpa (Exim 4.43) id 1D9rDh-0001cg-Kn for gentoo-dev@lists.gentoo.org; Fri, 11 Mar 2005 20:58:54 +0000 Message-ID: <42320696.7030404@gentoo.org> Date: Fri, 11 Mar 2005 20:59:02 +0000 From: Ian Leitch User-Agent: Mozilla Thunderbird 1.0 (X11/20050124) X-Accept-Language: en-us, en 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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] GLEP system worthwhile? References: <20050311143951.GA27199@dst.grantgoodyear.org> <4231BE29.2020408@gentoo.org> <20050311192526.GB30649@dst.grantgoodyear.org> In-Reply-To: <20050311192526.GB30649@dst.grantgoodyear.org> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 59c0270b-f7e3-48f2-92ab-f30070366801 X-Archives-Hash: 7ef48e18605a9cd3024299edc140f69a -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Grant Goodyear wrote: ~ > Really? It's usually just a matter of e-mailing me. I read through | it, and if I see that the GLEP fails to answer some questions that I | predict will arise, I will generally mention it to the GLEP author and | suggest that such issues be addressed, even it is just to add a | section labeled "open questions". Very occasionally I will mention to | an author that I don't think a GLEP is actually needed, and suggest | that the author just talk to the appropriate person and implement it. | I don't believe that I have ever outright refused a GLEP, or even added | more than a day to the time for it to be posted. For example, I first proposed the Planet idea long before GLEP 30 came along. Basically the idea got shot down on IRC because infra were worried about storing unmoderated material on Gentoo hardware. At that point it was pretty much a "no", so I didn't bother following it up with a GLEP. Moving forward 1 year, we have Planet Gentoo. How the hell did that happen then? Daniel persevered and produced a GLEP but which looked to be doing nothing (like most other GLEPS) until gentooexperimental.org came along setup a non official Planet. This made it obvious the idea was popular and the implementation of the GLEP soon followed, as did infra's concerns seem to disappear. If we'd had a voting system, the popularity of the GLEP would have been obvious from the start, and no doubt we would have had the Planet implemented _much_ sooner. In a nutshell, we need a system where ideas can be put forward so that they have maximum exposure AND accessibility to vote. Posting them to - -dev sure gets them a lot of exposure (though mostly only to devs), but the majority of people likely to respond are those not in favor. Having a simple voting system will allow people to put their voice forward with maximum ease. The thing I dislike about the current system is that most devs/users will never hear about an idea until it makes onto glep.g.o. GLEPs need to be put our there for everyone to see at an early stage so people can vote on the IDEA, not the specifics or the quality of the GLEP itself. | Most of these issues are moot, however, because in many cases GLEP | authors prefer to post an informal GLEP on -dev first, gather comments, | and then submit a formal GLEP after an initial revision. Having all those in a central place would be far better, I'm sure there are many GLEPs sitting in devspace that I or you have never seen. | It's worth noting that a GLEP author need not be a dev, so those | people, of course, would always require a surrogate to submit/revise | GLEPs. As for devs being able to upload/revise GLEPs, I'm not opposed. | The reason that devs cannot update their own GLEPs right now is purely | technical: the GLEP page is part of the www tree, and that tree has | fairly strict permissions. If opening up the GLEP directory isn't too | much of a pita for infra, I certainly won't oppose it. I would still | prefer that GLEPs be run by one of the editors before being posted, | since we may be able to help, but I wouldn't insist on it. I would be | very sad, though, if people took advantage of a more liberal policy to | post poorly-thought-out junk. If someone posts a poorly thought out GLEP then people will vote against it. If the author wishes, he/she can post a revised version and the voting process beings again. It's up to the author to make sure their idea is of decent quality first time round, unless they want to spend hours revising it. Regards, Ian Leitch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCMgaWefZ4eWAXRGIRAlq5AJ0abRJqZJBHsujCHgTGAqT56OZ+awCgjAAg 1sYVgg8bfD9xsKoI81VMPm4= =Wlfb -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list