Anonymous user
GSoC 2014/bug-set-creator: Difference between revisions
→Asheesh
imported>Ehashman |
|||
| (10 intermediate revisions by 3 users not shown) | |||
Line 68:
[[File:Bug-set-creator-view-screen.jpg|thumb|List view]]
# User gets to view a table very similar to that of the preview screen in List creation, but with
--><p>
#* Assigned Attendee
#* Task Description
#* Task Description </p><p>A user could then fill in these fields before or during an event: </p><!--▼
#* Assigned mentor
#* Language
#* Skills needed
#* Field of project
#* Estimated time to address bug
▲#*
--><p>
#* '''Assigned Attendee:''' Ke
#* '''Task Description:''' Improve our git training mission to be clearer. Purely HTML.
#* '''Assigned mentor:''' Elana
#* '''Language:''' HTML, CSS
#* '''Skills needed:''' web development, writing skills
#* '''Field of project:''' OH training missions
#* '''Estimated time to address bug:''' 30 minutes
#* '''Status:''' claimed</p>
# User clicks "Save" to submit this info. Page is refreshed.
Line 133 ⟶ 145:
I want to be able to tag bugs and filter them by tags.
* '''e:''' Also requested by Shauna. Definitely in the pipeline.
=== Asheesh ===
It would be really cool if I could click a button along the lines of "unblock this subnet", that would allow users from a particular IP block to edit bugs without being logged in.
* '''e''': I suggested this, it would be cool, not sure how feasible this is. Asheesh gives a +1 so he can claim credit for the idea.
I might add bugs to a set, have no one show up to my sprint, and then want to use the same bug set later. But perhaps someone has closed some of those bugs in the meantime! I would like to have a 'refresh metadata' button that will let me know if the OpenHatch bug tracker has recorded any of my set's bugs as "looks closed".
== Project Milestones ==
* '''gsoc14.4:''' Week 4, May 25 -- June 1
** List view
** Blog post due June 1
* '''gsoc14.5:''' Week 5, June 2 -- 8
** View list view iteration 1 (no edits)
* '''gsoc14.6:''' Week 6, June 9 -- 15
** View list view iteration 2 (edits)
* '''gsoc14.7:''' Week 7, June 16 -- 22
** Blog post due June 22
* '''gsoc14.8:''' Week 8, June 23 -- 29
** Attend Open Source Bridge
** Midterm Review
* '''gsoc14.9:''' Week 9, June 30 -- July 6
* '''gsoc14.10:''' Week 10, July 7 -- 13
** Blog post due July 13
* '''gsoc14.11:''' Week 11, July 14 -- 20
** View list view iteration 3 (refinement & css)
* '''gsoc14.12:''' Week 12, July 21 -- 27
** Create and Edit views
** Update list view
** Blog post due July 27
* '''gsoc14.13:''' Week 13, July 28 -- August 3
** Simultaneous editing: Notification on edited bug list/bug set
** Security fixes for production
** ''Refresh metadata to inform user if bug is closed [stretch]''
* '''gsoc14.14:''' Week 14, August 4 -- 10
** Call for user testing (Shauna, Jessica, Britta)
** Documentation
* '''gsoc14.15:''' Week 15, August 11 -- 17
** User testing
** Final Exams
** Blog post due August 17
*** Recommendations for future extension(s)
* '''gsoc14.16:''' Week 16, August 18 -- 22
** Final Review
** Security documentation PR for django-inplaceedit
== Implementation ==
| |||