Implement a recognition System
We identified that it was a challenge for contributors to know how to contribute to projects both inside and outside of the GitHub organization. This is why we refined the contribution journey with the issue #410 .
The scope of this issue is to go further and refine the recognition system.
Scope
The scope of this project includes:
- Adapt the website and slack contribution experience to the enhanced version on Github.
- Improve the recognition system.
Objectives
The objectives of this project are:
- Increase the total number of contributors.
- Provide clarity on the total number of contributors including non-code contributions and repositories outside the organization.
Plan
-
[ ] Enhance Recognition System
- [ ] Evaluate the enhancement of the current recognition system. E.G. Use All Contributors spec https://github.com/orgs/json-schema-org/discussions/390
- [ ] Page with TSC members.
- [ ] Page with Champions Program and members.
- [ ] Page with project maintainers
- [ ] Workflows to recognize and praise contributions
-
[ ] Comms Plan
- [ ] Define comms templates to praise new contributors
- [ ] Define comms to encourage contributions using the new contribution path.
Hi! I’m Avradeep Nayak, a student at VIT Bhopal studying Computer Science in my final year. I am a programming enthusiast, and my expertise lies in the MERN stack and on AIML. I have created several projects on Ai ML. So please alow me to work on this issue under gsoc24.
Hello! :wave:
This issue has been automatically marked as stale due to inactivity :sleeping:
It will be closed in 180 days if no further activity occurs. To keep it active, please add a comment with more details.
There can be many reasons why a specific issue has no activity. The most probable cause is a lack of time, not a lack of interest.
Let us figure out together how to push this issue forward. Connect with us through our slack channel : https://json-schema.org/slack
Thank you for your patience :heart:
Hello! :wave:
This issue has been automatically marked as stale due to inactivity :sleeping:
It will be closed in 180 days if no further activity occurs. To keep it active, please add a comment with more details.
There can be many reasons why a specific issue has no activity. The most probable cause is a lack of time, not a lack of interest.
Let us figure out together how to push this issue forward. Connect with us through our slack channel : https://json-schema.org/slack
Thank you for your patience :heart: