Florian Merges (FMERGES)

Showing the uploads of FMERGES

• 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
Log-Dispatch-Configurator-YAML		FMERGES	2007-09-08T22:50:38	Add repo	Add repo	Add repo		1117	0	7	2	79.07	Add dashboard	96.88	0
Catalyst-Model-JabberRPC		FMERGES	2007-07-12T19:51:43	Add repo	Add repo	Add repo		535	0	9	0	64.00	Add dashboard	100.00	0
Catalyst-Model-XMLRPC		FMERGES	2007-07-04T10:39:54	Add repo	Add repo	Add repo		476	0	8	0	72.73	Add dashboard	100.00	0
PGPLOT-Simple		FMERGES	2007-03-15T23:37:36	Add repo	Add repo	Add repo		41	0	2	13	90.00	Add dashboard	100.00	0
Spork-S5ThemePixel		FMERGES	2007-03-12T01:08:27	Add repo	Add repo	Add repo		3	0	0	0	50.00	Add dashboard	100.00	0
Spork-S5ThemeBlue		FMERGES	2007-03-10T12:16:22	Add repo	Add repo	Add repo		210	0	4	1	50.00	Add dashboard	100.00	0
FileUpload-Filename		FMERGES	2006-09-06T08:50:59	Add repo	Add repo	Add repo		0	2	0	0	85.53	Add dashboard	100.00	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% )