From 4638c8b95edafb25f527ac8418d2b4d9a722f130 Mon Sep 17 00:00:00 2001 From: francescomalatesta Date: Thu, 7 Jan 2016 09:27:19 +0100 Subject: [PATCH 1/4] Adding some headers for separate sections (existing and new translations) --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f7a45ef..60e4ff3 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -27,14 +27,14 @@ Maintaining the guide in several languages is a little confusing, so here is the - 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 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: +### Adding translations to new languages - Translations to new languages are always welcome, especially if you can maintain the translation! - If there is not an issue for your language, file one 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. From fc022b584a3d32abd09e7897c2b89ef207905bc5 Mon Sep 17 00:00:00 2001 From: francescomalatesta Date: Thu, 7 Jan 2016 09:28:14 +0100 Subject: [PATCH 2/4] Making the first item in the new translations section a simple message --- CONTRIBUTING.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 60e4ff3..e897de4 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -36,7 +36,8 @@ Maintaining the guide in several languages is a little confusing, so here is the ### Adding translations to new languages -- Translations to new languages are always welcome, especially if you can maintain the translation! +Translations to new languages are always welcome, especially if you can maintain the translation! + - If there is not an issue for your language, file one 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. - If the translation is in progress but stalled, offer to help. - To get it started, fork the repo, then submit a PR with the single file README-xx.md added, where xx is the lowercase language code. (Use standard two-letter ISO language codes, i.e. the same as is used by Wikipedia, not the code for a single country.) From 8d48e44ce3bdb32e19a3f7df96e26d96b589bf17 Mon Sep 17 00:00:00 2001 From: francescomalatesta Date: Thu, 7 Jan 2016 09:28:47 +0100 Subject: [PATCH 3/4] Moving up the getting started item in the new translations setction --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e897de4..3cf9ae0 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -38,9 +38,9 @@ Maintaining the guide in several languages is a little confusing, so here is the Translations to new languages are always welcome, especially if you can maintain the translation! +- To get it started, fork the repo, then submit a PR with the single file README-xx.md added, where xx is the lowercase language code. (Use standard two-letter ISO language codes, i.e. the same as is used by Wikipedia, not the code for a single country.) - If there is not an issue for your language, file one 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. - If the translation is in progress but stalled, offer to help. -- To get it started, fork the repo, then submit a PR with the single file README-xx.md added, where xx is the lowercase language code. (Use standard two-letter ISO language codes, i.e. the same as is used by Wikipedia, not the code for a single country.) - 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. - When done, indicate on the PR that it's ready to be merged into the main repo. From 5dbe213e3ed814feda53520119466a17a2eeea79 Mon Sep 17 00:00:00 2001 From: francescomalatesta Date: Thu, 7 Jan 2016 09:30:01 +0100 Subject: [PATCH 4/4] Added bold format to the main concepts of the entire document --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3cf9ae0..8b8b27c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -10,7 +10,7 @@ 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. +- Remember to focus on **brevity**, **specificity**, and **utility**. - Avoid long explanations and instead prefer links to resources. ### Using issues and PRs