---

3.7 Reporting Team Status

Team leaders must send an annual report about the status of the team. A good report should include:

• General information about the team’s accomplishments during the past year, like:
  • - A list of new translations.
  • - New members since the last report.
  • - Solved problems and other issues, if any. (Usual bug reports and other improvements/fixes to the existing translations do not count as problems in this sense.)
• Current active members.
• Current problems (technical or social), conflicts, and ideas for sorting them out.
• Anything else you consider important or worth mentioning.

The best time to send a report is near the end of the year, for example November.

If there is no sensitive information in the report and you feel like sharing it, you can send it to [email protected] (which is still a private mailing list). That way, other list readers may help with suggestions how to solve a particular issue. Informing each other about the progress improves the community spirit.

If you do not wish to share some information that is in the report, please send it to [email protected].