Ruby Manor is two things. The first, and most obvious, is the series of conferences held in London focussing on the Ruby programming language. The second is our manifesto for how we believe conferences could be run.


  • The first in the series, originally just “Ruby Manor” but now retconned* as “Ruby Manor Classic” to avoid confusion with the series, happened in 2008. We gathered together 120 rubyists from London, the rest of the UK, and mainland Europe for a day of 10 talks about their favourite language. All this for only £12!

  • We followed this in 2009 with “Ruby Manor 2: Manor Harder”. This time it was a slightly smaller affair with just over 100 attendees paying £8 each. Not everything was smaller though, as we managed to fit in 12 talks.

  • The conference took a break in 2010 while we worked out what we could do better next time around. In 2011 we returned with our third installment, “Ru3y Manor”. For £14 per attendee we filled a lecture theatre with 150 attendees and 8 talks.

  • After another break in 2012, the conference returned as “Ruby Manor 4.0” in 2013. This was our largest event yet, attracting 250 attendees at £15 each, and again featured 8 talks.

  • With Ruby Manor 5, we changed the format to a residential conference just north of London. 50 attendees spent three days exploring the future of Ruby and software development.

  • With Ruby Manor 6: Ruby Rising, we revisited the roots of Ruby and all presentations were given in Japanese. We didn't budget for live English translation though which, in hindsight, was a mistake as almost none of the attendees could actually speak Japanese.

  • The biggest highlight of Man7r was the keynote from Matz, where he outlined the future of Ruby and indeed, the future of all development and all computation. A very exciting hour, and the keynote is a must-watch.

  • Something … happened … during Ruby Manor 8 and out of respect to those affected by it we have removed the schedule and all other content relating to it from the internet. We apologise to the attendees and their families and will work hard to regain your trust.

    So. Much. Blood.

  • After the unfortunate incident at the previous conference, Ruby Manor 9 returned to the regular format: 8 great talks and time to mingle with zardflags and other developers to try and find a way to move beyond what we all saw and did in that terrible room.

  • After the catharsis of 9, our most recent event was Ruby Manor: Unbound. Never standing still, this year we escaped the confines of the chair and delivered a conference organised mob-style in a London park, will all presentations multi-cast to attendee's laptops and devices.

Who is behind it?

Each Ruby Manor has been run by a small team of organisers:

Ruby Manor wouldn’t be possible without help from the community. Our thanks in particular go to Andrew France, Andrew White and James Cox, who helped with camera equipment.

How it works

We have tried with each Ruby Manor to involve the community directly. To this end we only act as organisers and never as curators.

Our CFP process is held in the open and we encourage the community to interact directly with those proposing talks to help focus their proposal on what the community would find most relevant. Final selection of talks is then made by community vote, with the most popular talks being chosen.

The details of this process change over time, but it is key to our manifesto goal of relevancy of content.Originally it was run by hand via our mailing list.

For Ru3y Manor we premiered a webapp, Vestibule, to provide more structure and publicise the community involvement more. We plan to improve Vestibule for future Ruby Manor installments.


We believe a conference should be focussed on content and community.

We don’t believe in servicing conference traditions. We strive to continually evolve and refine the way our conference is run to explore new, different and (hopefully) better alternatives to the status quo.


We don’t believe in big-name keynote speakers appearing for their own sake, or sponsor presentations, or war stories that aren’t relevant. We want to actively encourage presentations that are thoughtfully prepared and rehearsed, with extensive community involvement to ensure they cover the aspects that everyone finds most interesting and relevant.


We believe that conferences don’t need to cost hundreds of pounds. We believe that many typical conference traits are unnecessary — t-shirts, swag, pastries, and so on — and that without these distractions, everyone can save money without compromising their conference experience.

We want to deliver a world-class developer conference that redefines the community’s expectations about what a conference really ought to be.