Bug Reports

So you've found a bug in r509. Awesome! (Wait, that came out wrong) Go ahead and open an issue and answer the following questions:

• What did you do?
• What did you expect to happen?
• What happened instead?

Please also supply code that replicates the bug. If you can, a failing test would be ideal, but a simple script demonstrating the error is acceptable.

Don't forget to specify what version of r509 you are using!

Pull Requests

• You must supply tests for your changes.

• All behavioral changes must be documented. Both the README and the yardoc must be kept up-to-date.

• One pull request per feature. If you want to do more than one thing, send multiple pull requests.