Skip to content
OSSC badge
Apply
Recruitment is liveOpenSource Students Club · DBIT

Engineering beyond the classroom

Daily sessions in Ubuntu Linux, daily DSA, open source, AI agents

Mentored by a 10-member core team. Real pull requests, not slides. A fair score every month.

Apply nowHow it works
Checking registration statusDeadline announced on Discord.
  • Sessions: Daily, 4-6 PM
  • Where: Lab A-306 / A-228
  • Who: All branches, 1st-4th year
domain tracks
3domain tracks
core-team mentors
10core-team mentors
every working day
2 hevery working day
members confirmed per drive
~20-25members confirmed per drive

What you do here

Daily practice. Real pull requests. Monthly accountability.

A student-run technical club under the Department of Computer Science and Engineering. Daily two-hour sessions, three domain tracks, and every member scored individually each month.

Ubuntu-first engineering

Ubuntu is the working environment: native, dual-boot or WSL, so nobody has to repartition a personal laptop. Shell, permissions, processes and SSH are checked hands-on in the first month.

DSA every day

Daily problem sets on a defined syllabus, peer and senior mentoring, and internal contests. Solve in any language.

Open source in public

Git from week two, club projects in a public GitHub org, then upstream work: Hacktoberfest and mentored GSoC proposals.

Fair monthly evaluation

Published scoring on attendance, tasks, Git activity and initiative, with written feedback and appeal to faculty.

Hackathon teams

Trained teams for inter-college and national hackathons. High monthly scorers get priority and project ownership.

Room for juniors

A Linux and Git baseline comes first. 1st to 3rd sem start from programming fundamentals, so nobody is left behind.

Three tracks

Pick where you want to go deep

You are placed in a track after recruitment, based on interest and aptitude. Everyone shares the Linux and Git foundation first.

01 · 3 mentors

Data Structures & Algorithms

Daily DSA practice with a defined syllabus progression, peer mentoring, periodic internal contests. 3 core-team mentors own problem sets and competitive programming guidance. Solve in whichever language you are comfortable with.

  • Problem Solving
  • Contests
  • LeetCode
  • Codeforces
02 · 3 mentors

AI & Development

Python for AI, ML fundamentals, open-source AI models, LLM APIs and prompt design, and building AI agents - tool calling, retrieval, memory, orchestration.

  • Python
  • LLM APIs
  • AI Agents
  • Open Models
03 · 4 mentors

Core CS & Systems

Ubuntu Linux and shell, OS and networking, DBMS and SQL, frontend and backend development, containers, deployment and CI/CD. 4 core-team mentors.

  • Ubuntu
  • Git & GitHub
  • Frontend
  • Backend

How selection works

From registration to confirmed member

One application per student, open to every branch. The decision reaches you by email.

  1. 1

    Register

    Sign in with Google or an email code and fill in the form. You join the WhatsApp group straight after.

  2. 2

    Screening test

    Semester-wise: programming fundamentals for 1st to 3rd sem, DSA, DBMS and networks for 5th to 7th sem.

  3. 3

    Interview

    Where required, a short interview after the test.

  4. 4

    Provisional member

    You start the first month with everyone else: Ubuntu, Git, and your first pull request.

  5. 5

    Confirmed on merit

    The first monthly evaluation confirms around 20 to 25 members. Scoring continues every month.

Your first month

What the first four weeks look like

Induction starts on day one. After that, every member is scored monthly on attendance, tasks, technical progress, Git activity, initiative and collaboration.

  1. Week 1

    Orientation, Ubuntu and the shell

    WSL or Ubuntu setup, filesystem, core commands, permissions, processes, shell basics and SSH keys.

  2. Week 2

    Git, GitHub and your first PR

    Branches, commits, merges and pull requests. Every member lands a first internal PR and sets up a GitHub profile.

  3. Week 3

    Open source and track kickoff

    Licences, issues and reading unfamiliar codebases. A practical Unix check, then domain tracks begin.

  4. Week 4

    Track work and evaluation one

    Full DSA, AI or systems work and the first internal contest, then the first monthly evaluation.

Questions

Before you apply

Who can apply?

Any DBIT student, from every branch and 1st to 4th year. First years give their college registration number because the USN is allotted later.

What is on the screening test?

It depends on your semester: programming fundamentals for 1st to 3rd sem, and DSA, DBMS and networks for 5th to 7th sem.

Do I need a laptop with Linux?

Bring a laptop if you have one. Ubuntu is the working environment and the team helps you set it up natively, as a dual-boot or through WSL in the first week, so you do not have to repartition anything.

When and where are sessions?

Daily on working days, 4:00 PM - 6:00 PM on working days, in Lab A-306 or Lab A-228.

What happens after I submit?

You are taken to the WhatsApp group for announcements. The core team reviews applications after the registration drive, and the decision reaches you by email.

Can I edit or withdraw my application?

You can update it until a reviewer has made a decision. You can withdraw at any time from the My application page, which deletes it.

How are members evaluated?

Every month, on attendance, tasks, technical progress, Git activity, initiative and collaboration, with written feedback and appeal to faculty. The first evaluation turns provisional membership into confirmed.

Something else? Ask on Discord.

Checking registration status

Sign in. Register. Show up daily.

Questions first? Ask the core team on Discord before you apply.

Apply nowJoin Discord