Proposal for Task Force reports

Please discuss on the discussion page.

Proposal

To increase the amount of communication and collaboration, each task force head is responsible for issuing a monthly status report. The report can be short: a list of the key tasks being worked on, a brief summary of any progress, and if known, a forecast schedule for completion of work items.

The report shall be issued on a fixed schedule. Examples: in the period between the first of the month and the second Thursday of the month; by the 10th of the month.

Perhaps once or twice a year, some task forces can give an annual/semi-annual report on their operations. For example, the infrastructure task force can give a report on the state of the hardware, network and other resource usage stats and trends, forecasts for future needs, emergency recovery plan (and any info on its testing), security incidents, and so forth.

Benefits

Having regular reports makes contributors aware of the progress of the tasks being done, which helps them figure out how they could assist. It also provides a regular catalyst for discussion on the work being done.

Regular reporting also serves a marketing purpose, both external and internal to the contributor team: it allows the community as a whole to see the project's ongoing progress.