RFC: Fetching module
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 307
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Hereinafter, the list of features to implement:
-
Local repositories
-
HTTP/HTTPs repositories
-
Integrate support of aggregate download per repository
-
Integrate support of custom Authentication support (Basic, Token, etc.)
-
Fetching packages from multiple sources (FTP, HTTP, Object Store, Directory)
-
Support incremental download for package revisions
-
Support Proxy Configuration
-
Support
--fetchonlyoption for prepare cache directory to use in offline env -
Mirror list for repository must be a separated file more easy to update through a package
-
Integrity check / packages verification
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
This is a broad RFC checklist for the fetching module, with several unfinished features and no files, tests, or entry points named. Start by reviewing the current fetching implementation and the unchecked requirements; the issue does not define a focused scope or a concrete completion test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100