91
"No right to relicense this project" - on changing the license of Mark Pilgrim's chardet from LGPL to MIT after a vibe-coded rewrite (github.com)
submitted 8 months ago by to c/technology@lemmy.ml
54 comments fedilink hide all child comments
 

for those not familiar with Mark Pilgrim, he is/was a prolific author, blogger, and hacker who abruptly disappeared from the internet in 2011.

HN comments

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 8 months ago (9 children)

Look at the number of MIT projects with such founding and contributions. Compare them to copy left projects.

What you will find is, that copy left projects have far more backing, financial support and contributions.

There are studies on this...

Qnd to keep Microsoft as an example. If the kernel would be permissive, what would Microsoft stop from using it, adding some property stuff on it and use their monopoly to force those feature everywhere.

Now they have taken the work of thousands of contributors and take all the money.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 9 child comments
    •
  • [–] 1 point 8 months ago (8 children)

    Now they have taken the work of thousands of contributors and take all the money.

    I have no problem with it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 2 points 8 months ago* (7 children)

    Did you contribute to the kernel? Because, I for sure have a problem with it. And I did contribute.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 1 point 8 months ago (6 children)

    Well at first, nice that we have a kernel developer here, it's not so easy to get your code into. And second, nope, I do not contributed to the kernel. I once wrote a module for educational purposes a long long time ago. Then FUSE came along and it helped me to solve the task with "more comfort".

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 2 points 8 months ago (5 children)

    I did contribute once. And it was a pain. 20 lines of code but hours of work, Mailinglists, feedback, ...

    Don't het me wrong , it was fun. But would I have done the same for BSD, so that apple could use this? Hell no

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 1 point 8 months ago (4 children)

    Perhaps this is our fundamental difference. I write code, solve my small task and have fun by doing it. If someone can get something of it, it's twice as nice.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 8 months ago (3 children)

    And that's fine. And everybody should license his code as he likes.

    But my point stands. String copyleft is important.

    That does not mean that LGPL is always a good idea, and charted is a good example, as the python stdlib is MIT licensed, and therefore an LGPL charted has no chance of getting accepted.

    Btw, the easiest first step would have been: mail every contributor (there are not that many in that case) that provided more then hast some minor fixes and ask for permission. That is a valid way to change the license.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 8 months ago (2 children)

    I agree at the point, that everyone should use that license he like.

    Btw, the easiest first step would have been: mail every contributor (there are not that many in that case) that provided more then hast some minor fixes and ask for permission. That is a valid way to change the license.

    No, I think, that would not work this way, you have to ask every contributor, no matter how big the influence was. And everyone must agree unanimously. It's almost an impossible task.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 8 months ago

    I agree regarding consesus. Unlikely, but: heaving major contributions greenlighted and only replace parts of the code are fat note feasible.

    No communication happened to my understanding at any point with any contributor.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 8 months ago

    You don't need it to be unanimous, but if it's not unanimous, you have to rewrite the parts from people who refused or can't be contacted. If their sum contributions aren't too big, it can be feasible but a lot of work. If too many or if key contributors refuse, the work can scale exponentially.

  • permalink
  • fedilink
  • source
  • parent