Smalltalk › Pharo › Pharo Smalltalk Developers

Fwd: Patches for Pharo packages you are maintaining

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

34 messages Options

Lorenz Köhl

Re: Patches for Pharo packages you are maintaining

>>> 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.

Is there something similar for pharo?

Contributing changes this way might get more complicated though, but possible.

philippeback

Re: Patches for Pharo packages you are maintaining

In reply to this post by Camillo Bruni-3

Is it so hard to register on STH and Fogbugz + give access to a Pharo inbox ?

Nah, come on.

At least, Fogbugz looks like a decent issue tracker and is easy to use.

(And we should push more Wiki pages in there).

Phil

philippeback

Re: Patches for Pharo packages you are maintaining

In reply to this post by Stéphane Ducasse

killing ugly monkey picture: +1000! (a reason why I don't go there BTW, it scares me).

Phil

On Sat, Nov 23, 2013 at 10:27 PM, Stéphane Ducasse <[hidden email]> 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
- remove this ugly monkey pictures (I do not like it - do you think that people can understand anything with it.
- get a newer version of smalltalkhub
and continue.

Stef

EstebanLM

Re: Patches for Pharo packages you are maintaining

I like the monkey... but I really don't care if is there or not.

Now... I think there are some real bugs in the bug tracker (like not updating the list).

I do not like fogbugz, I find it heavy, hard to use and a real pain in my ***, but I also think that "you do not change horses in the middle of the race" :)

Esteban

On Sun, Nov 24, 2013 at 12:38 AM, [hidden email] <[hidden email]> wrote:

killing ugly monkey picture: +1000! (a reason why I don't go there BTW, it scares me).

Phil

On Sat, Nov 23, 2013 at 10:27 PM, Stéphane Ducasse <[hidden email]> 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
- remove this ugly monkey pictures (I do not like it - do you think that people can understand anything with it.
- get a newer version of smalltalkhub
and continue.

Stef

EstebanLM

Re: Patches for Pharo packages you are maintaining

In reply to this post by Lorenz Köhl

Truth is that we can do better than others because we can serialize the stack and rebuild it in another place, making the reproduction of the error a triviality.

In my infinite TODO list I have: add a "submit bug" button to debugger window.

Only think that has prevented me to implement it is lack of time... If someone wants to take this task (not so hard, all the parts needed are already there), it would be a cool contribution to community.

Esteban

On Sat, Nov 23, 2013 at 10:51 PM, Lorenz Köhl <[hidden email]> 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.

Is there something similar for pharo?

Contributing changes this way might get more complicated though, but possible.

philippeback

Re: Patches for Pharo packages you are maintaining

In reply to this post by EstebanLM

For the easiest thing in town, I'd say "Atlassian Jira" https://www.atlassian.com/opensource/overview

I am using Fogbugz and JIRA on several client projects and JIRA definitely has more traction and engagement.

But, migrating may be less painful than before: https://confluence.atlassian.com/display/JIRA/Importing+Data+from+FogBugz+for+Your+Server

https://www.atlassian.com/software/jira/importer-migrations#!jira-fogbugz

Phil

EstebanLM

Re: Patches for Pharo packages you are maintaining

he, no, we are not going to re-migrate anytime soon :)

last year we needed a solution and we find it with fogbugz. Now, probably it does not fits completely with our process or our openness our other stuff, but still we have a reality: changing it is a lot of effort and even if fogbugz is not perfect, it works.

So... until we have time and a *proven* better solution, we will not change it.

As Stef said, the right step (now) is to make what we have work better, not run away from it :)

And of course, I'm not saying not to change ever... just not doing it impulsively and without reasoning...

Esteban

On Sun, Nov 24, 2013 at 10:15 AM, [hidden email] <[hidden email]> wrote:

For the easiest thing in town, I'd say "Atlassian Jira" https://www.atlassian.com/opensource/overview

I am using Fogbugz and JIRA on several client projects and JIRA definitely has more traction and engagement.

But, migrating may be less painful than before: https://confluence.atlassian.com/display/JIRA/Importing+Data+from+FogBugz+for+Your+Server

https://www.atlassian.com/software/jira/importer-migrations#!jira-fogbugz

Phil

Stéphane Ducasse

Re: Patches for Pharo packages you are maintaining

In reply to this post by Lorenz Köhl

On Nov 23, 2013, at 10:51 PM, Lorenz Köhl <[hidden email]> 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.

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.

Stéphane Ducasse

Re: Patches for Pharo packages you are maintaining

In reply to this post by EstebanLM

I like the monkey…

we talk about the picture

but I really don't care if is there or not.
Now... I think there are some real bugs in the bug tracker (like not updating the list).

I do not like fogbugz, I find it heavy, hard to use and a real pain in my ***, but I also think that "you do not change horses in the middle of the race" :)

