CONTRIBUTING - hitimes-1.3.1 Documentation

# Hi there!¶ ↑

I see you are interested in contributing. That is wonderful. I love contributions.

I guarantee that there are bugs in this software. And I guarantee that there is a feature you want that is not in here yet. As such, any and all bugs reports are gratefully accepted, bugfixes even more so. Helping out with bugs is the easiest way to contribute.

## The Quick Version¶ ↑

- Have a GitHub Account.

- Search the GitHub Issues and see if your issue already present. If so add your comments, :thumbsup:, etc.

- Issue not there? Not a problem, open up a new issue.

  - Bug reports please be as detailed as possible. Include:

    - full ruby engine and version: `ruby -e 'puts RUBY_DESCRIPTION'`

    - operating system and version

    - version of hitimes `ruby -rubygems -e "require 'hitimes'; puts Hitimes::VERSION"`

    - as much detail about the bug as possible so I can replicated it. Feel free to link in a gist

  - New Feature

    - What the new feature should do.

    - What benefit the new feature brings to the project.

- Fork the repo.

- Create a new branch for your issue: `git checkout -b issue/my-issue`

- Lovingly craft your contribution:

  - `rake develop` to get started

  - `rake test` to run tests

- Make sure that `rake test` passes. Its important, I said it twice.

- Add yourself to the contributors section below.

- Submit your pull request.

## Building Windows Binaries¶ ↑

This is done using github.com/rake-compiler/rake-compiler-dock

1. have VirtualBox installed

2. have Docker Machine installed (docs.docker.com/engine/installation/)

3. `gem install rake-compiler-dock`

4. `rake-compiler-dock` (this could take a while)

5. `bundle`

6. `rake cross native gem`

# Contributors¶ ↑

- Jeremy Hinegardner

- Wojciech Piekutowski