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.
post
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.
"It's not my code" "It is now!"
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.
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.
As a Martian I feel left out.
Them dusters always complaining about something smh
What should I say??
Luckily for you, there's a version 2!

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
Ah, the student loan loophole
If anyone I owe money to reads this, the debt is reversed.
I'll take the kiss though
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.
I think this is a sort of anti-license, so I think the sort of people who use it reject copyright law.
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.
So that's the legal equivalent of the guy committing 10k changes the day before leaving the company...

top 50 comments