From 58aa023b3e190b8e3694fae7a7045aed8182b900 Mon Sep 17 00:00:00 2001 From: Yangshun Tay Date: Sat, 24 Mar 2018 12:10:03 -0700 Subject: [PATCH] Update contributing guidlines for translations --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f74334028..f3745d32b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -14,7 +14,7 @@ As much as possible, try to follow the existing format of markdown and code. Any ### Translations -Feel free to add translations for the questions and answers only. You might want to retrieve a translated copy of the questions from [the original repository] and start from there. Simply create an issue expressing interest in being a translator and you will be added to the repository. Translators have the responsibility of keeping the translated content up to date with the master copy. However, the `master` branch is protected from direct writes and translated work have to go through the Pull Request and review process before it can be merged into the repository. This is more for organizational purposes as different translators tend to have individual collaboration approach (some prefer merging, some prefer rebasing). Going through a Pull Request process will make the commit history more organized and clean. +Feel free to add translations for the questions and answers only. You might want to retrieve a translated copy of the questions from [the original repository](https://github.com/h5bp/Front-end-Developer-Interview-Questions) and start from there. Simply create an issue expressing interest in being a translator and you can fork the repository and start translating. Translators have the responsibility of keeping the translated content up to date with the master copy. Translated work has to go through the Pull Request and review process before it can be merged into the repository. This is more for organizational purposes as different translators tend to have individual collaboration approach (some prefer merging, some prefer rebasing). Going through a Pull Request process will make the commit history more organized and clean. ### Code of Conduct