Add discussion template for new language translation requests

diff --git a/.github/DISCUSSION_TEMPLATE/translations.yml b/.github/DISCUSSION_TEMPLATE/translations.yml
new file mode 100644 (file)
index 0000000..52d86a5
--- /dev/null
+++ b/.github/DISCUSSION_TEMPLATE/translations.yml
@@ -0,0 +1,65 @@
+labels: [lang-all]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for your interest in help translating FastAPI! 🌍
+
+        Please follow these instructions carefully to propose a new language translation. 🙏
+
+        This structured process helps ensure translations can be properly maintained long-term.
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Initial Checks
+      description: Please confirm and check all the following options.
+      options:
+        - label: I checked that this language is not already being translated in FastAPI docs.
+          required: true
+        - label: I searched existing discussions to ensure no one else proposed this language.
+          required: true
+        - label: I am a native speaker of the language I want to translate to.
+          required: true
+        - label: I understand I need to wait for maintainer approval before starting.
+          required: true
+  - type: input
+    id: language
+    attributes:
+      label: Target Language
+      description: What language do you want to translate FastAPI docs into?
+      placeholder: e.g. Latin
+    validations:
+      required: true
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Motivation
+      description: |
+        Please explain:
+        1. Why you want to add this language
+        2. How you plan to maintain it long-term
+      placeholder: |
+        I want to add Latin translation because...
+        My plan for maintaining it is...
+    validations:
+      required: true
+  - type: textarea
+    id: contributors
+    attributes:
+      label: Community Support
+      description: |
+        You need at least 2 other native speakers to help with translations.
+        Ask them to comment on this discussion expressing their commitment.
+        
+        List their GitHub usernames below once they've commented.
+      placeholder: |
+        The following native speakers have committed to help:
+        - @username1
+        - @username2
+    validations:
+      required: true
+  - type: textarea
+    id: additional_info
+    attributes:
+      label: Additional Information
+      description: Any other relevant information about your translation proposal
\ No newline at end of file

diff --git a/docs/en/docs/contributing.md b/docs/en/docs/contributing.md
index 1b70a0ea93d6604aaffe8e1b134f9bd93b4603d6..06b26cf92bee97eca7c297dddf641d87b8f42407 100644 (file)
--- a/docs/en/docs/contributing.md
+++ b/docs/en/docs/contributing.md
@@ -293,30 +293,53 @@ Now you can translate it all and see how it looks as you save the file.
 
 Some of these files are updated very frequently and a translation would always be behind, or they include the main content from English source files, etc.
 
-#### New Language
+### Request a New Language
+
+Let's say that you want to add translations for a language that is not yet translated, not even some pages. For example, Latin.
+
+If there is no discussion for that language, you can start by requesting the new language. For that, you can follow these steps:
+
+1. Create a new discussion following the template.
+
+2. In the discussion, explain why you want to add the new language, what you plan to do, and how you plan to maintain it.
+
+3. Show community interest by:
+   * Getting at least 2 other native speakers to comment on the discussion expressing interest in helping with translations.
 
-Let's say that you want to add translations for a language that is not yet translated, not even some pages.
+**Important**: Wait for maintainer approval before starting any translation work.
+
+Approval typically requires:
+
+* Meeting the minimum number of interested contributors.
+* A clear plan for maintaining the translations.
+* Agreement from existing maintainers.
+
+This will help to prevent duplicate translation efforts, build a collaborative translation community, and ensure that the translations are maintained over time.
+
+Once your language request is approved, you can proceed with creating translations as described below.
+
+#### New Language
 
-Let's say you want to add translations for Creole, and it's not yet there in the docs.
+Once you have the approval to start a new language, you can proceed. First, you need to know the 2-letter code for the language you want to translate.
 
-Checking the link from above, the code for "Creole" is `ht`.
+Checking the link from above (List of ISO 639-1 codes), you can see that the 2-letter code for Latin is `la`.
 
-The next step is to run the script to generate a new translation directory:
+Now you can create a new directory for the new language, running the following script:
 
 <div class="termy">
 
 ```console
 // Use the command new-lang, pass the language code as a CLI argument
-$ python ./scripts/docs.py new-lang ht
+$ python ./scripts/docs.py new-lang la
 
-Successfully initialized: docs/ht
+Successfully initialized: docs/la
 ```
 
 </div>
 
-Now you can check in your code editor the newly created directory `docs/ht/`.
+Now you can check in your code editor the newly created directory `docs/la/`.
 
-That command created a file `docs/ht/mkdocs.yml` with a simple config that inherits everything from the `en` version:
+That command created a file `docs/la/mkdocs.yml` with a simple config that inherits everything from the `en` version:
 
 ```yaml
 INHERIT: ../en/mkdocs.yml
@@ -328,11 +351,11 @@ You could also simply create that file with those contents manually.
 
 ///
 
-That command also created a dummy file `docs/ht/index.md` for the main page, you can start by translating that one.
+That command also created a dummy file `docs/la/index.md` for the main page, you can start by translating that one.
 
 You can continue with the previous instructions for an "Existing Language" for that process.
 
-You can make the first pull request with those two files, `docs/ht/mkdocs.yml` and `docs/ht/index.md`. 🎉
+You can make the first pull request with those two files, `docs/la/mkdocs.yml` and `docs/la/index.md`. 🎉
 
 #### Preview the result