Clutch is a tool which gathers details about the projects (podlings) currently in incubation and re-generates the table below. A clutch analysis page is generated for each podling along with several data files. Its aim is 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 definitions and notes below regarding purpose, interpretation, and how to.
Clutch last gathered: Fri May 22 01:24:29 2020 UTC.
Number of podlings in incubation: 43
Current Board Report: May2020
The orange items indicate where more care and attention is needed.
Anything vermilion is an issue that should be addressed ASAP. Admittedly nothing can be done about elapsed time.
The bluish-green items indicate success.
The yellow items are okay.
Click on the column header link for definitions.
Click on cells to go to available related resources.
Click on the podling name in the first column to go to the podling’s clutch analysis page with deeper and more detailed information.
Podling | Sponsor | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Incubator |
2016-08-30 |
False |
1 |
2017-02-13 |
0,0,0 |
0 |
False |
||||||||||||
Incubator |
2019-10-17 |
False |
1 |
2020-05-03 |
7,13,18 |
5 |
False |
False |
|||||||||||
Incubator |
2018-11-13 |
False |
3 |
2018-11-23 |
0,0,0 |
0 |
False |
False |
False |
False |
False |
||||||||
Incubator |
2017-11-01 |
False |
3 |
2018-01-03 |
0,0,0 |
0 |
|||||||||||||
Incubator |
2017-08-27 |
False |
3 |
2018-08-28 |
0,0,0 |
0 |
|||||||||||||
Incubator |
2019-03-30 |
False |
2 |
2020-04-29 |
1,2,13 |
0 |
|||||||||||||
Incubator |
2018-08-20 |
False |
1 |
2020-05-18 |
2,2,2 |
0 |
|||||||||||||
Incubator |
2019-08-29 |
False |
2 |
2019-08-31 |
0,0,2 |
0 |
|||||||||||||
Incubator |
2018-07-18 |
False |
2 |
2018-08-23 |
0,0,0 |
0 |
|||||||||||||
Incubator |
2018-01-18 |
False |
2 |
2018-02-22 |
0,0,0 |
0 |
False |
||||||||||||
Incubator |
2016-07-13 |
False |
1 |
2019-08-02 |
0,0,0 |
0 |
|||||||||||||
Incubator |
2017-02-23 |
True |
1 |
2017-07-28 |
0,0,0 |
0 |
|||||||||||||
Incubator |
2017-06-23 |
False |
2 |
2018-09-21 |
0,0,0 |
0 |
False |
||||||||||||
Incubator |
2016-09-13 |
False |
3 |
2017-02-03 |
0,0,0 |
0 |
|||||||||||||
incubator |
2019-01-17 |
False |
1 |
2020-05-18 |
9,12,12 |
0 |
|||||||||||||
Incubator |
2018-11-16 |
False |
1 |
2020-05-12 |
3,3,8 |
2 |
|||||||||||||
Incubator |
2018-11-18 |
False |
3 |
2020-04-15 |
4,7,11 |
0 |
|||||||||||||
Incubator |
2017-06-05 |
False |
1 |
2017-06-23 |
0,0,0 |
0 |
False |
||||||||||||
Incubator |
2018-08-21 |
False |
3 |
2018-11-08 |
0,0,0 |
0 |
False |
False |
False |
||||||||||
Incubator |
2015-12-21 |
False |
1 |
2019-06-02 |
0,0,0 |
0 |
False |
||||||||||||
Incubator |
2017-01-23 |
False |
1 |
2019-04-14 |
0,0,0 |
0 |
|||||||||||||
Incubator |
2018-02-04 |
False |
3 |
2018-03-01 |
0,0,0 |
0 |
|||||||||||||
Incubator |
2020-02-13 |
True |
2 |
2020-03-15 |
0,11,- |
1 |
False |
||||||||||||
Incubator |
2019-12-09 |
False |
1 |
2020-01-30 |
0,4,8 |
0 |
|||||||||||||
Incubator |
2017-09-30 |
False |
2 |
2017-10-02 |
0,0,0 |
0 |
False |
False |
False |
False |
|||||||||
Incubator |
2018-10-17 |
False |
2 |
2020-01-09 |
0,0,1 |
0 |
|||||||||||||
Incubator |
2016-05-27 |
False |
1 |
2017-08-01 |
0,0,0 |
0 |
|||||||||||||
Incubator |
2017-01-03 |
False |
2 |
2017-02-02 |
0,0,0 |
0 |
|||||||||||||
Incubator |
2015-11-29 |
False |
2 |
2016-05-10 |
0,0,0 |
0 |
|||||||||||||
Incubator |
2014-12-15 |
False |
3 |
2015-01-06 |
0,0,0 |
0 |
|||||||||||||
Incubator |
2017-10-22 |
False |
2 |
2017-10-26 |
0,0,0 |
0 |
False |
False |
False |
||||||||||
Incubator |
2016-09-23 |
False |
3 |
2016-10-28 |
0,0,0 |
0 |
|||||||||||||
Incubator |
2019-11-11 |
False |
3 |
2019-12-09 |
0,0,4 |
0 |
|||||||||||||
Incubator |
2017-05-21 |
False |
3 |
2017-06-26 |
0,0,0 |
0 |
|||||||||||||
Incubator |
2019-08-20 |
False |
1 |
2019-12-14 |
0,0,1 |
0 |
False |
False |
False |
||||||||||
Incubator |
2015-12-02 |
False |
2 |
2018-09-18 |
0,0,0 |
0 |
|||||||||||||
Incubator |
2019-02-21 |
False |
2 |
2019-02-28 |
0,0,0 |
0 |
|||||||||||||
Incubator |
2019-11-03 |
False |
1 |
2019-12-26 |
0,0,2 |
0 |
False |
False |
False |
False |
|||||||||
Incubator |
2019-03-25 |
False |
2 |
2019-11-22 |
0,0,1 |
0 |
|||||||||||||
Incubator |
2019-03-06 |
False |
1 |
2019-08-02 |
0,0,0 |
0 |
|||||||||||||
Incubator |
2018-06-11 |
False |
3 |
2018-09-19 |
0,0,0 |
0 |
False |
False |
False |
False |
|||||||||
Incubator |
2016-11-30 |
False |
1 |
2019-02-21 |
0,0,0 |
9 |
|||||||||||||
Incubator |
2020-01-21 |
True |
1 |
2020-04-06 |
1,4,4 |
0 |
False |
||||||||||||
The orange and vermilion items indicate where more care and attention is needed. The following notes for each column provide definitions and attempt to link directly to the relevant process documentation:
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. The Projects page is also generated from content/podlings.xml.
Usually podlings are sponsored by the Incubator. Ocassionally podlings are sponsored by other Apache projects. The sponsor is chosen on the proposal. The value is set within 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. This is set within 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 reports then they are moved to monthly until they report 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 will send out the reporting schedule on a monthly basis along with reminders to each podling’s dev list.
Each podling maintains a status file in content/projects/(podling).xml which is converted to a status page. Your mentor will setup the file and then the podling should maintain it. The key part to maintain is the "News" section where New Committers, PPMC Members, and Releases should be announced. For greater detail, please see:
Click on the link in the cell to view the current status page.
The date status page was last updated. Keep the Status Page up to date with frequent news about:
New Committers
New PPMC Members
New Releases
New Repositories
New Resources
Days since the status page was last updated. The text is colored to warn when status is not being kept 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 total number of committers that have been established to date. Taken from Whimsy via public project ldap. Maintained in Whimsy through the roster pages. Click on the cell to view the public phone book.
The number of new committers added since establishment. This count is gathered from the Status page "News" section. See guides on voting in new committers and new ppmc members.
A Gitbox or Subversion code repository has been created. Projects may have multiple Gitbox repositories. Click on 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 is retrieved from Gitbox json.
The podling has an Issue Tracker. If the status file has been updated to have an issue tracker link and the link is valid then there will be a link to the tracker in the cell.
The podling has established a dev mail list and archives. This is picked up from the status page and then confirmed for the usual naming pattern. If the list is available the cell will link to the mailbox archive podling dev list.
The podling has established a commits mail list and archives. This is picked up from the status page and then confirmed for the usual naming pattern. If available he cell will link to the mailbox archive podling commits list. Sometime 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 that their users 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 then the usual naming patterns are tried. Assuming that the website exists the cell will provide 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".
The podling has a directory in the incubator’s release distribution directory. If this is present the cell provides a link.
The podling has a PGP "Signing KEYS" file in their distribution area. If this is present then the cell provides a link. There is a facility that performs periodic checks on Apache releases and signatures - "release checker".
The podling has a release in their distribution area. Podlings are expected to comply with release and release distribution policies as modified by the Incubator.
If there is a podling release then the cell will provide 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. Do various tasks as 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 retirement, update the podling metadata and tidy the status page. If the podling is continuing development elsewhere then make sure that the new location is provided. 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:
batchee
druid
flagon
joshua
myriad
netbeans
omid
rya
shardingsphere
singa
tamaya
taverna
tephra
toree
unomi
Essentially Clutch is helping us all to follow the process from the "Acceptance" phase onwards. 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.
This list is gathered from the Projects in incubation summary table. The Mentors are ASF members or individuals recognized by the IPMC 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 Gates (gates): SAMOA, Superset
Bikas Saha (bikas): Livy
Bob Paulin (bob): MXNet
Byung-Gon Chun (bgchun): Nemo, TVM
Carl Steinbach (cws): Iceberg
Chris Lambertus (cml): Warble
Christofer Dutz (cdutz): Daffodil, IoTDB, StreamPipes, Training
Craig Russell (clr): Training
David Fisher (wave): Daffodil, DataSketches, Doris, ECharts, Heron, NLPCraft
David Meikle (dmeikle): Flagon
Devaraj Das (ddas): Ratis
Evans Ye (evansye): DataSketches, NLPCraft
Felix Cheung (felixcheung): Crail, Teaclave, Pinot, YuniKorn
Flavio Paiva Junqueira (fpj): NuttX
Furkan Kamaci (kamaci): DataSketches, DLab, DolphinScheduler, Flagon, Teaclave, NLPCraft, Tuweni, TVM
Henri Yandell (bayard): MXNet
Henry Saputra (hsaputra): DLab, TVM
Holden Karau (holden): YuniKorn
Hyunsik Choi (hyunsik): Nemo
Jake Farrell (jfarrell): Heron
Jakob Homan (jghoman): Ratis, Superset
James Taylor (jamestaylor): Iceberg
Jason Dai (jasondai): MXNet
Jason Lowe (jlowe): YuniKorn
Jean-Baptiste Onofré (jbonofre): brpc, Gobblin, Livy, Nemo, StreamPipes, TubeMQ, Tuweni
Jean-Frederic Clere (jfclere): Milagro
Jianyong Dai (daijy): Hivemall, Teaclave
Jim Jagielski (jim): Gobblin, Pinot, Superset
John D. Ament (johndament): Pony Mail
Jukka Zitting (jukka): PageSpeed
Julian Feinauer (jfeinauer): StreamPipes
Julian Hyde (jhyde): Crail
Julien Le Dem (julien): Heron, Iceberg, Toree
Junping Du (junping_du): NuttX, TubeMQ, YuniKorn
Justin Mclean (jmclean): APISIX, IoTDB, NuttX, StreamPipes, Training, TubeMQ
Jörn Rottmann (joern): SDAP
Kenneth Knowles (kenn): DataSketches, StreamPipes
Kevin A. McGrail (kmcgrail): brpc, ECharts, IoTDB
Kevin Ratnasekera (djkevincr): APISIX, DolphinScheduler
Kishore Gopalakrishna (kishoreg): Hudi, Pinot
Koji Sekiguchi (koji): Hivemall
Konstantin I Boudnik (cos): DLab, NLPCraft
Lars Francke (larsfrancke): Training
Leif Hedstrom (zwoop): PageSpeed
Lewis John McGibbney (lewismc): Flagon
Liang Chen (chenliang613): DataSketches, DolphinScheduler
Luciano Resende (lresende): Crail, Hudi, Livy, Marvin-AI, Teaclave, Toree
Markus Weimer (weimer): MXNet, Nemo, TVM
Matt Sicker (mattsicker): Teaclave
Michael Wall (mjwall): MXNet, Tuweni
Mohammad Asif Siddiqui (asifdxtreme): NuttX
Myrle Krantz (myrle): Weex
Nick Kew (niq): Annotator, Milagro, PageSpeed
Olivier Lamy (olamy): Gobblin, Pinot
Owen O’Malley (omalley): Iceberg
P. Taylor Goetz (ptgoetz): DLab, Heron
Paul King (paulk): NLPCraft
Roman Shaposhnik (rvs): NLPCraft
Ryan Blue (blue): Iceberg, Toree
Sebastian Schelter (ssc): TVM
Sergio Fernández (wikier): S2Graph
Shao Feng Shi (shaofengshi): DolphinScheduler, Doris
Sharan Foga (sharan): Pony Mail
Sheng Wu (wusheng): DolphinScheduler, ECharts
Sijie Guo (sijie): TubeMQ
Suneel Marthi (smarthi): Hudi
Ted Liu (tedliu): ECharts
Thomas Weise (thw): Hudi
Tianqi Chen (tqchen): TVM
Tim Allison (tallison): Flagon
Timothy Chen (tnachen): TVM
Tommaso Teofili (tommaso): Annotator
Trevor Grant (rawkintrevo): SDAP
Uma Maheswara Rao G (umamahesh): Ratis, Spot
Von Gosling (vongosling): APISIX, brpc
Willem Ning Jiang (ningjiang): APISIX, Doris, IoTDB, Weex
William Colen (colen): Marvin-AI
Woonsan Ko (woonsan): S2Graph
Zhijie Shen (zjshen): Teaclave, TubeMQ
Any Incubator committer can run 'clutch'. In the top-level of the SVN repos incubator/public/trunk SVN, do: './clutch2.sh' which will re-generate the data files and Asciidoctor files for the clutch. This is all a part of the normal build in GIT: Incubator Git. See the Readme.
Clutch 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 and validates that certain resources are established and steps are achieved.
Clutch output includes data files
The clutch analysis both fills the data included on this page and creates an analysis for each podling that can be linked to from the podling name in the clutch table.
The podling description from content/podlings.xml
The podling start date.
The date of the last update of project/status.xml.
The reporting cycle.
The number of committers and ppmc members. Indication if these are equal.
Mentor list including apache ids.
Copies the news from the podling status page
Listing of various podling resources
Link to podling’s public website
Developer mailing list archive
Commits mailing list archive
Link to issue tracker
Link to wiki
Detailed list of gitbox repos from infra’s ground truth for the podling.
Link to any subversion repository.
For each gitbox repos:
Gitbox link
Github link
Description
Number of commits
Date of last commit
Information about the podling’s release harvested by reviewing the distribution area’s svn repository.
Current releases:
Link to the signing key, if it exists.
Link to instructions on how to verify a release.
Release list is suppressed if there are no signing keys
For each release:
Download link using closer.lua
Signature link
Hash link
Size of the download file
Date that the release was added to the distribution area.
User who moved the release.
Revision in the svn repository.
Issues which may require further work.
Errata has a list of potential issues identified for the podling
Critical issues are in bold.
Links to pages on how to resolve the issue
Link to the whimsy podling site scan
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 podlings due to report in that group. (See report_due_1.txt, report_due_2.txt, and report_due_3.txt) These are used by the IPMC to send monthly report alert reminders.
podlings_graduated.txt - list of graduated podlings, one per line with start and end dates.
podlings_retired.txt - list of retired podlings, one per line with start and end dates.
Occasionally there are other issues, usually regarding podlings not cleaning up after their "graduation".
batchee: Has graduated, but still has remains on Incubator distribution mirrors. See help.
druid: Has graduated, but still has remains on Incubator distribution mirrors. See help.
flagon: Has a distribution filename missing the word "incubating/incubator". See help.
joshua: Has graduated, but still has remains on Incubator distribution mirrors. See help.
myriad: retired project has remains on Incubator mirrors. See help.
netbeans: Has a distribution filename missing the word "incubating/incubator". See help.
netbeans: Has graduated, but still has remains on Incubator distribution mirrors. See help.
omid: Has graduated, but still has remains on Incubator distribution mirrors. See help.
rya: Has graduated, but still has remains on Incubator distribution mirrors. See help.
shardingsphere: Has graduated, but still has remains on Incubator distribution mirrors. See help.
singa: Has graduated, but still has remains on Incubator distribution mirrors. See help.
tamaya: retired project has remains on Incubator mirrors. See help.
taverna: retired project has remains on Incubator mirrors. See help.
tephra: Has graduated, but still has remains on Incubator distribution mirrors. See help.
toree: Has a distribution filename missing the word "incubating/incubator". See help.
unomi: Has a distribution filename missing the word "incubating/incubator". See help.
unomi: Has graduated, but still has remains on Incubator distribution mirrors. See help.
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 and the detailed pages from the point-of-view of encouragement and nurture.
The nest was becoming full, some podlings were forgotten, rolled into dark corners: a new tool "clutch" was created to assist oversight of all podlings (gmane link is now missing). The clutch was started 2008-10-19. (missing gmane link) There was prior list discussion. Also see INCUBATOR-78
The colours for the table were specifically chosen to assist with colour-blindness and general accessibility. See the email discussion that led to this Re: Clutch color coding. 2008-12-04 http://s.apache.org/clutch_colour and see some testing notes and demonstrations.
Thanks again to: "Color Universal Design (CUD) - How to make figures and presentations that are friendly to Colorblind people." Masataka Okabe and Kei Ito. (http://jfly.iam.u-tokyo.ac.jp/color/