Thanks everyone — I think we have converged, and the answer is the smaller one.
At this stage, both bodies simply hosting the configuration values is the right scope. No skills move. ComDev owns the TLP value set, the Incubator owns the podling one, and Magpie resolves them with project-level overrides on top. Rich — yes, governance/TLP_governance_defaults.yaml works. If the shape needs to change once Magpie consumes it (the per-action bodies I owe Justin), that is a PR to apache/comdev, not a new discussion. On the release skills: the Incubator already has one skill that Magpie consumes from trusted sources (releasecheck, pinned at releasecheck-0.5.1), and that is good enough to experiment with. Let us see how it behaves in practice rather than designing ownership for divergence we have not met yet. My goal for the coming months is to get Magpie more widely used; if real podling-vs-TLP divergence shows up then, we come back to this with evidence instead of speculation. Dave — same answer on where the licence checker lives: leaving it where it is for now is the cheapest way to find out whether it needs to move. I will close the tracking issues on both sides. They can be reopened the moment the divergence is real. Best regards, Jarek Potiuk -- Drafted with AI assistance (Claude Opus 5) and reviewed before sending. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
