1 |
On Sat, 2006-06-24 at 22:38 -0700, Donnie Berkholz wrote: |
2 |
> Ned Ludd wrote: |
3 |
> > I would be in favor of a gentoo-dev-announce list if it allowed me |
4 |
> > to unsubscribe from this list. |
5 |
> |
6 |
> Sure, if you want to just accept any decisions rather than participate |
7 |
> in making them. The -dev-announce list should be for finalized |
8 |
> decisions. It should be too late to dispute them once they're sent to it. |
9 |
> |
10 |
> For important discussions, it may be worth announcing that they're |
11 |
> starting -- e.g., for a GLEP -- so people could then be sure to pay |
12 |
> attention to that discussion on -dev. |
13 |
|
14 |
At one point, a long time ago, a few of us had actually started |
15 |
discussing a mailing list reorganization. It somewhat died out simply |
16 |
because we didn't keep up with it. However, it went something like |
17 |
this: |
18 |
|
19 |
- Create a new list ("gentoo-core-announce" ?) |
20 |
Reading: dev-only |
21 |
Posting: dev-only, reply-to set to gentoo-core |
22 |
This is the reference list of things (policy, decisions and discussions |
23 |
in progress) all developers must know about. |
24 |
|
25 |
- Keep -core and -dev, as non-required reading |
26 |
|
27 |
- Confirm the role of "gentoo-announce" as the official reference list |
28 |
of things all users must know about (especially difficult upgrades just |
29 |
before they reach stable). Posting is moderated. |
30 |
|
31 |
|
32 |
|
33 |
Now, do we really need it to be -core-announce? Not really. In fact, |
34 |
at one point we'd come up with both a -core-announce and a |
35 |
-dev-announce, with -core-announce being for more sensitive information. |
36 |
Some other ideas that were tossed about was changing "gentoo-announce" |
37 |
into "gentoo-security-announce" (since it is currently GLSA-only, |
38 |
really) with reply-to set to gentoo-security and create a |
39 |
"gentoo-user-announce" with reply-to set to gentoo-user, where we would |
40 |
put more information, such as the information that would be given via |
41 |
the portage tree in GLEP42. However, it was also brought up that anyone |
42 |
interested in security is probably also interested in things that might |
43 |
break their system (heh) so instead of splitting it to two lists, it |
44 |
would remain a single list. |
45 |
|
46 |
As you can guess, we never got around to actually writing up a GLEP for |
47 |
this or anything. We didn't reach any kind of impasse, we just quit |
48 |
working on it. |
49 |
|
50 |
I just thought I would pass this along so people know what was discussed |
51 |
previously and would also like to apologize for being one of the |
52 |
slackers who let this die a while back without so much as sending it to |
53 |
the list for discussion. |
54 |
|
55 |
-- |
56 |
Chris Gianelloni |
57 |
Release Engineering - Strategic Lead |
58 |
x86 Architecture Team |
59 |
Games - Developer |
60 |
Gentoo Linux |