| 1 |
On 2006.10.04 15:27, Chris Gianelloni wrote: |
| 2 |
|
| 3 |
[snip] |
| 4 |
|
| 5 |
> |
| 6 |
> I'll give you Release Engineering's "status reports" for September, |
| 7 |
> October, and November: |
| 8 |
> |
| 9 |
> September: taking a well-deserved break |
| 10 |
> October: taking a well-deserved break |
| 11 |
> November: taking a well-deserved break |
| 12 |
> |
| 13 |
> How about other projects that rely on things like upstream's release |
| 14 |
> cycle? What about projects that just maintain ebuilds? |
| 15 |
> |
| 16 |
> Here's the games team's "status reports" for every month: |
| 17 |
> |
| 18 |
> "Fixed more bugs, added more packages, cleaned up some ebuilds." |
| 19 |
> |
| 20 |
> Now, perhaps what everyone would like, instead, would be status |
| 21 |
> reports |
| 22 |
> *where necessary* from certain projects? |
| 23 |
> |
| 24 |
> In fact, the council has been discussing asking a few projects about |
| 25 |
> the |
| 26 |
> status on some of their tasks. The main reason for this is for |
| 27 |
> communications purposes. Basically, we'd just get a "Hey, where are |
| 28 |
> you |
| 29 |
> at on $x?" response from the teams. |
| 30 |
> |
| 31 |
> I don't *want* to drown projects in bureaucracy and paperwork. I want |
| 32 |
> them to *accomplish* things, instead. |
| 33 |
> |
| 34 |
> -- |
| 35 |
> Chris Gianelloni |
| 36 |
> Release Engineering Strategic Lead |
| 37 |
> Alpha/AMD64/x86 Architecture Teams |
| 38 |
> Games Developer/Council Member/Foundation Trustee |
| 39 |
> Gentoo Foundation |
| 40 |
> |
| 41 |
|
| 42 |
Before you can have useful reports, you need a plan to report against. |
| 43 |
Like a target date for 2007.0 and its contents. Such a plan depends on |
| 44 |
other projects delivering the contents in accordance with their own |
| 45 |
plans. Like real life, these plans will have external dependencies on |
| 46 |
$UPSTREAM, that Gentoo has little or no control over. |
| 47 |
|
| 48 |
With progress reports against plans and updated plans, everyone can see |
| 49 |
whats happened, why some things haven't and what the fallback is, if |
| 50 |
one is required. |
| 51 |
|
| 52 |
The old saw, "If you don't have a plan, then plan to fail" remains true |
| 53 |
for volunteer projects as well as funded ones. |
| 54 |
|
| 55 |
The content and update rate of plans/reports can vary from project to |
| 56 |
project and it need not be onerous. Reporting can even be by exception, |
| 57 |
so to take your "well-deserved break" example, if it was in your plan, |
| 58 |
no report would be needed. |
| 59 |
|
| 60 |
Regards, |
| 61 |
|
| 62 |
Roy Bamford |
| 63 |
(NeddySeagoon) |
| 64 |
|
| 65 |
|
| 66 |
-- |
| 67 |
gentoo-dev@g.o mailing list |
Archives