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

Contribution Badges #165

Open
robmoffat opened this issue Nov 26, 2024 · 6 comments
Open

Contribution Badges #165

robmoffat opened this issue Nov 26, 2024 · 6 comments

Comments

@robmoffat
Copy link
Member

robmoffat commented Nov 26, 2024

An idea from @smendis-scottlogic:

  • FINOS should issue badges to both firms and individuals contributing to FINOS projects.
  • Badges could be distributed via cred.ly, as with other LF badges
  • Individuals would be able to share these on LinkedIn etc. which would be a useful way of publicising when firms and individuals are building things for FINOS.
  • This may have the effect of making it easier to find volunteers for projects, both from firms and individuals, since there is a clear link to recognition.
  • TOC may be a good body to oversee and administer this.

Suggested schedule:

Badge Firm Individual
Bronze 🥉 2 days / pcm. 2 hrs / pcm
Silver 🥈 4 days / pcm. 4 hrs / pcm
Gold 🥇 8 days / pcm. 8 hrs / pcm

This would need to be based largely on honour, but the TOC could conduct spot-checks to make sure contributions are happening.

@eddie-knight
Copy link
Contributor

@eminty69 Conceptually, this seems like something a TOC Liaison would request on behalf of their respective projects to encourage and recognize ongoing contributions

@eminty69
Copy link

@eddie-knight I think the contribution badges are a really good idea but is there no way to allocate them automatically? Having the TOC liaison do a review of who/how many contributions for a project makes sense but a manual process where the TOC liaison has to request the badge seems like it might be a bit uneven.

@eddie-knight
Copy link
Contributor

Perhaps maintainers can request the badges, and the Liaison can approve? Then part of the quarterly review can be an eyeball check to make sure the badges are up to date. WDYT?

@psmulovics
Copy link
Contributor

I am all for 'developer flair', it has been a big success at many different places I worked / volunteered / etc at. The easier (but still trackable and comfortably trustable) we can make this process, the better benefit for all.

@robmoffat
Copy link
Member Author

cred.ly has an API so I don't think an automation is off the table once we get this up and running and working how we want it

@eminty69
Copy link

I think it has to be automated but we need a working process first. I would say that having the quarterly review makes sense but I'd probably go with the project maintainers allocating the badges. This is going to need to be honour based at some level so the maintainers should have the best view on who is doing what. The review can then look at consistency of approach with the liaison and will also feed into how active the projects are.

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

No branches or pull requests

4 participants