[Pharo-dev] make github issues clearer?

Myroslava Romaniuk romaniuk at ucu.edu.ua
Mon Nov 11 16:17:03 EST 2019

hi Stef

On Mon, 4 Nov 2019 at 11:16, ducasse <stepharo at netcourrier.com> wrote:

> Yes sometimes describing it takes more time than fixing it.
if that is the case, then maybe you should just fix it. easy issues are
cool in theory but if they are not sufficiently explained they will not be
of any use to beginner devs who want to contribute, either. if you are
creating an easy issue and marking it 'beginner', the description should be
level-appropriate. and in general there are templates that make this whole
process easier/faster because you have some things pre-filled and you have
section descriptions that helps you quickly remember the things you need to
describe. my whole point was about optimising this process on the org
level: individual contribution certainly counts for something, but there's
no need to reinvent the wheel.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20191111/ae4ead12/attachment.html>

More information about the Pharo-dev mailing list