This is hacker public radio episode 3,394 Thursday, the 12th of August 2021.
To its show is entitled, Linux in laws S01E36, open source licenses, and is part of the series Linux,
in laws it is hosted by monochromic, and is about 56 minutes long, and carries an explicit flag.
The summary is, the ultimate show on open source licenses, or how to fall asleep without chemicals.
This episode of HBR is brought to you by AnanasToast.com.
Get 15% discount on all shared hosting with the offer code HBR15,
that's HBR15.
Bit your web hosting that's Aniston Fair at AnanasToast.com.
This is Linux in laws, a podcast on topics around free and open source software,
and is hosted a contraband, communism the revolution in general, and whatever fences you take
of.
Please note that this and other episodes may contain strong language, offensive humor, and other
certainly not politically correct language, you have been warned.
Our parents insisted on this disclaimer.
Happy Num!
This, the content is not suitable for consumption in the workplace, especially when played
back in an open plan office or sub-non-varmance.
Any miners under the age of 35 are any pets including fluffy little killer bunnies.
You trust the guide dog, or less on speed, and qt-rexes, or other associated AnanasToast.
This is season something episode 30, whatever.
It's not an episode, and an episode, it's not an episode.
Great spirit.
Welcome to the episode on Frost Licensing.
Martin Howard Things.
Oh, I'm very much looking forward to tonight's episode.
I see.
Why?
Oh, it's a favorite topic of a friend.
I see.
So you look forward to using it as a, what's what I'm looking for medication, if you can,
if you can, if you can, if you can, I can sleep.
I'm sure we can make it far more interesting than that.
Yes.
That's what I call it.
But before we go into the details, a little bit of banter, as marketing normally, subscribe,
and prescribes, in terms of, so what's the weather like these days?
I mean, the summer is not there quite yet in the UK.
No, no, no, no.
It's coming.
It's coming.
There's a heat wave coming here.
Like what?
17 degrees?
There it is.
It hasn't arrived yet, but it's been a daily mail, so must be true.
If you're still in the internet, you're still in the internet.
I thought you can, so that's subscription.
Oh, really isn't really.
It's been going too far.
So what you're trying to say, a member of your household is a very lucky offer,
subscription.
I see.
Now, this is something our dear friends at Google decided I need to know as in my news feed.
It pops up with snippets from the Daily Mail for one day.
I see, you want to have a work with them just in case.
I'm sort of got the algorithms wrong now.
You see, Martin, I can't be fixed if he just started to write people.
So no worries.
Aha, excellent.
And what about yourself?
And currently, I'm looking at something called Crafthverk.
It's an IPA.
Funny enough.
It's a band as well.
Yes, but yes, but you see, it's
kind of a band.
It's kind of a band.
It's kind of a band.
It's kind of a band.
It's kind of a band.
It's kind of a band.
It's kind of a band.
Yes, but you see, it's a band.
There's a difference.
Okay, but it's quite good.
Temtate to reach out to them.
Crafthverk, if you're listening, the email response or
at lennios.INloros.eu.
Are you sure?
Yes, this is being made.
This is so work.
I'm positive Martin.
I'm positive Martin and yes we do tape him and I can't people if you're listening.
Of course only use only the germ post to address, do not do it to worry about the UK.
That's the ways of time.
Because as we all know, ordinary ordinary male takes one word four months to get from the UK to Germany and back.
This is just based on one data point right, which is yours.
No actually two.
Okay.
I mean I can't.
And you sent two deliveries of forbidden goods.
What do you expect from it?
I wouldn't call it dinner back and some, and some,
a much required food stuff coming out.
No.
Far from it actually.
Well you see this is what you know,
as they are because clearly that is very suspicious of someone's going to send the paper back.
In this day and age.
Okay.
Why?
I can't imagine that many youngsters beat book cinema.
Martin, I'm old.
In case I didn't know.
You said in yourself a book.
Okay.
No, no.
Oh no.
Oh no.
From a second hand bookstore in the UK.
I don't know.
Oh, they're coming to me.
I've been so happy.
Yes.
And that took about three and a half months to get here from,
I think even Birmingham, if I'm not completely mistaken.
And something from Frankfurt to London.
And that took about four months to get there.
Okay.
It doesn't sound very useful.
No.
But you see, Brexit is rubbish.
Because before Brexit, it took about a week at most.
It still takes a week to get to Ireland from Germany for that matter.
As an as an packages and stuff.
Okay.
Well, so the trick is to go for Ireland.
No.
The trick is basically to invade Great Britain.
I was left over anyway.
And to make it part of Europe again.
Scotland, Wales, Northern Ireland.
And what's where I'm going?
But what's, is that something missing?
No.
Anyway, if you're listening.
I know Ireland's probably.
Just.
But what I'm looking for, diverge.
No, it's not diverge.
It's.
The sect.
No.
Leave.
Leave the United Kingdom.
Apply for EU citizenship.
You will create a second Switzerland with a no-time.
What is this London?
I don't know.
What is this London?
What's London?
It's surrounded by European membership countries.
Uh-huh.
Did I kick it out?
Yeah.
Once.
Yes.
Well.
They are almost Europe.
Anyway.
Once this is done, where it's Scotland, Northern Ireland.
It's just surround Britain and send food for thought.
Let's put it this way.
Brussels may be able to get your weapons.
Just reach out.
But hopefully it doesn't have to come to that.
Maybe Westminster.
I think we have to cut this out, right?
Because I don't want it.
And my six-way century.
I'm not just a something.
I would worry about it too much here.
But yeah, I don't.
I mean, I think I'm sure the Swiss are pretty happy.
There.
And there are something like F-type, not completely mistaken.
It's almost Europe.
But without the without the union bit attached,
they can have a of pretty much many of the advantages in terms of
commercial stuff and economic stuff and stuff.
But they're officially a member of the European Union.
But it's like an association.
That's sort of thing.
Yeah.
So they don't have to implement the banara real on stuff like that.
What's the banan rule?
I can't go out of banan if it's not 50 degrees rounded or something.
It's interesting because I don't have any place in Europe that grows bananas.
Yeah.
It's not even the Dutch do this.
They grow something else.
But that's a different story.
You see Martin there was a tie basically.
When I was traveling from shipwood down to downtown in Amsterdam.
And whenever I took the train, this kind of past residential areas
where in the middle of the winter or the rooftops were actually clear of snow.
Hmm.
What are all going bananers, right?
Exactly.
You went down half a mile further and there was of course not on the rooftops.
You didn't know birds.
Maybe they need to do something about their insulation.
Yes or choose a different type of agriculture grow.
You never know.
But it was quite a ton of side actually.
And the couple of almost years that I did this actually.
All the rooftops actually frequently changed.
You never had it there that there were kind of rates or something on these days.
No.
It must be a lot again.
Oh yeah.
You're looking at about at least 13, 14 years as some flat is.
If my knowledge of Dutch and the first calmness I was able to go by.
Yes, there were actually rates being being done in these places.
Exactly.
But the Dutch agriculture is not the subject of that episode.
Oh, no.
It's not funny enough.
Is it my hookernals?
No, it's not actually.
No, the Dutch, no, the Amsterdam agriculture scene is planned for what is it.
A season 13 episode 12 I think.
If you're a completely mistaken.
But tonight episode is actually something called floss licenses.
Mm-hmm.
Oh, yes.
It didn't mention this.
It's not.
I think yes.
Okay.
People if you are.
Yes.
If you are not.
If you're if you listen to this later night and you cannot get to sleep.
The worry you'll be asleep in about five minutes tops.
Pretty sure of this.
Okay.
Food is food is totally people.
Martin and myself are not lawyers.
As a matter of fact, Martin had to give up that job.
Never mind.
The hourly fees when the coke habit just became too expensive.
And then it's going to have the organization for this now.
There is.
Martin, you don't know what I do.
No, no, no, no, no, no, no, no, no, no, no, no.
Okay.
So Martin used to be a lawyer.
I'm making things happen as I go long back because of drug prices here to give up that profession.
So he's now.
What are you Martin?
A database person, right?
I'm not sure that is such a thing, but.
And I was never a lawyer in the first place.
So the bottom line is kids, people who are listening.
This is not a legal show in terms of if you have any legal questions surrounding your open source project.
And associate licensing, you please, you conduct a licensing lawyer.
There are already.
I was.
I can.
But he always I yes, but the OSI doesn't compensate for lawyer.
They give it.
Yeah, but this advice is not legally binding.
It's the important bit.
So if you have any questions about the next.
Search engine as in if you want to kind of put Google in the payload.
Something like this or some other stuff.
Please do yourself a favor.
Consult a.
A last bar.
And he or she can talk you out.
This show is really meant to give an over is really meant to give an over view.
About the licenses and any surrounding topics.
So Martin, why don't you get us started?
Sure.
Sure.
So.
Okay, let's start with why would you be interested or worried about licensing your open source software?
Very interesting question.
Since you asked that Martin, why don't you know what I'm going to take this?
It's.
It's.
The.
Um, how can I put this?
It's essentially about to the fact where you want to take the code based in terms of how
what you want to do with it.
Different licenses have different aspects and they.
Mostly regulate the use of the source code and that already takes us to a very important
tool main distinctions.
There are.
Copy left.
Oh, you know, no, no, no, no, no, wait, wait, wait, wait, wait, what do you have an explain why people would be wanting
for.
I thought I did.
Well, you said, where do you want, where do you want to take him? What does that mean?
Okay, Martin, what has.
Plus mean as in free.
Libra open source software.
Oh, there's a whole bunch of definition.
That's.
Let's go for it.
Uh, heard this.
Freedom to distribute freedom to modify freedom to combine what else is there.
There's about 10 or something in the other side.
Martin has done this homework apparently.
Food marks, Mr. Fisher.
I was.
I was not exactly getting to that kind of technical level, but rather.
Yeah, that's exactly the problem.
Okay, well, okay, sorry.
It's not just by using it also about contributing, isn't it?
So I was just getting there before my calls interrupted.
Thank you, Martin.
Let's try to.
Speed things along with us.
Thank you, Martin. Thank you, Martin.
No, no, no, no.
Okay, let me. Let me start again.
Yes, I'm free in open source software.
It's all about reusing code, right?
And of course, contributing the changes back again.
But, and this is a very important part with the capital B.
It boils down how in what way you want to do this.
As in, do you want a force, for example?
Anybody taking your code and modifying it to publish these changes?
Or are you rather satisfied?
Maybe happy if somebody takes your code and does something completely
Providery with it without having the need in place to publish the changes back again to the community.
And this is the main distinction you see.
And when you say need, there is only a need from this is from the licensing perspective.
Or otherwise, you'll get sued kind of style, it's not.
That's why you really mean.
Well, I mean, lastly, lastly, this are legally binding contracts.
So if you violate a contract, you can take, you can be taken to court as it has happened in the past.
The link will be in the show notes.
There was actually a case where we ever violated the GPL or the GPL.
And we're going to get to it in a minute of something called the LIMS kernel.
And somebody in Hamburg took them to court.
So, yes, if you're not adhering to the license requirements, you can get sued.
That's exactly it.
Okay, back to the, obviously more relevant is someone is VMware than just a corner, but anyway.
Wait, you see if you're on the corner, basically, it does the next big thing.
Just makes a couple of buildings of from it.
I'm sure that you have people scrutinizing this or her source code.
If it is available or what components he may have used.
And what licenses they're under.
Yeah, there we go.
Okay, going back to the original argument, there are two main distinctions here between
permissive, so-called permissive licenses and so-called copy left licenses.
Do you want to give us an overview before I put the rest of the audience to sleep with the technical details?
Sure, sure.
I think the biggest difference is that with copy left, you have to put the old, all the changes or modifications to have to apply to the same
licensing rules as the original.
So it's really, if you start doing stuff with, or building on top of it, or making changes, then you,
all the best of its permission one you can.
It has, you know, like the Apache or whatever, BST ones.
They, you know, copy it, modify it and, without too many kind of restrictions around it.
Well, it's what it was servicer.
Yes, right.
In a nutshell, this is these are the main differences.
And we cannot put the term copy left by the way, you know?
I don't, I don't.
I reckon it goes back to the original MRT place where I got called Richard Armstrong and came up with something called the new popularized in CPL.
And of course, him being almost a communist, like we are, hence the copy left rather than copy right.
And intended, I reckon this is where it comes from.
Of course, this is pure speculation.
If somebody knows the deeper meanings, Richard, if you're listening, please do get in touch.
Especially once you have stepped back from the FSF board once again.
You may have more time to listen to podcasts and to contribute also to the community.
If not on worry about it, we'll make do.
Okay, get, get back to, get back to the main difference.
Martin, as Martin, right, it pointed out, yes, copy left licenses do require you to publish any changes of a code base that is, that is a license under a copy left license.
The most important copy left licenses are the GNU public license family.
Like the GPL2 GPL3, the FRO GPL and all the rest of it, they have very different meanings.
Makes sense of conversion over view and before we go over the permissive licenses.
So essentially the GPL and the successors of the GPL as in different versions just require you to publish any changes.
So conservative works of a code base to the public.
So if you even kind of take the code from a library and link to it, you're creating actually a derivative work.
So that means you actually have to publish the code that is linking to the license to the library back to the public and to the public domain.
Hence the subset of lesser GNU public licenses that do not have that requirement.
So you can simply take a component, link against it and create a derivative work without having to publish a source code.
There are of course more stringent versions of the GPL, for example, the FRO GPL.
Essentially this requires you to publish any source code.
I'm simplifying things. Of course the link to the corresponding Wikipedia page will be in the show notes.
The FRO GPL basically requires you to publish any source code that you're composing that in a referral GPL license component is talking to on the network.
Again, as I said, I'm simplifying things. It's not more difficult. Imagine a web server, imagine a web server that is issuing HTML.
So if you are implementing a rest API.
If this piece of code is licensed on the referral GPL, essentially any component that talks to it, especially your rest API, your rest base client has to be published as well as in the source code of it.
This is probably the most stringent and rigid member of the new family of licenses, because any component that talks to an FRO GPL license component has to be published as in the source code of it.
The idea when the FRO GPL was originally implemented originally designed was to ensure that any cloud software under the FRO GPL or that is used, that is used in the FRO GPL context would have to be published again.
I'm almost ready to say that this viral GPL notion spreads across the network, which is probably the most common is for wonderful pet expression license you can think of.
Well, interesting enough, the usage of the FRO GPL is pretty low, right? Why would that be modern? I'm just wondering, any thoughts?
Well, I think as you just mentioned, any component you speak to you on the network, that's kind of.
That's exactly it. Okay, you see there are two sides of the story, right? The more restrictive and the open source license is, the more restrictive, the use cases, because if you're linking against a copy left license, take the GPL for example, anything that you create with that code base, you have to publish.
Now, if this is not on your ally, please stay away from copy left licensees. So the more restrictions you put on the code base in terms of licensing, the more restrictive your usage gets, because quite a few people are written.
Let's use the example of a startup.
I mean, if you just give a have to develop the secret source, that will render the likes of Google and friends absolute within five years time, you don't necessarily want the public to have a gander at it.
So in that case, any component, license in our FRO GPL or another couple of license is probably not for you.
On the other side, if you have a permissive license and Martin just mentioned MRT Apache and the BSD licenses as three examples, this is the opposite of the of the of the spectrum.
You can do pretty much whatever you want with it. There are certain differences.
For example, the Apache licenses, the Apache license requires you to put a little more pros into your source code, the BSD license basically says, you're not falling a patent on the on the source code and you mentioned the offer probably one of the better no examples is something called that is.
As in the remote dictionary server, which is last in the free class BSD, so you can do pretty much whatever you want with it is you mean that you mentioned several times in the lipo as the original author and where it comes from and that's pretty much it.
So you can incorporate that component.
You just have to mention that you basically took it, but you are free to use that code base without any restrictions as long as you adhered to the license to the permissive license conditions.
So if you want to wrap this up in your text deck that does the next big thing, just go ahead.
Yeah, it's a misive is definitely the way to go.
Funny enough, then also rather optional. As you already mentioned and I think I mentioned terminus to be already on a few other few occasions, but terminus was under I think even the photo GPL about a year ago.
And as you rightly said, the adoption was pretty low of that code base. Sorry, terminus to be you front of English row notes is a combination of a git storage pregnant with graph database in front of it.
The reason why I'm imaging this is it comes from an old item of a matter, namely to the college where the PhD and terminus, I think, went live last year or some flat for so it's a brand new project, brand new code base you're fun and good to have.
But the last year they changed from a federal GPL to something called Apache for the for that exact same reason, namely they found the adoption pretty low because of the restrictive, I'm I'm licensing requirements.
So they changed this to Apache and voila, the adoption went I wouldn't say sky high, but grew significantly because now people were able to incorporate the code base in their in their text deck without having to publish any any group of work.
Well, in turn drives innovation and improvements.
I mean, if you're going for copy left license, people have to publish any graph work as interested derivative work.
Meaning that of course, if you are going for that license.
Give me a example of a project that is used in that way and people have to publish their changes.
Good new compiler collection.
That's an example.
It's probably one of the best sea compilers on the planet because about 20 years of development went into it, but it was of course licensed on the GPL.
So any modifications had to be published.
And I've yet to see a commercial compiler.
Yeah, it's with a collection.
Yeah, it's not just modifications.
It's also if people use it as part of their code base to do.
A compile on release or something like that right when they build this off fire.
It's probably the most used compiler collection as a component of the planet.
Because every Linux sister has it in their repositories.
Of course, the sea land is making strides for us.
But as I said, a lot of innovation went into the compiler to the train and it's probably one of the most mature two chains as a sea compilers to change on the planet.
Okay.
Yeah, but it's not really comparable to a,
an open social product that's monetized like a redness or a post-class or whatever is these days.
It's rather as modern times.
Okay.
It's not.
It's not.
It's not the word for it.
Yeah.
Yes, man.
Pretty much like enterprise TV.
If memory so it's correct.
Yes.
I said, the word isn't monetized.
Okay.
You got that wrong.
You know.
Thank you for enlightening.
You're more than working on.
No worries.
No worries.
No.
Post-class has his own license, right?
He does.
But it's not.
Yes.
So this is permissive.
I'm a copy-left.
It's similar to MIT as per his very permissive, which is why you find it in lots of applications
that people ship out, right?
It's part of this.
Many, many, many, you know,
if people building an application and then they're based on these other
musical prospects and just from really BV states.
If you're still kind of a member of the old guy,
looking for a secret technology.
Not that many people do it apparently,
because the no secret seems to be the rage.
Of course, that's a shameless teaser for an upcoming episode,
where we will have the great bathroom between.
I've heard about high particles, right?
Yeah.
Yes.
Yes, it was about 30 years ago.
No, it's still on the way up west.
No secret.
Apparently Jeff Bezos mentioned that he managed to get rid of us.
It was a last oracle instance about a year ago.
In something called Amazon.
I don't know.
It's a bookshops.
Because he doesn't want to pay them any money.
But we digress.
Indeed.
We do.
Okay.
Permissive licenses as a matter of fact.
Okay.
So, and of course, there are derivatives of set licenses.
So, for example,
the few of them.
Yes.
The conundrum of course is basically that
Martin already mentioned the OSI.
Can you shut down that on the open software initiative?
Well, the whole episode of it is.
Yes, indeed.
You know, they open the open source initiatives and time if you're listening.
This upcoming shows for you.
Because we have that.
Nicholson on the show.
No, the OSI is one of the vetting bodies of sets.
Open source licensing ecosystem.
Quite a few companies have tried to get the license.
This is vetted.
That's not all of them have.
Have have succeeded.
Because some of the restrictions or some of the attributes that Martin already mentioned are quite restrictive when it comes down to the vetting of open source licenses by the OSI.
So, for example, you cannot restrict usage rights.
We are recording this episode.
What is it?
It's an 8th of July 2021.
Thank you very much.
You're welcome.
For those of you who haven't heard there's something called out there called audacity, which funny enough we use to edit this podcast.
Now, audacity as in the project was acquired by a company called Oak Muse about a month ago.
And as probably the quite a few of you know audacity is under the GPL.
And what Muse actually did, obviously, notice whatever the company is called.
You're from the link in the show notes.
Actually, try to restrict the usage of audacity to people above the age of 13.
Funny enough.
Yeah, Muse that you cannot use audacity unless you are older than 13 years of age.
What?
That's not a link.
It doesn't, Martin.
It doesn't.
The link is on the show notes, but in this cut to be, of course, that violates the GPL letter on the center.
Because that's exactly the thing you cannot do with a GPL database.
You cannot restrict usage rights.
Very important.
Hmm.
Funny enough, quite a few people didn't know how to open source license lawyer.
Funny enough, quite a few people got upset about this.
And forked the core base left right in center.
Hmm.
They also tried to put, they also tried to put in some telemetry code into the core base,
but that's a different story where we're going to delete it.
I just check your local favorite open source news outlet for the details.
But surprised me to say it didn't go down well with the community,
and as expected, quite a few forks happens over the last couple of weeks.
And not surprising, by the way.
Going back to the original discussion,
quite a few companies have tried to restrict the usage with limited access, let's put it this way.
So for example, there was a...
There's today's a complicated redness lapse.
Hmm.
Well, there's a lot of work for them.
That put out something called the redness lapse,
source available license in 2019.
Yeah, it wasn't...
Didn't MongoDB do something similar before them, or I'm the same time.
We are getting to Mongo in a minute when we're going to discuss something called...
Yes.
The servers are popular.
I'm sorry.
I'm a little bit slow tonight.
Because these are two exact opposite stars of the coin.
But let's discuss our SAL first.
The idea behind the RSA was to restrict the usage of the so-called modules
that the meant the redness, the original redness code base,
so that it cannot be used by funny enough hyperscalers.
Hmm.
When redness lapse came up with the original idea for the RSAL,
AWS in France, we're already making new billions of dollars
by an elastic-ish and other derived offerings of the BSD license.
Redness open source code base, because what these habits can essentially date is,
or what they're still doing, or what they're still doing,
they take the open source code base, package it for their cloud environments,
and then set it as the managed servers.
Hmm.
So, race lapse is pouring a lot of money, I think,
into the development of the RPs,
because it's the server itself, it's less than three keys,
another three-class BSD, so people can do whatever they want with it,
software enough, and that won't change, and make money from it.
And the intention behind this RSAL was to not repeat this
with the modules, with the source code of the modules.
The modules are essentially a server extension
that transform redness into an application, or more application specific database,
like a graph database, a term search database, like a documentDB, that's all thing.
So, the idea was basically to restrict the usage of these modules
to non-cloud environments.
The source code is still available, you can look at it, you can compile it,
you can slot it into your own text, you don't know the deal,
but you can't deploy it as a managed service being a hardware scaler.
That's the most important difference here.
Hmm.
There was quite a lot of apparel about this.
There was a project called GoodForms, funny enough,
by somebody, a kind of a name.
Chris Lambe.
Yes, Chris Lambe.
As Chris Lambe and Nathan Scott forked this in 2019,
if I'm not completely mistaken, links on the show notes.
But nothing happened much after they forked the module code
based then and there.
The contributions data died down,
and you can take a look at the stats from GitHub,
nothing much happened afterwards.
I mean, Chris got a first and top out of it
about contributing code to a running steps control code base,
but that was pretty much the end of it.
Okay, but then answer the modules predominantly,
by when it's now saying,
as in the contributors.
Well, probably the standard modules,
basically, that are available on top of it is
are developed by running steps, yes.
But of course, the module SDK is published,
so you can do your own module if you want to.
Now, what is holding you back?
Yeah, but I mean, the modules code themselves,
the other projects, there's a pretty much maintained body.
Metislabs, employees, no?
Oh, yes.
Like time series, like like registration,
document to be like always stuff and all the rest of it, yes.
And during the steps,
it's also pouring a significant amount of money, as opposed
to the development into the copies of a code base,
or of these code bases, but it is where.
So, I mean, yes.
Yeah, yeah, yeah.
So, this is an example of why people are coming up with
different licenses, right, or adding restrictions
to the licenses that I already exist.
I mean, there's always, of course,
the other side of the flip side of the coin.
You have something called the server.
The server is our public license.
It's essentially a different approach to the same problem,
because what the server's our public license actually
mandate is if you,
what's what I'm going to do for
in corporate such a project,
run it, or I think.
No, it's a derivative of of the GPL3.
And it says, basically,
that if you cooperate code base,
license under the server's our public license.
In an environment that controls your infrastructure,
that controls the environment,
that has an orchestration thing around it,
you have to publish any surrounding components.
So, in that regard, it's pretty close to something called
an referral GPL,
meaning that if you are a cloud provider,
like a hyperscaler,
you would have to publish your infrastructure code
that runs that code base.
So, imagine if you want to take
Mongols, probably the best example of a server
that's our public license code base,
if you want to deploy a Mongol code base
in your cloud environment,
you would have to publish your orchestration stack,
your monitoring stack, and all the surrounding components
that control and execute the Mongol code base.
So, essentially, it's not comparable to the RSL,
but this rather, it doesn't have the code, right?
Yeah, it does.
Well, this serves the same purpose, right?
Yeah.
The hyperscaler is from using it.
That's exactly it.
Yes.
The lack of Amazon Microsoft and Google, of course, won't publish
that hypervisor code that control that orchestrate
that monitor these environments.
And that's exactly the purpose
of the server-side public license thing,
which is pretty interesting when you think about it,
because they simply say,
of course, you can take our code.
But if you want to do this,
you have to publish your own stuff as well,
whereas the RSL simply says,
sorry, you cannot use this code
because it happens together,
which is a different approach of course.
But the result is pretty much the same.
Okay.
Should we mention common class before we close off the show?
Is anybody still awake?
Yes.
Just in case.
Creative Commons is not a set of answers.
It essentially is mostly applied to creative content,
like songs,
roles, podcasts, books, magazines, whatever you want to articles,
whatever you want to refer to, whatever,
take it to your pharmacy, and the idea is essentially
to just to give credit.
Yes, it's for the...
Yes, it's attribution.
And it also mandates how you can share the content.
For example, if you can modify the content or not,
and this is probably the most important attributes of set license.
Mm-hmm.
Okay.
But that's irrelevant, so far we need it.
Well, I mean, it's relevant if you're a publishing content,
that is not necessarily technical.
Boom, true, yes.
Okay.
Like blog posts and what I think.
For example, this podcast is lessons under CCR,
CC Creative Commons,
Artibution and Sharelike, meaning you have to go for credit.
Of course, you can take the content,
and modify it to your art content,
but you still have to go to the attribution,
meaning you have to credit the limits and laws
for coming up with this, not to content in the first place.
Yes.
Pretty unique, obviously.
That's...
That attribution must be done.
That's reasonable, why, why, like, kind of...
Well, you see, finally enough, basically, it was kind of...
It might be more the problem, but the problem will be in touch.
Yeah, blah, by the HPR.
You see, probably enough, basically,
when we first discussed when we were the host,
the HPR, of course, came up as in the Hacker Public Radio,
but they kind of mandated the CCR by SA, as in Sharelike,
and this is especially what you have been using ever since.
Fair enough.
Yeah, exactly.
So we'll still only, on the platform,
can you're listening for credit?
Thank you very much for one and a half years of great service,
almost.
Hmm.
Is that anything that we have missed?
Well, as is clear, the whole licensing scenario.
For any, any, any, any budding,
also of a new project out there.
Well, maybe we'll miss out on the cat videos,
but please check your local video page.
I'll just watch it.
Sorry, they're on CC by, right?
That's...
CC by SA.
I suppose that depends on license.
Okay.
Hmm.
Well, like then, okay.
Excellent.
Well, thank you for that great description.
And...
Well, it's a little bit fizz off.
A philosophical, never mind, communist attitude.
And that takes us nicely to the poxels, Martin.
Well, what about the feedback?
Hmm.
We do have feedback, yes.
We do want to read this out.
I can do this.
So it's just feedback on episode 33
by Kevin O'Brien, who says,
I loved the show.
I found this discussion fascinating.
And I also noted that Linus had mentioned the possibility
of using rust for the dinosaur model.
And that it is not something you hear every day.
If sometimes a programmer out in HPR land wanted to do a series on programming in rust,
I think it would be a big hit.
So there you go.
Townsend programmer on rust.
And that was the show where we had the latest contributors
or on the table, the virtual one.
Is this not the rust one, let's Steve?
No, it wasn't.
Anyway, it doesn't matter.
And on this particular subject,
if 514 as in the release kind of is anything to go by,
rust is making great strides into the caramel
in terms of the earth.
The earth is finished.
It's a complete mistake.
And people and people are looking at,
they're looking at using rust beyond driver scope
or the kernel.
And that's it.
Okay.
Details on the change lock of a set kernel as in 514.
And with that, it's now really time for the boxes.
Martin, what's the box?
My box is something called,
I think it's called the farm, it's called the farm.
Rick and my Josh always, right?
No, not that one.
It's just written by,
the question,
does it written by,
but he was produced by Amazon, obviously.
Mark or a picture?
No.
Why would it be written by Amazon?
I'm confused.
I'm confused.
It's so in my mind.
Yeah.
Anyway, oh sorry,
he's not called the farm.
I was called Clarkson's farm, I think.
Anyway.
Okay.
So what is it about?
It's about a guy's TV presenter.
He's a lot of money doing TV shows.
He's bought a farm and he started into farming.
It's just quite amusing,
especially if you can see so close to having a farm.
Why would you buy a farm?
The do farming.
You're not living a city to,
what's the point?
People need food.
And so farmers produce food.
The rest comes from genetic lab or something.
From a few genetically.
I know.
I don't know.
I don't know.
Maybe it doesn't,
but not over here.
Still a farm.
I see.
Okay.
My pox of the week is a movie called Taking a Lies.
It takes lives.
It goes lives.
Yes.
It goes back to 20 or four.
It's a course with the engine largely.
And if you have a chance to get this on Netflix or something,
don't miss it.
It's one of the better ones done by her.
And it's really riveting with regards to plots.
Psychology behind the whole thing and acting.
Ah, this is not because she gets a kid off more than me.
I can't remember any movie where she did, actually.
Can you?
No, no, no.
Nothing there.
No work.
No, it's the same.
It's the same.
No, this is not only bastard.
This is actually.
Okay.
I mean, if you, if you're interested in campus fence,
throw less that movie to watch.
Okay.
That was good.
What was it called?
Taking, taking lives.
Exactly.
Exactly.
The links will be in the show notes.
The link rather will be in the show notes.
Exactly.
Okay.
And this is the end of something called Season 1 episode.
I can't remember.
Oh, he's six.
Yeah.
Yeah.
That is the micro kernels.
Yeah.
The jury is still out on the episode.
But it definitely seems one.
And as usual, Microsoft Google.
Amazon, if you're listening, the email address is sponsor.
At Lennon Sin knows what are you.
We'd like to thank Ken Fallen and H&H Public Radio.
Thank you.
Thanks, Ken.
For hosting the show.
And this is a can.
Yes, we do apologize for not showing up on the monthly HPR review.
But let me please do this.
Each year, we month HPR does a monthly review of the shows.
And if you saw in class, please join this slot and give feedback.
Because HPR's community living from participation.
Living by participation.
Living on participation.
Anyway, it doesn't matter.
The more you contribute, the more vital this platform gets.
Because otherwise, shows like.
The ones you fight in the HPR, including.
Then it's in last week, not be possible.
Definitely.
And thank you for listening.
Yes, and next week, we will have.
Like the next one.
Finally.
In about two weeks time, Martin.
We only published every two weeks.
I guess.
I guess.
Mark the consent of memo.
Oh, I used to don't know.
Did we get some new ones together?
And I'm afraid there's something in between called an interview.
So it'll be four weeks time.
Yeah.
You know what I mean?
Exactly.
People don't don't worry about the schedule.
We can't hear.
We don't hear.
No, that's okay.
And thank you for listening and looking forward to.
Be with you too.
Exactly.
This is the Linux in-laws.
You come for the knowledge.
But stay for the madness.
Thank you for listening.
This episode of Linux in-laws is sponsored by Linux Torvots.
Linux creator and to use his own words.
Linux kernel grant master flash.
Unfortunately, Linux was not able to deliver the following message in person.
So we had to resort to a voice double.
Due to budget constraints, we had to avail of bargain basement talent,
which may sound slightly different than the usual quality.
You have come to expect and love from the in-laws.
No.
I don't want to deal with this fucking put across a longer.
If you're not that wouldn't have used proper contraceptives,
I wouldn't have to face this fucking shit anymore.
Get alive and learn to properly code and see if I start.
Or if that's too difficult for you to admit it in intellectual capabilities,
just use rust going forward.
If you're smart enough to master a learning curve, get shit.
Oh, sorry.
This is not the Linux kernel menu list.
This is a person message from Linux Torvots.
Also, no less.
The kernel grant master flash of something called Linux.
Are they operating system?
I advised about 30 years ago.
For some odd reason unbeknownst to me,
this peck project has been the range for the last 20 years or so.
Even more important as Linux is approaching world domination,
also partly due to a fabulous putcast.
It looks a lot.
Choose your license wisely.
Let me emphasize this.
Choose your license wisely.
I must first find that.
Linux would not be where it is today.
Without that initial decision to put the code base on the group public license,
also known as GPL back in 1992.
That moved fostered innovation big time.
For example, two years after that decision,
I'm support entered the kernel mainline.
And the rest of history.
Even waiting for Andrew came to the conclusion that Linux was the way to go
for his mother operating system,
made after some cute plush robot.
Before some script keys,
with a revolutionary approach to such engines came to the conclusion
that Andrew's outfit might be a good addition along that path to world domination,
but I died grass.
Just make sure you choose the right license forever.
Now I'm off to my anger management therapy session.
Till of Christmas.
This podcast is licensed under the latest version of the creative comments license,
tap attribution share like.
Credits for the entry music go to bluesy roosters for the song Salud Margo
to twin flames for their piece called the flow,
used for the second intros,
and finally to the lesser ground for their songs sweet just is,
used by the darks art.
You find these and other did this license under creative comments at your manual.
The website dedicated to liberate the music industry
from choking copyright legislation and other crap concepts.
You are currently the only person in this conference.
The only person in this conference is the atmosphere.
I know you can go away.
Oh, there is a message on Linux so dear.
Just going to get myself another cup of beer,
or other bottles so we have to cut this out.
Anyway, does it matter?
But for the people who missed out on this.
Has it gone out?
Oh, will miss out on it.
Does it come out before this?
Yeah, let's check with marketing because they are writing the show again.
Far from yet.
There has been a certain wifial thing of episodes going on.
Anyway, that's a matter.
You've been listening to Hecker Public Radio at HeckerPublicRadio.org.
We are a community podcast network that release the shows every week day, Monday through Friday.
Today's show, like all our shows, was contributed by a HBR listener like yourself.
If you ever thought of recording a podcast, then click on our contributing to find out how easy it really is.
HeckerPublicRadio was found by the digital.com and the InfoNomicon computer club,
and is part of the binary revolution at bnref.com.
If you have comments on today's show, please email the host directly.
Leave a comment on the website or record a follow up episode yourself.
On this otherwise status, today's show is released on the creative comments,
in the description, share it like, stay up to our license.