Apologizing to the community.

[Xyon]

Then for me it would be easy as I care little about it. My goal is for people to use/abuse it.

About the WTFPL

The Do What The Fuck You Want To Public License (WTFPL) is a free software license. There is a long ongoing battle between GPL zealots and BSD fanati

www.wtfpl.net

 

[Face]

Jokes aside, I'd suggest to use what Martin used with Orbiter itself: MIT. https://github.com/git/git-scm.com/blob/main/MIT-LICENSE.txt

 

[Urwumpe]

Then for me it would be easy as I care little about it. My goal is for people to use/abuse it.

Then, the MIT licence is likely the best "safe for work" choice, followed by the creative commons.

The MIT License | Open Source Initiative

opensource.org

 

[gattispilot]

Looks good to me. Thanks. Do I need to have that somewhere in the add on. Or part of the code?

 

[Face]

Just add a LICENSE file with that text in the root or DOC folder of your addon. For bonus points, you can add a similar header in every source file:

// Copyright (c) <your_name_here>
// Licensed under the MIT License

But that is not really necessary.

 

[N_Molson]

Yes, a good practice would be to include such a licence 1) in the plugin documentation 2) in the plugin code files (.h , .cpp...). That way things are clear.

Martins did that in all the SDK files, so we should probably stick to it.

 

[jedidia]

About the WTFPL

The Do What The Fuck You Want To Public License (WTFPL) is a free software license. There is a long ongoing battle between GPL zealots and BSD fanati

www.wtfpl.net

Now I kind of would like to see a court case involving this license...

 

[Xyon]

Perhaps we can offer some standard license types you can select for your add-on when it's uploaded, if you wanted to go down the route of being covered by a standard license.

As we note in the ToS, for all add-ons we hold whose author didn't specify, we assume an "all rights reserved" kind of license (we kind of have to, unfortunately), but we could present that choice to uploaders of add-ons at creation time, and let the UI show if their work should be covered by a different one.

Licensing is, unfortunately, always a bit of a Topic here ever since the Great GPL Wars, but we do want to make publishing things to the system as painless as possible even so.

Added this now as a custom field on the Addon Creation screen;