>>> AFTER REVIEWING THESE RULES, YOU MUST register on the codeLinc MSU Registration Site <<<

WHAT AND HOW DO I SUBMIT? 

By 12:00 p.m. EST April 16, 2022, Registrants must submit a project packet including the application, a link to the working source code, the application login credentials, a written description and a brief demonstration (the “Entry”). 

Each Team may submit only one Entry.

Registrants will be provided with a URL to the third-party vendor website or provided an email address to submit their Entry. 

Before initiating the submission process, Registrants may be required to register and/or create a profile on the third-party site and to agree to the terms and conditions of the vendor site. Upon completion of the registration process, Registrants will be able to submit their Entries. 

WHAT IS REQUIRED OF THE PROJECT? 

Each Entry shall consist of a development project as outlined in the Project Templates provided. It is permissible to use open-source development tools. The application should not contain any third- party proprietary code and it is Registrant's responsibility to ensure that the submission does not infringe or violate any third-party rights or laws. Additional development resources will be made available to Registrants throughout the competition. If the solution employs components or plugins incurring future licensing costs, these must be prominently documented.

The application each Registrant submits must: 

• be an application or other programming project in alignment with the project templates provided; 
• have been developed solely as part of this Challenge; 

• be the sole work of the Registrant; 
• be submitted in English;
• be a completed solution or working application at time of submission; and comply with these Official Rules. 
• A full project submission should require all of the following:
• All source code via a link to GitHub or another repository. Your code repository can be public or private. If your repository is private, access must be given to codeLinc@lfg.com and indicated in the documentation.
• Any needed technical documentation including links to a description of 3rd-party frameworks employed

GENERAL STANDARDS FOR ENTRIES 

The intent and spirit of the Challenge is to encourage Registrants to develop innovative technical solutions that solve the challenge presented.

In addition to the content and technical requirements listed earlier, to be eligible for judging, all Entries must meet the following general standards: 

• All Entries must be presented and submitted in English. 
• The content of your Entry and any supporting materials must be acceptable for all viewing audiences. We will automatically disqualify any Registrant that submits an Entry or supporting materials that contain data, code, text, sound or images that We, in our sole opinion and for any reason, believe to be malicious, illegal, vulgar, offensive, or inappropriate for public viewing, or that presents us in a negative light. 
• By submitting an Entry in this Challenge, you represent:  
• That your team and the Entry submitted complies with these Official Rules; 
• That the entirety of the Entry is your team’s original work; and 
• That your team has obtained any and all consents, approvals, or licenses required for you to submit your Entry, and that your Entry will not violate anyone else’s rights or the law. 

HOW MANY ENTRIES MAY I SUBMIT? 

Each Team may submit only one Entry.

SUBMISSION MODIFICATIONS

a. Draft Submissions: Prior to the end of the Hackathon Submission Period, you may save draft versions of your Submission on Devpost to your portfolio before submitting the Submission materials to the Hackathon for evaluation. Once the Submission Period has ended, you may not make any changes or alterations to your Submission, but you may continue to update the project in your Devpost portfolio.

b. Modifications After the Hackathon Submission Period: The Poster may permit you to modify part of your Submission after the Submission Period for the purpose of removing material that potentially infringes a 3rd-party mark or right, discloses personally identifiable information, or is otherwise inappropriate. The modified Submission must remain substantively the same as the original Submission with the only modification being what the Poster permits.

PRIZE CONDITIONS: 

Your odds of winning a prize will depend on the number of eligible Entries received, the quality of the Entries, and the level of skill of the Registrants. If your team is confirmed as a winner: 

• You may not designate someone else or another team as the winner; 
• You agree to provide Us with the legal name, address, and social security number/tax ID as well as other information requested for tax reporting purposes, of each Participant; 
• If your team accepts a prize, you and each team member agrees to self-report to applicable taxing authorities, as may be required by applicable laws, and will be solely responsible for all applicable taxes and costs related to accepting and using the prize; and 
• You and team members will participate in media interviews as requested by us. 

Prize monies should be retained by individuals only in conformity with any applicable policies of his or her employers regarding participation in and receipt of promotional consideration relating to the Challenge and receipt and retention of prize. If an employer’s policies are applicable, it is the Registrant's sole and ultimate responsibility, in consultation with his or her government, employer or school, to determine how and if prize will be retained and/or distributed and accounted for and we assume no responsibility for the decisions made by such government, employers or schools regarding this issue. 

If you are selected as a winner, We may require you to sign an Affidavit of Eligibility, Liability and Publicity Release and W-9 tax form (for U.S. residents). 

HOW WILL ENTRIES BE JUDGED? 

For the judging, the team’s full submission packet must be submitted and posted to the codeLinc devpost site no later than 12pm EST on April 16, 2022. Scoring criteria are visible under the rules tab.

The winning Entries will be announced immediately following team presentations.