The TECHTONIC FET fest will begin on May 27, 2019 and will conclude with a highly competitive hackathon on June 15, 2019.
This event is a XXXXX hosted organization wide event and will be conducted in three locations; Pune, Gandhinagar and Hyderabad
The last date for applying for the hackathon is June 10, 2019 Registration must be completed through the event website.
The participation in the event comes with a list of rules and regulations. Read the rules carefully to fully understand the code of conduct during the event. Any non-compliance in the rules will lead to direct disqualification from the event.
- Responsibility of the components and the materials used during the hackathon lies solely on the participating teams.
- Administrator reserves the right in their sole discretion to disqualify any individual it finds tampering with the entry process or the operation of the hackathon.
- Any act of violation of the official rules or anything inappropriate, unsportsmanlike, not in the best interests of this hackathon, or a violation of any applicable law or regulation will be dealt with strict actions.
- Only 10 teams in each location will be allowed to participate.
- The selection of the team will solely depend on the selection of the topic submitted
- A selection panel will scrutinize the topics sent for participation. Based on the selection criteria, the most distinctive topics will be selected for final participation. You will receive a mail once selected.
- Each team can have a mentor who must be grade 5 or above (4 + 1 team)
- The mentor will guide the team in ideation, planning, and perfecting the pitch
- The TechTonic team will try its best to accommodate employees who register as individuals in multi-member teams.
Pune – Participants will form a team of five members. A team can register with a minimum of 3 members, however, organizers will add two members to make it a 5-member team. The team must have at least 2 FET or Full stack developers.
Gandhinagar and Hyderabad - Employees in Gandhinagar and Hyderabad can form a team of no more than 3 members. The team must have at least 1 FET or Full stack developer.
- If you register as a team, the following technology rules will apply.
- If you register as an individual, the technologies applicable to the individual will be considered while allocating to an existing team.
The following technology criteria will be considered for participation:
- Typescript + Angular
- ES6+ ReactJS
- VueJS
- HTML5/CSS3
- SCSS/SASS
- Bootstrap/RWD
- jQuery, JavaScript, OOJS
- NodeJS
- .NET
- JAVA
- PHP
- PERL
Applications may integrate third-party SDKs, APIs, and services, provided the maker is authorized to use them.
- The participants must bring their own equipment such as a laptop, data dongle, and any other equipment necessary to prepare and be able to participate in the Hackathon.
- No network connection will be provided inside the premise.
- All the equipment will have to go through security check.
The team must build a working software application that runs on frontend technology and can be paired with the above-mentioned backend technologies. Do not build on top of old projects.
- The team must make the application available without any restriction, for testing, evaluation and for use by the judges following the event until the judging period ends.
- The topics for the articles will be reviewed beforehand to avoid any duplication.
- The team must make their application available for testing by Including a link to the application code on GitHub or BitBucket.
- The code repository may be public or private:
- If the repository is private, access must be given in the testing instructions provided with your submission.
The code will be used only for application review and testing. Include all deployment files and testing instructions required for testing the application.
All submissions remain the intellectual property of the individuals or team that developed them.
By submitting an entry or accepting any prize, you represent and warrant the following:
you will not submit content that is copyrighted, protected by trade secret or otherwise. subject to third-party intellectual property rights or other proprietary rights, including privacy and publicity rights, unless you are the owner of such rights or have permission from their rightful owner to post the content; and the content submitted by you does not contain any viruses, Trojan horses, worms or other disabling devices or harmful code.
The participant represents and warrants that they are the sole author and copyright owner of the submission and that the submission is an original work of the participant.
If the submission is a work based on an existing application, then the participant has acquired sufficient rights to use and authorize others; and that the submission does not infringe upon any copyright or upon any other third-party rights of which the participant is aware. The submission should be free of malware.
The judges will evaluate all eligible submissions on the following criteria:
- Creativity: Creativity and originality of the idea
- Technology: How well FET technologies were leveraged by the developer
- Impact: Extent to which the solution can be useful
- Scalability: Potential growth of the application
- Any disputes arising out of or in relation with the Hackathon shall be settled amicably
- Questions with respect to the Hackathon can be directed to the appropriate location contact: [email protected]
Team leader need to fork this repository, for more help please visit (https://help.github.com/en/articles/fork-a-repo) Rest of the team member can contribute to the forked repository.
- Don't commit any code in master repo, it will be not approved. Only commit the code in forked repository
- You can create multiple fork repository, and PULL request to common fork repository for review
- Only one repository will be considered for code review from the panel, multiple repository/branch will not be considered
Open sonar-project.properties file and update these properties before staring off the project.
sonar.projectKey=my:<PROJECT_KEY>
Where <PROJECT_KEY> will be team name and theme without space, however you can use _.
sonar.projectName=<PROJECT_NAME>
Where <PROJECT_NAME> will be short name of your project/theme.
XXXXX is just a facilitator of such events and will not hold any responsibility or accountability of any incident/accident/mis happening/IP or copyright infringement.
The attendance to the event will be at your own discretion.