silverstripe-framework/docs/en/misc/contributing/index.md

# Contributing

Any open source product is only as good as the community behind it. You can
participate by sharing  code, ideas, or simply helping others. No matter what
your skill level is, every contribution counts.

See our [high level overview on silverstripe.org](http://silverstripe.org/contributing-to-silverstripe)
on how you can help out.

Or, for more detailed guidance, read one of the following pages:

 * [Sharing your **opinion** and raising **issues**](issues)
 * [Providing **code**, whether it's creating a feature or fixing a bug](code)
 * [Writing and translating **documentation**](documentation)
 * [**Translating** user-interface elements](translation)

## House rules for everybody contributing to SilverStripe
 * Ask questions on the [forum](http://silverstripe.org/forum), and stick to more high-level discussions on the [core mailinglist](https://groups.google.com/forum/#!forum/silverstripe-dev)
 * Make sure you know how to [raise good bug reports](/misc/contributing/issues)
 * Everybody can contribute to SilverStripe! If you do, ensure you can [submit solid pull requests](/misc/contributing/code)
Broke up contributing docs into 4 sections and unified code contribtion guide. The guidelines for contributing code were scattered across a section of contributing.md and collaboration-on-git.md. I've updated this to have separate contributing/code.md page with all the content in a single cohesive page. We also have contributing/documentation.md, contributing/issues.md and contributing/translation.md. 2012-10-09 01:32:22 +02:00			`# Contributing`

Update module development, remove outdated release steps 2013-06-15 02:05:40 +02:00			`Any open source product is only as good as the community behind it. You can`
			`participate by sharing code, ideas, or simply helping others. No matter what`
			`your skill level is, every contribution counts.`
Broke up contributing docs into 4 sections and unified code contribtion guide. The guidelines for contributing code were scattered across a section of contributing.md and collaboration-on-git.md. I've updated this to have separate contributing/code.md page with all the content in a single cohesive page. We also have contributing/documentation.md, contributing/issues.md and contributing/translation.md. 2012-10-09 01:32:22 +02:00
Update module development, remove outdated release steps 2013-06-15 02:05:40 +02:00			`See our [high level overview on silverstripe.org](http://silverstripe.org/contributing-to-silverstripe)`
			`on how you can help out.`
Broke up contributing docs into 4 sections and unified code contribtion guide. The guidelines for contributing code were scattered across a section of contributing.md and collaboration-on-git.md. I've updated this to have separate contributing/code.md page with all the content in a single cohesive page. We also have contributing/documentation.md, contributing/issues.md and contributing/translation.md. 2012-10-09 01:32:22 +02:00
			`Or, for more detailed guidance, read one of the following pages:`

			`* [Sharing your opinion and raising issues](issues)`
			`* [Providing code, whether it's creating a feature or fixing a bug](code)`
			`* [Writing and translating documentation](documentation)`
			`* [Translating user-interface elements](translation)`

DOCS Repositioned house rules and added core commiter list. 2014-11-21 00:05:21 +01:00			`## House rules for everybody contributing to SilverStripe`
			`* Ask questions on the [forum](http://silverstripe.org/forum), and stick to more high-level discussions on the [core mailinglist](https://groups.google.com/forum/#!forum/silverstripe-dev)`
			`* Make sure you know how to [raise good bug reports](/misc/contributing/issues)`
			`* Everybody can contribute to SilverStripe! If you do, ensure you can [submit solid pull requests](/misc/contributing/code)`