Potential use case: drop Distribution entirely?
Open
Nobody has claimed this yet.
Feature
Triage-Needed
- Dominant language
- Python
- Stars
- 1
- Forks
- 4
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 6
Description
So much is going directly through the API that it's questionable whether the distribution is even needed. The Distribution provides a base_url and a remote and that's basically it.
We should audit whether there is genuinely a need for:
- multiple views of the same repository
- content guard functionality
in the same way as other plugins
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
Start by auditing the Distribution and its base_url and remote, then investigate whether multiple views of the same repository and content guard functionality are needed, comparing other plugins as the issue requests. Done means a documented decision on whether Distribution can be dropped and what repository behavior that would affect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100