Skip to content

Instantly share code, notes, and snippets.

@lilliealbert
Last active November 30, 2015 15:10
Show Gist options
  • Save lilliealbert/18d91e9c1ad7defbbb50 to your computer and use it in GitHub Desktop.
Save lilliealbert/18d91e9c1ad7defbbb50 to your computer and use it in GitHub Desktop.

RailsBridge needs your help!

We’re searching for volunteers who can make RailsBridge more awesome by improving our communications, chapter outreach, and organization-wide fundraising. If you're interested in one of the positions described below, please apply here: http://bit.ly/volunteer-railsbridge-2015 by Sunday, November 15, 2015.

If you have any questions about the roles, email us at [email protected].

You don’t need to have professional experience in order to join a team — we're especially interested in volunteers who can manage projects independently and like to stay on top of their email (or Slack, or GitHub issues, depending on how the team communicates). 👯

These roles are ongoing; we are looking for you to make a 6-month commitment with the opportunity to continue if it’s still a good fit for you and RailsBridge. They are also all meant to be done as a member of a team. (No one person could be expected to do all of the things listed!)


Volunteer Positions on the Fundraising Team

Fundraising Lead

The fundraising lead will be the primary point of contact between the fundraising team and the RailsBridge board, and will work closely with the chair of the board to create a fundraising strategy. They will work with the rest of the fundraising team to make sure everyone is engaged and productive.

Crowdfunding Lead

We’re considering a crowdfunding campaign as a major portion of our fundraising. If you are excited about and/or have experience with running a crowdfunding campaign, we would love your help!

Fundraising Team Member

Members of the fundraising team will help plan and execute the fundraising campaign!

Depending on the type of campaign the fundraising team decides to run, this role could include:

  • Refine the sponsorship prospectus
  • Communicate with prospective donors (but no cold calling! ⚡)
  • Work with the Communications team to produce RailsBridge swag for donors
  • Work with the Finance team as needed

Volunteer Positions on the Communications Team

Communications Lead

The communications lead will have the opportunity to own or delegate the following responsibilities, depending on their interest:

  • Take a critical look at railsbridge.org and lead a refresh of the site’s content and design
  • Make RailsBridge swag happen — how about some stickers and tote bags?!
  • Manage a library of photos and videos compiled from RailsBridge events and work with chapters to include their media in the library
  • Create and implement a social media plan

Communications Team Member

Each member of the communications team will have a chance to help spread the word about RailsBridge, and there are so many ways to do so!

We’re particularly excited about having people do these things:

  • Manage the RailsBridge Twitter and Facebook accounts
  • Start an email newsletter & encourage people to sign up for it
  • Write or recruit writers for the RailsBridge blog
  • Write and submit press releases about RailsBridge initiatives, chapters, and milestones

Volunteer Positions on the Chapter Outreach Team

Chapter Outreach Support Lead

  • The Seed Chapter Support Lead will answer questions and help first-time organizers navigate the workshop cookbook, typically via GitHub issues and by writing into [email protected].
  • This person will also help coordinate mentors for new organizers.

Chapter Support Lead

  • Work closely with the board on establishing communication channels between chapters
  • Work with current organizers on improving documentation
  • Determine other ways that RailsBridge can help existing chapters have a better experience, whether that is more workshops, better chapter-wide organization, or something else entirely.

Apply now! http://bit.ly/volunteer-railsbridge-2015

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