✅ Relicensing a brand new project from LGPLv2.1 to LGPL3
I just realized something while working on my project - I have no idea how I ended up doing this, but I seem to have licensed it everywhere as LGPLv2.1 - on GitHub, on its NuGet packages, etc etc. To my understanding, it's heavily preferred to license new works under LGPLv3 instead - how should I go about doing this fix? I'm the only person who has worked on this project at all to this point, so there shouldn't theoretically be any issues with getting consent for a relicense...right?
I'm not sure if I'd be safe to just...relicense it willy nilly on github by changing the LICENSE file, but...what about the packages? should I push a new (patch? major??) version with the new license? replace the original published package (if possible?) with the re-licensed one? I mean...I literally uploaded the only packages about an hour or two ago.
I'm not sure if I'm just overthinking things, or if I should be nuclear and safe and start everything from scratch again - delete and recreate the repo and all that.
2 Replies
if you are the sole contributor to the project so far, you have complete copyright on it, and could change the license to whatever you wanted for future versions of the project
you would need to upload a new version of the package, I think
Yeah, I can't delete the current version (only unlist), and it would violate semver to replace it, so nuget doesn't allow it
guessssss I'll post a 1.1.0 version with the license change
that's fine and understandable. It...really doesn't affect me much at this point, but thought I'd nip that in the bud
interestingly, the reason this happened is...GitHub only offers an LGPLv2.1 license template, and not a 3.x one, and I was not paying attention when I added it 😅
![BlobShrug](https://cdn.discordapp.com/emojis/767219268671897661.png)