FR version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
52% Positive
Analyzed from 1298 words in the discussion.
Trending Topics
#open#source#more#coc#software#project#drama#free#should#bad

Discussion (10 Comments)Read Original on HackerNews
To be more specific, Open Source only promises the four fundamental freedoms (https://en.wikipedia.org/wiki/The_Free_Software_Definition).
It promises literally NOTHING else, including zero cost. Free and open source software can and should cost money! (The "free" in "free and open source" is not about money, people!)
I'm actually very enthusiastic about these OSS "supply chain" attacks that have been happening in various communities. Because optimistically I hope it'll help people realize that OSS _is not a supply chain_ (more details here: https://lobste.rs/s/cxwidw/no_one_owes_you_supply_chain_secu...). Unless you're paying your vendor AND/OR have a contract in place with them with certain guarantees, you do not have a supply chain.
One term thats in almost every FOSS license is "this software is provided with no warranty." A supply chain implies a warranty. Therefore, FOSS is not a supply chain.
no, that is FSF's free software.
I'm sick of coming here and see "open source" as something with "moral values" - stealing it from the free software with "the magic" of conflating the two concepts.
Open source is just big software companies stealing from innumerable volunteers
But my point is... the active dev group was, at any time, very small. Mostly I'm talking about small utilities like make, Sendmail, sed, awk, sed. Perl seemed like it was just Larry Wall and tchrist for most of the time before 1990. gcc was an insane counter-example with a cast of thousands who submitted patches and you had to socialize your patch w/ RMS if you wanted it upstream.
oh wait... I forgot to make my point... My point is... the new tools support larger teams of people constantly interacting. I think there are great benefits to having a small team and effectively giving the middle finger to internet randos who don't submit their patches on one of their kidneys (i.e. - they'll think long and hard and sure as he'll won't submit two.) But getting people interested in your work output isn't one of those benefits. So... absolutely... go old school... But keep in mind the size of your team will be small and it may be hard to attract users.
But... screw users... I write software to support my own use cases. I open source it on the off chance someone else may find it useful.
Better faith CoC people talk about freedom of association vs freedom of speech - if a platform doesn't like their oppponents, isn't it fine to ban them? Or say it should just be treated as a more utilitarian "be nice" convention for the mailing list (obviously it depends who is calling the shots, but that is true in any project).
Sure, but the problem here is far more insidious. By latching into delicate and, at times, controversial issues, CoC may hold a project hostage and threaten character assassination.
Imagine that for some bizarre reason, CoC establishes that issues are only to be talked about on Mondays. People can comply, or they can leave, no biggie. Strange but clear cut.
Now, say it instead establishes whatever politically motivated consideration. The choice now becomes one of positioning oneself into the current political climate. This makes sense at times, but also leaves a door open for abuse akin to rules lawyering, gotchas and crybullying. Sometimes creates a phantom HR that has no interest beyond exerting its power and which does d with no accountability.
Problem is anyone raising this as an issue or rejecting such proposal is going to look bad while doing so. It's easier to keep your head low.
Do you think open source projects just had to put up with anything and everything before they came along? No, if someone was being an active detriment to the project, they'd get naturally pushed away by the project leader, who was usually also the top contributor, in a clear and transparent manner. If the rest of the contributors agreed, that was that. If not, they could always fork. No drama needed, everyone was free to judge for themselves.
CoCs were introduced not only to to take that power from the leader or top contributors and hand it over to cliques of political activists, who often do not contribute to the project at all in terms of actually writing code, but also to allow them to invoke it in vague and secretive ways, for reasons that most actual contributors likely wouldn't agree with. Obviously, this leads to drama. You'll notice that CoC drama almost always boils down not to "this person is generally agreed to be a detriment to the project" but to "this person said or did something that offended me and thus violated the CoC".
It is not a political thing in my view. I get more tired by the metadrama. Things did change when open source became a business. It is impossible to compare a voluntary based project with a big one. I think the issue is that most people have no experience in doing large scale self organization.
What's clear is they mediating all selection choice and interest through pressure points of a single fixed trust board is of limited use going forward. I don't think the vouches and other web of trusts tackle the actual root need to disaggregate, decentralize.
You can anti-social open source, reject, flee to nihil and going away, solo-ing. I think that's mad bad and dumb; just my judgement call. I agree strongly with v-it, open source is social. It's interesting and fascinating to open your mind. These other signals are fascinating. The glut of goodness is something we should firehose better, not shy from. https://v-it.org/
This is not antisocial.
You didn't talk about being interested in what maintainers were up to. You talked about what your friends are interested in! That's the thing! We need to decentralize the decision making. If your friend is juggling some patches, some feature branches atop code you use, that is interesting. We seem to both agree that we do want to have interest & awareness.
We've only had one model for social ness ever and it's created enormous pinch-points, enormous thin-waist problems for getting stuff done. The maintainers themselves keep saying they can't handle the loads, don't enjoy it, don't want to. I think the submission is kind of a bad spirited loser but I'm sympathetic! I just think it's worth exploring pro social options before we all default to shutting down turning off all the exterior signals and going dark, like suggested. That sounds a lot like being a loser to me. Fine, do you! It sucks though, it really does. Everyone should hope aspire to & work for better. Let's discuss what that might look like.