You can reach us on the Civic Tech DC slack, in the #daria channel or contact us via our website. Please reach out!
This project is a case management system for abortion funds. Abortion funds are organizations that give grants to people who cannot afford the full cost of abortion care. Our primary goal with this project is to simplify routine case management processes, such as keeping track of patient data, pledges, and contact information.
This originated with the DC Abortion Fund (DCAF). 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. Since adopting this system, DCAF and several other funds have been able to operate at a much faster pace, and lowered the stress levels of their volunteers. We now support multiple funds across the country.
Get started with the how-and-why of the project by checking out Abortion funds, reading case manager Lisa's explanation of an abortion fund's business logic, reading our Code of Conduct, and joining the #daria channel on Slack.
You can also check out some of the other buzz or read about how it's impacted DCAF.
There's still work to do, but generally we're pretty stable these days. Our general administration/maintenance plan is here.
A deployed public demo version of Daria can be accessed at https://sandbox.dariaservices.com/
It updates to match the current state of main.
User: test@example.com
Password: AbortionsAreAHumanRight1
We have detailed instructions on how to get started here!
The team leads are:
- @colinxfleming (general lead)
- @lomky (technical lead)
- @lwaldsc (process lead)
Feel free to hit any of us up with questions about the project, we're nice!
- We are best reached via the Civic Tech 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
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 a couple gems.
We prioritize inclusivity of all skill levels on this project -- 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!
Like all volunteer projects, we'd be dead in the water if it weren't for the hard work of our valuable team. We are eternally grateful to every contributor, be they programmers, designers, researchers, case managers, project managers, bug hunters, documenters, or anyone else keeping us afloat!
The following are people who have been uniquely generous with their time, resources, and expertise:
- Team Brakeman, a group of security specialists who have been very kind to us
- Mike from OWASP DC, who provided critical guidance and insights when we were really bolting this down for production use
Made available under an MIT license. See LICENSE.txt for more info.