The anti crunch hours license
github.com
The anti crunch hours license
1–10 of 140 posts
Re: The anti crunch hours license
#2Ah, yet another "open-source if you follow my principles" license. It should be an uninteresting fact at this point that yes, you can in fact put whatever clauses you want in your software license.
Note that this is a license restriction addon, not a standalone license. To use, ammend to and reference by another license. Note that this removes "open-source" status from the original license if it is open-source, according to OSI's "No Discrimination Against Persons or Groups" definition.
Re: The anti crunch hours license
#3This license excludes any company that practices a 10x4 (10 hours for 4 day a week) work schedule which positive things have been said about previously. Also excludes companies with hourly jobs that work more than 45 hours but get paid 2/3x for extra hours. A lot of government agencies with unions have employees that love doing that since it gives them a lot of money.
edit: Hospitals as well since employees work odd shifts such as 2 weeks on and 2 weeks off for ER doctors, or 6 days in a row for lab technicians (with more days off every other week), etc.
Re: The anti crunch hours license
#4Similar comments made about the "No Evil" license apply: https://wiki.debian.org/qa.debian.org/jsonevil
Re: The anti crunch hours license
#5This license excludes any company that practices a 10x4 (10 hours for 4 day a week) work schedule which positive things have been said about previously. Also excludes companies with hourly jobs that work more than 45 hours but get paid 2/3x for extra hours. A lot of government agencies with unions have employees that love doing that since it gives them a lot of money. edit: Hospitals as well since employees work odd…
It's a hard problem. To cover all such cases, the license would essentially have to be as complex as a developed country's labour laws. But adding complexity adds loopholes that could be exploited, for instance if a rule just allowed "working more than 45 hours for 2/3x overtime pay", a company could just reduce the main pay by two thirds for non-overtime work. Countering this might require some reference to local minimum wages or average wages, which makes the license significantly more complex to apply across jurisdictions.
Re: The anti crunch hours license
#6You have no clue why someone is working more than 10 hours consecutively or more than 45 hours a week. Maybe that's something they're being paid quite well to do, and maybe they want to do so. This type of restriction just screams "I want to feel like a good person."
You're within your rights to use this restriction, but it's equally as ridiculous as a restriction forcing employees not to eat toast on Tuesdays, Wednesdays, or Thursdays.
I hope this doesn't catch on.
Edit: If the main target here is China, how much do you really believe Chinese companies care about Western copyright laws?
Re: The anti crunch hours license
#7Ah, yet another "open-source if you follow my principles" license. It should be an uninteresting fact at this point that yes, you can in fact put whatever clauses you want in your software license. Note that this is a license restriction addon, not a standalone license. To use, ammend to and reference by another license. Note that this removes "open-source" status from the original license if it is open-source, accor…
Why would anyone care about a bunch of OSI apparatchiks?
The people who talk loudest about Open Source always manage to get a position that profits from the labor of the actual authors.
Re: The anti crunch hours license
#8Ah, yet another "open-source if you follow my principles" license. It should be an uninteresting fact at this point that yes, you can in fact put whatever clauses you want in your software license. Note that this is a license restriction addon, not a standalone license. To use, ammend to and reference by another license. Note that this removes "open-source" status from the original license if it is open-source, accor…
Why would anyone care about the opinion of OSI?
The people who talk loudest about Open Source always manage to get a position that profits from the labor of the actual authors.
Re: The anti crunch hours license
#9You have no clue why someone is working more than 10 hours consecutively or more than 45 hours a week. Maybe that's something they're being paid quite well to do, and maybe they want to do so. This type of restriction just screams "I want to feel like a good person." You're within your rights to use this restriction, but it's equally as ridiculous as a restriction forcing employees not to eat toast on Tuesdays, Wedne…
Right, this is perhaps the fundamental objection to social-good software licenses: how many people who don't engage in social good do respect copyright?
The GPL works because it's pretty unambiguous about what exactly your obligations are, it's pretty unambiguous when there's a violation of those obligations, and because there are entities that do care deeply about copyright (like, oh, Microsoft and Oracle and IBM) that you'd like to affect.
Any license of the form "You must not use this code to wage war." is not going to get respected. The military doesn't care if you sue them.
Any license of the form "You must obey laws" (like this one, "The above license is only granted to entities that act in concordance with local labor laws") is not going to get respected. Either the entity was going to obey laws, in which case it's redundant, or they weren't, in which case what do they care about copyright.
Any license that's five lines long and tells a US court they have to decide whether a Chinese entity is complaint with Chinese labor law is just ... not going to work the way you want it to.
Any license that restricts use and not distribution has the practical problem of being difficult to enforce. If your code runs inside Palantir's systems or on a Patriot missile or as part of the PRISM backend, how will you ever know? The AGPL skirts this line by retaining the "distribution" concept and just defining networked use as distribution (and I think even that is questionable) but anything where you're not actually seeing the infringement is not going to be feasible to enforce.
Re: The anti crunch hours license
#10Before this comment section gets any more toxic, please understand the context.
The org on GitHub that developed this license is called 996ICU (https://996.icu/#/en_US). It is a (very large) group of Chinese developers that are upset with the common practice of working 9am to 9pm, 6 days a week.
Please be mindful of the fact that lots of developers around the world work under genuinely awful conditions, and that your (x times y) work week is a privilege earned by a long history of labour activism in the Western world.
(P.S. This is a protest, not a legally binding license)