OGB 2009/006
From Genunix
Working Draft
Contents |
Policy on regular reporting
This is a followup to OGB 2008/009 renumbered for the 2009 term. It refers to Bug 931, Establish regular reports from Projects on their status.
Aim
Each collective (community group, project, user group) should produce regular reports regarding their activities and status. This could also include problems that are being encountered and areas in which help is needed.
It is intended that the reporting mechanism be as lightweight as possible.
Use
The reports can serve several functions:
- To verify that the collective is still active
- To inform the OGB of where each collective is at
- To raise awareness of the work the collective is engaged in
- To give groups that produce newsletters or do advocacy material to work with
- To raise problems if a collective is experiencing issues
Schedule
Reports will be collected quarterly, by the end of the following months:
- May
- August
- November
- February
A call for reports will be issued at the start of the month.
The quarterly reports for May, August, and November, are optional, but should be regarded as an opportunity to give lightweight reports and progress updates.
All collectives should produce an annual report in February covering the activities of the entire year.
The OGB will create a full annual report covering the activities of the entire OpenSolaris Community, distilled from the reports from individual collectives, for the annual meeting. This report will be created by the end of March (hence the last report being produced by the end of February).
Format
The intention is that the minimum level of reporting be very simple. Some example reports are given here:
- The foo usergroup has held 2 meetings over the last quarter
- The bar project has released one prototype
- Work on the yogo project has stalled due to lack of resources
- The baz community continues to sponsor the gizmo project, and has approved the gadget project
Collectives are free to report in more detail if they wish.
For the annual report, the following guidance is given to different collectives as to the information they should be supplying:
- User groups should be reporting on events (meetings) and how many participants are involved
- Community groups should list the projects they sponsor or are associated with
- Projects should note if they have produced deliverables
Implementation
Note: this is sketchy; I'm not sure what's possible.
It is the responsibility of the each collective's facilitator or leader to make sure that the annual report is generated.
A mechanism to input the report should be available. It would be nice to have a simple web form in which the report could be typed in.
The mechanism will track which collectives have (or haven't) submitted reports. It will also track the historical reports. It should be possible to link to the list of reports, for example on a collective's web page.
We may wish to establish an OGB subcommittee to supervise the process.
If a collective fails to produce an annual report, then it will be contacted to give it the opportunity. We may consider the response to that prompting to comprise the report.
If a collective fails to produce two consecutive annual reports, then this will be taken as a sign that the collective is defunct.
