| 1 |
On Wed, 2006-10-04 at 22:00 -0400, Mike Kelly wrote: |
| 2 |
> > I don't *want* to drown projects in bureaucracy and paperwork. I want |
| 3 |
> > them to *accomplish* things, instead. |
| 4 |
> |
| 5 |
> Sending a brief "All's well with releng" email isn't exactly what I |
| 6 |
> would call "drowning in bureaucracy". |
| 7 |
|
| 8 |
Of course not, but that's where it starts. Forcing projects to really |
| 9 |
do anything on a regular set schedule that isn't internally set is |
| 10 |
bureaucracy and pointless. I don't *want* to have to spend my time |
| 11 |
thinking about which projects I'm supposed to be sending status reports |
| 12 |
on that haven't done anything. I'd *much* rather spend my time actually |
| 13 |
*developing* on the projects that *are* currently moving. |
| 14 |
|
| 15 |
This is my *entire* point. Forcing a project to send in worthless |
| 16 |
little "we're still here" messages doesn't do anything. Of *course* |
| 17 |
they're still there. They have a project page. They have members. |
| 18 |
They're doing commits. |
| 19 |
|
| 20 |
Rather than wasting time trying to get everybody out giving each other |
| 21 |
warm fuzzies, I'd prefer we focus on the areas where we truly need to |
| 22 |
improve communications. A couple good examples of projects/teams that |
| 23 |
affect everyone are infrastructure and the trustees. These are two good |
| 24 |
places for status reports. Things like the games team are not. |
| 25 |
|
| 26 |
-- |
| 27 |
Chris Gianelloni |
| 28 |
Release Engineering Strategic Lead |
| 29 |
Alpha/AMD64/x86 Architecture Teams |
| 30 |
Games Developer/Council Member/Foundation Trustee |
| 31 |
Gentoo Foundation |
Archives