Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Updated sections about conflicts and hack submissions. #65

Merged
merged 3 commits into from

5 participants

@theycallmeswift

Updated the sections about finding conflicting events and how to handle hack submissions. Most controversial part would be the "everybody demos" bit.

@danielknell
Owner

this feels like too much of a product advertisement.

@cbetta
Owner

I like the idea of what hacker league offers but I'd like to stay away from picking a site to recommend for use. I'd rather the changes focus on what the organisers should be offering that hacker league offers.

@cbetta
Owner

aka: :-1: for current revision

index.markdown
@@ -357,10 +358,14 @@ isolates the live API's from the increased usage the hack day will cause.
If possible, have a shared, public listing of the hacks that have been
submitted. This helps the judges, the attendees and bloggers/journalists who are
-covering the event. You can use Google Docs, Etherpad or a wiki. Several Hackday
-bespoke applications exist, too. Make sure that all attendees have write access
-and can concurrently edit. Plan for the hack listing to stay around as a
-historical record.
+covering the event. Hack submissions should be as straight forward as possible.
+There are services like [Hacker League](http://hackerleague.org) that will handle
+submissions for you or you can use Google Docs, Etherpad or a wiki. Make sure
+that all attendees have write access and can concurrently edit. Plan for the hack
+listing to stay around as a historical record.
+
+Anyone who hacks should be a allowed to demo at the end of the event, regardless
@cbetta Owner
cbetta added a note

:+1:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
index.markdown
@@ -357,10 +358,14 @@ isolates the live API's from the increased usage the hack day will cause.
If possible, have a shared, public listing of the hacks that have been
submitted. This helps the judges, the attendees and bloggers/journalists who are
-covering the event. You can use Google Docs, Etherpad or a wiki. Several Hackday
-bespoke applications exist, too. Make sure that all attendees have write access
-and can concurrently edit. Plan for the hack listing to stay around as a
-historical record.
+covering the event. Hack submissions should be as straight forward as possible.
+There are services like [Hacker League](http://hackerleague.org) that will handle
@cbetta Owner
cbetta added a note

I rather this doesn't mention hackerleague but rather focusses on what an organiser should look for in a tool for submitting hacks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
@cbetta cbetta commented on the diff
index.markdown
@@ -138,7 +139,7 @@ attendee.
As a minimum: ports used for SSH (22), DNS (53 — TCP & UDP),
VPN (47, 500, 1701, 1723, 5500), HTTP (80), NTP (123 — UDP),
-HTTPS (443), Submission (587), IMAPS (993), MSN Messenger (1863),
+HTTPS (443), Submissions (587), IMAPS (993), MSN Messenger (1863),
@cbetta Owner
cbetta added a note

:+1:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
index.markdown
@@ -95,10 +95,11 @@ remember that this may limit the number of people willing to travel after work.
One of the most frustrating things for attendees to see is two similar events
on the same day in the same area. To avoid this, check places like
-[Lanyrd](http://www.lanyrd.com) and [Eventbrite](http://eventbrite.com), and ask on
-twitter "anything going on in X on X". Remember that people may be travelling
-long distances for hack days, so even if an event is a few hundred miles away,
-you are still diluting your potental audience.
+[Lanyrd](http://www.lanyrd.com), [Eventbrite](http://eventbrite.com), or
+[Hacker League](http://hackerleague.org), and ask on twitter "anything going
@cbetta Owner
cbetta added a note

:-1: relatively new product, not well established, doubtful if it will stand the test of time.

@cbetta Owner
cbetta added a note

I'd still revert this.

I think this is the only withstanding issue. How about just "the hackathon platforms listed in the submissions section" and linking to the relevant section.

@cbetta Owner
cbetta added a note

Those tools are listed as hack submission tools, not event listing tools. Not sure I want to be rude but I simply just never heard of any of them and simply don't want to send people to sites that don't get many useful entries for hackdays anyway...

@cbetta Owner
cbetta added a note

Also: non of these sites have > 10 events listed. That's not very useful to most people.

I rather send people to generic event listing sites where they can make sure they don't clash with any kind of event that might steal away participants. These are often not just hackdays, but also barcamps and other events.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
@cbetta cbetta commented on the diff
index.markdown
@@ -357,10 +358,15 @@ isolates the live API's from the increased usage the hack day will cause.
If possible, have a shared, public listing of the hacks that have been
submitted. This helps the judges, the attendees and bloggers/journalists who are
-covering the event. You can use Google Docs, Etherpad or a wiki. Several Hackday
-bespoke applications exist, too. Make sure that all attendees have write access
-and can concurrently edit. Plan for the hack listing to stay around as a
-historical record.
+covering the event. Hack submissions should be as straight forward as possible.
+You can use Google Docs, Etherpad or a wiki. Make sure that all attendees have
+write access and can concurrently edit. Plan for the hack listing to stay around
+as a historical record. Alternatively, there are hack submission services that
+will handle the logistics for you like [Hacker League](http://hackerleague.org/),
+[Hackathon.io](http://hackathon.io), or [WeHack.it](http://wehack.it/).
@cbetta Owner
cbetta added a note

:+1:

@cbetta Owner
cbetta added a note

note: we should review these for dead links every year or so. Many of these feel like side projects.

Agreed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
@cbetta
Owner

:+1: Shipit! (will let @danielknell do that bit)

@theycallmeswift

Before you ship, I'd like to make one last stand for Hacker League being listed under the conflicts section. I can't speak for the other services, but I know for a fact that we keep all of our event listings completely public facing. These days there are somewhere is the neighborhood of 80 worldwide hackathons listed on our listing page.

Out of those 80, there are 8 listed for the upcoming September alone, including the two largest student hackathon in the US. If you do a quick search on lanyard for the word "hackathon" it yields 7 results for September and only 2 are cross posted on both. Comparitively if you do a search on eventbrite for the same query, you end up somewhere in the neighborhood of 60 results for September. That said, the Microsoft events are cross posted for every single city that they happen in which cuts them in nearly half. Additionally there is a strong scattering of reoccurring and mis-labeled events.

Even keeping Eventbrite at a conservative 30 events and giving the overlapping two to lanyard, that still leaves us with around a 20% market share of unique events on a month by month basis that are exclusively hackathons and hack days. I think maybe our biggest issue is that we aren't really represented in the UK and that's why you haven't heard of us. Thoughts?

@cbetta
Owner

I tend to stick to the word hack when I search because I still call them Hack Days, not Hackathons ;)

But pedantic aside, I agree with your logic. You seem to be listing a fair share of hack days. I think you're skewing the numbers slightly though because, like I said before, an organiser shouldn't just be interested in what other hack days are happening, but also what other BarCamps or other unconferences, conferences, workshops, etc are going on in the same weekend.

I'm a bit torn now between adding this or not. What do you think @danielknell?

@theycallmeswift

@danielknell any updates on this?

@danielknell
Owner

im not fond of where this path leads...

@cbetta
Owner

Nice and unconstructive @danielknell ;)

@kevinprince
Owner

:ok:

This is a good addition.

@danielknell
Owner

i would prefer to not mention specific tools as i fear the lists eventually growing unmanageable, but as there seems to be consensus for otherwise ill merge anyway.

@danielknell danielknell merged commit f8add7f into hackdaymanifesto:master
@theycallmeswift

Cool. Glad this finally went in. Thanks gents.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
This page is out of date. Refresh to see the latest.
Showing with 14 additions and 9 deletions.
  1. +14 −9 index.markdown
View
23 index.markdown
@@ -95,10 +95,10 @@ remember that this may limit the number of people willing to travel after work.
One of the most frustrating things for attendees to see is two similar events
on the same day in the same area. To avoid this, check places like
-[Lanyrd](http://www.lanyrd.com) and [Eventbrite](http://eventbrite.com), and ask on
-twitter "anything going on in X on X". Remember that people may be travelling
-long distances for hack days, so even if an event is a few hundred miles away,
-you are still diluting your potental audience.
+[Lanyrd](http://www.lanyrd.com) and [Eventbrite](http://eventbrite.com),
+and ask on twitter "anything going on in X on X". Remember that people may be
+travelling long distances for hack days, so even if an event is a few hundred
+miles away, you are still diluting your potental audience.
## Overnight Events
@@ -138,7 +138,7 @@ attendee.
As a minimum: ports used for SSH (22), DNS (53 — TCP & UDP),
VPN (47, 500, 1701, 1723, 5500), HTTP (80), NTP (123 — UDP),
-HTTPS (443), Submission (587), IMAPS (993), MSN Messenger (1863),
+HTTPS (443), Submissions (587), IMAPS (993), MSN Messenger (1863),
@cbetta Owner
cbetta added a note

:+1:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
CVS (2401), Subversion (3690), XMPP/Jabber (5222), IRC (6665-9),
and Git (9418), must be open and accessible, without the need of
proxy servers, and preferably without perimeter-level malware &c
@@ -357,10 +357,15 @@ isolates the live API's from the increased usage the hack day will cause.
If possible, have a shared, public listing of the hacks that have been
submitted. This helps the judges, the attendees and bloggers/journalists who are
-covering the event. You can use Google Docs, Etherpad or a wiki. Several Hackday
-bespoke applications exist, too. Make sure that all attendees have write access
-and can concurrently edit. Plan for the hack listing to stay around as a
-historical record.
+covering the event. Hack submissions should be as straight forward as possible.
+You can use Google Docs, Etherpad or a wiki. Make sure that all attendees have
+write access and can concurrently edit. Plan for the hack listing to stay around
+as a historical record. Alternatively, there are hack submission services that
+will handle the logistics for you like [Hacker League](http://hackerleague.org/),
+[Hackathon.io](http://hackathon.io), or [WeHack.it](http://wehack.it/).
@cbetta Owner
cbetta added a note

:+1:

@cbetta Owner
cbetta added a note

note: we should review these for dead links every year or so. Many of these feel like side projects.

Agreed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
+
+Anyone who hacks should be a allowed to demo at the end of the event, regardless
+of the quality or completeness.
### Time limit
Something went wrong with that request. Please try again.