So you’re considering leading a team for Ruby for Good. You’re probably wondering what the heck that means. We’ve assembled some info on
We’ll start with the TL;DR – Being a Ruby for Good Team Lead means making a 8-week commitment to lead and deliver an open source project: 6 weeks prepping before the event and 2 weeks of follow-up after the event.
As a team lead you will be connecting with a partner organization that has a non-profit or civic mandate and work to deliver them software in support of their mission. This entails everything from meeting with the stakeholders, gathering requirements, translating those requirements, providing initial architecting, planning out project milestones, communicating with Ruby for Good organizers, pitching your project to Ruby for Good attendees, leading your team at the event Sept 23—Sept 26, and then seeing the project through to completion.
READMEin the Ruby for Good GitHub repo we have created for your project. This
READMEshould give information about the organization and what we will be building for them. See a past project we completed for Habitat for Humanity for a good example of a
You may have noticed that we didn't list technical skills. The truth is that generally if you've been doing development for a year, you likely have the ability needed to lead a team. We'd love for you to get in touch about a project. Don't worry if you think you're missing some of the required skills. We're about learning and are happy to help and work with you to figure out a way to make it happen. Maybe that means a co-lead or appointing a technical decision-maker on your team. If you want to lead a team, we're committed to figuring out a strategy to make it work!
We encourage you to reach out to past team leads and ask them about their experiences! It's a lot of fun, great for the resume, and extremely rewarding. Click here to read a blog post about a past team lead's experience with their first time leading a Ruby for Good project.