Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Engagement Leaderboards #100

Open
Digbigpig opened this issue Jul 25, 2019 · 2 comments
Open

Engagement Leaderboards #100

Digbigpig opened this issue Jul 25, 2019 · 2 comments
Labels
feedback: discussion Active discussion is happening to scope this issue, set acceptance criteria, or decide to accept it priority: low This is an issue that is fine sitting for a while project: rewrite This issue applies to the rewrite of Pybot status: awaiting acceptance Issue has not been accepted - it may need documentation, discussion, or a decision - the ice box type: airtable modification This issue requires a change to the Airtable base type: code change Issue requires changes to the code base type: documentation Issue requires a change to the current documentation of the codebase or product type: feature Issue involves adding new functionality that doesn't currently exist

Comments

@Digbigpig
Copy link

Digbigpig commented Jul 25, 2019

Have a hiscores command to display slack and github metrics.

This feature would:

  • Award points to users for certain activities in slack. (1 point for messaging, 5 points for introducing new members, etc)
  • Award points for GitHub actions (Merged PR - 50 points, comment - 1 point, etc)
  • Display a rolling monthly hiscore list. It could also give achievements for "Most Helpful - Most active in #help" etc.

This was just an idea for a feature we could hypothetically have and Conrad asked me to make the issue a few weeks back.

@Digbigpig Digbigpig changed the title Engagement Leaderboards Feature: Engagement Leaderboards Jul 25, 2019
@ivanmartinezmorales
Copy link

Would this be similar to using the Karma bot for Slack?

@kylemh kylemh added the general: hacktoberfest Issue is a good fit for Hacktoberfest label Oct 1, 2019
@AllenAnthes AllenAnthes removed the general: hacktoberfest Issue is a good fit for Hacktoberfest label Dec 29, 2019
@kylemh kylemh added the general: hacktoberfest Issue is a good fit for Hacktoberfest label Oct 1, 2020
@aaron-junot aaron-junot added priority: low This is an issue that is fine sitting for a while and removed general: hacktoberfest Issue is a good fit for Hacktoberfest labels Aug 18, 2021
@aaron-junot aaron-junot added the general: hacktoberfest Issue is a good fit for Hacktoberfest label Sep 29, 2021
@JudsonStevens JudsonStevens added feedback: discussion Active discussion is happening to scope this issue, set acceptance criteria, or decide to accept it general: good first issue Good for newcomers project: rewrite This issue applies to the rewrite of Pybot status: awaiting acceptance Issue has not been accepted - it may need documentation, discussion, or a decision - the ice box type: airtable modification This issue requires a change to the Airtable base type: code change Issue requires changes to the code base type: documentation Issue requires a change to the current documentation of the codebase or product type: feature Issue involves adding new functionality that doesn't currently exist and removed general: hacktoberfest Issue is a good fit for Hacktoberfest general: good first issue Good for newcomers labels Jan 1, 2022
@JudsonStevens
Copy link
Collaborator

The way I could see this working is to have the message information stored in Airtable - so process messages across the entire team/workspace, grab the usernames, and maybe have a weighted system of points for channels? So posts in #help are worth more than posts in #random. Don't think we should get too crazy with it and just keep it very simple. To tie in Github information we would need to set up a webhook or two to monitor the OC repos and have it fire on PR merges, passing along the email/name of the user who wrote the PR. Similar for comments.

The initial trick will be matching those up to Slack user information - if they have the same email or similar names it shouldn't be too hard. This could be tied to a slash command or !command that would show the current leaderboard in a simple table format.

That's my initial thoughts at least, happy to discuss it further.

@JudsonStevens JudsonStevens changed the title Feature: Engagement Leaderboards Engagement Leaderboards Jan 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feedback: discussion Active discussion is happening to scope this issue, set acceptance criteria, or decide to accept it priority: low This is an issue that is fine sitting for a while project: rewrite This issue applies to the rewrite of Pybot status: awaiting acceptance Issue has not been accepted - it may need documentation, discussion, or a decision - the ice box type: airtable modification This issue requires a change to the Airtable base type: code change Issue requires changes to the code base type: documentation Issue requires a change to the current documentation of the codebase or product type: feature Issue involves adding new functionality that doesn't currently exist
Projects
None yet
Development

No branches or pull requests

6 participants