public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: John Nilsson <john@milsson.nu>
To: stuart@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP 26 -- Handling kernels with portage
Date: Tue, 04 May 2004 00:48:37 +0200	[thread overview]
Message-ID: <1083624517.19211.29.camel@newkid.milsson.nu> (raw)
In-Reply-To: <200405031736.38770.stuart@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2591 bytes --]

Would anyone be interested in improving the GLEP process?
Some thoughts:

A GLEP should have three parts

1. A case for the problem.
	This document will discuss the problem.
	* Is there a problem?
	* What is the nature of the problem?
	* Who is affected by the problem?
	* Should the problem be solved?

2. Solution requirement analysis.
	This document will declare the requirements that a proposed 	solution
will be tested against.

3. Solution
	A document describing the solution.

Each document should be accepted before the next part is worked on. A
document MUST have a version history. A solution(3) MUST link to a
particular version of the SRA(2) which MUST link to a particular version
of problem(1).

I also suggest a wiki-like development model for documents.

-John

On Mon, 2004-05-03 at 18:36, Stuart Herbert wrote:
> On Monday 03 May 2004 16:15, Nathaniel McCallum wrote:
> > However, its just a Proposal.  And if devs get this 
> > much negative "your idea can't work" criticism from a simple GLEP, how
> > do you think a Gentoo user would ever feel comfortable filing a GLEP
> > (which is what they were intended for!).
> 
> I think any submitted proposal needs to be able to stand up to rigorous 
> technical scrutiny.  If the idea has merit, or a groundswell of support, then 
> the proposal will be the better for it.  If the idea is weak, flawed, or 
> substantially incomplete - it's important we catch these things now before 
> it's our users catching the results ;-)
> 
> A commonly-taught method of evaluating any proposal is de Bono's hats - where 
> you look at a proposal from a specific viewpoint.  Look it up, and you'll see 
> where I'm coming from.
> 
> > In the same way as not bashing a user for contributing an ebuild
> > (remember, they could be a future contributer to Gentoo), we should,
> > when faced with a GLEP, stop and think if there is anything posative
> > about it, then try to come up with working scenarios.  Remember, devs
> > are contributers to Gentoo.
> 
> Yes they are.  And you're right - anyone should be able to put forward a GLEP 
> without fear.
> 
> > Thats also fine with me.  I don't want the GLEP approved right away, I
> > just wanted it to be a sounding board for discussion to develop a good
> > prototype.  Isn't that what a GLEP is for?
> 
> Maybe it would help if that discussion happened first, and the results were 
> written up into a GLEP for approval.  That's happened in the past, and seems 
> a successful model to reproduce.
> 
> Best regards,
> Stu

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-05-03 22:47 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-03  2:04 [gentoo-dev] GLEP 26 -- Handling kernels with portage Nathaniel McCallum
2004-05-03  2:45 ` [gentoo-dev] Re: [gentoo-core] " Greg KH
2004-05-03  2:54   ` Nathaniel McCallum
2004-05-03  3:06     ` [gentoo-dev] " Greg KH
2004-05-03  3:18       ` [gentoo-dev] Re: [gentoo-core] " Nathaniel McCallum
2004-05-03  3:32         ` [gentoo-dev] " Greg KH
2004-05-03  3:39           ` [gentoo-dev] Re: [gentoo-core] " Nathaniel McCallum
2004-05-03 17:17             ` Greg KH
2004-05-03 17:36               ` Nathaniel McCallum
2004-05-06 11:31         ` Duncan
2004-05-06 12:22           ` John Nilsson
2004-05-03  2:56   ` [gentoo-dev] Re: [gentoo-core] " Nathaniel McCallum
2004-05-03  3:56 ` [gentoo-dev] " Greg KH
2004-05-03  4:29   ` [gentoo-dev] Re: [gentoo-core] " Nathaniel McCallum
2004-05-03  5:40     ` John Nilsson
2004-05-03  6:04       ` Nathaniel McCallum
2004-05-03 10:12         ` Stuart Herbert
2004-05-03 10:18           ` Todd Berman
2004-05-03 11:18             ` Stuart Herbert
2004-05-03 12:12               ` Patrick Börjesson
2004-05-03 14:51                 ` Andrew Gaffney
2004-05-03 15:20               ` Nathaniel McCallum
2004-05-03 15:16           ` Nathaniel McCallum
2004-05-03 16:22         ` Greg KH
2004-05-05 16:33           ` John Mylchreest
2004-05-05 16:43             ` Ciaran McCreesh
     [not found]   ` <20040502222039.45139edd@traam-ii>
2004-05-03 22:02     ` [gentoo-dev] " Greg KH
2004-05-03  8:57 ` [gentoo-dev] " Ciaran McCreesh
2004-05-03 14:46   ` [gentoo-dev] Re: [gentoo-core] " Nathaniel McCallum
2004-05-03 10:09 ` Stuart Herbert
2004-05-03 15:15   ` Nathaniel McCallum
2004-05-03 16:36     ` Stuart Herbert
2004-05-03 22:48       ` John Nilsson [this message]
2004-05-05  1:16         ` N. Owen Gunden
2004-05-05  1:42           ` John Nilsson

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=1083624517.19211.29.camel@newkid.milsson.nu \
    --to=john@milsson.nu \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=stuart@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