Previously LGPL, now re-licensed as closed-source/commercial. Previous code taken down.
Commercial users pay $99/year, free for personal use but each user has to make a free account after a trial period.
Previously LGPL, now re-licensed as closed-source/commercial. Previous code taken down.
Commercial users pay $99/year, free for personal use but each user has to make a free account after a trial period.
If this project has other contributors, imagine how betrayed they must be.
Opening the project as FOSS until it becomes popular and then closing it to make money is such a scummy tactic
If any contributors haven’t signed a contract letting them close the source, this opens them up to lawsuits.
Never sign over copyright. If they didn’t, they can sue.
I’ve had to sign specific paperwork regarding copyright for just big projects, many smaller ones take contributions without paperwork, which would leave the rights with each contributor. They be better dot their i’s and cross their t’s, it just the legal fees could isnk them before making any money from the commercial license.
IANAL, just in case.
Fork the last commit with a LGPL commit?
GPL mentions explicitly that it is irrevocable, where as LGPL doesn’t mention anything about it. IANAL, but it looks like there is a case for irrevocable without violation of clauses by default https://opensource.stackexchange.com/questions/4012/are-licenses-irrevocable-by-default#4013
For people considering contributing to FOSS in the future, maybe check for irrevocable clauses? I wish licenses selectors https://choosealicense.com highlighted this part more clearly.
Also depends on the contributions terms.
If they were a traditional FOSS, they can’t change the terms without all contributors agreeing or removing/modifying the contributed code so that they no longer have ownership of their authored sections.
Either way, it’s a dick move.
Can’t anyone just fork one of the LGPL versions and start a new project?
@fidodo @SkyNTP It has already happened https://github.com/andor-pierdelacabeza/PySimpleGUI-4-foss
@fidodo @SkyNTP Sure, but unless that someone keeps it updated that fork will be useless soon. And that looks like a lot of (unpaid) work.
I like the project (was surprised to even see my user name in the contributor list) but stopped using it because I couldn’t get accessibility working (mainly no full keyboard shortcuts).
For me, buying a yearly developer license to have a few GUI pop-ups at work is something I’ll only consider if I run out of options.