Versity S3 Gateway is Apache‑licensed, backed by a commercial entity. Their contribution agreement forces you to give up copyright to them. It will follow the same path as Minio over time.
Their contribution agreement forces you to give up copyright to them.
The license just looks like the standard Apache license though, which doesn’t require this. With the Apache license, contributors still own the copyright to their code, but they license it to the project. Did you see a document in the repo that says something different?
Interesting - I didn’t see that. They say “You can add your own copyright as well”, so you don’t have to give up your rights to the code. They do still need to comply with the terms of the Apache license.
Versity S3 Gateway is Apache‑licensed, backed by a commercial entity. Their contribution agreement forces you to give up copyright to them. It will follow the same path as Minio over time.
The license just looks like the standard Apache license though, which doesn’t require this. With the Apache license, contributors still own the copyright to their code, but they license it to the project. Did you see a document in the repo that says something different?
Check their contribution rules. https://github.com/versity/versitygw/wiki/Contributing-Changes
quoting
All new files in the change should have the versitygw copyright and license headers.Interesting - I didn’t see that. They say “You can add your own copyright as well”, so you don’t have to give up your rights to the code. They do still need to comply with the terms of the Apache license.