Having the working groups report status updates in multiple places and formats seems like a waste of resources, but I believe it is useful communication channel to have a single location to be able to see a periodic contemporaneous status summary of our collective efforts in order to track our progress. In the past, the Status Update posts on the blog get a lot of hits, so I would continue to extract a summary from the wiki status update and make a blog post pointing back to the wiki page.

Maybe though, we don't need this higher-level summary weekly, perhaps monthly (or even quarterly) would be sufficient. And we could continue to post the individual status of each group in the list summaries for those that just want to focus on a particular project.

Pieter

On 6/19/06, Katie Capps Parlante <[EMAIL PROTECTED]> wrote:
For the last few months, we've been attempting to put together a weekly
OSAF "status rollup" on the wiki:
http://wiki.osafoundation.org/bin/view/Journal/WeeklyStatus20060407

Pieter takes the highlights and makes a blog entry:
http://wp.osafoundation.org/2006/04/17/osaf-status-overview-07-april-2006/

Lisa used to do this task, and last December asked if anyone found the
status rollup useful. Several folks mentioned that they did:
http://lists.osafoundation.org/pipermail/chandler-dev/2005-December/004545.html

The status to be "rolled up" and summarized is tracked in weekly meeting
notes for some teams:
http://wiki.osafoundation.org/bin/view/Journal/CommunityMtg20060407
http://wiki.osafoundation.org/bin/view/Journal/AppsMeeting20060406
http://wiki.osafoundation.org/bin/view/Journal/PlatformMtg20060404

As more decisions happen on the list and fewer in meetings, we've also
started doing list summaries:
http://lists.osafoundation.org/pipermail/cosmo-dev/2006-June/000963.html
http://lists.osafoundation.org/pipermail/design/2006-June/004845.html
http://lists.osafoundation.org/pipermail/chandler-dev/2006-June/006138.html

Those of us responsible for updating the wiki status page haven't been
keeping up with it regularly. Its not really clear to us that it is
important to do so, given the move to doing more work on the lists. Its
also not clear to us that anyone is reading the status wiki. We'd like
to stop doing the wiki status rollups, and spend more energy on list
discussions and summaries. One thing we can do is send out links to team
meeting notes with highlights summarized to the appropriate lists.

We're going to go ahead and try this, and see how it works out. Comments
welcome.

Cheers,
Katie











_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general

Reply via email to