Okay, cool. So basically I wanted to give the talk. This is a bit of a I gave part of

this talk already at the ADAS last year. It's mostly about how we got to our open source

policy at Astron and some points on it. Well, I actually after during the discussion, I

realized that it would actually be a good idea to actually apply creative commons to

the presentation itself because it does defies the purpose of the whole topic a bit. The

names you see down there are basically the members of the open source committee. And

this just the arrow to indicate that's not us. Those are very happy people looking at

documents and well, I mean, we're also very happy people looking at documents, but we're

not that. Okay, so why? So Astron is part of NWO. Well, lots of people have their own

association with NWO, especially when you're astronomers, of course, that's not us. That's

us. And NWO is basically the Dutch Research Council. So that means that we're publicly

funded. And well, from that, we conclude that we need to create open source code. Of course,

there is more argumentation there. NWO does not seem to, there is not much policy from

the NWO perspective on open source, or at least when we started doing this work, but

there was some clear policy in open data. And I think that this is immediate argument

for having open data licenses. And we interpret that as also applicable to the source code.

For without legal restriction thing is a specific one that makes it sort of, well, it sort of

already cuts out some licenses, I would say, but I think any license support has legal

restrictions. So we used to be using GPL version three, whoops, that was a very fast. And so,

I mean, this is the argumentation that we've seen in a few talks already. So I'm not going

to show that basically all the permissive licenses are probably making it easier to

comply with that specific rule. On the other hand, again, this is not something that was

not discussed before. The Institute itself really wants to receive credits for the code

we write, right? We want valorization by third parties using our code and being able to be

cited. So that's why at some point, the management team of Astron decided to put in an open source

committee. I guess this is the image that we like to see ourselves as a group of superheroes

helping the whole Institute to get better or something. But the fact that we actually

seem to be made out of Lego for some reason is also very illustrative. And then of course,

reality, reality is always a slight bit different than you expected. So after discussing a lot

about these topics for a year, we had a policy that was ratified by management. That was

great. We actually found out that the Netherlands East Science Center was doing a comparable

effort in getting such a policy. And so we basically got in touch with them and got feedback

and input from them. The headquarters of NWO was interested in our progress and there were

still some open questions. I will get back to those. I mean, I think the whole linking

thing is, well, as we have seen in the previous talks, it's an interesting one. We'll get

there in the final slides. I have some comments on things that are still relevant. Just to

give an illustration, this is the document history page of the document. So I think the

illustrative thing there is that after discussing it for almost a year, we had a version 1.0,

but it still took us until version 1.3 before we actually had a version that was actually

endorsed by the MT. So the subtleties are the devil is always in the details, I guess.

So just to go through the key points, so we picked the Apache 2.0 license. Part of it

is because, well, again, we wanted a permissive license because we felt that it fit the requirements

that we got from external the best. Yeah. And I think the reason that we wanted to pick

the license is also that we wanted to be sightable. Now, in principle, that doesn't have to do

with each other. But the issue is that we wanted to have a way to tell people that we

really like them to cite us when they use our code. And the Apache license has this

concept of notes file where you can sort of put in things that are not legally binding,

but are still, the file is sort of protected by the license, and it can tell people what

you actually want them to do. And of course, again, it's not the EULA, and we don't want

to go the EULA way, but you still can ask people very kindly to cite you if they use