Philip Crow (PHILCROW)

Showing the uploads of PHILCROW

• Having the link to your public Version Control System (VCS) in the META files help others to contribute to your code.
• Having an explicit link to your bugtracker/issues in the META file help people know where to submit bug reports.
• Having Continuous Integration (CI) configured helps the author catch regression and platform incompability much faster.
• Having license information in the META files can help people automatically verify that they use only approved licenses.
• Having your own CPAN Dashboard is cool.
• CT Stands for CPAN Testers
• No means the author does not have public VCS and does not want to have one or that the author is not interested in CI (for at least some of the modules).

Name	MetaCPAN	Author	Date	VCS	Issues	CI	Licenses	CT Pass	CT Fail	CT Unknown	CT NA	Coverage	Dashboard	Kwalitee	Reverse
Class-Colon		PHILCROW	2019-02-15T22:26:34	Add repo	Add repo	Add repo		334	0	0	0	91.67	Add dashboard	100.00	0
Bigtop		PHILCROW	2010-07-10T22:08:44	Add repo	Add repo	Add repo		22	117	2	0	10.85	Add dashboard	93.75	0
UML-Sequence		PHILCROW	2007-09-11T22:12:29	Add repo	Add repo	Add repo		0	2	0	0	73.08	Add dashboard	93.75	0
Inline-TT		PHILCROW	2006-02-04T14:58:39	Add repo	Add repo	Add repo		679	391	2	0	68.10	Add dashboard	100.00	1
Data-HTMLDumper		PHILCROW	2005-11-08T00:35:51	Add repo	Add repo	Add repo		0	2	0	0	89.81	Add dashboard	96.88	0
Java-Build		PHILCROW	2003-10-06T17:51:14	Add repo	Add repo	Add repo		0	10	274	0	-	Add dashboard	93.75	0
UML-State		PHILCROW	2003-06-03T16:16:32	Add repo	Add repo	Add repo		356	175	0	14	82.61	Add dashboard	96.88	0

Statistics

• Total: 7
• Has VCS: 0 ( 0% )
• - GitHub:
• - GitLab:
• Has CI: 0 ( 0% )
• - GitHub Actions: 0
• - Jenkins: 0
• - Azure Pipeline: 0
• - Travis-CI: 0
• - CircleCI: 0
• - Appveyor: 0
• - GitLab Pipeline: 0
• - Bitbucket Pipelines: 0
• Has Bugz: 0 ( 0% )