Free and open-source software

Monero uses permissive licensing.

So even if you are closed source or not FOSS, you can still use Monero's code for commercial purposes.

But yeah, there's a dependency that we wanted relicensed.

And eventually we got this compromised to work because there's a side of people who wanted only permissive licensing.

[ding]

So definition of FOSS.

Article 348 defines free and open source software as "software the source code of which is openly shared and which is made available under a free and open source license which provides for all rights to make it freely accessible, usable, modifiable and redistributable".

So, uh, again, it's a CRA definition.

I think it's also very interesting to contrast this to some of the other guidance.

I, I forgot the number, but it's about software, where it's explicitly stated that also source codes can be a product placed on the market.

So that shows that it's not just because you're selling somebody your source code or something that you can claim, "Oh, I give you the source code, so therefore it's free and open source." No, the bar is actually a lot higher than that, and if you're not meeting the two requirements of openly share, so basically having it publicly available on the internet for everyone, and then having the open source license applied to the software, then what you are providing is definitely not FOSS under the CRA.

This open license thing is, I mean, I'm kind of... don't know that I wanna step into that water, but it's a little murky to me.

Okay.

Um, and so, you know, this, this as a, as a, sort of, you know, as a FOSS guy, which is, you know, free, free and open source software.

As someone who's into FOSS bec- i- because it's a, it's a fr- it's a free and open source, uh, project.

Um, and, you know, a bit of a geek.

You know, this, this was, this jumped out at me, right? And I was like, "I have to, I have to find out about this." And, um, I think, I believe Ben Johnson's book pointed, um, readers to Lichess because the bots are available to play there.

What type of software classification allows the developer to view and change this source code? Would that be...

64-bit, FOSS, DRM, EULA, or MNDA? It's got to be one of those.

If you think you know the answer, again, please no answers in the chat room.

Please no hints in the chat room.

Let's get to work, shall we? Let's look at the question we asked earlier that asked...

A software developer at a startup wants to modify the underlying code of a database utility to optimize it for their proprietary hardware.

What type of software classification allows the developer to view and change this source code? Would it be 64-bit, FOSS, DRM, EULA, or MNDA? Which one of these is it? Well, let's find out what you think the answer is.

I'm going to close my poll.

Like, it's always been, like, a, a relationship there, right? Because Europe has a lot of people, the US has a lot of people.

Obviously places with a lot of people, you're gonna have a lot of people that are interested in doing FOSS things, open source things, and especially because these regions do have, you know, higher levels of internet conne- internet connectivity.

In, uh, India for example, not traditionally been heavily in the FOSS world, but as more infrastructure is built there, as more internet access is becoming available, you are seeing more and more of that in India as well.

Same with, uh...

China has a different problem.

E quindi voglio chiedere davvero consiglio anche a voi: cosa vi piacerebbe affrontare di-di particolare di questo videogioco e come vorreste che lo affrontassimo? Siamo ovviamente, eh, aperti al dibattito.

Chiudo con ultime cose rapide: grasso aggiornamento per F-Droid, lo store alternativo FOSS, Free and Open Source Software, quindi quello che ci piace, quello open source gratuito, il suo più grande aggiornamento degli ultimi 10 anni.

Peccato per una piccola postilla che a partire dal 2027 Google imporrà agli sviluppatori che distribuiscono app al di fuori del Play Store di pagare 25 dollari e di registrarsi, altrimenti il sideload sarà un pochino più complicato, non è che sarà impossibile.

Secondo me in realtà per gli utenti di F-Droid non cambierà molto perché sono comunque già utenti piuttosto smanettoni, piuttosto smaliziati, piuttosto abituati a sapersela cavare.

uh that's going to end up meeting although i mean if you if you push something that was ai generated that causes like a zero day um that's everybody's problem whether it's actually your problem or not right it's going to cause some issues um but anyways they've had that vote a couple weeks before that codebird came out and said yeah you want we don't want any ai assisted code at all um sourceforge came out right after that and said we're actually even more strict like we are absolutely no AI on our platform whatsoever.

We've had several high profile FOSS developers talk about how they're basically being buried under a tsunami of pull requests and bug reports and all sorts of stuff.

We've seen the Linux kernel go from like 200 reports in a week or whatever to like 2,000 or some crazy number.

So what I want to talk about tonight really is that AI inclusion into open source projects, distros, however you want to put it.

Okay.

So with regard to Debian's kind of stand on this, I think they had to do it this way.

I think, I don't think there was another option for them going forward, especially when you're talking about, you know, what are the other, you know, what are other people in the FOSS space doing and how can we kind of like be okay with this? if, if the Linux kernel says, okay, what Stan can we make with Debian? You know, I don't know that they had a choice here.

Uh, but at the same time, I mean, there are, it's, I think this is kind of like the best case scenario.

the keyword here is restrictive the problem graham was trying to solve is the same that almost every other open source project has people are feeding ai chat box chat bots bug reports pasting whatever comes out into a merge request and leaving a volunteer maintainer to figure out whether any of it even works you know this is the same thing we've talked about for a while now and various projects have handled it differently.

But as Graham put it bluntly, LLMs lower the barrier to enter for people who have no idea what they're doing to basically DDoS, FOSS, you know, free open source software maintainers with a tidal wave of crap.

Now, The reason I'm doing this story is this took on a life of its own, and I thought I should put what really happened out there so it kind of does it a little justice.

So on September 19th, Nate Graham opened a draft policy for discussion on the KDE Invent, the project's GitLab server, and its golden rule was don't be lazy.

That's F-A-I-R.

The F stands for Freedom and Free Open Source Software, and the R stands for Resilience and Responsibility.

The AI in the middle stands for AI, obviously.

And what makes FAIR a cool case study is who's in control.