>  They don't tell you whether a bundled dependency's license is
compatible, whether NOTICE says the right thing, or whether a file with a
correct-looking header is genuinely under that license. A release can pass
all of them and still ship GPL-licensed code, this has happened more than
once.

I want to challenge that. If you can articulate it in instructions to
someone as to what to look for, it can be automated IMO. This is precisely
the esoteric knowledge that is best codified ideally in deterministic
tooling, or reusable documentation (e.g. skills or MCP) that LLMs can help
interpret for a human. I don't claim that this will be fool proof, but
missings things should just happen once, and then the collective tooling
and documentation updated to prevent it happening again - and the entire
Apache community benefitting - not just a single project. I think this
would make the onboarding experience of a podling a lot clearer too since
there would be a clearwr bar to clear.


On Thu, Sep 10, 2026, 2:18 PM Paul King <[email protected]> wrote:

> For completeness, it also added:
> Remaining soft items, unchanged: the SDK zip is 116.5 MB against
> Infra's 100 MB recommendation, and jackson-core's shaded
> FastDoubleParser and Schubfach stay the deliberate exception.
>
> On Fri, Sep 11, 2026 at 7:16 AM Paul King <[email protected]> wrote:
> >
> > Another example below of GroovyPolicyMCP used by Claude. As other's
> > have said, it doesn't replace further human and adhoc analysis.
> >
> > Cheers, Paul.
> >
> > ----
> >
> > GroovyPolicyMCP analysis:
> >
> > **Verdict: 6.0.0-RC-2 is clean. I would vote +1.** Every check on the
> > release checklist passed including signatures.
> >
> > **Tag and source**
> >
> > - The annotated tag on gitbox resolves to commit
> > 760601d45f652b90950f5dd3ba4e60f201691e11, matching the vote email, and
> > its parent is on origin/master.
> > - The source zip is identical to `git archive` at the tag. The only
> > absent files are the deliberate omissions: benchmark, the perf
> > dashboard, wrapper, governance docs, CI configs, and the ABI surface.
> > - No compiled code or archives in the source zip. RAT passes at the
> > tag. Version properties carry no SNAPSHOT.
> > - The JIRA changelog lists 44 unique issues, as the email says.
> >
> > **Signatures and checksums**
> >
> > | Location                           | Artifacts | Signed by
> > 6A65176A0FB1CD0B | Checksums                           |
> > | ---------------------------------- | --------- |
> > -------------------------- | ----------------------------------- |
> > | dist.apache.org zips               | 4         | 4 good
> >        | SHA-256 match                       |
> > | Nexus staging orgapachegroovy-1122 | 297       | 297 good
> >        | md5, sha1, sha256, sha512 all match |
> >
> > **LICENSE and NOTICE**
> >
> > - Binary and SDK zips: 18 of 18 license pointers resolve, no
> > unreferenced texts, NOTICE dated 2003-2026 with all the upstream
> > credits. All 88 bundled third-party jars covered, the same set as
> > today's snapshot.
> > - Docs zip: 4 of 4 pointers resolve.
> > - All 167 staged jars carry META-INF LICENSE and NOTICE with every
> > pointer resolving. Raw, shaded, grooid, sources and groovy-all-sources
> > declarations match their content. Sources, javadoc and groovydoc jars
> > contain no classes.
> > - The core, grooid and groovy-test-grooid jars inside the binary zip
> > are byte-identical to the staged ones, as are all 39 module jars in
> > lib/.
> > - All 43 poms declare the license, none reference non-Groovy SNAPSHOT
> > dependencies.
> >
> > **SBOMs** show 729 of 729 components licensed.
> >
> > On Wed, Sep 9, 2026 at 4:18 PM Paul King <[email protected]> wrote:
> > >
> > > On Wed, Sep 9, 2026 at 3:30 PM tison <[email protected]> wrote:
> > > >
> > > > > To me this is all automateble. Why can't ASF have a blessed &
> centrally
> > > > > maintained way to check different file types at least as it
> pertains to
> > > > > licenses?
> > > >
> > > > It would be more than generous if you could give some concrete ideas
> > > > or a (referred) implementation.
> > >
> > > I find the various Gradle license plugins combined with a PolicyMCP
> > > goes a long way. Justin did various versions of a Python PolicyMCP
> > > implementation, I mostly use GroovyPolicyMCP (I have both normal
> > > Groovy and native versions, the latter faster than I can get combining
> > > Python/Rust).
> > >
> > > This is the kind of detail it gave on a recent Ivy release vote:
> > >
> > > **The jQuery Treeview plugin isn't listed in LICENSE.** Both zips
> > > bundle `jquery.treeview.js` (`asciidoc/js/` in src, `doc/js/` in bin).
> > > It's Treeview 1.2, copyright Jörn Zaefferer and Myles Angell,
> > > dual-licensed MIT/GPL — a separate work from jQuery core. The
> > > `LICENSE` file has a section for jQuery (John Resig) but nothing for
> > > Treeview, so it doesn't fully account for the package's exact content.
> > > The fix is a short "License for jQuery Treeview plugin" section taking
> > > the MIT option.
> > >
> > > One example from a recent Commons Collections release:
> > >
> > > 2. commons-collections4-4.6.0-javadoc.jar has no META-INF/LICENSE.txt
> or
> > >    NOTICE.txt, unlike the other jars. It carries the JDK's legal/
> directory
> > >    instead, where legal/LICENSE is the GPLv2 text (with Classpath
> Exception
> > >    via ASSEMBLY_EXCEPTION). Relatedly, the binary distribution bundles
> > >    jQuery 3.7.1 and jQuery UI (MIT) under apidocs/script-dir/, which
> the
> > >    root LICENSE.txt does not mention, though apidocs/legal/jquery.md
> and
> > >    jqueryUI.md are present. This is inherited from stock javadoc and is
> > >    common across ASF Java projects; the source release is unaffected.
> > >
> > > These happen to be using Claude but you can use your favourite agent.
> > >
> > > Paul.
> > >
> > > > Best,
> > > > tison.
> > > >
> > > > Stefan Krawczyk <[email protected]> 于2026年9月9日周三 13:21写道:
> > > > >
> > > > > To me this is all automateble. Why can't ASF have a blessed &
> centrally
> > > > > maintained way to check different file types at least as it
> pertains to
> > > > > licenses? I think the majority of this can be 100% deterministic
> code
> > > > > without the need for LLMs as well...
> > > > >
> > > > > On Tue, Sep 8, 2026, 2:52 AM Jarek Potiuk <[email protected]>
> wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > Another option is to distribute MCP server publishing and
> SKILL/Agents
> > > > > > marketplaces. Or, as JBO mentioned, use CLIs and remote APIs.
> > > > > >
> > > > > > MCP servers are often (more often than not) not actual remote
> servers that
> > > > > > need to run "somewhere else". Many run locally, outside the
> agent's
> > > > > > sandbox, and expose the MCP server on a local stdin/connection,
> shielding
> > > > > > the MCP logic from the agent. Their server functionality is
> merely the API
> > > > > > they expose to local agents.
> > > > > >
> > > > > > I think there are two broad models we can discuss: centralized
> > > > > > (framework-based) and distributed (standards-based). Both can
> coexist
> > > > > > within the ASF. I can very easily **everything** we dp routed by
> ASF
> > > > > > `llmao` and "tight controlled" by the infrastructure / tooling -
> but also I
> > > > > > can very easily imagine that ASF contributors and maintainers
> use their own
> > > > > > LLM /  Subscriptions and local servers, connecting to ASF APIs -
> this is
> > > > > > IMHO more scalable and more "Apache Way" approach. Both models
> have pros
> > > > > > and cons, but with the standards published in recent months, the
> barrier to
> > > > > > using the distributed approach has dramatically lowered.
> > > > > >
> > > > > > I personally strongly favor a distributed approach over a
> centralized one
> > > > > > for MCP servers, SKILLs, and Agent definitions. This allows each
> component
> > > > > > to be maintained and published separately by different PMCs
> directly in
> > > > > > their GitHub repos. It is sufficient for their code to be
> published
> > > > > > somewhere for the MCP server to be installed and run locally.
> For example,
> > > > > > the MCP servers for Ponymail and Apache Project MCPs in Comdev
> —which we
> > > > > > use in Magpie—are both simply installed and updated from the
> Comdev GitHub
> > > > > > repo.
> > > > > >
> > > > > > Standards for all of this were established in recent months (MCP
> 2.0 and
> > > > > > Agents Marketplace standards established in July/August).
> > > > > >
> > > > > > We recently converted Magpie to be installed from a distributed
> marketplace
> > > > > > in preparation for Magpie's 0.2.0 (or maybe even 1.0.0) release.
> ) release.
> > > > > > I am very happy with the test results; the open standards work
> smoothly
> > > > > > across many agent harnesses and are already quite powerful.
> > > > > >
> > > > > > For example, I used (rather than copying as I was doing so far)
> the threat
> > > > > > model skills from Alpha-Omega to handle threat modeling for our
> scan
> > > > > > preparation. I plan to make this accessible for all PMCs and
> non-ASF
> > > > > > projects—more details will be shared in Glasgow, where we plan
> to run
> > > > > > workshops addressing PMC needs around managing security issue
> volume
> > > > > > (including those from our scans).
> > > > > >
> > > > > > Moving forward, I plan to pursue what we previously discussed on
> the Magpie
> > > > > > devlist with Comdev and Incubator PMCs: distributing skill
> families back to
> > > > > > Comdev and Incubator so they can be managed and exposed directly
> by those
> > > > > > PMCs via distributed marketplaces, rather than hosting them in
> the Magpie
> > > > > > repository. There are few benefits to centralizing them in one
> place; it's
> > > > > > much better to have them managed by the respective PMCs and
> simply "link"
> > > > > > to them.
> > > > > >
> > > > > > Similarly, Legal could distribute their licensing, MCP, and SKILL
> > > > > > marketplace - and we could link to it from Magpie and expose the
> > > > > > "licencing" family of skills.
> > > > > >
> > > > > > This approach - I think - supports better scaling and distributes
> > > > > > governance in the true "Apache Way," giving each PMC autonomy
> over
> > > > > > implementation languages, scope, and publishing methods using
> open
> > > > > > standards.
> > > > > >
> > > > > > Best,
> > > > > > Jarek
> > > > > >
> > > > > > On Tue, Sep 8, 2026 at 11:45 AM Jean-Baptiste Onofré <
> [email protected]>
> > > > > > wrote:
> > > > > >
> > > > > > > That's a valid point: magpie is definitely worth a try on
> podlings.
> > > > > > >
> > > > > > > Regards
> > > > > > > JB
> > > > > > >
> > > > > > > On Tue, Sep 8, 2026 at 8:12 AM Justin Mclean <
> [email protected]>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > HI,
> > > > > > > >
> > > > > > > > On the AI side, Apache Magpie has a release skill that will
> find issues
> > > > > > > in release candidates for you. I suggest that prodlings try
> this out.
> > > > > > Also,
> > > > > > > the Policy MCP can be used to check releases. Having teh
> Policy MCP make
> > > > > > it
> > > > > > > consume a lot fewer tokens, faster, and up to date if the
> policy does
> > > > > > > change.
> > > > > > > >
> > > > > > > > Kind Regards,
> > > > > > > > Justin
> > > > > > > >
> ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail:
> [email protected]
> > > > > > > > For additional commands, e-mail:
> [email protected]
> > > > > > > >
> > > > > > >
> > > > > > >
> ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail:
> [email protected]
> > > > > > > For additional commands, e-mail:
> [email protected]
> > > > > > >
> > > > > > >
> > > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [email protected]
> > > > For additional commands, e-mail: [email protected]
> > > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to