Milestones
List view
An operator adds one address to a Jellyfin server, sees the plugins, and installs one. Everything before this milestone exists to make that step boring.
No due date•10/10 issues closedPersonal data stays on the operator's host unless the operator deliberately federates, this repository collects nothing, and the documents an operator reads say so.
No due date•6/7 issues closedThe gate on iderex/jellyfin-plugin-sso is the target. Each leg is either adopted here, adapted, or dropped, and every deviation carries one line saying why.
No due date•9/9 issues closedTurning the published design document into values a machine can compare and prose a reviewer can apply, so that holding a client to it means something.
No due date•4/4 issues closedThe public page: what it says, what it must not say before it is true, and a check that refuses a page pointing at something that does not exist.
No due date•5/5 issues closedPutting the generated file at an address an operator can paste into a server, and proving from outside this repository that the address answers. The address is a promise that cannot be withdrawn, so it is committed to last and once.
No due date•8/8 issues closedThe thing that makes the plugins installable at all. It reads the release artifacts of the declared source repositories and produces the manifest a Jellyfin server can read, deterministically and fail-closed.
No due date•15/15 issues closedLanguage, toolchain, layout, one CI entry point whose legs have real names, and a test harness that runs without a display and without elevation. Nothing after this milestone is allowed to introduce a test that cannot run in CI.
No due date•10/10 issues closedEvery architecture decision this board depends on, written down with its reasons before the thing that depends on it is built. A decision discovered later from reading code is not a decision, it is an accident that survived.
No due date•21/22 issues closed