The anti crunch hours license • Hacker News Board

Re: The anti crunch hours license

#21

Post by xnn » Sat, Mar 30, 2019, 2:25 PM UTC

vortico wrote: post #15

wqedwed wrote: post #8

Earlier quoted context omitted.

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.

>Why would anyone care about the opinion of OSI? Their opinion is not relevant. What is relevant is whether their definition of open-source ( https://opensource.org/osd ) is close to the ideals of developers. And it suffices for me and many others. Your second sentence is nonsense.

> Your second sentence is nonsense.

No it is not. But I see that you are a "founder" and thus profiting from my work. Your opinion is self-serving and meaningless.

Re: The anti crunch hours license

#22

Post by vortico » Sat, Mar 30, 2019, 2:27 PM UTC

xnn wrote: post #21

vortico wrote: post #15

Earlier quoted context omitted.

>Why would anyone care about the opinion of OSI? Their opinion is not relevant. What is relevant is whether their definition of open-source ( https://opensource.org/osd ) is close to the ideals of developers. And it suffices for me and many others. Your second sentence is nonsense.

> Your second sentence is nonsense. No it is not. But I see that you are a "founder" and thus profiting from my work. Your opinion is self-serving and meaningless.

Please use your main HN account. Temporary accounts for the purpose of hiding will continue to be banned.

Re: The anti crunch hours license

#23

Post by balfirevic » Sat, Mar 30, 2019, 2:33 PM UTC

I-Iuw wrote: post #10

Before 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 yo…

> Before this comment section gets any more toxic, please understand the context.

Comment section is not "toxic" just because it expresses the notion that this license is useless, nonsensical, stupid or any other thing you disagree with. Even if commenters might have missed the point.

Re: The anti crunch hours license

#24

Post by jimnotgym » Sat, Mar 30, 2019, 2:36 PM UTC

rbohac wrote: post #14

so hospitals can never use this? their doctors and nurses, who are "employees" regularily work 12 hour shifts. the same goes for first responders

I hope so. Hospitals make their staff work counter-productive hours, as if they couldn't function with 8 hour shifts.

And you don't need to put double quotes around employees. They are employees and deserve to work in a good environment like everyone else

Re: The anti crunch hours license

#25

Post by zzzcpan » Sat, Mar 30, 2019, 2:39 PM UTC

vortico wrote: post #2

Ah, 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…

It removes the status of OSI approved license if it used such license, because it becomes a different license, but it's still what people usually call open source. And it doesn't matter if you don't like the common meaning of open source, which has nothing to do with OSI's own definition.

Re: The anti crunch hours license

#26

Post by vortico » Sat, Mar 30, 2019, 2:45 PM UTC

zzzcpan wrote: post #25

vortico wrote: post #2

Ah, 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…

It removes the status of OSI approved license if it used such license, because it becomes a different license, but it's still what people usually call open source. And it doesn't matter if you don't like the common meaning of open source, which has nothing to do with OSI's own definition.

What bullet points does your "common meaning of open source" disagree with in https://opensource.org/osd?

Re: The anti crunch hours license

#27

Post by rqs » Sat, Mar 30, 2019, 2:45 PM UTC

TheCoreh wrote: post #18

I live in Brazil. Under Brazilian labor laws, a work week is defined as 44 hours, with each work day having up to 8 hours. So you just excluded companies that have ever had anyone do more than one hour of (paid) overtime any week. Which is basically every company in my country, considering (occasional, paid) overtime is normal and predicted in the relevant laws. Here, 12 hour shifts with 36 hour rest periods is also…

I think this worry is reasonable.

Maybe you can try to file a pull request to suggest a change, remember to explain your situation and concerns inside the pull request so it won't be discarded.

Re: The anti crunch hours license

#28

Post by rqs » Sat, Mar 30, 2019, 2:48 PM UTC

vortico wrote: post #2

Ah, 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…

> Note that this removes "open-source" status from the original license if it is open-source

From what I can read, that's the plan. After all "open-source" or not is pointless when developers are on the bed inside of ICU :D

Re: The anti crunch hours license

#29

Post by zzzcpan » Sat, Mar 30, 2019, 2:50 PM UTC

vortico wrote: post #26

zzzcpan wrote: post #25

Earlier quoted context omitted.

It removes the status of OSI approved license if it used such license, because it becomes a different license, but it's still what people usually call open source. And it doesn't matter if you don't like the common meaning of open source, which has nothing to do with OSI's own definition.

What bullet points does your "common meaning of open source" disagree with in https://opensource.org/osd ?

It's irrelevant if you don't want to recognize, that people usually don't use OSI's definition when they talk about "open source".

Re: The anti crunch hours license

#30

Post by captainbland » Sat, Mar 30, 2019, 2:50 PM UTC

geofft wrote: post #13

wqedwed wrote: post #8

Earlier quoted context omitted.

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.

Don't create new accounts to work around bans. However, since your question is one that comes up a lot (though, perhaps, only from your accounts), I'll answer it as if it's in good faith and not downvote / flag your comment. The Open Source Definition is not at all the opinion of OSI. It was taken word-for-word from the Debian Free Software Guidelines, with some minor editorial changes to make it more generic than ju…

Well, it might also be that you actually want many people to be able to use, learn and understand your software freely but you also don't want your software to be installed on a military drone or used to enable a company that is working its employees to death. Not everything is profiteering and marketing.