You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
I19.1 · Design: providers, sources, kinds and versions #172
As a contributor, I want one written plan for providers, sources, kinds and versions, so the refactor lands as small safe PRs and I know which kind a new source is before I write it.
Subtasks
docs/design/plugins.md: the current state (every duplicated step as file:function), the target model (provider → sources → kind / layer / category / versions), the ListVersions / ReadAt / Extract interfaces as Go sketches, the core/ and plugins/<kind>/ layout
Ids: provider/source, and how today's ids stay as aliases
Every version: where versions come from (git tags, releases, PyPI, npm, Go proxy, Maven, feed dates, Wayback at a date), ordering per ecosystem, and how a range is backfilled
The migration order as small PRs, each saying how it keeps the goldens byte-identical (or, for the contract PR, why they change)
Where I18's infrastructure sources fit (no Kubernetes or Terraform kind)
Open questions for the maintainers
Acceptance criteria
The doc names every duplicated step it removes, with file and function
Every existing plugin is mapped to a provider, a source id, a kind, a layer and a category
A maintainer has approved the model before I19.2 starts
changed the title [-]I19.1 · Design: one plugin pipeline, one source of truth[/-][+]I19.1 · Design: providers, sources, kinds and versions[/+]on Nov 20, 2026
Activity
[-]I19.1 · Design: one plugin pipeline, one source of truth[/-][+]I19.1 · Design: providers, sources, kinds and versions[/+]adssib commentedon Nov 20, 2026
Done: the design is developer-handbook
overview/redesign.md(merged via developer-handbook#36).