On 24 November 2013 09:28, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
On Nov 23, 2013, at 10:51 PM, Lorenz Köhl <lorenz@quub.de> wrote:
So registering on Pharo tracker *never* worked for me, since I try, before the summer. In the end I think is was a mistake to use fogbugz. For sure itâs nice for companies, but for open sourse projects it just does not work with a closed bug tracker.
Now the question is what is the effort to move to yet another one? I do not like fogbugz but I would not change now. Let us - make it easy for people to log
The Racket programming language (racket-lang.org) has in its IDE DrRacket a menu item - Submit bug report
Details about the system and a description of the bug is gathered and sent of to a bugs mailing list as well as creating an issue in a bug tracker. This way you get the issue number, a possible discussion thread about the bug/enhancement and any user can take part. IMHO this is the _right_ way to do it.
Long long time ago all the bugs could be submitted from Squeak itself (way before racket even started to exist) and we add a tool to crawl the emails and sort the bugs and it was a lot of work.
Ah, good old BFAV (Bug Fix Archive Viewer). Helping maintain that was the first thing I actually did for the community (as opposed to lurking). frank
So the Right way is something to evaluate and learn.
Is there something similar for pharo?
No but it was planned now if people can publish bug at a fast rate (and may be there are not bug) our question is: is it really reasonable to overwhelm with bugs :)
Contributing changes this way might get more complicated though, but possible.