licensing

[martunta]

I was wondering how exactly licensing works - with create-react-app it is a library, with which I generate my own application and I can use my own licensing on generated application (as far as I understand). but with create-react-library I have to clone the repo and use that as a basis for my lib.

And so I have to keep original included license also for whatever code I create that are actual contents of my library? Or can I somehow add my own license as well and separate actual create-react-library from my own software? It is a bit weird - if create-react-library would work like create-react-app does it would be so much clearer.

[DimiMikadze]

Hello,

Create-react-app is under MIT licence by Facebook Inc, not by user whos using it.

Create-react-library is also under MIT license, just noticed i forgot to upload it, thanks for reminding.

[martunta]

create-react-app generates new repository when using it as a command line tool, without any license files in it, when I start creating new app.

create-react-library has to be cloned, thus retaining all the license files in it. Hence my question - what happens when I start iterating on the cloned app (adding my own code under src/lib folder), all my stuff is also under your license automatically? If so, then I can not use it for closed source project.

or this is not how it works and I can safely remove all the license files after cloning your repo?

[martunta]

hmm, I wonder if you will see my comment as you already closed the issue

[DimiMikadze]

You can safely remove all the licence files after cloning our repo and add whatever licence you want for your own project.

This rule applies to all projects which is under MIT licence, no matter you have to clone it or generate from terminal.

[martunta]

well if I generate it, there are no files in the first place, so no question :)

[martunta]

though your license states:

Copyright (c) 2015 Rubbby

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies 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.

so it is not MIT right now

[DimiMikadze]

If it’s not MIT, then which licence it is?

[martunta]

well, this part:

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

does not match what you said before - that I can just remove it after cloning.

[DimiMikadze]

Updated licence file with current company name. Didn’t knew about that part, i have copied this licence file from template, can you suggest any other one?

[martunta]

I think it is fine as a MIT license goes.

I would just like to avoid using it for my own in-house library.

Hence my preference for code that is generated - as it has no license files attached to it. Then there is a clear distinction - library with build scripts is under MIT, and my code is under my own license - no duality and no confusion. Thats how it works with most of the npm libraries I have seen. Either they are included as a lib in node_modules, or they provide command line tools that lets you generate stuff that is fully your own.

[DimiMikadze]

Yep, understand what you are saying but how then Wordpress or similar projects work under MIT licence? I’m not proficient in this subject, i want this starter kit to be, as i’ve said above. Right now i’m in vacation, when i’ll get back i’ll think about creating command line tools for generating new project.

Thanks for openning this issue, i’ve never thought about this subject.

[martunta]

wordpress works just like firefox or java - you install it and then you use it, it is a tool and has its own licensing. And if you create your own IP by using it, then your IP is covered by license of your own choosing.