-
Notifications
You must be signed in to change notification settings - Fork 556
DPG Contribution Readiness Framework
The aim of this framework is to provide support to DPG organisations to understand where they are in terms of readiness for community contribution. Hence, we have defined it as a list which details 6 key & 16 sub-elements that need to exist for a product.
| # | DPG Readiness Checklist |
| 1 | Documentation |
| 1.1 | Product set-up documentation available |
| 1.2 | Product ReadMe documentation available with basic details |
| 1.3 | Code Documentation with code coverage |
| 1.4 | DPG Architecture & design documentation present |
| 2 | Engagement with Community |
| 2.1 | Good First Issues listed across repos to enable contributors |
| 2.2 | Channel for communication/Forum for contributors
eg: Discord, GitHub, Stackoverflow |
| 2.3 | Detailed community guidelines for open-source contributors |
| 2.4 | Working Group Meetings/Forums with the community with MOM for public access |
| 3 | Project Management |
| 3.1 | Updated project Management Boards (Eg: JIRA, GitHub) |
| 3.2 | Public assigning of tickets (for internal & external team members) to ensure transparency |
| 3.3 | Availability of public product roadmaps & a defined interval |
| 4 | Usage of open licences like MIT & Apache. |
| 4.1 | Use open licenses to allow for code re-use by adopters |
| 5 | Contributor Community |
| 5.1 | Active Engagement by external contributors on GitHub Tickets |
| 5.2 | PRs raised across repos by external contributors |
| 6 | Adopters Network |
| 6.1 | Number of Adopters leveraging building blocks |
| 6.2 | Number of public-integrations of the repo libraries
(This will happen if the adopter is also public/open-source) |
We will be sharing the benchmark for each sub-element as well to help understand what needs to be done for each item to help ensure the DPG gets maximum contribution.
Copyright © 2024 | All Rights Reserved
Step 1 : Install the C4GT GitHub App - Please install this GitHub App in your product repositories so that we can access your repositories and track the C4GT tickets to make it automatically discoverable for the contributors.
Step 2 : Format existing/create new issue tickets - Use this COMMUNITY issue template Or DMP issue template to update existing or create new tickets that you want listed in the C4GT Community And DMP. The consistency of this template will improve the experience of the contributors to explore and comprehend your tickets. Note - For all tickets that are being updated/added as per the format. Please create a label called C4GT Community or DMP 2026 and tag all tickets with that label. This is key to making the tickets automatically discoverable.
-
2023
-
Projects
- ABDM
- AI Tools
- Avni
- Bahmni
- Beckn
- CARE
- Cord Network
- cQube
- DevDataPlatform
- DevOps Pipeline
- DIGIT
- Diksha
- Doc Generator
- FarmStack
- Glific
- Health Claims Exchange
- Karmayogi
- ODK
- Quiz Creator
- QuML
- Solve Ninja Chatbot
- Sunbird DevOps
- Sunbird Ed
- Sunbird inQuiry
- Sunbird Knowlg
- Sunbird Lern
- Sunbird Obsrv
- Sunbird RC
- Sunbird Saral
- Sunbird UCI
- Template Creation Portal
- Text2SQL
- TrustBot and POSHpal
- TrustIn
- Unnati
- WarpSQL
- Workflow
- Yaus
-
-
2022
-
Projects
- UCI Web Channel
- Admin for Sunbird RC
- UCI Signal Integration
- Centralised Access Control
- Competency Passbook
- Low-code Admin Console
- Workflow Management
- Machine Learning Platform
- URL Shortener (YAUS)
- Doc Generator
- Shiksha Postgres Adapter
- Shiksha CMS and Announcements Module
- Shiksha Frontend Restructuring
- Shiksha Design System
- Sunbird QUML Player
-
-
Organization & Mentors
-
Contributors
-
Organization & Mentors