A new license

[KingInfinity]

The NEC License v1.5
What is the NEC License?
While working on some programs for the TI-84+CE, we needed to find a way to control where our software was going. Some licenses, such as the MIT license, were too loose and allowed no control anywhere. Other licenses were too strict. We needed a license that allowed modification, but not just direct copies. And thus, the NEC license was born.

What does it mean?
Don't sell the software
Do edit the software
Don't distribute copies
Do distribute versions of the software you have modified or improved upon significantly.
Do use this license in modified versions that you distribute.
Don't blame the developers if something goes wrong.
The author can request removal of copies or modified versions of the software.
Don't license the software to other people using a different license.

The License
The NEC License v1.5
Copyright (c) 2016, Author
Derived from a work originally created by Author.

You may not sell any portion of this software or use it for commercial use. However, the demonstration of the software at a commercial event is permitted. You are permitted to modify the software for personal use, or for distribution following the guidelines below.

Redistributions online, or using methods involving the internet, is prohibited unless significant alteration is made to the software, or unless express permission is given by the author. Significant alteration is defined as any addition or removal to the functionality of the software. Any redistrubitions must include a copy of this license. Redistributing verbatim copies of the software is not permitted. The author reserves the right to deny any redistribution, and to request removal of any redistribution if the privilege was abused or if permission was not granted, or for any other reason necessary to retain proper ownership over the software, be it modified or a verbatim copy. Sublicensing is not permitted.

The above copyright notice and this permission notice shall be included in all redistributions or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

[Lionel Debroux]

Don't you just love dealing with copyright issues?
It has come to my attention that some people are using loopholes in licenses to use other people's work without their permission, often causing old or outdated builds to be published in select locations. With this in mind, I have decided to come up with a new license that will hopefully cover all of that business... it's a little strict, but hopefully we can keep the open source spirit while remaining in control of our work.
The license is called the The NEC License (v1). This thread may be updated as the license may update.

Here it is in plain English:
Don't sell the software
Do edit the software
Don't distribute copies
Do distribute versions of the software you have modified or improved upon significantly. Making a bug fix is not a significant change.

Here is the actual license you should include with your program(s) (you may edit it as you see fit):

The NEC License v1.1
Copyright (c) 2016, Author
Derived from a work originally created by Author.

You may not sell any portion of this software or use it for commercial use. You are permitted to modify the software for personal use, or for distribution following the guidelines below.

Redistributions online, or using methods involving the internet, are permitted with significant alteration, in any format, unless express permission is given by author, in which case you may follow the author's guidelines. Redistributing copies of the software is not permitted. The author reserves the right to deny or request removal of any redistribution.

The above copyright notice and this permission notice shall be included in all redistributions or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

I will adopt this license in all of my future projects and I encourage you to do the same.

Before creating new licenses and participating to license proliferation, which is a well-identified issue in the FLOSS world... how about, you know, understanding the explicit meaning and implications of existing licenses ?
As outlined earlier, the one you used previously is the MIT license, which gives explicit permission to publish and distribute your program, provided the licensing information is kept. End of story
By labeling "loopholes" and "use other people's work without their permission" the explicit permissions in the license you used, not only you're openly lying, but also, you're showing your blatant incompetence...
Using legally weak licenses (that's what your NEC is...) which go counter the community's spirit is your choice, but a bad one

[DoOmnimaga]

Yeah I agree about that Lionel. It seems like in the past, some people in the TI community seemed to do everything possible, by using weird licenses or lack of licensing just to ensure that their own website or person gets the exclusive rights to even promote the software. This is not only counter-productive for the TI community, but also for the author, because by doing this he gets even less visibility.

[Adriweb]

He has since edited the first post to include his latest version (as far as I can tell), though the fact that he reserves the right to make a modified version removed will not make people want to contribute... (He did say he wouldn't "abuse" this right, but still).

Anyway, if he wants his programs to be more well-known to more people around the world (and especially in France with the 83 Premium CE being quite huge), he'll either give express reupload consent as the license would require, or upload them directly (and I'm talking about TI-Planet, sure, but other websites as well, such as CodeWalrus and ticalc.org)

My personal opinion is that for calculator programs (seriously...), stuff should be open-source and with restrictions not to be integrated in closed-source stuff, let alone being sold or whatever. The GPL seems like a good fit for that, although there are some less strict ones too.
And if for some reason (why not...), someone thinks it's better to have one central place of file upload, it could be GitHub, and community websites could just link the download to the file there. At least updates get synchronized etc. At the same time, it allows for clear open-sourceness and license visibility.

[critor]

He has since edited the first post to include his latest version (as far as I can tell), though the fact that he reserves the right to make a modified version removed will not make people want to contribute... (He did say he wouldn't "abuse" this right, but still).

Si il n'avait véritablement pas l'intention de l'utiliser, il n'aurait pas besoin de mettre cette ligne.

Je trouve cela totalement aberrant d'autoriser par défaut les gens à passer un nombre d'heures conséquent à modifier son programme, pour ensuite vouloir se permettre d'exiger le retrait d'un programme qui n'est plus le sien, et dans lequel son code est peut-être même devenu minoritaire.

Je ne sais pas pour l'Amérique, mais en Europe une telle clause problématique n'aura aucune valeur en justice. La loi est supérieure au contrat ou à la licence, et toutes les clauses abusives sont réputées non écrites.