Opensource@NITJ
Vol. 01
JUL 16, 2026
01 / PremiseFor builders, by builders

Building
Functional
Projects.

- Est. 2025Fetching public repositoriesOpen to all branches
02 / The Ledger

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.

Live Sync--:--:--
  • Fetching public repositories from GitHub...
03 / Active Spotlight

The
MUNSOC
website.

We are actively building the official web platform for the Model United Nations (MUN) Society of NITJ, establishing a modern digital home for their conferences and society activities.

Initiative · in progress

Building a bespoke web presence for the Model United Nations Society of NIT Jalandhar - delegates, registrations, archives, resources.

Status
Active
Stack
Next.js · Tailwind
Open issues
0
Good first
0
Visit WebsiteContribute
04 / Hall of Fame

The
Contributors.

Names on the masthead. Students, alumni and lurkers who shipped, reviewed, and maintained - listed in monospace, in no particular order.

05 / Activity

Recent
commits.

The latest public commits from repositories across the org...

github.com/Opensource-NITJ/commits
Fetching
  1. Fetching recent commits from GitHub...
06 / Sprints

Weekly
shipments.

A week-by-week editorial log documenting core features shipped, active sprints in progress, and planned cycles.

Select Cycle Issue
Sprint #2 Ledger
CYCLE WINDOW: Jun 28 – Jul 4

asknitj

↗
  • —refine context calls
  • —give structured data in the form of messages in chatCompletions for commentThreads and dMThreads

guessr

↗
  • —make the game playable by completing photo mode

osnitj-web

↗
  • ✓add sprints section to website
07 / Dispatches

Dispatches &
updates.

Technical posts, initiative updates, and reflections from the team.

08 / Manifesto

We don't ship demos.
We ship tools our campus
actually uses.

Principles
  1. i.Write code in the open. Pull requests over presentations.
  2. ii.Solve a real problem before naming the project.
  3. iii.Document for the freshers who will inherit it.
Your first PR
  1. 01
    Find a 'good first issue'

    Browse the index, open any repo, filter issues by the label.

  2. 02
    Fork & branch

    Clone, branch off main, write small commits, push to your fork.

  3. 03
    Ship it

    Open a PR, link the issue, accept review notes - and merge.

Open the GitHub org