Hacker News new | past | comments | ask | show | jobs | submit login

(parent post tried to abolish blame and called out the grandparent post as the issue, hence why the lack of continuation)

I don't, you messed up!

The fact that you're actually incentivising contributors to make PRs of any quality and without standards, whilst forcing the burden on to maintainers (without reward) and you do very little (no tutorials about how to make quality PRs, no standards information on what comprises of a good PR, no quality guidance what so ever!).

This seems like a marketing stunt that has backfired and you're saying that you don't deserve some backlash?





This isn't highlighted high enough, and the lack of what makes a good PR that shows new contributors the best way forward isn't shown enough.

Yet I standby my statement, you're not blameless here.


Would you be willing to share what you'd recommend? I don't work at DigitalOcean but I know a few of the folks working on hacktoberfesst and I'm happy to forward our suggestions. je at h4x dot club.


Only count pull requests that are merged. Make this fact obvious on the hacktoberfest website so contributors know spamming PRs will not help them.

I know the standard answer to this is that it would exclude some repos (ex: node) that merge PRs manually via git. However:

1. You already are excluding every open source project not on GitHub, so this is a really weak point.

2. I am extremely confident trading off not including a very small subset of repos for removing the incentive to spam bad PRs is a worthwhile trade.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: