Campus tools that just work.
Attendance, notices, resources — the everyday machinery that keeps a college running. We make it work better, faster, and less painful for the students who use it every day.
VOSS / 2026 Vidyalankar Institute of Technology, Mumbai
Open Source Software Labs
A student-run open-source lab at Vidyalankar Institute of Technology, Mumbai. We build real digital infrastructure for the college — collaboratively, transparently, and in public.
// CONTRIBUTING.md
// How to join VOSS
if (you.shipCode()) {
you.areIn = true;
you.role = "contributor";
}
// No forms. No interviews. Just commits. The Manifesto
Not a club. Not a committee. A lab where students build things that actually get used.
VOSS · Founded April 2026 · Mumbai, IN
01 — What We Do
We fix what's broken.
We identify the most broken, manual, and painful systems at Vidyalankar — and we fix them with software. Every project is open source, publicly maintained on GitHub, and built for daily use.
Dashboards departments want to use.
Internal portals that load fast, look clean, and ship features users actually requested. Built with the people who will use them, not for a brochure.
Tools to build the tools.
CLI utilities, GitHub bots, CI pipelines, and documentation generators that make the lab itself more productive. Meta-infrastructure, public from day one.
02 — Shipped
Things we've built.
Live repositories under github.com/voss-labs. Pulled fresh on every deploy. Star,
fork, or contribute — every one is open source.
03 — Join
No applications. No interviews.
No forms, no committees, no gatekeepers. You contribute, you're in.
- 01
Browse open issues
Look across our repositories. Filter by
good-first-issueif you're new. - 02
Pick something that fits
Match it to your skill level.
good-first-issuefor beginners,intermediateoradvancedfor the rest. - 03
Fork, build, submit a PR
Set up locally, build your solution in a feature branch, open a pull request with a clear description.
- 04
Get reviewed and merged
We review within 48 hours. Once merged, you're a contributor.
Your GitHub contribution history is your membership card.
Explore Repositories 04 — Standards
Every project follows the same baseline.
Consistency scales. Newcomers find the same shape in every repo.
01
MIT License
Permissively licensed. Anyone can use, fork, or build on what we ship.
02
Clear README
What the project does, how to run it, and where to find help — at the root of every repo.
03
CONTRIBUTING.md
Setup instructions and contribution guidelines included from day one.
04
Labeled Issues
good-first-issue, intermediate, advanced, bug, feature, docs.
05
Branch Protection
All changes to main go through pull requests with at least one review.
06
Public Discussion
Design decisions happen in issues and PRs. Nothing important happens off-platform.
05 — People
A flat, contribution-based structure.
No elected positions. Your commits are your credentials.
06 — Principles
Four non-negotiables.
The rules that guide every decision we make.
01
Ship over talk
Working code beats perfect plans. Merge early, iterate often.
02
Open by default
Every line of code is public. Every decision is documented. No private repos, no closed meetings.
03
Merit over seniority
A first-year who ships outranks a final-year who doesn't. Year of study and CGPA are irrelevant here.
04
Problems first
We build what Vidyalankar actually needs, not what looks good on a poster.
07 — Begin
Two paths in.
Pick the one that matches where you are. Both end at the same place.
New to open source
- Read the
CONTRIBUTING.mdin the project you're interested in - Set up the project locally following the README
- Pick a
good-first-issue— these are scoped specifically for first-time contributors - Ask questions in the issue thread or on Discord if you're stuck
- Submit your PR — we review within 48 hours
Done this before
Skip the training wheels. Browse any open issue labeled intermediate or
advanced, comment to claim it, and start building.
We trust you to read the codebase, follow conventions, and open clean PRs.
View all issues →