-
Notifications
You must be signed in to change notification settings - Fork 4
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
Comments
@eminty69 Conceptually, this seems like something a TOC Liaison would request on behalf of their respective projects to encourage and recognize ongoing contributions |
@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. |
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? |
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. |
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 |
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. |
An idea from @smendis-scottlogic:
Suggested schedule:
This would need to be based largely on honour, but the TOC could conduct spot-checks to make sure contributions are happening.
The text was updated successfully, but these errors were encountered: