Clutch is a tool which gathers details about the projects currently in incubation and re-generates the table below. It aims to encourage and nurture, to provide an overview of the state of establishment of various resources, and to provide quick access to those resources. See more notes below regarding purpose and interpretation.

• The orange items indicate where more care and attention is needed. Anything vermilion is an issue that should be addressed ASAP. The bluish-green items indicate success and the yellow items are okay.
• A: startDate
• B: elapsedDays - <3 <12 <18 <24 >24 months
• C: reportingMonthly in w.a.o/incubator/ReportingSchedule (current report: July2009)
• D: reportingGroup - in which set of months do they report:
  group-1=Jan,Apr,Jul,Oct group-2=Feb,May,Aug,Nov group-3=Mar,Jun,Sep,Dec
• E: hasReportingGroup - did podling remember to choose a group
• F: hasStatusEntry in i.a.o/projects
• G: statusUpdateDate - the status page was last updated
• H: statusAge - days since the SVN status page was last updated - <2 <4 <9 >9 months
• I: statusUpdateCounts - number of commits to status file in the previous 2,4,9 months (cumulative)
• J: numberCommitters - accounts have been established, total number to date
• K: numberCommittersNew - new committers added since establishment (gathered from each project's Status page "News" section)
• L: hasSvn - Subversion repository is created
• M: hasTracker - has an Issue Tracker
• N: hasMailListDev
• O: hasMailListCommits
• P: hasWebSite
• Q: hasDistribution - has w.a.o/dist/incubator/... area (not necessarily yet a release)
• R: hasKeys - has a PGP KEYS file in their distribution area

Clutch last gathered: Thu Jul 2 04:18:02 2009 UTC.
Number of podlings in incubation: 36

Occasionally there are other issues, e.g. Not listed in ReportingSchedule, yet listed in IncubationTable.

• No known issues.

Any Incubator committer can run 'clutch'. In the top-level of the "incubator/public/trunk" SVN, do: 'python clutch.py' which will generate a source xml file at "site-author/clutch.xml". Do 'svn diff' to see what changed. Then build and deploy the site as normal.

It reads the Wiki page at ReportingSchedule then builds a list of projects, adds some attributes, does some validation. Then it reads the source file for the "projects currently in incubation" table, ensures that each new project has an entry, adds some more attributes. Clutch then gathers some data from each project's Status page, makes other guesses, and validates that certain facilities are established and steps are achieved.

The clutch is the set of eggs which have been laid. The mother hen (our Incubator PMC) needs to continually gather them, to ensure that none have rolled from the nest or moved to the outside, being forgotten or becoming cold. Clutch also means to grasp eagerly.

So please interpret this table from the point-of-view of encouragement and nurture.

Essentially Clutch is helping us all to follow the process from the "Acceptance" phase onwards (explained in Process Description and Incubation Policy and Mentor Guide and Other Guides and summarised at Podling Bootstrap). Any committer on a podling can help with these steps. Don't leave it to your mentors, although there are some steps that only they can do.

The first steps are the "Acceptance" phase. See doc and doc and doc.

The orange and vermilion items indicate where more care and attention is needed. The following notes for each column, expand on the column definitions above and attempt to link directly to the relevant process documentation:

• Project - If your project is in incubation, but is missing from the Clutch table, then you have forgotten to add it to the Wiki ReportingSchedule. (doc and doc)
• Sponsor - This information is gathered from the list of Projects in incubation summary table. The "not known" is because it is missing from that table. See notes for "hasStatusEntry" below.
• A: startDate - This information is gathered from the list of Projects in incubation summary table. The "not known" is because it is missing from that table.
• B: elapsedDays - Calculated from startDate.
• C: reportingMonthly in ReportingSchedule.
• D: reportingGroup - in which set of months do they report.
• E: hasReportingGroup - did podling remember to choose a group. See notes for "Project" above.
• F: hasStatusEntry in Projects in incubation table and an associated project Status page. (doc and doc and doc and doc)
• G: statusUpdateDate - the status page was last updated. Clutch does an 'svn log' query for the project's Status page.
• H: statusAge - days since the SVN status page was last updated
• I: statusUpdateCounts - number of commits to status file in the previous 2,4,9 months (cumulative). Clutch does an 'svn log' query for the project's Status page, and counts the edits for those time ranges.
• J: numberCommitters - accounts have been established, total number to date. Clutch parses the relevant section of the ASF Committers by Project Modules page and counts the total, including mentors.
• K: numberCommittersNew - new committers added since establishment (gathered from each project's Status page "News" section). Clutch parses the News section and detects the string "new committer", counting each matched line. See notes for "hasStatusEntry" above. (doc and doc and doc)
• L: hasSvn - Subversion repository is created. (doc and doc)
• M: hasTracker - has an Issue Tracker
• N: hasMailListDev -
• O: hasMailListCommits -
• P: hasWebSite -
• Q: hasDistribution - has w.a.o/dist/incubator/... area (not necessarily yet a release)
• R: hasKeys - has a PGP KEYS file in their distribution area
• otherIssues - When projects graduate or become dormant, then they need to clean up.
• Graduate - Remove from the ReportingSchedule. In the Projects in incubation table, move it to the "Graduated" section. Remove entry from right-side panel. Do various other tasks listed in the docs. (doc and doc)
• Dormant or Retired - Remove from the ReportingSchedule. In the Projects in incubation table, move it to the "Dormant" or "Retired" section. Remove entry from right-side panel. (doc)

This list is gathered from the Projects in incubation summary table.

• Alan Cabrera: Shiro, VCL
• Andrus Adamchik: Click
• Bertrand Delacretaz: Ace, ESME
• Bill Stoddard: Bluesky, Imperius
• Brett Porter: Hama
• Brian Fitzpatrick: Shindig
• Brian McCallister: Cassandra, Shindig
• Carsten Ziegeler: Ace, PhotArk, RCF, Sanselan
• Cliff Schmidt: XAP
• Craig Russell: Imperius, JSPWiki, Olio, Sanselan, Shiro, Tashi
• Curt Arnold: Log4php
• Dan Kulp: Stonehenge
• Danese Cooper: Stonehenge
• Daniel Kulp: ESME
• Dave Johnson: JSPWiki, SocialSite
• Doug Cutting: Etch, Thrift
• Emmanuel Lecharny: Shiro
• Erik Hatcher: Lucene.Net
• Filip Hanik: Imperius
• Geir Magnusson Jr: River
• Gianugo Rabellino: ESME, River
• Grant Ingersoll: Droids
• Greg Stein: Shindig
• Henning Schmiedehausen: Click, Empire-db, JSPWiki, Olio, RCF, SocialSite
• Ian Holsman: Cassandra, Hama
• J. Aaron Farr: Bluesky, ESME
• Jeff Eastman: Hama
• Jeremias Maerki: PDFBox, Sanselan
• Jim Jagielski: Log4php, RAT, Stonehenge
• Jukka Zitting: PDFBox
• Ken Coar: Stonehenge, UIMA
• Kevan Miller: Imperius, OpenWebBeans, VCL
• Martijn Dashorst: Empire-db, Pivot
• Martin Cooper: PhotArk
• Martin van den Bemt: RCF
• Matt Hogstrom: Olio, RAT, VCL
• Matthias Wessendorf: OpenWebBeans
• Matthieu Riou: Cassandra, Stonehenge, Tashi
• Niall Pemberton: PDFBox
• Niclas Hedhman: Ace, Etch, Pivot
• Paul Fremantle: Droids, Shiro, Stonehenge, Tashi
• Phil Steitz: River
• Portals PMC members: WSRP4J
• Rick Hillegas: Olio
• Robert Burrell Donkin: XAP
• Roland Weber: PhotArk
• Ross Gardler: Droids, RAT
• Sam Ruby: JSPWiki, UIMA
• Santiago Gala: Shindig
• Scott Deboy: Log4php
• Susan Wu: XAP
• Sylvain Wallez: ESME, Shindig
• Ted Husted: Click
• Thomas Dudziak: Shindig
• Thomas Fischer: Empire-db
• Torsten Curdt: Cassandra
• Upayavira: Shindig
• Will Glass-Husain: Click
• Will Rowe: Lokahi
• Yoav Shapira: Lokahi, RAT, Sanselan
• Yonik Seeley: Etch

Data files are also generated so that other tools can easily re-use the metadata for the set of projects currently in incubation:

• clutch.txt - list of projects, one per line. Comma-separated values (CSV).
• clutch.pkl - a Python "pickle" file with various attributes (it is in the top-level of SVN incubator/public/trunk).
• Structured list of various details. Not yet happening - need to decide which format (e.g. RDFa, etc.) and which attributes to be stored.