1 |
Ciaran McCreesh wrote: |
2 |
> On Fri, 7 Apr 2006 09:51:58 +0100 "Christopher O'Neill" |
3 |
> <chris.oneill@×××××.com> wrote: |
4 |
> | Ideally, what I'd like is for the various dev teams to compile a |
5 |
> | weekly status report, which could then be compiled into the weekly |
6 |
> | newsletter (which currently seems to be lacking much useful |
7 |
> | information). It would be great if we (the users) could find out |
8 |
> | what's going on behind the scenes of our favourite distribution. |
9 |
> |
10 |
> The problem with this is... Once someone says "we're working on $x", |
11 |
> they're continuously pestered about it by users asking when it will be |
12 |
> ready. Given how few of us are paid to work specific hours on Gentoo |
13 |
> things, it's very easy for provisional release dates to be missed -- |
14 |
> and when half of a developer's time is spent responding to questions |
15 |
> about where $x is and why an early test of $x pulled out of a |
16 |
> supposedly "not for end users" repo broke their system and the other |
17 |
> half is spent writing status updates it's pretty much impossible to get |
18 |
> anything out consistently. |
19 |
<snip> |
20 |
|
21 |
Personally, I think this could be lessened by clear documenation. I know it's |
22 |
mentioned in the handbook, but a dedicated topic on "why packages disappear and |
23 |
how to find out why" would be invaluable. This would also help if meaningful |
24 |
notes were added by the dev's on *why* a package was pulled. It isn't a enough |
25 |
for some users to hear "it's broke". What if they want to help? Providing more |
26 |
info in the changelog/p.mask or in package notes (I believe something like this |
27 |
was mentioned some time ago in trying to help facilitate new devs coming up to |
28 |
speed on projects). Also, if there was a single place for info about this, devs |
29 |
would have a helpful place to link people instead of flaming/ignoring or |
30 |
writing out answers to the same old questions. |
31 |
-- |
32 |
gentoo-dev@g.o mailing list |