[openbeos] Re: Progress reports
- From: Simon Taylor <simontaylor1@xxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Mon, 02 Jun 2008 09:47:29 +0100
Howdy,
My "activity update" posts haven't actually been abandoned, despite how
it looks. I'm currently working on a summary of the last 3 months (600
emails read, over 7000 to go...) Once that's done I'm going to move my
list email address to an IMAP server so I can get the mails at work and
home, so I can keep track of things as they happen.
The kind of audience that I was aiming my update posts at were those on
the fringes of the community, who want a feel for what is happening
without having to subscribe to all the relevant feeds/lists. I think the
best way of doing this is an edited handwritten summary, so people can
check the website and get a feel for what's been going on recently. Your
"annotated commits" approach is an interesting one but is maybe aimed at
a different audience - those who want more frequent, yet more readable
updates on progress.
I think it's a useful thing to have, if only to make the "surface" of
the Haiku website accurately reflect the amount of action happening
underneath.
As for collaborating on this, I'd be happy to hear what ideas anyone has
for how to do that. There is often "related" activity from more than one
source - eg a Dev List discussion sparks a bug report which gets fixed
with a commit - and that makes it hard to split up the workload.
Right, back to reading emails - I'm amazed the Dev List has had over
2000 in 3 months!
Simon
Waldemar Kornewald wrote:
Hi everyone,
it's really sad that nobody is writing progress reports (e.g., commit
log summaries). Does anybody want to give it a try, maybe this time as
a group effort?
What do you think about this: Summarize individual commits using
Google Reader's "Share with note" feature. IOW, you just read the
commit logs and if you find something great then you can tell the
whole community with a single click and maybe a short comment. We'd
only need a short explanation. Most of the time the commit message
already says a lot.
Reader automatically provides a publicly accessible feed for all
shared items. It looks like this (WARNING: this is just an *example*
and it will be removed):
http://www.google.com/reader/shared/17874889821028276775
IOW, it could simply be a cleaned up and "pimped up" version of the
commits feed, intended for non-developers and enthusiasts who want to
follow Haiku's progress more closely.
Now, does anyone want to help with these per-commit "micro-summaries"?
Is there anyone who already uses Google Reader and reads the commit
logs?
Bye,
Waldemar Kornewald
Other related posts:
