Rails-based case management system for the DC Abortion Fund
Clone or download
colinxfleming Merge pull request #1492 from DCAFEngineering/more-gem-updates
Update jquery-rails, js-routes, kaminari
Latest commit f18eb14 Oct 10, 2018
Permalink
Failed to load latest commit information.
.circleci patch rubyzip cve Sep 14, 2018
.docker one last shot at 2.5.1 Apr 10, 2018
.github add link to SECURITY_INTRO.md to CONTRIBUTING and SETUP.md Jul 20, 2017
_design move old wireframes into specific folder Feb 18, 2017
app Merge branch 'master' of github.com:DCAFEngineering/dcaf_case_managem… Sep 24, 2018
bin rails app:update Aug 6, 2017
config resolve merge conflicts Jul 7, 2018
db resolve merge conflicts Jul 7, 2018
docs Merge branch 'impact' of github.com:DCAFEngineering/dcaf_case_managem… Jun 7, 2018
lib review fixes - ref a constant, use assert_not over refute May 30, 2018
log resolve merge conflicts Jan 3, 2016
public Move favico to asset pipeline Aug 4, 2017
spring added devise and minor updates Dec 22, 2015
test bundle update factory_bot_rails, squelch depreciation warning Sep 29, 2018
vendor/assets Remove Google Analytics from vendor, CRSF and assets Apr 18, 2017
.dockerignore extract setup instructions from readme into their own minidoc Jan 28, 2017
.gitignore Git Ignore that Jan 29, 2018
.rubocop.yml bump rubocop May 30, 2018
.slugignore make slugignore Aug 21, 2016
CODE_OF_CONDUCT.md Added "What to Do" section Mar 3, 2017
Gemfile Merge pull request #1492 from DCAFEngineering/more-gem-updates Oct 11, 2018
Gemfile.lock Merge pull request #1492 from DCAFEngineering/more-gem-updates Oct 11, 2018
LICENSE.txt add MIT license, associated edits Feb 21, 2016
Procfile Initial commit of changes to move from Unicorn to Puma Dec 8, 2016
README.md Merge pull request #1373 from DCAFEngineering/RipGemnasiumWeHardlyKne… May 12, 2018
Rakefile undo global call list nuking every night. SORRY EVERYONE Jan 17, 2018
app.json config out of the env and into the code Jun 21, 2018
civic.json fix a small typo in the civic.json Jul 22, 2017
clinics.yml Scaffold for integrating clinic_finder gem Mar 5, 2017
codecov.yml trying to remove commits Jul 6, 2016
config.ru move rails app to main dir Dec 21, 2015
docker-compose.yml updated rails to 5.1.5 Feb 21, 2018
knapsack_minitest_report.json rerack knapsack Jul 1, 2018

README.md

DARIA (DCAF Case Manager)

CircleCI codecov

A deployed demo version of what's in the master branch is at: https://sandbox.dcabortionfund.org/ User: test@test.com, Pass: P4ssword

Next major project milestone: Sharing with other funds

Major new feature development on this project has more or less drawn to a close. Our general administration/maintenance plan is here. If you are an abortion fund interested in whether this would work for you, hit us up and let us know!

Come hang out with us on slack!

Join via the Code for DC website.

Are you from an abortion fund and are interested in seeing this will work for you?

Join the Code for DC slack, go to the channel #dcaf_case_management, and let us know!

Project description

This project is a case management system for the DC Abortion Fund (DCAF), an all-volunteer, 501(c)(3) non-profit organization that gives grants to people in DC, Maryland, and Virginia who cannot afford the full cost of abortion care. Its primary goal is to simplify routine case management processes, such as keeping track of patient data, pledges, and contact information.

Before this app went into production at DCAF, a team of 75 case managers were inputting around 3,500 calls a year into shared Excel sheets. This app replaces that with a nice, clean, useable and shareable rails system that ditches spreadsheets forever! This lets DCAF and other funds continue to operate at a fast pace, and prevents volunteers from getting frustrated with shared Excel sheets.

In addition, other abortion funds doing similar work in other places can adopt this system to their use. We have a

Get started with the how-and-why of the project by checking out DCAF, checking out DCAF Case Manager Lisa's explanation of DCAF's business logic, reading the Code of Conduct, and reading the #dcaf_case_management channel on Slack. You can also check out some of the other buzz.

Who's in charge here?

The team leads are:

  • @colinxfleming (rails and technical lead)
  • @mebates (design and UI lead)
  • @nerdygirl573 (DARIA manager)
  • @lwaldsc (DCAF liaison)
  • @alisonnjones (data lead)

Feel free to hit any of us up with questions about the project, we're nice!

Contributing to this Project

tl;dr

  • We are best reached via the Code for DC slack
  • We run on forks and pull requests
  • Our list of issues in Github is our project's remaining TODO list
  • Post in an issue when you're starting work on something, so @colinxfleming can keep track of it and so we don't duplicate work
  • We <3 new people and beginners

If this is your first time, a good way to get oriented is to leave our users a nice note! Check out instructions here.

Setting Stuff Up

We have detailed instructions on how to get started here!

If you have any trouble getting things set up, please ping us in Slack!

If you see a spot in the docs that's confusing or could be improved, please pay it forward by making a pull request!

We <3 new people and beginners!

We recognize that not everyone comes to this project intimately familiar with rails. If you've got the time and energy to contribute, we've got the time to help guide you in the right direction and make sure your time is well spent. We've also got a set of issues that are good starting points if you're fresh to this project.

We've tried to structure the project in such a way that minimal specialized knowledge is required to contribute; we use the default Rails stack wherever possible, with the exception of MongoDB and a couple gems.

We prioritize inclusivity of all skill levels on this project -- in general, if you are willing to put in the time to learn, a team member will be willing to work with you to make it happen!

Pull Requests Please!

This project runs on Github forks and pull requests, so we can be sure to make changes incrementally and keep everything clean. For an introduction to Github, check out this guide on github.com.

Here's how you do it:

  • Visit the main project page and fork from the master branch by pressing the fork button near the top right.
  • Do any work in your local environment and commit it to your fork in github.
  • Once you have finished your changes and have confirmed they're all working, make a pull request by pressing the Pull Request button.
  • At least one other person will review and comment on code changes, work with you to resolve issues, and merge the pull request when it's ready.

Project Wall of Appreciation

Like all volunteer projects, we'd be dead in the water if it weren't for the hard work of our valuable team. Championship contributors to this project (so far!) include:

  • @ajohnson051
  • @Kevin-Wei
  • @charleshuang80
  • @drownedout
  • @rebeccaestes
  • @ashlynnpai
  • @camlatimer
  • @mchelen
  • @ewiggins
  • @katsdc
  • @eheintzelman
  • @DarthHater
  • @lomky
  • @ian.norris
  • @tingaloo
  • @colinmcglynn

Special thanks

The following are people who have been uniquely generous with their time, resources, and expertise:

License

Made available under an MIT license. See LICENSE.txt for more info.