Updated at 10/01/2020 13:00 UTC

Since the start of Hacktoberfest 2020, open source maintainers have experienced a noticeable uptick in spammy pull requests originating from Hacktoberfest participants. As of 2pm PST on October 1, at least 4% of pull requests from Hacktoberfest participants have been marked ‘invalid’ or ‘spam.’

We’ve traced the majority of this year’s spammy contributions back to a participant with a large online audience who openly encouraged their community to take part in spammy activities, including ideas on how to game the system. However, we know the spam issues go beyond this one example. This is an aspect of Hacktoberfest we have been working to improve since we started the program seven years ago.

We apologize for the impact this spam is having on the community. We often talk about intent versus impact and this is a classic example. Hacktoberfest aims to celebrate open source with positive engagement between contributors and maintainers alike. Unfortunately, the actions of some participants led to unintended consequences for all. They’ve overwhelmed maintainers and steamrolled other participants in an effort to receive a T-shirt they didn’t really earn.

Despite this, we are confident that, with your help, we can make things better. We’ve already started making changes to the program to help reduce spam and there is much more work planned in the days ahead.

What we’re doing about it (right now):

Excluding and banning:

In past years, we tried labelling issues “invalid” and “spam” to deter participants from spamming repositories. Unfortunately this has not made as much impact as we had hoped. Therefore, we’re adding new ways to discourage participants from spamming.

  1. For maintainers, we’re building on an existing idea and doubling down on an excluded repository list for Hacktoberfest. If you don’t want pull requests to your repositories counted toward Hacktoberfest, send us the info in an email to hacktoberfestmaintainers@digitalocean.com.
  2. We are also implementing a banning system that reviews and bans users with with too many flagged PR’s. This can result in exclusion from all future Hacktoberfests, not just this one.
  3. This year, we’re also extending the validation period from one week to 14 days. This will give maintainers more time to review pull requests before contributors earn their shirts.

Onboarding overhaul:

For participants of Hacktoberfest, the first step is always the onboarding journey of connecting their GitHub account, sharing their email, and agreeing to the program rules. Since we know that many participants skip over this important step, we’re creating a mandatory onboarding flow requiring each new participant to learn the rules and some specific dos and don’ts. We will also share this information with the nearly 100K participants who have already registered.

Going forward, every participant will have an entirely revamped profile page to highlight a few key pieces of information. We want to educate users so they can provide quality contributions. However, we will also include some ways for them to more easily earn a shirt so they don’t need to resort to spamming.

Communicating our community’s concern:

We also know communication is key and we can’t solve this issue all on our own. We plan to talk to maintainers across the community so we can hear more about their experience with Hacktoberfest and come up with solutions together. We’re setting up 20 maintainer roundtable sessions over the next week in all global time zones to gather feedback and ideas.

Lastly, we’re working closely with our sponsors to find more and more ways to reduce the amount of spam. A shining example of this is GitHub’s new addition of interaction limits, as well as the team at DEV who have put together a helpful Contributor Etiquette Guide.

Where (else) do we go from here?

To the maintainers: We’re sorry that these unintended consequences of Hacktoberfest have made more work for many of you. We know there is more work to do, which is why we ask that you please join us for a community roundtable discussion where we promise to listen and take actions based on your ideas.

To the event organizers and attendees: We’re committed to the original mission of getting people positively involved in open source. For all the folks who have had events already, we thank you for your support and your contributions to the community.

To the contributors: We know that Hacktoberfest has been a rewarding experience for many of you and we don’t want to lose sight of that. We ask that you please refrain from making spammy contributions that undermine the rules and values of Hacktoberfest. We know the majority of our participants are here to learn and grow through quality contributions. Please continue to help us make a positive impact on the community by reading the resources, connecting with others on DEV, or joining a helpdesk session.

As always, our Hacktoberfest communication channels are wide open. We review every inquiry that comes our way and we look forward to hearing and learning from this year’s Hacktoberfest to make it better. You can email us at hacktoberfest@digitalocean.com if you have more ideas on how we can improve Hacktoberfest and give back to the open source community.

Sincerely,


Hacktoberfest team at DigitalOcean

P.S. And if you’re still looking for some great projects to contribute quality pull requests to this Hacktoberfest, we encourage you to check out OSMI (Open Sourcing Mental Illness Help) and the mental health prompt.

Read More

ترك الرد

من فضلك ادخل تعليقك
من فضلك ادخل اسمك هنا