| 1 |
On 10/4/06, Chris Gianelloni <wolf31o2@g.o> wrote: |
| 2 |
> On Wed, 2006-10-04 at 12:21 -0700, Donnie Berkholz wrote: |
| 3 |
> > Donnie Berkholz wrote: |
| 4 |
> > > Chris Gianelloni wrote: |
| 5 |
> > >> Now, perhaps what everyone would like, instead, would be status reports |
| 6 |
> > >> *where necessary* from certain projects? |
| 7 |
> > >> |
| 8 |
> > >> In fact, the council has been discussing asking a few projects about the |
| 9 |
> > >> status on some of their tasks. The main reason for this is for |
| 10 |
> > >> communications purposes. Basically, we'd just get a "Hey, where are you |
| 11 |
> > >> at on $x?" response from the teams. |
| 12 |
> > >> |
| 13 |
> > >> I don't *want* to drown projects in bureaucracy and paperwork. I want |
| 14 |
> > >> them to *accomplish* things, instead. |
| 15 |
> > > |
| 16 |
> > > I really like the concept of answering questions rather than giving |
| 17 |
> > > arbitrary reports. The problem is, sometimes nobody outside your project |
| 18 |
> > > knows the right questions to ask. |
| 19 |
> > |
| 20 |
> > I was thinking more about this. What if, instead of these periodic |
| 21 |
> > status reports, you just send out a note when something interesting |
| 22 |
> > happens? There's no point in holding it back till your monthly required |
| 23 |
> > report, and it saves the trouble of the report when nothing's happening. |
| 24 |
> |
| 25 |
> That's really a good idea. When I was writing, I was thinking more |
| 26 |
> along the lines of things like: |
| 27 |
> |
| 28 |
> What's the status of bugs getting updated? |
| 29 |
> What's the status of anonsvn/anoncvs? |
| 30 |
> What's the status of QA's policy document? |
| 31 |
> |
| 32 |
> These are things that either are interesting to a large number of |
| 33 |
> developers, and easier to answer once rather than 300 times, or things |
| 34 |
> the council itself has asked a group to do based on one of our |
| 35 |
> decisions. Of course, we could/would take ideas for things to ask, and |
| 36 |
> again, all we need really is something like this (mock) answer: |
| 37 |
> |
| 38 |
> "Well, we have all the hardware in place and have gotten access to the |
| 39 |
> systems. We've installed the OS and setup the main databases, but we're |
| 40 |
> still having some issues with the virtual IP scheme, and that's slowing |
| 41 |
> us down on getting this implemented." |
| 42 |
> |
| 43 |
> That's it. No long "report" or anything is necessary. Just a simple, |
| 44 |
> short few sentences on the current status is all that's really needed |
| 45 |
> for the long ongoing projects. For other things, like, xorg 7.1 going |
| 46 |
> stable or KDE 3.5.5 being unmasked, a simple announcement from the team |
| 47 |
> when it happens should really cover it. That isn't even necessary from |
| 48 |
> most projects, as they simply do maintenance tasks which don't really |
| 49 |
> need an announcement. |
| 50 |
> |
| 51 |
> -- |
| 52 |
> Chris Gianelloni |
| 53 |
> Release Engineering Strategic Lead |
| 54 |
> Alpha/AMD64/x86 Architecture Teams |
| 55 |
> Games Developer/Council Member/Foundation Trustee |
| 56 |
> Gentoo Foundation |
| 57 |
> |
| 58 |
> |
| 59 |
> |
| 60 |
|
| 61 |
How about something in the "planet" format that where each group |
| 62 |
reporting status could do so at their schedule when they feel an |
| 63 |
update is necessary or warrented. |
| 64 |
|
| 65 |
Then users could just read the website for the latest status updates. |
| 66 |
|
| 67 |
There are a few "hot" items many people are interested in such as kde |
| 68 |
or gnome stablization, for example. A simple line like "Don't expect |
| 69 |
KDE 5.0 to go stable before the end of the year" provides transparency |
| 70 |
and a bit of communication to the user community. |
| 71 |
-- |
| 72 |
gentoo-dev@g.o mailing list |
Archives