The flagship event of Techfest, featuring various repositories across different tech fields with diverse tech stacks! This event is for everyone—even if you are completely new to Git, we will guide you in making your first PR.
📅 10th April, 12:00 AM – 12th April, 11:59 PM, 2026
Points will be allocated and reflected on this leaderboard.
Note
Read the AI Usage Policy. We explicitly don't welcome the use of AI tools as assistants, but if you do, then remain fully responsible for your contributions. You must understand the code you submit, ensure it meets our quality standards, and explicitly disclose any AI assistance.
- Fork and Clone the repositories you want to work on.
- Create a new branch and work there before submitting a pull request.
- Submit a pull request that merges your branch into the repository’s main branch.
- Work on issues or follow the instructions mentioned in the README of the participating projects.
- Complete the must-do tasks first, as they provide a strong foundational knowledge of Git.
- Issues are tagged as easy, medium, and hard based on difficulty:
- Start with easy issues before progressing to harder ones.
- Choose from a wide range of projects in:
- Git
- Web Development
- Web3
- App Development
- Machine Learning (ML)
- Scripting
- Keep an eye on the leaderboard and compete for amazing prizes!
FOSS Weekend is a solo event focused on promoting open-source contributions. We have curated a list of repositories ranging from basic learning tasks to production-level code. Participants are tasked with contributing to these repositories to earn points and improve their development skills.
Points are awarded based on the difficulty of the Pull Request (PR). The difficulty is initially tagged on the issue, but FOSS Wing members may adjust the final score if the actual solution proves significantly harder or easier than expected.
| Difficulty | Description | Points |
|---|---|---|
| Basic | Basics (Bash practice, Git drills) | 5 pts |
| Very Easy | General repo fixes, very simple UI tweaks | 15 pts |
| Easy | Simple to implement UI tweaks and minor bug fixes | 30 pts |
| Medium | Feature implementation, logic fixes | 45 pts |
| Hard | Complex refactoring, core logic | 60 pts |
| Very Hard | Performance optimization, major features | 70 pts |
| Exceptionally Hard | Reimplementation or rewriting certain modules of large scale projects | 80+ pts |
It is not advisable to spend time on Exceptionally Hard unless you know what you are doing.
- Create an issue: 5 to 15 points based on quality.
- Penalty: Points will be deducted for useless or spam issues.
To ensure fair distribution of tasks:
- Type
/assignon an issue to be officially assigned. - Type
/unassignif you need to release your assignment. - Limit: You may be assigned to a maximum of 3 issues at the same time.
- You can only assign additional issues when your previously assigned issues are closed.
- If two participants already opened PRs before assignment, the third should wait for maintainer review.
- Legacy timing model mapped across all difficulties:
- Basic, Very Easy, Easy: 1.5 hours
- Medium: 3 hours
- Hard, Very Hard: 5 hours
- Exceptionally Hard: 8 hours
- No label: considered Medium (3 hours)
- Multiple-PR repositories: no time limit
If you have not finished within your time window but are close to a solution:
- Show active progress (Draft PR recommended).
- Request additional time from a maintainer.
- If no progress is shown or extension expires, the issue may be passed to the next person in queue.
Issues and PRs are managed with labels to indicate:
- Difficulty tags (Very Easy to Very Hard)
- Current assignment status (issues only)
- Heavy AI usage (PRs only, for metrics)
All contributions are reviewed and managed by FOSS Wing members. The difficulty of an issue or PR may be adjusted during the review process if the solution is found to be significantly easier or harder than initially estimated.
- Review the curated list of repositories.
- Identify an issue or create a new one.
- Use the
/assigncommand. - Submit your pull request within the applicable time limit.
To understand how we score you, please refer to our detailed rulebook: Rulebook.md.
✔ Write clear and concise pull request descriptions
- Explain the changes you made and their impact.
- Include screenshots, GIFs, or short videos if possible.
✔ Mention issue numbers
- When creating a PR, reference the issue number (e.g.,
fixes #123) to automatically close it when merged.
✔ Use descriptive and concise commit messages
- Summarize the changes made in each commit, including issue numbers if applicable.
✔ Create separate branches for new features
- Always create a new branch from
main/masterfor each new feature or bug fix.
✔ Regularly merge from the main branch
- Keep your branch up-to-date by merging changes from the main branch into your feature branch.
- Git-Repo-2026 - FOSS WING
- Bash-Repo-2026 - FOSS WING
| Repository | Owner | Tech Stack |
|---|---|---|
| Student-Hub | Om Swami | Next.js, TypeScript, MongoDB |
| Alumni | Om Swami | Next.js, TypeScript, MongoDB |
| MessEase | Ayush Yadav | Kotlin, Firebase |
| Repository | Owner | Tech Stack |
|---|---|---|
| PlanWise | Naman Khandelwal | Next.js, TypeScript, Prisma |
| Zonic | Naman Khandelwal | React, Node.js, Express |
| insane-vitepress | Aryan Singh | VitePress, Vue, Node.js |
| AlgoJudge | Aryan Singh | Rust, Docker |
| Opensource_Compass | Vedant Kulkarni | Next.js, Go, Docker |
| Breach Battle | Aaryan Dadu | Next.js, TypeScript |
| CargoCut | Sidharth Singh | Rust, PostgreSQL, Redis |
| StonkSchool | Sidharth Singh | Next.js, TypeScript |
| yt-music-tauri | Shivansh Jain | Tauri, Rust, JavaScript |
| NewTab-Overdrive | Shivansh Jain | Next.js, TypeScript, MongoDB |
| Cp_Discord_Bot | Shivansh Jain | Node.js, Discord API |
| ChatterBox | Mayank | Next.js, Go, MongoDB |
| Local-Link | Mayank | Next.js, Node.js, MongoDB |
| MissionSakhi | Arham | React, Firebase, Node.js, MongoDB |
| Repository | Owner | Tech Stack |
|---|---|---|
| OxiDock | Sidharth Singh | Tauri, Rust, React |
| PerOXO | Sidharth Singh | Rust, RabbitMQ |
| Shadowlock | Sidharth Singh | Rust |
| ScreenExtractor | Gaurav Ghodinde | Go, Python, Next.js |
| warp | Gaurav Ghodinde | Go |
| chuck | Aaryan Dadu | Python, C++ |
| cp-rs | Aryan Singh | Rust |
| anilist_moe | Shivansh Jain | Rust |
| pygame-arcade | Merin | Python, Pygame |
| Repository | Owner | Tech Stack |
|---|---|---|
| CodeForces | Kishan | Kotlin, Android SDK |
| Wanderlens | Kishan | Kotlin, Firebase |
| StocksApp | Md Anas Ali Usmani | Kotlin, Android SDK |
| Student-Hub-App | Naman Gulati | Kotlin, Firebase |
| Tap2Eat | Naman Gulati | Kotlin, Firebase, Node.js |
| CForge | Sandesh | Swift, SwiftUI |
| Repository | Owner | Tech Stack |
|---|---|---|
| Linear-Regression | Nishchal | Python, NumPy |
| Logistic-Regression | Nishchal | Python, NumPy |
| smartdoc-workshop | Rushil | Python, FastAPI |
| EDA-IPL | Sanjana | Python, Pandas |
| Decision-Tree | Vennela | Python, NumPy |
| K-Means-Clustering | Vennela | Python, NumPy |
| Neural-Networks | Vennela | Python, NumPy |
| Repository | Owner | Tech Stack |
|---|---|---|
| Drishya | Ishaan | Next.js, Solidity, Ethereum |
| whisper | Janmesh | Next.js, Solana, Rust, IPFS |
| Victory-Verse | Janmesh | React, Solidity, Hardhat, Ethers.js, IPFS |
| BountyRaffle | Kaustubh | Solidity, Foundry |
| decentralized-uptime-monitoring | Raj | Go, PostgreSQL, RabbitMQ |
| CTNFT | Aryan Singh | Next.js, TypeScript, Solidity |