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.

You are viewing a single thread.
View all comments
94 points
*

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

permalink
report
reply
41 points
*

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.

permalink
report
parent
reply
13 points

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.

permalink
report
parent
reply
7 points

Can’t anyone just fork one of the LGPL versions and start a new project?

permalink
report
parent
reply
5 points

@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.

permalink
report
parent
reply
12 points

Never sign over copyright. If they didn’t, they can sue.

permalink
report
parent
reply
7 points

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.

permalink
report
parent
reply
5 points

If any contributors haven’t signed a contract letting them close the source, this opens them up to lawsuits.

permalink
report
parent
reply

Python

!python@programming.dev

Create post

Welcome to the Python community on the programming.dev Lemmy instance!

📅 Events
October 2023
November 2023
Past

July 2023

August 2023

September 2023

🐍 Python project:
💓 Python Community:
✨ Python Ecosystem:
🌌 Fediverse
Communities
Projects
  • Pythörhead: a Python library for interacting with Lemmy
  • Plemmy: a Python package for accessing the Lemmy API
  • pylemmy pylemmy enables simple access to Lemmy’s API with Python
  • mastodon.py, a Python wrapper for the Mastodon API
Feeds

Community stats

  • 428

    Monthly active users

  • 443

    Posts

  • 2.1K

    Comments