[taler-docs] branch master updated (74109cd -> 0c0a865)

[gnunet]

This is an automated email from the git hooks/post-receive script.

buck pushed a change to branch master
in repository docs.

    from 74109cd  layer->facade
     new 4b34f9a  adding to Internationalization
     new 0c0a865  adding to Internationalization

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 developers-manual.rst | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/developers-manual.rst b/developers-manual.rst
index cef2095..ba5d69b 100644
--- a/developers-manual.rst
+++ b/developers-manual.rst
@@ -629,18 +629,25 @@ The *GNU Taler* project is probably the correct project 
for most Components and
 How to Create a Component
 -------------------------
 
+Reference: 
https://docs.weblate.org/en/weblate-4.0.3/admin/projects.html#component-configuration
+
 In Weblate, a *Component* is a subset of a *Project* and each Component 
contains N translations.  A Component is generally associated with a Git repo.
 
 To create a Component, log into https://weblate.taler.net/ with your *Manager* 
or higher credentials and choose **+ Add* from the upper-right corner.
 
 What follows is a sort of Wizard.  You can find detailed docs at 
https://docs.weblate.org/.  Here are some important notes about connecting your 
Component to the Taler Git repository:
 
+Under *https://weblate.taler.net/create/component/vcs/*:
+
 * **Source code repository** - Generally 
`git+ssh://address@hidden/<reponame>`.  Check with `git remote -v`.
 * **Repository branch ** - Choose the correct branch to draw from and commit 
to.
 * **Repository push URL** - This is generally 
`git+ssh://address@hidden/<reponame>`  Check with `git remote -v`.
-* **Repository browser** - This is the www URL of the Git repo's file browser. 
 Example `https://git.taler.net/<repo>.git/tree/{{filename}}#L{{line}}`
+* **Repository browser** - This is the www URL of the Git repo's file browser. 
 Example 
`https://git.taler.net/<repositoryname>.git/tree/{{filename}}?h={{branch}}#n{{line}}`
 * **Merge style ** - *Rebase*, in line with GNU Taler development procedures
 
+* **Translation license** - *GNU General Public License v3.0 or Later*
+* **Adding new translation** - Decide how to handle adding new translations
+
 How to Create a Translation
 ---------------------------
 
@@ -661,10 +668,11 @@ You may also wish to refer to 
``https://docs.weblate.org/``.
 Translation Standards and Practices
 -----------------------------------
 
-By default, our Weblate instance is set to accept translations in English, 
French, German, Italian, Russian, Spanish, and Portuguese.
+By default, our Weblate instance is set to accept translations in English, 
French, German, Italian, Russian, Spanish, and Portuguese.  If you want to 
contribute a translation in a different language, navigate to the *Component* 
you want to translate for, and click "Start new translation" to begin.  If you 
require a privilege upgrade, please contact a superuser with your request.
 
-If you want to contribute a translation in a different language, navigate to 
the *Component* you want to translate for, and click "Start new translation" to 
begin.  If you require a privilege upgrade, please contact a superuser with 
your request.
+When asked, set the license to GPLv3 or later.
 
+Set commit/push to manual only.
 
 GPG Signing of Translations
 ---------------------------

-- 
To stop receiving notification emails like this one, please contact
address@hidden.