-1 binding from me

I agree that the Undraw files should be regarded as Category X under
https://www.apache.org/legal/resolved.html due to restrictions,
especially related to AI.
It might be feasible to see if the Legal team will approve the Undraw
for use in websites but it would probably be best to replace these
files.

The GitHub svg files appear to be copied from Apache StreamPark so
they might have a license issue too.
The Apache header should be removed from them and the correct headers
added to them. The Fesod License needs to mention these files and
their licenses.
github_icon.svg - my Claude AI instance suggests the path is
byte-identical to the Simple Icons GitHub glyph. Simple Icons is CC0
1.0, so it is public domain and Category A.
github.svg - suggested to be from Ant Design Icons and MIT Licensed
(also Category A). Copyright Ant UED. The image itself is the GitHub
mark, which is a GitHub trademark (same as github_icon.svg).

Claude also highlights:
website/src/pages/team/data/github-avatar.json and
website/blog/authors.json: generated files holding base64 JPEG avatars
of every PMC member and committer, fetched from GitHub. These are the
individuals' own profile photos, and neither GitHub nor the project
holds a license to redistribute them. Both files ship in the 2.1.0 rc6
source tarball.

So unless you have explicit rights to show these user images, I think
you should remove them.



On Wed, 16 Sept 2026 at 18:37, Ian Maxon <[email protected]> wrote:
>
> Hi,
> I think I have to vote -1. I checked
> - Signatures/checksums
> - RAT passes (so source files have headers)
> - Source compiles fine
> - Tarball matches source release
> - LICENSE,NOTICE,DISCLAIMER present
> - Incubator suffix present on all artifacts I saw
>
> However when digging around for other artifacts with an LLM, it
> brought to my attention some SVG files in
> website/static/img/index/undraw_* are actually from https://undraw.co/
> and just had the ASLv2 license header inadvertently added. The actual
> license for these artifacts seems to be a restrictive license
> (https://undraw.co/license). I was able to find, for example, the
> undraw_files.svg artifact, sans header, on this site.
> I also noticed the github logo SVG on
> website/src/pages/team/github.svg has the ASLv2 header injected. I
> don't know what the license of this is, I would imagine this one is
> less troublesome.
> I think these got missed because RAT is excluding all website files.
> If I'm misunderstanding something I'm happy to change my vote to +1, I
> didn't find any other issue.
>
> Other than that SVG problem the release seems great. A very cool project.
>
> On Wed, Sep 16, 2026 at 7:06 AM Ayush Saxena <[email protected]> wrote:
> >
> > +1 (Binding)
> >
> > * Built from source
> > * Verified Checksums
> > * Verified Signatures
> > * Source files have ASF header
> > * Verified NOTICE & LICENSE file
> > * DISCLAIMER file exists
> > * Verified incubating in name
> > * No unexpected binary
> >
> > The issues Justin mentioned exists. Please create a ticket/issue for
> > it & try to resolve it in the next release. Good Luck!!!
> >
> > -Ayush
> >
> > On Wed, 16 Sept 2026 at 14:53, Xuanwo <[email protected]> wrote:
> > >
> > > +1 (binding)
> > >
> > > Verified on Linux x86_64 with JDK 11:
> > > - Checksums and signatures passed.
> > > - The source archive matches the release tag.
> > > - LICENSE, NOTICE, source headers and archive contents checked.
> > > - The source build and 687 basic tests passed.
> > > - Staged source JARs match their documented build inputs.
> > >
> > > For follow-up, I agree with Justin's points about the remaining
> > > Alibaba copyright-header cleanup, stale POM description,
> > > a standalone META-INF/DISCLAIMER, and clearly marking
> > > pre-donation GitHub releases as non-ASF.
> > >
> > > Thanks,
> > > Xuanwo
> > >
> > > ---------------------------------------------------------------------
> > > 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