the-art-of-command-line/CONTRIBUTING.md

## Contributing to The Art of Command Line

This guide is a [collaborative effort](AUTHORS.md), based on the generous work of many contributors.

Contributions of all kinds, including corrections, additions, improvements, and translations, are welcome!

We hope you'll join and help, in small ways or large.
Here are few notes before you jump in.

### Style

- Stay close to the existing style of the document when possible.
- Remember to focus on **brevity**, **specificity**, and **utility**.
- Avoid long explanations and instead prefer links to resources.

### Using issues and PRs

- Please **create and comment on issues freely** to discuss. A lot of the difficulty in accepting PRs is around style and format, and whether changes should be made at all, so rationale or explanations for the change are useful.
- Please **review open issues and pull requests** before submitting a new one, to help reduce duplication.
- To the extent possible, **break up changes into multiple PRs** so they can be approved separately. Large contributions are also welcome, but are harder and slower to approve, as they tend to require discussion or rewriting.


## Translations

The guide is now available in many languages. Here is the process for maintaining translations:

- This original version and content of the guide is maintained in English.
- Translations follow the content of the original. Unfortunately, contributors must speak at least some English, so that translations do not diverge.
- Each translation has a maintainer to update the translation as the original evolves and to review others' changes. This doesn't require a lot of time, but review by the maintainer is important to maintain quality.
- See the [AUTHORS.md](AUTHORS.md) file for current maintainers. (This file is generated from the [authors-info.yml](admin/authors-info.yml) file.)

### Changes to translations

- Changes to content should be made to the English version first, and then translated to each other language.
- Changes that improve translations should be made directly on the file for that language. PRs should only modify one language at a time.
- Submit a PR with changes to the file in that language. Each language has a maintainer, who reviews changes in that language. Then the primary maintainer @jlevy merges it in.
- Prefix PRs and issues with language codes if they are for that translation only, e.g. "es: Improve grammar", so maintainers can find them easily.

### Adding translations to new languages

Translations to new languages are always welcome, especially if you can maintain the translation!

