My opinions:
1. we should replace them if we want to keep the Gaurav theme
2. same: we should remove/replace that stuff
3. there might be snippets, but not worth mentioning in the notice file

Dave


On Sat, Nov 14, 2026 at 4:24 PM Matt Raible <[email protected]> wrote:

> Hi all,
>
> While preparing the Roller 7.0.0 release candidate, I updated our LICENSE
> and NOTICE files to match what 7.0.0 actually ships:
>
> https://github.com/apache/roller/pull/265
>
> Three questions came up that I'd like the PMC's input on before we cut
> RC1, since release voters check these files.
>
> 1. Category B files in the source release
>
> Two sets of checked-in files are under Category B licenses:
>
> - Font Awesome 3.2.1 font files (SIL OFL 1.1) in
> app/src/main/webapp/themes/gaurav/font/
> - The Silk icons (CC BY 2.5) in app/src/main/webapp/images/ and
> themes/{fauxcoly,gaurav}/icons/
>
> Because they're checked in, they end up in the source archive. ASF policy
> allows Category B works in binary form only (
> https://www.apache.org/legal/resolved.html). Should we remove them from
> the source tree and replace them (for example with Bootstrap Icons, which
> the admin UI already uses), or is there a justification we can rely on for
> keeping them? PR #265 labels them for now rather than removing them.
>
> 2. Files with no recorded license or source
>
> - searchhi.js, from kryogenix.org (Stuart Langridge), in
> themes/fauxcoly/, themes/gaurav/js/ and theme/scripts/. It has no license
> statement.
> - Some smileys, editor GIFs and brand logos in themes/*/icons, which date
> from the 2005 initial import and have no recorded source.
>
> Does anyone know where these came from, or should we replace them?
>
> 3. The "RSS and Atom in Action" line in NOTICE
>
> NOTICE.txt credits "snippets of code written by Dave Johnson for RSS and
> Atom in Action" (Copyright 2005 David M Johnson), but I couldn't find code
> that clearly carries it anymore. Dave, do you know whether any of that code
> is still in Roller, or can we drop the line?
>
> Thanks,
>
> Matt
>
>

Reply via email to