NYCPlanning / NYCPlanning/data-engineering
QA app: infrastructure and per-product reports
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
Improvements to the QA app itself and to the QA reports for products other than PLUTO.
PLUTO-specific QA work lives in #1237.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the QA app and QA reports, but no files, tests, or entry points. Start by locating the QA app and the report-generation code, then clarify which infrastructure improvements and non-PLUTO product reports are required; done should be defined as the agreed changes working for the targeted products.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100