summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2019-10-12 11:20:02 +0000
committerintrigeri <intrigeri@boum.org>2019-10-12 11:38:00 +0000
commit01915911513a5635fe550788faa0cc162d2ba9fc (patch)
treea569f044126a16b15a2ba7d82f5a0b73578d70ab
parent52ec8eb26dd048680a0d792c5782e09c7a97f3e3 (diff)
Move translation platform specs to a subpage of the upcoming design doc (refs: #15086).
-rw-r--r--wiki/src/blueprint/translation_platform.mdwn53
-rw-r--r--wiki/src/contribute/design/translation_platform/specification.mdwn52
2 files changed, 52 insertions, 53 deletions
diff --git a/wiki/src/blueprint/translation_platform.mdwn b/wiki/src/blueprint/translation_platform.mdwn
index 9379c80..35dfa8a 100644
--- a/wiki/src/blueprint/translation_platform.mdwn
+++ b/wiki/src/blueprint/translation_platform.mdwn
@@ -524,56 +524,3 @@ Long-term maintenance plan
This is work in progress. A plan for the future maintenance of our
Weblate instance will be worked on in November 2019 and laid out here
before the end of the year.
-
-Choosing a translation web platform
-===================================
-
-These are the requirements that we have defined for our translation web platform.
-
-MUST
-----
-
-* provide a usable easy web interface
-* be usable from Tor Browser
-* automatic pull from main Git repo
-* provide a common glossary for each language, easy to use and improve
-* allow translators to view, in the correct order, all strings that
- come from the entire page being translated, both in English and in
- the target language
-* make it easy to view the translations in context i.e. when translating
- an entire page, all strings to be translated should only come from
- this page. translators should be able to view the page in context.
-* provide user roles (admin, reviewer, translator)
-
-SHOULD
-------
-
-* be "privacy sensitive", i.e. be operated by a non-profit
-* allow translators to push translations through Git (so that core
- developers only have to fetch reviewed translations from there)
-* provide support for Git standard development branches (devel, stable,
- and testing) but we could also agree upon translation only master
- through this interface
-* provide checks for inconsistent translations
-* provide feature to write/read comments between translators
-
-MAY
----
-
-* allow translating topic branches without confusing translators,
- causing duplicate/premature work, fragmentation or merge conflicts
- -- e.g. present only new or updated strings in topic branches;
- see <https://mailman.boum.org/pipermail/tails-l10n/2015-March/002102.html>
- for details
-* provide a feature to easily see what is new, what needs updating, what are translation priorities
-* provide possibility to set up new languages easily
-* send email notifications
- - to reviewers whenever new strings have been translated or updated
- - to translators whenever a resource is updated
-* respect authorship (different committers?)
-* provide statistics about the percentage of translated and fuzzy strings
-* Letting translators report about problems in original strings, e.g.
- with a "Report a problem in the original English text" link, that
- e.g. results in an email being sent to -l10n@ or -support-private@.
- If we don't have that, then [[contribute/how/translate]] MUST
- document how to report issues in the original English text.
diff --git a/wiki/src/contribute/design/translation_platform/specification.mdwn b/wiki/src/contribute/design/translation_platform/specification.mdwn
new file mode 100644
index 0000000..c8fa479
--- /dev/null
+++ b/wiki/src/contribute/design/translation_platform/specification.mdwn
@@ -0,0 +1,52 @@
+[[!meta title="Choosing a translation web platform"]]
+
+These are the requirements that we have defined for our translation web platform
+before we started working on it.
+
+MUST
+====
+
+* provide a usable easy web interface
+* be usable from Tor Browser
+* automatic pull from main Git repo
+* provide a common glossary for each language, easy to use and improve
+* allow translators to view, in the correct order, all strings that
+ come from the entire page being translated, both in English and in
+ the target language
+* make it easy to view the translations in context i.e. when translating
+ an entire page, all strings to be translated should only come from
+ this page. translators should be able to view the page in context.
+* provide user roles (admin, reviewer, translator)
+
+SHOULD
+======
+
+* be "privacy sensitive", i.e. be operated by a non-profit
+* allow translators to push translations through Git (so that core
+ developers only have to fetch reviewed translations from there)
+* provide support for Git standard development branches (devel, stable,
+ and testing) but we could also agree upon translation only master
+ through this interface
+* provide checks for inconsistent translations
+* provide feature to write/read comments between translators
+
+MAY
+===
+
+* allow translating topic branches without confusing translators,
+ causing duplicate/premature work, fragmentation or merge conflicts
+ -- e.g. present only new or updated strings in topic branches;
+ see <https://mailman.boum.org/pipermail/tails-l10n/2015-March/002102.html>
+ for details
+* provide a feature to easily see what is new, what needs updating, what are translation priorities
+* provide possibility to set up new languages easily
+* send email notifications
+ - to reviewers whenever new strings have been translated or updated
+ - to translators whenever a resource is updated
+* respect authorship (different committers?)
+* provide statistics about the percentage of translated and fuzzy strings
+* Letting translators report about problems in original strings, e.g.
+ with a "Report a problem in the original English text" link, that
+ e.g. results in an email being sent to -l10n@ or -support-private@.
+ If we don't have that, then [[contribute/how/translate]] MUST
+ document how to report issues in the original English text.