Add what you wish you had found.

You do not need permission, and you do not need to be an experienced contributor. If you have notes, a solved lab, a clearer explanation or just spotted a mistake, that is enough to start.

Some courses have nothing in them yet.

A repository can exist and still be empty. These are the ones waiting for their first upload — if you took one of them, you already have what it needs.

Checking which courses are still empty…

Four steps, start to finish.

Find the right repo

Search the repository index by course code — CSE-201, MAT-163 — or by topic. Each course has its own repo; side projects live under Projects & Other.

Fork it and add your work

Fork the repo to your own account, then add your files. Notes, slides, solved labs, summaries, corrections — anything that would have helped you when you took the course.

Open a pull request

One topic per pull request keeps review quick. Say briefly what you added and which course or week it belongs to. A short description is worth more than a perfect commit history.

It gets reviewed and merged

We check that it is in the right place and readable, then merge. From that point on it is part of the archive, and the next student finds it in seconds.

Notes. Labs. Past work.
Better explanations.

There is no minimum size. A single corrected formula, a missing lab report, or a README that finally explains how to build the project — all of it counts.

Open an issue Propose a missing repository, or flag something that is wrong.
Send a pull request Upload notes, code, labs, solutions, or improvements.
Review someone else's Reading a pull request and saying "this helped" is contribution too.

Everything happens in the open.

There is no private channel to be let into — the organisation and its documentation are public, and you can always just write.

Pick a course you have already passed.

That is the easiest place to start — you already know what was missing. Questions, advice or a request? [email protected]