├── README.md ├── judging ├── Peer judging model.md ├── README.md └── community_voting.md ├── outline.md ├── safety.md └── theme ├── README.md ├── build_that_one_project.md ├── random_word_tournament.md └── wacky_and_hacky.md /README.md: -------------------------------------------------------------------------------- 1 |

2 | 3 | On December 30th 2022, 180 hackers from around the world travelled to the Delhi NCR for Epoch — a 42-hour high-school hackathon over New Year's. With clubs & hackers in 130+ countries, Hack Club is a truly global community. After many magical summer events in the USA, Epoch was Hack Club's first flagship event outside of the United States. The Hack Club community came together to organise Epoch, the goal of this repository is to document that journey for future organisers to reference. 4 | 5 | ## 💬 Public Slack Channels 6 | 7 | Epoch was organised in public on the [Hack Club Slack](https://hackclub.com/slack) by dozens of Hack Clubbers. We've kept them open for your exploration. Looking through them will give you insight into the challenges we faced and how we overcome them. 8 | 9 | | Channel | Purpose | 10 | | ------- | ------- | 11 | | [`#epoch-bts`](https://hackclub.slack.com/archives/C044HSLSU06) | Everything & anything related to organising Epoch. | 12 | | [`#epoch-food-n-fun`](https://hackclub.slack.com/archives/C048947LXHD) | Coordinating meals and side activities. | 13 | | [`#epoch-swag-n-prizes`](https://hackclub.slack.com/archives/C048S4EMQE8) | Designing & sourcing swag as well as selecting & purchasing prizes. | 14 | | [`#epoch-theme-n-judging`](https://hackclub.slack.com/archives/C048S4F1C9J) | Planning for Epoch's theme selection and judging process. | 15 | | [`#epoch-workshops`](https://hackclub.slack.com/archives/C048PL8PRLJ) | Organising workshops for Epoch. | 16 | | [`#epoch-suppliers`](https://hackclub.slack.com/archives/C04EMQG47B5) | Sourcing supplies & swag from distributors / manufacturers. | 17 | | [`#epoch-satellites`](https://hackclub.slack.com/archives/C04BQJ3PXNW) | Organising a series of smaller Epoch satellite events in the USA. | 18 | | [`#epoch-cross-event-activity`](https://hackclub.slack.com/archives/C04G5EMGERF) | Coordinating an escape room-esque event for all Epoch events to participate in, together. | 19 | | [`#epoch-vt`](https://hackclub.slack.com/archives/C04BX4F6HGE) | Organising a Epoch satellite hackathon in Shelburne, VT, USA. | 20 | | [`#epoch-ba`](https://hackclub.slack.com/archives/C04AKL9UKEY) | Organising a Epoch satellite hackathon in Oakland, CA, USA. | 21 | | [`#epoch-texas`](https://hackclub.slack.com/archives/C04CGDDLC72) | Organising a Epoch satellite meetup in Austin, TX, USA. | 22 | 23 | ## 📌 Within This Repository 24 | 25 | | Document | Description | 26 | | ------- | ------- | 27 | | [`outline.md`](/outline.md) | Epoch's vision, budget, staffing, and problem statements. | 28 | | [`safety.md`](/safety.md) | Epoch's general safety and COVID-19 policies / protocols. | 29 | | [`/judging`](/judging) | Proposals for how judging should run at Epoch. | 30 | | [`/theme`](/theme) | Proposals for how we should choose Epoch's theme. | 31 | 32 | See [🟣 Issue #3](https://github.com/hackclub/epoch/issues/3) for additional context surrounding [`/judging`](/judging) & [`/theme`](/theme). 33 | 34 | ## 🗃️ Associated GitHub Repositories 35 | 36 | | Repository | Description | 37 | | ------- | ------- | 38 | | [`www-epoch`](https://github.com/hackclub/www-epoch) | Epoch's website! | 39 | | [`epoch-register`](https://github.com/hackclub/epoch-register) | Website for registering for Epoch. | 40 | | [`epoch-registrations`](https://github.com/hackclub/epoch-registrations) | Slack bot for registering for Epoch. | 41 | | [`epoch-prompter`](https://github.com/hackclub/epoch-prompter) | A static Next.js site to choose a prompt for Epoch. | 42 | | [`epoch-mission-control`](https://github.com/hackclub/epoch-mission-control) | Escape-room-style event for Epoch. | 43 | | [`epoch-reaction-listener`](https://github.com/hackclub/epoch-reaction-listener) | Slack bot to assign participants to teams for mission-control. | 44 | 45 | ## 📃 Miscellaneous Documents 46 | 47 | | Document | Description | 48 | | ------- | ------- | 49 | | [🏦 HCB](https://bank.hackclub.com/epoch) | Epoch's transparent account on HCB. | 50 | | [🎨 Figma](https://www.figma.com/file/jW5fmzrwUF4d6NZ2fHLRH9/Epoch?t=OISTk8mnHvlRwRpm-6) | Home of our branding assets & swag designs. | 51 | | [🛹 Project Board](https://github.com/orgs/hackclub/projects/16) | Project board for the early stages of the project. | 52 | | [🔢 Budget](https://docs.google.com/spreadsheets/d/1G-ukyf7spB8bfO9Mqnt8ks9swVIojfriPt1P4pEyWw4/edit?usp=sharing) | Open-source budget for Epoch (includes transactions on the Indian credit card). | 53 | | [📃 Venue Outreach](https://docs.google.com/document/d/1OyN7rPeg5BE-lFz1G2p_Y0eLViYmgk-UaQ6vZvBN6Zo/edit?usp=sharing) | Email copy used for venue outreach. | 54 | | [📃 Announcements](https://docs.google.com/document/d/1iDvmGILL0mb3I3r8DXbv9bhZ_ZjCVX7VsZwBEnpe7oQ/edit?usp=sharing) | Copy used for announcements on Slack & Twitter as well as to Hack Club's mailing list. | 55 | | [📕 Parent's Guide](https://cloud-o944bwtfx-hack-club-bot.vercel.app/0a_parent_s_guide_to_epoch.pdf) | Guide for parents with key safety information. | 56 | | [📃 Stipend Policy](https://docs.google.com/document/d/12uwVfoZG2AlfNkoSrzoIFcFAFfd179Qh2g-LSb4nG7Q/edit?usp=sharing) | Policy on how stipends should be distributed. | 57 | | [📃 Info Email](https://docs.google.com/document/d/16k7oVQWzPIfnZbgzsTVHQytLhBBRKy6blP8y5lUTFvA/edit?usp=sharing) | Extensive email for logistical information for attendees. | 58 | | [🎤 Opening Ceremony](https://cloud-f0hrhf8jz-hack-club-bot.vercel.app/0epoch_-_opening_ceremony.pdf) | Slides used to introduce Hack Club & Epoch. | 59 | | [📃 Ice Breaker Activity](https://docs.google.com/document/d/1OjOJSO1UivsyRrd-4JwlujfhphFSD74Dr58KjLxbswo/edit?usp=sharing) | Planning for ice-breaker activity in the opening ceremony. | 60 | | [📃 Food Menu](https://docs.google.com/document/d/19FevupqWtS-VegZIvK6CJYvfPIs5e84k6ooyjfkiVyU/edit?usp=sharing) | Menu for meals offered at Epoch. | 61 | | [📃 Workshops](https://docs.google.com/document/d/1767Za1rQsNxqv9BwArpZ3wTSXIKsh75Wwn-tfR7Xt4E/edit) | Schedule for workshops hosted at Epoch. | 62 | | [⏰ Run Of Show](https://docs.google.com/spreadsheets/d/1M3rOe1GRqriDZkEdiqrMQ6XMHIhSQ2_mrgG66n93RIo/edit#gid=0) | The run of show for Epoch| 63 | | [📃 Ideas Braindump](https://docs.google.com/document/d/1m-2JV8b4kXY3LRH5PC5FOWGPKVsN54WMkOiprX1iISU/edit?usp=sharing) | A random brainstorm by [@sampoder](https://github.com/sampoder) and other Hack Clubbers. | 64 | | [📸 The Photo Album](https://photos.app.goo.gl/CtgXTtiL37G3yX1E6) | Thousands of photos from Epoch, free for use by Hack Clubbers! | 65 | | [📸 Attendee's Photos](https://hack.af/epoch-album) | See Epoch from an attendee's perspective. | 66 | 67 | 68 | ## 🙏 Acknowledgements 69 | 70 | Epoch was made possible by dozens of Hack Clubbers. Thank you. A special thank you to our Temporal Agents: 71 | [Aaryan](https://github.com/aaryanporwal), [Akshay](https://github.com/akshay-99h), Anisha, [Arash](https://github.com/arashnrim/), [Arav](https://github.com/tregsthedev), [Arsh](https://github.com/arshshrivastavaa), [Ashish](https://github.com/ashishdevo28), [Christina](https://github.com/christinaasquith), [Dev](https://github.com/devenjadhav), [Fayd](https://github.com/faisalsayed10), [Gaurav](https://github.com/yednapg), [Kara](https://github.com/karamassie), Karan, [Mahi](https://github.com/mahi-agarwal), [Neil](https://github.com/neiltheghosh), Nila, [Nishant](https://github.com/Nishant2907), [Ojas](https://github.com/0jas0jas), [Sam](https://github.com/sampoder), Shatakshi, [Tej](https://github.com/tejasag), [Khaleel](https://github.com/khalby786) & [Zach](https://github.com/zachlatta). 72 | 73 | 74 | 75 | ## ❄️ In Years Past 76 | 77 | | Year | Project | Description | 78 | | ---- | ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 79 | | 2023 | [Epoch](https://epoch.hackclub.com) | _This repo!_ | 80 | | 2022 | [Assemble](https://assemble.hackclub.com) | The first high school hackathon since the pandemic! ([repo](https://github.com/hackclub/assemble)) ([finances](https://bank.hackclub.com/assemble)) ([photos](https://hack.af/assemble-photos)) | 81 | | 2021 | [The Hacker Zephyr](https://github.com/hackclub/the-hacker-zephyr) | A cross-country hacker adventure on a train. ([repo](https://github.com/hackclub/the-hacker-zephyr)) ([finances](https://bank.hackclub.com/zephyr)) | 82 | | 2020 | [Summer of Making](https://summer.hackclub.com) | $50k in hardware donations to teen hackers around the world + the creation of [Scrapbook](https://scrapbook.hackclub.com) ([code](https://github.com/hackclub/scrapbook)) ([finances](https://bank.hackclub.com/summer-of-making)) | 83 | | 2019 | [Flagship Summit](https://flagship.hackclub.com) | IRL meetup of high school hackathon organizers and coding club leaders ([photos](https://photos.google.com/share/AF1QipO3hb2mN-Q16icE-M16d-06uHyXLmvd3Rw6b_f_oosfAX9SnOvnouPOyO79P7pR7Q?key=anphZTNFUERPWXV3YnJQV2VzVVVFMFFVcGRDc3hB)) | 84 | | 2018 | [HCB](https://hackclub.com/bank/) | We built and launched the first version of HCB (read the [1st](https://medium.com/hackclub/hack-club-bank-a-bank-for-student-hackers-e5d894ea5375) and [2nd](https://medium.com/hackclub/hack-club-bank-is-now-live-for-everyone-including-you-884f7f54836f) announcement) | 85 | | 2016 | [Hack Camp](https://github.com/hackclub/camp/tree/master/2016) | Summer camp / further writing & testing workshops | 86 | | 2015 | [Hack Camp](https://github.com/hackclub/camp/tree/master/2015) | Summer camp / testbed for Hack Club's first [workshops](https://workshops.hackclub.com) ([content](https://github.com/hackclub/hackclub/tree/main/workshops#readme))([code](https://github.com/hackclub/workshops)) | 87 | -------------------------------------------------------------------------------- /judging/Peer judging model.md: -------------------------------------------------------------------------------- 1 | # Peer judging systemmmm! 2 | 3 | This is kind of based on [SoME2](https://youtu.be/cDofhN-RJqg). 4 | 5 | The idea is that we could have volunteers/participants/comittee of about 20ish people and these people contribute to a final judgement. 6 | 7 | ## The 20 people 8 | These people could be volunteers or just random participants or comittee on `#epoch-bts`. They get unnamed and unidentified projects. 9 | 10 | ## The judging 11 | These people will be given rubrics as follows 12 | 13 | | Creativity | Uniqueness | Difficulty making | Remarks 14 | | :---: | :---: | :---: | :---: 15 | | x/10 : INT | x/10 : INT | x/10 : INT | Comments : STRING 16 | 17 | ## The peer checking 18 | All peers will judge all projects based on the given rubrics. When all projects have been judged 20ish times, we take the average of the scores to find the final judgement. 19 | 20 | ## Ties 21 | Ties can be cleared with audience opinion or votes. 22 | 23 | ## If the project submission quantity > [a large number] 24 | There can be batches of 20 peers and these peers can have a divided amount of projects to judge. Then the averages will be matched for all the projects together. 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | //Suggestions welcome. -------------------------------------------------------------------------------- /judging/README.md: -------------------------------------------------------------------------------- 1 | # Judging Proposals 2 | 3 | This directory houses the proposals for the judging process at Epoch. Interested? Join [#epoch-bts](https://hackclub.slack.com/archives/C044HSLSU06) in the [Hack Club Slack](https://hackclub.com/slack) to help us organise! 4 | -------------------------------------------------------------------------------- /judging/community_voting.md: -------------------------------------------------------------------------------- 1 | # Community Voting Model 2 | 3 | I think the system that was used for Assemble would work well, with one change: not using emojis. 4 | The emojis were fun, but it wasn't disclosed what they were for, and there were so many emojis. 5 | Not sure how it looked on the judges' side, but I assume it was difficult to sort through the projects and assign categories. 6 | 7 | Instead, we could make a cookie 🍪 system, where each participant gets a number of cookies (maybe 50?). 8 | They can assign as many cookies as they want to **other** projects, and judges can sort the list by cookies and assign the final awards. 9 | 10 | One thing this loses is the categorization effect of the emojis, but judges will also be able to see the projects, so they can probably think of the best projects for each award pretty easily. 11 | 12 | ## Technical 13 | 14 | The ship cards from Assemble were really cool! But my potato camera was unable to detect the red QR (and installing a dedicated QR scanner creates friction), plus my phone didn't support NFT so that did not work :/ 15 | I'd suggest having the actual voting link somewhere on the card, as well as using a black and white QR code to make sure it works for everyone. 16 | (Yes, the ID was on the card, but it wasn't apparent what the link was.) 17 | And hopefully connection pooling is implemented ;-) 18 | 19 | ## Judges 20 | 21 | Not sure who the Assemble judges were, but I'd assume they could include Hack Club Staff, students part of the organizing team, and maybe some randomly selected attendees? Probably ~10 people would be good, but would love to hear what worked/didn't work at Assemble. 22 | -------------------------------------------------------------------------------- /outline.md: -------------------------------------------------------------------------------- 1 | **The Event’s Vision:** An epic, global high schooler-led hackathon organised in public to inspire the community and bring hundreds of Hack Clubbers together in Asia in the winter - the most epic hackathon this winter 2 | 3 | **Budget:** $40K for event itself. $4K emergency budget for day-of. There will be more costs around sending HQ staff and making a film, etc., this will come from HQ & not be in the event’s budget. 4 | 5 | **Staffing:** High schooler led, with HQ staff support. 6 | 7 | **Problem Statements:** 8 | 9 | 1. Lots of hackathons are being organised right now in #hackathon-organizers, and they need more support than we’re currently providing - especially around vision, marketing, and logistics. 10 | 2. It’d be one thing for us to write tutorials on how we think people should run their hackathons, but 1) we think people are better suited to run an awesome event for their community than we are, and 2) the Hack Club ethos is not to be instructional, but rather role model the behavior we want others to see. 11 | 3. We want this to be the most epic hackathon happening on the planet in the next 6 months. How can we make it feel like a truly global event? Attendees internationally, organised in public on the Slack, truly a global community event that happens to be happening in Asia. 12 | 4. How can we make sure everyone hearing about the event walks away thinking “Hack Club is amazing, and I want to get more involved”? 13 | -------------------------------------------------------------------------------- /safety.md: -------------------------------------------------------------------------------- 1 | # 🦺 Safety at Epoch 2 | 3 | **Table of Contents** 4 | 5 | - [🦠 COVID-19](#-covid-19) 6 | - [Before the Hackathon](#before-the-hackathon) 7 | - [Vaccination Requirements](#vaccination-requirements) 8 | - [Covid Test Documentation](#covid-self-testing) 9 | - [At the Hackathon](#at-the-hackathon) 10 | - [Resources](#resources) 11 | - [Self-report Response](#self-report-response) 12 | - [After the Hackathon](#after-the-hackathon) 13 | - [Reporting post-event positive-tests](#reporting-post-event-positive-tests) 14 | - [🛟 Additional Day-of Safety](#-additional-day-of-safety) 15 | - [Point of Contact](#point-of-contact) 16 | - [Sleeping](#sleeping) 17 | - [Supervision](#supervision) 18 | - [🛫 Travel Safety](#-travel-safety) 19 | - [Dedicated Point of Contact](#dedicated-point-of-contact) 20 | - [Airport Chaperoning](#airport-chaperoning) 21 | 22 | Documentation and implementation is handled by the **safety working group**. 23 | If you have any questions, or need to contact someone about these docs, please reach out to them. 24 | 25 | | Name | GitHub | Email | 26 | | ---------------- | ----------------- | --------------------------- | 27 | | Sam Poder | @sampoder | sam@hackclub.com | 28 | | Deven Jadhav | @devenjadhav | dev@hackclub.com | 29 | 30 | 31 | ## 🦠 COVID-19 32 | 33 | ## Before the Hackathon 34 | 35 | ### Vaccination Requirements 36 | 37 | All attendees will be required to have full vaccination against COVID-19. 38 | 39 | ### COVID Self Testing 40 | 41 | We require all attendees & organisers to take a antigen test within 24 hours of the event or (if flying) before you leave to travel. Those positive may not enter the venue. 42 | 43 | ## At the Hackathon 44 | 45 | ### Resources 46 | 47 | Rapid tests will be available on-request for those feeling unwell and hand sanitizer will be located throughout the venue. 48 | 49 | Masks are not required at the venue, but single-use masks will be available for anyone who wishes to wear one. 50 | 51 | ### Self-report Response 52 | 53 | If an attendee or organizer begins to show symptoms and/or has a positive test, they must isolate and leave the event. They are responsible for coordinating housing and rebooking travel if needed. 54 | 55 | We will send a notification email to attendees with exposure details if there is a positive test. 56 | 57 | ## After the Hackathon 58 | 59 | ### Reporting Post-event Positive Tests 60 | 61 | If an attendee or organizer has a positive test within 7 days of the event, they should report the possible exposure to self-report link made available after the event. 62 | 63 | To ensure attendees and organizers remember to self-report after the event, a scheduled text message will be sent with the self-report link. 64 | 65 | ## 🛟 Additional Day-of Safety 66 | 67 | ### Point of Contact 68 | 69 | There will be two designated adult safety points of contact, one female and one male. Both will be employed by Hack Club and will have the necessary background checks. They'll be introduced at the opening ceremony and their phone numbers will be made available to all attendees through email. 70 | 71 | ### Sleeping 72 | 73 | We will have a gender-seperated & adult-supervised space for sleeping within the venue. Supervising adults will be available to respond to any situations that arise. 74 | 75 | ### Supervision 76 | 77 | At all times, there will be at least two adults and ten members of the Epoch student team on site. All adult staff members will have the necessary background checks. 78 | 79 | ### The Venue 80 | 81 | The venue is closed doors which means that only those that have registered will be allowed to enter the venue. Once the event begins and bar an emergency, only event staff will be able to enter and exit the venue. Building security will be present at all times. 82 | 83 | ## 🛫 Travel Safety 84 | 85 | ### Dedicated Point of Contact 86 | 87 | A dedicated travel point of contact will be established. They will be available to support attendees as they travel to and from the event. This will be a remote role, to ensure they are focused. They will be armed with all required travel information. 88 | 89 | ### Airport Chaperoning 90 | 91 | Attendees will be able to travel alongside event staff to the venue from Indira Gandhi International Airport, if there inbound flight arrives on Friday (after 8:00) or their outbound flight departs on Sunday. 92 | -------------------------------------------------------------------------------- /theme/README.md: -------------------------------------------------------------------------------- 1 | # Theme Proposals 2 | 3 | This directory houses the proposals for Epoch's theme. Interested? Join [#epoch-bts](https://hackclub.slack.com/archives/C044HSLSU06) in the [Hack Club Slack](https://hackclub.com/slack) to help us organise! 4 | -------------------------------------------------------------------------------- /theme/build_that_one_project.md: -------------------------------------------------------------------------------- 1 | **Theme suggestion:** Build (or finish!) that one project you've always wanted to, but have been procrastinating on. 2 | 3 | **Alternatively:** Take an old project that you stopped working on and revive it with a rewrite or new features! 4 | 5 | This is in the spirit of New Year's resolutions, and is also pretty open ended to give attendees a lot of freedom :D 6 | -------------------------------------------------------------------------------- /theme/random_word_tournament.md: -------------------------------------------------------------------------------- 1 | # Random Word Tournament 2 | 3 | On the Epoch registration form, we've been collecting three random words from each participant. For example: 4 | 5 | ``` 6 | computer, music, yay! 7 | ``` 8 | 9 | I propose we make a list of all these, sort through them, (potentially) add some verbs and then run a tournament of sorts. 10 | 11 | Our theme will be a four word phrase. Attendees will vote to select each word in that phrase from a sub-section of the random words submitted by attendees. 12 | 13 | Here's an example of how the tournament would work: 14 | 15 | **Round 1** 16 | 17 | Words to choose: 18 | 19 | | Stupid | Magical | Supernatural | Chaotic | 20 | | --- | --- | --- | --- | 21 | 22 | The votes are in from participants, they've choosen **Chaotic**. 23 | 24 | Our prompt is currently _Chaotic XXX XXX XXX_. 25 | 26 | **Round 2** 27 | 28 | Words to choose: 29 | 30 | | Creations | Adventures | Mayhem | Stories | 31 | | --- | --- | --- | --- | 32 | 33 | The votes are in from participants, they've choosen **Creations**. 34 | 35 | Our prompt is currently _Chaotic Creations XXX XXX_. 36 | 37 | **Round 3** 38 | 39 | Words to choose: 40 | 41 | | That | With | Running | Without | 42 | | --- | --- | --- | --- | 43 | 44 | The votes are in from participants, they've choosen **Without**. 45 | 46 | Our prompt is currently _Chaotic Creations Without XXX_. 47 | 48 | **Round 4** 49 | 50 | Words to choose: 51 | 52 | | Meaning | Documentation | Windows | Sleep | 53 | | --- | --- | --- | --- | 54 | 55 | The votes are in from participants, they've choosen **Meaning**. 56 | 57 | Our prompt ends up as _Chaotic Creations Without Meaning_. 58 | 59 | --- 60 | 61 | OK... so I hope that slightly staged example helped a little bit! We would curate the words a little better and all but that's basic idea. 62 | 63 | I'm putting this idea out there because I think: 64 | 65 | * it would be a fun way of engaging the attendees with the prompt 66 | * it would lead to some wacky prompts and therefore wacky projects 67 | * no one knows what will happen (incl. organisers) before the tournament 68 | -------------------------------------------------------------------------------- /theme/wacky_and_hacky.md: -------------------------------------------------------------------------------- 1 | # Wacky and Hacky 2 | 3 | > Build something that may seem useless to other people, but actually has a unique and specific purpose. The wackier it is, the better! 4 | 5 | I got this idea through thinking about innovators like [Simone Giertz](https://www.youtube.com/@simonegiertz) and [Michael Reeves](https://www.youtube.com/@MichaelReeves). They make entertaining videos documenting them creating the most absurd project ideas, and sometimes they actually kinda work! 6 | 7 | It'll be interesting to apply this concept into this hackathon. A few pros that I can think of at the top of my mind while writing this suggestion: 8 | 9 | - Participants are more likely to build _for fun_ rather than build _to win_. While it is good to have a hackathon idea that's pretty good and applicable beyond the hackathon, I think it'd be great to let participants express their creativity! 10 | - Participants can be encouraged to try out and incorporate something new. This keeps the spirit of learning in hackathons alive! 11 | - Participants can learn about the reason behind why best practices exist. For example, they may hit a roadblock because of their wacky and hacky implementations, but that's perfectly okay! At the very least, they've taken away the lesson that the way they've chosen isn't the best way, for example. 12 | --------------------------------------------------------------------------------