9 ms·
This seems to mostly be a policy piece, targeted at political folks rather than technical ones. The laborious establishment of a couple analogies was particular
by bee_rider 4y ago
This seems to mostly be a policy piece, targeted at political folks rather than technical ones. The laborious establishment of a couple analogies was particularly hard to get through, but I suppose it will be useful for the target audience.
A concern with this sort of thing is that it will have weird expectations about developer responsibility in securing the, as they like to call it, “software supply chain.” It was nice to see that that they reiterated the open source developers basically have no responsibility.
I don’t see too much objectionable here, no idea if they proposals would actually help but they seem mostly harmless.
An analogy that occurred to me while reading was: open source developers could be seen as more like a natural resource, something like wild animals. In particular wild bees. People don’t really expect bees to follow many instructions. You can set up nice places for them to put their hives. But mostly you should just leave them alone and be happy to collect the honey they produce, which they produce as a side effect of existing — you can check if you want to eat it.
- RobotToaster 4y ago>You can set up nice places for them to put their hives. Paying their rent would be a good start, and like bees, make them more productive.
- Dalewyn 4y agoI'm going to be that guy and point out that Free and Open Source are two related but separate concepts. An open source dev can still charge for his code, and should if he needs/wants to make a living off of it.
- deleted 4y ago[deleted]
- tremon 4y agoSo can a Free Software developer, so what point are you trying to make with your first sentence?
- Dalewyn 4y agoWe have no obligation to pay their rent because they explicitly waived such desires. EDIT: I realize I failed at reading comprehension. Apologies. Free-as-in-libre runs counter to asking for payment because they, as far as my layman understanding is concerned, are mutually exclusive. Code can't be free-as-in-libre if you have to pay monies to get any rights thereof. Open source, on the other hand, is just that: The source is open for viewing. You can read the code at your leisure, but what you can do with the code or the knowledge gained from reading it is an entirely different matter. So a free dev fundamentally can't charge for his code, but an open source dev can charge for his code.
- TeMPOraL 4y agoFree-as-in-libre means you don't have to pay for code itself, as it exists at a given moment. You can, but don't have to. However, that doesn't mean Free Software becomes completely detached from the economy - on the contrary, it's actually meant to empower the economy, in particular smaller and local economies. That's because labor isn't free. Say the code, as is, solves 90% of the problem. To get to 100%, you need some changes to be made. That is, you need to get someone - the original author(s), or a third party - to make them for you. They're not obliged to do it for free - only to release such changes for free to everyone's benefit. So you have to pay someone. The license just makes sure everyone benefits, and that incremental benefits need to be only paid for once. Additionally, code alone isn't a solution. Any kind of deployment, hosting, management, etc. involves labor, whether in-house, hired, or from a service provider. Again, the code commands money to be moved to those providing value by building up on it. The license only makes sure nobody gets to treat the code itself as their exclusively-owned capital.
- fsckboy 4y agono! free as in libre means free as in freedom like the word liberation, not anything to do with paying. because, it gives the user the freedom to use a program and then modify it to suit their own taste, and to give that same freedom to any person using their version.
- RobotToaster 4y ago>An open source dev can still charge for his code I see this said a lot, and it seems to be somewhat accepted, but I've always wondered, since point five of the OSI definition is: >No Discrimination Against Persons or Groups Would this not technically count as economic discrimination?
- Dalewyn 4y agoIt's not discrimination because everyone has to pay the price tag. Equality is about equal opportunities, not equal outcomes. That said, commercial open source software by and large fail because the primary reason people want open source software is because they all tend to be free-as-in-beer. Nobody truly cares about libre and cooperation and auditing, it's all about the monies. Don't believe me? The first thing nearly all large-scale FOSS deployments tout is how much they will save in Windows and Office licenses.
- codeguro 4y agoRMS cares quite a bit about it, as do I. You don’t talk for everybody.
- eyelidlessness 4y agoHow would it?
- AndyMcConachie 4y agoThe Atlantic Council doesn't care about this distinction, nor should they.
- abdullahkhalids 4y agoMany countries like to ensure a certain level of food security by growing essential foods domestically or importing them from good allies. Yet, farmers also don't have any responsibility. They only respond to incentives set up by the government.
- bee_rider 4y agoI mean, you can always quit your job of course, but if you sell food I guess you have some responsibility to make a reasonable effort to ensure it isn’t poisonous.
- ClumsyPilot 4y ago> Yet, farmers also don't have any responsibility. Em, no, your food has to adhere to numerous rules around use of pesticides, livestock loving conditions, disease (can't sell infected meat) and statutory reporting. Developers on the other hand have no responsebility about quality of their code, unless it's outright malevolent i.e. a virus
- abdullahkhalids 4y agoYes, but that's because farmers are selling the food. If developers sell software, they should be liable for providing software according to spec. In both case, the act of selling is done under an implicit or explicit contract. But if they are FOSS developers, there is no contract, because there is no exchange. In this case, developers should have about as much responsibility as say authors who write books for the public. They should be liable if they go out of their way to write harmful information/software, but if they took reasonable precautions, they should be fine.
- Dalewyn 4y ago>They should be liable if they go out of their way to write harmful information/software, In the interests of free speech I staunchly disagree. If someone writes a virus, that should not be a crime. If someone uses that virus to cause harm or damage, that should be a crime.
- deleted 4y ago[deleted]
- CGamesPlay 4y ago> open source developers could be seen as more like a natural resource, something like wild animals. In particular wild bees. > bee_rider On the internet, nobody knows you're a colony of bees!
- bee_rider 4y agoPerforms an incorrect dance in hopes of throwing you off my trail
- nine_k 4y ago«You can domesticate programmers the way beekeepers tame bees. You can't exactly communicate with them, but you can get them to swarm in one place and when they're not looking, you can carry off the honey.» (Orson Scott Card)
- swyx 4y agothats an interesting quote from him. i only ever knew him as a writer - did he manage programmers too?
- nine_k 4y agoIt looks like a piece of poetic fiction, appropriate for the author. The largest piece of context I could find online is [1], dated 1995, and written apparently earlier, at the time when programming was seen as wizardry, not really engineering, and definitely not as a knowledge-heavy but mundane money-making occupation, on par with a stock trader. [1]: https://www.netjeff.com/humor/item.cgi?file=DeveloperBees https://www.netjeff.com/humor/item.cgi?file=DeveloperBees
- movpasd 4y agoIt seems to me that there ought to be a principle of "opacity entails responsibility". An open-source project and its developers can easily claim to have no liability because it's possible for downstream users to fully inspect the source code. However, it's harder to argue the same thing for a closed-source product or service. If a company claims to provide a closed-source service according to certain specifications, and then fails to, then they're liable for that failure. In other words, if you want to fence your code off to more effectively generate profit from it, OK -- but now you are liable for any disasters caused by it. It becomes particularly interesting if and when a closed-source project depends on open-source dependencies upstream, especially if these dependencies are not declared. Can the downstream company then deflect responsibility? It seems that not. Of course, it's not a black and white thing. A developer that deliberately inserts malicious code into an open-source codebase should still be held liable for this. I'm sure one could craft a similar argument for limitations on liability of even closed-sourced codebases.