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: May2012)
• 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 the main "Currently in incubation" table (i.e. i.a.o/projects generated from content/podlings.xml)
• 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 - has dev mail list and archives
• O: hasMailListCommits - has commits mail list and archives
• P: hasWebSite
• Q: hasDistributionArea - has w.a.o/dist/incubator/... area (not necessarily yet a release)
• R: hasKeys - has a PGP "KEYS" file in their distribution area
• S: hasRelease - has a release in their distribution area
• other persistent data files
• other issues listed below for: ace clerezza empire-db gora imperius jena lucy mrunit olio ooo opennlp river

Clutch last gathered: Sun May 20 23:45:33 2012 UTC.
Number of podlings in incubation: 50

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

• ace: Has graduated, but still has remains on Incubator distribution mirrors. See help.
• clerezza: Has a distribution filename missing the word "incubating". See help.
• empire-db: Has graduated, but still has remains on Incubator distribution mirrors. See help.
• gora: Has graduated, but still has remains on Incubator distribution mirrors. See help.
• imperius: Has a distribution filename missing the word "incubating". See help.
• jena: Has graduated, but still has remains on Incubator distribution mirrors. See help.
• lucy: Has graduated, but still has remains on Incubator distribution mirrors. See help.
• mrunit: Has graduated, but still has remains on Incubator distribution mirrors. See help.
• olio: Has a distribution filename missing the word "incubating". See help.
• ooo: Has a distribution filename missing the word "incubating". See help.
• opennlp: Has graduated, but still has remains on Incubator distribution mirrors. See help.
• river: Has graduated, but still has remains on Incubator distribution mirrors. See help.

Any Incubator committer can run 'clutch'. In the top-level of the "incubator/public/trunk" SVN, do: 'python3 clutch.py' which will re-generate some xml entities for the data. The normal site build process will automatically combine these with the "content/clutch.xml" source. Do 'svn diff' to see what changed. Then build and deploy the site as normal.

Clutch 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 (i.e. content/podlings.xml), 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)
• Project - If this cell is highlighted with a border, then this project is in the process of graduating or retiring, and not yet finished their move. Hence resources (e.g. mail lists, svn) seem to disappear as they migrate. See Other issues below.
• 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. See notes for "hasStatusEntry" below.
• B: elapsedDays - Calculated from startDate.
• C: reportingMonthly in ReportingSchedule. Your project PPMC should manage your entry in that schedule.
• 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 the Currently in incubation table (i.e. generated from content/podlings.xml) and has 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 - Hints about mail list names are gathered from their Status page, then tries standard convention, then verifies that the mailing lists are established, then ensures that the mail archives are now available.
• O: hasMailListCommits - see above.
• P: hasWebSite -
• Q: hasDistributionArea - has w.a.o/dist/incubator/... area (not necessarily yet a release)
• R: hasKeys - has a PGP "KEYS" file in their distribution area. This utilises Henk's md5 checker which gathers the list of all KEYS files.
• S: hasRelease - has a release in their distribution area. The test is whether they have a signature file (*.asc or *.sig ) associated with a source release artifact (*.tar.gz or *.tgz or *.bz2 or *zip) and the filename includes the word "incubating". (doc and doc)
• otherIssues - When projects graduate or become dormant, then they need to clean up.
• Graduate - Remove from the ReportingSchedule. In the Projects in incubation table, mark its status as "graduated". Do various other tasks listed in the docs, such as final tidy of Status page, tidy the distribution mirrors, etc. (doc and doc)
• Dormant or Retired - Remove from the ReportingSchedule. In the Projects in incubation table, mark its status as "dormant" or "retired". (doc)

This list is gathered from the Projects in incubation summary table. The Mentors are ASF members who have chosen to assist these projects. The best way to find mentors for a new project, is during your Discuss and Proposal phases on the general@ mail list.

