Title: [Previous Contributors Response Needed] Transition python-zeroconf to the Apache-2.0 License · Issue #1835 · python-zeroconf/python-zeroconf · GitHub
Open Graph Title: [Previous Contributors Response Needed] Transition python-zeroconf to the Apache-2.0 License · Issue #1835 · python-zeroconf/python-zeroconf
X Title: [Previous Contributors Response Needed] Transition python-zeroconf to the Apache-2.0 License · Issue #1835 · python-zeroconf/python-zeroconf
Description: Why python-zeroconf sits under a long list of Python projects. #1123 asked for a permissive license in 2023, and the same request has reached me many times since, mostly in private conversations with developers in the Matter and smart ho...
Open Graph Description: Why python-zeroconf sits under a long list of Python projects. #1123 asked for a permissive license in 2023, and the same request has reached me many times since, mostly in private conversations wi...
X Description: Why python-zeroconf sits under a long list of Python projects. #1123 asked for a permissive license in 2023, and the same request has reached me many times since, mostly in private conversations wi...
Opengraph URL: https://github.com/python-zeroconf/python-zeroconf/issues/1835
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Previous Contributors Response Needed] Transition python-zeroconf to the Apache-2.0 License","articleBody":"## Why\n\n`python-zeroconf` sits under a long list of Python projects. #1123 asked for a permissive license in 2023, and the same request has reached me many times since, mostly in private conversations with developers in the Matter and smart home space. When #1123 was raised I discussed it with jstasiak, the only other active maintainer at the time, and [they agreed](https://github.com/python-zeroconf/python-zeroconf/issues/1123#issuecomment-1411451210) a permissive license would be fine for their contributions; this issue proposes Apache 2.0, one of the two licenses that request named.\n\nThe LGPL's relinking requirement is deliberate: it guarantees users can swap in their own build of the library. That is easy for ordinary Python deployments and hard for frozen binaries and other sealed distributions (#276, #1363 and #1385 are all people shipping the library inside frozen executables, none of whom raised the license), so projects in those settings avoid the dependency or go without. In practice it mostly gets lumped into a blanket no-LGPL policy rather than weighed on its own, and projects only notice when it becomes a problem, so little of this is public; an example is OpenVoiceOS's license checks flagging the dependency (OpenVoiceOS/ovos-core#546). As maintainer, my call is that this protection is not worth the users it costs. The change has a price too: some contributors declined, and all of their surviving expression had to be removed and replaced (tracked below, down to a disclosed set of single-statement lines any implementation would share). This is the consent-based approach LLVM used, with declined contributions removed rather than relicensed; nothing already released changes license.\n\nTo be clear about what this is not (since it was asked below): I am self-employed, no company employs me or directs my work, all my time on this project is volunteer time given freely with as few strings attached as possible, and I do not profit from it. No company asked me for this, I personally deliberately accept no sponsorships of any kind to avoid even a potential misalignment (I do not have GitHub Sponsors enabled), and any legal review gets paid out of my own pocket. Nobody wants to be the person asking everyone for relicensing consent; I just happen to be the one maintaining the project now.\n\nWe likely will keep LGPL-2.1-or-later as an OR option for strict GPL-2.0-only compatibility. It is unlikely to be needed, but part of this is to avoid licensing discussions which take maintainer time, and friction wherever possible. Keeping the LGPL option needs no new consent, since those grants already exist; the consent being collected here is what enables the Apache option, and that is the same work either way.\n\n## The ask\n\nWe plan to migrate python-zeroconf from LGPL-2.1-or-later to [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0). To do this we need every contributor's permission to relicense their contributions.\n\nIf you are a contributor, please respond to this issue with something along the lines of:\n\n> I consent to my contributions to the python-zeroconf repository being relicensed under Apache 2.0 in place of the current LGPL license.\n\n(Future contributions arrive under both Apache 2.0 and LGPL-2.1-or-later via the notice on every pull request; we may keep the LGPL as an OR option so GPL-2.0-only projects can keep using the library. No ongoing obligation is created by consenting here.)\n\nConsent covers your commits authored on or before the date of your comment; later contributions are covered by the license notice posted on every pull request, and blame will be re-verified against consent dates before any switch. Declining is a normal option and is honored the way it has been so far: your surviving contributions are removed and replaced, nothing more. Each verified consent is also recorded in a ledger committed to the repository (username, commit emails, comment link, date), so the record cannot drift after the fact.\n\nFeel free to turn off notifications afterwards.\n\n## pyzeroconf heritage\n\npython-zeroconf exists thanks to pyzeroconf, created by Paul Scott-Murphy in 2003 and carried forward by William McBrine. This project would not be here without their work, and their names will stay in the project's history and acknowledgements regardless of the license. An initial `git blame` line audit understated what survives from that era; blame credits whoever moved code in the 2021 package split. An expanded audit with move and copy detection, run after @wmcbrine's comment below, found that a meaningful amount of Paul's 2009 expression was still in the tree, mostly docstrings, so he was added to the table. After both declined, all of that expression was removed and replaced through successive rounds of progressively stronger audits (blame, move aware blame, word n-grams, character level, fuzzy paraphrase, block level, AST structure, exact whole unit, arrangement comparison, and an adversarial re-audit); the removal history below lists every round. The original line by line findings are preserved in the expanded audit sections as a historical record.\n\nWe thank Paul Scott-Murphy, William McBrine, and Michał Górny for their historical contributions to the earlier LGPL licensed versions. (A fourth contributor asked not to be attributed; that request is honored in this acknowledgement. The consent tracking rows and audit records below necessarily keep usernames, since they are working records rather than attribution.) Their work has been removed from the current tree and will not be part of any Apache licensed release. This acknowledgement is a thank you, not an implication of consent to relicensing.\n\n## Contributors\n\nEveryone with surviving lines at current HEAD is listed below, sorted by count. The counts come from move and copy aware blame (`git blame -w -M -C -C -C`) over every tracked file except COPYING, get refreshed as rounds land, and the audit passes keep re-checking that nobody with surviving lines is missing. Contributors with nothing left in the tree and bot accounts are not listed.\n\nSmall mechanical changes (a dependency pin, a typo fix) are generally not copyrightable and would not need consent, but for now everyone with surviving lines is tracked, and anyone who does not reply gets evaluated case by case. Labels like below threshold, compelled or uncopyrightable anywhere in this issue are my read pending counsel review, not legal determinations.\n\n| Contributor | Active lines | Consent |\n| --------------- | -----------: | ------- |\n| @bdraco | 21,938 | ✅ |\n| @Rotzbua | 704 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5462300621) |\n| @jstasiak | 323 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5462270134) |\n| @agners | 213 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5465371892) |\n| @stephenrauch | 209 | |\n| @dtantsur | 135 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5573907204) |\n| @scop | 75 | |\n| @mattsaxon | 65 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5478214834) |\n| @pawlizio | 52 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5467104893) |\n| @apworks1 | 51 | |\n| @humingchun | 50 | |\n| @ibygrave | 50 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5463209000) |\n| @emontnemery | 47 | |\n| @bboe | 44 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5458732025) |\n| @azogue | 35 | |\n| @nocarryr | 29 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5486821065) |\n| @Tenebrosus3141 | 20 | |\n| @che0 | 19 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5467942853) |\n| @andrewbonney | 17 | |\n| @cdce8p | 14 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5464917296) |\n| @gjbadros | 14 | |\n| @inwotep | 14 | |\n| @schmittner | 9 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5467166859) |\n| @smcv | 8 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5469536878) |\n| @shenek | 7 | |\n| @jpbede | 6 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5460526155) |\n| @jacobtomlinson | 5 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5730191033) |\n| @foralesergi | 4 | |\n| @jmpcm | 4 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5568628585) |\n| @machinekoder | 4 | |\n| @stevencrader | 3 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5458645316) |\n| @lokesh2019 | 3 | |\n| @mtdcr | 3 | |\n| @bachp | 2 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5464361992) |\n| @marcosdiez | 2 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5467084050) |\n| @rima1881 | 2 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5458753986) |\n| @ZLJasonG | 2 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5568109941) |\n| @Pack3tL0ss | 1 | |\n| @PhilippSelenium | 1 | |\n| @xandey | 1 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5469168708) |\n| @devbanu | 1 | [✅](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5466504402) |\n| Giovanni Harting (no GitHub login resolvable from the commit) | 1 | |\n| @paulsm | 44\\* | ❌ [declined](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5463770593); all surviving expression removed and replaced (subject to audit), see the removal history and the line by line itemization in the paulsm expanded audit at the bottom of this issue |\n| @wmcbrine | 4\\* | ❌ [declined](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5463317251); all surviving expression removed and replaced (subject to audit), see the removal history and the line by line itemization in the wmcbrine expanded audit at the bottom of this issue |\n| @eshattow | 2\\* | [deferred to @wmcbrine](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5460600123), then [released all rights to his previous commits for reuse without attribution, stated as his form of protest](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5469107136), asking that his handle stay in this table; riscv64 wheel work reverted in #1841, workflow step names removed in #1852; only the two mechanical `ref:` expression fragments itemized in the eshattow expanded audit at the bottom of this issue remain under blame, and his branch switch step survives re-expressed in the maintainer's rework of that step (the branch selection expression inside it is the maintainer's own 2022 workflow line, restored) |\n| @mgorny | 0 | ❌ [declined](https://github.com/python-zeroconf/python-zeroconf/issues/1835#issuecomment-5460781566); his two contributions, a six line sdist include block and one Cython parameter type, are uncopyrightable configuration and type annotations; #1838 reverted them and #1839 re-added the include list re-keyed and the type annotation as written, since a one token type declaration has exactly one spelling |\n\n\\* the decliners' rows show the raw count a reader's own move and copy aware blame run produces, so nothing has to be reconciled against a zero: every one of these lines is a disclosed single statement (RFC constant assignments, attribute stores, bare raises, flag mask returns, two workflow fragments), itemized in the expanded audits below, with zero surviving prose. Some equally mechanical lines now blame to later commits because the delete and re-add rounds moved attribution; an exact text sweep counts several dozen such lines, 28 to 64 depending on the classifier, the same single statement class; the itemized lists in the expanded audits remain the authoritative inventory.\n\n## Pending consent audit\n\n\u003cdetails>\u003csummary>\u003cb>Surviving lines of the eighteen contributors who have not yet responded\u003c/b> (click to expand)\u003c/summary>\n\nMove and copy aware blame at current HEAD, non blank lines, so the case by case evaluation is already done if anyone does not respond by round close. Outreach runs on GitHub through September 2026; remaining non-responders will then be contacted directly at their commit email addresses. The dispositions are provisional plans for sustained silence, not determinations; any response supersedes them. Dispositions: \u003ci>substantive\u003c/i> means consent matters or a removal and replacement round is needed; \u003ci>small replacement\u003c/i> means a short delete and replace round like the earlier ones; \u003ci>below threshold\u003c/i> means the surviving lines are single statements, parameters or boilerplate that would be evaluated as falling under the originality threshold.\n\n| Contributor | Non blank lines | Where | Character | Disposition if unresponsive |\n| --- | ---: | --- | --- | --- |\n| @stephenrauch | 209 | `_utils/name.py` (the service name validator), `_services/types.py` (ZeroconfServiceTypes), `_protocol/outgoing.py`, test helpers in `test_init.py`, `.gitignore` | substantive validator and class logic plus test helpers | **substantive**; needs consent or a dedicated removal and replacement round |\n| @scop | 75 | test module logging boilerplate across seven files, one class statement line | idiomatic setup/teardown boilerplate | mostly below threshold |\n| @apworks1 | 51 | `record_manager.py` (one five line comprehension), browser/services tests | one src expression plus test code | small replacement |\n| @azogue | 35 | signature parameter lines in `_core`/`asyncio`, `test_name.py` tests | parameters and tests | small replacement |\n| @Tenebrosus3141 | 20 | context manager dunders in `browser.py`, tests | boilerplate dunders | below threshold to small replacement |\n| @gjbadros | 14 | packet offset bookkeeping in `outgoing.py` incl. one comment | small focused fix with one prose comment | small replacement |\n| @Pack3tL0ss | 1 | one docs link line | single line | below threshold |\n| @humingchun | 50 | `services/test_browser.py`, `test_core.py` | update event test code | small replacement |\n| @emontnemery | 47 | `test_protocol.py`, `test_handlers.py`, `test_cache.py` | test assertions across three files | small replacement |\n| @andrewbonney | 17 | `test_handlers.py`, question type plumbing in `_core`/`info`/`const` | parameters and tests | small replacement |\n| @inwotep | 14 | `test_handlers.py`, three lines in `query_handler.py` | small focused fix with tests | small replacement |\n| @shenek | 7 | `test_asyncio.py`, `test_core.py` | test code | small replacement |\n| @foralesergi | 4 | a comment block in `_utils/net.py` | prose comment | small replacement |\n| @machinekoder | 4 | `tests/services/test_types.py` | test code | small replacement |\n| @lokesh2019 | 3 | a comment in `_core.py` | prose comment | small replacement |\n| @mtdcr | 3 | `_services/info.py` | single statements | below threshold |\n| @PhilippSelenium | 1 | one `_utils/net.py` line | single line | below threshold |\n| Giovanni Harting | 1 | one `_utils/net.py` line | single line | below threshold |\n\n\u003c/details>\n\n## Removal history\n\n\u003cdetails>\u003csummary>\u003cb>Removal and hardening rounds, verified by successive adversarial audit passes\u003c/b> (click to expand)\u003c/summary>\n\nHow the audit passes were run, for the record: each is a fresh AI session commissioned by the maintainer, run against a clean clone with no access to any earlier pass's output, and instructed to re-derive every figure from the git object store and to disprove any claim here that it can. They are adversarial, not third party: no outside reviewer has examined this record yet. The full reports quote the removed expression and therefore cannot be committed to the repository without reintroducing it; whether and how to publish them is a question deferred to counsel. Every figure here is re-derivable by anyone from the public git object store with standard tooling (move and copy aware blame, n gram and shingle sweeps, difflib ratios, ordered LCS), and each round above names the commands and methods its pass used. The replacement text in the rounds below was likewise drafted with AI assistance under the maintainer's direction and review; the published similarity measurements are the operative test of the results, not the drafting method. Every threshold classification in this issue (below threshold, compelled, non expression) is the maintainer's position pending counsel review, not a legal determination. The removal rounds also stand on their own whatever happens to the relicense: if the effort stopped today, the tree would simply remain LGPL with the replacements in place.\n\nEach numbered round below was driven by a stronger audit than the last; deletions landed in revert PRs (five of them carried a handful of incidental insertion lines, one being the revert's own inverse hunk) and every replacement was freshly written and verified against the originals (two early replacements initially carried old text forward, the flag comments in #1844 and one test in #1853, and two code scaffolding lines re added by #1866 and #1873 carried old shapes; all were caught and removed by later rounds):\n\n1. #1841 reverted the riscv64 wheel work (eshattow); #1842 deleted the affected example file and test docstring\n2. #1843 deleted the blame attributed prose and code, #1844 replaced the behavior with fresh code\n3. #1847 deleted derivative docstrings that blame had misattributed to later editors, found by a blame independent n-gram audit; #1848 replaced them and recreated the two async examples\n4. #1849 deleted the readme fork note and seven short docstring lines (the loopback line appears in two classes); #1851 deleted sentence pattern echoes; #1850 added the fresh replacements\n5. #1852 deleted prose caught by a character level audit (four word class docstrings, test helper docstrings, a zunittest test string, workflow step names); #1853 replaced them\n6. #1854 deleted lines caught by a fuzzy paraphrase audit (production send docstrings, unregister docstrings, the remaining equality family); #1855 replaced them\n7. #1856 deleted two docstrings caught by a block level audit; #1857 replaced them; an AST structure comparison found no large scale structural matches in `src/` (its coverage of `tests/` was incomplete, see round 12; roughly twenty small bodies of two to seven statements (a loose upper bound; stricter metrics reproduce one to four) (field writes, flag mask tests, equality one liners, length prefixed string writes, short guard and dispatch bodies, the TTL formula) necessarily keep the 2009 statement sequence because the operation each performs admits essentially one expression, retained as compelled and confirmed by the fourth and fifth audits)\n8. #1858 deleted the two to four word verbatim docstrings caught by an exact whole unit audit with no length floor (accessor and entry docstrings, the unregister and listener family, the packets docstring); #1859 replaced them (an arrangement claim originally made here was later found to rest on a broken comparison and is corrected in round 12)\n9. a ninth audit of string literals and identifier names found nothing further in `src/`; the shared names there are the API classes (seven exported in `__all__`, the DNS record and codec classes importable and relied on by downstream projects) and RFC constant names, uncopyrightable short phrases and load bearing API surface (four 2009 test class names it missed were retired in round 12)\n10. #1860 removed the legacy 21 line banner from all 36 files (33 source modules and three test package inits) (the v0.14-wmcbrine title, the vestigial 2003/2014 copyright line, the original description prose, and the FSF boilerplate) and #1861 replaced it with a short LGPL header pointing at COPYING; with the banner gone the prose audits run with no exclusions and report zero shared five word prose runs with any pyzeroconf era blob; five word runs in code lines remain and are the mechanical matches documented in the expanded audits\n11. a 30 character audit over every tracked file, including the pxd files and changelog earlier passes skipped, found one last derivative docstring, removed in #1862 and replaced in #1863; every other match classified as mechanical, factual attribution, or the project name phrase\n12. an adversarial audit of all the claims above found that Paul's 2009 ZeroconfTest.py survived as a mechanically modernized port in test_init, test_protocol and test_core (same class names, method sequence, fixtures and assertions; blame lost the lineage at the 2021 test split, and the earlier structural audits did not cover tests). #1865 deleted sixteen test methods whole (the eleven the audit scored plus five sibling methods in the same 2009 descended families) and #1866 replaced the coverage with freshly authored bare pytest functions, retired the 2009 class names by converting the surviving class based tests to bare functions, and replaced the 2009 descended fixture values across the whole suite. The same audit corrected three earlier overclaims, reflected above: the working method order comparison shows `DNSRecord` and `DNSOutgoing` keep substantially the 2009 public method order and `_dns.py` keeps the 2009 class order, which is API surface and ordering rather than prose, noted here for transparency\n13. the adversarial auditor re-ran all eight of their audits against the round 12 tree and confirmed the revision holds: none of the 2009 test suite's def or class names remain (the public API class and exception names remain deliberately, per round 9: uncopyrightable short phrases and load bearing API surface), the ported fixtures are at zero occurrences, and the fresh tests are non derivative. Since that re-audit: #1867 reordered the classes and methods to a stated deterministic convention; by the third audit's reproducible metric (ordered LCS over shared snake cased method names) DNSRecord went 1.00 to 0.78 (0.75 on some audits' shared name sets) and DNSOutgoing 1.00 to 0.67, and the `_dns.py` class order went 8/8 to 7/8 shared name LCS, with the residual overlap being the alphabetical rule coinciding with the 2009 ordering of the shared DNSRecord accessor run (2009's layout is not near alphabetical in general); #1868 refreshed the stale `__author__` and `__maintainer__` metadata; #1869 replaced the remaining 2009 era path fixture values in the tests. A third adversarial re-audit against that tree confirmed all three PRs hold as described, with zero shared def or class names and only mechanical single statement matches remaining\n14. a second adversarial audit, run with a wider corpus (every intermediate pyzeroconf blob), confirmed every removal round as real and surfaced the last blind spots of blame driven scoping: two 2021 example files carrying wmcbrine's 2014 display block by copy paste, the readme usage example descended from the 2009 Browser.py, and the arbitrary DNSText repr truncation, all deleted whole in #1872 and replaced brand new in #1873 (the recreated readme example necessarily reuses five lines byte for byte: the import, three listener method signatures and the service info lookup call, compelled API surface matching the removed 2021 example and nothing in the pyzeroconf blobs); the ordering convention was extended to the remaining large classes in #1874; by the same third audit metric Zeroconf went 1.00 to 0.42, ServiceInfo 1.00 to 0.75 and DNSCache 1.00 to 0.75, while DNSIncoming and ServiceBrowser keep their two to three shared names in coincidental rule generated order\n\nOn replacement docstrings: five one sentence replacements measure 0.62 to 0.81 against the 2009 blobs; measured against the exact removed lines, nine sites reach 0.62 to 0.86, three of them sharing only the compelled 16 bit type name. The highest scoring lines were reworded again in #1886. A docstring that accurately names the fields a method compares can only be phrased so many ways; the position taken here is that such functional one liners are unprotectable however phrased, and the similarity is disclosed rather than claimed away. Retained as non expression and disclosed likewise: the const.py scalar constant block in numeric order (numeric order is the canonical arrangement of RFC values, and coincides with the 2009 arrangement, which is therefore unchanged), the `import zeroconf as r` idiom and the `Unit tests for zeroconf.X` docstring template across the test suite, and the compelled API surface itemized in the expanded audits.\n\n15. a third adversarial audit re-derived every claim from the object store, confirming the prose removal, the revert fidelity and the test replacement, and correcting the overstatements now fixed above; it surfaced the last structural port, the record display family in `_dns.py` whose hdr[type,class,name] layout, ?(x) fallback and ttl/remaining prefix reproduce the 2009 toString family, removed whole in #1878 and replaced in #1880 with an independently designed architecture: one module level formatter over structured field collections with label properties, no restored delegation chain, and the four public names kept as thin compatibility shims since API names are not copyrightable and downstream consumers depend on them, along with a 2021 comment paraphrase in the name compressor; the five surviving testname fixture stems it caught were replaced in #1881. Retained and disclosed per its inventory: the `generated` and `parsed` test variable idiom (a naming convention, not expression) and the compelled identifier surface\n\n16. a fourth adversarial audit confirmed all 205 expanded audit citations resolve exactly and every ordering metric reproduces, and found the last blind spot: the changelog, where semantic release had quoted mgorny's commit body verbatim outside blame's reach; #1884 replaces that entry and eshattow's PR title with neutral summaries, gives the pyproject authors metadata the #1868 treatment, renames the 2009 MyListener test class name, and rewords two remaining phrase echoes. #1885 hardens two governance items from the same review: the module headers now carry the modification notice LGPL section 2 calls for, and the pull request license notice no longer treats continuing a PR as consent for previous contributions, which now requires the explicit statement on this issue. The audit also corrected the eshattow record in the maintainer's favor (the qemu comment was the maintainer's own text he had copied), and authorship checks resolved every conditional it raised: the _fast_init family and test_interface_update are the current maintainer's own 2025 and 2026 work, and the test_init helper functions are Stephen Rauch's 2016 work, tracked in the table as pending consent. For clarity: the ordering rounds (#1867, #1874) only ever addressed arrangement; method bodies were addressed by the earlier delete and replace rounds, and the display subsystem was compared holistically (field selection is the record's own field set, while the fallback text, ttl presentation and composition mechanism all differ)\n\n17. a fifth adversarial audit verified all 205 citations, the 50 line blame count and the fixture zeroes, and caught regressions and gaps now fixed: #1880 had silently broken the ordering convention in two classes while rebuilding the display family, and a third, DNSRRSet, had never conformed (all three brought to the convention in #1886, with DNSRecord measuring 0.78 against the 2009 sequence under the audit's shared name matching, 0.62 to 0.70 when the renamed private suppression method is also counted, the spread depending on which private names fold in, and the timing and flag constant blocks alphabetized under the same rule); four docstrings scoring 0.65 to 0.86 against removed text were reworded and the known answer suppression docstring now cites RFC 6762 section 7.1; the similarity figures previously quoted in the #1856, #1867 and #1874 PR bodies came from earlier metrics and are superseded by the audit verified figures in this issue; and eight contributors with surviving lines had no table row, now added with daggered HEAD counts (pawlizio, humingchun, emontnemery, nocarryr, andrewbonney, inwotep, shenek, schmittner). Three blame attributed lines not previously itemized (a loop counter initialization and two test scaffolding lines) are noted in the expanded audit as part of the retained single statement set\n\n18. a sixth adversarial audit reproduced the 50 line blame count, the byte exact reverts and the zero prose result, and flagged the remaining residue and overstatements, all now addressed: the registration probe pacing loop, whose clock and counter skeleton descended from the 2009 checkService at a larger scale than the four statement bodies round 7 disclosed (simplified and renamed in #1888, which flattens the conflict loop, inverts the wait arithmetic and retires the 2009 blamed loop counter line, taking the itemized blame count from 50 to 49; the step sequence that remains implements the RFC 6762 section 8.1 probe and conflict handling behavior; the RFC compels the timing and the rename on conflict rather than the loop shape, which is retained and disclosed), the DNSOutgoing field initialization sequence at 0.83 token similarity (regenerated in #1889 under the alphabetical within groups rule, with the four section lists kept in RFC 1035 section 4.1 order), one five word prose run the round 17 reword had left in place, contradicting the round 10 zero claim at current HEAD (\"is at least half of\", reworded again in #1889), and the docstrings still measuring 0.60 to 0.65 against removed text (reworded or deleted in #1889; the ipaddress property and `_cache.py` docstrings the audits also scored are measured against removed 2021 text by the current maintainer, not pyzeroconf era text, and are retained (the ninth audit later traced one `_cache.py` line to a 2009 docstring; reworded in #1892, see round 21)). Ten more contributors with one to four surviving lines were added to the table with daggered HEAD counts. The audit's inventory of shared internal identifier names (method, local and constant names beyond the public API surface round 9 covered, including the preserved add_authorative_answer spelling) and the test_launch_and_close naming stem in test_core are retained and disclosed under the same rationale as the other idioms: names and naming conventions, not expression. The wmcbrine example line attribution below was also corrected: the registration and browser example lines were removed when #1843 deleted those files whole and #1844 recreated them, not in #1842\n\n19. a seventh adversarial audit re-derived every figure in this issue from the object store (the 49 line blame count, all 205 citations, the byte exact reverts, the banner and test method counts, and the ordering ratios) and confirmed them, while grading two sentences above as overstated, now reworded: #1888 is described as a simplification and rename rather than a restructure, since the step sequence it keeps is the RFC 6762 section 8.1 probe and conflict algorithm, and the #1844 constant table work is described as re-spacing and resorting, since the key to mnemonic pairs are RFC facts. Its remaining findings are addressed in #1890: the readme fork note had been quoting the 2009 project description sentence beyond plain attribution and no longer does, the launch and close test family (the naming stem round 18 disclosed as retained, plus a 2021 adapted unicast body that the round 12 claim of fresh replacements did not cover) was replaced with parametrized tests with fresh names (also retiring the rv.close() scaffolding line and taking the itemized blame count from 49 to 48), and the last docstring measuring 0.67 against removed text was reworded. The audit also noted 13 baseline prose lines the itemized paulsm list does not carry, covered by the 82 further docstrings sentence and all removed at HEAD, and confirmed that git ignored build output on the maintainer's disk (generated C files and an old docs build) still carried removed text; those artifacts are not in the tree and have been regenerated or deleted\n\n20. an eighth adversarial audit confirmed every count, revert fidelity and ordering ratio again, and its peripheral findings are now addressed: a stale `const.py` comment still describing the removed 2009 display fallback, one more docstring at 0.67 against a removed line, and two docstrings matching a 2009 docstring tail at up to 0.89 are fixed in #1891; the round 7 size bound is restated above as two to seven statements since four same shape bodies exceed four; round 9's wording now notes that eleven shared DNS class names are importable but not exported in `__all__`; the freshly written claim above carries the caveat about the two early replacements later rounds caught; the `_cache.py` docstrings scoring against the maintainer's own removed 2021 text are disclosed alongside the ipaddress ones; the shenek and five pending counts are refreshed to current HEAD; and the build output statement is now verified true for the checkout the removal rounds are made from: every git ignored generated file there (C files, bytecode caches, egg-info, ruff caches) was deleted and regenerated from the clean sources, with a sweep over all ignored files finding zero matches for the removed text (sibling clones used for the audit passes retain their own stale build output, which is not tree content). The 2009 era timing values (`_LISTENER_TIME`, `_REGISTER_TIME`, `_UNREGISTER_TIME`) are retained and disclosed as functional interop parameters rather than expression; changing them would change wire behavior\n\n21. a ninth adversarial audit re-derived the full record from the object store (all 205 citations, every count and ratio, both byte exact reverts, the 48 line blame list, zero surviving corpus prose outside the disclosed readme lines) and confirmed it, and its findings are addressed: the `_cache.py` lookup docstring, previously classed as scoring only against the maintainer's own removed 2021 text, traces to a 2009 docstring and is reworded in #1892, which also deletes the eight equality docstrings that still measured 0.60 to 0.69 rather than rewording them again; the round 13 alphabetical coincidence rationale is narrowed above to the DNSRecord accessor run; the round 14 brand new readme example claim now notes its five byte identical API surface lines; the round 20 disk statement is scoped to the checkout the rounds are made from; the paulsm expanded audit's 185 line figure is marked unreproduced with the itemized inventory remaining authoritative; and the numeric order disclosure now states that the constant block arrangement coincides with, and is therefore unchanged from, the 2009 arrangement\n\n22. a tenth adversarial audit reproduced the whole record again and corrected the record about itself in both directions: the 185 line figure reproduces exactly after all (the round 21 could-not-reproduce note was wrong and is fixed above), the recreated readme example shares five byte identical API surface lines rather than three, #1880 broke two ordering classes with a third never having conformed, and the probe loop disclosure no longer calls the loop shape compelled since the RFC compels the timing and rename behavior rather than the shape. Its code findings are addressed in three PRs: #1893 corrects the recursion available flag to the RFC 1035 value, retiring a wrong constant inherited from 2009 (and carried through the #1847 re-add) that no packet ever used; #1894 regenerates the DNSIncoming field initialization order under the same rule as #1889's DNSOutgoing work, folds the optional data payload of the two display compatibility shims into the modern formatter with fresh parameter names, aligns the TTL test double with the production formula, and drops a stale 2009 global from the lint allow list; the ServiceInfo request polling loop the audit flagged alongside is restructured the same way as the probe loop in #1895. Newly disclosed from its inventory: fourteen 2009 method names survive as underscore prefixed private helpers, a fuller similarity sweep finds further docstrings at 0.60 to 0.97 against the maintainer's own or consented era removed text (the highest being an RFC 6763 section 12 quotation), none pyzeroconf era, and the 2021 package split's module boundaries track the 2009 file's section order, retained as dependency driven architecture rather than prose\n\n23. an eleventh adversarial audit reproduced every count, revert and citation again and sharpened the summaries: the wmcbrine expanded audit headline now counts his readme fork note prose (8 lines, removed in #1849) alongside his 2 source prose lines; the retained lines footnote now carries the number an exact text sweep adds (roughly 28 single statement lines byte identical to 2009 text whose blame moved to later re-add commits); the round 7 category list gains the short guard and dispatch bodies it was missing; the #1856 PR body's zero matches sentence joins the earlier PR bodies as superseded by the audit verified figures here; and the one by-details docstring #1892 missed is reworded in #1896. Newly disclosed from its inventory: the freshly authored tests necessarily share the 2009 scenarios' build outgoing, add question and parse call sequence, which is the API's only spelling, and several of the maintainer's own 2021 sentences that the delete rounds swept out inside enclosing docstrings reappear in replacement docstrings, the maintainer's own text to reuse\n\n24. a twelfth adversarial audit reproduced the record again and caught the misses now fixed: the by-details docstring family had a third member, async_all_by_details, missed by rounds 21 and 23 and reworded in #1897, which also restructures the TXT record parse loop whose five statement walk was byte identical to the 2009 setText (the pxd locals move in the same commit and the CodSpeed benchmark referees the change) and replaces a query handler comment that both echoed a removed 2009 changelog line and described a ttl percentage check the code does not perform. Corrections to the record from the same audit are applied above: the eshattow row notes his branch switch step survives re-expressed alongside the two ref fragments, the byte identical unblamed count is stated as a classifier dependent range, the baseline figure parenthetical carries all three flag dependent reproductions, the DNSRecord private inclusive ratio is stated as a range, and the self test example's lineage is noted as resting on blame. Newly disclosed by name: the record parse dispatch in _read_record keeps the 2009 type order, retained under the round 7 dispatch body class\n\n25. a thirteenth adversarial audit reproduced every derivable number again and found nothing left to remove or replace, the first round for which that is true; every remaining finding is disclosure wording, applied above. Newly itemized: the RFC 6762 section 7.1 half ttl comparison survives re-typed at two `_dns.py` sites (the comparison the RFC itself specifies; the wmcbrine edit note above covered the deleted line, not the re-typed survivors); the 36 module headers' first sentence, the maintainer's 2022 project description, scores 0.74 to 0.81 against the 2009 title through the shared protocol name and belongs to the project name phrase class; three one sentence docstrings hold at 0.61 to 0.63 against removed text, disclosed under the standing position that functional one liners are unprotectable however phrased; DNSEntry's three shared names sit in rule generated 1.00 order like DNSIncoming and ServiceBrowser; and the regrouped DNSOutgoing initialization still measures 0.82 on the eleven shared fields, the grouped rule coinciding there. The 82 docstring figure is marked unit dependent and the baseline figure range is widened, both above\n\n26. a fourteenth adversarial audit reproduced the record and, like the thirteenth, found nothing in the tree to remove or replace. Its one actionable finding was environmental: the in place compiled extension binaries were untracked but not git ignored, closed by #1898 so stray staging can never commit build output. Newly itemized from its inventory: the nine ServiceListener callback signatures in tests/test_services.py match the 2009 listener interface parameter list for parameter list (the method names are snake cased, not the 2009 camelCase), the callback API's only spelling, joining the compelled API surface class. Wording fixes applied above: round 1 scoped to the one example file and test docstring #1842 actually deleted, round 10's 36 files broken out as 33 source modules plus three test package inits, the readme example note now states its five lines match the removed 2021 example and nothing in the pyzeroconf blobs, the DNSRecord figure carries its metric spread, and the recursion available note records the wrong value had been carried through the #1847 re-add\n\n27. a fifteenth adversarial audit reproduced the record with no contradicted claim, and a separate review of the process itself prompted the changes now visible in this body: the audit passes are described as what they are, maintainer commissioned adversarial AI sessions rather than independent review, with the method stated at the top of this section and the reports and scripts being published in the repository; the contributor table now shows one number system, current HEAD move and copy aware counts for everyone including the decliners' disclosed single statement remainders; the ask gained a consent cutoff, an explicit statement that declining is normal, and a repository ledger of verified consents; and the outreach timeline is stated. From the audit itself: the listener signature note is corrected to parameter list for parameter list, the branch selection expression in the eshattow note traces to the maintainer's own 2022 workflow line predating his commit, the 82 docstring figure is bracketed by a unit based count of about 113, the small bodies figure is marked a loose upper bound, and the five DNSRecord subclasses' 0.75 method order joins the arrangement disclosures\n\nEvery round above is merged or in review (plus #1883, which names the repr threshold constant).\n\nA note on scope, since outside reviews have raised it: two different kinds of changes appear in this history and they carry different claims. The removal rounds above deleted expression belonging to the contributors who declined and replaced it with freshly authored material; independence is claimed there and has held up across the adversarial audit passes. Separately, ordinary refactoring (converting test classes to functions, extracting helpers, reordering declarations, renaming fixtures) touched code belonging to consented or pending consent contributors; no independent authorship is claimed for that code, none is needed, and it remains under the current license with its authorship intact, tracked per contributor in the table and the pending consent audit above. Modernizing a pending contributor's test does not and is not meant to change whose work it is. Every finding from the adversarial audit passes is now either removed from the tree, replaced with rule generated or freshly written material, or disclosed above with the retained rationale; the summary comments on this issue were edited to match what a reader's own blame run produces.\n\nWhat remains from that era: the factual attribution line and LGPL statement in the readme (replaced by the relicense itself) and single statement textual matches any implementation would share (including a test double in test_browser.py that re-implements the TTL expiry arithmetic, the same mechanical class as the production formula). The `__author__` metadata line was refreshed in #1868 and the declaration ordering was regenerated from a stated convention in #1867, so neither remains.\n\n\u003c/details>\n\n## Expanded audits\n\nThe two blocks below are the original findings at commit f491259 (the pre squash head of #1839; its tree content landed as 6b2a040, which is where the line links resolve for anyone auditing from a clone), kept as a historical record; every prose line listed has since been removed by the rounds above.\n\n#### paulsm expanded audit\n\n\u003cdetails>\u003csummary>\u003cb>paulsm expanded audit: exact surviving lines (85 prose, 85 textual matches)\u003c/b>\u003c/summary>\u003cul>\u003cli>the audit counted 185 lines (audits reproduce 183 to 199 non blank body lines depending on the blame flags, file scope and banner exclusion rule; the itemized lines below plus the noted prose lines are the authoritative inventory); outside the header, 85 lines are docstrings and comments, his actual surviving prose (ten of them constant assignment lines counted for their trailing comments, one a bare docstring delimiter), and 85 lines are single statement textual matches (assignments, raises, constant and dictionary table entries, class statement lines and short return expressions) that any implementation would share and are listed only for completeness; all trace to \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/commit/c3a39f874a5c10e91ee2315271f13ae74ee381fd\">the 2009 root commit\u003c/a>\u003c/li>\u003cli>\u003cb>docstrings and comments (85 lines, all removed in #1843 and replaced with fresh text in #1844):\u003c/b>\u003cul>\u003cli>\u003ccode>const.py\u003c/code> (11): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/const.py#L111\">L111\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/const.py#L114-L116\">L114-L116\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/const.py#L119-L121\">L119-L121\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/const.py#L123-L125\">L123-L125\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/const.py#L158\">L158\u003c/a>\u003c/li>\u003cli>\u003ccode>_dns.py\u003c/code> (24): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L91\">L91\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L96\">L96\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L100\">L100\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L125\">L125\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L186\">L186\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L193-L194\">L193-L194\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L202-L203\">L202-L203\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L207-L208\">L207-L208\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L222\">L222\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L237\">L237\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L241\">L241\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L280\">L280\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L284\">L284\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L299\">L299\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L355\">L355\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L394\">L394\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L410\">L410\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L438\">L438\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L454\">L454\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L502\">L502\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L509\">L509\u003c/a>\u003c/li>\u003cli>\u003ccode>_core.py\u003c/code> (13): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_core.py#L153\">L153\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_core.py#L155-L156\">L155-L156\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_core.py#L166\">L166\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_core.py#L324\">L324\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_core.py#L331\">L331\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_core.py#L337\">L337\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_core.py#L657-L658\">L657-L658\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_core.py#L697\">L697\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_core.py#L719\">L719\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_core.py#L811\">L811\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_core.py#L829\">L829\u003c/a>\u003c/li>\u003cli>\u003ccode>_protocol/outgoing.py\u003c/code> (7): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/outgoing.py#L148\">L148\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/outgoing.py#L152\">L152\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/outgoing.py#L163\">L163\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/outgoing.py#L244\">L244\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/outgoing.py#L332\">L332\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/outgoing.py#L344\">L344\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/outgoing.py#L418\">L418\u003c/a>\u003c/li>\u003cli>\u003ccode>_services/info.py\u003c/code> (2): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_services/info.py#L425\">L425\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_services/info.py#L454\">L454\u003c/a>\u003c/li>\u003cli>\u003ccode>_listener.py\u003c/code> (6): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_listener.py#L58-L60\">L58-L60\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_listener.py#L62\">L62\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_listener.py#L243-L244\">L243-L244\u003c/a>\u003c/li>\u003cli>\u003ccode>_protocol/incoming.py\u003c/code> (3): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/incoming.py#L75\">L75\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/incoming.py#L107\">L107\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/incoming.py#L450\">L450\u003c/a>\u003c/li>\u003cli>\u003ccode>asyncio.py\u003c/code> (5): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/asyncio.py#L138\">L138\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/asyncio.py#L140\">L140\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/asyncio.py#L155\">L155\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/asyncio.py#L244-L245\">L244-L245\u003c/a>\u003c/li>\u003cli>\u003ccode>_handlers/record_manager.py\u003c/code> (4): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_handlers/record_manager.py#L56\">L56\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_handlers/record_manager.py#L67\">L67\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_handlers/record_manager.py#L80\">L80\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_handlers/record_manager.py#L174\">L174\u003c/a>\u003c/li>\u003cli>\u003ccode>_utils/net.py\u003c/code> (4): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_utils/net.py#L64\">L64\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_utils/net.py#L215-L217\">L215-L217\u003c/a>\u003c/li>\u003cli>\u003ccode>_cache.py\u003c/code> (3): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_cache.py#L261-L262\">L261-L262\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_cache.py#L306\">L306\u003c/a>\u003c/li>\u003cli>\u003ccode>_services/browser.py\u003c/code> (3): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_services/browser.py#L672\">L672\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_services/browser.py#L767\">L767\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_services/browser.py#L771\">L771\u003c/a>\u003c/li>\u003c/ul>\u003c/li>\u003cli>\u003cb>textual matches with no independent expression (85 lines, retained as uncopyrightable; the \u003ccode>const.py\u003c/code> tables were nonetheless re-spaced and resorted in #1844 with the nonstandard quada name dropped, the key to mnemonic pairs themselves being RFC facts; blame additionally attributes a loop counter initialization in \u003ccode>_core.py\u003c/code> and two test scaffolding lines, \u003ccode>rv.close()\u003c/code> and \u003ccode>import unittest\u003c/code>, to the 2009 tree, in the same single statement class):\u003c/b>\u003cul>\u003cli>\u003ccode>const.py\u003c/code> (48): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/const.py#L127-L134\">L127-L134\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/const.py#L137-L154\">L137-L154\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/const.py#L156\">L156\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/const.py#L162-L165\">L162-L165\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/const.py#L171-L187\">L171-L187\u003c/a>\u003c/li>\u003cli>\u003ccode>_dns.py\u003c/code> (14): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L187\">L187\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L209\">L209\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L238\">L238\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L246\">L246\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L300\">L300\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L311\">L311\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L359\">L359\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L414\">L414\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L455\">L455\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L460\">L460\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L494-L497\">L494-L497\u003c/a>\u003c/li>\u003cli>\u003ccode>_core.py\u003c/code> (5): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_core.py#L544\">L544\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_core.py#L550\">L550\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_core.py#L614\">L614\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_core.py#L669\">L669\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_core.py#L674\">L674\u003c/a>\u003c/li>\u003cli>\u003ccode>_protocol/outgoing.py\u003c/code> (11): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/outgoing.py#L121\">L121\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/outgoing.py#L125\">L125\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/outgoing.py#L149\">L149\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/outgoing.py#L160\">L160\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/outgoing.py#L164\">L164\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/outgoing.py#L202\">L202\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/outgoing.py#L246-L248\">L246-L248\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/outgoing.py#L257\">L257\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/outgoing.py#L343\">L343\u003c/a>\u003c/li>\u003cli>\u003ccode>_services/info.py\u003c/code> (5): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_services/info.py#L230\">L230\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_services/info.py#L244-L246\">L244-L246\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_services/info.py#L1103\">L1103\u003c/a>\u003c/li>\u003cli>\u003ccode>_protocol/incoming.py\u003c/code> (2): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/incoming.py#L147\">L147\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/incoming.py#L151\">L151\u003c/a>\u003c/li>\u003c/ul>\u003c/li>\u003cli>beyond these lines, 82 of his 2009 docstrings survived verbatim or lightly edited at audit time (baseline blame also reaches 13 prose lines in \u003ccode>asyncio.py\u003c/code>, \u003ccode>_services/info.py\u003c/code> and \u003ccode>_core.py\u003c/code>, plus one test docstring in \u003ccode>tests/test_protocol.py\u003c/code>, that the itemized list above does not carry; line based sweeps count roughly 150 such lines and unit based ones about 113, the definitions differing; all are gone at HEAD); they were removed across #1847, #1849, #1851, #1852, #1854, #1856, #1858 and #1862, and the round eight arrangement audit confirmed no class or method ordering from his tree remains\u003c/li>\u003cli>his original self test example script was deleted whole in #1842 (lineage by blame; its text had drifted to near zero similarity by then)\u003c/li>\u003c/ul>\u003c/details>\n\n#### wmcbrine expanded audit\n\n\u003cdetails>\u003csummary>\u003cb>wmcbrine expanded audit performed due to non-consent: exact surviving lines (2 src prose, 10 edits, 5 header lines, plus the 8 line readme fork note removed in #1849)\u003c/b>\u003c/summary>\u003cul>\u003cli>the audit traced 12 substantive lines outside the shared header, 5 header lines replicated in 36 files, and a few test and example fragments; only 2 source lines are his own prose (his other prose, the 8 line readme fork note, was removed in #1849, round 4), the rest are edits to 2009 text or artifacts, classified below\u003c/li>\u003cli>\u003cb>his own prose (2 lines, removed in #1843):\u003c/b>\u003cul>\u003cli>\u003ccode>_protocol/incoming.py\u003c/code> (2): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/incoming.py#L451-L452\">L451-L452\u003c/a>, the skip unknown record payloads comment, from \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/commit/488de8826ddd58646358900d057a4a1632492948\">488de882\u003c/a>\u003c/li>\u003c/ul>\u003c/li>\u003cli>\u003cb>edits and textual matches with no independent expression (10 lines; the surviving 2009 wording in \u003ccode>_dns.py\u003c/code> and \u003ccode>incoming.py\u003c/code> was removed in #1843 and replaced in #1844, the rest retained as uncopyrightable):\u003c/b>\u003cul>\u003cli>\u003ccode>_dns.py\u003c/code> (1): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_dns.py#L204\">L204\u003c/a>, collapsed the 2009 \u003ccode>if/return 1/return 0\u003c/code> into one \u003ccode>return\u003c/code>, the predicate is verbatim 2009 line 299, from \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/commit/173350e415e66c9629d553f820677453bdbe5724\">173350e4\u003c/a> (the tenth audit notes two origin over attributions in this list: the registration example's service name string is Paul's 2009 test fixture, only re-wrapped by 0f3b413b, and the offset increment already appeared three times in the 2009 tree)\u003c/li>\u003cli>\u003ccode>_protocol/incoming.py\u003c/code> (3): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/incoming.py#L317-L318\">L317-L318\u003c/a> line wrapping of a 2009 sentence from \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/commit/e5d930bb681f5544827fc0c9f37daa778dec5930\">e5d930bb\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/incoming.py#L453\">L453\u003c/a> \u003ccode>self.offset += length\u003c/code> from \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/commit/b8baed3a2876c126cac65a7d95bb88661b31483c\">b8baed3a\u003c/a>\u003c/li>\u003cli>\u003ccode>_protocol/outgoing.py\u003c/code> (3): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/outgoing.py#L240-L241\">L240-L241\u003c/a> simplified the 2009 pack call from \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/commit/e814dd1e6848d8c7ec03660d347ea4a34390c37d\">e814dd1e\u003c/a>, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_protocol/outgoing.py#L266\">L266\u003c/a> a blank line inside a 2021 docstring, blame artifact\u003c/li>\u003cli>\u003ccode>_utils/net.py\u003c/code> (1): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/_utils/net.py#L219\">L219\u003c/a>, truncation of a longer 2009 comment from \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/commit/eee7196626773eae2dc0dc1a68de03a99d778139\">eee71966\u003c/a>, the surviving words are 2009 text\u003c/li>\u003cli>\u003ccode>const.py\u003c/code> (2): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/src/zeroconf/const.py#L58-L59\">L58-L59\u003c/a>, removed trailing semicolons from the 2009 port constants, from \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/commit/f6615a9d7632f3510d2f0a36cab155ac753141ab\">f6615a9d\u003c/a>\u003c/li>\u003c/ul>\u003c/li>\u003cli>\u003cb>tests and examples (four itemized lines plus blanks: the test docstring removed in #1842; the registration and browser example lines removed when #1843 deleted those files whole and #1844 recreated them; the two async example files were the ones deleted whole in #1847 and recreated fresh in #1848):\u003c/b>\u003cul>\u003cli>\u003ccode>tests/test_init.py\u003c/code> (removed in #1842): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/tests/test_init.py#L1\">L1\u003c/a> docstring, from \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/commit/0884d6a56afc6fb559b6c90a923762393187e50a\">0884d6a5\u003c/a>\u003c/li>\u003cli>\u003ccode>examples/registration.py\u003c/code> (2): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/examples/registration.py#L3\">L3\u003c/a> docstring, \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/examples/registration.py#L37\">L37\u003c/a> service name string, from \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/commit/0884d6a56afc6fb559b6c90a923762393187e50a\">0884d6a5\u003c/a> and \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/commit/0f3b413b269f8b95b6f8073ba39d11f156ae632c\">0f3b413b\u003c/a>\u003c/li>\u003cli>\u003ccode>examples/browser.py\u003c/code> (1): \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/examples/browser.py#L33\">L33\u003c/a> \u003ccode>if info:\u003c/code>, from \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/commit/0a05f423ad591454a25c515d811556d10e5fc99f\">0a05f423\u003c/a>\u003c/li>\u003c/ul>\u003c/li>\u003cli>\u003cb>shared header (5 of 21 lines, in 36 files):\u003c/b> lines 1, 2, 5, 19, 20, from \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/commit/2a000c589302147129eed990c842b38ac61f7514\">2a000c58\u003c/a> (the \u003ccode>v0.14-wmcbrine\u003c/code> title and copyright line), \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/commit/4e396025ed666775973d54a50b69e8f635e28658\">4e396025\u003c/a> (FSF address), \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/commit/21d7c950f50827bc8ac6dd18fb0577c11b5cefac\">21d7c950\u003c/a> (one reflow); the whole banner was removed in #1860 and replaced with a short license header in #1861\u003c/li>\u003cli>context: his 51 commits (2008 to 2014) were mostly maintenance passes; the behavioral fixes have all since been replaced\u003c/li>\u003c/ul>\u003c/details>\n\n#### eshattow expanded audit\n\n\u003cdetails>\u003csummary>\u003cb>eshattow expanded audit: 0 surviving prose lines (riscv64 wheel work removed in #1841, workflow step names removed in #1852; only mechanical ref fragments remain)\u003c/b>\u003c/summary>\u003cul>\u003cli>the audit traced 17 non blank surviving lines, all in \u003ccode>.github/workflows/ci.yml\u003c/code>; the one line originally counted as his prose turned out to be the maintainer's own text (see below), the rest are mechanical workflow configuration\u003c/li>\u003cli>\u003cb>removed in #1841:\u003c/b> the riscv64 wheel matrix and its comment, dropped as a clean revert of the introducing commit\u003c/li>\u003cli>\u003cb>previously attributed as his prose (1 line, now removed; the fourth audit traced the qemu comment to the maintainer's own 2025 commit 8fbbe41, which he had copied, so no prose of his own ever survived):\u003c/b> \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/.github/workflows/ci.yml#L321\">L321\u003c/a>, the qemu runner comment, from \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/commit/8a7dff9ae39f58adfb2a7fe5ab6955864e9b363a\">8a7dff9a\u003c/a>\u003c/li>\u003cli>\u003cb>his step name labels (2 lines, removed in #1852 and named fresh in #1853):\u003c/b> the two Create local branch name step names at \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/.github/workflows/ci.yml#L190\">L190\u003c/a> and \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/.github/workflows/ci.yml#L225\">L225\u003c/a>, from \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/commit/bc8ec8d59d875522f75901644d423d30d803a030\">bc8ec8d5\u003c/a>\u003c/li>\u003cli>\u003cb>mechanical configuration (retained as uncopyrightable):\u003c/b> \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/.github/workflows/ci.yml#L322-L333\">L322-L333\u003c/a> the twelve riscv64 wheel matrix entries (removed with #1841 regardless) and the \u003ccode>ref:\u003c/code> expression fragments at \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/.github/workflows/ci.yml#L188-L189\">L188-L189\u003c/a> and \u003ca href=\"https://github.com/python-zeroconf/python-zeroconf/blob/f49125922b5348e1703a2a345aaf01555e208088/.github/workflows/ci.yml#L223-L224\">L223-L224\u003c/a>, workflow syntax any implementation would share\u003c/li>\u003c/ul>\u003c/details>\n\n\n\n\n\n","author":{"url":"https://github.com/bdraco","@type":"Person","name":"bdraco"},"datePublished":"2026-08-28T22:58:56Z","url":"https://github.com/python-zeroconf/python-zeroconf/issues/1835"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:63b27da4-cf01-4298-e6e1-b9e42a9976ac |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | A43A:1FDC76:5D41:7C4B:6B007D31 |
| html-safe-nonce | 96211dc5f0db01d122859f0b1bf7ed63221d89c27766380b96dce94647f0a6a4 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBNDNBOjFGREM3Njo1RDQxOjdDNEI6NkIwMDdEMzEiLCJ2aXNpdG9yX2lkIjoiMzM0MDM1NjA5NDA4MDg3NTgyNSIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 0e72f962508c1b83e91c88873f570d1dcd35682d89845dbc1a8845ab47bd984b |
| hovercard-subject-tag | issue:5282980979 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/python-zeroconf/python-zeroconf/1835/issue_layout |
| twitter:image | https://opengraph.githubassets.com/01083afcb3b48952eec461b5ccd232169961272992f7c2440a27c6299e715fa5/python-zeroconf/python-zeroconf/issues/1835 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/01083afcb3b48952eec461b5ccd232169961272992f7c2440a27c6299e715fa5/python-zeroconf/python-zeroconf/issues/1835 |
| og:image:alt | Why python-zeroconf sits under a long list of Python projects. #1123 asked for a permissive license in 2023, and the same request has reached me many times since, mostly in private conversations wi... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | bdraco |
| hostname | github.com |
| expected-hostname | github.com |
| None | 82c186f13e104004ab7bdb779f3195e59dd38bfde531aaa74b76470fc2462b83 |
| turbo-cache-control | no-preview |
| go-import | github.com/python-zeroconf/python-zeroconf git https://github.com/python-zeroconf/python-zeroconf.git |
| octolytics-dimension-user_id | 120192235 |
| octolytics-dimension-user_login | python-zeroconf |
| octolytics-dimension-repository_id | 21548731 |
| octolytics-dimension-repository_nwo | python-zeroconf/python-zeroconf |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 21548731 |
| octolytics-dimension-repository_network_root_nwo | python-zeroconf/python-zeroconf |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | d1bc2aa1939001689f5ce935982c10a6138f745c |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width