Do you that is think effective the label "good for beginners" or "easy-start" to mark some issue or PR to review for newbies? How can we encourage newcomers to start in our projects?
Absolutely a helpful convention to have! These repos can then be listed at places like Good First Issue: goodfirstissue.dev/
And even moreso, I'd highly encourage, if possible (and energy allowing!!), to have a "mentorship available" or "mentorship provided" tag for issues, so folks know you're happy to pair with them on those!
In the past I attend to Wikimedia Hackathon (I'm part of Wikimedia movement, Wikipedia, Wikidata, etc), and my question about newcomers is who says "easy-to-start" issues are really easy to start, because in some cases the easy is create a new button or filtering a list, but both tasks needs a lot of knowledge about Mediawiki (triggers, coding practices and gerrit).
We (developers) have some problem to say what is easy 😅
For further actions, you may consider blocking this person and/or reporting abuse
Hi Ramón, thanks for your talk :)
Do you that is think effective the label "good for beginners" or "easy-start" to mark some issue or PR to review for newbies? How can we encourage newcomers to start in our projects?
Thank you so much, Dennis!
Absolutely a helpful convention to have! These repos can then be listed at places like Good First Issue:
goodfirstissue.dev/
And even moreso, I'd highly encourage, if possible (and energy allowing!!), to have a "mentorship available" or "mentorship provided" tag for issues, so folks know you're happy to pair with them on those!
Thanks for your answer.
In the past I attend to Wikimedia Hackathon (I'm part of Wikimedia movement, Wikipedia, Wikidata, etc), and my question about newcomers is who says "easy-to-start" issues are really easy to start, because in some cases the easy is create a new button or filtering a list, but both tasks needs a lot of knowledge about Mediawiki (triggers, coding practices and gerrit).
We (developers) have some problem to say what is easy 😅