The alternative would be to hire one or two developers on our own for support, and then the cost savings would be out the door. Maybe this library is more performant, but it's a (relatively) small piece of the industrial control scheme. A massive shift like this is just not something companies will take a risk on.
Apache PLC4X announcing end of community support due to missing funding
101–110 of 162 posts
Re: Apache PLC4X announcing end of community support due to missing funding
#102Developments like this one and the faker.js and colors.js fiasco from last week have made me rethink my position about licensing. Now it seems to me that releasing code you wrote for free under a permissive open-source license is somewhere between ill-advised and unethical. On one hand it will not benefit you in any way, on the other, it will be incorporated in a company's proprietary project thus lowering the expens…
It takes a lot of effort and money to enforce copyleft open source licenses, a lot of companies just violate them regardless. Some companies even violate permissive licenses, for eg my router violates the microhttpd BSD license. The latest GPL lawsuit I saw was only possible due to a large grant from amateur radio hobbyists. https://sfconservancy.org/copyleft-compliance/vizio.html https://sfconservancy.org/press/qand…
Re: Apache PLC4X announcing end of community support due to missing funding
#103A good compromise for this kinds of things is usually dual licensing: - If you're big enough to make real money and you need my attention then pay me this much please - If you're some rando with a toy project, then we have a github issue tracker A project this size and age should always have a lawyer at hand just in case, and they should be able to walk the maintainers through the process of dual-licensing everything…
Dual licensing means that there are two licenses that the user can choose from at their discretion. This is why GPL may work together with a commercial license but not MIT, as businesses have reasons to avoid GPL.
Re: Apache PLC4X announcing end of community support due to missing funding
#104Earlier quoted context omitted.
Maybe. Or maybe you are just helping the rich get richer and the poor get poorer. Whether proprietary software is a force for good or just another mechanism of exploitation is a matter of opinion, and the GP might not share yours.
As a child starting from $0 I built up almost all of the money I have now doing contract work by making closed source software using open source software. Being able to quickly make things without even having to spend any money is great for someone with no money. It didn't make me poorer as someone with $0, it made me much richer. I know my software was a positive to the lives of many people even if it is closed sour…
Re: Apache PLC4X announcing end of community support due to missing funding
#105Earlier quoted context omitted.
> I don't see where it is not ethical. And that's the problem. Many people like the idea of 'helping' other people for free, even if these users never 'give something back' (because they can't program, don't have the time to translate something, ...). But helping other people (companies) make money for free that already have not only enough but way more than you, and you even do the less rewarding work like fixing bu…
At my company, a huge bank, where we use a ton of open source code, we were explicitly told that working on (contributing to) open source was a terminal offense.
Re: Apache PLC4X announcing end of community support due to missing funding
#106Just quoting this snippet from the landing page: "No license costs, no restrictive licenses. Being open source, PLC4X is free of charge. Start experimenting without worrying about license costs or shady license agreements. The Apache 2.0 is one of the worlds most trusted and adopted open source licenses out there." Big companies need to grow up and start contributing with serious amounts. I wonder how this could get…
I started a poll [1] asking if devs could get their employers to pay. Almost nobody answered. I'm not sure it would be possible to get companies to pay without regulation, as you say.
Re: Apache PLC4X announcing end of community support due to missing funding
#107Earlier quoted context omitted.
It takes a lot of effort and money to enforce copyleft open source licenses, a lot of companies just violate them regardless. Some companies even violate permissive licenses, for eg my router violates the microhttpd BSD license. The latest GPL lawsuit I saw was only possible due to a large grant from amateur radio hobbyists. https://sfconservancy.org/copyleft-compliance/vizio.html https://sfconservancy.org/press/qand…
Even so, I'd assume that a company that knowingly infringes on the GPL is much less likely to demand free support, lest they draw attention to their violation. So at the very least it should free maintainers from having to deal with bug reports/feature requests/entitled demands from corporate entities that refuse to give back.
Re: Apache PLC4X announcing end of community support due to missing funding
#108geee ... a friend pointed me here and I have to admit that I'm quite overwhelmed by the wave my post generated. But very happy it seeded some good discussions.
However I should point out that only I said that I would stop providing free community support. I am only one of the contributors. Even if I am probalby one of the most active ones, there are still others probably going to step up and tackle the one or the other issue someone might come up with.
If the project was just me, Apache would probably have already moved the project into the atic, which is far from happening :-)
Now I'll continue reading all of this ... but I had to set this straight first.
Chris
Re: Apache PLC4X announcing end of community support due to missing funding
#109Re: Apache PLC4X announcing end of community support due to missing funding
#110A good compromise for this kinds of things is usually dual licensing: - If you're big enough to make real money and you need my attention then pay me this much please - If you're some rando with a toy project, then we have a github issue tracker A project this size and age should always have a lawyer at hand just in case, and they should be able to walk the maintainers through the process of dual-licensing everything…
What you suggest is not really dual licensing though. It's a source-available license with a free tier. Dual licensing means that there are two licenses that the user can choose from at their discretion . This is why GPL may work together with a commercial license but not MIT, as businesses have reasons to avoid GPL.