Thanks for making the effort to accommodate first-time contributors.
I wrote this post mostly because I remembered how it was when I first started contributing to open source. I would open the Issues page on some repo and look for the good first issue label. Often times the results were either issues that sounded too complicated or there were already related PRs.
We sometimes talk about how we want more people to get involved but don't really provide guidance and/or tasks to get them started.
What if we had a weekly post on DEV where we plucked a bunch of "good first issues" and added a few sentences about why each might be a good first one and who it might be good for?
Having that extra editorial step might be a decent way for people to skim and discover, and also know that the issues are not stale because we're publishing about them today.
That great sound Ben, I would for help for sure, I tried helping you guys out a few times, but never found a relevant issue for me. This would make it a lot easier for people like me.
I will also encourage the idea of restricting somehow these issues to "first timers" only. It could be by politely rejecting the PRs of people who are not first time contributors (unless the issue is somehow critical). It could also be by saying that an issue can be taken by a first-time contributor within a month of its creation. Afterwards it's open for everyone.
I think that a post like that will have a positive effect. You can give it a try a few times and see if it works :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
We're making an effort to use
good first issueand difficulty tags more effectively in DEV's repo.github.com/thepracticaldev/dev.to/...
There are definitely some older issues in there, but if you are struggling to find places to contribute DM me and I'll help. :)
Thanks for making the effort to accommodate first-time contributors.
I wrote this post mostly because I remembered how it was when I first started contributing to open source. I would open the Issues page on some repo and look for the
good first issuelabel. Often times the results were either issues that sounded too complicated or there were already related PRs.We sometimes talk about how we want more people to get involved but don't really provide guidance and/or tasks to get them started.
What if we had a weekly post on DEV where we plucked a bunch of "good first issues" and added a few sentences about why each might be a good first one and who it might be good for?
Having that extra editorial step might be a decent way for people to skim and discover, and also know that the issues are not stale because we're publishing about them today.
I didn't actually realise that Dev.to was open source until your email came through. Now I love it even more 😍
That great sound Ben, I would for help for sure, I tried helping you guys out a few times, but never found a relevant issue for me. This would make it a lot easier for people like me.
That sounds fantastic! ❤
I will also encourage the idea of restricting somehow these issues to "first timers" only. It could be by politely rejecting the PRs of people who are not first time contributors (unless the issue is somehow critical). It could also be by saying that an issue can be taken by a first-time contributor within a month of its creation. Afterwards it's open for everyone.
I think that a post like that will have a positive effect. You can give it a try a few times and see if it works :)