whatbot 0.13-TRIAL Deleted
Kwalitee Issues
- has_readme
-
Add a README to the distribution. It should contain a quick description of your module and how to install it.
- has_meta_yml
-
Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.
- no_files_to_be_skipped
-
Fix MANIFEST.SKIP or use an authoring tool which respects MANIFEST.SKIP. Note that each entry in MANIFEST.SKIP is a regular expression. You may need to add appropriate meta characters not to ignore necessary stuff.
Error: MANIFEST.SKIP,t/00-compile.t,t/01-whatbot.t,t/11-database-table-url.t,t/21-command-admin.t,t/command-math.t,t/command-tell.t,t/command-trigger.t,t/database-table-karma.t,t/database-table-soup.t,t/database-table-useralias.t,t/example.conf,t/helper-bootstrap-link.t,t/helper-bootstrap.t,t/io-timer.t,t/manifest.t,t/role-bootstraptemplate.t
- manifest_matches_dist
-
Run a proper command ("make manifest" or "./Build manifest", maybe with a force option), or use a distribution builder to generate the MANIFEST. Or update MANIFEST manually.
Error:
- MANIFEST (70) does not match dist (80):
- Missing in MANIFEST: MANIFEST.SKIP, lib/whatbot/Command/Role/BootstrapTemplate.pm, lib/whatbot/Helper/Bootstrap.pm, lib/whatbot/Helper/Bootstrap/Link.pm, t/00-compile.t, t/01-whatbot.t, t/11-database-table-url.t, t/21-command-admin.t, t/command-math.t, t/command-tell.t, t/command-trigger.t, t/database-table-karma.t, t/database-table-soup.t, t/database-table-useralias.t, t/example.conf, t/helper-bootstrap-link.t, t/helper-bootstrap.t, t/io-timer.t, t/manifest.t, t/role-bootstraptemplate.t
- Missing in Dist: conf/whatbot.conf, inc/Module/Install.pm, inc/Module/Install/Base.pm, inc/Module/Install/Can.pm, inc/Module/Install/Fetch.pm, inc/Module/Install/Makefile.pm, inc/Module/Install/Metadata.pm, inc/Module/Install/Scripts.pm, inc/Module/Install/Win32.pm, inc/Module/Install/WriteAll.pm
- use_strict
-
Add 'use strict' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules are strictly written.
Error: whatbot::State
- prereq_matches_use
-
List all used modules in META.yml requires
Error:
- Clone
- DateTime
- LWP::UserAgent
- MooseX::DeclareX
- MooseX::Types
- URI::Encode
- namespace::autoclean
- main_module_version_matches_dist_version
-
Make sure that the main module name and version are the same of the distribution.
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: whatbot/lib/whatbot/State.pm -- Around line 54: =back without =over
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- meta_yml_has_license
-
Define the license if you are using in Build.PL. If you are using MakeMaker (Makefile.PL) you should upgrade to ExtUtils::MakeMaker version 6.31.
- has_known_license_in_source_file
-
Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.
- use_warnings
-
Add 'use warnings' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.
Error: whatbot::State
- test_prereq_matches_use
-
List all modules used in the test suite in META.yml test_requires
Error:
- Test::Exception
- has_separate_license_file
-
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
- has_security_doc
-
Add SECURITY(.pod|md). See Software::Security::Policy.
- security_doc_contains_contact
-
Add SECURITY(.pod|md) and add a contact address. See Software::Security::Policy.
- has_contributing_doc
-
Add CONTRIBUTING(.pod|md). See https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.