this post was submitted on 17 Sep 2024
45 points (97.9% liked)

Emulation

3531 readers
21 users here now

Community to talk about emulation & roms.

RULES:

1.) No bigotry

LINKS:

founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] potentiallynotfelix@lemdro.id 2 points 2 months ago (23 children)

Exactly my thoughts. The project is going to remain open source, but not free. I hate when people fail to recognize the difference between free software and open source software.

[–] Ferk@lemmy.ml 6 points 2 months ago* (last edited 2 months ago) (18 children)

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:

  1. 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.

[–] toastal@lemmy.ml 2 points 2 months ago (15 children)

And there is nothing wrong with folks choosing such licences—especially if trying to get paid or not exploited.

[–] Ferk@lemmy.ml 3 points 1 month ago* (last edited 1 month ago) (1 children)

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.

[–] toastal@lemmy.ml 2 points 1 month ago (1 children)

Not what I am arguing, but we do have two issues: 1) naming/branding for these types of licenses 2) FOSS banshees acting like these licenses aren’t acceptable & the whole idea is binary good or evil

[–] JackbyDev@programming.dev 2 points 1 month ago* (last edited 1 month ago) (1 children)

As long as we don't call them free, libre, or open source I don't care. We shouldn't make the terminology any more confusing for those.

[–] toastal@lemmy.ml 1 points 1 month ago (2 children)

There’s limited vocab to choose from & source available isn’t an appealing one

[–] Ferk@lemmy.ml 1 points 1 month ago* (last edited 1 month ago) (1 children)

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".

[–] toastal@lemmy.ml 1 points 1 month ago

Right. We want clear labels else they become meaningless like “boost immune system”. There probably is something that can fix the phrasing when someone finds it, but it also must not be poisoned by those going too hard into free software as a lifestyle or corporations looking to circumvent the premise. What it should be called tho, I don’t know.

[–] JackbyDev@programming.dev 1 points 1 month ago

It doesn't really roll off the tongue, I get it, but it's the best and most widely used term for software whose source is available to view but not modify and/or redistribute.

load more comments (13 replies)
load more comments (15 replies)
load more comments (19 replies)