Product Portfolio And Lifecycle¶

Status: governance. Updated 2026-10-02 after publication of rust-v0.1.0-beta.1. This is the current role map for repositories maintained or retained by the eMuleBB organization.

Lifecycle Classes¶

Class	Meaning
Active experimental	Current development and public prereleases; not a production-readiness claim
Maintenance	Published software accepting bounded, low-risk changes only
Paused experiment	Preserved and buildable on demand, but without roadmap, issue intake, or scheduled work
Reference	Retained for analysis or potentially upstreamable contributions
Harness	Test infrastructure whose behavior changes only when the maintained harness requires it
Infrastructure	Build, test, documentation, policy, and public-presence support
Archived experiment	Read-only historical source with no active backlog

Current Portfolio¶

Repository	Lifecycle	Current role
`emulebb-rust`	Active experimental	Primary active eD2K/Kad client; public `0.1.0-beta.1`
`emulebb` (MFC)	Maintenance	Stable Windows `0.7.x` line; bugs and bounded low-risk changes only
`qbittorrentbb`	Paused experiment	Preserved BitTorrent experiment; not part of the default workspace
`emulebb-libtorrent`	Paused experiment	qBittorrentBB engine fork; not part of the default workspace
`amutorrent`	Maintenance / paused	Frozen controller shipped with the `0.7.3` bundle; no forward roadmap
`trackmulebb`	Archived experiment	Private archived controller experiment
`goed2k-server`	Harness	Deterministic local eD2K test server; no product evolution
`ed2k-server`	Reference	Managed Rust fork for analysis and potentially upstreamable contributions
`emulebb/amule`	Reference	aMule analysis fork; automation remains active but is not product promotion
`analysis/amule`	Reference	Optional checkout of maintained upstream `amule-org/amule`
`emulebb-build`, `emulebb-build-tests`, `emulebb-tooling`	Infrastructure	Workspace orchestration, tests, policy, and documentation
`emulebb-pages`, `emulebb-org-profile`	Infrastructure	Public website and GitHub organization profile
Other `emulebb-*` dependency forks	Infrastructure	Reproducible native build inputs
`p2p-overlord-*`	Archived separate family	Retained outside the eMuleBB product roadmap

Product Direction¶

emulebb-rust is the only active product-development lane. It is an experimental beta and must not be presented as production-ready. eMuleBB MFC remains published and supported on 0.7.x, but its development surface is limited to compatibility-preserving bug fixes and bounded UX, performance, build, packaging, documentation, diagnostics, and release work. New subsystems, broad APIs, protocol expansion, and architectural modernization remain parked.

The forward cross-network suite program is retired. The term eMuleBB Suite is retained only for the shipped 0.7.3 MFC/aMuTorrent bundle, its artifacts, and historical documents. Current organization-wide planning uses eMuleBB Roadmap.

Native Windows VPN integration is not a forward development priority. Existing behavior and safety claims remain evidence-bound; no unnamed Docker/Gluetun stack is an eMuleBB product until explicitly adopted.

Backlog Rules¶

Project #3, eMuleBB Roadmap, contains current GitHub-primary work.
MFC feature expansion and major refactors remain DEFERRED as a parked ledger; they are not release commitments and are not closed as WONT_DO.
qBittorrentBB, aMuTorrent forward work, TrackMuleBB, and ed2k-server production-hardening items are historical, not active backlog.
New ed2k-server issues may cover analysis or upstreamable work, but must not recreate a production-service roadmap without a new operator decision.