/
1553.html
578 lines (492 loc) · 20.9 KB
/
1553.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<!-- See: http://trac.edgewall.org/wiki/TracInterfaceCustomization -->
<head>
<title>
#1553 (Make it easier for non-core-IJ2 developers to respond to tickets)
– ImageJ
</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<link rel="stylesheet" href="trac.css" type="text/css" /><link rel="stylesheet" href="ticket.css" type="text/css" /><link rel="stylesheet" href="tracvote.css" type="text/css" />
<link rel="stylesheet" type="text/css" href="style.css" />
</head>
<body>
<div id="main">
<div id="notice" style="width: 58em; max-width: 100%; margin-left: auto; margin-right: auto; border: 1px solid black; margin-bottom: 2em">
<table>
<tr>
<td style="font-size: 72px; color: firebrick; padding: 0 10px 0 10px">⚠</td>
<td>
<p style="margin: 0.4em">
NOTICE! This is a static HTML version of a legacy ImageJ Trac ticket.
</p>
<p style="margin: 0.4em">
The ImageJ project now
<a href="https://imagej.net/Issues">uses GitHub Issues</a> for issue tracking.
</p>
<p style="margin: 0.4em">
Please
<a href="https://github.com/imagej/imagej/issues/new">file all new issues</a>
there.
</p>
</td>
</tr>
</table>
</div>
<div id="content" class="ticket">
<h1 id="trac-ticket-title">
<a href="1553.html">Ticket #1553</a>
<span class="status">(closed defect: fixed)</span>
</h1>
<div id="ticket">
<div class="date">
<p>Opened 2012-10-25T00:33:16-05:00</p>
<p>Last modified 2014-05-01T13:01:34-05:00</p>
</div>
<h2 class="summary searchable">Make it easier for non-core-IJ2 developers to respond to tickets</h2>
<table class="properties">
<tr>
<th id="h_reporter">Reported by:</th>
<td headers="h_reporter" class="searchable">
dscho
</td>
<th id="h_owner">Owned by:</th>
<td headers="h_owner">
dscho
</td>
</tr>
<tr>
<th id="h_priority">
Priority:
</th>
<td headers="h_priority">
major
</td>
<th id="h_milestone">
Milestone:
</th>
<td headers="h_milestone">
imagej2-b8-analysis
</td>
</tr><tr>
<th id="h_component">
Component:
</th>
<td headers="h_component">
Server Admin
</td>
<th id="h_version">
Version:
</th>
<td headers="h_version">
</td>
</tr><tr>
<th id="h_severity">
Severity:
</th>
<td headers="h_severity">
serious
</td>
<th id="h_keywords">
Keywords:
</th>
<td headers="h_keywords" class="searchable">
</td>
</tr><tr>
<th id="h_cc">
Cc:
</th>
<td headers="h_cc" class="searchable">
cardonaa@…, imagej-devel@…
</td>
<th id="h_blockedby">
Blocked By:
</th>
<td headers="h_blockedby">
</td>
</tr><tr>
<th id="h_blocking">
Blocking:
</th>
<td headers="h_blocking">
<a class="closed" href="1915.html" title="Improve website resources [analysis]">#1915</a>
</td>
<th>
</th>
<td>
</td>
</tr>
</table>
<div class="description">
<h3 id="comment:description">
Description
</h3>
<div class="searchable">
<p>
Albert Cardona tried to respond to a ticket to which he was Cc:ed, but he could not log in, neither get a password via mail. In the interest of having an open development process, it needs to be possible for interested users to contribute, though.<br />
</p>
</div>
</div>
</div>
<div>
<h2 class="foldable">Change History</h2>
<div id="changelog">
<div class="change" id="trac-change-1">
<h3 class="change">
<span class="threading">
<span id="comment:1" class="cnum">
<a href="#comment:1">comment:1</a>
</span>
</span>
Changed 2013-03-19T11:23:40-05:00 by bdezonia
</h3>
<ul class="changes">
<li>
<strong>Status</strong>
changed from <em>new</em> to <em>reviewing</em>
</li>
</ul>
<div class="comment searchable">
<p>
dscho, please associated with some feature ticket<br />
</p>
</div>
</div>
<div class="change" id="trac-change-2">
<h3 class="change">
<span class="threading">
<span id="comment:2" class="cnum">
<a href="#comment:2">comment:2</a>
</span>
</span>
Changed 2013-03-19T14:26:09-05:00 by dscho
</h3>
<ul class="changes">
<li>
<strong>Blocking</strong>
<em>33</em> added
</li>
</ul>
<div class="comment searchable">
</div>
</div>
<div class="change" id="trac-change-3">
<h3 class="change">
<span class="threading">
<span id="comment:3" class="cnum">
<a href="#comment:3">comment:3</a>
</span>
</span>
Changed 2013-03-19T14:41:35-05:00 by curtis
</h3>
<ul class="changes">
<li>
<strong>Blocking</strong>
<em>1705</em> added; <em>33</em> removed
</li>
</ul>
<div class="comment searchable">
<p>
There is currently a very nasty problem with the Trac: certain functions that are supposed to send emails silently do not do so.<br />
</p>
<p>
Specifically, password requests are never sent (but the Trac reports no errors). Similarly, I attempted to enable new user account registration, but it also never sends the confirmation email necessary to greenlight a new account.<br />
</p>
<p>
It is probably sendmail being finicky about something due to permissions or similar, but I am not sure which logs to check to diagnose this problem.<br />
</p>
</div>
</div>
<div class="change" id="trac-change-4">
<h3 class="change">
<span class="threading">
<span id="comment:4" class="cnum">
<a href="#comment:4">comment:4</a>
</span>
</span>
Changed 2013-03-19T14:43:50-05:00 by curtis
</h3>
<div class="comment searchable">
<p>
Also, ultimately, to close out this ticket, we need to set up <a class="ext-link" href="https://oss.trac.surfsara.nl/email2trac"><span class="icon"> </span>email2trac</a>.<br />
</p>
</div>
</div>
<div class="change" id="trac-change-5">
<h3 class="change">
<span class="threading">
<span id="comment:5" class="cnum">
<a href="#comment:5">comment:5</a>
</span>
</span>
Changed 2013-03-19T14:44:49-05:00 by curtis
</h3>
<div class="comment searchable">
<p>
Another option would be to migrate our entire ticket infrastructure over to GitHub Issues. That would solve the openness problem completely, but at the expense of functionality: we would lose our hierarchical feature-based ticket classifications.<br />
</p>
</div>
</div>
<div class="change" id="trac-change-6">
<h3 class="change">
<span class="threading">
<span id="comment:6" class="cnum">
<a href="#comment:6">comment:6</a>
</span>
</span>
Changed 2013-03-19T14:54:53-05:00 by dscho
</h3>
<div class="comment searchable">
<p>
We would also be at the whim of the GitHub service which is in general quite good but not always.<br />
</p>
</div>
</div>
<div class="change" id="trac-change-7">
<h3 class="change">
<span class="threading">
<span id="comment:7" class="cnum">
<a href="#comment:7">comment:7</a>
</span>
</span>
Changed 2013-04-15T00:17:19-05:00 by dscho
</h3>
<div class="comment searchable">
<p>
Maybe as a compromise, we should encourage users to report problems on GitHub, but we still need to make it possible to respond to Trac tickets people are Cc:ed on.<br />
</p>
</div>
</div>
<div class="change" id="trac-change-8">
<h3 class="change">
<span class="threading">
<span id="comment:8" class="cnum">
<a href="#comment:8">comment:8</a>
</span>
</span>
Changed 2013-04-15T10:28:54-05:00 by curtis
</h3>
<div class="comment searchable">
<p>
Indeed, we could use GitHub for "user-facing" tickets and the Trac for "developer-facing" work. I am ambivalent, because it better targets the scope of each system. But the dichotomy could lead to duplicate or confusingly similar tickets. Ultimately I am leaning against it but more discussion would be good.<br />
</p>
</div>
</div>
<div class="change" id="trac-change-9">
<h3 class="change">
<span class="threading">
<span id="comment:9" class="cnum">
<a href="#comment:9">comment:9</a>
</span>
</span>
Changed 2013-06-05T15:47:46-05:00 by bdezonia
</h3>
<ul class="changes">
<li>
<strong>Blocking</strong>
<em>1915</em> added; <em>1705</em> removed
</li><li>
<strong>Milestone</strong>
changed from <em>imagej2-b7-ndim-data</em> to <em>imagej2-b8-analysis</em>
</li>
</ul>
<div class="comment searchable">
</div>
</div>
<div class="change" id="trac-change-10">
<h3 class="change">
<span class="threading">
<span id="comment:10" class="cnum">
<a href="#comment:10">comment:10</a>
</span>
</span>
Changed 2013-09-05T11:16:46-05:00 by dscho
</h3>
<div class="comment searchable">
<p>
We should seriously consider a custom solution based on procmail and the Python API. Hopefully I will have time to look into that soon; we need the same for Fiji's BugZilla because people find it too hard to follow the link to respond to tickets, and simply reply.<br />
</p>
</div>
</div>
<div class="change" id="trac-change-11">
<h3 class="change">
<span class="threading">
<span id="comment:11" class="cnum">
<a href="#comment:11">comment:11</a>
</span>
</span>
Changed 2013-09-05T12:23:58-05:00 by curtis
</h3>
<div class="comment searchable">
<p>
More and more, I want to migrate everything to GitHub Issues. Yes, it sucks when GitHub is down. Yes, we need to back up the tickets from there. But it would be <em>far</em> less time than maintaining a custom solution in an ever-hackier Trac installation, which is relatively less and less popular over time. Using GitHub Issues integrates with our other GitHub usage, is familiar to more and more developers, integrates with an increasingly large number of dev tools (such as Eclipse's Mylyn). Lastly, creating a new GitHub issue is a snap. Super fast, super easy. Better for core developers, better for the extended community.<br />
</p>
<p>
We are already using GitHub Issues with both ImgLib2 and SCIFIO now and it works well. The only thing I really miss from our Trac setup is hierarchical issues, but I am confident we can find an acceptable solution or substitute.<br />
</p>
</div>
</div>
<div class="change" id="trac-change-12">
<h3 class="change">
<span class="threading">
<span id="comment:12" class="cnum">
<a href="#comment:12">comment:12</a>
</span>
</span>
Changed 2013-09-05T14:23:56-05:00 by dscho
</h3>
<div class="comment searchable">
<p>
The only problem with GitHub issues we cannot really solve is that they require a user to be logged in to comment. And not everybody and her dog want to have a GitHub account...<br />
</p>
</div>
</div>
<div class="change" id="trac-change-13">
<h3 class="change">
<span class="threading">
<span id="comment:13" class="cnum">
<a href="#comment:13">comment:13</a>
</span>
</span>
Changed 2013-09-05T14:50:10-05:00 by curtis
</h3>
<div class="comment searchable">
<p>
Well, the Fiji wiki already requires people to create an account. Is that something you want to move away from? I.e., do you want to support anonymous bug reports? I don't know of any projects that support that, regardless of the bug tracker used.<br />
</p>
<p>
Of course, people can send a mail to the mailing list, and one of the developers can file the bug. I think that's what works best for nearly every project.<br />
</p>
<p>
Or are you saying you will miss the "CC" functionality of Trac and BugZilla where you can put an email address of someone who doesn't have an account? If we decide we really want that, we could support it via a custom script on one of our servers which reacts to GitHub Issue changes. And I believe it would still be less complicated than a "custom solution based on procmail and the Python API."<br />
</p>
</div>
</div>
<div class="change" id="trac-change-14">
<h3 class="change">
<span class="threading">
<span id="comment:14" class="cnum">
<a href="#comment:14">comment:14</a>
</span>
</span>
Changed 2013-09-05T14:54:05-05:00 by curtis
</h3>
<div class="comment searchable">
<p>
Also, I don't see the "require a user to be logged in to comment" issue as unique to GitHub Issues. The same problem exists for the IJ2 Trac and the Fiji BugZilla currently. You must have an account to comment. I am OK with that compromise, given the many other sacrifices we would need to make to pursue any alternative.<br />
</p>
</div>
</div>
<div class="change" id="trac-change-15">
<h3 class="change">
<span class="threading">
<span id="comment:15" class="cnum">
<a href="#comment:15">comment:15</a>
</span>
</span>
Changed 2013-09-05T15:18:37-05:00 by dscho
</h3>
<div class="comment searchable">
<p>
My idea was to auto-register BugZilla 'accounts' (which are really the email addresses, and hence automatically unique, in contrast to GitHub's) upon receiving a mail.<br />
</p>
<p>
I see that dramatically more difficult with GitHub where you really have to go through their website to register an account, including the intimidation about source code control for non-programmers ;-)<br />
</p>
</div>
</div>
<div class="change" id="trac-change-16">
<h3 class="change">
<span class="threading">
<span id="comment:16" class="cnum">
<a href="#comment:16">comment:16</a>
</span>
</span>
Changed 2013-09-05T15:38:57-05:00 by curtis
</h3>
<div class="comment searchable">
<p>
I understand the concern, but it sounds like too much work/time for us to accommodate. One option would be to simply register a single account like "ImageJ community" with GitHub and then pipe all emails we receive through that. Implementing a feature like that would make me uncomfortable though, since it would be a hacky workaround to the limitations of GitHub Issues. Unfortunately I don't have a better idea, but I am very reluctant to abandon GitHub Issues since it has myriad other benefits for those willing to register an account.<br />
</p>
</div>
</div>
<div class="change" id="trac-change-17">
<h3 class="change">
<span class="threading">
<span id="comment:17" class="cnum">
<a href="#comment:17">comment:17</a>
</span>
</span>
Changed 2013-09-09T09:54:58-05:00 by dscho
</h3>
<div class="comment searchable">
<p>
I think that the hacky workaround would also have one very nasty side effect: it would not notify the reporters of bugs whenever there was an update to their ticket.<br />
</p>
<p>
As to how much work it would take: I think I need to do this for <a class="ext-link" href="http://fiji.sc/bugzilla/"><span class="icon"> </span>http://fiji.sc/bugzilla/</a> anyway, so let's assess how much additional work it would be for Trac after that. Or just decide that Fiji's BugZilla is supposed to serve the user-visible side of ImageJ2, too. Something to mull over in the back of our minds for now, I guess.<br />
</p>
</div>
</div>
<div class="change" id="trac-change-18">
<h3 class="change">
<span class="threading">
<span id="comment:18" class="cnum">
<a href="#comment:18">comment:18</a>
</span>
</span>
Changed 2013-09-09T10:00:07-05:00 by curtis
</h3>
<div class="comment searchable">
<p>
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.<br />
</p>
<p>
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.<br />
</p>
</div>
</div>
<div class="change" id="trac-change-19">
<h3 class="change">
<span class="threading">
<span id="comment:19" class="cnum">
<a href="#comment:19">comment:19</a>
</span>
</span>
Changed 2014-05-01T13:01:34-05:00 by curtis
</h3>
<ul class="changes">
<li>
<strong>Status</strong>
changed from <em>reviewing</em> to <em>closed</em>
</li><li>
<strong>Resolution</strong>
set to <em>fixed</em>
</li>
</ul>
<div class="comment searchable">
<p>
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.<br />
</p>
<p>
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.<br />
</p>
<p>
I am in the process of migrating all existing ImageJ Trac tickets to GitHub Issues in the appropriate repositories.<br />
</p>
<blockquote class="citation">
<p>
just decide that Fiji's BugZilla is supposed to serve the user-visible side of ImageJ2, too.<br />
</p>
</blockquote>
<p>
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.<br />
</p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>