From 6152fddc31af4a46951151bdffa62e3c0bb2bd0b Mon Sep 17 00:00:00 2001 From: Zoey Rose Date: Thu, 6 Aug 2026 15:34:44 +0000 Subject: [PATCH 1/2] docs: add contribution policy --- CONTRIBUTING.md | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 CONTRIBUTING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..450aab6 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,6 @@ +# Contributing + +Use a Conventional Commits pull-request title and run the validation commands +for each changed utility. Keep component-specific build tooling in its owning +repository, consume the released protocol package for packet-aware Python +tools, and preserve the GNU General Public License terms in `COPYING`. From a4a6456147b69c5897c932c4048f108f182a178b Mon Sep 17 00:00:00 2001 From: Zoey Rose Date: Thu, 6 Aug 2026 15:35:31 +0000 Subject: [PATCH 2/2] docs(license): clarify new tool licensing --- CONTRIBUTING.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 450aab6..aa35965 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -3,4 +3,7 @@ Use a Conventional Commits pull-request title and run the validation commands for each changed utility. Keep component-specific build tooling in its owning repository, consume the released protocol package for packet-aware Python -tools, and preserve the GNU General Public License terms in `COPYING`. +tools, and preserve the GNU General Public License terms in `COPYING`. A new, +independently authored utility may use the MIT License when feasible, but it +must carry a clearly scoped license and must not relicense the extracted GPL +utilities.