1 |
On Wed, 2006-10-25 at 13:17 +0100, Stuart Herbert wrote: |
2 |
> On 10/25/06, Chris Gianelloni <wolf31o2@g.o> wrote: |
3 |
> > Also, I'd like to know what you would propose we do if we were to follow |
4 |
> > something like this. Would we post something like GLEP 39a, as an |
5 |
> > amendment to GLEP 39, or would we have to rewrite the whole thing, with |
6 |
> > just the one change, to supersede? |
7 |
> > |
8 |
> > Perhaps we need an amendment to GLEP 1 to allow explictly-stated |
9 |
> > amendments? |
10 |
> |
11 |
> I think it'd be common sense to post -r1, -r2 etc, and extend the XML |
12 |
> syntax so that we could easily indicate which sentences had been |
13 |
> changed. I think it'll make things easier than a |
14 |
> read-GLEP-39-now-read-GLEPs-39a-to-39z type of approach. |
15 |
> |
16 |
> We could also have a 'Revisions' section somewhere (if we don't have |
17 |
> one already) in the GLEP listing the date, a link to the Council |
18 |
> meeting logs approving the change, and a (very) brief summary of the |
19 |
> change. |
20 |
> |
21 |
> I'm sure there are other ways we could do this that would also be practical. |
22 |
|
23 |
I think the likely best way would be to do something like: |
24 |
|
25 |
All new projects must first be proposed as an RFC to the gentoo-dev |
26 |
mailing list with a list of goals, project plan, and a list of resources |
27 |
required[1]. |
28 |
|
29 |
Then there would be an "Amendments" section, which would contain |
30 |
something like: |
31 |
|
32 |
1. This was added by vote of the Gentoo Council on 2006/10/19 to |
33 |
improve communications between developers. |
34 |
|
35 |
We could then include a link to the meeting summary, too, or a link to |
36 |
the mailing list thread or whatever, that caused the change. |
37 |
|
38 |
This should satisfy everyone, as changes are noted from the original, |
39 |
yet there's still just the one authoritative place to look for the |
40 |
information. |
41 |
|
42 |
How does this work for you? |
43 |
|
44 |
-- |
45 |
Chris Gianelloni |
46 |
Release Engineering Strategic Lead |
47 |
Alpha/AMD64/x86 Architecture Teams |
48 |
Games Developer/Council Member/Foundation Trustee |
49 |
Gentoo Foundation |