This repository aims to document the Carceral Ecology project, that is being developed by Professor Nicholas Shapiro, UCLA, and Professor Lindsay Poirier, UCD.
Incarcerated people are on the frontlines of environmental injustice. This systematic exposure of, at a minimum, tens of thousands of incarcerated individuals results from mass incarceration’s close ties with declining, but very much ongoing, industrialism. Often built atop the brownfields of former manufacturing facilities or mines or on the cheap land next to operating facilities, prisons serve as a “recession-proof” employer to those laid off in deindustrialization beginning in the 1970s. This project seeks to assess the environmental hazards of mass incarceration on a national scale.
This project has three main arms:
- Environmental monitoring
- Iterative study design with stakeholders
- Data analysis of datasets that may cast light on the environmental conditions of prisons, jail, and detention centers
It is the third component, and specifically work related to ECHO data, is what we will be working on in this repo. We are managing our work flow through the issues function. Thats probably the best place to start contributing.
See our protocols for this project here.
- Existing issues:
- Review this repo's issue queue (and particularly the issues labeled "Help Wanted") for opportunities to contribute to open questions and ongoing tasks.
- Assign yourself to issues you are contributing to so that the group knows who to contact in regards to the issue.
- Comment on issues with relevant ideas or resources.
- Mark your progress on issues in this repo's project board.
- New issues
- File a new issue via this repo's issue queue, asking a question, documenting a bug, or suggesting a direction for further research and development.
- Assign yourself or others to issues so that the group knows who to contact in regards to the issue.
- Select Labels to note whether the issue is a question, bug, or a suggested enhancement. Select the "Help Wanted" label to signal that you are looking for collaborators on the issue.
- If the issue contributes to a project or milestone, be sure to add this label.
- Mark your progress on issues in this repo's project board.
- When contributing code, please be sure to:
- Fork this repository, modify the code (changing only one thing at a time), and then issue a pull request for each change.
- Follow the project's coding style (using K&R-style indentation and bracketing, commenting above each feature, and using snake case for variables).
- Test your code locally before issuing a pull request (not sure how to do this? here's how).
- Clearly state the purpose of your change in the description field for each commit.
- After your first pull request is approved, please add yourself to the contributors list in the README as is appropriate.
For any questions on decorum please see our Code of Conduct.
| Contributions | Name |
|---|---|
| 🔢 📋 🤔 | Nick Shapiro |
| 🔢 📋 🤔 | Lindsay Poirier |
| 🔢 📋 🤔 | Melissa Chimwaza |
| 🔢 | Kelly Salinas |
| 🔢 🤔 | Nathan Tran |
| 🔢 📋 🤔 | Sarah Tan |
| 🔢 📆 🤔 | Ramya Natarajan |
| 💻 🚇 🤔 | Ben Millam |
| 🔢 🤔 | Derek Sportsman |
| 🔢 | Ivy Molina |
| 🔢 | Savannah Ramirez |
| 🔢 | Prasann Ranade |
| 🔢 | Alice Lu |
| 🔢 | Raymond Ko |
(For a key to the contribution emoji or more info on this format, check out “All Contributors.”)
LICENSE file for details.