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 |
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 |
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 /> |
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, |
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. |
18 the task is open for claims and can be claimed by users. |
19 If a task has neither subtasks nor dependencies, it is open as well and users claim the task. Any of the mentors can select user(s) |
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) |
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 |
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. |
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 /> |
22 Also selecting a user to work on the task implies the task has all its dependencies satisfied.<br /><br /> |
23 |
23 |
24 During the working stage of task, a mentor can request assign of pynts to users working on task or the mentors. The assign pynts link |
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 |
25 will be available to mentor on the task page. If there are no users working, the mentor can request assign of credits to himself |
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 |
26 or one of the other mentors, who ever has done work on the task. Even if there are no users working on task, if there is a |
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 |
27 request for assign of credits to the task implies that someone has worked on the task and hence dependencies cannot be |
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 /> |
28 added after that.<br /><br /> |
29 |
29 |
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 |
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 |
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. |
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. |
32 After a considerable amount of work has been done and all the users and mentors have been assigned pynts properly, any mentor in the |
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 |
33 task can mark the task as complete. The link is available on assign pynts page just in case |
33 task can mark the task as complete. The link is available on assign pynts page just in case |
34 the mentor wants to assign more pynts before marking the task as complete.<br/> |
34 the reviewer wants to assign more pynts before marking the task as complete.<br/> |
35 If a mentor 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 |
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 |
36 by providing a closing message. The link to close task will be available to mentors on the task page itself.<br /><br/> |
36 by providing a closing message. The link to close task will be available to reviewers on the task page itself.<br /><br/> |
37 |
37 |
38 Now all this can be done by any of the mentors and hence think twice before you request a user to mentor the task. |
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. |
39 {% endblock %} |
39 {% endblock %} |