NYCPlanning / NYCPlanning/data-engineering
dcpy and build lifecycle improvements
Open
Nobody has claimed this yet.
platform
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
Structural work on dcpy and the build lifecycle: reproducibility, configuration, naming, and documentation.
Grouped from long-standing issues that may or may not still be worth doing
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
No files, tests, or entry points are named. Start by reviewing dcpy, the build lifecycle, and the long-standing issues grouped here; completion would require a defined scope for the reproducibility, configuration, naming, and documentation work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100