| 1 |
I don't normally subscribe to this list, but I figured I should respond to |
| 2 |
this message: |
| 3 |
|
| 4 |
>1) Recruit one or more non-developers from the community and give them |
| 5 |
>read-only access to the closed development list. Their job is to write a |
| 6 |
>condensed summary of what's being discussed. (perhaps like KernelTraffic) |
| 7 |
|
| 8 |
This is already being done via the GWN. Some of the stories that have been |
| 9 |
pulled *directly* from -core conversations: |
| 10 |
|
| 11 |
* The proposed "Secure Portage" (2 articles: 20030421, 20030407) |
| 12 |
* Gentoo/PPC team restructuring (20030401) |
| 13 |
* Changes in the way Gentoo Linux supports CFLAGS (20030324) |
| 14 |
* Gentoo Linux launches a "hardened Gentoo" effort (20030317) |
| 15 |
* Gentoo partners with NeTraverse (20030224) |
| 16 |
* New Release Manager for 1.4 (20030210) |
| 17 |
|
| 18 |
Those are the first 6 I saw from scanning the summaries. It is by no |
| 19 |
means a complete list. |
| 20 |
|
| 21 |
Additionally, the entire "Moves, Adds and Changes" section comes directly |
| 22 |
from -core as well. |
| 23 |
|
| 24 |
Most of the stuff on -core is, well, boring. There's a lot of stuff that |
| 25 |
belongs on -dev -- as others have said, we're working on fixing that. |
| 26 |
|
| 27 |
The stuff that is interesting *does* get summarized for the Gentoo |
| 28 |
community to read and review. |
| 29 |
|
| 30 |
Absolutely, some stuff is kept private. We bicker amongst ourselves, toss |
| 31 |
out stupid ideas that quickly get shot down and all sorts of other stuff |
| 32 |
that has no place in the public eye. I think it's crucially important that |
| 33 |
the Gentoo developers have some place where they can vent frustrations, ask |
| 34 |
stupid questions, etc. without having to worry about having every word |
| 35 |
scrutinized, torn apart and second-guessed by the user community. |
| 36 |
gentoo-core provides that channel. |
| 37 |
|
| 38 |
--kurt |
Archives