this post was submitted on 18 Feb 2024
149 points (98.7% liked)

Python

6394 readers
10 users here now

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

πŸ“… Events

PastNovember 2023

October 2023

July 2023

August 2023

September 2023

🐍 Python project:
πŸ’“ Python Community:
✨ Python Ecosystem:
🌌 Fediverse
Communities
Projects
Feeds

founded 1 year ago
MODERATORS
149
submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/python
 

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 comment's thread
view the rest of the comments
[–] [email protected] 5 points 9 months ago (1 children)

This is so sad. I'm especially bothered about the force push to change history. This was a great library. Now I guess it's time to either use the fork or find something else.

[–] MadhuGururajan 4 points 9 months ago (1 children)

The history change was probably to avoid violating the LGPL. If any contributors don't agree with the change (or you don't want to do the onerous task of getting consensus as required) you should remove their contributions from the work you make closed source as the contributions still come under LGPL until the original author consents to the change.

Or at least that's what people said here.

[–] [email protected] 4 points 9 months ago

That's incorrect in that you have to remove the contributions from source code or get permission. Rewriting git history doesn't get permission or remove history. It just hides it.