-
Notifications
You must be signed in to change notification settings - Fork 352
How to participate as an organisation
- High ROI - Minimise effort & leverage the C4GT community for quality contributions.
- Community-Led Effort - Ensure sustainability & adoption with access to long-term contributors.
- Innovate - Conduct PoCs, new feature development & more through the community.
- Identify Talent - Create a talent pipeline through active contributors.
- DPG Visibility: Higher DPG visibility with a DPG Readiness Framework.
- Engage with Adopters - Connect with potential adopters who are a part of the community.
- Link Projects - Share a wide variety of project types with varying levels of complexity.
- Update Documentation- Ensure product documentation is up to date & easy to comprehend
- Engage Contributors- Be proactive, and engage on tickets & the community
- Incentivise Contributors - Consider paying contributors per ticket, and providing learning opportunities, certificates, and possible employment opportunities.
- Build Product Awareness- Feel free to use our Discord channel to build awareness around your product so that contributors can connect with your vision. This will lead to a higher number of contributions.
Please refer to the DPG Readiness Framework to understand the key requirements for a product to ensure maximum open-source contributions.
-
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 community ticket to make it automatically discoverable for the community.
-
Step 2 : Format existing/create new issue tickets - Use this issue template to update existing or create new tickets that you want listed in the C4GT Community. The consistency of this template will improve the experience of the community 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
and tag all tickets with that label. This is key to making the tickets automatically discoverable. In addition to this label, kindly also add one or more ofC4GT Bounty
,C4GT Coding
,C4GT Design
,C4GT Mentorship
and/orC4GT Advisory
depending on the kind of ticket for this. For example, if you wish to upload a coding related ticket that has a bounty amount attached to it, add the labelsC4GT Community
,C4GT Coding
&C4GT Bounty
to it. For design, mentorship and advisory tickets we require a 1 to 1 mapping for tickets and contributors. For the same, we request you to make a copy of this google form in your own drive and attach a link to it in the issue ticket for contributors to fill in. This way you will be able to see all the applications that come in and assign it to the selected contributor. We have also provided a proposal template that has been attached in the google form for interested applicants to use as a base. Feel free to make a copy of it and edit it to suit your needs better. -
Step 3 : View your ticket on the C4GT Community - All projects with the shared taxonomy once tagged to C4GT will be automatically listed on our C4GT Community for contributors to discover on the Community Projects Listing Page You can view the ticket and drive any communication/clarification with interested community members on your respective Discord product channel.
-
Step 4 : Ensuring the correct contributor gets C4GT points - C4GT Community Coding Projects have a single method for contributors to apply: through GitHub comments. Potential contributors can display their interest by commenting on a ticket. The organization will then assign the ticket to one of the applicants. After that the assigned contributor will raise a PR and the organization will merge it if it is of the required quality. If the organization deems the contributor is not active or of the required quality, the organization will need to unassign the ticket and can reassign it to someone else. C4GT Community Design, Mentorship and Advisory Tickets have 1 to 1 mapping of project to contributor. After going through the applications received in the google form attached to the ticket, you will have to assign the ticket to the selected contributor on Github and close the ticket. Please inform the C4GT team of who has been chosen and if they successfully complete the project, we will award them the points.
Note
- Join our Discord Channel using this Link
- Explore Projects on the C4GT Community Projects Listing
Copyright © 2024 | All Rights Reserved
-
2023
-
Products
- 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