Locked History Actions

Diff for "Events/GCC2014/Hackathon"

Differences between revisions 22 and 23
Revision 22 as of 2014-04-17 21:38:36
Size: 6487
Editor: DannonBaker
Revision 23 as of 2014-04-17 21:40:38
Size: 6509
Editor: DannonBaker
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:
 * write code,
 * know something about Galaxy internals,
 * are passionate about improving Galaxy, and
 * have 2 or 3 free days this June,
 * write code
 * know something about Galaxy and/or Cloudman internals
 * are passionate about improving Galaxy and/or Cloudman
 * have 2 or 3 free days this June

GCC2014 Hackathon


There will be a Galaxy Hackathon at Johns Hopkins immediately preceding - and in some part overlapping with - GCC2014.

What's a Hackathon?

A hackathon is an intense event at which a group of developers with different backgrounds and skills collaborate hands-on and face-to-face to develop working code that is useful to the community as a whole. Hackathons gather people in a room where than can focus on coding, free of distractions that are inevitable when you are in your office.

Hackathons are driven by participants. Participants propose and coalesce around a set of core goals early on the first day, and then spend the rest of their time working towards those goals.

Who Should Attend / Apply?

If you

  • write code
  • know something about Galaxy and/or Cloudman internals
  • are passionate about improving Galaxy and/or Cloudman
  • have 2 or 3 free days this June

then this event is for you.

There is limited space for this event and we don't yet have a very good feel for the level of interest there is in participating. Therefore to avoid 60 people showing up for an event that can accommodate 40 people at most, we will have a minimal application form. Once the 40 seats available have been claimed, they're gone. If you're interested in this, please register as soon as we make the form available.


Schedule? At a hackathon?

Hackathons are self-organizing events and attempts to impose anything as detailed as an agenda should be met with resistance and humor. With that in mind, this schedule tries to provide the absolute minimum amount of structure needed to ensure that something actually gets done.

Hacking at a NESCent/GMOD Hackathon

The hackathon is "officially" scheduled for three days, starting on Saturday, June 28. The first two days will happen in the Taylor Lab at Johns Hopkins. The last "official" day overlaps with the Training Day and we haven't yet decided if that will happen in the Taylor Lab or at the conference venue. Our hope is that hackathoners will be able to slip in out during this day.

We keep putting official in quotes because our hope is that activity will continue throughout the conference and afterward as well. If you have experience with hackathons you know that followup is often a challenge. The project will do all it can to support followup efforts. We very much want to make sure that the efforts from this hackathon make it into the code.

Minimum Amount of Structure

Here's a proposal for "the absolute minimum amount of structure needed to ensure that something actually gets done."


One challenge with hackathons is getting things done in the short amount of time the event itself is going on. To help this along we'll use a Trello board to help organize both ideas and people into concrete projects and teams. The hackathon organizers will be active contributors here both to seed ideas (though, add your own as well, please!) and offer commentary on proposed projects. We will also establish what participants should learn and do before the event.

Day 0: Saturday, June 28

We'll meet at the Taylor Lab.


Participant introductions: 1-3 minutes each, including 1-2 things you hope to achieve at this hackathon


Task proposals: 5 mins per proposal


Brownian motion, coalescence, and bonding around a subset of of task proposals/teams


Hacking, lunch, hacking, dinner, hacking

Day 1: Sunday, June 29

We'll meet at the Taylor Lab.


Team status reports


Hacking, lunch, hacking


Team status reports.
This will include each team's plans for meeting over the next three days, and how each team plans to followup after GCC2014 is done.


Hacking, dinner, hacking

Day 2: Monday, June 30

We will meet at the Taylor Lab or at the conference venue. The GCC2014 Training Day starts today, and so do conference meals. We aren't yet sure if there will be one place for participants to meet or if teams will be distributed around the venue.

There is probably no formal hackathon schedule for today other than a single evening meeting at which everyone presents their work so far. During the day, teams will meet according to their own agreements and continue work.

Lastly, each team will send out their final pre-conference team report for that day, via email, before midnight.

Post-Hackathon: GCC2014

Teams are encouraged to continue work and meet during breaks and other unscheduled time.


Join us in IRC (irc.freenode.net #galaxyproject) and keep on hacking!


There is no registration cost for the hackathon. Why? Please thank the sponsors. Repeatedly.

Participants will need to cover their own lodging costs, and (most) of their own meal costs. We will do our best to keep caffeine flowing throughout the event.


Curoverse: Open Source developers of Arvados    Arvados: a free and open source bioinformatics platform for genomic and biomedical data

Curoverse, makers of the Arvados open source bioinformatics platform,
is the exclusive Peta level Hackathon sponsor

Is this part of GCC2014?

Mostly yes, but, there is a separate registration/application process, and a separate organizing committee.

Questions? Contact the Organizers.