1. The DotNetNuke Hackathon is open to ANYBODY, ANYWHERE. To be eligible for the Grand Prize, an individual must have registered for a user account on this site before Wednesday, June 16, 2010 @ 9 p.m. Eastern Time. There is no advance registration requirement for other prizes.

2. In order to be eligible to win a Hackathon prize, you must follow these guidelines:

a) Hackathon Entry: Develop one or more new DotNetNuke modules ("Entry") during the scheduled Hackathon period per the specifications of one of the projects listed on the page: http://hackathon.in/Cities/DC/Projects.aspx 

b) Components, Plug-ins, Scripts etc.: Your modules may make use of third-party components, plug-ins, scripts, etc. as long as they have a license that permits free and unrestricted usage in both commercial and non-commercial settings. This includes MIT, BSD, GPL, LGPL, MPL etc. If in doubt, DO NOT use a component. Use of the Telerik components included with DotNetNuke is allowed as long as you use the DotNetNuke wrappers for the components. Even if you own a Telerik license yourself, you may NOT use the Telerik components directly from your code.

c) Installable Package: For each Entry, you must submit a standard DotNetNuke module ZIP file package so that it can be uploaded, installed and is functional on DotNetNuke Community Edition 5.4.1.

d) Source Code Package: For each Entry, you must submit a ZIP file containing the source code of your module. The source code must contain a Visual Studio 2008 or 2010 Project file and must include all dependencies (other than the DotNetNuke Core) needed to successfully compile.

e) License: Both ZIP packages MUST include an MIT license (http://www.opensource.org/licenses/mit-license.php). You, as an individual, must be the copyright owner (i.e. copyright ownership by non-person entities is not allowed). The Installable Package must include the MIT license in the manifest so that it is displayed to the user during module installation. The Source Code Package must include a License.txt file in the root folder that contains the MIT license. You must also follow all requirements regarding display of license for any third-party components, plug-ins, scripts etc. used in your entry.

NOTE: By submitting an Entry under an MIT License, you are retaining copyright of the submitted code, but giving any individual or entity the right to use your work in any manner as long as they retain notice of your copyright. If you do not want this, do not submit an Entry.

f) Disqualification Criteria: Your Entry will be instantly disqualified if your code does any of the following:

- DIRECTLY calls unmanaged code

- DIRECTLY reads or writes from the file-system to any folder other than the DesktopModules sub-folder where your module is installed or the home folder for the Portal where the module is being used.

- DIRECTLY reads, writes or executes any database object other than those created by your module

- MAKES a .NET or DotNetNuke API call that directly or indirectly adversely impacts the functioning of DotNetNuke or any other installed module

Basically, keep it clean.

3. In order to submit an Entry, you must send an email to hackathon@hypercrunch.com using the following guidelines:

a) Subject: The Subject of the email must contain the Title of your entry. This will be displayed in the Voting area so please keep it short but descriptive.

b) Body: The Body of the email must contain the following information:

- Required: Your first and last name

- Required: Description of your module in up to 200 words

- Required: Installable module package ZIP file named as follows: {FirstName}_{LastName}_{ModuleName}.zip

- Required: Module source code ZIP file (must compile) named as follows: {FirstName}_{LastName}_{ModuleName}_Source.zip

- Optional: YouTube link of a video (maximum 10 minutes) describing your module

- Optional: URL to a website page demonstrating your module. You should use every effort to "market" your module on this page. Use multiple pages if needed. Give the user a clear understanding of what your module does. If possible, have some user accounts pre-created that they can use to try out the module's functionality.

- Optional: 468px x 60px non-animated banner image for your module (displayed in Voting list)

- Optional: We encourage you to create a DotNetNuke Forge project for your Entry (http://forge.dotnetnuke.com). This will ensure that your Entry is discoverable by the DotNetNuke Community and you can manage its future on CodePlex. If you do create a DotNetNuke Forge project, please prefix the project title with "Hackathon: " so Hackathon entries are easy to find.

4. The deadline for receiving your Entry submission is Sunday, June 20, 2010 @ 7 p.m. U.S. Eastern Time. The time of submission is the receipt time recorded by our mail server. It is your responsibility that your Entry is received before the deadline.

5. You will receive a response confirming your "Official Submission Time" if you have followed all the instructions and everything is in order. For minor issues with content, we will use the time of first submission, even if you have to re-submit. For major issues (cannot install, incorrect license or missing etc.), we will request a re-submission and use the re-submission time as your "Official Submission Time."

6. If you have not provided a demo URL, we will install your module on an empty portal and give you administrator rights on this portal. You will need to configure your module and create a suitable demo experience so people voting on your module can have a good idea of what it does. Setting up the portal and granting you access will take time. We STRONGLY encourage you to provide a demo URL with your submission. If that's not possible, submit a YouTube video. Use the Hackathon-provided demo portal as an absolute last resort.

7. On Monday, June 21, 2010 @ 7 p.m. Eastern Time we will publish a list of Entries that were accepted for the Hackathon on this site. Each Entry will have its own page where a registered user may vote or comment.

8. Voting: Each Hackathon participant has 10 points which they may allocate as they wish to Entries other than their own. If you submitted an Entry, you MUST vote and allocate your 10 points to other Entries. If you do not allocate all your points, you are not eligible to win a prize. Each Entry page keeps a running tally of the number of points received by each Entry.

9. Voting ends on Wednesday, June 23, 2010 @ 7 p.m.  Eastern Time. All Entries will be sorted by number of points (highest to lowest), then by Submission time (earliest to latest). The Entry with the highest number of points and earliest submission time wins the Hackathon.

10. The Hackathon Winners will be announced Thursday, June 24, 2010 @ 12 p.m. Eastern Time. Winners will be announced for:

a. Grand Prize

b. Local Winner

c. Online Winner

Grand Prize and Online Winner Prize will be shipped directly to the Winner in the continental U.S. If a non-continental U.S. resident wins the Grand Prize or Online Winner Prize, he/she will need to provide a U.S. shipping address where prize will be shipped.