From 615284f6d407c6c92feae5bc51b7f65c2e628d1c Mon Sep 17 00:00:00 2001 From: apiraino Date: Wed, 3 Jun 2026 12:51:08 +0200 Subject: [PATCH 1/2] Add clause to etiquette about using English --- src/how-to-start-contributing.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/how-to-start-contributing.md b/src/how-to-start-contributing.md index 599120260..eb0516b96 100644 --- a/src/how-to-start-contributing.md +++ b/src/how-to-start-contributing.md @@ -128,6 +128,7 @@ To achieve this goal, we want to build trust and respect of each other's time an - If you want to fix an issue but have doubts about the design, you're welcome to join our [Zulip][rust-zulip] server and ask for tips - Please respect the reviewers' time: allow some days between reviews, only ask for reviews when your code compiles and tests pass, or give an explanation for why you are asking for a review at that stage (you can keep them in draft state until they're ready for review) - Try to keep comments concise, don't worry about a perfect written communication. Strive for clarity and being to the point +- We prefer using the English language to follow conventions of existing commits. Again, don't worry about writing a perfect prose [^1]: Free-Open Source Project, see: https://en.wikipedia.org/wiki/Free_and_open-source_software From 3faa350c7fac023c3b5fc5318aec0ec806155df2 Mon Sep 17 00:00:00 2001 From: apiraino Date: Wed, 3 Jun 2026 17:26:38 +0200 Subject: [PATCH 2/2] second-try --- src/how-to-start-contributing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/how-to-start-contributing.md b/src/how-to-start-contributing.md index eb0516b96..e49e01d92 100644 --- a/src/how-to-start-contributing.md +++ b/src/how-to-start-contributing.md @@ -128,7 +128,7 @@ To achieve this goal, we want to build trust and respect of each other's time an - If you want to fix an issue but have doubts about the design, you're welcome to join our [Zulip][rust-zulip] server and ask for tips - Please respect the reviewers' time: allow some days between reviews, only ask for reviews when your code compiles and tests pass, or give an explanation for why you are asking for a review at that stage (you can keep them in draft state until they're ready for review) - Try to keep comments concise, don't worry about a perfect written communication. Strive for clarity and being to the point -- We prefer using the English language to follow conventions of existing commits. Again, don't worry about writing a perfect prose +- Please use English to communicate (including e.g. commit messages) for consistency with the communication in our project (English is the accepted common language in our project). The grammar or prose does not need to be perfect at all! [^1]: Free-Open Source Project, see: https://en.wikipedia.org/wiki/Free_and_open-source_software