| author | Nishanth Amuluru <nishanth@fossee.in> |
| Wed, 05 Jan 2011 22:22:10 +0530 | |
| changeset 218 | 59107ce0a618 |
| parent 186 | c083ebb6f8d7 |
| child 219 | f04a1ec7a07f |
| permissions | -rw-r--r-- |
| 185 | 1 |
{% extends 'base.html' %}
|
2 |
{% block title %}
|
|
3 |
PyTasks - About - Task life cycle |
|
4 |
{% endblock %}
|
|
5 |
{% block content %}
|
|
6 |
The task is created by a user and will start life in unpublished state. The creator has all rights over the task. The task in this |
|
7 |
stage will be visible only to the creator. He can anyways request other users to view and review the task. Then the requested user |
|
8 |
can view the task untill he does not reply to the request. If the user accepts the request, he can view, edit and comment on the task. |
|
9 |
The user can also add/remove subtasks or dependencies. If he rejects the request he is just like other users and cannot view the task. |
|
10 |
When the creator decides the task is ready to be published, he publishes the task. Through out this phase, |
|
11 |
the creator of the task can delete the task at any point in time. |
|
12 |
<br /><br /> |
|
13 |
||
14 |
If the task survives and is published, the task is available to be viewed by all the users. The task cannot be edited after this |
|
15 |
point but subtasks/dependencies can be added/removed. If the task has subtasks, the task is locked forever. It implies that the task |
|
16 |
cannot be claimed by anyone and exists only to show all of its subtasks in one place.<br /><br /> |
|
17 |
If a task has dependencies, the task is locked untill all of its dependencies are completed. If all its dependencies are completed, |
|
18 |
the task is open for claims and can be claimed by users. |
|
|
218
59107ce0a618
Replaced the word mentor with reviewer
Nishanth Amuluru <nishanth@fossee.in>
parents:
186
diff
changeset
|
19 |
If a task has neither subtasks nor dependencies, it is open as well and users claim the task. Any of the reviewers can select user(s) |
| 185 | 20 |
from the claimed users to work on the task . Dependencies can be added/removed only untill a user is selected to work on the task. This is due |
21 |
to the fact that user had a chance to claim when the task had no dependencies or all its dependencies were satisfied. |
|
22 |
Also selecting a user to work on the task implies the task has all its dependencies satisfied.<br /><br /> |
|
23 |
||
|
218
59107ce0a618
Replaced the word mentor with reviewer
Nishanth Amuluru <nishanth@fossee.in>
parents:
186
diff
changeset
|
24 |
During the working stage of task, a reviewer can request assign of pynts to users working on task or the reviewers. The assign pynts link |
|
59107ce0a618
Replaced the word mentor with reviewer
Nishanth Amuluru <nishanth@fossee.in>
parents:
186
diff
changeset
|
25 |
will be available to reviewer on the task page. If there are no users working, the reviewer can request assign of credits to himself |
|
59107ce0a618
Replaced the word mentor with reviewer
Nishanth Amuluru <nishanth@fossee.in>
parents:
186
diff
changeset
|
26 |
or one of the other reviewers, who ever has done work on the task. Even if there are no users working on task, if there is a |
| 185 | 27 |
request for assign of credits to the task implies that someone has worked on the task and hence dependencies cannot be |
28 |
added after that.<br /><br /> |
|
29 |
||
|
186
c083ebb6f8d7
finished the phase-2 successfully. added all the learnmore templates. hav to look for bugs if any.
nishanth
parents:
185
diff
changeset
|
30 |
The users can be selected to work or removed from working users at any point in time. If a user is removed, he can claim again |
|
c083ebb6f8d7
finished the phase-2 successfully. added all the learnmore templates. hav to look for bugs if any.
nishanth
parents:
185
diff
changeset
|
31 |
to request to continue working on the task. If a user is removed, all the pending requests for assigning pynts to user will be made invalid. |
|
218
59107ce0a618
Replaced the word mentor with reviewer
Nishanth Amuluru <nishanth@fossee.in>
parents:
186
diff
changeset
|
32 |
After a considerable amount of work has been done and all the users and reviewers have been assigned pynts properly, any reviewer in the |
| 185 | 33 |
task can mark the task as complete. The link is available on assign pynts page just in case |
|
218
59107ce0a618
Replaced the word mentor with reviewer
Nishanth Amuluru <nishanth@fossee.in>
parents:
186
diff
changeset
|
34 |
the reviewer wants to assign more pynts before marking the task as complete.<br/> |
|
59107ce0a618
Replaced the word mentor with reviewer
Nishanth Amuluru <nishanth@fossee.in>
parents:
186
diff
changeset
|
35 |
If a reviewer feels that the task is invalid or decides to delete the task, he will not be allowed to do it. Instead he can close the task |
|
59107ce0a618
Replaced the word mentor with reviewer
Nishanth Amuluru <nishanth@fossee.in>
parents:
186
diff
changeset
|
36 |
by providing a closing message. The link to close task will be available to reviewers on the task page itself.<br /><br/> |
| 185 | 37 |
|
|
218
59107ce0a618
Replaced the word mentor with reviewer
Nishanth Amuluru <nishanth@fossee.in>
parents:
186
diff
changeset
|
38 |
Now all this can be done by any of the reviewers and hence think twice before you request a user to reviewer the task. |
| 185 | 39 |
{% endblock %}
|