The Ruby for Good DC Conference is an annual event based out of the DC metro area where engineers, designers, product managers, and other gooders from all over the globe get together over a long weekend to collaboratively build projects in service of our communities. Gooders stay on-site, and hacking and socializing takes place in communal areas. Questions? Check out the FAQ or drop us a note on Slack or via email at firstname.lastname@example.org.
This year we are going to be holding the event at a gorgeous retreat space in the woods, just about an hour outside of DC. With the pandemic and the stress of the past year, we wanted to get away from the hustle and bustle of the cities where we could destress with our friends both new and old. Spending time in nature is good for you. Don't take it from us, that's just science! Plus, eating s'mores in front of a campfire after a day of civic hacking is pretty much the best thing ever.
We're very proud to once again be organizing the Ruby for Good DC conference. This conference, to our knowledge, is the first and currently the only one of its kind. We are bringing together technologists to learn, teach, and work on civic and open source projects.
We're very proud to once again be organizing the Ruby for Good DC conference. This conference, to our knowledge, is the first and currently only conference of this kind ever. We are bringing together technologists to learn, teach, and work on civic and open source projects.
By the very nature of our conference, our attendees are some of the most passionate, connected, and involved in the Ruby community. For companies looking to hire, this is an excellent opportunity to meet and interact professionally and socially with prospective candidates. By sponsoring, you are demonstrating your commitment to your community, open source, and the Ruby community.
For the safety of all, we are requiring that all attendees be fully vaccinated (meaning 2 weeks after the date of your last shot), in order to attend this event. Proof must be submitted 2 weeks prior to the event (at the latest) with non-compliance resulting in participants being unable to attend the event.