DPG Approved

Human Essentials is an inventory management system built to address the needs of Diaper Banks as directly and explicitly as possible and adapted to meet the needs of other Essentials Banks. Essentials Banks maintain inventory, receive donations and other human essentials supplies (e.g. diapers, period supplies), and issue distributions to community partner organizations. Like any non-profit, they also need to perform reports on this data and have day-to-day operational information they need. This application aims to serve those needs and facilitate the general operations of the Diaper Banks (e.g., using barcode readers, scale weighing, inventory audits).

Human Essentials has over 200 registered banks across the United States at no cost to them. It is currently helping over 3 million children receive diapers and over 400k period supply recipients receive period supplies. Our team is in partnership with the National Diaper Bank Network (NDBN) and can be found in their annual conference that brings numerous of non-profit organizations that distribute essential products to people.

We are proud of our achievements up to date but there is much more to do! This is where you come in...

Human Essentials is one of many projects initiated and run by Ruby for Good. You can find out more about Ruby for Good at https://rubyforgood.org

The Digital Public Goods Alliance recognizes Human Essentials as a digital public good (DPG). This project supports the following Sustainable Development Goals:

• SDG 1 - End poverty in all its forms everywhere
• SDG 3 - Ensure healthy lives and promote well-being for all at all ages
• SDG 10 - Reduce inequality within and among countries

Use as an Organization or Contribute as an Individual/Team to this Project:

• NGO Adoption Info - information about how to use this DPG
• Skills Based Volunteering Info - information about how to volunteer

Thanks for checking us out! Check out our Contributing Guidelines on how to contribute.

The human-essentials & partner application should ideally be deployed on a weekly or bi-weekly schedule depending on the merged updates in the main branch. This is the process we take to deploy updates from our main branch to our servers.

• SSH access to our servers (usually granted to core maintainers)
• Login credentials to our Mailchimp account

All deploys deploy from the production branch, which keeps track of what is currently in production.

git checkout production
git merge main

1. Push a tag with the appropriate date versioning. Refer to the releases for the correct versioning. For example, if you are deploying on June 23, 2024:

   git tag 2024年06月23日
   git push origin tag 2024年06月23日

2. Publish a release, associated to that tag pushed up in the previous step, here. Include details about the release's updates (we use this to notify our stakeholders on updates via email).

Run delayed jobs locally with the rake jobs:work command. This is necessary to view any emails in your browser. Alternatively, you can run a specific delayed job by opening a Rails console and doing something like:

Delayed::Job.last.invoke_job

You can replace the last query with any other query (e.g. Delayed::Job.find(123)).

Thanks to Rachel (from PDX Diaperbank) for all of her insight, support, and assistance with this application, and Sarah ( http://www.sarahkasiske.com/ ) for her wonderful design and CSS work at Ruby For Good '17!

FOSSA Status

Thanks goes to these wonderful people (emoji key):

This project follows the all-contributors specification. Contributions of any kind welcome!