New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove MongoDB - License issue #10785

Open
pierreozoux opened this Issue Jan 20, 2019 · 5 comments

Comments

Projects
None yet
5 participants
@pierreozoux
Copy link
Contributor

pierreozoux commented Jan 20, 2019

As RedHat and Debian removed MongoDB from their catalog, I think we'll have to do the same here.

Does anybody has access to a lawyer to answer these questions?

As a consequence, we'll need to remove all project that depend on it as a default option.

@beltran-rubo

This comment has been minimized.

Copy link
Contributor

beltran-rubo commented Jan 21, 2019

Hi @pierreozoux, AFAIK there is not any issue about having MongoDB published in this repo. There is no requirement for the software package to be open source e.g. there is one for MSSQL available https://github.com/helm/charts/tree/master/stable/mssql-linux

@steven-sheehy

This comment has been minimized.

Copy link
Collaborator

steven-sheehy commented Jan 21, 2019

I am one of the maintainers of the mongodb-replicaset chart. I am against removing MongoDB from this repository. All the charts in this repository are licensed under the Apache license and no MongoDB code or binaries are stored here. So even if there was any issue with MongoDB's license, it's not applicable because the charts are separate from the applications they run that are stored in a docker registry.

cc @unguiculus

@unguiculus

This comment has been minimized.

Copy link
Member

unguiculus commented Jan 22, 2019

IANAL, but I don't see any issue either and fully agree with @steven-sheehy.

@pierreozoux

This comment has been minimized.

Copy link
Contributor Author

pierreozoux commented Jan 22, 2019

I guess then this issue depends on

What if these repo remove MongoDB support, where will you host the docker image? (I can see that you already use personal repos, and I have to admit that this worries me a bit).

What is the strategy to warn users about the change from open source to proprietary software? I think it is important to manage our users expectations.
Maybe we can use a acceptEula.value flag, or acceptProprietaryLicense.value that default to false so users are aware.

I'm a hoster myself, and this worries me, event though i think my whole infrastructure is free software.
@steven-sheehy do you use this chart personally or in a professional context? If you use it in a professional context, what is the strategy of your company on this topic?

I'm very curious, and these are questions I think are important to answer.

@prydonius

This comment has been minimized.

Copy link
Member

prydonius commented Jan 28, 2019

What is the strategy to warn users about the change from open source to proprietary software? I think it is important to manage our users expectations.
Maybe we can use a acceptEula.value flag, or acceptProprietaryLicense.value that default to false so users are aware.

Hmm, I'm not sure what the right thing to do here is. I would think that adding a new required value to accept the new license isn't the best way to notify people about this (I think it would confuse/annoy people, rather than be helpful). Has mongo or mongod changed to require some acceptance of the new license?

We don't currently share the license of the underlying software used in the charts in this repo, perhaps that's something we need to start doing? We also probably want to add something to the chart README notifying the change of license (e.g. under the https://github.com/helm/charts/tree/master/stable/mongodb#upgrading section).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment