There's a good chance that a lot of repositories won't opt in after this mess and thus cause this event leave out regular contributors, but that's okay, I guess; the focus is probably more on...
There's a good chance that a lot of repositories won't opt in after this mess and thus cause this event leave out regular contributors, but that's okay, I guess; the focus is probably more on getting people into open source, and this should probably highlight projects that are ready and willing to teach instead of people going to projects they know and making unwarranted PRs that the maintainers don't have time to review
What I'd like to see: time consuming, yet beginner-friendly issues being tagged somehow to indicate they are what a maintainer would appreciate help on (as opposed to "beginner friendly", "boot...
pull requests will only count toward earning a T-shirt or planting a tree if they are submitted in a repository classified with the ‘hacktoberfest’ topic. The pull requests will also need to be merged, approved by a maintainer, or labeled as ‘hacktoberfest-accepted’ in order to qualify.
What I'd like to see: time consuming, yet beginner-friendly issues being tagged somehow to indicate they are what a maintainer would appreciate help on (as opposed to "beginner friendly", "boot camp", "good first issue", etc.)
If they limited accepted PRs to those that are merged that resolve the issues tagged as mentioned above, maybe that'd offset the time wasted by maintainers on spam.
Also, why isn't there a GitHub project called "all PRs accepted" for those who just want some mug or whatever? Seems trivially easy to do, as easy as spamming a legitimate project.
Also, why isn't there a GitHub project called "all PRs accepted" for those who just want some mug or whatever? Seems trivially easy to do, as easy as spamming a legitimate project.
That’s what happened a few years ago: a repository that just had all kinds of algorithms in different languages. People can contribute stuff there and everyone is happy. The result is also pretty...
That’s what happened a few years ago: a repository that just had all kinds of algorithms in different languages. People can contribute stuff there and everyone is happy. The result is also pretty cool, I’d say
I vaguely wonder if the reason they switched to opt-in wasn't just bad PR but because it was going to be too much work for them to do opt-out. It wasn't automated at all - all they did was provide...
I vaguely wonder if the reason they switched to opt-in wasn't just bad PR but because it was going to be too much work for them to do opt-out. It wasn't automated at all - all they did was provide an email. I sent them an email, and pointed towards my profile, which has 30+ repos in it, and said to exclude them all. If other developers did the same, that would mean their support staff is spending hours manually entering thousands of repo names into an opt-out list.
Or one could post a link to their repo in an opt-out web form. I typically assume good faith; the community asked for opt-in and that's what DigitalOcean did.
Or one could post a link to their repo in an opt-out web form.
I typically assume good faith; the community asked for opt-in and that's what DigitalOcean did.
There's a good chance that a lot of repositories won't opt in after this mess and thus cause this event leave out regular contributors, but that's okay, I guess; the focus is probably more on getting people into open source, and this should probably highlight projects that are ready and willing to teach instead of people going to projects they know and making unwarranted PRs that the maintainers don't have time to review
What I'd like to see: time consuming, yet beginner-friendly issues being tagged somehow to indicate they are what a maintainer would appreciate help on (as opposed to "beginner friendly", "boot camp", "good first issue", etc.)
If they limited accepted PRs to those that are merged that resolve the issues tagged as mentioned above, maybe that'd offset the time wasted by maintainers on spam.
Also, why isn't there a GitHub project called "all PRs accepted" for those who just want some mug or whatever? Seems trivially easy to do, as easy as spamming a legitimate project.
There is. DigitalOcean didn't appreciate it.
That’s what happened a few years ago: a repository that just had all kinds of algorithms in different languages. People can contribute stuff there and everyone is happy. The result is also pretty cool, I’d say
I vaguely wonder if the reason they switched to opt-in wasn't just bad PR but because it was going to be too much work for them to do opt-out. It wasn't automated at all - all they did was provide an email. I sent them an email, and pointed towards my profile, which has 30+ repos in it, and said to exclude them all. If other developers did the same, that would mean their support staff is spending hours manually entering thousands of repo names into an opt-out list.
Or one could post a link to their repo in an opt-out web form.
I typically assume good faith; the community asked for opt-in and that's what DigitalOcean did.