Goal: Us: A working POC for end of Summer events
- Backend
- Frontend (UX)
Items | |
---|---|
Decide on the date and time | Week Long: Intro to Giving Chain Intro to Firefly Where we are where we want to get |
Invite using Hyperledger Princeton (networked) | |
Workshop (intro to Firefly) | |
How to pick teams -focus on the same goal or parts | |
Introduction What we are working on | Good first issues |
Pre Requisites for the event | |
Prizes (cash or swag) | |
Event Bright ...Zoom...Metaverse.. | |
Team Leaders |
GUIDE:
Hacking is creative problem-solving.
- A hackathon is any event of any duration where people come together to solve problems. Most hackathons I’ve run also have a parallel track for workshops.
- Participants typically form groups of about 2-5 individuals, take out their laptops (if the event is technology themed), and dive into problems.
- Hacking begins with project introductions. Participants that bring projects to the event have an opportunity to briefly (1 minute max) explain what they are working on at the very start of the event so that other participants can join that project. At the end of the event, a wrap-up session gives each project a chance to demonstrate some accomplishments.
Venue & Sponsors:
- Start: ? End: ? Plan at least 30 minutes before and after the event
- Sponsors will give you something — cash, space, food, t-shirts — with the expectation that they get something out of their support for your event. They might be recruiting/hiring and are looking to scout out your attendees, or they might be marketing a product that they want to promote.
Find project leaders
Bobbi, Hardik, Nicko?- and others.
...
© Joshua Tauberer 2014-2017. Feel free to use under the terms of CC-BY 4.0.
- Don’t expect to have actually solved a problem by the end of the hackathon