+1 on the status overview, and to the one or two line summaries that
have been in each section - I think there's real value to boiling down
the detailed meeting minutes into one or two key points.
and +1 on copying it to this list.
I think the blog tends to be an outward-facing view of chandler, but
the status of all 3 projects is of particular value to both outsiders
looking in, and developers focused on their own area who would benefit
from knowing about the other projects.
I would actually argue that postings to the blog should also
automatically go to the dev list as well, but I'm not sure everyone
would agree with that :) I for one rarely ever read the blog, even if I
know I really should :)
Alec
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
