Difference between revisions of "GSoC 2014/task-browser-info"

From OpenHatch wiki
Jump to navigation Jump to search
imported>Shauna
imported>Shauna
Line 8: Line 8:
 
Each bug will be associated with a project. The project itself will have some info associated with it (see the bottom of [http://campus.openhatch.org/projects.html this page] for a portion of that info - links to help info, etc). Ideally this info only has to be entered once, and when entering a bug for a pre-existing project you can just associate it with a project.
 
Each bug will be associated with a project. The project itself will have some info associated with it (see the bottom of [http://campus.openhatch.org/projects.html this page] for a portion of that info - links to help info, etc). Ideally this info only has to be entered once, and when entering a bug for a pre-existing project you can just associate it with a project.
   
When entering bugs, there should be a number of fields, including: link to the bug, status of the bug, when the status was last verified (default to when the bug is entered), skills associated with fixing the bug.
+
When entering bugs, there should be a number of fields, including: link to the bug, status of the bug, when the status was last verified (default to when the bug is entered), skills associated with fixing the bug, mentor at the event you can ask for help with the bug.
   
 
Entering the bugs should be a process that does not require significant work or special permissions for the person entering the info.
 
Entering the bugs should be a process that does not require significant work or special permissions for the person entering the info.

Revision as of 04:01, 19 March 2014

Workflow

Backend

Entering Projects

Each bug will be associated with a project. The project itself will have some info associated with it (see the bottom of this page for a portion of that info - links to help info, etc). Ideally this info only has to be entered once, and when entering a bug for a pre-existing project you can just associate it with a project.

When entering bugs, there should be a number of fields, including: link to the bug, status of the bug, when the status was last verified (default to when the bug is entered), skills associated with fixing the bug, mentor at the event you can ask for help with the bug.

Entering the bugs should be a process that does not require significant work or special permissions for the person entering the info.

We will want the ability to edit and remove bugs.

Frontend

How people in the workshops would use it.