Content Ops
For: Writers, Editors, Documentarians.
- Write documentation & tutorials.
- Create guides and blog posts.
- Proofread existing content.
Operations_Manual // V1.0
Contribution
Guidelines.
Welcome to Open Dev Society! We're building a vibrant community where everyone can contribute—not just developers. Whether you write code, create content, teach, or organize events, you belong here.
Code Ops
For: Developers, Engineers, Innovators.
- Fix bugs or implement features.
- Review Pull Requests.
- Improve performance & security.
Education Ops
For: Educators, Mentors, Trainers.
- Develop course materials.
- Lead workshops & sessions.
- Mentor newcomers.
Media Ops
For: Podcasters, Designers, Creators.
- Create podcasts & videos.
- Design logos & graphics.
- Create social media assets.
Event Ops
For: Organizers, Facilitators.
- Organize hackathons & meetups.
- Facilitate workshops.
- Moderate community channels.
Global Ops
For: Translators, Polyglots.
- Translate docs & sites.
- Localize UI elements.
- Adapt content for culture.
$ init_sequence --step=1
# Explore Our Projects
> Visit GitHub: OpenStock, OpenReadme, BookTrace...
$ connect_network --step=2
# Join Community
> Discord: [LINK_PENDING]
> Email: opendevsociety@gmail.com
$ find_task --step=3
# Look for labels:
- - "good first issue" (Newcomers)
- - "help wanted" (Expertise)
- - "documentation" (Writers)
$ execute_commit --step=4
# Submit Work
> Code: Pull Request
> Creative: Share via channels
$
Open & Transparent
Inclusive & Welcoming
Free & Accessible
Community-Driven
Quality & Impact
Respectful & Collaborative
Code of Conduct
All contributors must follow our Code of Conduct. Be respectful, welcoming, and report violations to opendevsociety@gmail.com.
We believe in celebrating contributions!
📜Public Credits
📣Social Shoutouts
🏅Badges
👕Swag / Merch
General Questions?
Open a GitHub Discussion or ask in Discord.
Found a bug?
Open an issue with the label 'bug' on the relevant repository.