-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
Automate issuing of badges for completion of tour #118
Comments
@Relequestual I would like to work on this. |
@pavanydg The issue was discussed with @aialok in slack (message link), so we are assigning this to him. Thank you |
Please assign this to me. Thanks. |
Yeah sure no worries. |
Hi @pavanydg , are you still working on this issue ?? |
@AQIB-NAWAB, I think @aialok is currently working on this issue. |
okk got it , Thanks for clarification |
Firstly, the tour is awesome. Great work to all those involved. Thank you!
While we have been manually issuing certificates, this does not scale, and should be automated.
A while back while I was full time on JSON Schema, I looked for a good solution for providing attestable badges. The only good free solution I could find is https://badgr.com.
We created an account and an issuer identity for JSON Schema.
Currently, on completion of the tour, we capture the users name and email.
This goes into a google sheet.
We could automate the issuing of badges in multiple ways.
I was going to suggest using GitHub Actions workflow scheduled events, but there is a limit in that they will not continue to trigger if the repo has no update for 60 days.
My suggestion is to use Cloudflare Workers. We will very likely not hit the free limits.
Investigation work needs to be done to find out if this is feasable or if any limitaitons going to cause issues.
Proposed solution:
Considerations:
Approach:
Feel free to break these down into smaller Issues.
Please ask questions if anything is unclear (and notify me on Github if I don't reply within 2 days 😅)
The text was updated successfully, but these errors were encountered: