| 1 |
On 07-04-2006 11:07:28 +0100, Ciaran McCreesh wrote: |
| 2 |
> I mean, as a purely hypothetical example... Could you imagine just how |
| 3 |
> many dumb feature requests, questions and requests for code from the |
| 4 |
> unwashed masses someone would get if they admitted to having an early |
| 5 |
> alpha of an alternative to Portage that didn't require Python? Having |
| 6 |
> to deal with the noise would be more than enough to ensure that no more |
| 7 |
> development would ever get done... |
| 8 |
|
| 9 |
This is ofcourse a purely hypothetical prediction for a hypothetical |
| 10 |
example. Another hypothesis might be that noone would care about the |
| 11 |
hypothetical alternative to Portage, hence no developer obstruction |
| 12 |
would take place at all. Yet another hypothesis might be that there |
| 13 |
would actually exist a few smart users that give some smart comments on |
| 14 |
the, in this case hypothetical, product. |
| 15 |
|
| 16 |
Maybe user-rel should, together with GWN bridge this problem by keeping |
| 17 |
the source of news anonymous? Just to use it as teasers of what kind of |
| 18 |
things are being done in Gentoo's kitchen? |
| 19 |
Of course this only holds for new projects like in your hypothetical |
| 20 |
example. |
| 21 |
|
| 22 |
Existing projects, like KDE and GCC probably already deal with questions |
| 23 |
from users, and giving a status update once a month would in my opinion |
| 24 |
help them to keep users both informed and interested, which is what the |
| 25 |
original poster meant I think. From a user-rel perspective the |
| 26 |
information is used to inform the users that they're not waiting in vain |
| 27 |
for something not to happen, as well as why they are waiting, for |
| 28 |
example. |
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
Fabian Groffen |
| 33 |
-- |
| 34 |
gentoo-dev@g.o mailing list |
Archives