Lx&R: Marked this version for translation

2019-05-08T02:11:31Z

Marked this version for translation

Lx&R: Created page with " {{reqbox who-know-english}} ==Protocol== The main page with a list of tasks is {{#plang:Project:Project tasks}..."

2019-05-07T23:19:26Z

Created page with "<languages /> {{reqbox who-know-english}} ==<translate>Protocol</translate>== <translate> The main page with a list of tasks is</translate> {{#plang:Project:Project tasks}..."

New page

<languages />

{{reqbox who-know-english}}
==<translate>Protocol</translate>==

<translate>
The main page with a list of tasks is</translate> [[{{#plang:Project:Project tasks}}|<translate>Project tasks</translate>]].

<translate>
Tasks in the task list are arranged, if possible, in order of priority. Top priority at the top. The solved tasks are transferred to the [[{{#plang:Project:Project tasks solved}}|Project tasks solved]] list in chronological order.

The name of the task has the prefix "Project:Task-NNN ", where NNN is a sequence number in the general task list, starting with 001. The name should reflect the essence of the task as accurately as possible. The name of the task implies the creation of a page for it with this name, therefore it obeys the rules for the names of the pages.

When creating a page in another language (non-English), after the prefix "Project:Task-NNN ", the language prefix should follow that obeys the language policy. For example, the prefixes for the main languages are:</translate>

:* francaise - 'Project:Task-NNN Fr! "
:* deutsch - "Project:Task-NNN De! "
:* русский - "Project:Task-NNN Ru! "

<translate>
If a task name is created in another language (non-English), the translator must translate it into English, create an English redirect page to the original page, and replace the non-English name with an English name in the task list.

Tasks have 4 states in the task list:</translate>

:* <translate>Plain text - it is new task, no one has chosen yet.</translate>
:* <translate>Green tag - the task is taken into development.</translate>
:* <translate>Violet tag - the task is temporarily postponed.</translate>
:* <translate>Red tag - the task is stopped due to a problem.</translate>

<translate>
Stages of creating and solving the task:</translate>

# <translate>A new task is formulated in plain text.</translate>
# <translate>A task name and a page for it are created.</translate>
# <translate>Someone from the project stuff undertakes to solve it.</translate>
# <translate>The task is solved, transferred to the page of solved tasks.</translate>

<translate>
Task may be delayed, stopped due to a problem, canceled, resumed.

When the name of the task is created, then in the task list the task statement should begin with the name of the task with link to the task page. The name of the task should be followed by a brief explanation, clarification of the essence in plain text.

Any project member can choose a task. To do this, he creates a page with the name in his own language, and inserts his signature at the top of the page using <nowiki>"~~~~"</nowiki>. If the name is non-English, then the project member himself (or the translator) creates an English name - redirection to the task page. The name of the page (if there is no English, then non-English) should be inserted at the beginning of the statement of the task.

If necessary, the task page should be prepared for translation using [[Special:PagePreparation]], and then “{{int:translate-tag-markthis}}”</translate>

==<translate>Task page content</translate>==

<translate>
Task page should contain:</translate>

:* <translate>Names of members involved in its solution.</translate>
:* <translate>Main steps.</translate>
:* <translate>Current state — the status category.</translate>

==<translate>Status Categories</translate>==

<translate>
Task status categories:</translate>

:* TaskBegan (<translate>Work is started</translate>)
:* Task-25% (<translate>Resolved by 25%</translate>)
:* Task-50% (<translate>Resolved by 50%</translate>)
:* Task-75% (<translate>Resolved by 75%</translate>)
:* TaskAtEnd (<translate>The work comes to an end</translate>)
:* TaskSolved (<translate>Task is solved</translate>)

<translate>
Assignment of intermediate categories is important only for long-term tasks, so that project staff understand their condition.
</translate>

@@ Line 2: / Line 2: @@
 {{reqbox who-know-english}}
-==<translate>Protocol</translate>==
+==<translate><!--T:1--> Protocol</translate>==
 <translate>
-The main page with a list of tasks is</translate> [[{{#plang:Project:Project tasks}}|<translate>Project tasks</translate>]].
+<!--T:2-->
 <translate>
 Tasks in the task list are arranged, if possible, in order of priority. Top priority at the top. The solved tasks are transferred to the [[{{#plang:Project:Project tasks solved}}|Project tasks solved]] list in chronological order.
 The name of the task has the prefix "Project:Task-NNN ", where NNN is a sequence number in the general task list, starting with 001. The name should reflect the essence of the task as accurately as possible. The name of the task implies the creation of a page for it with this name, therefore it obeys the rules for the names of the pages.
 When creating a page in another language (non-English), after the prefix "Project:Task-NNN ", the language prefix should follow that obeys the language policy. For example, the prefixes for the main languages are:</translate>
@@ Line 19: / Line 23: @@
 <translate>
 If a task name is created in another language (non-English), the translator must translate it into English, create an English redirect page to the original page, and replace the non-English name with an English name in the task list.
 Tasks have 4 states in the task list:</translate>
-:* <translate>Plain text - it is new task, no one has chosen yet.</translate>
+:* <translate><!--T:9--> Plain text - it is new task, no one has chosen yet.</translate>
-:* <translate>Green tag - the task is taken into development.</translate>
+:* <translate><!--T:10--> Green tag - the task is taken into development.</translate>
-:* <translate>Violet tag - the task is temporarily postponed.</translate>
+:* <translate><!--T:11--> Violet tag - the task is temporarily postponed.</translate>
-:* <translate>Red tag - the task is stopped due to a problem.</translate>
+:* <translate><!--T:12--> Red tag - the task is stopped due to a problem.</translate>
 <translate>
 Stages of creating and solving the task:</translate>
-# <translate>A new task is formulated in plain text.</translate>
+# <translate><!--T:14--> A new task is formulated in plain text.</translate>
-# <translate>A task name and a page for it are created.</translate>
+# <translate><!--T:15--> A task name and a page for it are created.</translate>
-# <translate>Someone from the project stuff undertakes to solve it.</translate>
+# <translate><!--T:16--> Someone from the project stuff undertakes to solve it.</translate>
-# <translate>The task is solved, transferred to the page of solved tasks.</translate>
+# <translate><!--T:17--> The task is solved, transferred to the page of solved tasks.</translate>
 <translate>
 Task may be delayed, stopped due to a problem, canceled, resumed.
 When the name of the task is created, then in the task list the task statement should begin with the name of the task with link to the task page. The name of the task should be followed by a brief explanation, clarification of the essence in plain text.
 Any project member can choose a task. To do this, he creates a page with the name in his own language, and inserts his signature at the top of the page using <nowiki>"~~~~"</nowiki>. If the name is non-English, then the project member himself (or the translator) creates an English name - redirection to the task page. The name of the page (if there is no English, then non-English) should be inserted at the beginning of the statement of the task.
 If necessary, the task page should be prepared for translation using [[Special:PagePreparation]], and then “{{int:translate-tag-markthis}}”</translate>
-==<translate>Task page content</translate>==
+==<translate><!--T:22--> Task page content</translate>==
 <translate>
 Task page should contain:</translate>
-:* <translate>Names of members involved in its solution.</translate>
+:* <translate><!--T:24--> Names of members involved in its solution.</translate>
-:* <translate>Main steps.</translate>
+:* <translate><!--T:25--> Main steps.</translate>
-:* <translate>Current state — the status category.</translate>
+:* <translate><!--T:26--> Current state — the status category.</translate>
-==<translate>Status Categories</translate>==
+==<translate><!--T:27--> Status Categories</translate>==
 <translate>
 Task status categories:</translate>
-:* TaskBegan (<translate>Work is started</translate>)
+:* TaskBegan (<translate><!--T:29--> Work is started</translate>)
-:* Task-25% (<translate>Resolved by 25%</translate>)
+:* Task-25% (<translate><!--T:30--> Resolved by 25%</translate>)
-:* Task-50% (<translate>Resolved by 50%</translate>)
+:* Task-50% (<translate><!--T:31--> Resolved by 50%</translate>)
-:* Task-75% (<translate>Resolved by 75%</translate>)
+:* Task-75% (<translate><!--T:32--> Resolved by 75%</translate>)
-:* TaskAtEnd (<translate>The work comes to an end</translate>)
+:* TaskAtEnd (<translate><!--T:33--> The work comes to an end</translate>)
-:* TaskSolved (<translate>Task is solved</translate>)
+:* TaskSolved (<translate><!--T:34--> Task is solved</translate>)
 <translate>
 Assignment of intermediate categories is important only for long-term tasks, so that project staff understand their condition.
 </translate>

Paradatabase:Tasks solving system - Revision history

Lx&R: Marked this version for translation

Lx&R: Created page with " {{reqbox who-know-english}} ==Protocol== The main page with a list of tasks is {{#plang:Project:Project tasks}..."