NYCPlanning / NYCPlanning/data-engineering
Long Term Plan for edm-data-operations
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
Do we own this? Does it makes sense for us to?
I think it would make sense for us to add it to our product lifecycle, given our expertise.
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
Start by reviewing the linked edm-data-operations repository and the issue's question about ownership. Determine whether it belongs in this team's product lifecycle; done would be a documented decision and agreed next steps, but the issue does not name files, tests, or an implementation entry point.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100