Permalink
Browse files

initial import of Dist-Zilla-Plugin-CheckMetaResources

  • Loading branch information...
0 parents commit 37fd61ea454f3e8822053b655508ef7fbd2c8625 @xdg xdg committed Aug 8, 2012
Showing with 125 additions and 0 deletions.
  1. +2 −0 .gitignore
  2. +6 −0 Changes
  3. +50 −0 README.PATCHING
  4. +9 −0 dist.ini
  5. +35 −0 lib/Dist/Zilla/Plugin/CheckMetaResources.pm
  6. +23 −0 perlcritic.rc
@@ -0,0 +1,2 @@
+/Dist-Zilla-Plugin-CheckMetaResources*
+.build
@@ -0,0 +1,6 @@
+Revision history for Dist-Zilla-Plugin-CheckMetaResources
+
+{{$NEXT}}
+
+ - First release
+
@@ -0,0 +1,50 @@
+README.PATCHING
+
+Thank you for considering contributing to this distribution. This file
+contains instructions that will help you work with the source code.
+
+The distribution is managed with Dist::Zilla. This means than many of the
+usual files you might expect are not in the repository, but are generated
+at release time (e.g. Makefile.PL).
+
+However, you can run tests directly using the 'prove' tool:
+
+ $ prove -l
+ $ prove -lv t/some_test_file.t
+
+For most distributions, 'prove' is entirely sufficent for you to test any
+patches you have.
+
+You may need to satisfy some dependencies. See the included META.json
+file for a list. If you install App::mymeta_requires from CPAN, it's easy
+to satisfy any that you are missing by piping the output to your favorite
+CPAN client:
+
+ $ mymeta-requires | cpanm
+ $ cpan `mymeta-requires`
+
+Likewise, much of the documentation Pod is generated at release time.
+Depending on the distribution, some documentation may be written in a Pod
+dialect called WikiDoc. (See Pod::WikiDoc on CPAN.) If you would like to
+submit a documentation edit, please limit yourself to the documentation you
+see.
+
+If you see typos or documentation issues in the generated docs, please
+email or open a bug ticket instead of patching.
+
+Dist::Zilla is a very powerful authoring tool, but requires a number of
+author-specific plugins. If you would like to use it for contributing,
+install it from CPAN, then run one of the following commands, depending on
+your CPAN client:
+
+ $ cpan `dzil authordeps`
+ $ dzil authordeps | cpanm
+
+Once installed, here are some dzil commands you might try:
+
+ $ dzil build
+ $ dzil test
+ $ dzil xtest
+
+You can learn more about Dist::Zilla at http://dzil.org/
+
@@ -0,0 +1,9 @@
+name = Dist-Zilla-Plugin-CheckMetaResources
+author = David Golden <dagolden@cpan.org>
+license = Apache_2_0
+copyright_holder = David Golden
+copyright_year = 2012
+
+[@DAGOLDEN]
+:version = 0.027
+
@@ -0,0 +1,35 @@
+use 5.008001;
+use strict;
+use warnings;
+
+package Dist::Zilla::Plugin::CheckMetaResources;
+# ABSTRACT: No abstract given for Dist::Zilla::Plugin::CheckMetaResources
+# VERSION
+
+# Dependencies
+use autodie 2.00;
+
+1;
+
+=for Pod::Coverage method_names_here
+
+=head1 SYNOPSIS
+
+ use Dist::Zilla::Plugin::CheckMetaResources;
+
+=head1 DESCRIPTION
+
+This module might be cool, but you'd never know it from the lack
+of documentation.
+
+=head1 USAGE
+
+Good luck!
+
+=head1 SEE ALSO
+
+Maybe other modules do related things.
+
+=cut
+
+# vim: ts=2 sts=2 sw=2 et:
@@ -0,0 +1,23 @@
+severity = 5
+verbose = 8
+
+[Variables::ProhibitPunctuationVars]
+allow = $@ $!
+
+[TestingAndDebugging::ProhibitNoStrict]
+allow = refs
+
+# Turn these off
+[-BuiltinFunctions::ProhibitStringyEval]
+[-ControlStructures::ProhibitPostfixControls]
+[-ControlStructures::ProhibitUnlessBlocks]
+[-Documentation::RequirePodSections]
+[-InputOutput::ProhibitInteractiveTest]
+[-Miscellanea::RequireRcsKeywords]
+[-References::ProhibitDoubleSigils]
+[-RegularExpressions::RequireExtendedFormatting]
+[-InputOutput::ProhibitTwoArgOpen]
+
+# Turn this on
+[Lax::ProhibitStringyEval::ExceptForRequire]
+

0 comments on commit 37fd61e

Please sign in to comment.