- Check existing issues to see if a translation is in progress or stalled. If so, offer to help.
- If it is not in progress, file an issue for your language so people know you are working on it and we can arrange. Confirm you are native level in the language and are willing to maintain the translation, so it's not orphaned.
- To get it started, fork the repo, then submit a PR with the single file README-xx.md added, where xx is the language code. Use standard [IETF language tags](https://www.w3.org/International/articles/language-tags/), i.e. the same as is used by Wikipedia, *not* the code for a single country. These are usually just the two-letter lowercase code, for example, `fr` for French and `uk` for Ukrainian (not `ua`, which is for the country). For languages that have variations, use the shortest tag, such as `zh-Hant`.
- Invite friends to review if possible. If desired, feel free to invite friends to help your original translation by letting them fork your repo, then merging their PRs.
- Add links to your translation at the top of every README*.md file. (For consistency, the link should be added in alphabetical order by ISO code, and the anchor text should be in the native language.)
- When done, indicate on the PR that it's ready to be merged into the main repo.

### Further questions

Unsure of the process?
Or do you have skills and inclination to help in a more substantial way?
File an issue or e-mail the original author [@jlevy](https://github.com/jlevy).
Add contribution guidelines. 2016-01-07 13:47:15 +08:00			`## Contributing to The Art of Command Line`

More tweaks to contributing guidelines. 2016-01-08 08:24:18 +08:00			`This guide is a [collaborative effort](AUTHORS.md), based on the generous work of many contributors.`
Add contribution guidelines. 2016-01-07 13:47:15 +08:00
			`Contributions of all kinds, including corrections, additions, improvements, and translations, are welcome!`

			`We hope you'll join and help, in small ways or large.`
			`Here are few notes before you jump in.`

			`### Style`

			`- Stay close to the existing style of the document when possible.`
Added bold format to the main concepts of the entire document 2016-01-07 16:30:01 +08:00			`- Remember to focus on brevity, specificity, and utility.`
Add contribution guidelines. 2016-01-07 13:47:15 +08:00			`- Avoid long explanations and instead prefer links to resources.`

			`### Using issues and PRs`

Tweaks to contributing guidelines. 2016-01-07 23:42:47 +08:00			`- Please create and comment on issues freely to discuss. A lot of the difficulty in accepting PRs is around style and format, and whether changes should be made at all, so rationale or explanations for the change are useful.`
			`- Please review open issues and pull requests before submitting a new one, to help reduce duplication.`
			`- To the extent possible, break up changes into multiple PRs so they can be approved separately. Large contributions are also welcome, but are harder and slower to approve, as they tend to require discussion or rewriting.`
Add contribution guidelines. 2016-01-07 13:47:15 +08:00
More tweaks to contributing guidelines. 2016-01-08 08:24:18 +08:00
Add contribution guidelines. 2016-01-07 13:47:15 +08:00			`## Translations`

Note on translations following English version. Follow-up on #336. 2016-01-10 08:42:44 +08:00			`The guide is now available in many languages. Here is the process for maintaining translations:`
Add contribution guidelines. 2016-01-07 13:47:15 +08:00
Note on translations following English version. Follow-up on #336. 2016-01-10 08:42:44 +08:00			`- This original version and content of the guide is maintained in English.`
			`- Translations follow the content of the original. Unfortunately, contributors must speak at least some English, so that translations do not diverge.`
Add contribution guidelines. 2016-01-07 13:47:15 +08:00			`- Each translation has a maintainer to update the translation as the original evolves and to review others' changes. This doesn't require a lot of time, but review by the maintainer is important to maintain quality.`
			`- See the [AUTHORS.md](AUTHORS.md) file for current maintainers. (This file is generated from the [authors-info.yml](admin/authors-info.yml) file.)`

Adding some headers for separate sections (existing and new translations) 2016-01-07 16:27:19 +08:00			`### Changes to translations`
Add contribution guidelines. 2016-01-07 13:47:15 +08:00
			`- Changes to content should be made to the English version first, and then translated to each other language.`
			`- Changes that improve translations should be made directly on the file for that language. PRs should only modify one language at a time.`
			`- Submit a PR with changes to the file in that language. Each language has a maintainer, who reviews changes in that language. Then the primary maintainer @jlevy merges it in.`
			`- Prefix PRs and issues with language codes if they are for that translation only, e.g. "es: Improve grammar", so maintainers can find them easily.`

Adding some headers for separate sections (existing and new translations) 2016-01-07 16:27:19 +08:00			`### Adding translations to new languages`
Add contribution guidelines. 2016-01-07 13:47:15 +08:00
Making the first item in the new translations section a simple message 2016-01-07 16:28:14 +08:00			`Translations to new languages are always welcome, especially if you can maintain the translation!`

Tweaks to contributing guidelines. 2016-01-07 23:42:47 +08:00			`- Check existing issues to see if a translation is in progress or stalled. If so, offer to help.`
			`- If it is not in progress, file an issue for your language so people know you are working on it and we can arrange. Confirm you are native level in the language and are willing to maintain the translation, so it's not orphaned.`
Fix typos 2016-06-14 03:53:28 +08:00			- To get it started, fork the repo, then submit a PR with the single file README-xx.md added, where xx is the language code. Use standard [IETF language tags](https://www.w3.org/International/articles/language-tags/), i.e. the same as is used by Wikipedia, not the code for a single country. These are usually just the two-letter lowercase code, for example, `fr` for French and `uk` for Ukrainian (not `ua`, which is for the country). For languages that have variations, use the shortest tag, such as `zh-Hant`.
Add contribution guidelines. 2016-01-07 13:47:15 +08:00			`- Invite friends to review if possible. If desired, feel free to invite friends to help your original translation by letting them fork your repo, then merging their PRs.`
Tweak contributing guidelines. #336 2016-01-10 09:00:42 +08:00			`- Add links to your translation at the top of every README*.md file. (For consistency, the link should be added in alphabetical order by ISO code, and the anchor text should be in the native language.)`
Add contribution guidelines. 2016-01-07 13:47:15 +08:00			`- When done, indicate on the PR that it's ready to be merged into the main repo.`

More tweaks to contributing guidelines. 2016-01-08 08:24:18 +08:00			`### Further questions`

			`Unsure of the process?`
			`Or do you have skills and inclination to help in a more substantial way?`
			`File an issue or e-mail the original author [@jlevy](https://github.com/jlevy).`