# Contributing

`HorizonCalendar` welcomes both fixes, improvements, and feature additions. If you'd like to contribute, open an issue or a Pull Request with a detailed description of your proposal and/or changes. If you'd like some help getting started, take a look at the [Technical Details](Docs/TECHNICAL_DETAILS.md) document for an overview of `HorizonCalendar`'s architecture.

### One issue or bug per Pull Request

Keep your Pull Requests small. Small PRs are easier to reason about which makes them significantly more likely to get merged.

### Issues before features

If you want to add a feature, consider filing an [Issue](../../issues). An Issue can provide the opportunity to discuss the requirements and implications of a feature with you before you start writing code. This is not a hard requirement, however. Submitting a Pull Request to demonstrate an idea in code is also acceptable, it just carries more risk of change.

### Backwards compatibility

Respect the minimum deployment target. If you are adding code that uses new APIs, make sure to prevent older clients from crashing or misbehaving. Our CI runs against our minimum deployment targets, so you will not get a green build unless your code is backwards compatible.

### Forwards compatibility

Please do not write new code using deprecated APIs.

### Pull Request Process

1. Use the provided [Pull Request template](Docs/PULL_REQUEST_TEMPLATE.md). 
2. Update the README.md with details of changes to the public interface, if necessary.
3. Increase the version number in the [Xcode project file](HorizonCalendar.xcodeproj) (edit in Xcode, not directly) and in the [Podspec file](HorizonCalendar.podspec) with the new version that this
   Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).