To maintain quality, not just the contributors but also the maintainers should come forward too.
A maintainer is mostly well aware of his/her project. As a participant, I expect maintainers to elaborate their issues in details with some workflow of the corresponding activity and the unexpected behaviour happening around.
Not just like opening an issue and saying "Hey guys, fix this problem" with no further details. Afterall, Contributors are human not the genie of Alaadin.
One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
To maintain quality, not just the contributors but also the maintainers should come forward too.
A maintainer is mostly well aware of his/her project. As a participant, I expect maintainers to elaborate their issues in details with some workflow of the corresponding activity and the unexpected behaviour happening around.
Not just like opening an issue and saying "Hey guys, fix this problem" with no further details. Afterall, Contributors are human not the genie of Alaadin.
😇
FYI the way I handle that I create issues that don't need a lot of context, label them with "good first issue" using an issue template which starts by asking people to read the CONTRIBUTING guide
Worked really well so far, I'm happy to report that in a couple of days, I got 7 meaningfull pull requests and 0 spam.
That sounds cool, Fayard. 🎉