Jim Bacon (BOFTX)

Showing the uploads of BOFTX

• 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
Role-RunAlone		BOFTX	2020-09-07T06:41:06	Add repo	Add repo	Add repo						100.00	Add dashboard	100.00	0
MooX-Role-CliOptions		BOFTX	2019-09-25T02:12:17	Add repo	Add repo	Add repo		269	1	0	0	82.44	Add dashboard	100.00	0
DateTime-Fiscal-Retail454		BOFTX	2015-09-14T20:39:15	Add repo	Add repo	Add repo		5	0	0	0	82.67	Add dashboard	??	0
MooX-Role-Reconstruct		BOFTX	2014-11-08T17:31:40	Add repo	Add repo	Add repo						92.00	Add dashboard	96.88	0
Games-Dukedom		BOFTX	2014-11-07T04:13:33	Add repo	Add repo	Add repo						17.09	Add dashboard	96.88	0
DateTimeX-Fiscal-Fiscal5253		BOFTX	2014-10-24T19:49:22	Add repo	Add repo	Add repo		5	0	0	0	89.31	Add dashboard	??	0
Acme-Thoroughly-Modern-Perl		BOFTX	2014-04-01T12:16:36	Add repo	Add repo	Add repo						100.00	Add dashboard	100.00	0
Acme-Dice		BOFTX	2013-10-19T05:02:55	Add repo	Add repo	Add repo		3	0	0	0	87.18	Add dashboard	100.00	0

Statistics

• Total: 8
• 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% )