diff options
Diffstat (limited to 'templates/about')
| -rw-r--r-- | templates/about/addmentors.html | 24 | ||||
| -rw-r--r-- | templates/about/admin.html | 8 | ||||
| -rw-r--r-- | templates/about/developer.html | 8 | ||||
| -rw-r--r-- | templates/about/manager.html | 7 | ||||
| -rw-r--r-- | templates/about/mentor.html | 21 | ||||
| -rw-r--r-- | templates/about/notification.html | 7 | ||||
| -rw-r--r-- | templates/about/request.html | 25 | ||||
| -rw-r--r-- | templates/about/starthere.html | 14 | ||||
| -rw-r--r-- | templates/about/task.html | 22 | ||||
| -rw-r--r-- | templates/about/tasklife.html | 39 |
10 files changed, 0 insertions, 175 deletions
diff --git a/templates/about/addmentors.html b/templates/about/addmentors.html deleted file mode 100644 index e0d19ea..0000000 --- a/templates/about/addmentors.html +++ /dev/null @@ -1,24 +0,0 @@ -{% extends 'base.html' %} -{% block title %} - PyTasks - About - Add Reviewers -{% endblock %} -{% block content %} - - A Reviewer <sup><a href="/about/reviewer/" target="_blank">learn more</a></sup> - of the task can request other users to reviewer the task by clicking the link "Add more reviewers" available on the task page. - A request will be sent to the user. If a user has claimed the task or is working on the task, he cannot be requested to be a reviewer. - If the requested user accepts the request, he will also become the reviewer of the task.<br /><br /> - - Since reviewers can view unpublished tasks, reviewers can be requested to view, edit and comment upon unpublished tasks. - They can also add or remove subtasks/dependencies in unpublished state. Thereby, the creator of task can fix on the task. - Publishing/Deleting of an unpublished task is available only to the creator of the task.<br /><br /> - - Users can also be requested to reviewer an published task. If the user accepts the request, he also becomes the reviewer of the task. - In this case, the reviewer is equivalent to the creator of the task. He can select/remove users; request pynts; close/complete the task. - He will have complete control over the task.<br /><br /> - - If a reviewer requests a user to act as a reviewer, he cannot make the same request to the same user again untill the previous one is - rejected. However, another reviewer in the task can request the same user to be a reviewer, unless there is already a similar request to the user - from this reviewer also. - -{% endblock %} diff --git a/templates/about/admin.html b/templates/about/admin.html deleted file mode 100644 index e618d3e..0000000 --- a/templates/about/admin.html +++ /dev/null @@ -1,8 +0,0 @@ -{% extends 'base.html' %} -{% block title %} - PyTasks - About - Admin -{% endblock %} -{% block content %} - Admin is the user who has to approve assign of pynts to any user for his/her work on the task.<br /> - An Admin also has the right to request normal users to become admins or managers or developers. -{% endblock %} diff --git a/templates/about/developer.html b/templates/about/developer.html deleted file mode 100644 index b0a7713..0000000 --- a/templates/about/developer.html +++ /dev/null @@ -1,8 +0,0 @@ -{% extends 'base.html' %} -{% block title %} - PyTasks - About - Developer -{% endblock %} -{% block content %} - A Developer has the right to post a task. The link is available on your homepage.<br /> - <a href="/about/tasklife/" target="_blank">click here</a> to know the complete life cycle of a task. -{% endblock %} diff --git a/templates/about/manager.html b/templates/about/manager.html deleted file mode 100644 index 804cda5..0000000 --- a/templates/about/manager.html +++ /dev/null @@ -1,7 +0,0 @@ -{% extends 'base.html' %} -{% block title %} - PyTasks - About - Manager -{% endblock %} -{% block content %} - A Manager has the right to request normal users to become managers or developers. -{% endblock %} diff --git a/templates/about/mentor.html b/templates/about/mentor.html deleted file mode 100644 index 9e2609e..0000000 --- a/templates/about/mentor.html +++ /dev/null @@ -1,21 +0,0 @@ -{% extends 'base.html' %} -{% block title %} - PyTasks - About - Reviewer -{% endblock %} -{% block content %} - Reviewering is a right specific to the task. The user who creates a task will become the reviewer for the task. A Reviewer can request - other <sup><a href="/about/addreviewers/" target="_blank">learn more</a></sup> users also to reviewer the task. - Reviewer is a person who reviewers the task. Reviewer has all the rights over the task.<br /> - - <ul> - <li>Reviewer can view the task even if it is unpublished.</li> - <li>Reviewer can edit the task when it is in unpublished state.</li> - <li>Reviewer can add/remove subtasks/dependencies to a task.</li> - <li>Reviewer decides whom to assign the task (choose from claimed users).</li> - <li>Reviewer also has the rights to remove a working user from a task.</li> - <li>Reviewer requests assigning of pynts to users/reviewers for the task.</li> - <li>Reviewer has the rights to close a task or mark the task as complete.</li> - <li>Publishing/Deleting an unpublished task is a special right available only to the creator of the task.</li> - </ul> - <a href="/about/tasklife/" target="_blank">click here</a> to know the complete life cycle of a task. -{% endblock %} diff --git a/templates/about/notification.html b/templates/about/notification.html deleted file mode 100644 index 3fce3ce..0000000 --- a/templates/about/notification.html +++ /dev/null @@ -1,7 +0,0 @@ -{% extends 'base.html' %} -{% block title %} - PyTasks - About - Notification -{% endblock %} -{% block content %} - Notification is a message generated by the system to inform you about any events. -{% endblock %} diff --git a/templates/about/request.html b/templates/about/request.html deleted file mode 100644 index 9776b3a..0000000 --- a/templates/about/request.html +++ /dev/null @@ -1,25 +0,0 @@ -{% extends 'base.html' %} -{% block title %} - PyTasks - About - Request -{% endblock %} -{% block content %} - Request is a request made by a user, requesting you to become someone else. It can also be request of assigning pynts to a user - for a task ( goes to all the admins only ). - You can accept or reject a request. You can also provide optional remarks when rejecting. When you respond to a request, it is - automatically removed from your requests and you will be redirected to browse requests page. - Redundant requests are automatically removed.<br /><br /> - The following can be redundant requests. - <ul> - <li>You are requested to act as a reviewer and the task is published or deleted or closed or completed</li> - <li>There are requests for assigning pynts to a user for a task and the task is closed or completed</li> - <li>There are requests for assigning pynts to a user and the user is removed from the working users of the task</li> - </ul> - These redundant requests when removed, a notification is sent to the requested user. - <ul> - <li>You accept a request to act as reviewer for a task and there are similar requests </li> - <li>You accept a request to act as an admin and there are similar or less privileged requests ("Manager", "Developer")</li> - <li>You accept a request to act as a manager and there are similar or less privileged requests ("Developer")</li> - <li>You accept a request to act as a developer and there are similar requests</li> - </ul> - -{% endblock %} diff --git a/templates/about/starthere.html b/templates/about/starthere.html deleted file mode 100644 index 26130a3..0000000 --- a/templates/about/starthere.html +++ /dev/null @@ -1,14 +0,0 @@ -{% extends 'base.html' %} -{% block title %} - PyTasks - Start here -{% endblock %} -{% block content %} - PyTasks is a website designed to encourage open source participation of people. Now that you are registered, you are a - contributor in the website. - You can see your notifications and requests from the links available in side bar. - You can browse all the tasks through the tasks link in the side bar.<br /> - Choose a task <sup><a href="/about/task/" target="_blank">learn more</a></sup> of your choice and claim it to start working on it.<br /> - - <!-- To know more on your rights in the website <a href="/about/contributor" target="_blank">click here</a>.<br /> --> - <!-- To know more on tasks <a href="/about/task/" target="_blank">click here</a>.<br /> --> -{% endblock %} diff --git a/templates/about/task.html b/templates/about/task.html deleted file mode 100644 index b744b56..0000000 --- a/templates/about/task.html +++ /dev/null @@ -1,22 +0,0 @@ -{% extends 'base.html' %} -{% block title %} - PyTasks - About - Task -{% endblock %} -{% block content %} - A task is an entity that people can work on and get pynts for their work. Every task has pynts which are given to - users working on the task. A task is created by a privileged user and he becomes a - reviewer <sup><a href="/about/reviewer/" target="_blank">learn more</a></sup> for the task. - The task if open, can be claimed by other users if they would like to work on the task.<br /><br /> - - The task can be claimed by submitting a proposal in the view claims page. The link to view claims page is available on the task page. - By claiming the task, you are actually proposing that you would like to do the task and hence the reviewer of the task will - be given an option to choose you for the task. A user can only submit one claim per task. But if a user is assigned a task - and for some reason, is removed from the task later on, he can submit a second claim requesting to continue working on the task.<br /><br /> - - A task can also have subtasks and dependencies. - The task can only be calimed when it is open for people to work on. If the link is unavailable it implies that the task is locked - since it has subtasks or it has dependencies that are not complete or the task is closed or the task is complete.<br /><br /> - - <a href="/about/tasklife/" target="_blank">click here</a> to know the complete life cycle of a task. - -{% endblock %} diff --git a/templates/about/tasklife.html b/templates/about/tasklife.html deleted file mode 100644 index 448b9d9..0000000 --- a/templates/about/tasklife.html +++ /dev/null @@ -1,39 +0,0 @@ -{% extends 'base.html' %} -{% block title %} - PyTasks - About - Task life cycle -{% endblock %} -{% block content %} - 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 - stage will be visible only to the creator. He can anyways request other users to view and review the task. Then the requested user - 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. - 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. - When the creator decides the task is ready to be published, he publishes the task. Through out this phase, - the creator of the task can delete the task at any point in time. - <br /><br /> - - 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 - point but subtasks/dependencies can be added/removed. If the task has subtasks, the task is locked forever. It implies that the task - cannot be claimed by anyone and exists only to show all of its subtasks in one place.<br /><br /> - If a task has dependencies, the task is locked untill all of its dependencies are completed. If all its dependencies are completed, - the task is open for claims and can be claimed by users. - 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) - 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 - to the fact that user had a chance to claim when the task had no dependencies or all its dependencies were satisfied. - Also selecting a user to work on the task implies the task has all its dependencies satisfied.<br /><br /> - - 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 - will be available to reviewer on the task page. If there are no users working, the reviewer can request assign of pynts to himself - 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 - request for assign of pynts to the task implies that someone has worked on the task and hence dependencies cannot be - added after that.<br /><br /> - - 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 - 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. - After a considerable amount of work has been done and all the users and reviewers have been assigned pynts properly, any reviewer in the - task can mark the task as complete. The link is available on assign pynts page just in case - the reviewer wants to assign more pynts before marking the task as complete.<br/> - 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 - by providing a closing message. The link to close task will be available to reviewers on the task page itself.<br /><br/> - - Now all this can be done by any of the reviewers and hence think twice before you request a user to reviewer the task. -{% endblock %} |