[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:  reviewing
 Priority:  major         |   Milestone:  imagej2-b8-analysis
Component:  Server Admin  |     Version:
 Severity:  serious       |  Resolution:
 Keywords:                |  Blocked By:
 Blocking:  1915          |
--------------------------+----------------------------------

Comment (by curtis):

 I agree that solving the issue tracker is not our top priority right now.
 However, I would like to address it by year's end. ImageJ2 has gone
 several years with a bug tracker that is not really usable for the
 community at large. That must end before we come out of beta.

 Fiji's bug tracker is indeed much more usable. The idea of making the Fiji
 BugZilla also be the user-facing ImageJ2 bug tracker is intriguing. But we
 should first answer the question: "Do we need separate user-facing and
 developer-facing issue trackers?" My answer leans toward "no" right now --
 most projects do not have such a separation, and the line between them
 becomes extremely blurry in many cases, making duplication (and hence
 disorganization) prevalent.

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