# HG changeset patch # User nishanth # Date 1267569495 -19800 # Node ID f65e62255e47147ab2484277b14f30f03774584e # Parent 8ca20bacc78edd49cfc0a4b995adf1cb9460e269 added a few more learn more pages. diff -r 8ca20bacc78e -r f65e62255e47 taskapp/views/user.py --- a/taskapp/views/user.py Tue Mar 02 22:50:17 2010 +0530 +++ b/taskapp/views/user.py Wed Mar 03 04:08:15 2010 +0530 @@ -18,13 +18,11 @@ about = { "addmentors": "about/addmentors.html", - "mentor": "about/mentor.html", ## - include role in different stages and merge with mentorrights + "mentor": "about/mentor.html", "starthere": "about/starthere.html", - ## "claimtask": - ## "edittask": - contains both about up and pub states - ## "mentorrights": - ## "assigntask": - ## "developer": + "task": "about/task.html", + "tasklife": "about/tasklife.html", + "developer": "about/developer.html", ## "manager": ## "admin": ## "request": - also contains about automatic rejection of requests diff -r 8ca20bacc78e -r f65e62255e47 templates/404.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/templates/404.html Wed Mar 03 04:08:15 2010 +0530 @@ -0,0 +1,5 @@ +{% extends 'base.html' %} +{% block content %} + The page you requested does not exist.
+ Click here to get back to the previous page. +{% endblock %} diff -r 8ca20bacc78e -r f65e62255e47 templates/about/addmentors.html --- a/templates/about/addmentors.html Tue Mar 02 22:50:17 2010 +0530 +++ b/templates/about/addmentors.html Wed Mar 03 04:08:15 2010 +0530 @@ -1,12 +1,24 @@ {% extends 'base.html' %} {% block title %} - {{task.title}} + PyTasks - About - Add Mentors {% endblock %} {% block content %} - A Mentorlearn more + A Mentor learn more of the task can request other users to mentor the task by clicking the link "Add more mentors" available on the task page. - A request will be sent to the user and he will also become the mentor of the task if he accepts it.
+ 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 mentor. + If the requested user accepts the request, he will also become the mentor of the task.

+ + Since mentors can view unpublished tasks, mentors 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.

+ Users can also be requested to mentor an published task. If the user accepts the request, he also becomes the mentor of the task. + In this case, the mentor 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.

+ + If a mentor requests a user to act as a mentor, he cannot make the same request to the same user again untill the previous one is + rejected. However, another mentor in the task can request the same user to be a mentor, unless there is already a similar request to the user + from this mentor also. {% endblock %} diff -r 8ca20bacc78e -r f65e62255e47 templates/about/mentor.html --- a/templates/about/mentor.html Tue Mar 02 22:50:17 2010 +0530 +++ b/templates/about/mentor.html Wed Mar 03 04:08:15 2010 +0530 @@ -1,10 +1,21 @@ {% extends 'base.html' %} {% block title %} - {{PyTasks - Learn more - Mentor}} + PyTasks - About - Mentor {% endblock %} {% block content %} - The user who created a task will become a mentor for the task. Mentor is a person who mentors the task. - Mentor has all the rights over the task. A Mentor can request other users also to mentor the task. - Mentor can add/remove subtasks if applicable. Mentor can request assign of credits for task. - Mentor can mark the task as Invalid/Complete.
+ Mentoring is a right specific to the task. The user who creates a task will become the mentor for the task. A Mentor can request + other learn more users also to mentor the task. + Mentor is a person who mentors the task. Mentor has all the rights over the task.
+ + + click here to know the complete life cycle of a task. {% endblock %} diff -r 8ca20bacc78e -r f65e62255e47 templates/about/starthere.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/templates/about/starthere.html Wed Mar 03 04:08:15 2010 +0530 @@ -0,0 +1,14 @@ +{% 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.
+ Choose a task learn more of your choice and claim it to start working on it.
+ + + +{% endblock %} diff -r 8ca20bacc78e -r f65e62255e47 templates/about/task.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/templates/about/task.html Wed Mar 03 04:08:15 2010 +0530 @@ -0,0 +1,22 @@ +{% 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 credits which are given to + users working on the task. A task is created by a privileged user and he becomes a + mentor learn more for the task. + The task if open, can be claimed by other users if they would like to work on the task.

+ + 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 mentor 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.

+ + 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.

+ + click here to know the complete life cycle of a task. + +{% endblock %} diff -r 8ca20bacc78e -r f65e62255e47 templates/about/tasklife.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/templates/about/tasklife.html Wed Mar 03 04:08:15 2010 +0530 @@ -0,0 +1,37 @@ +{% 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. +

+ + 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.

+ 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 mentors 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.

+ + 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 + will be available to mentor on the task page. If there are no users working, the mentor can request assign of credits to himself + 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 + request for assign of credits to the task implies that someone has worked on the task and hence dependencies cannot be + added after that.

+ + After a considerable amount of work has been done and all the users and mentors have been assigned pynts properly, any mentor in the + task can mark the task as complete. The link is available on assign pynts page just in case + the mentor wants to assign more pynts before marking the task as complete.
+ 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 + by providing a closing message. The link to close task will be available to mentors on the task page itself.

+ + Now all this can be done by any of the mentors and hence think twice before you request a user to mentor the task. +{% endblock %} diff -r 8ca20bacc78e -r f65e62255e47 templates/task/view.html --- a/templates/task/view.html Tue Mar 02 22:50:17 2010 +0530 +++ b/templates/task/view.html Wed Mar 03 04:08:15 2010 +0530 @@ -127,7 +127,12 @@ {% endif %} {% if task_claimable %} - View claims + + {% if is_mentor %} + View claims + {% else %} + Claim the task + {% endif %} {% endif %} {% if comments %}