John Peacock (JPEACOCK)

Showing the uploads of JPEACOCK

• 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
Module-Starter-XSimple		JPEACOCK	2012-12-10T00:26:26	Add repo	Add repo	Add repo						25.17	Add dashboard	100.00	0
SVN-Notify-Mirror		JPEACOCK	2012-07-04T17:10:21	Add repo	Add repo	Add repo		4	0	0	0	22.88	Add dashboard	93.75	0
SVN-Notify-Snapshot		JPEACOCK	2008-08-30T15:06:43	Add repo	Add repo	Add repo		491	53	55	0	28.04	Add dashboard	96.88	0
SVN-Notify-Config		JPEACOCK	2008-03-08T15:26:01	Add repo	Add repo	Add repo		70	54	1	0	-	Add dashboard	93.75	0
version-Limit		JPEACOCK	2007-07-26T14:53:11	Add repo	Add repo	Add repo		551	0	3	0	91.23	Add dashboard	93.75	0
version-AlphaBeta		JPEACOCK	2006-02-05T15:54:56	Add repo	Add repo	Add repo		483	0	5	0	81.94	Add dashboard	100.00	0
Math-FixedPrecision		JPEACOCK	2002-05-24T18:30:34	Add repo	Add repo	Add repo		500	0	2	0	87.72	Add dashboard	87.50	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% )