10 ms·
Consider how happy this made me: I wrote a PR to fix something in Vault, then nothing happened for a while, then I saw that hashicorp is changing their licensi
by korhojoa 3y ago
Consider how happy this made me:
I wrote a PR to fix something in Vault, then nothing happened for a while, then I saw that hashicorp is changing their licensing, and soon after that, my fix was merged. My fix sat waiting until they changed their license, and then it was merged before I had time to consider if I wanted to contribute under that license.
(Incidentally, sentry also changed their license soon after I interacted with the project. Maybe it's me ruining the OSS world)
- fishnchips 3y agoCan I send you a list of projects to not contribute to? ;) /s
- zappb 3y agoThis is why it’s important to check if an OSS project is also developed under an open governance model like at Apache or Linux Foundation.
- qualitystreet 3y agoSo, we should check if OpenBAO is then..? I assume this means the assigned copyright holder is a trusted non-commercial body (Apache or Linux Foundation). I saw a similar thing happen with another product recently. It made me realise even though the project was touting itself as open source you couldn't even build the open code into a useable product. So the importance of assigning copyright to a suitable body crystallised for me.