Filepack Roadmap
- Dominant language
- Rust
- Stars
- 94
- Forks
- 8
- Avg merge
- 23m
- Merged PRs (30d)
- 164
Description
I thought it would be a good idea to share a roadmap. Filepack has lofty goals, but I don't think this necessarily comes across in the documentation, since I like to keep it focused on the current state of the project.
The following is very much incomplete, but should give some idea of the big groups of features and functionality that are planned.
- *Basic media types:* Audio, documents, images, and video.
- *Demo server:* Package 10 packages of free content for each media type. Basic styling for all pages.
- *User accounts:* Add user accounts to the server, so communities of people can collaborate on creating and curating packages. Invite users to demo server to package more free content. Collect feedback and improve usability.
- *Backwards compatibility:* At some point, filepack must commit to backwards compatibility. It has a huge surface area, so this is a huge, scary effort.
- *Simple sharing:* Server RSS feeds, CBOR package feed, server federation.
- *P2P network:* P2P network dedicated to sharing filepack packages.
- *Misc:* Rust library with cross-language bindings. SPA media player. jj/git backend. Package versioning. More media types: executables, physical media images, source packages, web apps, WASM apps.
Contributor guide
Research direction
No files, tests, or entry points are named; start by reviewing the existing documentation and the roadmap in this issue. Done would mean agreeing on where and how these planned feature groups should be documented, with the roadmap accurately reflecting the project's intended direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100