This is an old revision of the document!
Required Regular software product releases are a sign of a healthy project. Reports should list the releases made since your last report, along with the release date of each. NOTE: If no releases were made, list the date of the most recent prior release.
Required Discuss briefly how active the project mailing lists and chat channels are. Are emails or user questions regularly read and responded to? What technical changes is the project working on? Is there new development happening, or just bug fixes? NOTE: If activity is minimal, verify whether or not there are at least three active maintainers who can step in when needed, and include this information in the report.
Required A healthy project will often be working towards a common goal, or have a shared understanding of what is being done next - even if individual contributors have their own “itches”. What are the main features planned? What releases are planned? Are there any specific efforts or branches of development under way? This does not need to be described in technical detail. Conversely, if activity is minimal, discuss how the project plans to address that - whether through seeking out new contributors, maintaining in a dormant but available state, or planning towards a move to a Deprecated (and ultimately End of Life) state.
Required Please include the maintainers that were added since your last report. This information will allow us to track the diversity and growth of the maintainers of the project. NOTE: If no maintainers were added since your last report, provide the list of existing maintainers.
Required A healthy project should survive the departure of any single contributor or employer of contributors. Healthy projects also serve needs of many parties. Include information on the number of unique organizations currently contributing to the project. NOTE: The contributions do not need to be source code.
Optional Please provide any additional information that you feel would be useful for TSC to be aware.