1<!doctype html> 2<html> 3 <head> 4 <meta charset="utf-8"> 5 <link rel="stylesheet" href="https://unpkg.com/tachyons/css/tachyons.min.css"> 6 <link href="https://fonts.googleapis.com/css?family=Roboto+Condensed" rel="stylesheet"> 7 <link href="https://fonts.googleapis.com/css?family=Roboto" rel="stylesheet"> 8 <style> 9 .roboto { 10 font-family: 'Roboto', sans-serif; 11 } 12 .roboto-condensed { 13 font-family: 'Roboto Condensed', sans-serif; 14 } 15 16 @media print { 17 .no-print { 18 display: none !important; 19 } 20 21 .header-bg { 22 background: none; 23 } 24 } 25 </style> 26 <title>The Hack Day Manifesto</title> 27 </head> 28 29 <body> 30 <main class="roboto"> 31 32 <article> 33 <div class="center measure-wide f5 pt5 pb3 ph2 lh-copy"> 34 <h1 class="f1 f-headline-l roboto-condensed">The Hack Day Manifesto</h1> 35 <p>So you're organising a hack day or hackathon? Here are some basic requirements 36to make your event a success, and avoid the common pitfalls that could otherwise 37ruin it. If you cannot provide any of the following, make it clear to guests 38before registration. Attendees are generally forgiving when clear communication 39is given. These are only guidelines, but exist to help you run a hack day in the 40easiest possible way.</p> 41<h1 class="f2 lh-title roboto-condensed">Announcing the event</h1> 42<p>Once you know when and how your event will take place, you'll want to tell the 43world about it. At a bare minimum, you should decide on a canonical place where 44all public information about the event lives - this might be a dedicated web 45site, an event on an existing event online service or some other place which is 46publicly accessible.</p> 47<p>Once you've decided where that location is, use tools like Twitter and Facebook 48to make people aware of the event, and also consider which Google Groups and 49mailing lists developers relevant to your event may be hanging out. Don't spam 50them, though - nobody enjoys that.</p> 51<h2 class="f3 roboto-condensed">Registration <small class="fr gray">Optional</small></h2> 52<p>If you require your attendees to register, make it clear what information is 53required for signing up and what the deadline for the registration is. If 54there's a maximum number of attendees the venue can handle, communicate how the 55selection process works and when/how people will be notified if they've been 56granted attendance or not.</p> 57<p>If there's a waiting list for the event, make sure to explain how it works.</p> 58<p>Most registration forms lets applicants enter name, contact details and food 59preferences/allergies (if applicable). Depending on your event and your venue, 60you might want to ask for additional information - this manifesto lists a few 61other topics which might make sense to add to the registration form.</p> 62<p>There are also a number of things you probably should <em>not</em> ask for, like 63gender, religious preferences etc.</p> 64<h1 class="f2 lh-title roboto-condensed">Venue</h1> 65<h2 class="f3 roboto-condensed">Location</h2> 66<p>The venue should be relatively easy for people from outside of town to locate, 67with good public transport links. If it's difficult to reach, try to provide 68alternative means of transportation, such as coaches to/from local transport 69hubs throughout the event. Provide a full address, and if necessary, 70additional instructions to all attendees well in advance of the event.</p> 71<p>Include instructions/contacts/getting in arrangements, too (i.e., what 72to do at reception/security desks).</p> 73<p>Print big signs that will guide your attendees to the venue (and in some case 74inside the venue).</p> 75<h2 class="f3 roboto-condensed">Accessibility</h2> 76<p>Hack day venues should be accessible to everyone: at a bare minimum, there 77should be step-free access to all common parts of the building. If an attendee 78is blind or deaf, they should be able to participate too. Make sure your event 79signup forms mention accessibility and ask what accommodations might be needed.</p> 80<h2 class="f3 roboto-condensed">Insurance</h2> 81<p>Does your venue have the relevant insurance? Are guests' belongings protected in 82case of fire or theft? If not, you should make them aware of the risks so they 83can take extra precautions.</p> 84<p>Do you, as an organizer have adequate insurance?</p> 85<h2 class="f3 roboto-condensed">Security</h2> 86<p>Attendees will often be bringing a lot of expensive kit: laptops, tablets, etc. 87Make sure they have some security. If the venue does not have some form of 88lockers, can you run a cloakroom system?</p> 89<h2 class="f3 roboto-condensed">Secure sites and photo ID</h2> 90<p>Are the rooms going to be available to non-attendees? Work out whether you are 91running a secure site and whether people need to bring photo ID; if so, tell 92them when they sign up and remind them close to the event date. For some people,
93showing photo ID may be a deal breaker. Not everyone will have 94'government issued ID', either. Providing proof of address may be hard for some.</p> 95<h1 class="f2 lh-title roboto-condensed">Dates</h1> 96<h2 class="f3 roboto-condensed">Weekend or Not?</h2> 97<p>Most hack days are held at the weekend as this allows people to attend without 98taking time off work. If you are planning a hack day that begins on a Friday, 99remember that this may limit the number of people willing to travel after work.</p> 100<h2 class="f3 roboto-condensed">Checking for clashes</h2> 101<p>One of the most frustrating things for attendees to see is two similar events 102on the same day in the same area. To avoid this, check places like 103<a href="http://www.lanyrd.com">Lanyrd</a>, <a href="http://eventbrite.com">Eventbrite</a>, <a href="http://www.meetup.com">Meetup</a>, 104and ask on Twitter "is anything going on in X on X?". Remember that people may be 105travelling long distances for hack days, so even if an event is a few hundred 106miles away, you are still diluting your potential audience.</p> 107<h1 class="f2 lh-title roboto-condensed">Overnight Events</h1> 108<h2 class="f3 roboto-condensed">Sleeping provision</h2> 109<p>If attendees are staying overnight, then a separate (dark, quiet) area should be 110available away from the hacking should people decide to sleep. If possible, this 111should be several areas potentially including dedicated areas, for example 112male/female/mixed, minors (+chaperones?), snorer/non-snorer, night-owls/early birds.</p> 113<h2 class="f3 roboto-condensed">Showers <small class="fr gray">Optional</small></h2> 114<p>Despite the stereotypes, most geeks like to keep clean. Only a few venues are 115able to provide showers - but if you can, you should. Make sure you tell 116attendees well in advance so they can bring towels and toiletries.</p> 117<h1 class="f2 lh-title roboto-condensed">Network</h1> 118<h2 class="f3 roboto-condensed">Your 4MB DSL isn't enough</h2> 119<p>Hack days have special requirements: don't just trust anyone who tells you that 120"it'll be fine". Think about the networking issues, and verify that they work 121for the kind of capacity you are going to have. People from the venue or their 122commercial partner will tell you all sorts of things you want to hear but keep 123in the back of your mind that they may not have any clue what they are talking 124about. Given the importance of network access, if you are operating a commercial 125event consider requiring network performance as part of your contract with 126venues and suppliers.</p> 127<h2 class="f3 roboto-condensed">Rock solid WiFi</h2> 128<p>Many commercial WiFi providers plan for much lower use than actually occurs at 129hack days. The network should be capable of handling at least 4 devices per 130attendee.</p> 131<h2 class="f3 roboto-condensed">Minimal firewalling</h2> 132<p>As a minimum: ports used for SSH (22), DNS (53 â TCP & UDP), 133VPN (47, 500, 1701, 1723, 5500), HTTP (80), NTP (123 â UDP), 134HTTPS (443), Submissions (587), IMAPS (993), 135MQTT (1883), CVS (2401), Subversion (3690), XMPP/Jabber (5222), IRC (6665-9), 136and Git (9418), must be open and accessible, without the need of 137proxy servers, and preferably without perimeter-level malware checks.</p> 138<h2 class="f3 roboto-condensed">Subnet / DHCP capacity</h2> 139<p>Subnet and DHCP server must have capacity for allocating 6 IPv4 (and 140optionally, IPv6) addresses (preferably a /29) per hacker.</p> 141<p>If NAT is not used, attendees should be informed in advance.</p> 142<h2 class="f3 roboto-condensed">WiFi security</h2> 143<p>Use WPA2 security over an open WiFi network, to offer some basic protection 144against the monitoring of other users' network traffic.</p> 145<h2 class="f3 roboto-condensed">No device isolation</h2> 146<p>Attendees should be reminded that when connected to the network, their devices 147may be accessible to all other devices on the network so they would be wise to 148secure them.</p> 149<p>Organisers should make it clear that they absolve themselves of 150liability for any intrusion or damage caused over the network. Attendees will 151want to share resources with other attendees (version control, for example) but 152while it would be wise for them to do so in a controlled manner it is ultimately 153up to each individual to be responsible for the security of their own devices, 154connected or otherwise.</p> 155<p>Attendees should be encouraged/advised to run their own firewalls, 156too, remembering that IPv6 exists.</p> 157<h2 class="f3 roboto-condensed">IP Whitelisting</h2> 158<p>For events with 150 attendees or more, you will need to contact organisations 159such as Twitter, Google, and Freenode in advance to inform them of the increased 160number of connections from your IP range; they may have an existing process that 161you should use.</p> 162<p>In many cases, rate-limiting is handled by authentication, not IP 163address (ranges).</p> 164<p>For Freenode, email <a href="mailto:[email protected]">[email protected]</a> with dates, 165expected number of attendees and IP addresses if possible.</p> 166<h2 class="f3 roboto-condensed">QoS and Monitoring</h2> 167<p>Traffic shaping and monitoring should be employed to help prevent a few users 168abusing the connection to the detriment of all others.</p> 169<p>
169Deep packet inspection should not be used.</p> 170<h2 class="f3 roboto-condensed">Ethernet to the Chair <small class="fr gray">Optional</small></h2> 171<p>In case of WiFi collapse (or if you can't provide adequate WiFi at all) you 172should have ethernet available at the chairs. Have at least 100 megabit ethernet 173feeding into a gigabit backbone arranged in an (extended) star topology. 174If you go ethernet-only, announce this up-front. Regardless if you provide 175cables or attendees bring their own, you should have a big pile of spare 176cables at the venue.</p> 177<h2 class="f3 roboto-condensed">Single subnet <small class="fr gray">Optional</small></h2> 178<p>Both WiFi and ethernet should share a single subnet, allowing devices to 179communicate regardless of how they are connected to the network.</p> 180<h1 class="f2 lh-title roboto-condensed">Power</h1> 181<h2 class="f3 roboto-condensed">Power sockets</h2> 182<p>You will need a minimum of 1.5 power sockets available for every seat. That's a 183minimum; many attendees will bring two, three, or more devices that require 184separate power. Have spare cables available. Make sure you have access to the 185 fuses of all used power circuits, and review power requirements with the venue.</p> 186<h2 class="f3 roboto-condensed">Portable Appliance Testing</h2> 187<p>As stated above, your attendees will be bringing two, three, or more devices 188making full PATs for every device an impossible endeavour. But if you are 189providing a lot of power strips it can be worth getting them tested.</p> 190<h2 class="f3 roboto-condensed">Isolated power for hardware hacks <small class="fr gray">Optional</small></h2> 191<p>Isolating the power for those doing hardware hacks is generally a good idea, 192don't let one soldering iron knock out the power for the entire venue.</p> 193<h1 class="f2 lh-title roboto-condensed">Sustenance</h1> 194<h2 class="f3 roboto-condensed">Dietary requirements</h2> 195<p>Not everyone in the technical community is hyper-carnivorous. Be sure to 196check with your attendees for dietary requirements: food allergies, 197vegetarians, vegans and people with dietary restrictions. Make provisions 198to ensure they are provided for equally. If youâre on a budget, prioritise 199allergies and vegan alternatives; the vegan alternative will satisfy most 200non-allergy based requirements. Common food allergies include milk, eggs, 201nuts, fish, shellfish, soya, and wheat (gluten).</p> 202<p>It's important to note that that vegan meals exclude all animal products, 203not just meat, and therefore it should exclude eggs, cheese, milk, yoghurt, honey 204and much more.</p> 205<h2 class="f3 roboto-condensed">Breakfast</h2> 206<p>If your event starts before 11am you should provide breakfast to attendees, 207either continental or cooked.</p> 208<h2 class="f3 roboto-condensed">Lunch</h2> 209<p>You should provide a lunch for each day of the event, this should consist at 210least of sandwiches (or suitable alternatives for gluten intolerant folk).</p> 211<h2 class="f3 roboto-condensed">Dinner</h2> 212<p>If your event runs later than 6pm or overnight you should provide attendees with 213a proper evening meal, not sandwiches or snacks (and not everybody likes/eats pizza).</p> 214<h2 class="f3 roboto-condensed">Overnight</h2> 215<p>If your event runs through the night, you should arrange for food to be 216available throughout the night, either by periodically refreshing it or 217supplying something that can still be eaten after it has gone cold.</p> 218<h2 class="f3 roboto-condensed">Drinks</h2> 219<p>A selection of coffee, green and black tea (plus milks, sugars), energy drinks, 220caffeinated and non-caffeinated soft drinks, juices and <em>water</em> should be freely available to 221attendees throughout the event.</p> 222<h2 class="f3 roboto-condensed">Snacks</h2> 223<p>Chocolate, sweets, biscuits, fruit, crisps, etc. should be freely available to 224attendees throughout the event. Try to ensure there are healthy options too. 225Fresh fruit, nuts and vegetable platters can provide sustainable high energy levels to 226developers through out an event.</p> 227<h2 class="f3 roboto-condensed">Alcohol</h2> 228<p>Should be served as if you are the owner of your local bar because, in fact, 229you are. Check licensing rules with the venue, including where and when alcohol 230can be served and consumed and what time you need to stop serving. If you have underage attendees, 231make sure they're not served alcohol. Penalties for failing to do this could range 232from a fine to imprisonment for the person providing alcohol and loss of licence for the venue.</p> 233<h1 class="f2 lh-title roboto-condensed">APIs / Datasets</h1> 234<h2 class="f3 roboto-condensed">Presentations</h2> 235<p>Presentations by API and dataset providers should be kept to a minimum, try to 236make it a quick introduction involving the company name, the type of data / 237platform they have, and who to speak to for more information. Have technical - 238not marketing - people give the presentation as they will be asked technical 239questions, both on stage and during the rest of the event.</p> 240<h2 class="f3 roboto-condensed">Working APIs</h2> 241<p>The APIs pitched to attendees should be checked in advance by someone technical 242to confirm that they are suitable, work, and are of a high enough quality.</p> 243<h2 class="f3 roboto-condensed">Multiple clients</h2> 244<p>All APIs should provide client libraries in at least three major 245languages unless there is good reason for them not to (such as the target 246platform only supporting a single language).</p> 247<p>(And if you haven't got the client libraries written, maybe you need an 248internal hack day to write them!)</p> 249<h2 class="f3 roboto-condensed">Clean datasets</h2> 250<p>Datasets provided for use in the hack day should, where possible, be 251checked in advance by someone technical to ensure they are well 252structured and in a sensible format (CSV, XML, JSON, RDF etc., rather 253than Excel spreadsheets and PDFs).</p> 254<h2 class="f3 roboto-condensed">Thorough documentation</h2> 255<p>All APIs and datasets should have thorough documentation, detailing format, any 256codes or abbreviations, as well as the underlying assumptions and business logic 257of what it represents. The documentation should be checked by someone technical 258before announcing the API.</p> 259<h2 class="f3 roboto-condensed">Local downloads</h2> 260<p>Datasets -- especially large datasets -- should be available over the network 261from local servers without the need for registration, and where possible 262available on USB keys for even faster transfer.</p> 263<h2 class="f3 roboto-condensed">Make data explorable</h2> 264<p>Try and ensure that large datasets are accompanied by smaller sample files so 265attendees can check them for suitability and write parsers using a small number 266of records before downloading and importing multi-gigabyte files.</p> 267<h2 class="f3 roboto-condensed">API Keys</h2> 268<p>If an API requires a key to use it, then make sure that someone is on site and 269able to authorize the requests quickly, and with as little fuss as possible.</p> 270<h2 class="f3 roboto-condensed">Licensing</h2> 271<p>Get clear licensing information from API and dataset providers ahead of time, 272and communicate those licences clearly to the attendees, remembering that those 273in the technical community often have strong opinions about open licences for 274data and code.</p> 275<h2 class="f3 roboto-condensed">Longevity</h2> 276<p>Attendees are often averse to building on top of platforms and datasets that 277could disappear or will incur usage fees after an event, try to avoid companies 278making resources available only for the duration of the event and communicate 279clearly the risk of building on top of any alpha or beta APIs.</p> 280<h1 class="f2 lh-title roboto-condensed">Demos</h1> 281<h2 class="f3 roboto-condensed">Hack submissions</h2> 282<p>If possible, have a shared, public listing of the hacks that have been 283submitted. This helps the judges, the attendees and bloggers/journalists who are 284covering the event. Hack submissions should be as straight forward as possible. 285You can use Google Docs, Etherpad or a wiki. Make sure that all attendees have 286write access and can concurrently edit. Plan for the hack listing to stay around 287as a historical record. Alternatively, there are hack submission services that 288will handle the logistics for you like <a href="http://hackathon.io">Hackathon.io</a>, 289<a href="http://wehack.it/">WeHack.it</a>, or <a href="https://devpost.com/">Devpost</a>.</p> 290<p>Anyone who hacks should be a allowed to demo at the end of the event, regardless 291of the quality or completeness.</p> 292<h2 class="f3 roboto-condensed">Time limit</h2> 293<p>Each demo should be given a fixed time limit, standard times are 60, 90, 180,
294and 300 seconds. Tell presenters ahead of time, let them know how much time 295remains (either half time cards or an on-screen count down), and don't let them 296run over.</p> 297<h2 class="f3 roboto-condensed">Clear expectations</h2> 298<p>Try and communicate clear expectations for the demos to all attendees from the 299beginning of the event. Some attendees will become frustrated when they see 300others demo-ing paper prototypes or Photoshop mockups when they believed a 301working implementation was required. If hacks do not meet these base 302requirements, they should not be able to win a prize.</p> 303<h2 class="f3 roboto-condensed">Audience vote</h2> 304<p>If you have an "audience choice" prize, someone will attempt to game the system, 305either technically or by running an obnoxious "vote for me" campaign. Keep the 306prize for it relatively small, and give attendees a one-time token (a code on 307the reverse of their pass for large events, or a physical item for smaller ones) 308in order to vote.</p> 309<h2 class="f3 roboto-condensed">Judge selection</h2> 310<p>The judges for your hack day should reflect the nature of your event. 311For standard hack days, judges should be primarily technical or knowledgable in the relevant thematic area (eg. musicians judging Music Hack Day). 312Try to avoid having businesspeople (VCs, non-technical founders, journalists, etc.) judge technical events, as it encourages hackers to build prototype businesses, not interesting hacks. 313Your judging panel should be chosen to allow participants to win a hack day based purely on technical merit, even if the hack is completely impractical as a business.</p> 314<h2 class="f3 roboto-condensed">Judge previews <small class="fr gray">Optional</small></h2> 315<p>If possible, let the judges meet all the teams for a few minutes, a couple of 316hours before the presentations. This means people don't need to cram their whole 317idea in 60 seconds, but instead can demo the product to their peers knowing the 318judges understand how technically awesome their product is. This also allows for 319judges to fully inspect if a product was actually implemented, or is just a 320bunch of screenshots - and how technically advanced their project is.</p> 321<h1 class="f2 lh-title roboto-condensed">Audio / Video</h1> 322<h2 class="f3 roboto-condensed">Support</h2> 323<p>There should be staff on hand to help users set-up quickly for their demos, such 324as connecting to the projector. If the equipment at the venue allows it, have 325one demo presenting while the next is setting up.</p> 326<h2 class="f3 roboto-condensed">Video connectors</h2> 327<p>For the demos, either have a set of adapters handy for (Apple Mac) Thunderbolt, Mini DisplayPort, VGA, 328DVI, and HDMI video outputs, or make sure attendees know the projector's inputs 329ahead of time so they can make sure they have the relevant adapters.</p> 330<h2 class="f3 roboto-condensed">Projector info</h2> 331<p>Information on projector resolution, contrast, etc should be provided to 332attendees and speakers ahead of the event.</p> 333<h2 class="f3 roboto-condensed">Hardware and mobile hacks</h2> 334<p>If mobile or hardware hacks are expected, equipment to demonstrate them on the 335device should be present. Have a camera feed or visualiser available on the big 336screen. State ahead of time if that'll be provided, to allow these to be demoed 337adequately.</p> 338<h1 class="f2 lh-title roboto-condensed">Prizes</h1> 339<h2 class="f3 roboto-condensed">Not every hack day needs prizes</h2> 340<p>Some people go to hack days to learn, or to play. Having one team go home with 341enormous prizes and many other teams go home with nothing may sour the end of 342the event. Make sure it's not all about the money/toys.</p> 343<h2 class="f3 roboto-condensed">Prizes per team member</h2> 344<p>Prizes must be divisible to encourage teamwork: it is very hard to slice an iPod 345into three bits. If you wish to give away physical goods there should be enough 346that they may be given to each member of a reasonably sized team.</p> 347<h2 class="f3 roboto-condensed">Available on the day</h2> 348<p>Prizes should be on site on the day of judging and ready to be handed to 349attendees as the winners of the various prize categories are announced. 350Attendees should not need to claim a physical prize after the event unless said 351prize is dependent on winner. If the prize is not available on the day, clear 352printed instructions on how to claim must be provided instead.</p> 353<h2 class="f3 roboto-condensed">No cost to claim</h2> 354<p>Attendees should not be required to pay a subscription or sign a contract in 355order to claim or make use of their prize. Requiring prizewinners to do so is 356likely to induce negative feelings in the winner towards the company providing 357the prize and the hack day organisers.</p> 358<h2 class="f3 roboto-condensed">Avoid service prizes</h2> 359<p>Discounts and credit for an API, face time with a company's CEO, or development 360resources to continue a hack make for poor prizes (with obvious exceptions such 361as of companies offering music/video streaming services or online stores) and 362are likely to just disappoint the winning team. When organizations/individuals
363wish to pursue further development of a hack they should speak to the winning 364team separately.</p> 365<h1 class="f2 lh-title roboto-condensed">Atmosphere and attitudes</h1> 366<h2 class="f3 roboto-condensed">Don't make people feel unwelcome</h2> 367<p>Avoid sexism and other discriminatory language or attitudes. Don't make any 368assumptions about your attendees. Get someone who is demographically very 369different from you to check your marketing material through to see if it makes 370sense and isn't offensive to someone who doesn't share your background.</p> 371<p>Many event attendees expect events to have and enforce a code of conduct. Having 372such a code encourages diversity of participation and can help to create and maintain a 373welcoming environment. It is highly recommended to adopt a code of conduct for 374your event. One such example is the <a href="http://hackcodeofconduct.org">Hack Code of Conduct</a>, 375and there are several other appropriate examples. You can either reference your chosen 376code of conduct directly or create your own customized version. 377Make sure to communicate clearly to attendees ahead of time the existence of this 378code and the enforcement policy behind it. 379In addition, the code should be linked prominently from the event web site and 380promoted by the event organizers and by members of the event's community. The code 381should be known to and practiced by event staff and volunteers and enforcement 382procedures should be clear.</p> 383<h2 class="f3 roboto-condensed">Make assumptions around privacy clear</h2> 384<p>Tell people up front what level of privacy they should expect during the event.</p> 385<p>If you allow people to take photographs, tell photographers to respect people's 386privacy if they do not wish to be photographed: if someone objects to being 387photographed, they have a right to have that objection taken seriously.</p> 388<p>Sleeping areas should be explicitly marked as no photography as sleeping people 389are unable to implicitly consent to being photographed by not objecting.</p> 390<h2 class="f3 roboto-condensed">Do not charge attendees</h2> 391<p>If developers are willing to donate their time -- which could otherwise be used 392for paid work or hanging out with family and friends -- they should not be 393charged for tickets. It shows a complete disrespect for the value of their 394time, and is likely to leave a bad feeling towards the organisers and 395sponsors. The developers are providing the sponsors a service in testing and 396showing the possibility of their APIs, data, products and services.</p> 397<h2 class="f3 roboto-condensed">Intellectual property</h2> 398<p>The intellectual property rights of hacks produced at the event should belong to 399the attendees, and not to the organisers, sponsors, or partners, with the 400obvious exception of (a) hack days based around the further development of an open 401source project, or (b) commercially run hacks.</p> 402<p>Intellectual property can be a big issue; it is best to make expectations clear 403in advance, both to developers and to sponsors or data providers.</p> 404<h2 class="f3 roboto-condensed">What are you after?</h2> 405<p>Have some idea what counts as success, but don't be too tight: people will 406surprise you! Some hack days are specifically focused on one language or tool, 407others on a theme, while others are meant for a particular open source project 408or problem that needs solving. The point of the event will inform how you do 409marketing, judging and many other aspects of the event.</p> 410<h2 class="f3 roboto-condensed">This is not a rock concert!</h2> 411<p>Some hack days have hired bands or other entertainment. This is usually a bad 412idea. People are at the event to hack, and hacking requires extended periods of 413concentration. You don't need silence, but if you are thinking about putting on 414entertainment you may not understand exactly what the point of a hack day is. If 415you do insist on putting noisy entertainment on, don't be surprised if the 416people actually trying to build things go and hide in the lobby to carry on with 417what they are doing.</p> 418<h2 class="f3 roboto-condensed">Emergency plans</h2> 419<p>Make sure you have a plan for attendees who are injured, fall ill or
420suffer any other emergencies. Have at least one designated first aider 421on call. Make sure you know where the first aid box is, and check it's 422appropriately stocked. Know the procedures for calling an ambulance, 423sounding the fire alarm, evacuation point, and logging incidents in 424the venue. Make sure attendees know who to turn to for help; a phone 425number, a few bright crew shirts and a central crew desk or wardrobe 426go a long way. A central point of contact will also help you deal with 427inevitable electric, network, venue- or food-related questions.</p> 428<h2 class="f3 roboto-condensed">Handling problematic people</h2> 429<p>It's unlikely that you'll have to throw someone out, but just in case know what 430the procedures are, what you're legally able to do and what kind of misbehaviour 431would actually trigger ejection. Some events have instituted safe space and 432anti-harassment policies due to widely reported incidents of sexual harassment.</p> 433<h2 class="f3 roboto-condensed">Keep your crew safe too</h2> 434<p>Working at a hack day, as a volunteer or otherwise, can be a stressful and demanding 435job. Make sure your crew are safe, happy and well-fed throughout, and that 436you've got enough staff to cope with emergencies or unexpected dropouts!</p> 437<h2 class="f3 roboto-condensed">Finally, remember to have fun!</h2> 438<p>If you follow all these guidelines, prepare well in advance, and get plenty of 439rest before the big day, you'll maximize your odds of having an event that's 440not just successful, but enjoyable as well. Good luck!</p> 441 442 </div> 443 444 445 <div class="center measure-wide f5 pt5 pb3 ph2 lh-copy"> 446 <h1 class="f2 lh-title roboto-condensed no-print">Supporters</h1> 447 <div class="flex flex-wrap no-print"> 448 449 <div class="fl w-third pv3 pr2"> 450 <p class="f5 b pa0 ma0 fw"> 451 452 <a class="no-underline blue dim" href="http://danielknell.co.uk/">Daniel Knell</a> 453 454 </p> 455 <p class="pa0 ma0 f6">Way Past Eleven</p> 456 </div> 457 458 <div class="fl w-third pv3 pr2"> 459 <p class="f5 b pa0 ma0 fw"> 460 461 <a class="no-underline blue dim" href="http://tommorris.org/">Tom Morris</a> 462 463 </p> 464 <p class="pa0 ma0 f6"></p> 465 </div> 466 467 <div class="fl w-third pv3 pr2"> 468 <p class="f5 b pa0 ma0 fw"> 469 470 <a class="no-underline blue dim" href="http://geeksoflondon.com/">Kevin Prince</a> 471 472 </p> 473 <p class="pa0 ma0 f6">Geeks of London</p> 474 </div> 475 476 <div class="fl w-third pv3 pr2"> 477 <p class="f5 b pa0 ma0 fw"> 478 479 <a class="no-underline blue dim" href="http://geeksoflondon.com/">Melinda Seckington</a> 480 481 </p> 482 <p class="pa0 ma0 f6">Geeks of London & FutureLearn</p> 483 </div> 484 485 <div class="fl w-third pv3 pr2"> 486 <p class="f5 b pa0 ma0 fw"> 487 488 <a class="no-underline blue dim" href="http://geeksoflondon.com/">Cristiano Betta</a> 489 490 </p> 491 <p class="pa0 ma0 f6">Geeks of London & ex-PayPal</p> 492 </div> 493 494 <div class="fl w-third pv3 pr2"> 495 <p class="f5 b pa0 ma0 fw"> 496 497 <a class="no-underline blue dim" href="http://tomscott.com/">Tom Scott</a> 498 499 </p> 500 <p class="pa0 ma0 f6"></p> 501 </div> 502 503 <div class="fl w-third pv3 pr2"> 504 <p class="f5 b pa0 ma0 fw"> 505 506 <a class="no-underline blue dim" href="http://linkedgov.org/">Hadley Beeman</a> 507 508 </p> 509 <p class="pa0 ma0 f6"></p> 510 </div> 511 512 <div class="fl w-third pv3 pr2"> 513 <p class="f5 b pa0 ma0 fw"> 514 515 <a class="no-underline blue dim" href="http://abscond.org/">James Darling</a> 516 517 </p> 518 <p class="pa0 ma0 f6">Music Hack Day, Rewired State</p> 519 </div> 520 521 <div class="fl w-third pv3 pr2"> 522 <p class="f5 b pa0 ma0 fw"> 523 524 <a class="no-underline blue dim" href="http://arrelid.com/">Mattias Arrelid</a> 525 526 </p> 527 <p class="pa0 ma0 f6"></p> 528 </div> 529 530 <div class="fl w-third pv3 pr2"> 531 <p class="f5 b pa0 ma0 fw"> 532 533 <a class="no-underline blue dim" href="http://geeksoflondon.com/">Robert Lee-Cann</a> 534 535 </p> 536 <p class="pa0 ma0 f6">Geeks of London</p> 537 </div> 538 539 <div class="fl w-third pv3 pr2"> 540 <p class="f5 b pa0 ma0 fw"> 541 542 <a class="no-underline blue dim" href="http://thehodge.co.uk">Dom Hodgson</a> 543 544 </p> 545 <p class="pa0 ma0 f6">Leeds Hack</p> 546 </div> 547 548 <div class="fl w-third pv3 pr2"> 549 <p class="f5 b pa0 ma0 fw"> 550 551 <a class="no-underline blue dim" href="http://kaikoda.com">Sheila Thomson</a> 552 553 </p> 554 <p class="pa0 ma0 f6">Kaikoda</p> 555 </div> 556 557 <div class="fl w-third pv3 pr2"> 558 <p class="f5 b pa0 ma0 fw"> 559 560 <a class="no-underline blue dim" href="http://flexewebs.com">Jason Grant</a> 561 562 </p> 563 <p class="pa0 ma0 f6">Flexewebs</p> 564 </div> 565 566 <div class="fl w-third pv3 pr2"> 567 <p class="f5 b pa0 ma0 fw"> 568 569 <a class="no-underline blue dim" href="http://inuda.org/">Jonathan Markwell</a> 570 571 </p> 572 <p class="pa0 ma0 f6">Inuda Community</p> 573 </div> 574 575 <div class="fl w-third pv3 pr2"> 576 <p class="f5 b pa0 ma0 fw"> 577 578 <a class="no-underline blue dim" href="http://greenhackathon.com/">Hannes Ebner</a> 579 580 </p> 581 <p class="pa0 ma0 f6">Green Hackathon</p> 582 </div> 583 584 <div class="fl w-third pv3 pr2"> 585 <p class="f5 b pa0 ma0 fw"> 586 587 <a class="no-underline blue dim" href="http://greenhackathon.com/">Jorge Zapico</a> 588 589 </p> 590 <p class="pa0 ma0 f6">Green Hackathon</p> 591 </div> 592 593 <div class="fl w-third pv3 pr2"> 594 <p class="f5 b pa0 ma0 fw"> 595 596 <a class="no-underline blue dim" href="https://andypiper.me">Andy Piper</a> 597 598 </p> 599 <p class="pa0 ma0 f6">Developer Advocate, Twitter</p> 600 </div> 601 602 <div class="fl w-third pv3 pr2"> 603 <p class="f5 b pa0 ma0 fw"> 604 605 <a class="no-underline blue dim" href="http://samlr.com/">Sam Cook</a> 606 607 </p> 608 <p class="pa0 ma0 f6"></p> 609 </div> 610 611 <div class="fl w-third pv3 pr2"> 612 <p class="f5 b pa0 ma0 fw"> 613 614 <a class="no-underline blue dim" href="http://hackdays.ca/">Chad McCallum</a> 615 616 </p> 617 <p class="pa0 ma0 f6">HackDays Organizer</p> 618 </div> 619 620 <div class="fl w-third pv3 pr2"> 621 <p class="f5 b pa0 ma0 fw"> 622 623 <a class="no-underline blue dim" href="http://micrypt.com/">Seyi Ogunyemi</a> 624 625 </p> 626 <p class="pa0 ma0 f6"></p> 627 </div> 628 629 <div class="fl w-third pv3 pr2"> 630 <p class="f5 b pa0 ma0 fw"> 631 632 <a class="no-underline blue dim" href="http://thelondonbiker.com">Matthew Cashmore</a> 633 634 </p> 635 <p class="pa0 ma0 f6">Hack Day Organiser</p> 636 </div> 637 638 <div class="fl w-third pv3 pr2"> 639 <p class="f5 b pa0 ma0 fw"> 640 641 <a class="no-underline blue dim" href="http://renocollective.com/">Colin Loretz</a> 642 643 </p> 644 <p class="pa0 ma0 f6">Reno Collective/Hack4Reno</p> 645 </div> 646 647 <div class="fl w-third pv3 pr2"> 648 <p class="f5 b pa0 ma0 fw"> 649 650 <a class="no-underline blue dim" href="http://renocollective.com/">Don Morrison</a> 651 652 </p> 653 <p class="pa0 ma0 f6">Reno Collective/Hack4Reno</p> 654 </div> 655 656 <div class="fl w-third pv3 pr2"> 657 <p class="f5 b pa0 ma0 fw"> 658 659 <a class="no-underline blue dim" href="http://hackdeoverheid.nl">Alper Cugun</a> 660 661 </p> 662 <p class="pa0 ma0 f6">Hack de Overheid</p> 663 </div> 664 665 <div class="fl w-third pv3 pr2"> 666 <p class="f5 b pa0 ma0 fw"> 667 668 <a class="no-underline blue dim" href="http://amyl.org.uk/">Adam McGreggor</a> 669 670 </p> 671 <p class="pa0 ma0 f6">Developer Network Builder</p> 672 </div> 673 674 <div class="fl w-third pv3 pr2"> 675 <p class="f5 b pa0 ma0 fw"> 676 677 <a class="no-underline blue dim" href="http://patriciomolina.com">Patricio Molina</a> 678 679 </p> 680 <p class="pa0 ma0 f6">Software developer, Wikipedist</p> 681 </div> 682 683 <div class="fl w-third pv3 pr2"> 684 <p class="f5 b pa0 ma0 fw"> 685 686 <a class="no-underline blue dim" href="http://hackerleague.org">Abe Stanway</a> 687 688 </p> 689 <p class="pa0 ma0 f6">Hacker League</p> 690 </div> 691 692 <div class="fl w-third pv3 pr2"> 693 <p class="f5 b pa0 ma0 fw"> 694 695 <a class="no-underline blue dim" href="http://micheljansen.org/">
695Michel Jansen</a> 696 697 </p> 698 <p class="pa0 ma0 f6"></p> 699 </div> 700 701 <div class="fl w-third pv3 pr2"> 702 <p class="f5 b pa0 ma0 fw"> 703 704 <a class="no-underline blue dim" href="http://hackerleague.org/">Swift</a> 705 706 </p> 707 <p class="pa0 ma0 f6">Hacker League</p> 708 </div> 709 710 <div class="fl w-third pv3 pr2"> 711 <p class="f5 b pa0 ma0 fw"> 712 713 <a class="no-underline blue dim" href="http://overtheair.org">Margaret Gold</a> 714 715 </p> 716 <p class="pa0 ma0 f6">Over the Air</p> 717 </div> 718 719 <div class="fl w-third pv3 pr2"> 720 <p class="f5 b pa0 ma0 fw"> 721 722 <a class="no-underline blue dim" href="http://pennapps.com">Alexey Komissarouk</a> 723 724 </p> 725 <p class="pa0 ma0 f6">PennApps</p> 726 </div> 727 728 <div class="fl w-third pv3 pr2"> 729 <p class="f5 b pa0 ma0 fw"> 730 731 <a class="no-underline blue dim" href="http://mager.co">Andrew Mager</a> 732 733 </p> 734 <p class="pa0 ma0 f6">Hacker Advocate, Spotify</p> 735 </div> 736 737 <div class="fl w-third pv3 pr2"> 738 <p class="f5 b pa0 ma0 fw"> 739 740 <a class="no-underline blue dim" href="http://api.jack.ly">Jack Pearkes</a> 741 742 </p> 743 <p class="pa0 ma0 f6">Developer Advocate, Kiip</p> 744 </div> 745 746 <div class="fl w-third pv3 pr2"> 747 <p class="f5 b pa0 ma0 fw"> 748 749 <a class="no-underline blue dim" href="http://forwardtechnology.co.uk">Andrew Nesbitt</a> 750 751 </p> 752 <p class="pa0 ma0 f6">Developer, Forward</p> 753 </div> 754 755 <div class="fl w-third pv3 pr2"> 756 <p class="f5 b pa0 ma0 fw"> 757 758 <a class="no-underline blue dim" href="http://mijndertstuij.nl">Mijndert Stuij</a> 759 760 </p> 761 <p class="pa0 ma0 f6"></p> 762 </div> 763 764 <div class="fl w-third pv3 pr2"> 765 <p class="f5 b pa0 ma0 fw"> 766 767 <a class="no-underline blue dim" href="http://MusicMachinery.com">Paul Lamere</a> 768 769 </p> 770 <p class="pa0 ma0 f6">Music Hack Day</p> 771 </div> 772 773 <div class="fl w-third pv3 pr2"> 774 <p class="f5 b pa0 ma0 fw"> 775 776 <a class="no-underline blue dim" href="http://sammachin.com">Sam Machin</a> 777 778 </p> 779 <p class="pa0 ma0 f6">Geek</p> 780 </div> 781 782 <div class="fl w-third pv3 pr2"> 783 <p class="f5 b pa0 ma0 fw"> 784 785 <a class="no-underline blue dim" href="http://mattclements.co.uk">Matt Clements</a> 786 787 </p> 788 <p class="pa0 ma0 f6">Developer</p> 789 </div> 790 791 <div class="fl w-third pv3 pr2"> 792 <p class="f5 b pa0 ma0 fw"> 793 794 <a class="no-underline blue dim" href="http://sydlawrence.com">Syd Lawrence</a> 795 796 </p> 797 <p class="pa0 ma0 f6">Developer</p> 798 </div> 799 800 <div class="fl w-third pv3 pr2"> 801 <p class="f5 b pa0 ma0 fw"> 802 803 <a class="no-underline blue dim" href="http://openlexington.org">Chase Southard</a> 804 805 </p> 806 <p class="pa0 ma0 f6">OpenLexington</p> 807 </div> 808 809 <div class="fl w-third pv3 pr2"> 810 <p class="f5 b pa0 ma0 fw"> 811 812 <a class="no-underline blue dim" href="http://carter.rabasa.com">Carter Rabasa</a> 813 814 </p> 815 <p class="pa0 ma0 f6">Developer Evangelist, Twilio</p> 816 </div> 817 818 <div class="fl w-third pv3 pr2"> 819 <p class="f5 b pa0 ma0 fw"> 820 821 <a class="no-underline blue dim" href="http://design-mensch.de">Jannette Mensch</a> 822 823 </p> 824 <p class="pa0 ma0 f6">IxD & Hack Day participant</p> 825 </div> 826 827 <div class="fl w-third pv3 pr2"> 828 <p class="f5 b pa0 ma0 fw"> 829 830 <a class="no-underline blue dim" href="http://apassant.net">Alexandre Passant</a> 831 832 </p> 833 <p class="pa0 ma0 f6">Music and Data Geek</p> 834 </div> 835 836 <div class="fl w-third pv3 pr2"> 837 <p class="f5 b pa0 ma0 fw"> 838 839 <a class="no-underline blue dim" href="http://paulosman.me">Paul Osman</a> 840 841 </p> 842 <p class="pa0 ma0 f6">Developer Evangelist, SoundCloud</p> 843 </div> 844 845 <div class="fl w-third pv3 pr2"> 846 <p class="f5 b pa0 ma0 fw"> 847 848 <a class="no-underline blue dim" href="http://wawra.co.uk">Michael Wawra</a> 849 850 </p> 851 <p class="pa0 ma0 f6">Geek</p> 852 </div> 853 854 <div class="fl w-third pv3 pr2"> 855 <p class="f5 b pa0 ma0 fw"> 856 857 <a class="no-underline blue dim" href="http://chrisweekly.com/">Chris Weekly</a> 858 859 </p> 860 <p class="pa0 ma0 f6"></p> 861 </div> 862 863 <div class="fl w-third pv3 pr2"> 864 <p class="f5 b pa0 ma0 fw"> 865 866 <a class="no-underline blue dim" href="http://adactio.com/">Jeremy Keith</a> 867 868 </p> 869 <p class="pa0 ma0 f6">Founder, Science Hack Day</p> 870 </div> 871 872 <div class="fl w-third pv3 pr2"> 873 <p class="f5 b pa0 ma0 fw"> 874 875 <a class="no-underline blue dim" href="http://twitter.com/smithsam">Sam Smith</a> 876 877 </p> 878 <p class="pa0 ma0 f6">organiser, ex-RS, wears semi-contradictory hats</p> 879 </div> 880 881 <div class="fl w-third pv3 pr2"> 882 <p class="f5 b pa0 ma0 fw"> 883 884 <a class="no-underline blue dim" href="http://freenerd.de">Johan Uhle</a> 885 886 </p> 887 <p class="pa0 ma0 f6">Freenerd, Music Hack Day organizer</p> 888 </div> 889 890 <div class="fl w-third pv3 pr2"> 891 <p class="f5 b pa0 ma0 fw"> 892 893 <a class="no-underline blue dim" href="https://twitter.com/SeraAndroid">Tim Messerschmidt</a> 894 895 </p> 896 <p class="pa0 ma0 f6">Developer Evangelist, PayPal</p> 897 </div> 898 899 <div class="fl w-third pv3 pr2"> 900 <p class="f5 b pa0 ma0 fw"> 901 902 <a class="no-underline blue dim" href="http://blog.johnbunting.me">John Bunting</a> 903 904 </p> 905 <p class="pa0 ma0 f6">Tumblr API Lead</p> 906 </div> 907 908 <div class="fl w-third pv3 pr2"> 909 <p class="f5 b pa0 ma0 fw"> 910 911 <a class="no-underline blue dim" href="http://twitter.com/jonmarkgo">Jonathan Gottfried</a> 912 913 </p> 914 <p class="pa0 ma0 f6">
914Developer Evangelist at Twilio, hackathon organizer</p> 915 </div> 916 917 <div class="fl w-third pv3 pr2"> 918 <p class="f5 b pa0 ma0 fw"> 919 920 <a class="no-underline blue dim" href="http://blog.clickslide.co">Aaron Franco</a> 921 922 </p> 923 <p class="pa0 ma0 f6">CTO at ClickSlide Limited</p> 924 </div> 925 926 <div class="fl w-third pv3 pr2"> 927 <p class="f5 b pa0 ma0 fw"> 928 929 <a class="no-underline blue dim" href="http://martyndavies.me">Martyn Davies</a> 930 931 </p> 932 <p class="pa0 ma0 f6">Coordinator, Music Hack Day</p> 933 </div> 934 935 <div class="fl w-third pv3 pr2"> 936 <p class="f5 b pa0 ma0 fw"> 937 938 <a class="no-underline blue dim" href="http://twitter.com/matthewforr">Matthew Forr</a> 939 940 </p> 941 <p class="pa0 ma0 f6">Baltimore Hackathon Organizer</p> 942 </div> 943 944 <div class="fl w-third pv3 pr2"> 945 <p class="f5 b pa0 ma0 fw"> 946 947 <a class="no-underline blue dim" href="http://joel.franusic.com">Joel Franusic</a> 948 949 </p> 950 <p class="pa0 ma0 f6">Developer Evangelist, Twilio</p> 951 </div> 952 953 <div class="fl w-third pv3 pr2"> 954 <p class="f5 b pa0 ma0 fw"> 955 956 <a class="no-underline blue dim" href="http://cleanweb.org.uk">James Smith</a> 957 958 </p> 959 <p class="pa0 ma0 f6">Cleanweb UK</p> 960 </div> 961 962 <div class="fl w-third pv3 pr2"> 963 <p class="f5 b pa0 ma0 fw"> 964 965 <a class="no-underline blue dim" href="http://stefanopaluello.wordpress.com">Stefano Paluello</a> 966 967 </p> 968 <p class="pa0 ma0 f6">Geek, Pastesoft</p> 969 </div> 970 971 <div class="fl w-third pv3 pr2"> 972 <p class="f5 b pa0 ma0 fw"> 973 974 <a class="no-underline blue dim" href="http://about.me/daigofujiwara">Daigo Fujiwara</a> 975 976 </p> 977 <p class="pa0 ma0 f6">Founder, Boston Baseball Hack Day</p> 978 </div> 979 980 <div class="fl w-third pv3 pr2"> 981 <p class="f5 b pa0 ma0 fw"> 982 983 <a class="no-underline blue dim" href="http://twitter.com/olofster">Olof Mathé</a> 984 985 </p> 986 <p class="pa0 ma0 f6">Art Hack Day organizer</p> 987 </div> 988 989 <div class="fl w-third pv3 pr2"> 990 <p class="f5 b pa0 ma0 fw"> 991 992 <a class="no-underline blue dim" href="http://www.hackitarians.com">Richard Kastelein</a> 993 994 </p> 995 <p class="pa0 ma0 f6">Hackfest Organiser</p> 996 </div> 997 998 <div class="fl w-third pv3 pr2"> 999 <p class="f5 b pa0 ma0 fw"> 1000 1001 <a class="no-underline blue dim" href="http://twilio.com">James Parton</a> 1002 1003 </p> 1004 <p class="pa0 ma0 f6">Twilio</p> 1005 </div> 1006 1007 <div class="fl w-third pv3 pr2"> 1008 <p class="f5 b pa0 ma0 fw"> 1009 1010 <a class="no-underline blue dim" href="http://developers.hyves.nl">Derk Braakman</a> 1011 1012 </p> 1013 <p class="pa0 ma0 f6">Product Manager API, Hyves</p> 1014 </div> 1015 1016 <div class="fl w-third pv3 pr2"> 1017 <p class="f5 b pa0 ma0 fw"> 1018 1019 <a class="no-underline blue dim" href="http://stereoartist.com) Developer (Titanium AppCamp & London Titanium organiser">Ketan Majmudar</a> 1020 1021 </p> 1022 <p class="pa0 ma0 f6"></p> 1023 </div> 1024 1025 <div class="fl w-third pv3 pr2"> 1026 <p class="f5 b pa0 ma0 fw"> 1027 1028 <a class="no-underline blue dim" href="http://twitter.com/aoberoi">Ankur Oberoi</a> 1029 1030 </p> 1031 <p class="pa0 ma0 f6">Developer Evangelist, TokBox</p> 1032 </div> 1033 1034 <div class="fl w-third pv3 pr2"> 1035 <p class="f5 b pa0 ma0 fw"> 1036 1037 <a class="no-underline blue dim" href="http://stemount.co.uk">Stephen Mount</a> 1038 1039 </p> 1040 <p class="pa0 ma0 f6">Developer</p> 1041 </div> 1042 1043 <div class="fl w-third pv3 pr2"> 1044 <p class="f5 b pa0 ma0 fw"> 1045 1046 <a class="no-underline blue dim" href="http://overtheair.org">Daniel Appelquist</a> 1047 1048 </p> 1049 <p class="pa0 ma0 f6">Over the Air</p> 1050 </div> 1051 1052 <div class="fl w-third pv3 pr2"> 1053 <p class="f5 b pa0 ma0 fw"> 1054 1055 <a class="no-underline blue dim" href="http://twitter.com/adamyeats">Adam Yeats</a> 1056 1057 </p> 1058 <p class="pa0 ma0 f6">Developer Relations Engineer, Pusher</p> 1059 </div> 1060 1061 <div class="fl w-third pv3 pr2"> 1062 <p class="f5 b pa0 ma0 fw"> 1063 1064 <a class="no-underline blue dim" href="http://hacksocnotts.co.uk">Joe Nash</a> 1065 1066 </p> 1067 <p class="pa0 ma0 f6">
1067HackSoc Nottingham founder & organiser</p> 1068 </div> 1069 1070 <div class="fl w-third pv3 pr2"> 1071 <p class="f5 b pa0 ma0 fw"> 1072 1073 <a class="no-underline blue dim" href="http://www.mattstine.com">Matt Stine</a> 1074 1075 </p> 1076 <p class="pa0 ma0 f6">Community Engineer, Cloud Foundry</p> 1077 </div> 1078 1079 <div class="fl w-third pv3 pr2"> 1080 <p class="f5 b pa0 ma0 fw"> 1081 1082 <a class="no-underline blue dim" href="http://elsmore.me">Mike Elsmore</a> 1083 1084 </p> 1085 <p class="pa0 ma0 f6">Hackference founder & organiser</p> 1086 </div> 1087 1088 <div class="fl w-third pv3 pr2"> 1089 <p class="f5 b pa0 ma0 fw"> 1090 1091 <a class="no-underline blue dim" href="http://www.whymca.org/">Paolo Sinelli</a> 1092 1093 </p> 1094 <p class="pa0 ma0 f6">WhyMCA co-founder & organiser</p> 1095 </div> 1096 1097 <div class="fl w-third pv3 pr2"> 1098 <p class="f5 b pa0 ma0 fw"> 1099 1100 <a class="no-underline blue dim" href="http://twitter.com/JamesAaronCox/">James Cox</a> 1101 1102 </p> 1103 <p class="pa0 ma0 f6">Developer Evangelist, The Hackfest</p> 1104 </div> 1105 1106 <div class="fl w-third pv3 pr2"> 1107 <p class="f5 b pa0 ma0 fw"> 1108 1109 <a class="no-underline blue dim" href="http://twitter.com/HackyGoLucky">Tracy Abrahms</a> 1110 1111 </p> 1112 <p class="pa0 ma0 f6">PDXNode organizer</p> 1113 </div> 1114 1115 <div class="fl w-third pv3 pr2"> 1116 <p class="f5 b pa0 ma0 fw"> 1117 1118 <a class="no-underline blue dim" href="http://scottmotte.com">Scott Motte</a> 1119 1120 </p> 1121 <p class="pa0 ma0 f6">Developer Evangelist, SendGrid</p> 1122 </div> 1123 1124 <div class="fl w-third pv3 pr2"> 1125 <p class="f5 b pa0 ma0 fw"> 1126 1127 <a class="no-underline blue dim" href="http://www.meetup.com/UK-Hackathons-and-Jams/">Rob Finean</a> 1128 1129 </p> 1130 <p class="pa0 ma0 f6">UK Hackathons & Jams</p> 1131 </div> 1132 1133 <div class="fl w-third pv3 pr2"> 1134 <p class="f5 b pa0 ma0 fw"> 1135 1136 <a class="no-underline blue dim" href="http://twitter.com/BillinghamJ">James Billingham</a> 1137 1138 </p> 1139 <p class="pa0 ma0 f6"></p> 1140 </div> 1141 1142 <div class="fl w-third pv3 pr2"> 1143 <p class="f5 b pa0 ma0 fw"> 1144 1145 <a class="no-underline blue dim" href="http://twitter.com/tfogo">Tim Fogarty</a> 1146 1147 </p> 1148 <p class="pa0 ma0 f6">Major League Hacking UK, HackSoc Nottingham</p> 1149 </div> 1150 1151 <div class="fl w-third pv3 pr2"> 1152 <p class="f5 b pa0 ma0 fw"> 1153 1154 <a class="no-underline blue dim" href="http://arielwaldman.com">Ariel Waldman</a> 1155 1156 </p> 1157 <p class="pa0 ma0 f6">Global Instigator, Science Hack Day</p> 1158 </div> 1159 1160 <div class="fl w-third pv3 pr2"> 1161 <p class="f5 b pa0 ma0 fw"> 1162 1163 <a class="no-underline blue dim" href="http://hack4good.io">Dan Cunningham</a> 1164 1165 </p> 1166 <p class="pa0 ma0 f6">Head of Geeklist Corps of Developers + #hack4good global organiser</p> 1167 </div> 1168 1169 <div class="fl w-third pv3 pr2"> 1170 <p class="f5 b pa0 ma0 fw"> 1171 1172 <a class="no-underline blue dim" href="http://ruparel.co">Shyamal Ruparel</a> 1173 1174 </p> 1175 <p class="pa0 ma0 f6">LocalHackDay.mlh.io organizer</p> 1176 </div> 1177 1178 <div class="fl w-third pv3 pr2"> 1179 <p class="f5 b pa0 ma0 fw"> 1180 1181 <a class="no-underline blue dim" href="http://www.hackhumanity.org">Klaus Bravenboer</a> 1182 1183 </p> 1184 <p class="pa0 ma0 f6">HackHumanity founder + organizer</p> 1185 </div> 1186 1187 <div class="fl w-third pv3 pr2"> 1188 <p class="f5 b pa0 ma0 fw"> 1189 1190 <a class="no-underline blue dim" href="http://www.hack24.co.uk">Andrew Seward</a> 1191 1192 </p> 1193 <p class="pa0 ma0 f6">Hack24 founder & organizer</p> 1194 </div> 1195 1196 <div class="fl w-third pv3 pr2"> 1197 <p class="f5 b pa0 ma0 fw"> 1198 1199 <a class="no-underline blue dim" href="http://www.multizone.co.uk">Angus Fox</a> 1200 1201 </p> 1202 <p class="pa0 ma0 f6">CTO to go & Product Manager & Secretary, Social Developers London</p> 1203 </div> 1204 1205 <div class="fl w-third pv3 pr2"> 1206 <p class="f5 b pa0 ma0 fw"> 1207 1208 <a class="no-underline blue dim" href="http://manoj.ninja">Manoj Nathwani</a> 1209 1210 </p> 1211 <p class="pa0 ma0 f6">Hackathon enthusiast, Banter Ventures</p> 1212 </div> 1213 1214 <div class="fl w-third pv3 pr2"> 1215 <p class="f5 b pa0 ma0 fw"> 1216 1217 <a class="no-underline blue dim" href="http://ezefranca.com">Ezequiel França</a> 1218 1219 </p> 1220 <p class="pa0 ma0 f6">Brazilian Hackathon enthusiast, iOS Developer.</p> 1221 </div> 1222 1223 <div class="fl w-third pv3 pr2"> 1224 <p class="f5 b pa0 ma0 fw"> 1225 1226 <a class="no-underline blue dim" href="https://hackinout.co">Shakti Goap</a> 1227 1228 </p> 1229 <p class="pa0 ma0 f6">InOut Founder & Lead Organizer</p> 1230 </div> 1231 1232 <div class="fl w-third pv3 pr2"> 1233 <p class="f5 b pa0 ma0 fw"> 1234 1235 <a class="no-underline blue dim" href="https://www.facebook.com/gunasekaran.sengodan">Gunasekaran Sengodan</a> 1236 1237 </p> 1238 <p class="pa0 ma0 f6">Sitecore & Insite eCommerce Developer, Bangalore, India</p> 1239 </div> 1240 1241 <div class="fl w-third pv3 pr2"> 1242 <p class="f5 b pa0 ma0 fw"> 1243 1244 <a class="no-underline blue dim" href="http://jr0cket.co.uk">
1244John Stevenson</a> 1245 1246 </p> 1247 <p class="pa0 ma0 f6">Community Developer</p> 1248 </div> 1249 1250 <div class="fl w-third pv3 pr2"> 1251 <p class="f5 b pa0 ma0 fw"> 1252 1253 <a class="no-underline blue dim" href="http://otaciliomaia.com">Otacilio Maia</a> 1254 1255 </p> 1256 <p class="pa0 ma0 f6">Co-Founder @ReciHub; LocalHackDay organizer</p> 1257 </div> 1258 1259 </div> 1260 1261 <p class="tc"> 1262 <a class="no-underline blue dim" href="https://github.com/hackdaymanifesto/hackdaymanifesto.github.com/" title="Fork on GitHub">Fork this project on GitHub</a>, add yourself, and send us a pull request. 1263 </p> 1264 </div> 1265 </article> 1266 1267 1268 </main> 1269 1270 <footer class="bg-near-black white-80 pv1 ph4 roboto-condensed"> 1271 <div class="center measure-wide"> 1272 <p class="f6 tc">© Copyright 2015–2017, <a class="no-underline white dim" href="https://creativecommons.org/licenses/by/3.0/">Some Rights Reserved</a></p> 1273 </div> 1274 </footer> 1275 </body> 1276</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.