10000 GitHub - AIT-TECHBOARD/hackathons: hosting hackathons details by - technical and engineering board AIT Pune
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

AIT-TECHBOARD/hackathons

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Technical & Engineering board AIT Pune-HACKATHONS, JOBS, EVENTS AND MUCH MORE

About Project

A website for checking upcoming Hackathons and events organized by the Technical & Engineering board AIT Pune-HACKATHONS. Participate, test your skills and learn alongside! More fuctionalities are bring added to make it better, contributions are most welcome.

How it works?

  • Visit our website.
  • You will be able to have a glance at all the Hackathons that the Technical & Engineering board AIT will be conducting throughout the year.
  • Read the description of the hackathon.
  • If it excites you then go ahead and click on the Register button.
  • Woah! you're good to go.

Contribution Guidelines

Stray Pull Requests are not accepted. Before you start working on the project, discuss the needed changes with the owners of the repository. You can ask the owners to assign you existing issues or raise new issues and wait for acceptance. Don't forget to star the repository.

How to contribute?

  • 💾Fork the repository: Look for the 'Fork' button in the repository pages

  • 💕Clone the repository: `git clone https://github.com/github_username/hackathons.git

  • 😎Code Blooded: Make changes to the project

  • 🗳Add the changes made to git: git add .

  • 📝Commit the changes: git commit -m "ENTER AN ATTRACTIVE COMMIT MESSAGE"

  • 👊Push the changes to the forked repository: git push origin master

  • 🙏Send your Pull Request (PR): After commiting go to the forked repository of your's and click on 'Pull request' and create one with an attractive name*

  • 🕤Wait wait and wait untill its approved or fix any bugs if markes

  • 🎉hurray! You did it!

Contribution Process

  • Make sure you have checked the existing website thoroughly before making any changes.
  • Comment on the issues to get assigned. If you don't find an issue aligned with your purpose, you can create a new issue and wait for the reply of the owners.
  • After getting assigned to a particular issue, fork and clone the project on your local machine and start working on the project.
  • Update the README.md file with details of your contributions.
  • Associate each Pull Request with the required issue number (mentioned at the side of every issue).
  • Always describe the changes you are making before sending the pull requests.

Contribution Practices

  • Please be respectful towards other contributors, do not comment on anyone's caste, gender, etc.
  • If a person is working or has been assigned an issue and you want to work on it please ask the assignee if he/she is working on it or if he/she wants to work together (only if the issue is big and could need another set of hands).
  • We are happy to allow you to work on your issues, but in case of long period of inactivity the issue will be assigned to another volunteer.
  • If you report a bug, please provide steps to reproduce the bug in a new issue.
  • If there is a UI related change, it would be great if you could attach a screenshot of the proposed changes so it is easier to get a quick review by the owner.
  • If the issue is too big to complete in given time frame, ask for the extension (the owner might/might not approve the extension after reviewing its need).
  • Good luck! If you get stuck anywhere, ask for help but do not give up.

Contributors List

Releases

No releases published

Packages

No packages published
0