Thank you for your interest in Indic Accelerationism. This is an open movement and every contribution matters -- whether you're a researcher, developer, policy analyst, designer, writer, or organizer.
in/acc is organized around seven pillars. Find the one that matches your skills:
| Pillar | You might... |
|---|---|
| Research Mediation (Anvikshiki) | Write literature reviews, synthesize data, produce evidence briefs |
| Design Proposals (Kalpana) | Draft technical specs, system architectures, UX designs |
| Policy Advocacy (Nitivada) | Analyze policy, draft recommendations, engage with institutions |
| Change Management (Yojana) | Plan rollouts, manage stakeholder communication, facilitate adoption |
| Build & Execution (Nirmana) | Write code, build prototypes, ship tools and platforms |
| Deployment & Operations (Vyavahara) | Set up infrastructure, maintain systems, monitor performance |
| Marketing & Consultation (Samvada) | Create content, grow the community, advise on strategy |
- Improve the Manifesto -- Refine language, add evidence, propose new sections
- Propose a Project -- Open an issue describing a new initiative aligned with in/acc goals
- Contribute Research -- Add to the knowledge base with studies, data, or analysis
- Build Something -- Prototype a tool or platform that advances an in/acc priority area
- Spread the Word -- Write about in/acc, share with your network, bring in new contributors
- Check existing issues to avoid duplicates
- Open a new issue with a clear title and description
- Tag it with the relevant pillar or project area
- Include context: what problem does this solve? Who benefits?
- Fork this repository
- Create a branch from
mainwith a descriptive name (e.g.,research/judiciary-ai-survey) - Make your changes -- keep commits focused and well-described
- Submit a pull request against
main - Describe your changes -- what you did, why, and how it connects to the manifesto or roadmap
Use the format pillar/short-description:
research/corruption-survey
design/smart-toll-architecture
policy/education-access-brief
build/case-prioritization-prototype
ops/community-infra-setup
marketing/launch-blog-post
- Be clear and direct
- Cite sources when making empirical claims
- Use inclusive language
- Keep the Indian context front and center, but draw from global knowledge
- Prefer concrete proposals over abstract commentary
- Be respectful -- Disagree on ideas, not on people
- Be constructive -- Critique should come with alternatives
- Be inclusive -- This movement is for all of India
- Be honest -- Acknowledge uncertainty, cite sources, correct mistakes
See the full Code of Conduct for details.
- Community chat: Join on X (Twitter)
- Questions: Open an issue tagged
question - New contributor? Look for issues tagged
good first issue
By contributing, you agree that your contributions will be released under the Unlicense (public domain).