Incubator Clutch Status

The name of each podling is linked to a podling clutch analysis page. If your podling is in incubation, but is missing from the Clutch table, then it still needs to be added to the content/podlings.xml file. See the mentor’s guide. Clutch also generates the Projects page from content/podlings.xml.

Usually the Incubator sponsors podlings. Occasionally Apache Top Level Projects (TLPs) sponsor podlings. The sponsor is chosen on the proposal. Set the value in the content/podlings.xml entry for the podling.

This is the date the podling started. Usually this is the date the podling proposal vote passed on the Incubator mailing list. Set this in the content/podlings.xml entry for the podling.

This is the number of days since the start date. This is color coded according to the normal timeline of a podling. <3, <12, <18, <24, >24 months. We may adjust these levels to better fit currently-observed cycles.

For the first three months podlings report monthly. If the podling misses a report, it returns to the monthly-reporting requirement until it reports again.

Which months the podling reports: 1 = January, April, July, October; 2 = February, May, August, November; 3 = March, June, September, December. Note that the report process for a month begins at the end of the prior month. The IPMC chair sends out the reporting schedule on a monthly basis, and reminders to each podling’s dev list.

Each podling maintains a status file in content/projects/(podling).xml which Clutch converts to a status page. Your mentor sets up the file and then the podling maintains it. The key part to maintain is the "News" section, where you announce New Committers, PPMC Members, and Releases. For greater detail, please see:

Click the link in the cell to view the current status page.

The date the status page was last updated. Keep the Status Page up to date with frequent news about:

Days since the status page was last updated. The text color indicates when a podling is not keeping its status up to date. <2, <4, <9, >9 months.

Cumulative number of commits to the podling status file in the previous 2, 4, and 9 months

The number of committers who have been approved to date. Taken from Whimsy via public project ldap. Maintained in Whimsy through the roster pages. Click the cell to view the public phone book.

The number of committers added since establishment. This count comes from the Status page "News" section. See guides on voting in new committers and new ppmc members.

Indicates whether the podling has created a Gitbox or Subversion code repository. Projects may have multiple Gitbox repositories. Click the podling name in the first column to view all of the podling’s repositories. A podling coming to the ASF may need to request a migration or a new repository. The list of Gitbox repositories comes from Gitbox json.

Indicates whether the podling has an Issue Tracker. If the status file has an issue tracker link and the link is valid, there is a link to the tracker in the cell.

Indicates whether the podling has established a dev email list and archives. This comes from the status page, and Clutch confirms that it matches the usual naming pattern. If the list is available, the cell has a link to the mailbox archive podling dev list.

Indicates whether the podling has established a commits email list and archives. This comes from the status page, and Clutch confirms that it matches the usual naming pattern. If the list is available, the cell has a link to the mailbox archive podling commits list. Sometimes a podling will start by directing code repository and issue tracker notification emails to their dev list. This will often obscur meaningful conversation.

Podlings should maintain a website so the user community can find out information about the podling and The Apache Software Foundation. Here is the incubator’s website guide. If the website is not provided in the status file, Clutch tries to find it using the usual naming patterns.

If the website exists, the cell provides a link to it. Whimsy provides a periodic scan of podling websites which you can view here. The clutch process uses json data to add notes about website issues to the podling’s clutch analysis page under "Errata".

Indicates whether the podling has a directory in the incubator’s release distribution directory. If this exists, the cell provides a link.

Indicates whether the podling has a PGP "Signing KEYS" file in its distribution area. If this is present, the cell provides a link.

Indicates whether the podling has a release in their distribution area. Podlings must comply with Apache release and release distribution policies as modified by the Incubator.

If there is a podling release, the cell provides a link to the podling’s clutch analysis page’s release section.

Once the Board has approved the podling’s graduation resolution, update your podling metadata in the content/podlings.xml file as you progress through graduation. Complete the tasks listed in the documentation, such as a final tidy of the status page. See Infrastructure steps for graduation.

Once the Incubator PMC has agreed to a podling’s retirement, update the podling metadata and tidy the status page. If the podling is continuing development elsewhere, make sure to provide the new location. When this occurs chances are someone on the IPMC will handle these duties ad hoc.

Sometimes other issues are found which are listed below for:

Copies the news from the podling status page

Listing of various podling resources

Information about the podling’s release, harvested from the distribution area’s svn repository.

Issues which may require further work.