Closed brianLoomis closed 2 months ago
sagikazarmark
commented
3 months ago @brianLoomis my understanding is that the API package is still licensed under MPL 2.0: https://github.com/hashicorp/consul/blob/main/api/LICENSE
MPL 2.0 is a recognized OSS license and doesn't affect how you use crypt (as far as my understanding of licensing goes).
brianLoomis
commented
3 months ago Thank you – I was only looking at the top level BSL, thanks for pointing out the lower level API-specific one.
From: Márk Sági-Kazár @.> Date: Wednesday, April 3, 2024 at 6:54 PM To: sagikazarmark/crypt @.> Cc: Brian Loomis @.>, Mention @.> Subject: Re: [sagikazarmark/crypt] license question (Issue #265)
@brianLoomishttps://github.com/brianLoomis my understanding is that the API package is still licensed under MPL 2.0: https://github.com/hashicorp/consul/blob/main/api/LICENSE
MPL 2.0 is a recognized OSS license and doesn't affect how you use crypt (as far as my understanding of licensing goes).
— Reply to this email directly, view it on GitHubhttps://github.com/sagikazarmark/crypt/issues/265#issuecomment-2035742286, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVQZPBWRQL2VF5RG365JBN3Y3SCA5AVCNFSM6AAAAABFWDZX52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZVG42DEMRYGY. You are receiving this because you were mentioned.Message ID: @.***>
crypt uses hashi's consul/api, which since 1.17 has been under Business Source License (BSL), which is not a recognized open source license. Are there plans to update crypt to either take up BSL as its license, or get an MIT-compliant license for hashi's component? We would like to use crypt under MIT license. Please feel free to reply to brian.loomis@progress.com and delete this issue since it's really a question. thanks!