SpaceVim/CONTRIBUTING.md

# Contributing to SpaceVim

SpaceVim is an volunteer effort; we encourage you to pitch in. The community makes SpaceVim what it is.
We have a few guidelines, which we ask all contributors to follow.

You need only consider reading the sections relevant to what you are going to do:

- [Asking for help](#asking-for-help) if you are about to open an issue to ask a question.
- [Reporting issues](#reporting-issues) if you are about to open a new issue.
- [Contributing code](#contributing-code) if you are about to send a Pull Request (PR).

### Asking for help

If you want to ask an usage question, be sure to look first into some places as it may hold the answers:
- <kbd>:h SpaceVim-faq</kbd>: Some of the most frequently asked questions are answered there.
- [SpaceVim documentation](https://spacevim.org/documentation): It is the general documentation of SpaceVim.

### Reporting issues

Issues have to be reported on [issues tracker](https://github.com/SpaceVim/SpaceVim/issues), Please:


- Check the **[FAQ](https://github.com/SpaceVim/SpaceVim/wiki/FAQ)**.
- Search existing issues (including closed!)
- Update SpaceVim to the latest version to see if your problem persists.
- Use a clear title and follow the issue template.
- Include step by step details on how to reproduce it.

### Contributing code

Code contributions are welcome. Please read the following sections carefully. In any case, feel free to join us on the [gitter chat](https://gitter.im/SpaceVim/SpaceVim) to ask questions about contributing!

#### License

The license is GPLv3 for all the parts of SpaceVim. this includes:

- The initialization and core files.
- All the layer files.
- The documentation

For files not belonging to SpaceVim, such as local packages and libraries, refer to the header file. Those files should not have an empty header. We may not accept code without a proper header file.

#### Conventions

SpaceVim is based on conventions, mainly for naming functions, keybindings definition and writing documentation. Please read the [conventions](https://spacevim.org/conventions/) before your first contribution to get to know them.

#### Pull Request

Submit your contribution against the `master` branch. You should not use your master branch to modify SpaceVim, this branch is considered to be read-only.

You may want to read our [development guidelines](https://spacevim.org/development/).
Remove content from contrubuting to website 2018-01-21 12:17:59 +08:00			`# Contributing to SpaceVim`
Async with development.md 2017-06-20 20:50:43 +08:00
Edits: Minor spelling and grammar edits 2017-10-09 05:43:24 +08:00			`SpaceVim is an volunteer effort; we encourage you to pitch in. The community makes SpaceVim what it is.`
Async with development.md 2017-06-20 20:50:43 +08:00			`We have a few guidelines, which we ask all contributors to follow.`

Edits: Minor spelling and grammar edits 2017-10-09 05:43:24 +08:00			`You need only consider reading the sections relevant to what you are going to do:`
Async with development.md 2017-06-20 20:50:43 +08:00
			`- [Asking for help](#asking-for-help) if you are about to open an issue to ask a question.`
			`- [Reporting issues](#reporting-issues) if you are about to open a new issue.`
Edits: Minor spelling and grammar edits 2017-10-09 05:43:24 +08:00			`- [Contributing code](#contributing-code) if you are about to send a Pull Request (PR).`
Async with development.md 2017-06-20 20:50:43 +08:00
			`### Asking for help`

			`If you want to ask an usage question, be sure to look first into some places as it may hold the answers:`
			`- <kbd>:h SpaceVim-faq</kbd>: Some of the most frequently asked questions are answered there.`
			`- [SpaceVim documentation](https://spacevim.org/documentation): It is the general documentation of SpaceVim.`

			`### Reporting issues`

Edits: Minor spelling and grammar edits 2017-10-09 05:43:24 +08:00			`Issues have to be reported on [issues tracker](https://github.com/SpaceVim/SpaceVim/issues), Please:`
Remove content from contrubuting to website 2018-01-21 12:17:59 +08:00

			`- Check the [FAQ](https://github.com/SpaceVim/SpaceVim/wiki/FAQ).`
			`- Search existing issues (including closed!)`
			`- Update SpaceVim to the latest version to see if your problem persists.`
Async with development.md 2017-06-20 20:50:43 +08:00			`- Use a clear title and follow the issue template.`
Edits: Minor spelling and grammar edits 2017-10-09 05:43:24 +08:00			`- Include step by step details on how to reproduce it.`
Async with development.md 2017-06-20 20:50:43 +08:00
			`### Contributing code`

			`Code contributions are welcome. Please read the following sections carefully. In any case, feel free to join us on the [gitter chat](https://gitter.im/SpaceVim/SpaceVim) to ask questions about contributing!`

			`#### License`

Relicense (#1406) 2018-02-15 22:25:03 +08:00			`The license is GPLv3 for all the parts of SpaceVim. this includes:`

Edits: Minor spelling and grammar edits 2017-10-09 05:43:24 +08:00			`- The initialization and core files.`
Async with development.md 2017-06-20 20:50:43 +08:00			`- All the layer files.`
Relicense (#1406) 2018-02-15 22:25:03 +08:00			`- The documentation`
Async with development.md 2017-06-20 20:50:43 +08:00
Remove content from contrubuting to website 2018-01-21 12:17:59 +08:00			`For files not belonging to SpaceVim, such as local packages and libraries, refer to the header file. Those files should not have an empty header. We may not accept code without a proper header file.`
Async with development.md 2017-06-20 20:50:43 +08:00
			`#### Conventions`

Remove content from contrubuting to website 2018-01-21 12:17:59 +08:00			`SpaceVim is based on conventions, mainly for naming functions, keybindings definition and writing documentation. Please read the [conventions](https://spacevim.org/conventions/) before your first contribution to get to know them.`
Async with development.md 2017-06-20 20:50:43 +08:00
			`#### Pull Request`

Remove content from contrubuting to website 2018-01-21 12:17:59 +08:00			Submit your contribution against the `master` branch. You should not use your master branch to modify SpaceVim, this branch is considered to be read-only.
Async with development.md 2017-06-20 20:50:43 +08:00
Update wiki 2018-01-21 12:47:42 +08:00			`You may want to read our [development guidelines](https://spacevim.org/development/).`
Async with development.md 2017-06-20 20:50:43 +08:00