|
|
| Page 1 of 1 |
|
|
 Posted: Wed, 14th Jul 2021 22:58 Post subject: Publishing a library |
|
 |
So I had developed this presentation engine back in 2014 that I've been using on and off to present stuff in the companies that I had worked in. Whoever saw my presentations asked which tool I had used and I always said it's my custom library. It's just some HTML, JS and CSS but out of convinience I recently cleaned up the code a little bit and now it'd be ready to be published as ready-to-use Vue components.
I really like what it can do and I honestly think it's super easy to use, so naturally I want to release it to the WWW as apparently nobody came up with something similar in the last 7 years or well there is no need for this 
Anyhow: How do I properly release this? I assume github and then creating and publishing the package on npm are the first steps. Do I have to take care of specific license models? I want this thing to be free, be it personal or commercial use but I don't want someone to clone the library, slap a different name on it and then try to make money out of it.
|
|
| Back to top |
|
|
X_Dror
Posts: 4955
Location: Jerusalem, Israel
|
| Posted: Wed, 14th Jul 2021 23:18 Post subject: |
|
|
Licenses like MIT/BSD/Apache are permissive and will allow folks to use the component for personal and commercial use, while requiring them to mention the source of the material (e.g, you). The material is still under your authorship, which means, people shouldn't claim it's theirs... but in practice, it will be very difficult to enforce it.
On the other hand you have much more strict licenses like GPL which force whoever uses your component to open source their code as well. Yet again, enforcing is a whole different matter.
|
|
| Back to top |
|
|
LeoNatan
Banned
Posts: 73193
Location: Ramat Gan, Israel 🇮🇱
|
| Posted: Thu, 15th Jul 2021 01:30 Post subject: |
|
|
If you put a restrictive license, companies and developers will not use it because they’ve been conditioned to run away from these licenses, and malicious actors will still steal it, app a different name to it and make money from it.
So just put the MIT or BSD license and be happy.
|
|
| Back to top |
|
|
|
|
| Posted: Thu, 15th Jul 2021 10:47 Post subject: |
|
|
| LeoNatan wrote: | If you put a restrictive license, companies and developers will not use it because they’ve been conditioned to run away from these licenses, and malicious actors will still steal it, app a different name to it and make money from it.
So just put the MIT or BSD license and be happy. |
+1
PC: Yes. Console: No.
|
|
| Back to top |
|
|
|
|
| Posted: Thu, 15th Jul 2021 11:19 Post subject: |
|
|
I was always aiming at MIT but I just wasn't sure. Thanks!
|
|
| Back to top |
|
|
| Page 1 of 1 |
All times are GMT + 1 Hour |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB 2.0.8 © 2001, 2002 phpBB Group
|
|
 |
|