• Alan Cabrera: Kafka, VCL
• Alan Gates: Bigtop, Giraph, HCatalog, Oozie
• Alek Slominski: Airavata
• Alex Karasulu: CloudStack, HCatalog
• Alexei Fedotov: Openmeetings
• Andrew Savory: Cordova, DeviceMap, Wookie
• Andrus Adamchik: Openmeetings, Wave
• Anne Kathrine Petteroe: Flex
• Anthony Elder: DirectMemory, EasyAnt, Kato, Nuvem
• Antoine Lévy-Lambert: EasyAnt
• Arun C. Murthy: Ambari
• Arun Murthy: S4
• Ate Douma: Airavata, Wookie
• Ben Laurie: Wave
• Benson Margulies: Isis, Lucene.Net
• Bernd Fondermann: Chukwa
• Bertrand Delacretaz: DeviceMap, Flex
• Brett Porter: CloudStack
• Brian McCallister: Amber, Mesos
• Chris Douglas: Ambari, Chukwa, Kafka, Oozie
• Chris Mattmann: Airavata, Any23, Giraph, SIS
• Christian Grobmeier: OpenOffice.org
• Colm O Heigeartaigh: Syncope
• Craig Russell: JSPWiki, Tashi
• Danese Cooper: OpenOffice.org
• Davanum Srinivas: Wink
• Dave Fisher: Flex
• Dave Johnson: JSPWiki
• David Blevins: DeltaSpike
• David Jencks: Amber
• Dennis Lundberg: NPanday
• Devaraj Das: Oozie
• Donald Woods: Nuvem
• Doug Cutting: Etch
• Emmanuel Lecharny: AWF, Syncope
• Geir Magnusson Jr.: Kafka, Kato
• Gerhard Petracek: DeltaSpike
• Gianugo Rabellino: Amber, Cordova, Lucene.Net
• Greg Reddin: Flex, SIS
• Greg Stein: Bloodhound
• Henning Schmiedehausen: JSPWiki, Wookie
• Henri Gomez: Kalumet
• Hyrum Wright: Bloodhound
• Ian Holsman: Hama
• Isabel Drost: Stanbol
• J. Daniel Kulp: CloudStack
• James W. Carman: Isis
• Jean-Baptiste Onofre: Kalumet
• Jean-Frederic Clere: Amber, Nuvem
• Jeff Eastman: Hama
• Jim Jagielski: CloudStack, DeltaSpike, Kalumet, Kitty, Openmeetings, OpenOffice.org, RAT
• Jochen Wiedmann: VXQuery
• Joe Schaefer: OpenOffice.org, SIS
• Jukka Zitting: Cordova
• Karl Pauls: Celix, Clerezza
• Kevan Miller: DeviceMap, Kitty, SIS, VCL, Wink
• Luciano Resende: Celix, PhotArk, Wookie
• Marcel Offermans: Celix
• Maria Odea Ching: NPanday
• Mark Struberg: AWF, DeltaSpike, Isis
• Martijn Dashorst: Etch
• Matt Benson: DeltaSpike
• Matt Franklin: Wookie
• Matt Hogstrom: RAT, VCL
• Matt Richard Hogstrom: CloudStack
• Matthias Wessendorf: DeltaSpike, NPanday
• Matthieu Riou: Tashi
• Mohammad Nour El-Din: CloudStack, AWF, Isis
• Nick Burch: ODF Toolkit
• Nick Kew: Any23
• Niclas Hedhman: Etch
• Nigel Daley: Flume
• Noirin Plunkett: OpenOffice.org
• Olivier Lamy: CloudStack, DirectMemory, Kalumet
• Owen O'Malley: Ambari, Bigtop, Giraph, HCatalog, Kafka, Oozie
• Patrick Hunt: Bigtop, Flume, S4
• Paul Fremantle: Airavata, Droids, Nuvem, Tashi, VXQuery
• Paul Ramirez: Any23
• Radu Preotiuc-Pietro: VXQuery
• Ralph Goers: Flume
• Raymond Feng: Amber
• Reinhard Poetz: Clerezza
• Richard Frovarp: Droids
• Robert Burrell Donkin: Kato
• Ross Gardler: Airavata, Cordova, Clerezza, Openmeetings, OpenOffice.org, RAT, Stanbol, Wookie
• Sam Ruby: JSPWiki, ODF Toolkit, OpenOffice.org
• Sanjiva Weerawarana: Airavata, VXQuery
• Santiago Gala: Wave
• Shane Curcuru: OpenOffice.org
• Siegfried Goeschl: Isis
• Simone Tripodi: Any23, Syncope
• Stefan Bodewig: EasyAnt, Lucene.Net
• Steve Loughran: Bigtop, Hama
• Sylvain Wallez: DeviceMap, DirectMemory, Wookie
• Ted Dunning: Stanbol
• Thorsten Scherler: Droids
• Tim Williams: DirectMemory
• Tom White: Bigtop, Flume, Mesos
• Tommaso Teofili: Any23, Hama
• Upayavira: Stanbol, Wave
• Vincent Massol: Isis
• Vincent Siveton: Wave
• William A. Rowe Jr.: Chukwa
• Yegor Kozlov: ODF Toolkit, Openmeetings
• 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).
• One text file for each Reporting group listing the dev mail address of the group of projects due to report. (See report_due_[1-3].txt) This is used by other systems to send monthly marvin mail alert reminders.
• Structured list of various details. Not yet happening - need to decide which format (e.g. RDFa, etc.) and which attributes to be stored.

Origin

Colour Scheme

Other Summaries