BSD License issue

[ltoenning]

In our project we must strictly stick to the 3-Clause BSD license and want to use cereal.

I checked the LICENSE file and it seems you made small changes to license text (maybe that is also why Github doesn't detect the license).

1. In the third clause you're stating:

Neither the name of cereal nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

but the original says:

Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

2. Further you specify:

[...] IN NO EVENT SHALL RANDOLPH VOORHIES OR SHANE GRANT BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES [...]

where the original says:

[...] IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES [...]

so theoretically nearly all contributors could be liable for damages.

Are these changes compared to 3-clause BSD intended? If not, could you adjust the license?

I know its a very minor thing but we really would like to use cereal but need to stick to the license.

[ptrdtznr]

I know this is a critical and an important topic (not only for us, probably for everyone who uses cereal already and who wants to use it in the future) - are there any updates/news regarding the license topics? @AzothAmmo @randvoorhies

[AzothAmmo]

Will look into this around the end of the month.

…

________________________________ From: Peter Detzner ***@***.***> Sent: Monday, December 20, 2021 11:39:54 AM To: USCiLab/cereal ***@***.***> Cc: Shane Grant ***@***.***>; Mention ***@***.***> Subject: Re: [USCiLab/cereal] BSD License issue (Issue #729) I know this is a critical and an important topic (not only for us, probably for everyone who uses cereal already and who wants to use it in the future) - are there any updates/news regarding the license topics? @AzothAmmo<https://github.com/AzothAmmo> @randvoorhies<https://github.com/randvoorhies> — Reply to this email directly, view it on GitHub<#729 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAMPCT2IDFAEX4MJYKZPXO3UR4IYTANCNFSM5JLO37VQ>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[ltoenning]

Sorry for annoying with this issue... But are there any news on this @AzothAmmo ?