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

DBeaver CE relicense on Apache License #1180

Closed
serge-rider opened this Issue Jan 24, 2017 · 5 comments

Comments

Projects
None yet
3 participants
@serge-rider
Member

serge-rider commented Jan 24, 2017

DBeaver CE 4.0 will be licensed under Eclipse Public License (EPL).

Main reason is to allow DBeaver CE sources/binaries usage in commercial/proprietary software.

@serge-rider serge-rider added this to the 4.0 milestone Jan 24, 2017

@serge-rider serge-rider changed the title from DBeaver CE relicense to Eclipse Public License (EPL) to DBeaver CE relicense on Eclipse Public License (EPL) Jan 24, 2017

@carlosspohr

This comment has been minimized.

carlosspohr commented Jan 24, 2017

@maitrepylos

This comment has been minimized.

maitrepylos commented Jan 25, 2017

Cool, thanks

@serge-rider

This comment has been minimized.

Member

serge-rider commented Jan 25, 2017

Also check #1145

@serge-rider

This comment has been minimized.

Member

serge-rider commented Feb 1, 2017

After all I think that ASL (https://www.apache.org/licenses/LICENSE-2.0) would be better for DBeaver CE.
EPL is a bit more restrictive.

@serge-rider serge-rider changed the title from DBeaver CE relicense on Eclipse Public License (EPL) to DBeaver CE relicense on Apache License Feb 1, 2017

serge-rider added a commit that referenced this issue Feb 1, 2017

@serge-rider

This comment has been minimized.

Member

serge-rider commented Feb 1, 2017

Official statement:
DBeaver CE is licensed under Apache License 2.0 since Feb 02 2017.

@serge-rider serge-rider closed this Feb 1, 2017

serge-rider added a commit that referenced this issue Feb 1, 2017

tchibatron pushed a commit to tchibatron/dbeaver that referenced this issue Sep 23, 2018

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