[ImageJ-devel] [ImageJ] #1553: Make it easier for non-core-IJ2 developers to respond to tickets

[ImageJ]

#1553: Make it easier for non-core-IJ2 developers to respond to tickets
--------------------------+----------------------------------
 Reporter:  dscho         |       Owner:  dscho
     Type:  defect        |      Status:  closed
 Priority:  major         |   Milestone:  imagej2-b8-analysis
Component:  Server Admin  |     Version:
 Severity:  serious       |  Resolution:  fixed
 Keywords:                |  Blocked By:
 Blocking:  1915          |
--------------------------+----------------------------------
Changes (by curtis):

 * status:  reviewing => closed
 * resolution:   => fixed


Comment:

 New ImageJ issues have been being filed on GitHub Issues for a while now.
 And now that the final ImageJ component structure is in place, which
 repository houses each sort of issue is quite clear.

 So we will keep using GitHub Issues for all core SciJava software issue
 tracking. This makes it very simple for developers worldwide to respond to
 issues, either on the website or via email. GitHub takes care of all that
 for us.

 I am in the process of migrating all existing ImageJ Trac tickets to
 GitHub Issues in the appropriate repositories.

 > just decide that Fiji's BugZilla is supposed to serve the user-visible
 side of ImageJ2, too.

 Indeed, we could still generalize the Fiji BugZilla as a user-facing
 destination for all ImageJ bugs filed using the "Report a Bug" mechanism.
 Then from there we could link to relevant GitHub Issue(s). It's basically
 the difference between "user stories" and "developer tasks" which Agile
 methodologies emphasize.

-- 
Ticket URL: <http://trac.imagej.net/ticket/1553#comment:19>
ImageJ <http://trac.imagej.net>
ImageJ core development