We are building an integration to put our requests into github in the future; in the present, we would benefit from being able to allow community participation (our db does not let people comment or assign themselves)
[x] create a github issue the same repository as this issue
use the below template for the body
summarize the request in a few words for the title
[x] copy the github issue URL to the "github_issue" property in the spreadsheet
[x] migrate the work_required column as labels. For example, "data location,records request" would get data location and records request labels. Ignore "collaborators" label.
Josh tasks
[x] add the issue to this project, and give it the appropriate status
[x] This leaves out pdap_response. I will comment that on each issue after the fact.
[x] I will also close issues based on their status. One day a bot will do this
Template
You can copy and paste this into the issue, and it will start properly formatted
Someone has requested help on a data project:
## Submission notes
{submission_notes}
## Location
{location_described}
## Requirements
{data_requirements}
Target date: {target_date} (leave this out if not present)
Coverage range: {coverage_range} (leave this out if not present)
## How to help
Leave a comment if you'd like to help. Do you have ideas, questions, or need any more information to get started?
Context
We are building an integration to put our requests into github in the future; in the present, we would benefit from being able to allow community participation (our db does not let people comment or assign themselves)
This spreadsheet is our source.
Requirements for each request:
Example issue: https://github.com/Police-Data-Accessibility-Project/data-projects/issues/10
work_required
column as labels. For example, "data location,records request" would getdata location
andrecords request
labels. Ignore "collaborators" label.Josh tasks
pdap_response
. I will comment that on each issue after the fact.Template
You can copy and paste this into the issue, and it will start properly formatted