On Tue, Mar 23, 2010 at 7:11 PM, Peter Tribble <peter.tribble at gmail.com>wrote:
> On Tue, Mar 23, 2010 at 3:05 PM, Giovanni Tirloni <gtirloni at sysdroid.com> > wrote: > > Hello, > > > > I would like to suggest that it would be good for the project if we > > released the Community Reports [1] on a quarterly basis. This would keep > the > > whole community, as well as outside parties, aware of things that are > > happening. > > Feel free to comment on: > > http://wiki.genunix.org/wiki/index.php/OGB_2009/006 > > which was reasonably close to where we wanted to be, but was > never actually approved. > > Thanks for the pointer. I knew my idea was far from original but didn't know it had already been documented. Reminder: add genunix.org to the list of websites that should be searched :) Regarding the periodicity, I think we should stick to the 3-month period suggested but drop the annual report requirement. Since each quarterly report will be a delta from the previous one, they can be read in sequence to get an idea of what happened in that year. Breaking it down into small pieces also increases the probability it'll get done. With that in mind, the reports for May, August and November should not be made optional. The February report would comprise the months of December, January and February... there's New Years in the middle where people take vacation days, travel, etc. When they come back perhaps it will be hard to remember everything that happened... so my suggestion would be to move the months to (end of) March, June, September, December. If we get the December report on time we can release an annual report before Dec 31st, essentialy closing the year's activities. As for the format, the following fields should suffice: - Title - URL (or mailing list if there isn't a project web page yet) - Summary of recent activities - Next/Open Tasks If it's the first report that a project is submitting, they should provide a *quick* overview of what they are all about in one paragraph and another 1-2 paragraphs for the recent activities. Subsequent reports don't need that overview. Regarding the mechanism for input, a simple web form recording to a database is enough. Is that something that needs to go through website-discuss ? I haven't a clue on how this would be added to opensolaris.org. Thanks, -- Giovanni -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/ogb-discuss/attachments/20100325/5bf605c7/attachment.html>
