Good idea.

I have done that for commons-codec, and GH has now agreed to use  AL2.0

However it did seem to need a dummy change to the LICENSE file to
re-evaluate the license.

I'll see about fixing the others

On Tue, 9 Mar 2021 at 01:15, Melloware Inc <melloware...@gmail.com> wrote:
>
> In commons beanutils we recommend using /src/conf for these type of files.
>
> Sent from my iPhone
>
> > On Mar 8, 2021, at 8:13 PM, sebb <seb...@gmail.com> wrote:
> >
> > On Tue, 9 Mar 2021 at 01:08, Bernd Eckenfels <e...@zusammenkunft.net> 
> > wrote:
> >>
> >> Checkstyle-header.txt sounds good and maybe also moving it to a subdir 
> >> like src/build/ or src/test/?
> >
> > There are other checkstyle files at the top-level; best to keep them 
> > together.
> >
> >> Gruss
> >> Bernd
> >>
> >>
> >> --
> >> http://bernd.eckenfels.net
> >> ________________________________
> >> Von: sebb <seb...@gmail.com>
> >> Gesendet: Tuesday, March 9, 2021 1:41:02 AM
> >> An: CommonsDev <dev@commons.apache.org>
> >> Betreff: GitHub license display confused by LICENSE-header.txt
> >>
> >> Most of the Commons projects show up in GitHub as having the Apache 2.0 
> >> License
> >>
> >> However a few show up as 'other':
> >>
> >> commons-codec
> >> commons-csv
> >> commons-dbutils
> >> commons-exec
> >> commons-jelly
> >> commons-logging
> >> commons-math
> >> commons-rdf
> >> commons-text
> >> commons-weaver
> >>
> >> AFAICT this is because there is more than 1 LICENSE file at the top level:
> >> I forked codec and deleted the LICENSE-header.txt file, and the
> >> license then showed up as AL 2.0.
> >>
> >> I think it's not only GitHub that might be confused by such files, so
> >> I suggest they are moved or renamed to avoid the confusion. They are
> >> only needed for Checkstyle, so perhaps could be named accordingly,
> >> e.g. checkstyle-header.txt
> >>
> >> [Obviously there would need to be corresponding changes in the pom and
> >> assembly files]
> >>
> >> WDYT?
> >>
> >> Sebb.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >> For additional commands, e-mail: dev-h...@commons.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to