Personally, I think it's useful, particularly at the beginning of the
project when people are working on large pieces of functionality and
there is less visibility into the details. I am thinking of the stage
where we haven't finished implementing big features yet, they are in
progress. I attend both the services and apps meetings but I find it
useful to have stuff consolidated into one summary. It gives a high
level view of the progress/priorities across the teams. I actually
used content from these when I put together the milestone report cards.
Once we hit the bug fix phase where everything is tracked in
bugzilla, having a written status was less useful - at least for me.
I really just cared about bug counts/priorities and who was working
on what. I just ran a bunch of searches for this info. I think this
is more meaningful than listing out what bugs people were working on
in a status summary.
I know it's quite a bit of work since I did it in your absence one
week :-).
On Dec 6, 2005, at 2:40 PM, Lisa Dusseault wrote:
I've been doing a status rollup for a while. The first few went to
this mailing list but then Pieter convinced me to post it to the
blog <wp.osafoundation.org> and since then I've been inconsistent
about copying it to this list.
Doing this rollup has been a significant amount of work: though I
don't do it every week (don't expect one this week), it can be
nearly half a day's work of finding information, writing it or
rewriting it, and formatting, each time. The hardest work is
actually trying to summarize masses of information. I know what
the services team did this week, in my head -- but how do I explain
that succinctly to somebody not part of the group or perhaps even
not involved day-to-day in OSAF? (e.g. what does it *mean* to a
reader if somebody fixed bug 4028 and worked on 4031 and 4685?)
So I'd like to get some sense of the value or lack thereof. Who is
this useful for? Reply with at least a +1 if this practice has
been useful to you; suggestions and comments welcome too.
Lisa
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
