Am Thu, May 28, 2026 at 11:06:22PM +0900 schrieb Maxim Cournoyer: > "cannot be considered free software" is preposterous, no? We have > doubts, but no certainty as of now. For our own source code, it seems > wise to avoid the uncertainty creeping in, but for packages... I think > given the gray area, and the low risk of it (we can easily remove such > packages if/when it becomes clear that they aren't free software)
This is a claim that I think is not correct. In a sense, we can only go forward. Of course *theoretically*, we can take out any package; but things become complicated as soon as dependents enter the game (and it has taken a bit of effort to work on the question for GCD 006, and each and every package removal means additional work). And also think of updates - the vibe coding could happen between version X-1 and version X of a package. It may be very difficult to downgrade (already our user tools are not designed for this). Just imagine that we decided we wanted to roll back the Python 3.11 to 3.12 transition - I think it is close to impossible. So I would suggest to rather err on the side of caution here. Andreas
