├── .gitignore
├── .ruby-version
├── 2016.md
├── 2017.md
├── 2018.md
├── 2019.md
├── 2020.md
├── Gemfile
├── README.md
├── _config.yml
├── _data
├── constants.yml
└── organizers.yml
├── _includes
├── _global_js.html
├── github-avatar.html
├── github-block.html
├── header.html
└── projects-yearbook.html
├── _layouts
├── base.html
└── page.html
├── assets
├── css
│ ├── animate.css
│ ├── bootstrap-combined.min.css
│ ├── bootstrap.min.css
│ ├── color-chooser.css
│ ├── custom.css
│ ├── font-awesome.min.css
│ ├── font-lineicons.css
│ ├── index.html
│ ├── jquery.fancybox.css
│ ├── style-2018.css
│ ├── style-berry.css
│ ├── style-blue.css
│ ├── style-green.css
│ ├── style-orange.css
│ ├── style-pink.css
│ ├── style.css
│ ├── syntax.css
│ └── toastr.min.css
├── fonts
│ ├── FontAwesome.otf
│ ├── fontawesome-webfont.eot
│ ├── fontawesome-webfont.svg
│ ├── fontawesome-webfont.ttf
│ ├── fontawesome-webfont.woff
│ ├── fontawesome-webfont.woff2
│ ├── index.html
│ ├── line-icons.eot
│ ├── line-icons.svg
│ ├── line-icons.ttf
│ ├── line-icons.woff
│ └── styles.css
├── ico
│ ├── apple-touch-icon-114-precomposed.png
│ ├── apple-touch-icon-144-precomposed.png
│ ├── apple-touch-icon-57-precomposed.png
│ ├── apple-touch-icon-72-precomposed.png
│ ├── favicon.ico
│ └── web-slack-icon.png
├── img
│ ├── 2016photo.jpg
│ ├── about-placeholder-iphone.jpg
│ ├── about-placeholder-mbp.jpg
│ ├── about-placeholder-starbucks.jpg
│ ├── apple-touch-icon-114x114.jpg
│ ├── apple-touch-icon-72x72.jpg
│ ├── apple-touch-icon.jpg
│ ├── fancybox
│ │ ├── blank.gif
│ │ ├── fancybox_loading.gif
│ │ ├── fancybox_loading@2x.gif
│ │ ├── fancybox_overlay.png
│ │ ├── fancybox_sprite.png
│ │ ├── fancybox_sprite@2x.png
│ │ └── index.html
│ ├── favicon.ico
│ ├── favicon.png
│ ├── gallery
│ │ ├── chris_thumbnail.jpg
│ │ ├── craig_thumbnail.jpg
│ │ ├── index.html
│ │ ├── jen_thumbnail.jpg
│ │ ├── kalimar_thumbnail.jpg
│ │ ├── polly_thumbnail.jpg
│ │ ├── sean_thumbnail.jpg
│ │ ├── teresa_thumbnail.jpg
│ │ ├── thumb-1.jpg
│ │ ├── thumb-2.jpg
│ │ ├── thumb-3.jpg
│ │ └── thumb-4.jpg
│ ├── header-bg-1.jpg
│ ├── header-bg.jpg
│ ├── image.png
│ ├── index.html
│ ├── magnify-cur.cur
│ ├── magnify-cur.png
│ ├── pmarker.png
│ ├── preloader.gif
│ ├── r4g-map-pin.png
│ ├── r4g.png
│ ├── red-panda.png
│ ├── register-bg.jpg
│ ├── renee.png
│ ├── sound-wave-trans.png
│ ├── sound-wave.jpg
│ ├── speaker
│ │ ├── index.html
│ │ ├── speaker-1.jpg
│ │ ├── speaker-2.jpg
│ │ ├── speaker-3.jpg
│ │ └── speaker-4.jpg
│ ├── sponsor
│ │ ├── 1password.png
│ │ ├── booster.png
│ │ ├── claritylogoretina.png
│ │ ├── customi.jpg
│ │ ├── customink.png
│ │ ├── digitalocean.png
│ │ ├── distil.svg
│ │ ├── excella.png
│ │ ├── excella.svg
│ │ ├── flatiron.png
│ │ ├── framebridge.png
│ │ ├── georgetown.png
│ │ ├── github.png
│ │ ├── godaddy.png
│ │ ├── heroku.png
│ │ ├── heroku2.png
│ │ ├── honeybadger.svg
│ │ ├── index.html
│ │ ├── jibe.png
│ │ ├── knightpoint.png
│ │ ├── kps.png
│ │ ├── linode.png
│ │ ├── mapbox-logo-color.svg
│ │ ├── mapbox.svg
│ │ ├── mason.png
│ │ ├── newrelic.png
│ │ ├── optoro-logo.png
│ │ ├── optoro-logo.svg
│ │ ├── ordway.png
│ │ ├── pardot.png
│ │ ├── sevatec.png
│ │ ├── sponsor-logo-0.jpg
│ │ ├── sponsor-logo-1.jpg
│ │ ├── sponsor-logo-10.jpg
│ │ ├── sponsor-logo-2.jpg
│ │ ├── sponsor-logo-3.jpg
│ │ ├── sponsor-logo-4.jpg
│ │ ├── sponsor-logo-5.jpg
│ │ ├── sponsor-logo-6.jpg
│ │ ├── sponsor-logo-7.jpg
│ │ ├── sponsor-logo-8.jpg
│ │ ├── sponsor-logo-9.jpg
│ │ ├── stickermule.svg
│ │ ├── stsi.png
│ │ ├── taphere.png
│ │ ├── vibes-single.png
│ │ ├── vibes.svg
│ │ ├── vibes_blue_rgb.svg
│ │ ├── xogroup.jpeg
│ │ ├── xogroup.png
│ │ └── xogroupold.png
│ └── stat-bg.jpg
├── index.html
├── js
│ ├── bootstrap.min.js
│ ├── color-chooser.js
│ ├── form-validation.js
│ ├── html5.js
│ ├── index.html
│ ├── jquery-1.11.0.min.js
│ ├── jquery-2.1.0.min.js
│ ├── jquery-2.1.0.min.map
│ ├── jquery.appear.js
│ ├── jquery.countTo.js
│ ├── jquery.countdown.js
│ ├── jquery.fancybox.js
│ ├── jquery.js
│ ├── jquery.mixitup.min.js
│ ├── jquery.plugin.js
│ ├── jquery.validate.js
│ ├── moment.min.js
│ ├── respond.min.js
│ ├── scripts.js
│ ├── spin.min.js
│ ├── toastr.min.js
│ ├── waypoints-sticky.min.js
│ └── waypoints.min.js
└── mailchimp
│ ├── css
│ ├── default.css
│ └── error.gif
│ ├── inc
│ ├── MCAPI.class.php
│ ├── error_log
│ └── store-address.php
│ └── js
│ └── mailing-list.js
├── attend.md
├── coc.md
├── faq.md
├── help.md
├── helpwanted.html
├── icons-reference.html
├── images
├── captain.png
├── cfa_brigade_logo.png
├── cfa_logo_greyscale.png
├── code_across_banner.png
├── community.png
├── google_groups.png
├── image.png
├── meetup.jpg
├── noun_project_756_citizen.png
├── original
│ ├── captain.png
│ ├── cfa_brigade_logo.png
│ ├── cfa_logo_greyscale.png
│ ├── code_across_banner.png
│ ├── community.png
│ ├── google_groups.png
│ ├── meetup.jpg
│ ├── noun_project_756_citizen.png
│ └── sunrise-top.jpg
├── smithsonian_parking.jpg
├── sunrise-top.jpg
└── tidalbasin.jpg
├── index.html
├── partner.md
├── projects.html
├── sponsors.md
├── submit-project.md
├── team-leads.md
└── yearbook.md
/.gitignore:
--------------------------------------------------------------------------------
1 | .DS_Store
2 | _site
3 | Gemfile.lock
4 |
--------------------------------------------------------------------------------
/.ruby-version:
--------------------------------------------------------------------------------
1 | 2.4.2
2 |
--------------------------------------------------------------------------------
/2016.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: page
3 | ---
4 |
5 | ### Ruby for Good 2016
6 |
7 | [Join us on Slack](https://rubyforgood.herokuapp.com/) before, during, and after the event for announcements and making friends.
8 |
9 | ###### Thursday June 16th
10 |
11 | * Arrive before 5:00 pm — most of the organizing team is planning on arriving at 10:00 am but feel free to beat us there!
12 | * 1:00 pm - 26 people on [FONZ](https://nationalzoo.si.edu/JoinFonz/join.cfm) tour of Smithsonian-Mason Institute (see below) — [reserve your spot](https://docs.google.com/spreadsheets/d/1gTi3wUj8MJLG637wdYBsasBrca53P7X-FFjXWw-SF2k/edit?usp=sharing).
13 | * 5:00 pm - Event kickoff and announcements
14 | * 5:30 pm - Team pitches, team assignments
15 | * 6:30 pm - Dinner, initial team discussion, setting up environments, cloning down repos, etc.
16 | * 8:30 pm? - Board games, computer games, socializing, and other random fun.
17 |
18 | ###### Friday June 17th
19 |
20 | * 8:00 am - Breakfast
21 | * 9:00 am - Work on projects
22 | * 10:00 am - 26 people on [FONZ](https://nationalzoo.si.edu/JoinFonz/join.cfm) tour of Smithsonian-Mason Institute (see below) — [reserve your spot](https://docs.google.com/spreadsheets/d/1gTi3wUj8MJLG637wdYBsasBrca53P7X-FFjXWw-SF2k/edit?usp=sharing).
23 | * 12:00 pm - Lunch
24 | * 1:00 pm - 26 people on [FONZ](https://nationalzoo.si.edu/JoinFonz/join.cfm) tour of Smithsonian-Mason Institute (see below) — [reserve your spot](https://docs.google.com/spreadsheets/d/1gTi3wUj8MJLG637wdYBsasBrca53P7X-FFjXWw-SF2k/edit?usp=sharing).
25 | * 1:00 pm - Work on projects
26 | * 5:00 pm - Dinner
27 | * 6:30pm - Werewolf, board games, socializing, fun!
28 |
29 | ###### Saturday June 18th
30 |
31 | * 8:00 am - Breakfast
32 | * 9:00 am - Work on projects
33 | * 12:00 pm - Lunch
34 | * 1:00 pm - Work on projects
35 | * 5:00 pm - Dinner
36 | * 6:30pm - Outdoorsy fun (bring a sweater, lawn chairs, and a sweet tooth).
37 |
38 | ###### Sunday June 19th
39 |
40 | * 8:00 am - Breakfast
41 | * 9:00 am - Work on projects
42 | * 12:00 pm - Lunch
43 | * 1:00 pm - Demos (if your project isn't finished, demo what you can!)
44 |
45 | ### Location
46 |
47 | George Mason University’s Smithsonian-Mason School of Conservation
48 | 1500 Remount Rd
49 | Front Royal, VA 22630
50 |
51 | The location is only accessible by car — we are helping to [coordinate carpooling](https://docs.google.com/forms/d/1aA0fJbbmxYW3lTqP6A7zLOnZbECzCd5d9f7L9ok_jLI/viewform?c=0&w=1). Please fill out the form if you need a ride or can offer a ride and Kalimar will do his best to match people up! Contact Kalimar at [kalimar@rubyforgood.org](mailto:kalimar@rubyforgood.org).
52 |
53 | If you arrive and the gate is locked, dial #90 at the phone at gate #2 for access.
54 |
55 | Once you enter through the gates, drive to the top of the hill (the Smithsonian Tower with yellow and blue sun will be on your right). Make a right after the Smithsonian tower, and parking is on the right.
56 |
57 | After arriving, head to the “Residences” building to check in.
58 |
59 | ### FONZ Tours
60 |
61 | The [Friends of the National Zoo (FONZ)](https://nationalzoo.si.edu/JoinFonz/join.cfm) is giving us a personalized, not-open-to-the-public tour of the Smithsonian Conservation Biology Institute (SCBI) grounds and animal habitats so we can learn about red pandas, bison, and other friendly creatures, their homes, and the research being done on-site. We have three tours lined up as indicated above. Only 26 people are allowed for each tour and tours last between 1.5 and 2 hours. Be sure to [reserve your spot](https://docs.google.com/spreadsheets/d/1gTi3wUj8MJLG637wdYBsasBrca53P7X-FFjXWw-SF2k/edit?usp=sharing) on one of the tours.
62 |
63 | ### What to Bring
64 |
65 | Bring yourself, your laptop, a power source, some clothes and your favorite board games. Maybe some sunscreen if the weather’s nice. If you anticipate skipping group meals, bring some munchies. If you’re a light sleeper, bring earplugs. All the basics are provided (linens, pillows, beds, towels, etc.). We have a fun outdoor activity planned for one evening so camping chairs, a sweater and maybe some bug spray are highly recommended.
66 |
--------------------------------------------------------------------------------
/2017.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: page
3 | ---
4 |
5 | ### Ruby for Good 2017
6 |
7 | [Join us on Slack](https://rubyforgood.herokuapp.com/) before, during, and after the event for announcements and making friends.
8 |
9 | ###### Thursday May 18th
10 |
11 | * Arrive before 5:00 pm — most of the organizing team is planning on arriving early and be sure to come before 1:00pm if you intend to attend the [FONZ](https://nationalzoo.si.edu/JoinFonz/join.cfm) tour of Smithsonian-Mason Institute!
12 | * 5:00 pm - Event kickoff and announcements
13 | * 5:30 pm - Team pitches, team assignments, dinner with your team, initial team discussion
14 | * 6:30 pm - Finish setting up environments, cloning down repos, etc.
15 | * 8:30 pm or earlier if teams have everything ready to go for Friday - Board games, computer games, socializing, and other random fun.
16 |
17 | ###### Friday May 19th
18 |
19 | * 8:00 am - Breakfast
20 | * 9:00 am - Work on projects
21 | * 10:00 am - 26 people on [FONZ](https://nationalzoo.si.edu/JoinFonz/join.cfm) tour of Smithsonian-Mason Institute (see below)
22 | * 11:30 pm - Lunch
23 | * 1:00 pm - 26 people on [FONZ](https://nationalzoo.si.edu/JoinFonz/join.cfm) tour of Smithsonian-Mason Institute (see below)
24 | * 1:00 pm - Work on projects
25 | * 5:00 pm - Dinner
26 | * 6:30 pm - Werewolf, board games, socializing, fun!
27 |
28 | ###### Saturday May 20th
29 |
30 | * 8:00 am - Breakfast
31 | * 9:00 am - Work on projects
32 | * 12:00 pm - Lunch
33 | * 1:00 pm - Work on projects
34 | * 5:00 pm - Dinner
35 | * 6:30 - More games, socializing and fun!
36 |
37 | ###### Sunday May 21st
38 |
39 | * 8:00 am - Breakfast
40 | * 9:00 am - Work on projects
41 | * 12:00 pm - Lunch
42 | * 1:00 pm - Demos (if your project isn't finished, demo what you can!)
43 |
44 | ### Location
45 |
46 | George Mason University's Smithsonian-Mason School of Conservation
47 | 1500 Remount Rd
48 | Front Royal, VA 22630
49 |
50 | The location is only accessible by car — we are helping to [coordinate carpooling](https://docs.google.com/forms/d/1aA0fJbbmxYW3lTqP6A7zLOnZbECzCd5d9f7L9ok_jLI/viewform?c=0&w=1). Please fill out the form if you need a ride or can offer a ride and Kalimar will do his best to match people up! Contact Kalimar at [kalimar@rubyforgood.org](mailto:kalimar@rubyforgood.org).
51 |
52 | If you arrive and the gate is locked, dial #90 at the phone at gate #2 for access.
53 |
54 | Once you enter through the gates, drive to the top of the hill (the Smithsonian Tower with yellow and blue sun will be on your right). Make a right after the Smithsonian tower, and parking is on the right.
55 |
56 | After arriving, head to the "Residences" building to check in.
57 |
58 | See a helpful [annotated satellite photo](/images/images/smithsonian_parking.jpg) or a link on [Google Maps](https://goo.gl/maps/ei3HcuBW1ZT2).
59 |
60 | ### FONZ Tours
61 |
62 | The [Friends of the National Zoo (FONZ)](https://nationalzoo.si.edu/JoinFonz/join.cfm) is giving us a personalized, not-open-to-the-public tour of the Smithsonian Conservation Biology Institute (SCBI) grounds and animal habitats so we can learn about red pandas, bison, and other friendly creatures, their homes, and the research being done on-site.
63 |
64 | ### What to Bring
65 |
66 | Bring yourself, your laptop, a power source, some clothes and your favorite board games. Maybe some sunscreen if the weather's nice. If you anticipate skipping group meals, bring some munchies. If you're a light sleeper, bring earplugs. All the basics are provided (linens, pillows, beds, towels, etc.). We have a fun outdoor activity planned for one evening so camping chairs, a sweater and maybe some bug spray are highly recommended.
67 |
--------------------------------------------------------------------------------
/2018.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: page
3 | ---
4 |
5 | ### Ruby for Good 2018
6 |
7 | [Join us on Slack](https://rubyforgood.herokuapp.com/) before, during, and after the event for announcements and making friends.
8 |
9 | ##### Attendee Agenda
10 |
11 | ##### Thursday June 7th
12 |
13 | * 4:00 pm - Visit with team leads, familiarize yourself with each project’s nonprofit and their mission, ask about particular projects, get a sense of technical requirements. Consider this an opportunity to go into a little more depth with projects before you choose to commit to one in particular. This portion is optional, but you may find it helpful in making your decision!
14 | * 5:00 pm - Event kickoff and announcements
15 | * 5:30 pm - Team pitches, team selection, initial team discussion
16 | * 6:00 pm - Dinner with your team (and others!)
17 | * 6:30 pm – Teams set up environments, clone down repos, etc.
18 | * 8:30 pm or earlier if teams have everything ready to go for Friday - Board games, computer games, socializing, and other random fun.
19 |
20 | ##### Friday June 8th
21 |
22 | * 8:00 am - Breakfast
23 | * 9:00 am - Work on projects
24 | * 11:30 pm - Lunch
25 | * 1:00 pm - Work on projects
26 | * 5:00 pm – PHOTOS (entire group, individual teams, and fridayhug)
27 | * 5:30 pm - Dinner
28 | * 6:30 pm - Werewolf, board games, socializing, fun!
29 |
30 | ##### Saturday June 9th
31 |
32 | * 8:00 am - Breakfast
33 | * 9:00 am - Work on projects
34 | * 12:00 pm - Lunch
35 | * 1:00 pm - Work on projects
36 | * 5:00 pm - Dinner
37 | * 6:30 pm - Career fair -- talk to our sponsors about positions at the awesome companies!
38 | * 7:00 - More games, socializing and fun!
39 |
40 | ##### Sunday June 10th
41 |
42 | * 8:00 am - Breakfast
43 | * 9:00 am - Work on projects
44 | * 12:00 pm - Lunch
45 | * 1:00 pm - Demos (if your project isn’t finished, demo what you can!)
46 |
47 | ### Location
48 |
49 | Georgetown University
50 | 37th and O Streets, N.W.
51 | Washington D.C. 20057
52 |
53 | Take a look at [this map](http://pompeii.gmu.edu/lgP6v.png) as it annotates the various locations where we'll be.
54 |
55 | ### What to Bring
56 |
57 | Bring yourself, your laptop, a power source, some clothes and your favorite board games. Maybe some sunscreen if the weather's nice. If you anticipate skipping group meals, bring some munchies. If you're a light sleeper, bring earplugs. All the basics are provided (linens, pillows, beds, towels, etc.).
58 |
--------------------------------------------------------------------------------
/2019.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: page
3 | ---
4 |
5 | ### Ruby for Good 2019
6 |
7 | [Join us on Slack](https://rubyforgood.herokuapp.com/) before, during, and after the event for announcements and making friends.
8 |
9 | ##### Attendee Agenda
10 |
11 | ##### Thursday July 25th
12 |
13 | * 4:00 pm - Visit with team leads, familiarize yourself with each project’s nonprofit and their mission, ask about particular projects, get a sense of technical requirements. Consider this an opportunity to go into a little more depth with projects before you choose to commit to one in particular. This portion is optional, but you may find it helpful in making your decision!
14 | * 5:00 pm - Event kickoff and announcements
15 | * 5:30 pm - Team pitches, team selection, initial team discussion
16 | * 5:30 pm - Dinner with your team (and others!)
17 | * 6:30 pm – Teams set up environments, clone down repos, etc.
18 | * 8:30 pm or earlier if teams have everything ready to go for Friday - Board games, computer games, socializing, and other random fun.
19 |
20 | ##### Friday July 26th
21 |
22 | * 8:00 am - Breakfast
23 | * 9:00 am - Work on projects
24 | * 12:00 pm - Lunch
25 | * 1:00 pm - Work on projects
26 | * 5:00 pm - Dinner
27 | * 6:00 pm - Werewolf, board games, socializing, fun!
28 |
29 | ##### Saturday July 27th
30 |
31 | * 8:00 am - Breakfast
32 | * 9:00 am - Work on projects
33 | * 12:00 pm - Lunch
34 | * 1:00 pm - Work on projects
35 | * 4:30 pm – PHOTOS (entire group, individual teams, and fridayhug)
36 | * 5:00 pm - Dinner
37 | * 6:30 pm - Career fair -- talk to our sponsors about positions at the awesome companies!
38 | * 7:00 - More games, socializing and fun!
39 |
40 | ##### Sunday July 28th
41 |
42 | * 8:00 am - Breakfast
43 | * 9:00 am - Work on projects
44 | * 12:00 pm - Lunch
45 | * 1:00 pm - Demos (if your project isn’t finished, demo what you can!)
46 |
47 | ### Location
48 |
49 | George Mason University
50 | 4400 University Drive
51 | Fairfax, VA 22030
52 |
53 | ### What to Bring
54 |
55 | Bring yourself, your laptop, a power source, some clothes and your favorite board games. Maybe some sunscreen if the weather's nice. If you anticipate skipping group meals, bring some munchies. If you're a light sleeper, bring earplugs. All the basics are provided (linens, pillows, beds, towels, etc.).
56 |
--------------------------------------------------------------------------------
/2020.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: page
3 | ---
4 |
5 | ### Ruby for Good 2020
6 |
7 | [Join us on Slack](https://rubyforgood.herokuapp.com/) before, during, and after the event for announcements and making friends. The schedule below is in Eastern Daylight Time (EDT).
8 |
9 | ##### Attendee Agenda
10 |
11 | ##### Saturday, September 5th
12 |
13 | * 10:00am - 12:00pm: Project Coding
14 | * 12:00pm - 2:00pm: Facilitated Social Event
15 | * 2:00pm - 4:00pm: Project Coding
16 | * 4:00pm - 6:00pm: Facilitated Social Event
17 | * 6:00pm - onward: Games, Socializing
18 |
19 | ##### Sunday, September 6th
20 |
21 | * 10:00am - 12:00pm: Project Coding
22 | * 12:00pm - 2:00pm: Facilitated Social Event
23 | * 2:00pm - 4:00pm: Project Coding
24 | * 4:00pm - 6:00pm: Facilitated Social Event
25 | * 6:00pm - onward: Games, Socializing
26 |
27 | ##### Saturday, September 12th
28 |
29 | * 10:00am - 12:00pm: Project Coding
30 | * 12:00pm - 2:00pm: Facilitated Social Event
31 | * 2:00pm - 4:00pm: Project Coding
32 | * 4:00pm - 6:00pm: Facilitated Social Event
33 | * 6:00pm - onward: Games, Socializing
34 |
35 | ##### Sunday, September 13th
36 |
37 | * 10:00am - 1:00pm: Prepare for demos
38 | * 1:00pm - onward: Demos (if your project isn’t finished, demo what you can!)
39 |
--------------------------------------------------------------------------------
/Gemfile:
--------------------------------------------------------------------------------
1 | source 'https://rubygems.org'
2 |
3 | gem 'github-pages'
4 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # rubyforgood.org
2 |
3 | This repository holds [rubyforgood.org](http://rubyforgood.org), a site built on [GitHub Pages](https://pages.github.com/).
4 |
5 | ## Running Locally for Development
6 |
7 | First, install dependencies with bundler:
8 |
9 | ```
10 | bundle install
11 | ```
12 |
13 | Then, run the site with `jekyll`:
14 |
15 | ```
16 | jekyll serve
17 | ```
18 |
19 | The site will be available at [http://localhost:4000](http://localhost:4000).
20 |
21 | ## Project Information
22 |
23 | Project information for Yearbook, Projects and the Help Wanted board is kept in the repo
24 | [meta](https://github.com/rubyforgood/meta). Submit a pull request in that repo
25 | to change project listings.
26 |
--------------------------------------------------------------------------------
/_config.yml:
--------------------------------------------------------------------------------
1 | highlighter: rouge
2 | gems:
3 | - jekyll-redirect-from
4 |
--------------------------------------------------------------------------------
/_data/constants.yml:
--------------------------------------------------------------------------------
1 | ---
2 |
3 | dates:
4 | start: Sept. 5th
5 | end: Sept. 6th
6 | year: "2020"
7 | start2: Sept. 12th
8 | end2: Sept. 13th
9 | year2: "2020"
10 | address: "Online"
11 | suggest_project: 'https://airtable.com/shrC6VjWgka26a6eh'
12 | contact_email: "info@rubyforgood.org"
13 | cost: $60
14 | apply_scholarship: 'https://docs.google.com/forms/d/1M3PJepMOZcqUcIN81Ju7YEeXpQKhYWnSWnmgeZTX33w/viewform#start=openform'
--------------------------------------------------------------------------------
/_data/organizers.yml:
--------------------------------------------------------------------------------
1 | ---
2 |
3 | - name: Sean Marcia
4 | title: Founder
5 | about: Came up with Ruby for Good, and it would not be possible without his hard work.
6 | twitter: seanmarcia
7 | github: SeanMarcia
8 | img: assets/img/gallery/sean_thumbnail.jpg
9 | - name: Polly Schandorf
10 | title: Go-Getter
11 | img: assets/img/gallery/polly_thumbnail.jpg
12 | about: Loves building a great and supportive community, and playing games. Definitely not a villager.
13 | github: pollygee
14 | twitter: N3rdyTeacher
15 | # - name: Jen Pengelly
16 | # title: Empathizer
17 | # img: assets/img/gallery/jen_thumbnail.jpg
18 | # about: Loves organizing things and getting people together, solving cool problems, and making good food.
19 | # github: jenpen
20 | # twitter: jenpengelly
21 | - name: Craig Zaccaro
22 | title: Organizer
23 | img: assets/img/gallery/craig_thumbnail.jpg
24 | about: Loves building useful stuff and contributing to the community.
25 | github: CraigJZ
26 | twitter: craigzaccaro
27 |
--------------------------------------------------------------------------------
/_includes/_global_js.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 | {% for js_name in page.extra_js %}{% endfor %}
5 |
6 |
18 |
19 |
33 |
34 | {% if page.deeplink == true %}
35 |
55 | {% endif %}
56 |
--------------------------------------------------------------------------------
/_includes/github-avatar.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
--------------------------------------------------------------------------------
/_includes/github-block.html:
--------------------------------------------------------------------------------
1 |
2 | View Project on GitHub
3 |
4 | {% assign team = include.team | split:"|" %}
5 |
6 | {: .github-avatars .pull-left}
7 | {% for member in team %}
8 | - {% include github-avatar.html username=member %}
9 | {% endfor %}
10 |
11 |
8 | ### Partner With Us
9 | [Suggest a project we can build for your organization.](https://airtable.com/shrC6VjWgka26a6eh)
10 |
11 | We build software solutions to help your organization achieve its mission! We bring technologists together to build projects toward effecting large-scale social impact. Inefficient and expensive software solutions are an impediment to efficiency. We want to help develop software solutions, so you can focus on your mission.
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
Projects We Build
20 |
21 | We excel at figuring out what your biggest pain points are and what kind of tedious repetitive tasks you do. Then we set about automating those tasks so your time can better be spent elsewhere. Our expertise is primarily with building web applications. This means that the kind of projects that we excel at are those that require the recording and sharing of information, collaboration, web-based databases and coordination tools.
22 |
23 | These can seem a little vague, especially to non-technically oriented people, but if you are having difficulty sharing, storing or accessing data for your organization, we might be able to help.
24 | We can and have built other kinds of software and this is only to give you an idea. We'll definitely find a way to help!
25 |
26 |
27 |
28 |
29 |
30 |
Problems We Solve
31 |
32 | 1. Are you recording data with pen/paper and later transferring that data to a computer?
33 | 2. Do you pass word/excel/text files around with collaborators to share information?
34 | 3. Are you using software for a project now that wasn't built for the kind of work you are doing (“making it work” even though it’s super painful)?
35 | 4. Do you take data entered somewhere, manually manipulate it and send it on elsewhere?
36 | 5. Do you have databases that require different access levels? For example, a volunteer can record and enter data, a principal researcher can then lock it and prevent further volunteer edits and only allow researchers to edit to protect data integrity, reviewers can see but not edit data, and so on.
37 | 6. Do you use desktop programs to record information so you are locked into doing it from a certain location but it would be more convenient to have it web based so you can see/edit from anywhere?
38 |
39 |
40 |
41 |
42 |
43 |
44 |
Cost
45 |
46 | The project development is free! We do this to help the people who are making the world a better place. For the past three years we have also been very fortunate to have received sponsorships from hosting companies to host the projects.
47 |
48 | However, there is no guarantee these sponsorships will continue. You may need to find hosting for the project once it is built. We will work with you to find the most affordable solution for your project or to integrate it with your current hosting.
49 |
50 |
51 |
52 |
53 |
54 |
55 |
Your Involvement
56 |
57 | In order to build you the best software possible we need your participation so we can understand your needs. We require you to commit to at least two meetings with the person leading your team in the lead up to the event.
58 |
59 | You will also need to be available at least once during the event, ideally each day. Your team will coordinate the times. This is necessary because the team building your software will inevitably run into design decisions that will require your input in order to resolve and keep the project moving forward.
60 |
61 |
62 |
63 |
64 |
65 |
66 |
Testimonial
67 |
68 | Listen to what one of our amazing partner organizations from 2017 had to say:
69 |
70 |
71 | In addition to the PDX Diaper Bank, we have ongoing projects that we contribute to throughout the rest of the year.
72 |
73 | [View a list of other active, ongoing projects.](/projects.html)
74 |
75 |
76 |
77 |
78 |
79 |
80 |
Schedule
81 |
82 | About 5-6 weeks before the event we'll find someone suitable to lead a team to build your software and put them in touch with you.
83 |
84 | They will meet and drill down with you and what you really need. They will confirm requirements with you and then present them to the team that will be working on your software at our event.
85 |
86 | They will meet virtually (Skype, Google Hangouts, etc.) with you during the event to introduce the team and to clarify any questions.
87 | Within one month of the event's completion we will deliver the software to you.
88 |
96 | After you submit your project, we'll follow up with a conversation. We'll get in touch and determine how we can best help you. It may turn out that your best solution is to use something already out there and we'll help you with that.
97 |
98 |
104 |
105 |
314 |
--------------------------------------------------------------------------------
/sponsors.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: page
3 | ---
4 |
5 | ### Sponsors
6 |
7 | The Ruby for Good coding event is a one of a kind event for developers, designers, product managers, and people of diverse skill sets and levels. It is exclusively volunteer driven and your support would be incredibly meaningful, enabling us to continue providing technology solutions to nonprofit organizations in need, that are serving vital missions in their local communities.
8 |
9 | ###### Why Sponsor?
10 |
11 | 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 showing your commitment to your community, open source, and the Ruby community. Plus, we are a 501(c)3 non-profit!
12 |
13 |
14 |
23 |
24 | - Small logo on the conference homepage
25 | - Listed on the website
26 | - Mention on Twitter
27 | - One ticket to attend the conference
28 |
29 |
39 |
40 | - Large logo on the conference homepage
41 | - Listed on the website
42 | - Mention on Twitter
43 | - Two tickets to attend the conference
44 |
45 |
55 |
56 | - Name and URL included in email blasts to attendees
57 | - Recognition in the welcome announcements
58 | - At one mealtime (breakfasts, lunches or dinner) on each of the three days we will give a shout out to your company
59 | - Listed on the website
60 | - Mention on Twitter
61 | - Three tickets to attend the conference
62 |
63 |
73 |
74 | - We're excited to discuss partnership opporutnities, with a customized package
75 | - Name and URL included in email blasts to attendees
76 | - Recognition in the welcome announcements
77 | - All our partner non-profits will express their thanks for your company on social media
78 | - Hugs and goodwill from the conference organizers for life
79 | - The opportunity to address the attendees on day two
80 | - Four included tickets for the event
81 |
82 |
96 |
97 | - Name and URL included in email blasts to attendees
98 | - Recognition in the welcome announcements
99 | - Hugs on demand for life from the conference organizers
100 | - Two tickets to attend the conference
101 |
102 |
114 |
115 | - Contribute towards the Ruby for Good Scholarship fund, used to allow more people the opportunity to participate
116 | - Feel great about making Ruby for Good gooder
117 |
118 |
119 |
120 |
121 |
--------------------------------------------------------------------------------
/submit-project.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: page
3 | ---
4 |
5 |
6 |
--------------------------------------------------------------------------------
/team-leads.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: page
3 | ---
4 |
5 | ### Team Lead Guide
6 | So, you’re considering leading a team for Ruby for Good 2020. You’re probably wondering what that entails! We’ve assembled some info on 1) what you can expect, 2) what we’ll expect from you, and 3) how to actually go about signing up.
7 |
8 | Summary: Being a Ruby for Good Team Lead means making a 10-week commitment to lead and deliver an open source project: 6 weeks prepping before the event, and 4 weeks of follow up after the event.
9 |
10 | #### What Does It Mean To Lead A Team?
11 |
12 | As a team lead you will be connecting with a nonprofit partner organization doing critical work in the community, to deliver a software solution 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 and then seeing the project through to completion.
13 |
14 | We will be updating this page soon for 2020's online Ruby for Good event. In the meantime, here is the team lead schedule from last year.
15 |
16 | #### What we expect from team leads:
17 |
18 | ###### 2019
19 |
20 | ###### Week 1 (June 17-23)
21 | * Attend an all-hands google hangout for 2019 team leads
22 | * After your organizer writes an introduction email, reach out to stakeholder via email to introduce yourself
23 | * Research your organization and familiarize yourself with their business problems. Begin to understand the organization and their needs.
24 |
25 | ###### Week 2 (June 24-30)
26 | * Connect face-to-face with stakeholder—skype or google hangout is okay; meeting in person when possible is even better! Meet ‘n greet, have a conversation about the technical capability of the organization, the project they had in mind, specific project requirements, nice-to-haves, both yours and the organization’s expectations, etc.
27 | * Connect with your organizer to provide update on project status
28 |
29 | ###### Week 3 (July 1-7)
30 | * Communicate with your stakeholder to drill down on project requirements, as necessary. If not needed, reach out to them anyway and let them know you’re continuing to think about their project.
31 | * Connect with your organizer to provide update on project status
32 |
33 | ###### Week 4 (July 8-14)
34 | * Connect face-to-face with stakeholder for SECOND time, tell them where you are in solving their business problem.
35 | * Brainstorm newbie tasks for your project.
36 | * Connect with your organizer to provide update on project status.
37 |
38 | ###### Week 5 (July 15-21)
39 | * Create a readme in the rubyforgood github repo we have created for your project. This readme should give information about the organization and what we will be building for them. A good example readme can be seen [here](https://github.com/rubyforgood/habitat_humanity/).
40 | * Attend all-hands google hangout for 2019 team leads – a final check in to get your questions answered before the official event happens in one week.
41 | * Connect with your organizer to provide update on project status, as necessary.
42 |
43 | ###### Week 6 (July 22-28)
44 | * Attend a team lead and stakeholder bbq on July 24th.
45 | * Ruby for Good 2019 – July 25-28
46 | * Pitch your project to Ruby for Good attendees on opening night (5pm sharp): provide a brief intro to the organization, to the project, ask for specific technical skills if needed, communicate your team’s goals if you feel strongly about it (examples: deploy by end of event, emphasize team learning, master new gems, mandate pairing for all coding, explore new front end technologies, etc.)
47 | * Set team goals with your team. See above for inspiration.
48 | * Lead the team during the event.
49 |
50 | ###### Week 7 (July 29-Aug 4)
51 | * Make plan to deploy with organizer.
52 | * Note that about 20% of our projects finish during the event—and we’re happy about that. We don’t want you or your team burning yourselves out. Ruby for Good is as much about building community as it is about doing good. If you work late into the evenings, you miss out on playing board games and werewolf and we want to see your face during these social times!
53 |
54 | ###### Week 8-10 (Aug 5-25)
55 | * Connect with your organizer to update them on status.
56 | * Deploy; project will be finished and delivered.
57 | * Receive feedback on your mad team leading skillz.
58 |
59 | ##### What team leads can expect from us?
60 | * We will ensure that the partner organization will work with you and be available for questions at the event.
61 | * We will make introductions between you and the partner organization.
62 | * It sucks to be at a roadblock so the organizer overseeing your project will provide multiple methods of contact and will commit to responding to any request within a day.
63 | * During the event we will be available to help in any way you many need it.
64 | * After your project is delivered we will collect and give you meaningful feedback from the organization, your team and the organizers. We all want to grow and improve and we’ll provide actionable feedback to help you.
65 | * We will take over maintenance of the application after it has been delivered. You are completely welcome to stick with it and continue managing the project if you'd like.
66 |
67 | ##### What skills do you need to lead a team?
68 | * Organization. Do you like making to-do lists and keeping track of what has been finished? Perfect! There are a lot of details and moving parts and it pays to be organized.
69 | * Decision making. Developers have lots and lots of opinions and we love to debate. I think we’ve all seen the rabbit hole we can fall down when people start discussing things like vim vs emacs, angular v react and so on. The team lead needs to be able to make decisions and keep the project moving forward.
70 | * Communication. You will need to translate what the org needs to your team. This also means that when your team is deciding how to build the app you can effectively communicate the stakeholders needs if you need to reign in your team and prevent over-engineering what otherwise would be a simple solution.
71 | * Empathy. We all participate because we are interested in making the world a better place. If we start with that belief we realize that some problems come because people care too much.
72 |
73 | **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!**
74 |
75 | **You should definitely reach out to past team leads and ask their experience. It is a lot of fun, great for the resume and extremely rewarding. [A past team lead wrote this excellent write-up of the experience.](http://www.blrice.net/blog/2015/08/10/leading-a-team-at-ruby-for-good/)**
76 |
77 | ##### Interested in Leading a Team?
78 | Send us an email at [{{ site.data.constants.contact_email }}](mailto:{{ site.data.constants.contact_email }})
79 |
80 |
--------------------------------------------------------------------------------
/yearbook.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: page
3 | title: Yearbook
4 | extra_js:
5 | - https://rawgit.com/rubyforgood/meta/master/projects.js
6 | ---
7 |
8 | ### Projects
9 |
10 | Here’s a list of the organizations and projects we’ve been able to help over the past years making the world a gooder place — if you have a great idea for a future project, let us know and suggest a project.
11 |
12 | #### 2017
13 |
14 | In 2017, the Ruby for Good event was held in Front Royal, Virgina at [George Mason University’s Smithsonian-Mason School of Conservation](http://smconservation.gmu.edu/).
15 |
16 | {% include projects-yearbook.html year="2017" %}
17 |
18 | #### 2016
19 |
20 | In 2016, the Ruby for Good event was held in Front Royal, Virgina at [George Mason University’s Smithsonian-Mason School of Conservation](http://smconservation.gmu.edu/).
21 |
22 | ##### Portland Diaper Bank
23 |
24 | There are 150,000 children living in poverty in Oregon whose parents often have to make the difficult choice of choosing between feeding their children and putting diapers on them. The great people at the Portland Diaper Bank are helping and need our help to do the great work that they do! [More about the Portland Diaper Bank](http://www.pdxdiaperbank.org/).
25 |
26 | The application we developed was to replace the existing inventory system to provide better data on their operations. The intake process is volunteer-driven but very time-consuming, and the hours spent doing intake of donations is time they can't spend doing other work. The organization had requested intake methods other than hand-counting, such as barcode scanning or using a scale to weight large volume of loose product. We were able to get barcode intake functioning, and have plans to work in some kind of rudimentary scale-assistant as well.
27 |
28 | {% include github-block.html
29 | href="https://github.com/rubyforgood/pdx_diaper"
30 | team="armahillo|cattywampus|tmobaird|katiesteiner|cmmovius|cubadomingo|chrisboredom|shehanr|D-matz"
31 | %}
32 |
33 | ##### Smithsonian Studying the Scimitar Oryx
34 |
35 | Let's be honest, we all want to do great things. What is better than being part of a group that is helping to bring a species that is extinct in the wild back? There are captive populations of the oryx on ranches in Texas that researchers need some help with. They need a centralized database to keep track of the oryx, things like numbers, breeding history (can't let them get inbred), and so on. Once a stable gene pool and other information can be established, researchers are hoping to re-introduce them into the wild!
36 |
37 | {% include github-block.html
38 | href="https://github.com/rubyforgood/scimitar_oryx"
39 | team="nht007|pachacamac|cmar|duaimei|SuperJones|jcavena|rpchurchill|mkmckenzie|jeremywrnr|dpulliam"
40 | %}
41 |
42 | ##### Smithsonian Logging the Loggerhead
43 |
44 | There is only one Shrike native to North America and it is a surprisingly important part of the ecosystem. While they were once extremely common throughout the eastern US and Canada, no other bird species has seen their populations reduced as much since the 1960s. The Conservation Centers for Species Survival needs an application to serve as a central repository for researchers in Canada, the US and Mexico to log their research. How amazing would it be to be part of research that may prevent this amazing animal from going extinct?
45 |
46 | {% include github-block.html
47 | href="https://github.com/rubyforgood/loggerhead_shrike"
48 | team="jjlangholtz|michaelbyrd|holytoastr|marshmalien|jkeam|mobjohnson|ahirschberg"
49 | %}
50 |
51 | ##### Smithsonian Red Pandas
52 |
53 | The red panda researchers are currently using a mish-mash of methods for recording notes and pictures on the state of the red pandas. They need something centralized and accessible by other people. They'd also ideally like the application to work well on tablets since when they are out with the red pandas they use tablets to record their notes.
54 |
55 | {% include github-block.html
56 | href="https://github.com/rubyforgood/panda_app"
57 | team="rmalecky|bhaibel|tpinecone|jgaskins|nathanielksmith|andrewpurcell|christinaforney|"
58 | %}
59 |
60 | ##### Working Landscapes
61 |
62 | The amazing people at the Virginia Working Landscapes have done all the heavy lifting creating wildlife surveys, and now need somewhere to house their information. Virginia Working Landscapes works with partner land-owners throughout the state in numerous watershed zones and organizes teams of citizen scientists to record wetland data. This data is invaluable for state conservation efforts but the current process Virginia Working Landscapes uses to collect and collate that data is slowing down important research. They need an application to record their findings, keep their data organized, and simplify generating accurate reports.
63 |
64 | {% include github-block.html
65 | href="https://github.com/rubyforgood/working_landscapes"
66 | team="h-m-m|maxtedford|exbinary|bglusman|danielpclark|scherenack|cflipse"
67 | %}
68 |
69 | ##### NOLA Habitat Humanity
70 |
71 | As software developers we have it pretty good and and housing isn't a concern for us. Unfortunately, not everyone is as lucky, especially the people of New Orleans. Despite hurricane Katrina happening about a decade ago, there are still a lot of displaced people in temporary residences who need somewhere to call home. The amazing people at habitat for humanity are trying to fix this with their work in New Orleans 9th ward (one of the hardest hit areas by Katrina) and with a recent grant they received their work is only going to move quicker. The problem is, one of the requirements of the grant is a stricter recording and reporting process of their 300 or so daily volunteers which is where we come in! Let's help them with the great work they are doing by making this process faster so they have more time to rebuilding people's lives.
72 |
73 | {% include github-block.html
74 | href="https://github.com/rubyforgood/habitat_humanity"
75 | team="bjmllr|robbkidd|pat|scooter-dangle|Brantron|jenpen|jdsayle"
76 | %}
77 |
78 | ##### Share Your Christmas
79 |
80 | It is an unfortunate reality that not every child has presents under their Christmas tree. The amazing people at the Durham Volunteer Center have a program, Share your Christmas, that matches needy children up with people able to ensure they have something special under their tree. They need a new app to facilitate their process of matching donors and receivers. Ideally they would also like to have it generic enough to also work for thanksgiving (turkeys) and the start of the school year (backpacks full of school supplies for kids.) Even though their current process is extremely terrible, other cities have expressed interest in this so this group will potentially be helping kids from all over the country!
81 |
82 | {% include github-block.html
83 | href="https://github.com/rubyforgood/share_christmas"
84 | team="craig-riecke|AEgan|nolds9|ajohnson052|jaydorsey|vegajdr|Josecc"
85 | %}
86 |
87 | ##### Manjia
88 |
89 | Manjia was born out of disappointment over the amount of food waste created each year that goes unrecovered. We know there are people in desperate need of food donations and that there are also a lot of people with a surplus of food. We believe that by providing a simple way for people from those two groups to be connected it will significantly reduce the amount of food wasted. As sustainability becomes more and more a topic of conversation we hope that food recycling can be discussed as one of the easiest ways to improve the lives of those in need while at the same time lessening our impact on the world by reducing landfill waste.
90 |
91 |
95 |
96 | ---
97 |
98 | #### 2015
99 |
100 | In 2015, Ruby for Good was held at the Fairfax Campus of George Mason University.
101 |
102 | ##### Humane Society of Fairfax County
103 |
104 | {% include github-block.html
105 | href="https://github.com/rubyforgood/hsfc"
106 | team="adamlwalker|maebeale|dgarnder|jjlangholtz|valeriecodes|ldewald|madtypist|michaelbyrd|Ameria|htakeguchi|pamtaro|edwardpark"
107 | %}
108 |
109 | ##### The Purple Door
110 |
111 | Purple Door Coffee is a specialty espresso bar and coffee shop in Denver, Colorado that employs teens and young adults who have been homeless and want to leave homelessness behind. Their mission is to reclaim and sustain the lives of homeless youth and young adults through supportive and meaningful employment.
112 |
113 | {% include github-block.html
114 | href="https://github.com/rubyforgood/purple_door-1"
115 | team="saturnflyer|elight|crrdev01|jcavena|mallorybucell|jgujgu|CraigJZ|jayroh|gxespino|mlpinit|GeekOnCoffee"
116 | %}
117 |
118 | ##### Growhaus
119 |
120 | A statistics recording and tracking application made for the folks at The Growhaus.
121 |
122 | The GrowHaus is a nonprofit indoor farm in Denver's Elyria-Swansea neighborhood. Our vision is to catalyze a neighborhood-based food system in our community that is healthy, equitable, and resident-driven.
123 |
124 | {% include github-block.html
125 | href="https://github.com/rubyforgood/growhaus_stats"
126 | team="nevern02|indiesquidge|adunkman|bengm|nonegiven444|waffle-iron|fearthegoat"
127 | %}
128 |
129 | ##### All Income Foods
130 |
131 | An app that lists places that accept food stamps.
132 |
133 | {% include github-block.html
134 | href="https://github.com/rubyforgood/AllIncomeFoods"
135 | team="shrtlist|jwieringa|jerseycoder|abannert|ysiadf|mabundo|onezerojeremy|zph|kwals|rmalecky|tommarkallen|davix"
136 | %}
137 |
138 | ##### RSpec
139 |
140 | Contributing to the RSpec testing framework.
141 |
142 | {% include github-block.html
143 | href="https://github.com/rspec/rspec"
144 | team="cupakromer"
145 | %}
146 |
147 | ---
148 |
149 | #### 2014
150 |
151 | In 2014, Ruby for Good was held at the Fairfax Campus of George Mason University.
152 |
153 | ##### Kutoa
154 |
155 | Help the sole developer of the non-profit Kutoa.org. They are looking for help figuring out how best to test with Rails and Rspec and hope to get a solid foundation.
156 |
157 | Kutoa is an innovative giving movement that is uniting people around the world to give to a common cause. Give your $1/month and get a vote what project all of our money should support. Every dollar matters!
158 |
159 | {% include github-block.html
160 | href="#privaterepo#"
161 | team="rcarter|armahillo"
162 | %}
163 |
164 | ##### Pathway Homes
165 |
166 | Pathway Homes is a charitable organization providing non-time-limited housing and supportive services to adults with serious mental illness and other co-occurring disabilities in Northern Virginia. Founded in 1980, Pathways currently serves more than 400 adults with serious mental illness in community-based homes in Northern Virginia.
167 |
168 | {% include github-block.html
169 | href="https://github.com/rubyforgood/pathway-homes"
170 | %}
171 |
172 | ##### Trail Reporter
173 |
174 | App for crowdsourcing hiking trail hazards and conditions.
175 |
176 | {% include github-block.html
177 | href="https://github.com/rubyforgood/trail_reporter"
178 | team="syoder|alloy-d|briandamaged|maryhipp|michaelbyrd|joellastraley"
179 | %}
180 |
--------------------------------------------------------------------------------