Project: ExampleProject

Release: Fluorine

Summary

This is an example of a request for a project to moved from Unmanaged to Managed. It should be submitted no later than the start of the release. The request should make it clear that the requesting project meets all of the Managed Release Requirements.

Healthy Community

The request should make it clear that the requesting project has a healthy community. The request may also highlight a history of having a healthy community.

Responsiveness

The request should make it clear that the requesting project is responsive over email, IRC, Jira and in regular meetings. All committers should be subscribed to the project's mailing list and the release list. The request may also highlight a history of responsiveness.

Active Committers

The request should make it clear that the requesting project has a sufficient number of active committers to review contributions in a timely manner, support potential contributors, keep CSIT healthy and generally effectively drive the project. The requesting project should also make it clear that they have pruned any inactive committers. The request may also highlight a history of having sufficient active committers and few inactive committers.

TSC Attendance

The request should acknowledge that the requesting project is required to send a committer to represent the project to at least 50% of TSC meetings. The request may also highlight a history of sending representatives to attend TSC meetings.

Checkpoints Submitted On-Time

The request should acknowledge that the requesting project is required to submit checkpoints on time. The request may also highlight a history of providing deliverables on-time.

Jobs Required for Managed Projects Running

The request should show that the requesting project has the required jobs for Managed Projects running and healthy. Links should be provided.

Depend only on Managed Projects

The request should show that the requesting project only depends on Managed Projects.

Documentation

The request should acknowledge that the requesting project is required to produce a user guide, developer guide and release notes for each release. The request may also highlight a history of providing quality documentation.

CLM

The request should acknowledge that the requesting project is required to handle Component Lifecycle Violations in a timely manner. The request should show that the project's CLM job is currently healthy. The request may also show that the project has a history of dealing with CLM violations in a timely manner.