CONTRIBUTING

This project is free software for the express purpose of collaboration. We welcome all input, bug reports, feature requests, general comments, and patches.

If you're not sure about anything, please open an issue and ask!

Standard of Conduct

To ensure a welcoming, safe, collaborative environment, this project will enforce a standard of conduct:

• The topic of this project is the project itself. Please stay on-topic.
• Stick to the facts
• Avoid demeaning remarks and sarcasm

Unacceptable behavior will receive a single, public warning. Repeated unacceptable behavior will result in removal from the project.

Remember, all the people who contribute to this project are volunteers.

About this Project

Project Goals

Statocles is a content management system built on plain files, easily edited by a text editor, transformed into HTML, and written out to be served by an HTTP daemon as static content.

Statocles tries to simplify building a website as much as possible. Plugins are provided to automatically ensure that web best practices are followed. Statocles should assume defaults of web accessibility and interoperability for all devices.

Statocles should provide an easy framework to build rich web content. As much as possible, the user should be writing their content, and Statocles should handle all the rest.

Repository Layout

This project follows CPAN conventions with some additions, explained below.

lib/

Modules are located in the lib/ directory. Most of the functionality of the project should be in a module. If the functionality should be available to users from a script, the script should call the module.

bin/

Command-line scripts go in the bin/ directory. Most of the real functionality of these should be in a library, but these scripts must call the library function and document the command-line interface.

t/

All the tests are located in the t/ directory. See "Getting Started" below for how to build the project and run its tests.

xt/

Any extra tests that are not to be bundled with the CPAN module and run by consumers is located here. These tests are run at release time and may test things that are expensive or esoteric.

share/

Any files that are not runnable code but must still be available to the code are stored in share/. This includes default config files, default content, informational files, read-only databases, and other such. This project uses File::Share to locate these files at run-time.

site/

This project has a Statocles site located in the site/ directory. This site is deployed to http://preaction.me/statocles and serves as the official site of the project for release announcements and documentation.

What to Contribute

Comments

The issue tracker is used for both bug reports and to-do list. Anything on the issue tracker, open or closed, is available for discussion.

Fixes

For fixes, simply fork and send a pull request. Fixes to anything, documentation, code, tests, are equally welcome, appreciated, and addressed!

If you are fixing a bug in the code, please add a regression test to ensure it stays fixed in the future.

Features

All contributions are welcome if they fit the scope of this project. If you're not sure if your feature fits, open an issue and ask. If it doesn't fit, we will try to find a way to enable you to add your feature in a related project (if it means changes in this project).

When contributing a feature, please add some basic functionality tests to ensure the feature is working properly. These tests do not need to be comprehensive or paranoid, but must at least demonstrate that the feature is working as documented.

Getting Started Building and Running Tests

This project uses Dist::Zilla for its releases, but you aren't required to use it for contributing.

Using Build.PL

This is the easiest way that requires the fewest dependencies.

Install the project's dependencies and run the tests by doing:

perl Build.PL
./Build installdeps
./Build test

Using Makefile.PL

This is the older standard way. If you can install CPAN modules, you can probably do this. It requires make and maybe a C compiler.

Run the tests by doing:

perl Makefile.PL
make test

Install the module's dependencies by doing:

cpanm .

Using Dist::Zilla

Once you have installed Dist::Zilla, you can get this distributions's dependencies by doing:

dzil listdeps --author --missing | cpanm

Once all that is done, testing is as easy as:

dzil test

Before you Submit Your Contribute

Copyright and License

All contributions are copyright their respective owners, so make sure you agree with the project license (found in the LICENSE file) before contributing.

The list of Contributors is calculated automatically from the Git commit log. If you do not wish to be listed as a contributor, or if you wish to be listed as a contributor with a different e-mail address, tell me so in the ticket or e-mail me at doug@preaction.me.

Code Formatting and Style

Please try to maintain the existing code formatting and style.

• 4-space indents
• Opening brace on the same line as the opening keyword
  • Exceptions made for lengthy conditionals
• Closing brace on the same column as the opening keyword

Documentation

Documentation is incredibly important, and contributions will not be accepted until documentated.

• Methods must be documented inline, above the code of the method
• Method documentation must include name, sample usage, and description of inputs and outputs
• Attributes must be documented inline, above the attribute declaration
• Attribute documentation must include name, sample value, and description
• User-executable scripts must be documented with a short synopsis, a longer description, and all the arguments and options explained