├── .github ├── ISSUE_TEMPLATE │ ├── AddNewTipsandTricks.md │ ├── HackathonCriteria.md │ └── IssueFeatureBug.md └── images │ ├── After.png │ ├── Agenda.png │ ├── Asset 1@4x.png │ ├── Closing ceremony.png │ ├── Designer Coder Innovator.png │ ├── Explore.png │ ├── Game Off.png │ ├── GitHub Hackathons Logo.png │ ├── Hackathon Colours GitHub Logo - Pink.png │ ├── Judge.png │ ├── Time.png │ ├── files.md │ └── swag_shirts.png ├── CNAME ├── CodeofConduct.md ├── LICENSE ├── README.md ├── Resources.md ├── TipsandTricks.md ├── What-are-GitHub-Hackathons.md └── index.html /.github/ISSUE_TEMPLATE/AddNewTipsandTricks.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: ✨ Add/edit tip or trick 🔮 3 | about: 'Adding or editing a tip or trick' 4 | title: "✨ Request to add tip or trick to documentation 🔮" 5 | labels: add-tip, documentation 6 | assignees: MishManners 7 | 8 | --- 9 | 10 | Do you want to add a tip or trick or make a change to the documentation? Head to the [Discussions](https://github.com/github/hackathons/discussions) and ask your questions there 😄 11 | 12 | If it's something specific you don't want to ask the community, open an issue, but please start with the [Discussions](https://github.com/github/hackathons/discussions) first! 13 | 14 | Remember, this repository is designed for hackathon organisers and managers. It is not designed for participants. If your addition or change is not focused on organising or running a hackathon, then your tip/tricks probably won't be added to the documentation. 15 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/HackathonCriteria.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: 🤖 GitHub Hackathon Criteria ✔️|❌ 3 | about: 'Do you have a question about the GitHub Hackathon Criteria?' 4 | title: "Question ❓ regarding eligibility criteria " 5 | labels: 6 | assignees: MishManners 7 | 8 | --- 9 | 10 | Do you have a question regarding the eligibility criteria? Please make your question as detailed as possible. 11 | 12 | Please do not open an issue asking for an exemption from one or more of the criteria in order to showcase your hackathon. If your hackathon does not meet the criteria then you are not eligible to feature your hackathon on the GitHub Events site. Consider promoting your hackathon on some of the other sites mentioned in our [Resources](https://github.com/github/hackathon/blob/main/Resources.md) document. 13 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/IssueFeatureBug.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: ⚡ Issue, Feature, or Bug 🐛 3 | about: 'Use this to report an issue, feature, or bug' 4 | title: "⚡ Request to add tip or trick to documentation 🐛" 5 | labels: 6 | assignees: MishManners 7 | 8 | --- 9 | 10 | Is there something you'd like to flag to me. Is there any issues or bugs (probably not many bugs, unless there's a broken link somewhere). Do you have an idea or suggestion? Open an issue and I'll try and respond as soon as I can. 11 | 12 | If it's something you think the community can help you with, head to the [Discussions](https://github.com/github/hackathons/discussions) and ask your questions there 😄 13 | 14 | -------------------------------------------------------------------------------- /.github/images/After.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/github/hackathons/d04e0c3fe94a4d324e999b2a5d346af27a077889/.github/images/After.png -------------------------------------------------------------------------------- /.github/images/Agenda.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/github/hackathons/d04e0c3fe94a4d324e999b2a5d346af27a077889/.github/images/Agenda.png -------------------------------------------------------------------------------- /.github/images/Asset 1@4x.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/github/hackathons/d04e0c3fe94a4d324e999b2a5d346af27a077889/.github/images/Asset 1@4x.png -------------------------------------------------------------------------------- /.github/images/Closing ceremony.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/github/hackathons/d04e0c3fe94a4d324e999b2a5d346af27a077889/.github/images/Closing ceremony.png -------------------------------------------------------------------------------- /.github/images/Designer Coder Innovator.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/github/hackathons/d04e0c3fe94a4d324e999b2a5d346af27a077889/.github/images/Designer Coder Innovator.png -------------------------------------------------------------------------------- /.github/images/Explore.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/github/hackathons/d04e0c3fe94a4d324e999b2a5d346af27a077889/.github/images/Explore.png -------------------------------------------------------------------------------- /.github/images/Game Off.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/github/hackathons/d04e0c3fe94a4d324e999b2a5d346af27a077889/.github/images/Game Off.png -------------------------------------------------------------------------------- /.github/images/GitHub Hackathons Logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/github/hackathons/d04e0c3fe94a4d324e999b2a5d346af27a077889/.github/images/GitHub Hackathons Logo.png -------------------------------------------------------------------------------- /.github/images/Hackathon Colours GitHub Logo - Pink.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/github/hackathons/d04e0c3fe94a4d324e999b2a5d346af27a077889/.github/images/Hackathon Colours GitHub Logo - Pink.png -------------------------------------------------------------------------------- /.github/images/Judge.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/github/hackathons/d04e0c3fe94a4d324e999b2a5d346af27a077889/.github/images/Judge.png -------------------------------------------------------------------------------- /.github/images/Time.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/github/hackathons/d04e0c3fe94a4d324e999b2a5d346af27a077889/.github/images/Time.png -------------------------------------------------------------------------------- /.github/images/files.md: -------------------------------------------------------------------------------- 1 | Files used in the documentation are placed here. 2 | -------------------------------------------------------------------------------- /.github/images/swag_shirts.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/github/hackathons/d04e0c3fe94a4d324e999b2a5d346af27a077889/.github/images/swag_shirts.png -------------------------------------------------------------------------------- /CNAME: -------------------------------------------------------------------------------- 1 | hackathons.github.com 2 | -------------------------------------------------------------------------------- /CodeofConduct.md: -------------------------------------------------------------------------------- 1 | # ![Code of Conduct](https://user-images.githubusercontent.com/36594527/118597758-7cdfae00-b7f0-11eb-97c0-57131cbd9994.png) 2 | 3 | ## Our Pledge 4 | 5 | We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation. 6 | 7 | We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. 8 | 9 | ## Our Standards 10 | 11 | Examples of behavior that contributes to creating a positive environment 12 | include: 13 | 14 | * Demonstrating empathy and kindness toward other people 15 | * Being respectful of differing viewpoints and experiences 16 | * Giving and gracefully accepting constructive criticism 17 | * Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience 18 | * Focusing on what is best not just for us as individuals, but for the overall community 19 | 20 | Examples of unacceptable behavior by participants include: 21 | 22 | * The use of sexualized language or imagery and unwelcome sexual attention or 23 | advances 24 | * Trolling, insulting/derogatory comments, and personal or political attacks 25 | * Public or private harassment 26 | * Publishing others' private information, such as a physical or electronic 27 | address, without explicit permission 28 | * Other conduct which could reasonably be considered inappropriate in a 29 | professional setting 30 | 31 | ## Enforcement Responsibilities 32 | 33 | Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. 34 | 35 | Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate. 36 | 37 | ## Scope 38 | 39 | This Code of Conduct applies within all project spaces, and it also applies when 40 | an individual is representing the project or its community in public spaces. 41 | Examples of representing a project or community include using an official 42 | project e-mail address, posting via an official social media account, or acting 43 | as an appointed representative at an online or offline event. Representation of 44 | a project may be further defined and clarified by project maintainers. 45 | 46 | ## Enforcement 47 | 48 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 49 | reported by contacting the project team at opensource@github.com. All 50 | complaints will be reviewed and investigated and will result in a response that 51 | is deemed necessary and appropriate to the circumstances. 52 | 53 | All community leaders are obligated to respect the privacy and security of the reporter of any incident. Further details of specific enforcement policies may be posted separately. 54 | 55 | Community leaders who do not follow or enforce the Code of Conduct in good 56 | faith may face temporary or permanent repercussions as determined by other 57 | members of the project's leadership. 58 | 59 | ## Attribution 60 | 61 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, 62 | available at [Contributor Covenant](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html). 63 | 64 | [homepage]: https://www.contributor-covenant.org 65 | 66 | For answers to common questions about this code of conduct, see the [FAQ](https://www.contributor-covenant.org/faq). 67 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Creative Commons Legal Code 2 | 3 | CC0 1.0 Universal 4 | 5 | CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE 6 | LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN 7 | ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS 8 | INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES 9 | REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS 10 | PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM 11 | THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED 12 | HEREUNDER. 13 | 14 | Statement of Purpose 15 | 16 | The laws of most jurisdictions throughout the world automatically confer 17 | exclusive Copyright and Related Rights (defined below) upon the creator 18 | and subsequent owner(s) (each and all, an "owner") of an original work of 19 | authorship and/or a database (each, a "Work"). 20 | 21 | Certain owners wish to permanently relinquish those rights to a Work for 22 | the purpose of contributing to a commons of creative, cultural and 23 | scientific works ("Commons") that the public can reliably and without fear 24 | of later claims of infringement build upon, modify, incorporate in other 25 | works, reuse and redistribute as freely as possible in any form whatsoever 26 | and for any purposes, including without limitation commercial purposes. 27 | These owners may contribute to the Commons to promote the ideal of a free 28 | culture and the further production of creative, cultural and scientific 29 | works, or to gain reputation or greater distribution for their Work in 30 | part through the use and efforts of others. 31 | 32 | For these and/or other purposes and motivations, and without any 33 | expectation of additional consideration or compensation, the person 34 | associating CC0 with a Work (the "Affirmer"), to the extent that he or she 35 | is an owner of Copyright and Related Rights in the Work, voluntarily 36 | elects to apply CC0 to the Work and publicly distribute the Work under its 37 | terms, with knowledge of his or her Copyright and Related Rights in the 38 | Work and the meaning and intended legal effect of CC0 on those rights. 39 | 40 | 1. Copyright and Related Rights. A Work made available under CC0 may be 41 | protected by copyright and related or neighboring rights ("Copyright and 42 | Related Rights"). Copyright and Related Rights include, but are not 43 | limited to, the following: 44 | 45 | i. the right to reproduce, adapt, distribute, perform, display, 46 | communicate, and translate a Work; 47 | ii. moral rights retained by the original author(s) and/or performer(s); 48 | iii. publicity and privacy rights pertaining to a person's image or 49 | likeness depicted in a Work; 50 | iv. rights protecting against unfair competition in regards to a Work, 51 | subject to the limitations in paragraph 4(a), below; 52 | v. rights protecting the extraction, dissemination, use and reuse of data 53 | in a Work; 54 | vi. database rights (such as those arising under Directive 96/9/EC of the 55 | European Parliament and of the Council of 11 March 1996 on the legal 56 | protection of databases, and under any national implementation 57 | thereof, including any amended or successor version of such 58 | directive); and 59 | vii. other similar, equivalent or corresponding rights throughout the 60 | world based on applicable law or treaty, and any national 61 | implementations thereof. 62 | 63 | 2. Waiver. To the greatest extent permitted by, but not in contravention 64 | of, applicable law, Affirmer hereby overtly, fully, permanently, 65 | irrevocably and unconditionally waives, abandons, and surrenders all of 66 | Affirmer's Copyright and Related Rights and associated claims and causes 67 | of action, whether now known or unknown (including existing as well as 68 | future claims and causes of action), in the Work (i) in all territories 69 | worldwide, (ii) for the maximum duration provided by applicable law or 70 | treaty (including future time extensions), (iii) in any current or future 71 | medium and for any number of copies, and (iv) for any purpose whatsoever, 72 | including without limitation commercial, advertising or promotional 73 | purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each 74 | member of the public at large and to the detriment of Affirmer's heirs and 75 | successors, fully intending that such Waiver shall not be subject to 76 | revocation, rescission, cancellation, termination, or any other legal or 77 | equitable action to disrupt the quiet enjoyment of the Work by the public 78 | as contemplated by Affirmer's express Statement of Purpose. 79 | 80 | 3. Public License Fallback. Should any part of the Waiver for any reason 81 | be judged legally invalid or ineffective under applicable law, then the 82 | Waiver shall be preserved to the maximum extent permitted taking into 83 | account Affirmer's express Statement of Purpose. In addition, to the 84 | extent the Waiver is so judged Affirmer hereby grants to each affected 85 | person a royalty-free, non transferable, non sublicensable, non exclusive, 86 | irrevocable and unconditional license to exercise Affirmer's Copyright and 87 | Related Rights in the Work (i) in all territories worldwide, (ii) for the 88 | maximum duration provided by applicable law or treaty (including future 89 | time extensions), (iii) in any current or future medium and for any number 90 | of copies, and (iv) for any purpose whatsoever, including without 91 | limitation commercial, advertising or promotional purposes (the 92 | "License"). The License shall be deemed effective as of the date CC0 was 93 | applied by Affirmer to the Work. Should any part of the License for any 94 | reason be judged legally invalid or ineffective under applicable law, such 95 | partial invalidity or ineffectiveness shall not invalidate the remainder 96 | of the License, and in such case Affirmer hereby affirms that he or she 97 | will not (i) exercise any of his or her remaining Copyright and Related 98 | Rights in the Work or (ii) assert any associated claims and causes of 99 | action with respect to the Work, in either case contrary to Affirmer's 100 | express Statement of Purpose. 101 | 102 | 4. Limitations and Disclaimers. 103 | 104 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 105 | surrendered, licensed or otherwise affected by this document. 106 | b. Affirmer offers the Work as-is and makes no representations or 107 | warranties of any kind concerning the Work, express, implied, 108 | statutory or otherwise, including without limitation warranties of 109 | title, merchantability, fitness for a particular purpose, non 110 | infringement, or the absence of latent or other defects, accuracy, or 111 | the present or absence of errors, whether or not discoverable, all to 112 | the greatest extent permissible under applicable law. 113 | c. Affirmer disclaims responsibility for clearing rights of other persons 114 | that may apply to the Work or any use thereof, including without 115 | limitation any person's Copyright and Related Rights in the Work. 116 | Further, Affirmer disclaims responsibility for obtaining any necessary 117 | consents, permissions or other rights required for any use of the 118 | Work. 119 | d. Affirmer understands and acknowledges that Creative Commons is not a 120 | party to this document and has no duty or obligation with respect to 121 | this CC0 or use of the Work. 122 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ![Hackathon Logo](https://user-images.githubusercontent.com/36594527/117592199-10730800-b17b-11eb-84f8-4ffcae8116d4.png) 2 | 3 | #

JOIN A COMMUNITY CONNECTED BY CODE

4 | 5 | This repository contains Tips, Tricks, and Resources to help you plan, organise, and execute your hackathons. Hopefully you'll find these useful when planning your next hackathon. 6 | 7 | There are three main sections in this repository: 8 | 9 | 🔮 [Tips and Tricks](https://github.com/github/hackathons/blob/main/TipsandTricks.md) 10 | 11 | 📚 [Resources](https://github.com/github/hackathons/blob/main/Resources.md) 12 | 13 | 📣 [Discussions](https://github.com/github/hackathons/discussions/1) 14 | 15 | Guidelines are detailed below on how to contribute to each of these documents. If there are any issues within this repo you'd like to flag, please [open an issue](https://github.com/github/hackathons/issues/new?assignees=MishManners&labels=&template=IssueFeatureBug.md&title=%3Azap%3A+Request+to+add+tip+or+trick+to+documentation+%3Abug%3A+). 16 | 17 | ### Participating in a hackathon 18 | 19 | Please note this repository is **NOT** geared towards participants. This repository contains information and guides for hackathon organisers and managers. It does not contain tips, tricks, or resources for participating in a hackathon. 20 | 21 | If you are looking for a hackathon to participate in, and you want some guidance you can check out the following sites: 22 | - [Major League Hacking](https://mlh.io/) 23 | - [DevPost](https://devpost.com/) 24 | - [Hackathons International](https://www.hackathonsinternational.com/) 25 | - [Hackaday](https://hackaday.com/) 26 | - [DevFolio](https://devfolio.co/hackathons) 27 | - [Hack Club](https://hackathons.hackclub.com/) 28 | - [HackaList](http://www.hackalist.org/) 29 | - [AngelHack](https://angelhack.com/hackathons/) 30 | - [Hackathon IO](https://www.hackathon.io/) 31 | - [Game Jams](https://itch.io/jams) 32 | 33 | **Tip for organisers**: the above sites are great places where you can promote your hackathon! 34 | 35 | ## 🔮 [Tips and Tricks](https://github.com/github/hackathons/blob/main/TipsandTricks.md) 36 | 37 | The [Tips and Tricks file](https://github.com/github/hackathons/blob/main/TipsandTricks.md) contains lots of information on how to run your hackathon. Whether you're thinking about running an in-person, online hackathon, or hybrid hackathon, this document will help you answer some of your questions. 38 | 39 | You can [download](https://github.com/github/hackathons/files/6497549/GitHub.Hackathon.Tips.and.Tricks.2020.pdf) this document as a PDF. Feel free to use it, share it around, and consult it. 40 | 41 | ### Contribution Guidelines 42 | 43 | If you have new ideas you'd like to add to the Tips and Tricks document, please [head to the Discussions](https://github.com/github/hackathons/discussions/categories/tips-and-tricks) and start a conversation. If your tip or trick gets a lot of attention, we'll consider adding it to the documentation. 44 | 45 | When talking about tips and tricks, ensure your additions/changes include information that is useful for hackathon organisers. If your addition or change does not include enough information or is not geared towards hackathon organisers, then your change will probably not be included. Remember, this repository is for hackathon organisers, not participants. 46 | 47 | #### We're opted in for Hacktoberfest, so please feel free to contribute based on the guidelines here 48 | 49 | ## 📚 [Resources](https://github.com/github/hackathons/blob/main/Resources.md) 50 | 51 | Organisers are often looking for good resources for running their hackathons. The [Resources file](https://github.com/github/hackathons/blob/main/Resources.md) contains a list of useful resources for you to consult. There's everything from platforms to host your hackathon, promotion sites, judging recommendations, communication tools, and more. 52 | 53 | ### Contribution Guidelines 54 | 55 | If you would like to add a resource to the [Resources file](https://github.com/github/hackathons/blob/main/Resources.md), please [open a pull request](https://github.com/github/hackathons/pulls). Ensure your resource recommendation includes: 56 | - Name of the resource 57 | - Link to the resource (ie. website) 58 | - Short description of the resource 59 | 60 | See the [Resources document](https://github.com/github/hackathons/blob/main/Resources.md) to see how other resources are displayed. Please follow this format otherwise your pull request could be rejected. Ensure your resource is placed in the correct alphabetical order. 61 | 62 | Format for adding your resource: 63 | 64 | `[Name of the Resource in H2 format](with link to website)` 65 | 66 | `Short description, between two and four sentences long. Talk about what the resource is and how it can help organisers. Ensure the link above includes https instead of http.` 67 | 68 | `# you can add an appropriate gif, short video, or image if it suits. However, this is not necessary.` 69 | 70 | Remember, this resource is for organisers, not participants. If your resource is not for organisers and does not meet the requirements above, your pull request may be rejected. 71 | 72 | You can also [head to the Discussions](https://github.com/github/hackathons/discussions/categories/resources) to talk about certain resources before adding them to the documentation. 73 | 74 | ## 📣 [Discussions](https://github.com/github/hackathons/discussions/1) 75 | 76 | This is a great place to connect to other hackathon organisers. You can use the [Tips and Tricks](https://github.com/github/hackathons/discussions/categories/tips-and-tricks) or [Resources](https://github.com/github/hackathons/discussions/categories/resources) Discussions before adding content to this repository. You can also share [ideas](https://github.com/github/hackathons/discussions/categories/ideas), talk about [random things](https://github.com/github/hackathons/discussions/categories/general), or [ask questions](https://github.com/github/hackathons/discussions/categories/q-a). 77 | 78 | This is an open community so feel free to answer any of the questions in the Discussions, comment on other people's threads, and share your own ideas. Remember, constructive thoughts and feedback is good, just please always be mindful not to shut people down or discourage other members of the community. 79 | 80 | _______ 81 | 82 | #### Made with ❤️ by GitHub and friends 83 | 84 |
85 | 86 |
87 | -------------------------------------------------------------------------------- /Resources.md: -------------------------------------------------------------------------------- 1 | # ![Resources Logo2](https://user-images.githubusercontent.com/36594527/117616341-55fcf880-b1ae-11eb-8917-ef4f75ac48ba.png) 2 | 3 | Need some resources for your hackathon? Want some more tips and tricks? Check out all our resources below. This is by no means an exhaustive list. We hope you find it useful. Don't forget you can contribute to this repo via a pull request. 4 | 5 | Whether you’re running an in-person hackathon, online, or even hybrid, here are some useful tools and resources to help ensure your hackathon is a success. Remember, there are a number of places to promote your hackathon, so promote it in as many places as possible! Check out the [Readme file](https://github.com/github/hackathons/blob/main/README.md) in this repo for some great websites where you can promote your hackathon. 6 | 7 | Don't forget to read our own [Tips and Tricks document](https://github.com/github/hackathons/blob/main/TipsandTricks.md) for lots of information on running your hackathon. 8 | 9 | # Resources 10 | 11 | You'll find an alphabetical list of resources below. If you'd like to add your own resource to this document, you can. Simply [open a pull request](https://github.com/github/hackathons/pulls). Make sure you follow the contribution guidelines detailed below. 12 | 13 | ## [Accredible](https://www.accredible.com/) 14 | 15 | Certifying the participants or giving them digital badges of hackathon is hard enough. Luckily, with Accredible, you are covered. Accredible makes it easy to create beautiful, interactive, digital badges and certificates. This gives you many more features than a traditional paper certificate could: correct misspelled names on your own, download and print a PDF copy, or attach rich evidence like reports or video to substantiate your learning. 16 | 17 | ## [Awesome Hackathon](https://github.com/dribdat/awesome-hackathon/blob/main/README.md) 18 | 19 | The [Awesome](https://awesome.re/) project curates resources across the open source community, with thousands of lists that you and your participants will find useful to bootstrap their projects. [Awesome Hackathon](https://github.com/dribdat/awesome-hackathon/blob/main/README.md) is aimed at the organizers and participants of such events, keeping track of open platforms, tools, guidelines (like this one!) that can boost your event. And you are welcome to contribute your own links and guides to support this community effort. 20 | 21 | ## [Canva](https://www.canva.com/) 22 | 23 | Developing and executing a hackathon is hard enough without having to worry about branding, graphics, emails, and social media. Luckily, with Canva, you are covered. Get tonnes of graphics for your hackathon promo videos, presentations, social media, emails, and more. You can get started with [Canva's free tier](https://www.canva.com/pricing/), trial Pro for a free 30 days, or use your [GitHub Student Developer pack](https://education.github.com/experiences/virtual_event_kit) to get 12 months of Canva Pro Tier for free. 24 | 25 | ## [Code of Conduct](https://docs.github.com/en/github/site-policy/github-event-code-of-conduct) 26 | 27 | Nearly every event nowadays requires a Code of Conduct. If you are looking for a good basis to build your Code of Conduct, check out the [GitHub Event Code of Conduct](https://docs.github.com/en/github/site-policy/github-event-code-of-conduct) there's also the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/), another great place to start, as well as the [open source Code of Conduct](https://opensource.guide/code-of-conduct/). 28 | 29 | ## [Community in a box](https://github.com/orgs/community/discussions/86520) 30 | 31 | This resource shows you how to get started with using GitHub Discussions for your community. You might like to use GitHub Discussions for your hackathons; building a community, sharing knowledge, showcasing projects, and more. Community in a box will give you everything you need to enable Discussions for your organisation and how to get started. 32 | 33 | ## [DEV](https://dev.to/) 34 | 35 | DEV is a community of software developers. They help one another out, posting tutorials, information, and collaborating. DEV host an array of hackathons and is a great place to get lots of information on running a hackathon, or a great site to consider hosting your hackathon. The team hold plenty of collaboration hackathons, so if you're a company looking to run a developer focused or writing focused hackathon, then speak to the team at DEV. They'll do all the heavy lifting for you, and in return you'll have your participants creating a lot more content. 36 | 37 | ![6hqmcjaxbgbon8ydw93z](https://user-images.githubusercontent.com/36594527/117923859-2679f780-b338-11eb-83a9-aebd1f4f9bf1.png) 38 | 39 | ## [DevPost](https://devpost.com/) 40 | 41 | DevPost is known as the home for hackathons. Hackathons are featured on there, and there’s a whole host of tips and tricks on running hackathons too. Check out their page for best practices, and even how to promote a hackathon. This is also a great place to consider promoting your hackathon. 42 | 43 | ## [DevPost Expo](https://github.com/nealrs/expo) 44 | 45 | DevPost Expo is an open sourced tool for helping filter and distribute table numbers. If you’re running a science-fair, expo style presentation format this is the perfect tool. 46 | 47 | ## [Discord Hackathon Template](https://dis.gd/GHhackathon) 48 | 49 | Lots of communities run on Discord these days. If you are running a hackathon for a community that already has a Discord presence, you might want to think about adding a Hackathon Template to your Discord server. This template is designed specifically for hackathons. Give it shot. 50 | 51 | ## [Dribdat](https://dribdat.cc) 52 | 53 | Dribdat is an open source (MIT licensed) web application that assists teams working playfully on projects with data. Designed to support awesome hackathons, we think of it as a Swiss Army Knife for civic tech. Time-track your events, embed guidelines, put up digital signage, run a project log, progress tracker, integrate prototyping tools, GitHub repositories, open data APIs, and more. 54 | 55 | ![Dribdat](https://github.com/loleg/hackathons/assets/31819/68abae63-d953-4126-adaf-7c309d74e81e) 56 | 57 | ## [Envato](https://envato.com/) 58 | 59 | Envato is the digital marketplace for EVERYTHING. You can find lots of great resources for using in videos, making presentations, designing graphics, website templates, and heaps more. There’s lots of free content and some cheap assets as well. 60 | 61 | ![Envato3](https://user-images.githubusercontent.com/36594527/117928703-44972600-b33f-11eb-9ace-fd30d8929bc2.gif) 62 | 63 | ## [Gather Town](https://gather.town/) 64 | 65 | Are you running a virtual hackathon? Want a better way to engage your audience? Gather town is fun way to have virtual conversations, meetings, chats, and even large presentations. It's completely customisable, and super fun... like playing a video game and chatting to your friends. It's the perfect way to break people out of their comfort zone and they won't even feel like they are on a video call. 66 | 67 | ![ezgif-3-1378a7de7701](https://user-images.githubusercontent.com/36594527/117616530-98bed080-b1ae-11eb-8e01-bb3a96906ad7.gif) 68 | 69 | ## [Gavel](https://github.com/anishathalye/gavel) 70 | 71 | Gavel is an open sourced judging tool. It was originally built for a hackathon back in 2015 and has been used for heaps of events since then. It’s a great way to get participants voting for their favourite hackathons and can be used for a “People’s Choice” category. 72 | 73 | ## [GitHub](https://github.com/) 74 | 75 | Well, we can’t go past our own amazing developer platform! GitHub is a great way to collaborate on a project, track your progress, manage a project, and more. Check out how to get GitHub for free on our [GitHub Teams page](https://github.com/pricing). You can also check out our [GitHub Docs Pages](https://docs.github.com/) for heaps of information on using GitHub and how-to guides. 76 | 77 | ![banner-code-graph](https://user-images.githubusercontent.com/36594527/117921831-c3d32c80-b334-11eb-8bab-a423ac34272a.png) 78 | 79 | ## [GitHub Campus Experts](https://education.github.com/students/experts) 80 | 81 | If you’re a student running a hackathon, then why not see if you can get some money to help you out. Through our partnership with Major League Hacking, we offer students $1000 USD to help run a hackathon. Find out more on the [GitHub Campus Experts website](https://education.github.com/students/experts) and click “apply for hackathon grant”. 82 | 83 | ![opengraph-bbc921c34890fc1a76d65167838766b9adf12237a9f54354bcea2d4bbbf46e9e](https://user-images.githubusercontent.com/36594527/117616718-d4f23100-b1ae-11eb-96ee-a4d655f083db.png) 84 | 85 | ## [GitHub Classroom](https://classroom.github.com/) 86 | 87 | If you're a teacher or an educational institution looking to run a hackathon, look no further than GitHub Classroom. With Classroom, you get free access to Codespaces and lots of resources. You can manage assignments (or hackathon submissions) in your dashboard, grade hackathons automatically, and provide help to your students. 88 | 89 | ## [GitHub Issues](https://github.com/features/issues/) 90 | 91 | The new GitHub Issues allows users to manage projects. It's the ultimate tool for organising your hackathon and encouraging participants to manage their hackathon projects. Users can create issues, break them into tasks, track relationships, add custom fields, and more. There's ways to visualise projects as tables or boards, and automate everything with code. 92 | 93 | ## [Google Docs](https://www.google.com/docs/about/) 94 | 95 | There's lots of documents that go into event planning. Lists, spreadsheets, welcome packs, and more. The good thing is that multiple users of your team can collaborate and add some spices to the docs. You also can share these docs with edit/view access to your audience. It's very easy and secure. Explore it on [Google Docs Page](https://www.google.com/docs/about/). 96 | 97 | ## [Google Drive](https://www.google.com/intl/en_in/drive/) 98 | 99 | Use Google Drive as a communication and organizational tool to keep your organisation team on the same page. Don't bother emailing or dropboxing. Use one thing that does it all, from organising your hackathon, to sharing videos after the event. 100 | 101 | ## [Google Forms](https://www.google.com.au/docs/about/) 102 | 103 | Are you wanting to run a survey, collect information from participants, or encourage your participants to collect information for their projects, you can’t go past Forms. It’s free and super easy to use. GitHub now also allows you to [build HTML-like forms](https://dev.to/github/how-to-build-google-like-forms-with-github-3ig2) with the new [GitHub Issues](https://github.com/features/issues/). 104 | 105 | ## [Google Meet](https://meet.google.com/) 106 | 107 | There's going to be lots of meetings and meet-ups during any event. Google Meet have made this easy. Just join via a Google Meet link or create and share a meeting link with your fellow teammates or audience and have some fun. Explore it on [Google Meet Page](https://meet.google.com). 108 | 109 | ## [Hackathon Guide](https://hackathon.guide/) 110 | 111 | The hackathon guide was put together as a guide for running IRL (in person) hackathons. It's a great resource that walks through all the things to consider when running your hackathon, from emailing participants before the event, to booking locations, sorting out workshops, food, sponsorship, and more. 112 | 113 | ## [Hackathon Organiser’s Guide](https://guide.mlh.io/) 114 | 115 | This guide was put together by our friends over at [Major League Hacking](https://mlh.io). They have a lot of useful information on how to run community focused hackathons. There are some resources around budgets, volunteering guides, proposals, sponsorship decks, and more. A lot of the information is not only targeted towards community hackathons, but also very much towards student hackathons. You can even view, edit, and contribute to [this guide on GitHub](https://github.com/MLH/mlh-hackathon-organizer-guide/blob/master/README.md)! 116 | 117 | ## [Hackathon Queen](https://hackathongoddess.wordpress.com/) 118 | 119 | From GitHub’s own Hackathon Queen. Mish puts up lots of insights into hackathons, innovation, outcomes, and more. Check out her website for some great inspiration when you’re thinking about running your hackathon. 120 | 121 | ## [Hackathons International](https://www.hackathonsinternational.com/) 122 | 123 | Hackathons International is a global organisation, started in Melbourne. They have a whole host of hackathons on their website, from all over the world. This is a great resource if you’re looking to send your customers/clients to hackathons. There are opportunities for you to have your hackathon featured on the website. Their site also has a blog with lots of tips and tricks on running a hackathon. 124 | 125 | ## [HackerEarth](https://www.hackerearth.com/) 126 | 127 | HackerEarth lets you engage or source top developers with hackathons, while also enabling you to assess, interview and upskill them with ease. As a pioneer of conducting hackathons to drive business impact, HackerEarth has a huge amount of experience in conducting and managing hackathons at scale. You can host your hackathons towards a global community of 6 million developers. 128 | 129 | ## [Holopin](https://www.holopin.io/) 130 | 131 | This is a super cool place where developers can earn verifiable digital badges for skills, achievements, and all the amazing things you do. If you are running a hackathon, think about offering a Holopin badge to participants and place winners. It's a great way to help developers build their resumes. 132 | 133 | ## [IncubateIND](https://incubateind.com/) 134 | 135 | IncubateIND is India's largest and fastest-growing community of technology innovators including startups and student innovators. They are conducting lot of workshops, challenges and GitHub Externship program provides attractive stipends and hands on experience. 136 | 137 | ![inc](https://user-images.githubusercontent.com/71702982/119085250-ffe74b00-ba20-11eb-9db4-3c43b8e233d2.png) 138 | 139 | ## [Localist](https://www.localist.com/) 140 | 141 | Event management, marketing automation, and tonnes of analytics is what Localist is. There's custom branding and you can get a lot of insights about your community from the built-in data. It is designed specifically for community events. It's main appeal is the community calendar that allows you to display all the events coming up in your community. This is useful if you're running more than one hackathon and you want your community to see what's available to them. 142 | 143 | ![Localist2](https://user-images.githubusercontent.com/36594527/118575019-e6e45d00-b7c8-11eb-977b-4cde33c87700.gif) 144 | ## [Luma](https://lu.ma/) 145 | 146 | Worried about how the users will register for your online hackathon event and get notified? We've got you covered. Luma allows you to host delightful events and foster meaningful relationships with events, newsletters, and community analytics. 147 | 148 | ## [Major League Hacking](https://mlh.io/) 149 | 150 | Find out where all the awesome hackathons are running! There’s a whole bunch of resources, tips, freebies, and more on their website. It’s a must to check out if you’re running a hackathon. 151 | 152 | ![1_Q6GvThiNFFZByD00DJANVg](https://user-images.githubusercontent.com/36594527/117923877-2d086f00-b338-11eb-96c6-c392797dab9c.jpg) 153 | 154 | ## [Mentimeter](https://www.mentimeter.com/) 155 | Need a resource for doing great interactive presentations? As an organiser, this is an awesome platform. Use Mentimeter to run live polls, quizzes, word clouds, Q&As and more. Check out all the awesome things you can do to make your sessions more interactive. 156 | 157 | ## [Namecheap](https://www.namecheap.com/) 158 | 159 | If you're looking for a great domain hosting platform, you can't go past Namecheap. Choose from thousands of domain names to host your hackathon event page. If you have the [GitHub Developer Pack](https://education.github.com/experiences/virtual_event_kit) you can register one free .me domain name for 12 months. 160 | 161 | ## [Open Source Guide](https://opensource.guide/) 162 | 163 | This guide is mostly geared towards people launching Open Source projects, but there's a lot of great information on [building a community](https://opensource.guide/building-community/). This is also a really good resource to point your participants to at the end of the hackathon. The guide can be used if participants in your hackathon want to launch their projects after the hack. Alternatively, if you've discovered some really cool things during the course of organising your hackathon, you can open source your findings! This guide will be perfect for showing off the things you learned. 164 | 165 | ## [Party Space](https://www.party.space/) 166 | 167 | This platform for hosting virtual events is like playing a first person shooter. You walk around in the virtual space in FPS view and bump into other people. It can be a 2D or 3D space and has a super interactive feel. You can sit together with other people and watch videos, play games like Pacman, go to the bar, hang out in a room or just run around and explore the space. It's perfect in VR too. This would be a great platform for gaming hackathons. 168 | 169 | ![Party4](https://user-images.githubusercontent.com/36594527/118588437-bb21a100-b7e1-11eb-82e8-184bd50de5bb.gif) 170 | 171 | ## [Picsart](https://www.picsart.com/) 172 | 173 | Worried about creating a banner or social media image for advertising your hackathon? Fortunately, Picsart has you covered. It allows users to take and edit pictures and videos, draw with layers, and share the images on Picsart and other social networks. 174 | 175 | ## [Remo](https://remo.co) 176 | 177 | Another one for the virtual event orgainsers. Remo is a fully online and customisable virtual event experience. This really makes participants feel like they are at a physical hackathon. It has all the features of a real building; elevators, different floors, tables to 'sit' at, and places to watch larger presentations. It's perfect if you want to run with the 'weekend long' format in a virtual setting. 178 | 179 | ![Remo](https://user-images.githubusercontent.com/36594527/117923887-31348c80-b338-11eb-800f-fa1e75b71e24.gif) 180 | 181 | ## [Slack](https://slack.com/) 182 | 183 | The communication tool of this century! If you don’t have it, you need it. All your comms are easily accessible in one place. Use it to keep track of your organising team and it’s also a great platform for participants to connect and share knowledge. Slack is perfect for both online and offline hackathons. 184 | 185 | ![Slack](https://user-images.githubusercontent.com/36594527/117923901-3560aa00-b338-11eb-8f79-3e649a084671.gif) 186 | 187 | ## [Sparkle](https://sparklespaces.com/) 188 | 189 | There's definitely a lot more event platforms around now. Sparkle is an interactive and immersive space for running your virtual events. There are interactive maps, social venues, customisable spaces, chat, video, and more. It's super colourful and great for hosting a hackathon. 190 | 191 | ## [Splash](https://splashthat.com/) 192 | 193 | An event marketing platform that helps with all virtual, hybrid, and live events. It's mostly an event registration/management platform that pairs nicely if you're already using Zoom, YouTube live, etc. to run your virtual event. You can also use it for IRL events, just don't use the streaming part of it. Splash will help create all your marketing assets like event page, registration form, emails, branded live stream, check-in, stats and more. 194 | 195 | ## [Stack Overflow](https://stackoverflow.com/) 196 | 197 | If you've never heard about Stack Overflow this is the perfect time to get familiar. This is the place where developers come to learn together. The [Q&A Section](https://stackoverflow.com/questions) is probably what you'll want to look at the most. As an organiser, this is the perfect resource to point your participants to when they need answers on pretty much any developer question on the planet. 198 | 199 | ![Stackoverflow3](https://user-images.githubusercontent.com/36594527/117927116-1c0e2c80-b33d-11eb-95fa-2ae6505f2322.gif) 200 | 201 | ## [Streamyard](https://streamyard.com/) 202 | 203 | If you decide to host a virtual hackathon, and you are planning on having multiple presenters/presentations, Streamyard is a fantastic way to host your event. You can bring in multiple presenters on a screen, and it's a pretty good user experience for your speakers. If you have the [GitHub Student Developer Pack](https://education.github.com/experiences/virtual_event_kit), you'll get free access to the Streamyard Essential Plan while you are a student. 204 | 205 | ## [Unsplash](https://unsplash.com) 206 | 207 | This is the perfect place to find royalty free stock photos and images. They are great for promoting your hackathon, putting together event sites, and even using for slide shows. 208 | 209 | ## [Vercel](https://vercel.com/virtual-event-starter-kit) 210 | 211 | Vercel is a virtual event starter kit. It allows you to fully customise your event to your needs. It runs in any browser without additional downloads and is perfect if you are thinking of hosting a virtual hackathon with presentations and more of an 'event' flair. 212 | 213 | ## [Vevox](https://www.vevox.com/word-cloud) 214 | 215 | Vevox is an interactive word cloud generator, polling, and Q&A app that can be utilised to run live word cloud polls. It can be used in virtual hackathons to engage participants and increase collaboration. Creating and running a live word cloud poll can evoke excitement, and give the participants energy. People can see all their text responses appear on your presentation screen in front of them. 216 | 217 | ## [Zoom](https://zoom.us/) 218 | 219 | No doubt you’ve now heard about Zoom! It’s essential to use some sort of video conferencing tool when you’re running an offline hackathon with presentations and workshops. Zoom can be used for organisers to host and kick off a hackathon, as well as having participants dial in and present their ideas at the end. Depending on the format for your hackathon you might decide to limit interaction and leave people to their own devices. If you are interacting with people however, you can’t go past Zoom… just remember to set a password to deter “zoom bombers”! 220 | 221 | # Contribution Guidelines 222 | 223 | If you would like to add a resource to this document, please [open a pull request](https://github.com/github/hackathons/pulls). Ensure your resource recommendation includes: 224 | - Name of the resource 225 | - Link to the resource (ie. website) 226 | - Short description about the resource 227 | 228 | See the above to see how other resources are displayed. Please follow this format otherwise your pull request could be rejected. Ensure your resource is placed in the correct alphabetical order. 229 | 230 | Format for adding your resource: 231 | 232 | `[Name of the Resource in H2 format](with link to website)` 233 | 234 | `Short description, between two and four sentences long. Talk about what the resource is and how it can help organisers. Ensure the link above includes https instead of http.` 235 | 236 | `# you can add an appropriate gif, short video, or image if it suits. However, this is not necessary.` 237 | 238 | Remember, this resource is for organisers, not participants. If your resource is not for organisers and does not meet the requirements above, your pull request could be rejected. 239 | 240 | You can also [head to the Discussions](https://github.com/github/hackathons/discussions/categories/resources) to talk about Resources before adding them to this documentation. 241 | 242 | _____ 243 | 244 | #### Made with ❤️ by GitHub and friends 245 | 246 |
247 | 248 |
249 | -------------------------------------------------------------------------------- /TipsandTricks.md: -------------------------------------------------------------------------------- 1 | # ![Tips and Tricks Logo](https://user-images.githubusercontent.com/36594527/117604280-58ecee80-b198-11eb-854b-b75fe55d4343.png) 2 | 3 | So you want to run a hackathon? There are a lot of different types of hackathons you can run. Some are simply ideation sessions, others focus on the first stages of solving a problem, and others still are designed to teach people certain concepts, like human-centered design, particular tech stacks like JavaScript, or certain products like GitHub Actions. 4 | 5 | ## What is a hackathon 6 | 7 | Don’t believe the Hollywood movies! In general, a hackathon usually has nothing to do with “breaking into things”. Hacking refers to taking a problem or issue, breaking it down into its root cause, and finding a viable solution. 8 | 9 | A hackathon is a short competition where people work together in teams to solve problems and challenges by coming up with solutions and ideas. 10 | 11 | We know there are _lots_ of different types of hackathons. If you'd like to have your hackathon promoted by GitHub, you can submit a request to have your hackathon featured on our [GitHub Events page](https://github.com/events). If you'd like to do this however, your hackathon will need to align to specific criteria. Read about the criteria on our [What is a GitHub Hackathon](https://github.com/github/hackathons/blob/main/What-are-GitHub-Hackathons.md) documentation. 12 | 13 | ## Why would developers come to your hackathon? 14 | 15 | Developers love working on hackathons for a number of reasons. When it comes to coding, hackathons are a perfect way to practice skills and network with people. Here’s some of the reasons why developers go to hackathons: 16 | - Work on problems and solutions they care about 17 | - Build their CV/GitHub profile through creation of products 18 | - Learn and develop skills 19 | - Practice pitching 20 | - Network with people in an industry 21 | - Opportunity to work on/with great software, technology, datasets 22 | - Of course, people always appreciate any freebies and SWAG! 23 | 24 |
25 | 26 |

Participants love their SWAG. What can you offer?

27 |
28 | 29 | When creating a hackathon, you should think about what you can provide people as incentives to attend. How are you going to stand out and convince developers your event is a great way to spend their free time? 30 | 31 | ## What is the theme for your hackathon? 32 | 33 | Your theme could be very specific (ie. how to use AI to solve traffic congestion in a city) or it could be something more open (ie. how to unlock a city’s potential and increase urban mobility?) The less specific themes are often better as it opens up to outside the box thinking. The more narrow the topic, the more similar ideas you’ll get. If you want lots of different ideas for various things, then open up the theme. 34 | 35 | You don’t need to have a theme. Depending on your goals, simply having a “build something, anything, in 24 hours, and present the solution for review.” can be a good way of encouraging networking and building teams. These hackathons often have a “it has to work” theme rather than a specific problem to solve. This leaves the hackathon completely open to the participants to define their own problems and suggest a solution for it. 36 | 37 |
38 | 39 |

40 |
41 | 42 | It can be really great for encouraging new startup ideas, business ideas, and when trying to recruit people for innovative thinking. 43 | 44 | Other times you may want a theme, but still remember to keep it relatively broad. Themes like “MedTech”, “aged care”, “transportation”, or similar are great because they are very broad and can be taken in a lot of different contexts. Another example is the GitHub Game Off where the only guidance is that participants have to build a game. Other times you may want to narrow it down a little further. Slightly more narrow themes such as “How can we unlock a city’s potential?”, “how can we use machine learning in MedTech”, or “how can we use data X for the purpose of X industry?”. These are good because they are broad enough for people to interpret them, and narrow enough that desired outcomes are achieved. 45 | 46 |
47 | 48 |

GitHub's Game Off for example, only requires participants to build a game. There is no other criteria beyond this.

49 |
50 | 51 | Avoid having a hackathon around something very narrow. For example “build a real time strategy video game to inspire kids to do their homework”. This would ensure all the ideas are very similar, which is not what you want. 52 | 53 | Whatever theme you choose, whatever data sets, or technology you decide to have, it’s important to remember you’ll need mentors and experts there to help. For example, if you are using a data set that shows information around traffic congestion in the city, it’s useful to have someone from the transport industry to help explain the data. If you’re designing a hackathon to develop on a new blockchain platform, ensure the experts are available to help with that platform. Otherwise you’ll find participants will have questions that can’t be answered quickly and instead will either give up and go home. 54 | 55 |
56 | 57 |

Not sure where to start as a developer? Check out our handy guides and reference documentation you can use to start building.

58 |
59 | 60 | ## Is the event in-person or online? 61 | 62 | You’ll need to decide if this event is virtual (online) or physical (in-person). There are pros and cons to each type of event. Let’s take a look at what those are: 63 | 64 | ### In-Person event 65 | 66 | **Advantages:** 67 | - Build a great culture amongst people within the room 68 | - Motivate the participants with “hype” and “atmosphere” 69 | - People can easily learn from one another if in the same room 70 | - Allows for serendipitous encounters 71 | - Useful for short form events (ie. 5 hours up to a couple of days) 72 | - Easy to hold a “science-fair” style demo pit of all the solutions/ideas 73 | - People are more likely to participate while in the room due to “seeing” other people working 74 | - Help builds a collaborative culture 75 | 76 | **Disadvantages:** 77 | - Venue hire, food, and other physical location costs will need to be covered by fundraising 78 | - Need a good MC to tie everything together and keep the energy going and have in-person mentors available 79 | - Less people can potentially participate 80 | - People need to travel and therefore can exclude a number of people from attending. 81 | 82 | ### Online event 83 | 84 | **Advantages:** 85 | - Not limited by region, therefore you can open it up to have a lot more people participate 86 | - Barrier to entry is low; anyone with an internet connection can participate 87 | - Better for long form events; ie. a number of weeks 88 | - Easily recorded as you go 89 | - Heaps of online tools to help you 90 | 91 | **Disadvantages:** 92 | - Much harder to create “connection” and “atmosphere” in a digital only world 93 | - Participant networking is more difficult 94 | - Harder to coordinate people into teams 95 | - Harder to know if people need more help and to build connections with your mentors 96 | 97 | If you prefer graphical formats, you might like this table showing the above information: 98 | 99 | ![Format Table](https://user-images.githubusercontent.com/36594527/118071182-a2347c80-b3ea-11eb-9be2-9217a1f55790.png) 100 | 101 | ## What is the agenda of the hackathon? 102 | 103 | Now you have decided on online or in-person you also need to decide the type of format you want. 104 | 105 | These are some of the things you can consider implementing into your hackathon plan. 106 | 107 |
108 | 109 |

110 |
111 | 112 | ### Kick off 113 | 114 | The opening ceremony is your hype train. This is your opportunity to present to participants, sponsors, VIPs, and supporters about the hackathon. In the opening ceremony you can consider adding: 115 | - Welcome from a sponsor or VIP 116 | - Information around what the problem is or why you decided to run a hackathon 117 | - Information from sponsors 118 | - Tips and tricks for a successful hackathon from a participant’s point of view 119 | - Explain how the results will be judged (ie. presenting, judging, voting etc.) 120 | - Any team formation exercises if needed. 121 | 122 | ### Check in sessions 123 | 124 | Regular review periods where you focus attendees attention on what is happening and where people are at. This will help keep participants on track but sometimes is also an opportunity for teams to join resources or for people to swap teams if another solution sounds like something they would have more fun implementing. 125 | 126 | ### Workshops 127 | 128 | In a longer running hackathon, you might also hold workshops. Giving help on pitching, coding, design thinking, open source, maintaining projects, problem solving etc. All these workshops will not only upskill participants but will also help them develop good ideas and contribute to a successful hackathon. 129 | 130 | ### Closing ceremony 131 | 132 | Closing ceremony: whether online or in person, it’s great to close out the hackathon: 133 | - Presentation of idea 134 | - Judging of ideas 135 | - Presentation of prizes 136 | - Recap hackathon 137 | - Thank yous 138 | - Next steps (see below) 139 | 140 | Other things you might like to consider depending on budget and goals: 141 | - Food and drink breaks: mix groups up and allow them to network with a wider group of people 142 | - Yoga sessions (great for 24 hour+ hackathons) 143 | - Mini competitions: 144 | - Dance Central 145 | - Social media 146 | - Best memes 147 | - Massages 148 | - Video sessions: vox pops with participants, sponsors, organizers 149 | - LEGO Serious Play 150 | 151 |
152 | 153 |

154 |
155 | 156 | ## How long should the hackathon be? 157 | 158 | Most physical, in-person hackathons will be run over one to three days. This is due to the intense nature of physical events and the required energy from both participants and organizers. 159 | 160 | Virtual coding hackathons can last anywhere between a couple of days, and a few weeks. Think about what you’re trying to achieve and ensure you give participants adequate time to build out their ideas. 161 | 162 |
163 | 164 |

165 |
166 | 167 | ## What types of people will the hackathon suit? 168 | 169 | Even though GitHub Hackathons are about solving problems with technology, the most successful projects always have a diverse set of people involved. Even when it comes to coding, you don’t want all the same people in one team. For example, if you have all front-end developers, you’ll get lots of nice websites, but no back-end functionality. If it’s all coders then the design might be terrible, the documentation or video not understandable or the business idea not well thought through. 170 | 171 | Most hackathon goers would have heard of the terms coder, innovator, designer. These three terms refer to the different roles within a hackathon team (even a team of one). If you have the right mix of these three personas, you’ll have the perfect dream team! 172 | 173 | ### Who are these people and what’s their roles? 174 | 175 | **Coder:** your techies. Engineers and developers are your coders. They are the dev gurus and usually have good knowledge of many different tech stacks. A more technical focused hackathon might have multiple coders in the group, just like a product or service will have multiple developers working together. 176 | 177 | **Innovator:** your business and marketing people. They are the ones who validate ideas, understand the problem, research the market, and usually they’ll be the one presenting the final product. 178 | 179 | **Designer:** your creative type. Every project needs great design, from beautiful UI to UX. These people focus on the product itself and how it looks and feels to the customer. 180 | 181 |
182 | 183 |

Any one person could have multiple skill sets that cover multiple roles above. For a hackathon however where there is usually a short timeframe required, it’s best to pick one role and focus your efforts there. It can also be more beneficial to the team. This is because roles are clearly defined and the team will be able to deliver something faster.

184 |
185 | 186 | ## How should we ‘judge’ the ideas presented? 187 | 188 | First thing to note, not every hackathon needs to have judging. For example, the GitHub Actions Hackathon is more a “challenge” where participants completed the steps outlined. In this hackathons, there were no “winners”—simply participating and delivering a solution that met the criteria was enough to qualify for a reward. 189 | 190 | But a little light hearted competition can go a long way to motivate people. When it comes to coding, here’s some of the areas to think about judging. 191 | 192 |
193 | 194 |

195 |
196 | 197 | ### Considerations 198 | 199 | **Approachable:** is the code easy to understand and contribute to? 200 | 201 | **Solution usability:** is the end result easily used? It is utilising current tech stacks and practices? 202 | 203 | **Documentation:** how well has the team documented their solution? Is it easy to understand? Is there a README file to get people started? 204 | 205 | **Security:** is the code secure? Has the team thought about vulnerabilities and/or denial of service issues? 206 | 207 | ## What will you do at the end of the hackathon? 208 | 209 | So all the fun is over, now what? There’s a number of options for what to do after a hackathon. 210 | 211 | What you choose will depend on the reason for running the hackathon, what resources you have available, and what you’re able to do. Here’s some ideas of what you can do at the end of the hackathon: 212 | 213 | ### Present it 214 | 215 | Showcase the ideas in a public forum. Create a video, write a blog post, or have them on your website. Participants will be able to see the projects they created and tell their friends. Others in the community can see how successful your hackathon was. 216 | 217 | ### Share it 218 | 219 | Your hackathon was successful and new ideas were created, and problems solved. Why not celebrate that? Post about it on social media, share some highlights and more. 220 | 221 | Encourage participants to share on their channels, and to put their accolades on places like LinkedIn. For an example, check out the [GitHub Actions Hackathon blog post](https://github.blog/2020-04-09-featured-actions-from-the-github-actions-hackathon/). 222 | 223 | ### Showcase it 224 | 225 | Encourage participants to add their hackathon creations to their own LinkedIn and GitHub profiles. Using the “pin project” on each individual’s GitHub profile is a great way to showcase what’s been built. 226 | 227 | ### Incubate ideas 228 | 229 | Some people in the hackathon might like to continue to build on their ideas. If you have people who can help your participants take their ideas to the next level, do it! 230 | 231 | ### Implement concepts 232 | 233 | Encourage your participants who attended the hackathon to understand the concepts learned during the hackathon, Have them apply these concepts to everyday work life. Innovation, creativity, problem solving, critical thinking, teamwork, communication, and customer-centric thinking, should all become part of the way you work. 234 | 235 | ### Do another hackathon! 236 | 237 | Liked the hackathon? Then run another one! Some companies and teams run annual, half-yearly, and even mini-monthly hackathons. 238 | 239 |
240 | 241 |

242 |
243 | 244 | ## Tips and Tricks 245 | 246 | We hope these Tips and Tricks were useful. You can also [download this document as a PDF](https://github.com/github/hackathons/files/6497549/GitHub.Hackathon.Tips.and.Tricks.2020.pdf). Feel free to use it, share it around, and consult it. 247 | 248 | Don't forget to check out the [Resources documentation](https://github.com/github/hackathons/blob/main/Resources.md) for more tips and tricks, plus great tools that can help you as an organizer. 249 | 250 | ### Contribution Guidelines 251 | 252 | If you have new ideas you'd like to add to the Tips and Tricks document, please [head to the Discussions](https://github.com/github/hackathons/discussions/categories/tips-and-tricks) and start a conversation. If your tip or trick gets a lot of attention, we'll consider adding it to the documentation! 253 | 254 | When talking about tips and tricks, ensure your additions/changes includes information that is useful for hackathon organizers. If your addition or change does not include enough information, or is not geared towards hackathon organizers, then your change will probably not be included. Remember, this repository is for hackathon organizers, not participants. 255 | 256 | _____ 257 | 258 | #### Made with ❤️ by GitHub and friends 259 | 260 |
261 | 262 |
263 | -------------------------------------------------------------------------------- /What-are-GitHub-Hackathons.md: -------------------------------------------------------------------------------- 1 | # ![GitHub Hackathons](https://user-images.githubusercontent.com/36594527/118075399-4a4e4380-b3f3-11eb-8cd9-5196988ff25b.png) 2 | 3 | We know there are _lots_ of different types of hackathons. If you'd like to have your hackathon promoted by GitHub, you can submit a request to have your hackathon featured on our [GitHub Events page](https://github.com/events). If you'd like to do this however, your hackathon will need to align to specific criteria. Read on to find out more. 4 | 5 | ## What is a GitHub Hackathon 6 | 7 | GitHub Hackathons are focused on technology solutions, typically underpinned by code. Hackathons in general are focused on identifying problems and coming up with creative solutions, presenting a proof of concept or Minimum Viable Product (MVP) for that solution. 8 | 9 | Rather than creating new ideas, your hackathon could be a coding challenge. This is where a problem is presented and developers use code to solve the coding challenge. The problem could be “build a GitHub Action”, or it could be “solve these issues in a particular program”. Coding challenges are a great way to learn new technologies while working in a team, or individually. 10 | 11 | ## GitHub Hackathon Criteria 12 | 13 | To organize an event that qualifies as an official GitHub Hackathon, these are the things you need to implement: 14 | - The hackathon projects and ideas MUST be available in a public GitHub repository and published with a recognized open source license. When you create your code repository in GitHub, we help you pick a license or see [choose a license](https://choosealicense.com/) for more information. 15 | - The hackathon MUST enforce a code of conduct to help ensure the event is inclusive and welcoming to all. Codes of Conduct can vary for the type of hackathon. For an in-person event, something like the [GitHub Event Code of Conduct](https://help.github.com/en/github/site-policy/github-event-code-of-conduct) is a great start. For any open source repo, you’ll need a Code of Conduct, which can be found on the [Contributor Covenant](https://help.github.com/en/github/site-policy/github-event-code-of-conduct). 16 | 17 | If you have questions about the GitHub Hackathon Criteria, please [open an issue](https://github.com/github/hackathons/issues/new?assignees=MishManners&labels=&template=HackathonCriteria.md&title=Question+%E2%9D%93+regarding+eligibity+criteria+) and we'll try and respond as soon as possible. 18 | 19 | _______ 20 | 21 | #### Made with ❤️ by GitHub 22 | 23 |
24 | 25 |
26 | -------------------------------------------------------------------------------- /index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | GitHub Hackathons 4 | 5 | 6 | 7 | --------------------------------------------------------------------------------