[Pharo-dev] make github issues clearer?

ducasse stepharo at netcourrier.com
Mon Nov 4 04:15:20 EST 2019


Yes sometimes describing it takes more time than fixing it. 
I would encourage people complaining to participate more. (no need to tell me that if we do not describe then people
cannot get it). 
At the end of the day, the key point is to contribute for real. 

Stef

>> minimum reproducible example (MRE).
> 
> +100
> 
> I am not sure that it needs a name (never heard it), but this should be so obvious.
> 
> Of course there has to be code that shows the issue, as simple as possible.
> 
> BTW I hate it when people explain their issue by saying: load a couple of complex projects, install some other software and then run it 10 times and it will probably happen.





More information about the Pharo-dev mailing list