Skip to content
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 Commons Clause modules #984

Closed
wants to merge 1 commit into from
Closed

Conversation

@vmbrasseur
Copy link

vmbrasseur commented Sep 24, 2018

Hi, all. Vice President of the Open Source Initiative (OSI) here.

The Commons Clause, when applied to an OSI-approved license, creates a new license that violates the Open Source Definition (OSD). The OSI does not approve licenses that violate the OSD and does not approve of the Commons Clause in general. Therefore modules with licenses that include the Commons Clause are not OSI-approved.

As this page says it lists only OSI-approved licenses, I've removed the Commons Clause-using modules from the list so that the page is now accurate.

Hi, all. Vice President of the Open Source Initiative (OSI) here.

The Commons Clause, when applied to an OSI-approved license, creates a new license that violates the Open Source Definition (OSD). The OSI does not approve licenses that violate the OSD and does not approve of the Commons Clause in general. Therefore modules with licenses that include the Commons Clause are not OSI-approved.

As this page says it lists only OSI-approved licenses, I've removed the Commons Clause-using modules from the list so that the page is now accurate.
@antirez
Copy link
Contributor

antirez commented Sep 27, 2018

Hello, thanks @vmbrasseur, the current situation of the module page stating that only OSS modules are listed but instead reports the Common Clause modules is wrong indeed, however I don't think I'll remove the Redis Labs modules, I would like to rather find a way to enlist them as well, for two main reasons:

  1. They are the most notable modules in the Redis ecosystem.
  2. They could be seriously useful to Redis users, and are free as beer.

However how to change the policy is currently not clear, if to allow any commercial module to be listed or just "source available and free as beer" modules. However I plan to highlight such modules as non OSS modules.

@vmbrasseur
Copy link
Author

vmbrasseur commented Sep 27, 2018

Removing the "only OSI-approved" bit would accomplish the immediate goal, but I like your additional plan to flag the proprietary-licensed modules as non OSS modules.

Those two things would keep the popular modules on the list, make their licensing clear to potential users, and be accurate from an OSI point of view.

I'm happy to update my PR to do these two things instead, if you'd like?

@ddevault
Copy link

ddevault commented Oct 4, 2018

Hey @antirez, can you answer @vmbrasseur's questions? The current page is disengenous and should probably be quickly corrected.

@natoscott
Copy link

natoscott commented Oct 12, 2018

@vmbrasseur @antirez some of the Redis Labs' modules have been forked and are being maintained as open source software, it would be great if these could be mentioned on the modules page as well.

https://goodformcode.com/

@ddevault
Copy link

ddevault commented Oct 29, 2018

Bump.

antirez added a commit that referenced this pull request Dec 20, 2018
@antirez
Copy link
Contributor

antirez commented Dec 20, 2018

Hello, I did two things:

  1. Modified the wording in the web site to specify that non OSI approved licenses are specified in the list.
  2. Mark all the non OSI modules clearly in the listing.

The changes should be online in a matter of minutes as the site fetches the new version from Git.

Cheers,
Salvatore

@antirez antirez closed this Dec 20, 2018
@ddevault
Copy link

ddevault commented Dec 20, 2018

Thanks! Took your time...

@ddevault
Copy link

ddevault commented Dec 21, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants
You can’t perform that action at this time.