Esteban

On Sun, Nov 24, 2013 at 12:38 AM, [hidden email] <[hidden email]> wrote:

killing ugly monkey picture: +1000! (a reason why I don't go there BTW, it scares me).

Phil

On Sat, Nov 23, 2013 at 10:27 PM, Stéphane Ducasse <[hidden email]> 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
- remove this ugly monkey pictures (I do not like it - do you think that people can understand anything with it.
- get a newer version of smalltalkhub
and continue.

Stef

EstebanLM

Re: Patches for Pharo packages you are maintaining

On Sun, Nov 24, 2013 at 10:29 AM, Stéphane Ducasse <[hidden email]> wrote:

I like the monkey…

we talk about the picture

yeah, I know... me too, I like it :D

(but as I say, I do not care about it :P)

but I really don't care if is there or not.
Now... I think there are some real bugs in the bug tracker (like not updating the list).

I do not like fogbugz, I find it heavy, hard to use and a real pain in my ***, but I also think that "you do not change horses in the middle of the race" :)

Esteban

On Sun, Nov 24, 2013 at 12:38 AM, [hidden email] <[hidden email]> wrote:

killing ugly monkey picture: +1000! (a reason why I don't go there BTW, it scares me).

Phil

On Sat, Nov 23, 2013 at 10:27 PM, Stéphane Ducasse <[hidden email]> 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
- remove this ugly monkey pictures (I do not like it - do you think that people can understand anything with it.
- get a newer version of smalltalkhub
and continue.

Stef

Camillo Bruni-3

Re: Patches for Pharo packages you are maintaining

On 2013-11-24, at 10:44, Esteban Lorenzano <[hidden email]> wrote:
> On Sun, Nov 24, 2013 at 10:29 AM, Stéphane Ducasse <[hidden email]> wrote:
>
>
>> I like the monkey…
>
> we talk about the picture

I removed it roughly 2 months ago but due to the seaside configuration hick-up the
Jenkins job / public issue list configuration does no longer work.

signature.asc (457 bytes) Download Attachment

hilaire

Re: Patches for Pharo packages you are maintaining

In reply to this post by EstebanLM

CONTENTS DELETED

The author has deleted this message.

Frank Shearar-3

Re: Patches for Pharo packages you are maintaining

In reply to this post by Stéphane Ducasse

On 24 November 2013 09:28, Stéphane Ducasse <[hidden email]> wrote:

>
> On Nov 23, 2013, at 10:51 PM, Lorenz Köhl <[hidden email]> 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.
>
>

Ben Coman

Re: Patches for Pharo packages you are maintaining

In reply to this post by hilaire

Hilaire Fernandes wrote:

Le 23/11/2013 19:05, Sean P. DeNigris a écrit :

But seriously if this is not clear, how do we improve it?


Make it work. It never worked for me, I keep trying then give up,
thinking about a temporary failure, then doing other business.
I don't understand what the monkey really want but it is not nice with
me. So I guess I miss something that should be documented.

Hilaire

(Sorry for this is a late reply. I found it stuck in my drafts.)

The initial problem with a dot in the name of an email address hit me. However after that was fixed I seemed to still have trouble registering until I worked out that my first registration had actually worked, it was just the email notification that had failed. So all my subsequent tries were failing because my account had already been registered - there was just no indication that was the problem. The "Assigned To" field actually shows an item 'hilaire' - so perhaps the same also happened with you. So this worked for me...

1. Went to pharo.fogbugz.com.
2. In the top right clicked <Login>
3. Clicked 'Forgot Password'

cheers -ben