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

PROCESS CHANGE: provide digital contribution badges #1493

Open
Cali0707 opened this issue Jan 19, 2024 · 8 comments
Open

PROCESS CHANGE: provide digital contribution badges #1493

Cali0707 opened this issue Jan 19, 2024 · 8 comments
Assignees

Comments

@Cali0707
Copy link
Member

Things to include with your process proposal (delete this text):

  • Expected benefits. Who gains the benefits? Why will they benefit?
  • Expected costs. Who bears the costs? How heavy are they?
  • Timeframe for implementation / rollout.
  • Are you willing to drive the process, or is this a request for help?

It would be interesting if we provided contribution badges based on the number of contributions an individual has made to Knative. For example, "Knative Contributor Level 1" could be making a single contribution, level 2 could be 10, level 3 could be 50 or 100, and so on.

Expected Benefits

This would help to encourage contributor growth, and help convert contributors who only make a few contributions into longer term contributors. A lot of contributors to open source projects do so for professional growth, so by providing them with public recognition (e.g. on their LinkedIn profile with a badge) we will be appealing to their interest. By providing multiple levels of the badge, we can encourage contributors to continue contributing beyond their first few contributions to the project and to "level up" their badge.

Expected costs

We would need to pay for some platform like Credly. Perhaps we could get access to the CNCF account that is used to create badges for talks at conferences?

Timeframe

One option would be to check this manually and periodically send the badges out ourselves. Another option would be to use the API for the platform we choose (such as Credly) to automatically send them. We could create a GitHub action that runs periodically and checks contributions, then sends new badges to the email associated with the account.

I would be happy to build the GitHub action or help drive this project in whichever direction is decided

@Cali0707
Copy link
Member Author

cc @aliok

@aliok
Copy link
Member

aliok commented Jan 23, 2024

Thanks for creating this ticket Calum. I think this would be a great initiative.

Things to find out:

  • Does Credly have an open source free usage?
  • How much Credly costs?
  • Can we find funding for it?
  • Does CNCF have some agreement with Credly that we can leverage?

@aliok
Copy link
Member

aliok commented Jan 23, 2024

Related: cncf/mentoring#1105

@mmejia02
Copy link

Hello! This sounds really great :) I’m not sure this is super relevant but I was also thinking that you could offer after a couple of contributions (maybe 15?), to give a recommendation or endorsement on the persons LinkedIn? This would be free, but it might also be time consuming for the maintainers.

It might be viewed well by possible contributors as it’s a publically available personalized message on their work ethic they can point to.

@aliok
Copy link
Member

aliok commented Jan 29, 2024

Related: cncf/toc#1248

@Cali0707
Copy link
Member Author

@aliok I was speaking to @krook about this last week and he recommended also taking a look at Holopin, it seems like they have an open source program, although it isn't currently active (apparently it is being revamped). They do have public pricing though, so maybe we can assess if that pricing is reasonable

@aliok aliok moved this to 🏗 In progress in Steering Committee Backlog Feb 27, 2024
@aliok
Copy link
Member

aliok commented Feb 27, 2024

@salaboy Naina told me you're working on something similar on Dapr side. Any information that you can share with us?

@aliok aliok moved this to 📋 Backlog in Steering Committee Backlog Feb 27, 2024
@aliok
Copy link
Member

aliok commented Mar 26, 2024

There's some progress made on CNCF side on this matter: cncf/toc#1248 (comment)

No details available at this moment though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📋 Backlog
Development

No branches or pull requests

4 participants