FOSS-Weekend

About

Equinox'23 presents a 2 day long event FOSS Weekend presented by GitHub and Axios, where participants will get the opportunity to handle issues related to the technology that interests you and win exciting prizes from GitHub. This event will be a great chance for growing developers of 1st year to practice and brush up their skills in git, which is a very essential part of their learning journey.

Event Timeline: 00:00 AM 04th February to 11:59 PM 5th February, 2022

Instructions

• Create a pull request for the issues and/or instructions highlighted in the readme of the following projects.
• Try to complete the must do tasks before you move further, because they will give you a very good foundational knowledge about git by visiting the repositories, and looking through the issues.
• The issues are tagged easy, to hard depending on difficulty.
• You should try to start by trying to solve the easy issues before progressing to the harder ones.
• View the leaderboard at https://foss.pranavg.me (Leaderboard will be active once the event starts)

Special Instructions for to-be-assigned labelled issues:

• If the issue has a to-be-assigned label, ask for the issue to be assigned to you, and start working on it only after you recieve confirmation that you have been assigned. These issues will be assigned only to 3 participants on a first come first serve basis, and each of them will have to submit a PR fixing it within 3 hours from the time of assignment.

• Out of these 3 PRs, all satisfactory ones will be scored, and 1 or 2 may get a bonus for exceptional work. If all the PRs have roughly the same quality of content, the earliest submission may get a bonus. Bonus scores are at the discretion of the event organizers.

• If you realise after getting yourself assigned an issue, that you cannot work on it due to any reason, be sure to unassign yourself, to give a chance to others who may want to work on the issue. Also leave a comment informing everyone that this issue is again open to assignment.

Projects

Must do

• Learn git for FOSS development, right from the fundamentals - https://github.com/iiitl/git-practice-2023
• Add your participant profile JSON data - https://github.com/iiitl/Participants-API/issues/1

Web Development

• A small website using oMDb API to fetch movie details - https://github.com/iiitl/moviedb
• An API with data on all participants of IIIT-L Equinox's FOSS Weekend - https://github.com/iiitl/Participants-API
• A javascript simulation website which simulates the gravitational field of planets - https://github.com/iiitl/Planets
• A website which produces cool visual artworks - https://github.com/iiitl/Times-Table
• A travel website which provides information about various travel destinations - https://github.com/iiitl/Wanderlusters
• A clone of a portolio website of a famous visual designer - https://github.com/iiitl/Sean-Halpin-Portfolio
• A URL shortener website which shortens the links for you - https://github.com/iiitl/URL-Shortener
• A simple password generator - https://github.com/iiitl/Password-Generator

Android Development

- Flutter:

• An application to tell us a bit about yourself - https://github.com/iiitl/introduce-yourself-app
• An application which tries to predict your salary after your placements - https://github.com/iiitl/its-money

- Kotlin:

• A quiz application which will test your knowledge - https://github.com/iiitl/Binary
• An application which calculates your age which uses multiple views in android - https://github.com/iiitl/Age-Calc

Machine Learning

• A repository which will help you get started in Artificial Intelligence and Machine Learning - https://github.com/iiitl/ML_tutorial

Bash Scripting

• A set of scripts which make your life easier in linux - https://github.com/iiitl/Foss-BashScripting/

---

Good practices (must read before starting)

• Write clear and concise pull request descriptions: Explain the changes you made, and how they impact the project. You may add a SS, gif or a small video of your changes made if possible.
• Mention issue numbers: When creating a PR, reference the issue number (for eg: fixes #123) in your PR description which lets github know to automatically close the issue when your PR is merged.
• Use descriptive and concise commit messages: Summarize the changes made in each commit, including the issue number if applicable.
• Create separate branches for new features: create a new branch from main/master for each new features or bug fixes you are working on.
• Regularly merge from the main branch: To keep your branches up-to-date, regularly merge changes from the main branch into your feature branches.

Leaderboard