Think hard about whether this is something that would be good for a new contributor, if it is, add as much detail as you can to help, then label it as such.

Most importantly, bug triagers should always be nice. We're grateful to know about issues, so if anybody responds rudely, please contact Henrik by email henrik@andyet.net. We're committed to making this whole process as inclusive and friendly as possible.

We do our best to adhere strictly to semver throughout the project. This is crucial to the architectural approach we're taking with Ampersand.

Most merged pull requests will be published to npm immediately unless we're bundling up a few fixes for releases.

Many small documentation fixes don't justify a release, in which case we'll just merge them to the master branch and leave them there. We'll leave a comment with the version number of the npm release that contains the merged code.

We use the following labels on issues, these will get programmatically applied by a bot to all projects in the AmpersandJS organization on github:

breaking changes: Will change existing behavior, necessistates a major version bump per semver conventions

bug: It's broke, yo.

dependency: Changes/updates a dependency

discussion: Needs discussion or was opened for discussion.

documentation: Improves docs (we love this).

enhancement: Adds feature or improves functionality.

example: Adds example.

help wanted: We'd love help with this one, open for contributions and it's not yet been assigned.

new contributor: This is a good one for a new contributor to tackle. (note to contributors, if triaging and adding this label, please try to add as much detail/instruction as possible to help new contributor be successful).