Remove the frontend
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 67
- Forks
- 52
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 54
Description
Nobody is really using it as far as I know. If we want to visualize results for debugging reasons, we can just connect to the backend DB manually. Another option could be to ingest the issues into BigQuery so we can also query them and see evolution over time, etc.
WDYT @Archaeopteryx @La0, any concerns?
Contributor guide
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 locating the frontend and checking how it is used, then review the proposed backend database and BigQuery alternatives. Done means the project agrees on a direction and defines the scope and validation for removing or retaining the frontend.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, python
- Domain
- data, frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100