this post was submitted on 18 Feb 2024
149 points (98.7% liked)
Python
6375 readers
20 users here now
Welcome to the Python community on the programming.dev Lemmy instance!
๐ Events
Past
November 2023
- PyCon Ireland 2023, 11-12th
- PyData Tel Aviv 2023 14th
October 2023
- PyConES Canarias 2023, 6-8th
- DjangoCon US 2023, 16-20th (!django ๐ฌ)
July 2023
- PyDelhi Meetup, 2nd
- PyCon Israel, 4-5th
- DFW Pythoneers, 6th
- Django Girls Abraka, 6-7th
- SciPy 2023 10-16th, Austin
- IndyPy, 11th
- Leipzig Python User Group, 11th
- Austin Python, 12th
- EuroPython 2023, 17-23rd
- Austin Python: Evening of Coding, 18th
- PyHEP.dev 2023 - "Python in HEP" Developer's Workshop, 25th
August 2023
- PyLadies Dublin, 15th
- EuroSciPy 2023, 14-18th
September 2023
- PyData Amsterdam, 14-16th
- PyCon UK, 22nd - 25th
๐ Python project:
- Python
- Documentation
- News & Blog
- Python Planet blog aggregator
๐ Python Community:
- #python IRC for general questions
- #python-dev IRC for CPython developers
- PySlackers Slack channel
- Python Discord server
- Python Weekly newsletters
- Mailing lists
- Forum
โจ Python Ecosystem:
๐ Fediverse
Communities
- #python on Mastodon
- c/django on programming.dev
- c/pythorhead on lemmy.dbzer0.com
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
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Does the LGPL really allow that or did they make all the contributors agree to allow their code to be relicensed?
Previous versions licensed under LGPL will remain licensed as such. The current maintainers have no obligation to contribute distributing the older versions, but they aren't permitted to prevent others from distributing it or modifying or doing anything else that was permitted by the license.
And, yes, to change from GPL/LGPL to another license you would need all of the contributors to consent, or to rewrite the parts that were contributed by anyone who doesn't agree with the license change. Since it looks like there only one contributor according to the GitHub page, this probably wasn't too difficult.
Was there only ever one contributor? There's only one now, but all the old commits have been removed.
They apparantly had a police of not accepting merge requests or even code snippets.
Ahh huh, I wonder if this was the plan the whole time then
Hmm thatโs a scary conspiracy. Seems like checking that there are at least a handful of contributors needs to be part of adding new dependencies.