├── backend.md ├── christina_sat_1 ├── closing_sun_5 ├── community_sun_4 ├── diff_sun_1 ├── discussion_sat_3 ├── discussion_sun_3 ├── everything_wrong_with_hackathons.md ├── keynote ├── lee_sat_11 ├── lightning_talks_sat_4 ├── mentorship.md ├── mentorship_sun_1 ├── organization_sun_12 ├── stuff_you_dont_need.md └── use_these /backend.md: -------------------------------------------------------------------------------- 1 | Backend 2 | ======= 3 | 4 | - Website with table numbers so hackers can fill a form for mentors to know where to go. 5 | - Website -> static 6 | - Subdomain: Example, registration. 7 | - STANDARDIZATION FOR BACKEND SERVICES! 8 | - **ACTION ITEM:** Talk to MLH (Niko?). 9 | - Consider creating an internal StackOverflow for giving badges (gamification for getting better mentors). 10 | - **ACTION ITEM:** Have a system with a map system and "discover" people who are working on a project (twitter handle as well). 11 | 12 | # How do you manage internal team tasks? 13 | - Notifsta -> http://notifsta.com/#/ 14 | - Private Github repos with issues; open source later right before the event. 15 | - Slack 16 | - Trello 17 | - JIRA 18 | - Google Sheets 19 | - Teams forget to update their issues. 20 | - Big facebook group and messenger conversation and a Google Drive folder which you chat about and send links to them in the FB chat. 21 | - GroupMe 22 | - Some teams moved away because sharing code snippets to Slack. 23 | 24 | # Day Of 25 | - Don't use Slack, etc. 26 | - Get walkie-talkie. 27 | - Use codewords to switch channels to a private one. 28 | - Keep external battery packs for back up with cellphones/walkie-talkie. 29 | 30 | # Organizing teams and times 31 | - One list to rule them all; people will call you and tell you if they can make it or not. <- Not terribly efficient. 32 | - Get freshman/sorotizes to join and help with service hours. 33 | 34 | # Incentivize 35 | - Get volunteers from clubs and take care of the clubs (via $$?) for getting your volunteers. 36 | - Get communities/profs to give service hours for helping in a hackathon. 37 | 38 | # Mobile applications 39 | - Pro tip: Submit your mobile app in advance to get approved by the application store you submit to. 40 | - Guidebook app as a universal one. 41 | - May not work, but you end up making it so generic that it doesn't work for every hackathon. 42 | 43 | # Challenges when backend developers leave 44 | - Keep secret keys documented. 45 | 46 | # Misc 47 | 48 | **ACTION ITEM:** Make a backend for the mentorship with a backend of Github Issues so that anyone can mentor (not sponsors). 49 | -------------------------------------------------------------------------------- /christina_sat_1: -------------------------------------------------------------------------------- 1 | Christina Liu 2 | Diversity Through Empathy 3 | 4 | Silicon Chef 5 | Hardware Hacks for females 6 | Spark Fun inventor's kit is what they used 7 | 8 | Sympathy - Understand feelings that you aren't having 9 | - comes of as just "being nice" 10 | Empathy - Feeling the feelings of someone else as someone else 11 | - makes or breaks experience 12 | - shows that you really get people 13 | 14 | Sympathy & Empathy 15 | - sympathy is the buzz words, empathy is the action 16 | 17 | Narrative Crafting - give people a story to care about for your event 18 | - creates an experience for attendees 19 | - write something through the eyes of an attendee team 20 | - now use that to plan the event 21 | - allows you to ask if decisions align with the desired expereince 22 | - sets the messaging tone 23 | * This tells people how to behave and what to expect * 24 | Code of Conduct 25 | - have one. 26 | - use it if you need to kick someone out 27 | - you can have a conversation about why offenders are breaking the code 28 | 29 | How to food. 30 | food fuels you 31 | - having good food keeps you going 32 | veg, vegan, gluten 33 | - more than lettuce... 34 | label food with common allergens 35 | 36 | Experience Crafting 37 | post speakers as soon as you know 38 | t-shirts, multiple cuts if possible 39 | have feminine products in the bathrooms 40 | advertise through groups who have the same mission 41 | ask attendees to help clean up 42 | 43 | Retro 44 | sit on down and go over the event 45 | look for some feedback 46 | what worked/didn't and why 47 | how can we get better for the next one 48 | ask and listen to the attendees 49 | 50 | Barrier Removal 51 | get rid of as many barriers as possible 52 | or maybe focus on one or two 53 | - they can be physical or mental 54 | get ready to fail. 55 | - you can't remove everything or think of every possibility 56 | be quick to give affirmation 57 | explicit opt in v. implicit opt out 58 | - if you want something, you go to it. 59 | - force people who want something to move to do it 60 | - don't force people to leave if they want out 61 | 62 | Take Care of yourself 63 | this allows you to be present for others 64 | if you aren't taking care of you, you can't take care of others 65 | 66 | -- Q&A -- 67 | People might not know they're breaking the code of conduct. 68 | 69 | -------------------------------------------------------------------------------- /closing_sun_5: -------------------------------------------------------------------------------- 1 | Nick, Loons, Running into Swift, and lividity. 2 | 3 | All the things you need. 4 | -------------------------------------------------------------------------------- /community_sun_4: -------------------------------------------------------------------------------- 1 | Building hacker community outside of hackathons 2 | Rodney Folz 3 | 4 | build a culture of creation on campus 5 | -building cool shit is a super power 6 | 7 | when staring a community, just do it 8 | - power through 9 | - people come to events because they're interested in things 10 | - do things so people can be interested in them 11 | - evening events, food, advertising 12 | 13 | The key is making your events happen 14 | - add value, that makes community 15 | - go beyond the info session 16 | * poster signed by cs faculty * <- that's funny 17 | 18 | Don't be alone. have the community yourself while opening it to others 19 | - everyone wins or loses together. 20 | 21 | Bureaucracy is tough 22 | - load balance around teams not events 23 | - have a doubly linked list of responsibility 24 | 25 | -------------------------------------------------------------------------------- /diff_sun_1: -------------------------------------------------------------------------------- 1 | Jeff Hilnbrand 2 | How to Diff 3 | 4 | We're talking about how to differentiate yourself. 5 | 6 | * Hackathons are like startups with a timebomb * 7 | - fundraising 8 | - development 9 | - marketing 10 | - design 11 | - product fit 12 | 13 | When will things slow down? 14 | - Things can get harder 15 | - Sponsors more difficult 16 | - Then you have to differentiate 17 | 18 | Diff 19 | - Show what's added/removed 20 | - Too often hackathons are just changing metadata 21 | - same hackathon different name or location 22 | - it's hard to just make the event, but we have to try and change. 23 | 24 | How can we do that? 25 | - Embrace constraints 26 | - look at the things that block you and use that to motivate iteration 27 | - just like designing within a box. 28 | 29 | throw localhost:2015 30 | - what can you do with what you have? 31 | - people are going to disagree. you'll have to justify it 32 | - ask other people to help 33 | 34 | Technica: a focus on culture. 35 | 36 | What is your diff? 37 | - give it a real thought. 38 | -------------------------------------------------------------------------------- /discussion_sat_3: -------------------------------------------------------------------------------- 1 | Discussion 1, Saturday 2 | Content and Differentiation 3 | 4 | Promotion: 5 | Ask people to get involved in the event 6 | - Announcements 7 | - What shirt design do you like? 8 | Blog posts for the hackathon 9 | - Weekly hacker spotlight. 10 | - Gets people involved and sharing 11 | - Standardizing quality is important 12 | Keep things going in the off time 13 | Measure referrals 14 | Partner with other hackathons. 15 | - find things on the same weekend and partner with them 16 | Design limited run stickers 17 | 18 | Keeping people engaged between events 19 | Making videos... 20 | Leverage the hacker club to get the word out. 21 | 22 | What do we want to hear? 23 | What's going on at the hackathon. 24 | Email broadcasts. 25 | 50 days of bitcamp <- be consistent 26 | Target people who are close. 27 | SNIPE the freshmen 28 | Make resources for people to learn about tech 29 | Get alums to give workshops 30 | 31 | Being beginner friendly pays dividends 32 | 33 | How do you brand the hackathon? 34 | Have something that is consistent 35 | Make little changes each time 36 | Don't overthink it though 37 | Use the resources you have 38 | 39 | USE GOOGLE ANALYTICS. 40 | Measuring clicks and conversion is cool 41 | It lets you determine how people interact 42 | Look at numbers. 43 | 44 | Lowering dropoff and Atrition 45 | Inentivize shares 46 | Give something physical before the event 47 | Keep in touch between sign up and the event 48 | Why didn't people go? <- the question. 49 | Talk to small universities, they want to do things too! 50 | 51 | 52 | -------------------------------------------------------------------------------- /discussion_sun_3: -------------------------------------------------------------------------------- 1 | Passing The Torch Discussion, Sunday 2 | 3 | People leaving is the biggest killer of student-run events. 4 | - hearty agreement 5 | 6 | How does organization size come into play? 7 | - bring in someone new each time. 8 | - directors are young. 9 | > this allows people to maintain knowledge 10 | > feeds back into the community 11 | - directors, volunteers, advisors 12 | - becoming a part of the leadership takes interviews 13 | - have a playbook 14 | > a document going over your role. things that you've known 15 | > go over your mistakes 16 | * MAKE A PLAYBOOK * 17 | 18 | How do you recruit new people? 19 | - ask professors 20 | - compartmentalize the parts of a hackathon 21 | - get people who are interested in their area (business, design, marketing...) 22 | - talk to TAs who know young students 23 | - hackathons are a whole different skill set and scale 24 | - have some extra volunteers stay on and keep helping 25 | - remember a bigger team is not always better 26 | - keeping teams small is helpful 27 | 28 | Make sure you don't keep unresponsive people around 29 | - but give them tools to succeed 30 | 31 | How do you keep momentum over the summer 32 | - be annoying sometime 33 | - set consistent meetings 34 | - understand people's commitment 35 | - make people feel important 36 | - get the word public about achievements 37 | - help people take thier own initiative 38 | - own the area of expertise 39 | 40 | * If someone is unresponsive start sympathetic not angry * 41 | 42 | Get a University champion. They'll advoacate to faculty for you 43 | - have them show up. 44 | - find a person students respect 45 | - understand that faculty want university to get something back 46 | - start sympathetic not angry. 47 | 48 | Be present after you leave 49 | - don't leave a mess when you leave 50 | -------------------------------------------------------------------------------- /everything_wrong_with_hackathons.md: -------------------------------------------------------------------------------- 1 | Everything Wrong with Hackathons 2 | ================================ 3 | - Make friends 4 | - No experience necessary 5 | - Do a side project 6 | - Learn something 7 | - Projects -> Products 8 | - Feel connected to mentors 9 | - Atrition rates 10 | - Build something at the event 11 | - Other fields 12 | - Active outside 1 weekend 13 | - Part of the community 14 | - Encourage Exploration 15 | - Make people never feel like they "aren't good enough" 16 | - Internship 17 | - Proud 18 | - Starts > Wall Street 19 | - Bond the organizing team 20 | - Language independant 21 | - People want to give back 22 | - Committed organizers 23 | 24 | ## Part of the community 25 | - Emphase the importance of giving back. 26 | - Alumni want to help, but don't know how to help. Maybe have alumni mixers? Send sponsors newsletters? 27 | - Make friends -> Feel connected to young people. 28 | 29 | ## Do a side project 30 | - Make a hacker space for collaboration. 31 | - Pitch it to the CS department (or equivalent) to get an area. 32 | - If you spend 24 hours on it, you thought it was worth, there will be others who think it's worth it. 33 | - Make them present and get them going even if it isn't complete or not that great compared to them. 34 | 35 | ## Build something at the event 36 | - To get travel reimbursement, you have to build something (submit to ChallengePost). 37 | - MAKE THAT CLEAR IN THE BEGINNING. 38 | - Doesn't always work; can harm some people. 39 | - Maybe kill travel imbursements? 40 | 41 | ## Highlighting the learning aspect of large hackathons 42 | - Let everyone demo. 43 | - Split it into two different rounds. 44 | - ??? 45 | 46 | ## Active outside 1 weekend 47 | - "We still hack on Monday." 48 | - For us your club or events for the rest of the year and not just the hackathon. 49 | - ??? 50 | 51 | ## Make people never feel like they "aren't good enough" 52 | - Stop labelling hackathons as a competition and are more of a learning experience. 53 | - Take the technical jargon away from the website. 54 | - The word hack is intimidating. See "After hours", "DevFest", "Cookies & Code" 55 | - Have dev classes for beginners, intermediate, advanced. See "No experience necessary" events. 56 | - "Learn how to build an app in a week, oh, there's also a hackathon at the end." 57 | - Chill out sessions, but leave it informal. 58 | 59 | -------------------------------------------------------------------------------- /keynote: -------------------------------------------------------------------------------- 1 | Hackcon KEYNOTE 2 | 3 | HackerLeague, Sendgrid, 4 | 5 | > Spring Recap 6 | 77 sanctioned events, woah! 7 | 22,000 students 8 | 9 simultaneous events, 10 countries 9 | 10 | > Announcements 11 | MLH Community Council 12 | - 7 people who are gonna listen to the community 13 | - hi@mlh.io for more info 14 | MLH Coaches 15 | - community members going around and learning/sharing 16 | - Nico an Jared did this 17 | my.mlh.io 18 | - single sign on solution!! 19 | - api for data. 20 | - people can sign up for hackathons with a button and their info :) 21 | - MLH login page. dis da bomb 22 | - The mlh login collects everything we need, and an API 23 | 24 | HOW DO I GET THE INFO? 25 | http://my.mlh.io/api/v1/users 26 | 27 | > THE FALL 28 | a couple events get the my.mlh.io stuff <- i want that :) 29 | 30 | -------------------------------------------------------------------------------- /lee_sat_11: -------------------------------------------------------------------------------- 1 | Lee Felsenstein 2 | Hacking - Technology Development as a Sport 3 | 4 | Literally the oldest computer I've ever seen. 5 | - tiny screen. big box. 23 pounds. 6 | 7 | Tech vs Magic. 8 | What's the process of development? 9 | - it's all about exploring the unknown 10 | - extend your limits 11 | It's all about FLOW 12 | - from my main man Mihaly 13 | - You forget time, place, it's only the groove 14 | - no worries about economic gain 15 | - so much of what hacking is pursuing that flow experience 16 | - when you flow, you forget everything except the hack 17 | - balance difficulty with ability 18 | * not too hard that you're frustrated, but not tedious 19 | 20 | Hacking as Sport 21 | Lee is a sportsman, his game is hacking 22 | - requires socialization (i.e. the community) 23 | - exhibition (show of your sick nasty skills) 24 | - mentoring 25 | - moral development (be a part of society, get ahead ofthe social curve) 26 | *Fun Fact* Lee made a social network in 1970 27 | - American Radio Relay League people have tight asses. 28 | 29 | The hacker league 30 | Get these outlaws togther 31 | - exchange info, tech, converences, etc. 32 | Mentor each other 33 | - it's a big deal to help each other 34 | - we can't all do it alone and the community is here to help 35 | What are the benefits? 36 | - get ahead of the educational institutions 37 | - you have people to bounce ideas off of 38 | Hacking stared coworking 39 | - suprise, hackers like to be social 40 | - getting together and nerding out about stuff they like 41 | 42 | Hackathons are more than just play 43 | They are fun though - "Computer Play Parties" 44 | Tech Dev solves problems. It gets away from the institutionalization of design. 45 | We don't need to wait to learn and solve problems. 46 | Staying in school isn't enough 47 | - learn the tools to get better 48 | 49 | Q&A 50 | What are the core items to learn? 51 | - hands on experience making patterns 52 | - teaching binary with your fingers (each finger is a bit) 53 | - figure out the patterns. 54 | - tie it to physical reality 55 | What's your best hack? 56 | - Bill Gates said "cool" 57 | How do you go about achieving flow? 58 | - Make some ciruit board layouts 59 | - Sometimes you just have to do it yourself. 60 | What would you change about education? 61 | - there are lots of things to change 62 | - ivan illich - the philosopher 63 | - people can teach each other 64 | - maybe we can use computers for that? 65 | - have people teach other people. 66 | 67 | And then the computer caught on fire... 68 | 69 | 70 | -------------------------------------------------------------------------------- /lightning_talks_sat_4: -------------------------------------------------------------------------------- 1 | Lightning Talks, Saturday 2 | 3 | Sponsorship - Shrav from CalHacks 4 | Find your secret sauce 5 | - messaging 6 | - audience 7 | - how are you unique 8 | Determine who is best to target 9 | Who? 10 | - Recruiting 11 | - Event marketing 12 | - Dev Evangelist 13 | Where? 14 | - Linkedin 15 | - Hackathon Websites 16 | - Conferences 17 | - Career Fairs - those companies already have a relationships 18 | Essentials: 19 | Date/Participants/Location/University 20 | DONT EMAIL YOUR SPONSORSHIP DOC 21 | Always follow up. 22 | Ask until they give you an answer 23 | 8am tuesdays 24 | Show your worth. Give them a value proposition 25 | Send updates, care for them 26 | Get it in writing 27 | NOTHING IS OFFICIAL UNTIL YOU CLOSE. 28 | - sign the contract 29 | - collect the $$ before the hackathon 30 | Tools: leadiq, persistiq, tryprospect 31 | 32 | github.com/shrav/hackathons 33 | 34 | Corporate Sponsorship - Vikram from MHacks 35 | Companies that aren't tech centered, and are huge 36 | Remember companies aren't necessarily hackathon literate. 37 | Initial contact: Highest ranking alum and in IT 38 | Hackathon is a dirty word, try 'innovation marathon' 39 | Reach out to recruiting and marketing 2x the $$ 40 | Build a long term relationship and keep it realiztic 41 | * It's all about the value addition * 42 | 43 | Code - Niko from Hack Texas 44 | OPEN SOURCE yo shit 45 | 46 | Local Hack Day - Shy Ruparel 47 | October 10, localhackday.mlh.io 48 | Make a community and empower it 49 | Get's you in on the entry level. 50 | Organizing can be easy since this is small. 51 | 52 | Campus Data - Dan Schlosser Devfest 53 | What's open campus data? 54 | Students work with administrators to make apis for school data 55 | Make apps using campus data! 56 | A connection gets built with the university and administrators 57 | campusdata.org 58 | - add a school and find data they provide 59 | 60 | Shit you don't need - Taylor Barnett HackTX/KeenIO 61 | "If we care about money, attendees will care about money" 62 | Don't need the coolest venue 63 | - wifi, power, temp, space 64 | Don't need premium food 65 | - get a balance. not all pizza, but not extravagant 66 | Don't need shirts 67 | - b-but.... 68 | Don't need a big keynote 69 | - just need the details 70 | - set the tone 71 | - the speaker isn't a big deal 72 | Don't need the BEST hackers (or hackers at all) 73 | - it's all about making things 74 | Don't need HUGE events 75 | - love your events own skin 76 | - accept what you can get 77 | - focus on the event itself not getting people there 78 | Don't need travel reimbursments 79 | - too much time and $$ focusing on that 80 | - focus inside the community and close people 81 | Don't need fancy awards 82 | - give sponsors a nod. 83 | - show cool projects 84 | - fix any lingering problems 85 | 86 | How to Avoid engineering and be a dev evangelist - Github 87 | Why do you organize the event? 88 | - running events is ahead of the curve 89 | Why you should be a dev evangelist 90 | - get paid to build a network 91 | - become an 'authority' on the subject 92 | - it helps you build networks for the future 93 | - we already have some skills necessary 94 | FIND A MENTOR! 95 | 96 | The Hacker Renaissance - Dave Fontenot 97 | The first renaissance required apprenticships, patronage, printing press 98 | This one has internships, hackathons, the internet 99 | What's the point of the event? 100 | - they build a movement 101 | - open peoples's eyes to the tech they user every day 102 | - you have agency to fix problems in the world 103 | - build a community. that's what matters 104 | - contribute to the culture, set a precedence 105 | Greet people enthusiastically! 106 | - be happy for people to be there 107 | -------------------------------------------------------------------------------- /mentorship.md: -------------------------------------------------------------------------------- 1 | Mentorship 2 | ========== 3 | 4 | > **Notes**: Please excuse typos and english fails. 5 | 6 | - Feel comfortable for people learning something new 7 | - How do you things at your hackathon? 8 | 9 | Hack@Brown 10 | - Get alumni via their companies 11 | - Linkedin 12 | - Internal student tools 13 | - They were all sponsors 14 | 15 | HackBSCA 16 | - Don't set a goal to learn how to hack over night 17 | - Show them they can make real projects 18 | - Leave the event with a working project 19 | - Help people create a landing page, etc. 20 | - Inspire them to learn 21 | 22 | # How do you distinguish your mentors from your alumni? 23 | - Colored bandanas. 24 | - Wristbands 25 | - Coloured shirts: Sponsors, mentors, hackers, volunteers 26 | - Capes! 27 | 28 | # Swag for mentors, how did you pick those people 29 | - Mentors sign up before the event. Stay on track to be a mentor. 30 | 31 | # How did you find them? 32 | - Classroom labs with office hours. 33 | 34 | # Organizing mentors 35 | - Number tables; mentors have to take care of areas. 36 | - Number tables; have an online form that assigns mentors to the table. 37 | - Online mentors: Lightscale. 38 | - Ask HH? 39 | 40 | # How did you prepare mentors for the event? 41 | - Handing packets of when mentors should approach people. 42 | - Mentors guide sent to mentors a week before. 43 | 44 | # How to keep mentors stay for the entire event? 45 | - Talk to people how important it is for them to stay. 46 | - Don't let them leave at 5pm. 47 | - Get them excited to help people (at 2am). 48 | 49 | # How do you offer an insentive for the mentors? 50 | - Incentivize student mentors. 51 | - May not be good for sponsored mentors; they already have been paid to be there. <- talk to them. 52 | - Keep the mentors on the same floor/room as the hackers so they don't lose sense of help needed. 53 | 54 | # What do you think about hackers helping other hackers? 55 | - From a hackers perspective, discourage teams of beginner-only teams. 56 | - Incentivize teams with prizes that if they have 50 newbies/50 experienced. 57 | 58 | # Adopt a beginner program? 59 | - Second time hackers, put your name and area of experience and put them to email each other pre-event. <- May not work all the time. 60 | 61 | # Dealing with bad mentors. 62 | - Infringing on MLH rules: kick 'em. 63 | - Bad mentor by technical standards: Teach them how to google. 64 | 65 | # Sign up to be mentor/hacker: 66 | - What happens in practice, experienced wanted to work on their own hacks. 67 | - Beginners tended to be left behind. 68 | - Incentive was with swag; people will mentor only for minimum hours. <- Not what they wanted. 69 | 70 | # Misc 71 | - Beginner 101 workshops for how to google & VERY basics of github. 72 | - "Cortexes" create communities of people in the same room. Mobile room, Web room, etc. 73 | - Breaking into groups so create the feeling of smaller hackathons. 74 | - Incentive with unlimited food? 75 | - Send personal thank you cards for mentors (especially who helped a lot). 76 | - Inform sponsored mentors (providing SDKs) to come prepared with simple empty projects in popular languages/frameworks that have their SDKs setup in it. 77 | 78 | > **ACTION ITEM**: Create online form system for the "mentor pool". 79 | > 80 | > **ACTION ITEM**: Create a tool for team building that's targeted for hackers with no previous experience to match with experienced. 81 | -------------------------------------------------------------------------------- /mentorship_sun_1: -------------------------------------------------------------------------------- 1 | Mentorship and Learning discussion, Sunday 2 | 3 | How can we get beginners comfortable? 4 | - get alumni to help out 5 | > Linkedin, email, etc. 6 | - use sponsor mentors 7 | - tech talks to teach beginners 8 | 9 | Don't try to teach everything overnight. 10 | - just leave the event with a working project 11 | - portfolio pages are great. 12 | 13 | How to you distinguish mentors from hackers? 14 | - colored bandanas. 15 | - wristbands 16 | - different colored shirts (sponsors, hackers, mentors) 17 | - CAPES 18 | 19 | How did you allocate swag? 20 | - clear definition coming in of mentor v hacker 21 | - having peers as mentors can be troublesome 22 | - workshops are a risk, sometimes they're good but can be a fail 23 | 24 | How to make mentors available? 25 | - online form for mentors 26 | - app shows available mentors and help requests get divvied out 27 | - the thread pool, mentors can help with their specific mentors 28 | 29 | How do you prepare mentors prior to the event? 30 | - create a mentors guide. 31 | - started mentorship discussion with sponsorship 32 | - push people to bring engineers <- this is big 33 | - more engineers makes a more successful event 34 | - differentiate from a career fair 35 | - let mentors know that being around more is always good. 36 | 37 | What about incentivizing mentorship? 38 | - the best option is telling mentors that helping more is the best values 39 | - put the mentors with the hackers 40 | 41 | Try scheduling engineers to have shifts throuhout the weekend. 42 | 43 | What do you think about hackers helping other hackers? 44 | - Encourage teams and grouping up 45 | - Try and have advanced people to pair with beginners 46 | - separate experience with beginners 47 | - have a public page where people can tag problems for others to help 48 | - internal stack overflow 49 | - just make sure people follow up 50 | 51 | Adopt a beginner 52 | - match beginners with emails before the event 53 | > sort of fell apart after one email 54 | 55 | Just use github tickets. 56 | 57 | Sometimes you just need to have an ecosystem built up. 58 | 59 | Have project speed dating after the keynote. 60 | A team management tool for building an updating team. 61 | 62 | Don't worry about bad mentors, things will work out. 63 | - if they break the code of conduct though, that's an issue 64 | 65 | Maybe it would be good to have some example projects to point beginners to. 66 | - point mentors to beginners 67 | - have people for types of projects 68 | 69 | Have rooms for different types of hacks 70 | - webdev, mobile, hardware, etc. 71 | - put mentors with their strength 72 | - splitting rooms by subject can help with venues that are spread out 73 | 74 | * The best mentors have intrinsic motivation * 75 | - yay intangibles 76 | - maybe have mentors lead a workshop in the week coming up 77 | - but mentor game rooms and food are nice 78 | - make sure mentors aren't burned out 79 | - help them take care of themselves 80 | - SEND PERSONAL THANK YOU'S 81 | - reimburse mentor's travel rogue 82 | -------------------------------------------------------------------------------- /organization_sun_12: -------------------------------------------------------------------------------- 1 | Brynn from Pennapps 2 | Working with Organizations 3 | 4 | Reach out to these places to do cool things 5 | - not sponsors 6 | - not affiliated with your hackathon 7 | 8 | Go to other hackathons and learn how they do things 9 | - you can share organizers and volunteers 10 | 11 | Pennapps hackathon exchange 12 | It's a great way to help others and still learn 13 | 14 | Who can volunteer? 15 | Connected with volunteer organizations 16 | They have a reason to help, 17 | More incentive to stick around and show up 18 | Gets awesome new people involved. 19 | 20 | PennApps did health and stitchfest 21 | 22 | Can you partner with non-profits/ 23 | Be sure to understand the scope of the project 24 | Maybe it takes going outside of the weekend 25 | 26 | * The key is being able to bring in people who aren't in tech * 27 | -------------------------------------------------------------------------------- /stuff_you_dont_need.md: -------------------------------------------------------------------------------- 1 | Stuff You Don't Need 2 | ==================== 3 | 4 | - You don't need the coolest venue. 5 | - No one is going to remember that. 6 | - You don't need premium food. 7 | - No pizza. 8 | - Worry about people's different dietary needs. 9 | - Focus on having food that keeps students full. 10 | - You don't need t-shirts. 11 | - Cheaper swag that is personalized. 12 | - Things that are NOT t-shirts. 13 | - You don't need a BIG keynote speaker. 14 | - You don't need the "best" hacks. 15 | - You don't need the non-quantifiable words. 16 | - You don't need HUGE events. 17 | - ~100 - 600 people events are a good portion. 18 | - If you aren't doing the basic things right, 19 | - You don't need random attractions. 20 | - "Wow-factor" things like gaming rooms. 21 | - You (may not) need travel reimbursements. 22 | - We spend too much time doing this. 23 | - Worry about buses for people a few hours around, rather than getting people to fly from the other side of the country. 24 | - You don't need a fancy award ceremony 25 | - At the end of the hackathon, people are tired and want to go to sleep. 26 | - Don't stand inbetween people and sleep; no one will pay attention. -------------------------------------------------------------------------------- /use_these: -------------------------------------------------------------------------------- 1 | /* Just some reminders of stuff to use at the next hackathon */ 2 | 3 | Challenge Post will send reps! Email them 4 | 5 | Let's have a version control speedtalk! 6 | so many stuents in their first semesters don't know how to git. 7 | let's fix that 8 | 9 | A prehackathon prep session? 10 | does a sponsor want to do that? 11 | thursday night, speed prep sesh w/ sponsors. 12 | 13 | Can we make HackISU more about learning? 14 | 15 | Help organizers take care of themselves 16 | - have scheduled 'on-call' times 17 | - times when you're expected to be present 18 | 19 | Give sponsors a spotlight 20 | - prepare them for the spotlight. 21 | - clearly outline how much time sponsors have, and what is allowed 22 | 23 | Prizes can be trips or interviews. 24 | Let companies sponsor prizes, or interviews 25 | 26 | Api Speed dating?? if we have enoughi 27 | 28 | Mendeley API 29 | a16z - IOWA IS AWESOME LOVE US 30 | campusdata.org 31 | talk to Kleiner Perkins about ISU 32 | keenIO 33 | 34 | Maybe try a "Best ISU Hack" 35 | 36 | Can we have topics for the tech talks? or suggest things to sponsors that will be more effective? 37 | 38 | Can we have a thursday sponsorship dinner? <- that's a great place to do final prep for mentors and sponsors over last minute questions 39 | --------------------------------------------------------------------------------