98
"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 7 months ago by to c/technology@lemmy.ml
53 comments fedilink hide all child comments
 

cross-posted from: https://lemmy.ml/post/44059967

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

cross-posted from: https://lemmy.bestiver.se/post/968527

HN comments

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 7 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 7 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 7 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