Okay, so thanks for the previous presentations. Both of them were very, very good and they

covered some of the topics I was going to discuss. But what I was also wondering while

listening to them is, it would have been so great to have all these discussions before

I entered this enterprise of licensing because, so I'm not a lawyer, right? I'm just a physicist

with a mission and the mission in CTA is to build a software world package and a software

product which is the array control and data acquisition software which is responsible

of coordinating the control of all the telescopes, acquire the data, implement a real-time analysis

and give an interface to the operators in the control rooms. And since my world package

is going, let's say, is one of the fastest or the first who will provide real software

release contributions, we came to the situation that we need to organize in-kind contributions

with the contributors and we realized that we don't have any licensing policy at all

in CTA. So I stand up and work with my colleagues, with Mathias Fussling and others in CTA. We

look around, we talk with experts outside and we basically do this policy which we are

now very advanced, not analyzed, but very much discussed inside the project. Just to

give you an idea, a simplified view of what's the landscape of CTA software contributors,

we have a legal entity which has direct powers. At this moment, it's a German company, a GMBH,

but it will evolve to an ERIC, to a European Union level entity. And we have in-kind contributors

and the main, I'm simplifying it, but the main product is central software systems like

the one I coordinate or software systems which are used to process data or to offer an archive,

things like that. And we also have array elements, meaning here telescopes or weather stations

which have their own control software. And basically, we formally, the project office

are responsible of the central software systems, so we are responsible of organizing them and

making sure they arrive. But the main workforce comes from in-kind contributors which are

from entities like that will sign and sign in-kind contribution agreements with the CTA

organization. So we together, we do the central software systems, but not only because we

also will have industry contracts and sometimes we will not have any in-kind contributor to

do a certain modular subsystem and then in those cases either we will directly hire the

industry ourselves or we will develop software ourselves as central organization personnel,

but also some of our in-kind contributors will do their in-kind contributions sometimes

as their own developers from software engineers down to PhD students, but also sometimes get

contracts directly themselves to industry and then give to us, to our software, the

in-kind contribution. And of course, another thing is that the in-kind contributors are

themselves responsible of giving complete array elements. So for example, in CTA we

have so-called large size telescope, we have medium size telescope and small size telescope.

So the large size telescope work package is responsible to deliver the whole product which

includes all the control systems and also the high level software which plugs with the

central control system. So they have to also develop this software. But we also have a

CTA consortium. It's a consortium made of 1500 people which is basically the collection

of the high energy gamma ray community which basically started the concept of CTA. They

have the general idea, it collects all the physicists, but it also collects a lot of

people which are working in things like machine learning, in things of data reduction, all

these things. And there is an analysis simulation working group that they also develop software

and of course this knowledge and this work must be incorporated. So they provide support

to let's say to the central organization, but also to in-kind contributors. And then

there is a community software that we may want to use and we may also contribute to

this community software because we will also want to use. And there may be external contributors

that you know are not members at all of CTA, but they say, well, I would like to help you

in your software. So I should say no, right? And they may support our development. So why

does CTA and contributors need a software license in policy? Well, I think I don't need

to repeat it. I think we are convinced now based on Karina's and Jutta's presentations