Skip to content

Prudhvi-232/FOSS-Weekend-2024

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

13 Commits
 
 

Repository files navigation

FOSS-Weekend-2024

About

Equinox'24 presents a 3 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: 12:30 AM 15th March to 11:59 PM 17th March, 2024

Instructions

  • Kindly fork and clone the repos first, on which you have decided to work on.

  • You should create a new branch and do your work there, then the PR would be merging from your branch to repo's main branch.

  • 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.

Choose from a wide range of projects in Git, Web Development, Web3, App Development, ML, and Scripting.

Keep an eye on the leaderboard to see how you're faring against the competition.

Climb to the top of the leaderboard and win some amazing prizes!

Special Instructions for hard labelled issues:

  • If the issue has a hard 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. (You can ask for more time if you require it)

  • 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.

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.

MUST DO

Git Practice : Learn git for FOSS development, right from the fundamentals - https://github.com/iiitl/git-practice-weekend-24

Repos

  1. Web3 : A Real Estate Platform using Blockchain and Web Development - https://github.com/iiitl/Realty

  2. App Dev

  1. ML
  1. Web Dev
  1. Bash Practice - https://github.com/iiitl/bash-practice-repo-24 - A set of scripts which make your life easier in linux

Leaderboard

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published