--- Begin Message ---hi Stef On Mon, 4 Nov 2019 at 11:16, ducasse <[email protected]> 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. best, Myroslava
--- End Message ---
Re: [Pharo-dev] make github issues clearer?
Myroslava Romaniuk via Pharo-dev Mon, 11 Nov 2019 13:18:08 -0800
- [Pharo-dev] make github issues clearer? Myroslava Romaniuk via Pharo-dev
- Re: [Pharo-dev] make github issues c... Nicolas Cellier
- Re: [Pharo-dev] make github issu... Serge Stinckwich
- Re: [Pharo-dev] make github ... Marcus Denker
- Re: [Pharo-dev] make github issu... Marcus Denker
- Re: [Pharo-dev] make github issues c... Torsten Bergmann
- Re: [Pharo-dev] make github issu... HernĂ¡n Morales Durand
- Re: [Pharo-dev] make github ... Marcus Denker
- Re: [Pharo-dev] make github ... Sven Van Caekenberghe
- Re: [Pharo-dev] make git... ducasse
- Re: [Pharo-dev] mak... Myroslava Romaniuk via Pharo-dev
- Re: [Pharo-dev] make github ... Nicolas Cellier
- Re: [Pharo-dev] make github issues c... Gabriel Cotelli
