Decision D16 — plugin licensing — is open, and it gates publishing the declarative format as stable.
Why now rather than later
D16 records that GPLv3 answers the derivative-work question differently for each of §3.10's three plugin forms, and that this must be answered before an ecosystem exists, not after: a term introduced later cannot be applied to plugins already written.
D16 explicitly does not block FR-PLG-2, which is why the declarative format could ship. It blocks publishing that format to third parties as a stable interface.
What closes this
A decision recorded in requirements.md, covering each of the three plugin forms separately. Not code.
Related
#15 — the §3.10 / §7 contradiction, which should probably be settled in the same sitting.
**Decision D16 — plugin licensing — is open**, and it gates publishing the declarative format as stable.
## Why now rather than later
D16 records that GPLv3 answers the derivative-work question **differently for each of §3.10's three plugin forms**, and that this must be answered *before* an ecosystem exists, not after: a term introduced later cannot be applied to plugins already written.
D16 explicitly does **not** block FR-PLG-2, which is why the declarative format could ship. It blocks publishing that format to third parties as a stable interface.
## What closes this
A decision recorded in `requirements.md`, covering each of the three plugin forms separately. Not code.
## Related
- #15 — the §3.10 / §7 contradiction, which should probably be settled in the same sitting.
- #16 — the plugin host, blocked on both.
See `docs/outstanding.md` §1.
Blocks#16, for publishing the format as stable. Does not block FR-PLG-2, which is why the declarative format could ship. Settle alongside#15.
**Blocks** #16, for publishing the format as stable. Does **not** block FR-PLG-2, which is why the declarative format could ship.
**Settle alongside** #15.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Decision D16 — plugin licensing — is open, and it gates publishing the declarative format as stable.
Why now rather than later
D16 records that GPLv3 answers the derivative-work question differently for each of §3.10's three plugin forms, and that this must be answered before an ecosystem exists, not after: a term introduced later cannot be applied to plugins already written.
D16 explicitly does not block FR-PLG-2, which is why the declarative format could ship. It blocks publishing that format to third parties as a stable interface.
What closes this
A decision recorded in
requirements.md, covering each of the three plugin forms separately. Not code.Related
See
docs/outstanding.md§1.Blocks #16, for publishing the format as stable. Does not block FR-PLG-2, which is why the declarative format could ship.
Settle alongside #15.
Defers with §3.10 (1da91b7). To be answered before the format is published as stable, which is now a post-v1 event.