top 50 comments

sorted by: hot top controversial new old
[–] 173 points 2 years ago (3 children)

Ok, I might be misunderstanding here, but since committing changes is allowed for everyone, doesn't this mean fixing bugs is something you could do? You'd just be stuck with all the other rights as well until someone else makes a change.

  • source
  • hideshow 6 child comments
  • [–] 89 points 2 years ago* (6 children)

    The main dev made the last commit, so they dont have the right to make another commit, until they arent the last person to make a commit anymore (until someone else has made a commit). This makes sure that there are at least 2 people making commits but hopefully much more.

    In other words, making a commit revokes your right to do so until someone else makes a commit.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 87 points 2 years ago (2 children)

    Am I just bad at reading? It says the right to make changes is granted to everyone one Earth. That would include the last person to make a commit as well, assuming they're a citizen of Earth. I'm sure what you're saying is what it's supposed to say, but it isn't actually what it says.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 39 points 2 years ago (1 child)

    All rights reserved by......, except the right to commit to this repository.

    Being a legal license it requires much more rigorous and clear statement

  • source
  • parent
  • hideshow 2 child comments
  • [–] 44 points 2 years ago (3 children)

    You can't just ignore the second part of that sentence which gives the right to make commits to all citizens of earth. That would include the person who wrote the last commit.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 23 points 2 years ago (1 child)

    Yeah, that should read "all other citizens of earth".

  • source
  • parent
  • hideshow 2 child comments
  • [–] 23 points 2 years ago (1 child)

    I'm pretty sure it means exactly what it says, but you lot are all misreading it.

    I interpret it as "all rights, except the right to commit, are reserved" (which doesn't mean you surrender the right to commit, but rather that it's the only right you aren't depriving everyone else of)

  • source
  • parent
  • hideshow 2 child comments
  • [–] 12 points 2 years ago (1 child)

    And I'm pretty sure that the name "hot potato license" and the comment above the license are very strong indicators for this not being the case. The license is meant to mimic a game of hot potato where you get the code for a short moment (one commit) and have to throw it to someone else. Sure, the analogy doesn't quite work because you can't decide who has to make the next commit but it would make even less sense if you were able to keep control over the code and add more and more commits. That would defeat the whole point of naming it "hot potato license".

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (1 reply)
  • load more comments (1 reply)
  • load more comments (4 replies)
  • [–] 31 points 2 years ago

    the fact that there are this many people having different interpretations shows that the license would need waaaaaay clearer wording to hold any sort of water.

    this is why i hate licenses like WTFPL and its ilk, just saying "do whatever" cannot possibly be legally viable and thus using anything with such a license is impossible by anyone who cares about copyright law (such as say, companies).

    If you want your creations to be free for all to use, just slap a fat CC0 on it.

  • source
  • parent
  • [–] 103 points 2 years ago (1 child)

    But in a moment of legal discovery, it was found that "GitLab Support Bot" always owns the repository since it creates the merge commit after CI runs.

  • source
  • hideshow 2 child comments
  • [–] 21 points 2 years ago (1 child)
    1. The bot is not a person and this cannot have the rights
    2. Just don't use something as fancy as that. CI for a HLP project? Wth are you doing, there aren't even tests
  • source
  • parent
  • hideshow 2 child comments
  • [–] 61 points 2 years ago (1 child)

    "It's not my code" "It is now!"

  • source
  • hideshow 2 child comments
  • [–] 56 points 2 years ago

    This is how I handle code at work, almost. Program not working? Who has the last commit on the code? You get the question!

  • source
  • [–] 53 points 2 years ago (1 child)

    Way to discriminate against future people on Mars.

  • source
  • hideshow 2 child comments
  • [–] 41 points 2 years ago (1 child)

    There are a few flaws.

    There should be a clause forcing it to remain open source. Another clause should be that the license must not be changed. A warrenty and liability disclaimer would be also good. Otherwise a splendid license.

  • source
  • hideshow 2 child comments
  • [–] 37 points 2 years ago (3 children)

    As a Martian I feel left out.

  • source
  • hideshow 6 child comments
  • [–] 9 points 2 years ago (2 children)
  • [–] 29 points 2 years ago

    The secret license everyone gets while working for an enterprise. If the previous dude left, good luck changing anything.

  • source
  • [–] 24 points 2 years ago* (1 child)

    git commit --amend

    git push --force

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 23 points 2 years ago
    [–] 22 points 2 years ago (4 children)

    What happen when the repository is getting forked? Goofing with the license is all haha fun till nasty lawyers get into the picture and you get all sort of liability claims

  • source
  • hideshow 7 child comments
  • [–] 57 points 2 years ago (4 children)

    Just writing words doesn't make it legally binding. Anyone who reads this comment owes me $1,000,000 USD.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 41 points 2 years ago* (3 children)

    Oh shit, what's your PayPal?

    Anyone who reads this comment owes me $1,000,000 USD and a kiss

  • source
  • parent
  • hideshow 6 child comments
  • [–] 21 points 2 years ago (1 child)

    I don't have 2 mil, how do I get out of this? File for bankruptcy?

  • source
  • parent
  • hideshow 2 child comments
  • Ofcourse its legally binding. If you include a license text with your own code on a platform that doesnt have a clause to license your code under different terms, then that license is legally valid.

    But writing the license yourself without making sure that it doesnt allow for any legal loopholes is a bad idea.

  • source
  • parent
  • load more comments (2 replies)
  • load more comments (1 reply)
    [–] 15 points 2 years ago

    So that's the legal equivalent of the guy committing 10k changes the day before leaving the company...

  • source
  • load more comments
    view more: next ›