Community
There is no chat server and no QQ group. Everything happens in the repository, where it is searchable and permanent.
Where each kind of question goes
No chat, so the routes are explicit. Nothing on this site is a dead end.
routes
Searchable and permanent, which a chat log is not.
Issues
A bug report is worth ten opinions. Useful reports include: the TurboDL version (v0.4.1.0), the JDK, the target URL or a minimal reproduction, and what you expected instead.
Before you open a pull request
These are the same steps the maintainer runs. Nothing secret, nothing extra.
the checklist
The suite covers byte-level correctness, resume and the plugin lifecycle; a change that breaks it is a change that is not ready.
Discussions
GitHub Discussions is not enabled on this repository, so this site does not pretend otherwise — questions go to Issues too.
What a useful report contains
Four fields, and a report missing any of them usually turns into three round trips of questions.
the template
Nothing else is required, and nothing is collected automatically.
Contributing
Bug fixes, new plugin backends, and documentation corrections are all welcome. Please keep the dependency direction (runtime → core) and run ./gradlew test before opening a pull request — the suite covers byte-level correctness, resume, and the plugin lifecycle.
License
MIT License, with supplemental terms clarifying that plugins are independent works: they may carry any license, and interacting through the public API does not make them derivatives of TurboDL.
what MIT lets you do
The project's own code is MIT; the plugin-ecosystem terms only clarify that interacting through the public API does not make a plugin a derivative.
Acknowledgements
TurboDL borrows architectural and algorithmic ideas — no source code — from these projects, with thanks: aria2, Xtreme Download Manager, axel, Persepolis, Motrix, ab-download-manager.