Building
Functional
Projects.
Repositories,
in print.
A live ledger of every project under the Opensource@NITJ banner. Each row is a repository - public, hackable, and looking for hands.
- Fetching public repositories from GitHub...
The
CampusIn
rebuild.
The campus food delivery platform is moving off a closed website builder and onto a custom, scalable stack - designed, written, and operated by students. Public from day one.
Replacing the old website builder with a scalable platform built end-to-end by the community - orders, kitchens, riders, payments.
The
Contributors.
Names on the masthead. Students, alumni and lurkers who shipped, reviewed, and maintained - listed in monospace, in no particular order.
- Fetching contributors from GitHub...
Recent
commits.
The latest public commits from repositories across the org...
- Fetching recent commits from GitHub...
Blog &
updates.
Technical posts, initiative updates, and reflections from the team.
We don't ship demos.
We ship tools our campus
actually uses.
- i.Write code in the open. Pull requests over presentations.
- ii.Solve a real problem before naming the project.
- iii.Document for the freshers who will inherit it.
- 01Find a 'good first issue'
Browse the index, open any repo, filter issues by the label.
- 02Fork & branch
Clone, branch off main, write small commits, push to your fork.
- 03Ship it
Open a PR, link the issue, accept review notes - and merge.