| 1 |
On 2006.10.07 00:26, Chris Gianelloni wrote: |
| 2 |
> On Fri, 2006-10-06 at 10:24 +0100, Roy Bamford wrote: |
| 3 |
> > Before you can have useful reports, you need a plan to report |
| 4 |
> against. |
| 5 |
> > Like a target date for 2007.0 and its contents. Such a plan depends |
| 6 |
> on |
| 7 |
> > other projects delivering the contents in accordance with their own |
| 8 |
> |
| 9 |
> > plans. Like real life, these plans will have external dependencies |
| 10 |
> on |
| 11 |
> > $UPSTREAM, that Gentoo has little or no control over. |
| 12 |
> |
| 13 |
> Please stop assuming that Release Engineering has any control over |
| 14 |
> what goes on in the tree. Not only do we not have any such control, |
| 15 |
> we also do not *want* any such control. |
| 16 |
> |
| 17 |
[snip] |
| 18 |
|
| 19 |
> I'll be honest, Release Engineering work is *very* stressful. My |
| 20 |
> primary goal as the lead is to try to come up with ways to make |
| 21 |
> working on a release easier for the guys doing the work. I don't see |
| 22 |
> how doing reporting improves their lives. After all, we put out four |
| 23 |
> "reports" a year, two releases, and two meetings between the releases |
| 24 |
> where we plan the next release. Anything more than that is wasteful. |
| 25 |
> |
| 26 |
> ;] |
| 27 |
> |
| 28 |
> -- |
| 29 |
> Chris Gianelloni |
| 30 |
> Release Engineering Strategic Lead |
| 31 |
> Alpha/AMD64/x86 Architecture Teams |
| 32 |
> Games Developer/Council Member/Foundation Trustee |
| 33 |
> Gentoo Foundation |
| 34 |
|
| 35 |
Chris, |
| 36 |
|
| 37 |
I understand you don't have any control over what goes on in the tree. |
| 38 |
In Gentoo, nobody outside of the individual projects does. My post was |
| 39 |
not intended as a crit of yourself or the Release Engineering team. |
| 40 |
I replied in your part of the thread because Release Engineering are |
| 41 |
the obvious users of the mooted plans and reports. |
| 42 |
|
| 43 |
As long as Gentoo is organised as an anarchy, which I have seen work |
| 44 |
well in other groups, then the status quo is fine. If Gentoo is to be |
| 45 |
organised as a single project, then some bureaucracy to oil the wheels |
| 46 |
is needed. In turn, that would mean setting up a management body of |
| 47 |
some sort (not Release Engineering) but that's a whole new thread. No |
| 48 |
replies to that here please. |
| 49 |
|
| 50 |
Either organisation can work providing the contributors want it to make |
| 51 |
it work but there will always be some dissenters discussing change |
| 52 |
(change != improvement). That's a healthy sign in any group. |
| 53 |
|
| 54 |
Regards, |
| 55 |
|
| 56 |
Roy Bamford |
| 57 |
(NeddySeagoon) |
| 58 |
|
| 59 |
|
| 60 |
|
| 61 |
-- |
| 62 |
gentoo-dev@g.o mailing list |
Archives