1 |
On Fri, 07 Apr 2006 15:19:35 +0100 Christel Dahlskjaer |
2 |
<christel@g.o> wrote: |
3 |
| So, from a developer pov Ciaran; if we could come up with some way of |
4 |
| keeping up to date with what you guys do (without eating up any of |
5 |
| your time or getting in your way) and then keep the masses informed, |
6 |
| would that be more attractive? Obviously making sure that information |
7 |
| is kept to a not exactly bare minimum, but presented in such a way |
8 |
| that it doesn't in any way halt progress or potential change of |
9 |
| direction? |
10 |
|
11 |
If it's information on things that are fine being public but aren't |
12 |
simply because of lack of time to write them up, then that would be |
13 |
great. If it's things that're being kept quiet purposefully, however, |
14 |
then the last thing we want is to start telling people things. |
15 |
|
16 |
| > Hence why some of us don't announce non-trivial projects on public |
17 |
| > mailing lists, and instead keep any discussion on -core and sekrit |
18 |
| > IRC channels. That's how what's now known as eselect was developed, |
19 |
| > and it turned out far nicer than the XML-laden aborted gentoo-config |
20 |
| > project precisely because of the lack of end user 'input'. |
21 |
| |
22 |
| In more of a informative 'these are the exciting things we're doing' |
23 |
| sort of way rather than a 'tell us why you disagree' sort of way |
24 |
| maybe. |
25 |
|
26 |
See, that doesn't work. There's this strange notion that because we're |
27 |
open source, users somehow have a right to a) see the code, b) make |
28 |
suggestions, c) demand new features, d) get support and e) annoy other |
29 |
developers or upstream when they break something that has a knock-on |
30 |
effect of breaking an unrelated package. |
31 |
|
32 |
-- |
33 |
Ciaran McCreesh : Gentoo Developer (Wearer of the shiny hat) |
34 |
Mail : ciaranm at gentoo.org |
35 |
Web : http://dev.gentoo.org/~ciaranm |