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

Choice of Open Source License #18

Closed
catull opened this issue Oct 22, 2017 · 6 comments
Closed

Choice of Open Source License #18

catull opened this issue Oct 22, 2017 · 6 comments

Comments

@catull
Copy link
Contributor

catull commented Oct 22, 2017

WTFPL is anarchic and offensive.

It is your right, dear maintainer, to keep it that way, or to switch to a different one.

However, the current license is a deterrent for me.

Since I take Open Source software development seriously, both as a beneficiary as well as a contributor, I certainly cannot identify with nonchalance.

Please consider alternative license models, such as

My favourite ones are: BSD 3-clause, BSD 2-clause, APL, MIT, EPL, MIT or ISC.
I would still stick around with *GPL.

CDDL is out, though.

Choose wisely.

@xMase
Copy link

xMase commented Oct 22, 2017

I like WTFPL license, why is it offensive for you?

@catull
Copy link
Contributor Author

catull commented Oct 22, 2017

Far more important is the "anarchic" part, which deters me.

I cannot associate with anarchic views.
It shows no pride in what you do.

Why does one still invest time and brain-power without caring what happens to/with the software ?
What is the motivation ?

As far as the offensive part is concerned, I'd like to show my appreciation for "profanity" with a scene from the "Big Lebowski": Cuss words

I can deal with it in only one context: no-fuss comedy.
That's where I draw the line.

Had I paid more attention to the license, I would not have contributed.
It is too late now, I have made some contributions, which I will not revoke.

My contributions are small in comparison; the project will carry on, no matter what happens to the license.

One more thing: both AdminLTE and Angular are licensed under MIT.
No obligation there.

@xMase
Copy link

xMase commented Oct 22, 2017

the community is divided on this license and a license should not be a reason for division, into the open source world. I think that the admin repo should change the license to MIT and take all community power.

@TwanoO67
Copy link
Owner

I just read the thread suggested by @catull
And I wasn't aware of the "don't blame me" missing part of this license.

And I'm ok with @xMase this should not be a division reason.

So listening to both of you, I will change licensing to MIT in the next release

@catull
Copy link
Contributor Author

catull commented Oct 23, 2017

Thanks to both of you.

I am glad this is issue is treated appropriately.

@gsouf
Copy link

gsouf commented Dec 15, 2017

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

No branches or pull requests

4 participants