This is the repo where we track all of our Issues, regardless of project area.
For the actual code and to submit Pull Requests outside of README and other project-level documentation, see:
| Repo | Tech | Description |
|---|---|---|
| nightingale-server | Elixir, Phoenix, Postgres, PostGIS | The backend API server used by the mobile app. |
| nightingale-mobile | React Native | The user-facing mobile app. |
| nightingale-cluster | Kubernetes, FluxCD | The YAML files that define our Kubernetes cluster resources. |
| nightingale-site | Wordpress | This is the source code for nightingale.revelry.org. |
Our goals for the week starting Tuesday, May 26, 2020:
- Prototype and validate/invalidate an Open Source Contact Tracing App that automates, securely and anonymously, the contact tracing process.
- Conduct customer research and design studios to identify the most impactful way to address Contract Tracing and/or other COVID-19 needs among the hardest hit populations
While we work on creating a robust README for this Open Source project, interested parties can review this Google Slides presentation for an easily-consumable overivew. You can also review this public Google doc, which serves as a Work in Progress (WIP) README that we are adapting and pulling over into this repo.
For insights into early decisions, see the prior discussion on revelrylabs/tracing#1.
For insights into our plans for the U.S.-holiday shortened week of May 26, 2020, please see this Issue: #1
Please see the Milestones page to get a sense of the initial shaping of the work for Track A.
- Kanban Board for Issue prioritization and tracking.
- Project Folder on Google Drive
- A place to store and collaborate on non-git documents, such as docs, spreadsheets, presentations, etc.
- This folder or subsets of folders may have limited access (such as documents with personal contact info for customer interview participants).
- Nightingale Marketing Website
- Public Domain TBD
- Production (Pushing all code and content to Production until we go live, then we'll switch to a Staging > QA/UAT > Production workflow)
- Staging (Staging will remain empty until we go live with Production)
We encourage discussion to occur using the Comments on Issues and their respective Pull Requests. We find it important to capture questions and decisions as close to where the work is committed, so we lean on GitHub Comments.
For general discussion, deliberation, and planning, we encourage you to join the #tracing Slack channel in the Revelry Public Slack. Not yet a member? Gain access via https://community.revelry.co
As an Open Source project, we aim to foster positive and generative interaction among contributors and with the community at-large.
Please see the CONTRIBUTING file for our guidelines.
Nightingale is MIT licensed and Copyright (c) 2020 Revelry Foundation, as found in the LICENSE file.