My two cents on the "Open Sourcerer" and "Heart on Your Sleeve" achievements requirements

[rickstaa]

Select Topic Area

Product Feedback

Body

I just noticed that a user posted the requirements for getting the "Heart On Your Sleeve" and "Open Sourcerer" achievements on the non-official Achievements page (see Schweinepriester/github-profile-achievements#738). I double-checked with the GitHub support and the requirements for achieving currently planned as:

Open Sourcerer: User had PRs merged in multiple public repositories.
Heart on your Sleeve: React to something on GitHub with a ❤️ emoji.

Since the support asked me if I would provide feedback on these requirements in the https://github.com/orgs/community/discussions and start a discussion to help GitHub's @productTeam to get feedback on these requirements, here are my two cents.

In my opinion, the requirements of the Open Sourcerer achievements are great since it incentivises people to contribute to OS projects 🚀! It would be great to also have different levels to show how much PRs a person did for OS projects. I, however, can see how this will be too similar to the Pull Shark achievements.

For the Heart on your Sleeve achievement requirements, although I love to see more hearts on GitHub, I think the requirements of this achievement are too easy. I would love to see extra requirements added. For example:

1. React to something with a ❤️ AND
2. Donate to an OS project AND
3. Answered a discussion post in an OS project.

Further, since the naming of the achievement is similar to the pride moth slogan, you could also link the release of this badge to that month (see https://github.blog/2017-05-09-get-ready-for-pride-month-with-our-new-github-pride-and-trans-shirts/). For example, only award the achievement for hearts put on GitHub during this month. Hope my feedback helps!

[abinth11]

They mentioned that by just reacting a heart we will get that. But i didn't get it

[sahilpanghal]

❤️

[Kir4R00t]

❤️

[Parq254]

❤️

[shirabiton]

❤️

[BrianCodeDev]

nice

[github-staff]

Because of an influx of users creating low quality, nonsensical or spam posts in the Community with the aim of earning certain Achievements, we’ve made the difficult decision to disable the ability to earn Achievements in our Community.

Note that this change does not affect your ability to earn badges in other projects and communities across GitHub. This change only applies to GitHub’s Community Discussions.

You can learn more about this decision in our announcement post here Achievements will no longer be available in the Community.

Let us know if you have any other questions 🚀

[saucecontrol]

Clearly this has not had the desired effect, as the low quality, nonsense, and spam posts continue.

Even if this change were to have been effective, it would simply shift the nonsense to other orgs/projects in GitHub. The problem is the 'Achievements' themselves. When you make childish rewards, you invite childish behavior. This has no place in GitHub.

[WallysonMachadoDeLima]

❤️