To earn your Hacktoberfest tee or tree reward, you must register and make four valid pull requests (PRs) between October 1-31 (in any time zone). PRs can be made to participating public repos on GitHub, those that have the Hacktoberfest topic. If a maintainer reports your pull request as spam or behavior not in line with the project’s code of conduct, you will be ineligible to participate. This year, the first 50,000 participants who successfully complete the challenge will be eligible to receive a prize.
-
Read the participation details to learn how to earn your Hacktoberfest tee or tree reward.
-
Those who have not registered yet for hacktoberfest can get themselves registered here .
-
All issues must be Resolved within 5 days time or the PR will be closed.
-
All the changes must be in accordance with clubs associated to BIT Mesra only.
This time around we have different prizes for the top 15 contributors who will be judged on the basis of points distribution criteria in each task!
-
First 15 contributors who have made pull requests in at least 3 mentioned tasks.
-
Winners will be selected on the basis of
- First come first serve (FCFS)
- QUALITY OF CODE
-
Points will be allotted for each task and highest scorers will be selected as winners. Marks distribution criteria will be mentioned in detail in respective task's
readme.md
-
All decisions made by IETE will be final and binding, no changes will be entertained after the result declaration.
- Implementing any of the features which are mandatory are important to mark your score in order to be eligible for prizes.
- Also resolving issues will add an extra benefit.
- Optional tasks:
- Contributing towards optional tasks will give you an edge and extra points.
- You can also create your own issue and get yourself assigned to it, this will be highly appreciated.
- Contributing towards making the website responsive.
Humble Request !important
All the enthusiastic contributors are requested to add their part carefully following the proper code block which is to be to be copy-pasted and then edited. Also, before sending a PR, it would be great if you yourself render the html page at least once to see how your changes are manifested. There have been instances where a single contribution destroyed the entire layout of the page, even affecting others' contributions.