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

Proposal: BSD-3-Clause to replace MS-RL #3

Merged
merged 2 commits into from
Nov 26, 2021
Merged

Conversation

sr229
Copy link
Member

@sr229 sr229 commented Nov 26, 2021

There has been raised concerns that GPL projects cannot use MS-RL Projects, so with some consideration witht heir requirements and our requirements, this is the middle ground for all of us.

This will be used on all first-party projects we're currently maintaining

There has been raised concerns that GPL projects cannot use MS-RL Projects, so with some consideration witht heir requirements and our requirements, this is the middle ground for all of us.
@Speykious
Copy link
Contributor

It looks like the BSD-3-Clause license is ideal for trademark and misinterpretation protection for our libraries.
However, on the code side, it doesn't seem to restrict proprietary forks - which I would say is my last concern.
Maybe that is implicitly included in the "without specific prior written permission" expression, as in, we would decide whether to allow that?

@sr229 sr229 merged commit 831b856 into master Nov 26, 2021
@sr229 sr229 deleted the proposal/bsd-3-clause branch November 26, 2021 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants