Skip to content
Permalink
Browse files

chore(CONTRIBUTING.md): Move instructions to documentation

  • Loading branch information...
Betree committed Mar 29, 2019
1 parent 4761e82 commit a56b1b54ab6adf9a497dc50dd94ea3778ef78af7
Showing with 1 addition and 39 deletions.
  1. +1 −39 CONTRIBUTING.md
@@ -1,39 +1 @@
OpenCollective is an open source project and we love to receive contributions from our community — you!

# Introduction

First, thank you for considering contributing to OpenCollective! It's people like you that make OpenCollective such a great community.

We welcome any type of contribution, not only code. You can help with

- **QA**: file bug reports, the more details you can give the better (e.g. screenshots with the console open)
- **Documentation**: suggest edits to [our wiki](http://docs.opencollective.com/)
- **Marketing**: writing blog posts, use cases, sharing success stories.
- **Internationalization**: [translating the interface](https://github.com/opencollective/opencollective-frontend/tree/master/src/lang)
- **Design**: many collectives don't have a logo or a background image for their hero. Create an issue for it and submit your proposal. We always give credit where credit is due.
- **Code**: there are plenty of [open issues](https://github.com/OpenCollective/OpenCollective/issues). Even if you can't write code, commenting on them, showing that you care about a given issue matters. It helps us triage them.

# Your First Contribution

Unsure where to begin contributing to OpenCollective? You can start by looking through the
[good first issues](https://github.com/opencollective/opencollective/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) - issues which should only require a few lines of code, and a test or two.

Working on your first Pull Request? You can learn how from this _free_ series, [How to Contribute to an Open Source Project on GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github).

# Submitting code

Any code change should be submitted as a pull request. The description should explain what the code does and give steps to execute it. The pull request should also contain tests.

# Code review process

The bigger the pull request, the longer it will take to review and merge. Try to break down large pull requests in smaller chunks that are easier to review and merge.

If it's a bug fix, it will probably be quickly merged and deployed. If it's a new feature, we will probably ask to limit it to your own collective as a start to see how it goes before releasing it to all other collectives.

# Questions

If you have any questions, reach out to us on [Slack](https://slack.opencollective.com).

# Credits

This `CONTRIBUTING.md` is based on @nayafia's template https://github.com/nayafia/contributing-template
# See how you can contribute in [our documentation](https://docs.opencollective.com/help/about/contributing)

0 comments on commit a56b1b5

Please sign in to comment.
You can’t perform that action at this time.