Anonymous user
GSoC 2014/task-browser-info: Difference between revisions
no edit summary
imported>Shauna |
imported>Shauna No edit summary |
||
Line 3:
== Backend ==
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.
Line 16 ⟶ 14:
== Frontend ==
People in the workshop should be able to search or filter through the bugs to find ones matching their skills and interests. They should be able to search/filter along multiple axes (for instance, looking for education projects coded in Python).
Ideally people using the browser would be able to add notes to it, though perhaps not edit the main info. It would be neat if there was a field where they could indicate that they were working on it. Perhaps if they removed their name from working on it, they could be prompted as to why they were ceasing work and that information could be stored, either on the bug or hidden for mentors to view.
| |||