|
| 1 | +# Contributing |
| 2 | +When contributing to this repository, please first discuss the change you wish to make via issue, |
| 3 | +email, slack, or any other method with the contributes of this repository, or Code for Baltimore, before making a change. |
| 4 | + |
| 5 | +Please note we have a [Code of Conduct](/docs/Code_of_Conduct.md), please follow it in all your interactions with the project. |
| 6 | + |
| 7 | +## Overview |
| 8 | +In the event of a disaster a municipality or state may have need to check in on the status of all healthcare providers, |
| 9 | +or other types of entities, within in the jurisdiction. This system will provide methods for healthcare providers and |
| 10 | +entities to check-in during disasters, and update their contact information during non-emergency periods. During an |
| 11 | +emergency this system will track (among other things) if any entity: |
| 12 | + |
| 13 | +* Has power |
| 14 | +* Has sufficient supplies |
| 15 | +* Is informed about the emergency |
| 16 | + |
| 17 | +This system will make use of digital services and modern methodologies to automate and simplify parts of the check-in process |
| 18 | +to help the municipality prioritize its call/check-in list and response plan. Additionally, the system will validate contact |
| 19 | +information regularly during non-emergency times to ensure the municipality has the most up-to-date information for each entity. |
| 20 | + |
| 21 | +### Non Goals |
| 22 | +What will this project not accomplish during its initial creation? |
| 23 | + |
| 24 | +- No front-end website or app |
| 25 | +- No outside data interactions |
| 26 | +- Non-city employee full login (dashboard, etc) |
| 27 | +- Statistical or analytical endpoints |
| 28 | + |
| 29 | +### Minimum Viable Product |
| 30 | +To use this product as quickly as possible we will be implementing the following features: |
| 31 | +- User creation |
| 32 | +- Contact creation |
| 33 | +- Entity creation |
| 34 | +- Contact->Entity linking |
| 35 | +- Contact single-use login check-in ability |
| 36 | + |
| 37 | +### Roadmap |
| 38 | +Milestones and project timelines can be viewed on the [Projects page](https://github.com/CodeForBaltimore/Bmore-Responsive/projects) |
| 39 | + |
| 40 | +## Technology and Code |
| 41 | + |
| 42 | +This project will make exclusive use of open-source software, packages, and contributions. The application is built with the following |
| 43 | +technologies: |
| 44 | + |
| 45 | +- Javascript (ES6) |
| 46 | +- [Node.js](https://nodejs.org/en/) |
| 47 | +- [Express.js](https://expressjs.com/) |
| 48 | +- [Sequelize](https://sequelize.org/v3/) |
| 49 | +- [Docker](https://www.docker.com/) |
| 50 | +- [Terraform](https://www.terraform.io/) |
| 51 | + |
| 52 | +Please see our [Tech Spec](/docs/Tech_Spec.md) for a full breakdown of the project and workflows. |
| 53 | + |
| 54 | +Please see our [Best Practices](/docs/Best_Practices.md) for code standards, git standards, and other guidance for writing clean and well |
| 55 | +documented code. |
| 56 | + |
| 57 | +### Pull Request Process |
| 58 | +1. Ensure you thoroughly fill out the pull request form presented when submitting the request. |
| 59 | + This includes listing what work was done, what issues are resolved by that work, what tests |
| 60 | + have been added, how to perform other tests or run the code, and other potentially relevant |
| 61 | + notes. |
| 62 | +2. Update the README.md with details of changes to the application, this includes new environment |
| 63 | + variables, exposed ports, useful file locations and/or container parameters. |
| 64 | +3. If you are on the project team you may merge the Pull Request in once you have the sign-off of one other developer, or if you |
| 65 | + do not have permission to do that, you may request the second reviewer to merge it for you. |
| 66 | + |
| 67 | +## Contact |
| 68 | +The best ways to get in touch with us is via Slack. An active Slack link can be found on our website: |
| 69 | + |
| 70 | +***[codeforbaltimore.org](https://codeforbaltimore.org/)*** |
| 71 | + |
| 72 | +You can also reach out to the tech lead [Jason Anton](https://github.com/revjtanton) via email at [jason@codeforbaltimore.org](mailto:jason@codeforbaltimore.org). |
| 73 | + |
| 74 | +## Sources and Links |
| 75 | +We are also building a front-end application called [Healthcare Rollcall](https://github.com/CodeForBaltimore/Healthcare-Rollcall) to interact |
| 76 | +with this backend API. To view that project, or to contribute to it, please visit the repo here: https://github.com/CodeForBaltimore/Healthcare-Rollcall |
0 commit comments