You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to raise a question about the license under which this repo was created two years ago. If I read the purpose of this repo as "This has been developed as a starting point or foundation and is not necessarily considered 'complete'. It is being made available to allow learning, development, and knowledge-sharing amongst communities.", it would seem that the GNU General Public License is not appropriate as that license carries with it obligations to provide source code if it were used a larger product and other things.
Wouldn't the MIT license be more appropriate for this kind of purpose? It would already include the kind of liability disclaimer which is in it too.
I don't want to presume on James's (or his co-contributors) purposes, so if I am not correct on this it is okay. I have a use case that is relevant to the question. Thank you.
The text was updated successfully, but these errors were encountered:
I wanted to raise a question about the license under which this repo was created two years ago. If I read the purpose of this repo as "This has been developed as a starting point or foundation and is not necessarily considered 'complete'. It is being made available to allow learning, development, and knowledge-sharing amongst communities.", it would seem that the GNU General Public License is not appropriate as that license carries with it obligations to provide source code if it were used a larger product and other things.
Wouldn't the MIT license be more appropriate for this kind of purpose? It would already include the kind of liability disclaimer which is in it too.
I don't want to presume on James's (or his co-contributors) purposes, so if I am not correct on this it is okay. I have a use case that is relevant to the question. Thank you.
The text was updated successfully, but these errors were encountered: