Re: GitHub license display confused by LICENSE-header.txt

Le mar. 9 mars 2021 à 01:41, sebb a écrit : > > 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 >

Re: [crypto] Interest in adding support for cryptographic hash function?

Coming back to this thread since I started porting the Blake3 code. Seeing the AES differences makes a lot of sense since most of the software optimizations possible are insecure, and the only secure software designs for AES have noticeable performance penalties compared to AES intrinsics. I'd sti

Re: GitHub license display confused by LICENSE-header.txt

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 wrote: > > On Tue, 9 Mar 2021 at 01:08, Bernd Eckenfels wrote: >> >> Checkstyle-header.txt sounds good and maybe also moving it to a subdir like >> src/build/ o

Re: GitHub license display confused by LICENSE-header.txt

On Tue, 9 Mar 2021 at 01:08, Bernd Eckenfels 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 > _

Re: GitHub license display confused by LICENSE-header.txt

Checkstyle-header.txt sounds good and maybe also moving it to a subdir like src/build/ or src/test/? Gruss Bernd -- http://bernd.eckenfels.net Von: sebb Gesendet: Tuesday, March 9, 2021 1:41:02 AM An: CommonsDev Betreff: GitHub license display confused by LICE

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

Re: [COMPRESS] OSS-Fuzz integration

Note that we already have FIVE mailing lists: commits dev issues notifications user PLUS, private and security. Do we really want a SIXTH? Can't this fit in one of the above? Gary On Mon, Mar 8, 2021 at 12:43 PM Stefan Bodewig wrote: > > On 2021-03-08, Gary Gregory wrote: > > > Are we talking

[BOARD][REPORT] Proposed report

Here is the report I plan on submitting to the board tomorrow; feedback is welcome :-) -- ## Description: The mission of Apache Commons is the creation and maintenance of Java focused reusable libraries and components ## Issues: There are no issues requiring board attention. ## Membership Data: A

Re: [COMPRESS] OSS-Fuzz integration

On 2021-03-08, Gary Gregory wrote: > Are we talking about a human sending emails to the security list or letting > the actual tool loose on the list to possibly spam it with false positives? We are talking about a tool sending mails that (currently) is unable to identify whether an issue it detec

Re: [CSV] New release anytime soon?

Hm, I am pretty sure that a release would just be like what you get in a local build, minus the -SNAPSHOT postfix in version label. Gary On Mon, Mar 1, 2021, 07:05 Rob Vesse wrote: > Gary > > I have already tried testing what's in master > > It seems like you only get Automatic-Module-Name when

Re: [COMPRESS] OSS-Fuzz integration

Are we talking about a human sending emails to the security list or letting the actual tool loose on the list to possibly spam it with false positives? Gary On Mon, Mar 8, 2021, 02:56 Peter Lee wrote: > I think the security list is a good choice. > > Lee > On 3 8 2021, at 2:55, Stefan Bodewig