Remove legacy ingester code
- Dominant language
- Python
- Stars
- 0
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Since we have moved to the django ingester, the implementation in this repository is outdated and unnecessary. Not only that, but having two different codes for the same tool might be confusing for external folks. So I would say that we can remove the ingester's code in this repository and point users to the dashboard implementation, unless there's more reason to keep it here
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the legacy ingester implementation and references to it in this repository, then compare them with the Django ingester and dashboard implementation mentioned in the issue. Done means the obsolete code is removed, users are pointed to the dashboard implementation, and no remaining references require the old ingester.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend, data-engineering
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100