Yeah, it definitely is more appealing from a marketing perspective.

I do understand why some projects might wanna use the term, it’s to their advantage to be associated with “open source” even if the source code itself has a proprietary license.

The problem is that then it makes it harder / more confusing to check for actually openly licensed code, since then it’s not clear what term to use. Already “free software” can be confused with “free as in free beer”.

That discussion concluded essentially the same thing I said: that both the OSI and the FSF have essentially the same conditions and that “merely having the source available is not enough to meet what the OSD defines as open source” (sic).

Don’t police perfectly innocent and common use of language please.

Using “open source” for all kinds of source, regardless of how restrictive its license is, is definitely not a common use of the term.

People aren’t gonna start using “open source” like that just because a few people find it more convenient for the marketing of their projects. To me it sounds like they are the ones policing to push for a particular language standard against what people commonly use, which is what makes language prescriptive, instead of descriptive.

I guess it’s better than not providing any source code. What’s wrong is calling it “open source” when it isn’t.

VVVVVV and Anodyne are some examples of “source available” games.

According to the definition from the Open Source Initiative, “open source” also requires free redistribution. See the first point (emphasis mine).

1. Free Redistribution

The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license shall not require a royalty or other fee for such sale.

It also requires freedom to distribute modifications:

3. Derived Works

The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.

CC-BY-NC-ND is not “open source” (both due to the NC and the ND), it’s more of a “source available” type of license (when applied to source code). The difference between “free software” and “open source” is more ideological than anything else, they both define the same freedoms, just with different ideological objectives / goals.

I think that was already done a while ago with Swanstation libretro core.

Which is why you should only care about the personal opinion of those people when it actually relates to that reliability.

I don’t care whether Linus Torvalds likes disrespecting whichever company or people he might want to give the middle finger to, or throw rants in the mailing list or mastodon to attack any particular individual, so long as he continues doing a good job maintaining the kernel and accepting contributions from those same people when they provide quality code, regardless of whatever feelings he might have about whatever opinions they might hold.

You rely on the performance of the software, the clarity of the docs, the efficiency of their bug tracking… but the opinions of the people running those things don’t matter so long as they keep being reliable.

I have contributed to other projects without really needing to get involved in their community in any personal/parasocial level, though.

I just make a pull request and when the code was good it was accepted, when not it got rejected. Sometimes I’ve had to make changes before it getting merged, but I had no need to engage in discussions on discord or anything like that. I’ve been in some mailing lists to keep track on some projects, but never really engaged deeply, specially if it goes off-topic.

If I find that a good code contribution is rejected for whatever toxic reason, then the consequence of that is the code would stop being as good as it could have (because of the contributions being rejected/slowed down), so it’s then that forking might be in order. Of course the code matters.

To his point: if not “discuss”, what is the correct approach against fascism? war and murder? dismiss it, try to “cancel it” without giving any arguments so it can continue to fester on its own and keep growing in opposition?

To me, fascism is a stupid position that doesn’t make much sense, to the point that it falls on itself the moment you “discuss” it.

I would have expected that it would be the fascists the ones unable/unwilling to discuss their position, since it’s the least rational one. So it’s certainly very jarring whenever I hear people jumping to defend against fascism while at the same time stopping in their tracks when it comes to discussing it. Even if those unable to reason might not be convinced by our arguments, anyone with reason would. Rejecting discussion does a disservice, because it does put off those willing to listen and strengthens those who didn’t really want an argument anyway.

Like flat-earthers, they should be challenged with reason, with discussion. Not dismissed as if it were true that there’s a huge conspiracy against them. Whether they listen or not to that reason, dehumanizing them and rejecting civil and rational discourse would play in favor of their movement.

Stating “genocide is bad” should NOT be a statement of faith. Faith is the shakiest of the grounds, if we are unable to articulate the specific reasons that make genocide be bad, then we are condemned to see it repeat itself. So, I’d argue it’s for the sake of the victims in Auschwitz that antifascism should not be turned into a religion, but into a solid and rational position that’s not distorted nor used willy-nilly.

The average Windows user would easily be put off by the project if they tried it this early. I feel it’d actually be better if they don’t release on Windows until they are ready. That way they can get better press when it finally releases on Windows.

Bash. By default it might seem less featureful than zsh… but bash is a lot more powerful and extensible than some give it credit for. It might be more complex to set it up the way you like it, but once you do it, that configuration can be ported over wherever bash exists (ie. almost everywhere).