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.
this post was submitted on 27 May 2024
1091 points (99.4% liked)
Programmer Humor
19551 readers
597 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
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.
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.
All rights reserved by......, except the right to commit to this repository.
Being a legal license it requires much more rigorous and clear statement
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.
Yeah, that should read "all other citizens of earth".
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)
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".
load more comments
(1 replies)
Are you doxing OOP right now??? How do you know they life on earth?
Thats why I said it needs to be more rigorous. The license probably meant Everyone in the earth except the last person who commited to it
load more comments
(1 replies)
That may be what they meant, but that's not what it says.
load more comments
(4 replies)
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.
Yeah, the problem with the proposition is that you have all rights and access to the code regardless of who made the last commit, unless the last person to commit revoked the HPL.
load more comments
(1 replies)
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.
- The bot is not a person and this cannot have the rights
- Just don't use something as fancy as that. CI for a HLP project? Wth are you doing, there aren't even tests
You don't have to be a person to have the rights of a person. That's what a corporation is.
But the license mentions all of earths citizens. Corpos can't be citizens, right? Legal terms are confusing.
load more comments
(3 replies)
This is how I handle code at work, almost. Program not working? Who has the last commit on the code? You get the question!
Way to discriminate against future people on Mars.
The Musk followers? Good.
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.
I would 100% use this HPL-v2 for all of my (temporary) foss projects. It's just genius. I mean, good luck keeping track of the current owner, Nintendo lawyers.
As a Martian I feel left out.
What should I say??
Nah, we're alright. I don't think anyone has clearly defined the requirements of earth citizenship, we can assume it's like Ireland who hand it out like candy
Share water, brother.
I grok
The secret license everyone gets while working for an enterprise. If the previous dude left, good luck changing anything.
git commit --amend
git push --force
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
Just writing words doesn't make it legally binding. Anyone who reads this comment owes me $1,000,000 USD.
Oh shit, what's your PayPal?
Anyone who reads this comment owes me $1,000,000 USD and a kiss
I don't have 2 mil, how do I get out of this? File for bankruptcy?
on a technicality, debts like this are not legally dischargable through bankruptcy
If anyone I owe money to reads this, the debt is reversed.
I'll take the kiss though
I don't have the money, can I kiss you twice instead?
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.
You declaring a debt isn't meaningful because you don't have legal authority to do so.
A licence statement is describing in what way you're granting permission for something you do have the right to control, which makes it meaningful
load more comments
(1 replies)
If you want to fork the repo then you make a commit to the original repo giving yourself rights then you make the fork and you’re golden.
load more comments
(1 replies)
I think this is a sort of anti-license, so I think the sort of people who use it reject copyright law.
load more comments
(1 replies)
load more comments
(1 replies)
So that's the legal equivalent of the guy committing 10k changes the day before leaving the company...
view more: next ›