WEBVTT 00:00.000 --> 00:10.000 Are you trying to leave this out? 00:10.000 --> 00:15.000 We need to stay as late as possible. 00:15.000 --> 00:20.000 Before we start with the presentation, 00:20.000 --> 00:24.000 I thank you for everybody who's organizing this room. 00:24.000 --> 00:28.000 So thanks to Leia, to Felix and to Thorsten and also to Sven who's helping us. 00:28.000 --> 00:30.000 So a round of applause on that. 00:36.000 --> 00:38.000 Yeah, great. 00:38.000 --> 00:40.000 Thanks for having us here. 00:40.000 --> 00:47.000 We are here to talk a little bit about the German perspective on how we currently working 00:47.000 --> 00:50.000 around building sovereign software for public sector. 00:50.000 --> 00:54.000 And I'm here with my colleague Alex. 00:54.000 --> 00:56.000 I'm responsible for the platform part. 00:56.000 --> 00:59.000 I'm part of the business where we talk a bit quite soon. 00:59.000 --> 01:04.000 And Alex, it was me here doing the products, 01:04.000 --> 01:07.000 all the products, products, and this. 01:07.000 --> 01:10.000 Maybe one starting point was big numbers. 01:10.000 --> 01:11.000 It's over there. 01:11.000 --> 01:15.000 So last year in Germany we spent more than one billion 01:15.000 --> 01:20.000 just on federal licenses for software within the German government. 01:20.000 --> 01:22.000 So it means there's a big question. 01:22.000 --> 01:25.000 This is also where we don't own, where we don't have an independent 01:25.000 --> 01:26.000 and sovereign solution. 01:26.000 --> 01:29.000 It's not innovation for society on a long term. 01:29.000 --> 01:32.000 So that's a point of stepping in and saying, 01:32.000 --> 01:36.000 okay, is there a part of this money that we could use for more sovereign 01:36.000 --> 01:38.000 perspective on that? 01:38.000 --> 01:42.000 And this is where the center of digital sovereignty came in place. 01:42.000 --> 01:46.000 It was founded two years ago, actually, 01:46.000 --> 01:49.000 but one year ago we really started stepping up. 01:49.000 --> 01:52.000 The idea came from government side saying five years ago, 01:52.000 --> 01:59.000 okay, we have the high level of dependency in the software, 01:59.000 --> 02:02.000 software stacks we're using at public sector. 02:02.000 --> 02:06.000 And we need to find a way of tackling those things. 02:06.000 --> 02:13.000 And the Zenis is a full state on property-owned company. 02:13.000 --> 02:17.000 Our function is, we just here, the Ospo term, 02:17.000 --> 02:20.000 being the open-source program office on one place, 02:20.000 --> 02:24.000 being working like an institution helping the public sector 02:24.000 --> 02:27.000 getting into those fields and into usage of that. 02:27.000 --> 02:30.000 And also being an active solution to play out, 02:30.000 --> 02:34.000 where we are providing things like open-desk for that administration. 02:34.000 --> 02:38.000 And we here's already some of our colleagues here talking about 02:38.000 --> 02:43.000 their President France and EU and we are kind in a close contact 02:43.000 --> 02:46.000 to each other and work together on those fields. 02:47.000 --> 02:50.000 Maybe a few words on the server entity term we work with. 02:50.000 --> 02:53.000 So I think one of the most important things 02:53.000 --> 02:56.000 is having a choice of choosing between options. 02:56.000 --> 02:59.000 So being not able doing that as a public sector 02:59.000 --> 03:02.000 is not like a big deal on negotiating and being contracts. 03:02.000 --> 03:04.000 So you're sitting there and saying, okay, I need that. 03:04.000 --> 03:06.000 Give me a price, I need to sign. 03:06.000 --> 03:10.000 And if you have a choice, if you have an option, you are able to go through. 03:10.000 --> 03:13.000 And we all know there's a lot of things to do 03:13.000 --> 03:17.000 to be getting back to the state where we are really able to choose between options 03:17.000 --> 03:18.000 and that way. 03:18.000 --> 03:20.000 And also for sure we need to adapt in the way. 03:20.000 --> 03:23.000 We need to bring our own features, our requirements into it, 03:23.000 --> 03:26.000 and also having a strong seat on the table, 03:26.000 --> 03:29.000 negotiating those things and defining how digital structure 03:29.000 --> 03:32.000 is defined in the common age. 03:32.000 --> 03:38.000 And that came to the two, one of the two main pillars we're working at the 03:38.000 --> 03:39.000 centers. 03:39.000 --> 03:42.000 The one is talking about products. 03:42.000 --> 03:46.000 And the other one is building a platform where distribution 03:46.000 --> 03:51.000 and the hospital ruling can take place for the whole public sector. 03:51.000 --> 03:54.000 And I will hand over to my colleague. 03:54.000 --> 03:55.000 Cool. 03:55.000 --> 03:56.000 Thanks. 03:56.000 --> 03:57.000 Perfect. 03:57.000 --> 04:02.000 We are always attached to each other just like the development circle 04:02.000 --> 04:05.000 so to say also in that regard. 04:06.000 --> 04:07.000 Yeah, open desk. 04:07.000 --> 04:10.000 Many of you already know of open desk, 04:10.000 --> 04:13.000 but we call it our office and collaborations with. 04:13.000 --> 04:16.000 And basically if you want to have a look at it, 04:16.000 --> 04:19.000 also just visit our website and get a demo, 04:19.000 --> 04:25.000 but also what you have is a bundle of applications in which you can have 04:25.000 --> 04:29.000 your day-to-day productivity, collaboration and also 04:29.000 --> 04:32.000 all sorts of communication, all in one. 04:33.000 --> 04:37.000 I think it's really important to say that. 04:37.000 --> 04:40.000 Open desk is something that we don't develop ourselves, 04:40.000 --> 04:43.000 but it's always a product which is based on a big, 04:43.000 --> 04:46.000 we call ourselves an open desk family, 04:46.000 --> 04:48.000 but but a network of partners. 04:48.000 --> 04:50.000 So we have a general service provider. 04:50.000 --> 04:53.000 We have a possibility to have a software as a service solution, 04:53.000 --> 04:57.000 but also we have a great network of partners. 04:57.000 --> 05:01.000 There was a deaf room just yesterday in the afternoon with. 05:01.000 --> 05:05.000 Many of the colleagues from all sorts of companies, 05:05.000 --> 05:10.000 some of them are here and obviously also going to maybe share and talk 05:10.000 --> 05:15.000 if you want to on their partnership with us and open desk. 05:15.000 --> 05:20.000 So it's a product which consists of many products actually. 05:20.000 --> 05:24.000 Yeah, I think it's really important just to, 05:24.000 --> 05:28.000 it's always good to give numbers in a presentation. 05:28.000 --> 05:34.000 So we launched in mid-October last year with our first enterprise solution. 05:34.000 --> 05:39.000 Ever since we had over a thousand different public institutions 05:39.000 --> 05:43.000 and administrations on all sorts of federal, state levels, 05:43.000 --> 05:46.000 but also from other countries asking us, 05:46.000 --> 05:49.000 giving us inquiries in regards to the usage of open desk, 05:49.000 --> 05:53.000 which is more than we ever hoped and expected at the beginning, 05:53.000 --> 05:57.000 but it's really cool and it shows that there is an urgent need 05:57.000 --> 06:02.000 and as of January we started also providing enterprise licenses 06:02.000 --> 06:05.000 to different partners, so to say, 06:05.000 --> 06:10.000 and we have over 40,000 active users by beginning of this month. 06:10.000 --> 06:14.000 So it's really cool to see that we are jumping all the time. 06:14.000 --> 06:18.000 We had a few thousand less which we announced in January. 06:18.000 --> 06:24.000 Now we are climbing a little bit, but we are going hopefully further up and up 06:25.000 --> 06:28.000 in that regard, so to say, and it's really important, I think, 06:28.000 --> 06:31.000 to show that it's not just a demo or a use case, 06:31.000 --> 06:37.000 which we're working on somewhere in a dark room with no window, 06:37.000 --> 06:43.000 but we have actually people using it and having it in their day-to-day lives. 06:43.000 --> 06:47.000 It's really important and that's one part of the sovereignty aspect, 06:47.000 --> 06:51.000 which we have is that there are different options how you can deploy it, 06:52.000 --> 06:55.000 sometimes especially for the non-tech world, 06:55.000 --> 06:59.000 so to say it's really, it sounds mind-blowing that you can have something 06:59.000 --> 07:01.000 not only as a software as a service solution, 07:01.000 --> 07:04.000 but also in a self-hosted environment nowadays. 07:04.000 --> 07:06.000 This is something which is really important, 07:06.000 --> 07:11.000 especially for institutions within the security sector, 07:11.000 --> 07:14.000 for example, sometimes we never talk about that, 07:14.000 --> 07:17.000 but there are projects with special infrastructure, 07:17.000 --> 07:20.000 where people are thinking about deploying open-desk. 07:20.000 --> 07:24.000 What we are also working on is a solution right now 07:24.000 --> 07:26.000 in regards to confidential cloud computing, 07:26.000 --> 07:31.000 because there are actually there are a few agencies, 07:31.000 --> 07:35.000 also in the German government, which are located mostly outside of Germany, 07:35.000 --> 07:38.000 so they need some sort of a secure access, 07:38.000 --> 07:41.000 and that's where we are with some of our partners 07:41.000 --> 07:44.000 looking into how we can deploy that, 07:44.000 --> 07:47.000 also thanks to that, because some of them are in the room. 07:47.000 --> 07:49.000 Next one. 07:49.000 --> 07:51.000 I think it's really important, and that's the topic, 07:51.000 --> 07:55.000 and that's where I'm going to start the story, 07:55.000 --> 07:59.000 so to say, of why we work on open-desk, on open-code, 07:59.000 --> 08:03.000 and what we call it, it's some sort of a developer experience. 08:03.000 --> 08:07.000 It's not the question in regards to what kind of two we want to put you get into, 08:07.000 --> 08:10.000 but it's the question what kind of outcome you can have 08:10.000 --> 08:13.000 when you use this kind of software. 08:13.000 --> 08:17.000 And if we go back, I don't know, who here is, 08:17.000 --> 08:22.000 is some sort of a public servant or in public administration? 08:22.000 --> 08:26.000 Okay, then the question the other way around, 08:26.000 --> 08:29.000 who is somewhere in the private sector? 08:29.000 --> 08:31.000 Cool. 08:31.000 --> 08:35.000 So you are the ones who I'm going to address right now. 08:35.000 --> 08:39.000 But basically, all of us sometimes had an idea, 08:39.000 --> 08:42.000 and we had an idea and we wanted to give it to somebody, 08:42.000 --> 08:44.000 and somebody within the public administration, 08:44.000 --> 08:49.000 because we say, public sector is a super cool place to host 08:49.000 --> 08:52.000 or to have your software in, 08:52.000 --> 08:54.000 and then you come to the public sector, 08:54.000 --> 08:56.000 and you say, I have an idea, and suddenly, 08:56.000 --> 09:01.000 the public sector, which is always a great sort of, 09:01.000 --> 09:05.000 this is some sort of a high and visual story right now, 09:05.000 --> 09:08.000 which you are experiencing. 09:08.000 --> 09:11.000 But then in the public sector, there are always restrictions, right? 09:11.000 --> 09:17.000 So there are restrictions in regards to security, 09:17.000 --> 09:19.000 procurement, we always hear that. 09:19.000 --> 09:22.000 There are questions in regards to quality, 09:22.000 --> 09:25.000 but also in regards to the support, which is being provided. 09:25.000 --> 09:29.000 And we always get the question on how to get in, 09:29.000 --> 09:32.000 and learn how can we get in. 09:32.000 --> 09:36.000 That's the point of taking over things. 09:36.000 --> 09:41.000 Yeah, so this is a part where we cannot only talk about 09:41.000 --> 09:44.000 the product part of this or anything, 09:44.000 --> 09:47.000 also we need to tackle the whole concept of access to it, 09:47.000 --> 09:50.000 of how to get into the tooling and the using 09:50.000 --> 09:52.000 and how to make it automated and really useful 09:52.000 --> 09:56.000 that we have stable and long-lasting tooling. 09:56.000 --> 09:58.000 So open code on that. 09:58.000 --> 10:02.000 Yeah, open code is also one of these key projects 10:02.000 --> 10:05.000 of the German government saying, okay, this is part. 10:06.000 --> 10:09.000 We use open code is an enabler for digital sovereignty 10:09.000 --> 10:12.000 for the whole sectors or everything around skills, services, 10:12.000 --> 10:15.000 and solution, which we need to strengthen those aspect. 10:15.000 --> 10:18.000 And for sure, this is being done with open source, 10:18.000 --> 10:20.000 because this is a toolkit that has helped us 10:20.000 --> 10:23.000 getting here very fast and much, much more 10:23.000 --> 10:26.000 progress on the line. 10:26.000 --> 10:29.000 In the beginning, and the whole start of a bit 10:29.000 --> 10:32.000 telling about the history of open code, which is two in a year. 10:32.000 --> 10:36.000 So now we've got to be in charge of sets 10:36.000 --> 10:40.000 since one year now with the zeniths. 10:40.000 --> 10:43.000 And it started as a software directory for the public sector, 10:43.000 --> 10:45.000 and we now discussing more and more around 10:45.000 --> 10:48.000 what does it mean as a platform for digital sovereignty? 10:48.000 --> 10:52.000 And in this, I was called the version one of open code 10:52.000 --> 10:55.000 when to get these more, all this question 10:55.000 --> 10:57.000 around the entry door, it was really important 10:57.000 --> 11:00.000 defining for the sector and the political aspect 11:00.000 --> 11:03.000 and what kind of, we need a software directory 11:03.000 --> 11:06.000 where we start collecting all those open source solutions 11:06.000 --> 11:08.000 because we realize there is a lot of this everywhere, 11:08.000 --> 11:11.000 also in the public sector, but we don't have any overview 11:11.000 --> 11:14.000 and that makes it really difficult getting into cooperation 11:14.000 --> 11:16.000 which is one of the key things of open source. 11:16.000 --> 11:20.000 So it's a big issue having a place there is important. 11:20.000 --> 11:23.000 So this was step one, then for sure, 11:23.000 --> 11:26.000 make a definition what is open source for the public sector. 11:26.000 --> 11:28.000 So yeah, this is not a new invention for sure. 11:28.000 --> 11:32.000 We used the OZ definitions, just made it 11:32.000 --> 11:37.000 in a more public sector, suitable effort 11:37.000 --> 11:42.000 and communication layer, usable for that as well. 11:42.000 --> 11:44.000 And then we started talking about license catalog 11:44.000 --> 11:48.000 because we have 13,000 public sector institutions in Germany 11:48.000 --> 11:54.000 when they all start getting knowledge about all the 500 different open source 11:54.000 --> 11:56.000 licenses out there on the country. 11:56.000 --> 11:58.000 It will never lead us anywhere. 11:58.000 --> 12:01.000 And these are these kind of questions we need to answer 12:01.000 --> 12:04.000 when a public sector wants to sign contracts around that. 12:04.000 --> 12:06.000 So we have now with open code one place 12:06.000 --> 12:09.000 where we legally checked over 500 open source solution 12:09.000 --> 12:11.000 that's all publicity on our website 12:11.000 --> 12:14.000 and made an allow list for the public sector saying 12:14.000 --> 12:17.000 when you have a component which sets open source 12:17.000 --> 12:20.000 and it uses license and it's good, you can go proceed 12:20.000 --> 12:23.000 for the next level of your contracts. 12:23.000 --> 12:26.000 And then sure it needs a platform collaboration. 12:26.000 --> 12:30.000 So any member of the public sector needs 12:30.000 --> 12:33.000 as a possibility collaborates there. 12:33.000 --> 12:38.000 And there's an unrestricted and freeway. 12:38.000 --> 12:42.000 And the last one is talking a lot about policy and government. 12:42.000 --> 12:46.000 So figuring out how can we now, when we have a place like this, 12:46.000 --> 12:50.000 how can we bring in the general daily processes of government. 12:50.000 --> 12:53.000 So this was the open code version one. 12:53.000 --> 12:57.000 And this is for sure this is how all the topics we are discussing here 12:57.000 --> 12:58.000 all about this. 12:58.000 --> 13:01.000 This covering and understanding open source sharing developing code 13:01.000 --> 13:03.000 for sure it's finding and using software. 13:03.000 --> 13:06.000 It's documenting and sharing all these knowledge. 13:06.000 --> 13:11.000 It's offering participation on forums and in our example 13:11.000 --> 13:14.000 we offer the discourse and where a lot of groups 13:14.000 --> 13:17.000 are changing their ideas and their experience 13:17.000 --> 13:21.000 from rebuilding community structure around that. 13:21.000 --> 13:24.000 And we give direct support to public sector members 13:24.000 --> 13:27.000 when they have questions how can I get onboard for this 13:27.000 --> 13:30.000 and their first steps for me to get into that. 13:30.000 --> 13:34.000 And for now we have around 4,500 users in Germany 13:34.000 --> 13:35.000 or around the projects. 13:35.000 --> 13:39.000 It's more than 1,000 public freeway level projects 13:39.000 --> 13:40.000 right now on the platform. 13:40.000 --> 13:43.000 Even more on the private side because sometimes needs time 13:43.000 --> 13:46.000 or have rather been into to work together 13:46.000 --> 13:49.000 and to get into using of these two links. 13:49.000 --> 13:52.000 And they also start now realizing, 13:52.000 --> 13:55.000 if I use something like a repository and like a good lab, 13:55.000 --> 13:57.000 there are two links like static pages. 13:57.000 --> 14:01.000 They make my life easier getting into website deployment 14:01.000 --> 14:02.000 out there. 14:02.000 --> 14:05.000 And this is something I don't need to have a long procurement process. 14:05.000 --> 14:07.000 This is two links all there. 14:07.000 --> 14:10.000 And we can really make things much, 14:11.000 --> 14:13.000 it's free in the way because it doesn't cost extra money 14:13.000 --> 14:14.000 and you can do it by your own. 14:14.000 --> 14:18.000 So it's self empowering in a broader way. 14:18.000 --> 14:23.000 So one of these overall layers on the platform open code 14:23.000 --> 14:26.000 is this being a community of many communities. 14:26.000 --> 14:29.000 So we don't have one community is more like we try having 14:29.000 --> 14:31.000 with our formats. 14:31.000 --> 14:32.000 We creating a zenders. 14:32.000 --> 14:35.000 A perspective saying we want to be having 14:35.000 --> 14:37.000 an overview of what kind of communities are out there 14:37.000 --> 14:39.000 and how can we bring them together. 14:39.000 --> 14:41.000 What's what's useful there, 14:41.000 --> 14:44.000 who needs maybe to talk to whom and to learn 14:44.000 --> 14:47.000 and to share experiences and stuff like that. 14:47.000 --> 14:51.000 We have two links which we get now out of these two 14:51.000 --> 14:54.000 box we have there and which we get more and more used 14:54.000 --> 14:57.000 by members of ministries and stuff like that. 14:57.000 --> 14:59.000 For example, one of this here is really interesting. 14:59.000 --> 15:03.000 There's a federal layer, the highest board, 15:03.000 --> 15:04.000 which we're just talking about. 15:04.000 --> 15:07.000 The architect, the IT architecture policy in Germany. 15:07.000 --> 15:09.000 And their process so far was sending emails 15:09.000 --> 15:12.000 and bringing all those answers year by year together 15:12.000 --> 15:17.000 and having an negotiated policy in a way. 15:17.000 --> 15:20.000 But for us it might be quite easy. 15:20.000 --> 15:22.000 OK, use the repository. 15:22.000 --> 15:26.000 Use it as a transparent way of organizing those content. 15:26.000 --> 15:28.000 And we need to get some steps, 15:28.000 --> 15:31.000 but then we also get a lot of possibility we never had before. 15:31.000 --> 15:34.000 So in this example we have a repository in the middle 15:34.000 --> 15:37.000 and we have a front end which makes it really easy 15:37.000 --> 15:39.000 comparing the different version, 15:39.000 --> 15:41.000 also colored layer for people who might not really 15:41.000 --> 15:45.000 have this one or see this on a get few. 15:45.000 --> 15:47.000 And on the output layer we can generate 15:47.000 --> 15:49.000 the next set of these versions, 15:49.000 --> 15:53.000 also generating accessible PDF document, 15:53.000 --> 15:56.000 license free or other machine-readable formats 15:56.000 --> 16:00.000 which might be used to connect with the next steps 16:00.000 --> 16:03.000 and processes we have there, but in this we accept. 16:03.000 --> 16:06.000 So the collaboration platform itself with this tool 16:06.000 --> 16:09.000 starts getting new concepts of how to use it. 16:09.000 --> 16:11.000 For the sector it's really big step. 16:11.000 --> 16:13.000 I know from many people in the room it might not be, 16:13.000 --> 16:16.000 but it's like a culture shift we're seeing right now 16:16.000 --> 16:20.000 which is I guess for everyone for us really important. 16:20.000 --> 16:22.000 We have a batch program. 16:22.000 --> 16:26.000 This is all about how can we record missophic quality. 16:26.000 --> 16:30.000 And currently we are on our way next month starting with the first batches 16:30.000 --> 16:32.000 in this case. 16:32.000 --> 16:35.000 When you have a repository in our software catalog, 16:35.000 --> 16:37.000 makes it really easy to understand, 16:37.000 --> 16:38.000 what can I use it? 16:38.000 --> 16:40.000 So there's a question in public sector. 16:40.000 --> 16:42.000 Yeah, this is software, but is it real? 16:42.000 --> 16:45.000 And can I use it and is it secure and all this stuff? 16:45.000 --> 16:49.000 So we think it's important that we add those extra information 16:49.000 --> 16:52.000 as much as we get an information on the software catalog 16:52.000 --> 16:55.000 and ensuring that there's a first understanding of, 16:55.000 --> 16:58.000 okay, it's a real thing and it's used by others. 16:58.000 --> 17:02.000 And it's also driven and run in operational environments 17:02.000 --> 17:03.000 and all this stuff. 17:03.000 --> 17:07.000 And maybe it's even already a bit of CV checked and all those things. 17:07.000 --> 17:10.000 So this is really important where you're getting open source 17:10.000 --> 17:15.000 and software and solutions into public sector. 17:15.000 --> 17:17.000 And then there's more, again, 17:17.000 --> 17:20.000 when it comes again to the server and it's high, 17:20.000 --> 17:22.000 we say, okay, this platform part, 17:22.000 --> 17:24.000 this has kind of a machine room in it. 17:24.000 --> 17:26.000 And on server and it, 17:26.000 --> 17:29.000 okay, when we talk about server and products like Open Desk, 17:29.000 --> 17:33.000 we now also need to think about how is this components 17:33.000 --> 17:36.000 of Open Desk, how gets they distributed? 17:36.000 --> 17:38.000 And what is the software development, 17:38.000 --> 17:40.000 the software supply chain underneath, 17:40.000 --> 17:42.000 that that's playing a role in that way, 17:42.000 --> 17:45.000 because only if we are able to look at this as well, 17:45.000 --> 17:48.000 we really can have and so when perspective as public sector 17:48.000 --> 17:51.000 means when we talk about Open Desk, 17:51.000 --> 17:54.000 we're talking about container technologies for sure 17:55.000 --> 17:57.000 and when it comes to container technologies, 17:57.000 --> 18:00.000 we need to raise a lot of question as actors. 18:00.000 --> 18:02.000 So the first one is stability in a way. 18:02.000 --> 18:07.000 So where is actually how reliable is these container distributed for us? 18:07.000 --> 18:10.000 So it's, or the question on a little bit other frame, 18:10.000 --> 18:13.000 what does that happen was our digital infrastructure 18:13.000 --> 18:17.000 when Docker happens down or has a kind of a new entry key on that. 18:17.000 --> 18:20.000 So I guess a lot of people in the room would stop being, 18:20.000 --> 18:23.000 okay, it's going to be a problem for me and maybe, 18:23.000 --> 18:25.000 the colleague says, well, and it's a lot of work to be done. 18:25.000 --> 18:28.000 So but actually the main point is we are not really 18:28.000 --> 18:31.000 currently prepared around situations like that 18:31.000 --> 18:34.000 and the problem and it might be really big success 18:34.000 --> 18:36.000 in the last 20 years in the digitalization, 18:36.000 --> 18:39.000 but we kind of proceed the next decade on that. 18:39.000 --> 18:41.000 Security at all on this supply chain, 18:41.000 --> 18:43.000 what is the chain of a way, 18:43.000 --> 18:45.000 this container came to me, 18:45.000 --> 18:47.000 can I have a look into it now, not really, 18:47.000 --> 18:49.000 so no chance on this way. 18:49.000 --> 18:52.000 And who created this container anyway? 18:52.000 --> 18:55.000 So I would say from the, okay, some of these containers 18:55.000 --> 18:57.000 we're using there just from the internet, 18:57.000 --> 18:59.000 so I don't know more. 18:59.000 --> 19:01.000 I guess on content wise, 19:01.000 --> 19:03.000 it has not been always a good idea, 19:03.000 --> 19:05.000 just taking the stuff from the internet and it's 19:05.000 --> 19:08.000 think we don't should do it with the core components as well. 19:08.000 --> 19:10.000 And then we had a lot of talks around, 19:10.000 --> 19:12.000 and I think there's a whole deaf room as well, 19:12.000 --> 19:15.000 and yesterday we really go talk about the ass bombs. 19:15.000 --> 19:17.000 Yeah, there's this ass bombs and it looks good, 19:17.000 --> 19:19.000 okay, we have a long list of things on it, 19:19.000 --> 19:21.000 but we are not really having the two things working with it. 19:21.000 --> 19:24.000 Making detection and allergies and all these stuff, 19:24.000 --> 19:27.000 which we need to have this as a really good tooling, 19:27.000 --> 19:29.000 ensuring this is proper software. 19:29.000 --> 19:32.000 So we are highly depending on those things, 19:32.000 --> 19:36.000 so we have to address this as public sector, 19:36.000 --> 19:40.000 meaning being an infrastructure provider by itself, 19:40.000 --> 19:44.000 going into this role and offering solutions on that, 19:44.000 --> 19:48.000 thinking about offering decentralized container, 19:48.000 --> 19:50.000 image supply infrastructure, 19:50.000 --> 19:53.000 so also there, we just tiered on the news side, 19:53.000 --> 19:56.000 but it means on structural infrastructure layers, 19:56.000 --> 20:01.000 but it also says it's really important if you want to be stable on cloud. 20:01.000 --> 20:05.000 There's a lot about hardening and ensuring the container safety. 20:05.000 --> 20:07.000 For now, we don't really have, 20:07.000 --> 20:10.000 there's a correct rules and criteria as negotiated, 20:10.000 --> 20:13.000 that makes it able to put a stamp on the container and say, 20:13.000 --> 20:17.000 okay, this is the rules and criteria we need in the public sector. 20:17.000 --> 20:21.000 It's still a lot of work to be done working on that. 20:21.000 --> 20:26.000 And then all these two links around as bombs and around. 20:26.000 --> 20:28.000 For us, at open-coded means, 20:28.000 --> 20:31.000 this is our next list of things we currently want to welcome, 20:31.000 --> 20:34.000 saying this is really what we need on this supply chain. 20:34.000 --> 20:36.000 And when the distribution infrastructure, 20:36.000 --> 20:39.000 we want to provide a secure build and development environment 20:39.000 --> 20:42.000 for developing those service, 20:42.000 --> 20:46.000 we already put in an attestation service around open-desk. 20:46.000 --> 20:49.000 We want to establish this registry for all these artifacts 20:49.000 --> 20:51.000 that we can use and also rebuild, 20:51.000 --> 20:55.000 so being able to really know what's in there, what we're using. 20:55.000 --> 20:59.000 We need to negotiate more on the criteria for this supply chain evidence 20:59.000 --> 21:00.000 and builds. 21:00.000 --> 21:05.000 And all these build up on a more decentralized distribution concept. 21:05.000 --> 21:08.000 Because we're not going to grab one again. 21:08.000 --> 21:11.000 What's our relation, so to say, to the partners, 21:11.000 --> 21:15.000 which we work with at open-desk, 21:15.000 --> 21:20.000 and what comes with contribution, so to say, in that regard. 21:20.000 --> 21:23.000 Feature requests we do, it's a long process of planning. 21:23.000 --> 21:26.000 Maybe two colleagues can raise their hands, 21:26.000 --> 21:28.000 run a and victor. 21:28.000 --> 21:31.000 If you have questions in regards to product or tech, 21:31.000 --> 21:34.000 these are the guys who are building open-desk. 21:34.000 --> 21:40.000 And everything we do, two main things I think to mention. 21:40.000 --> 21:43.000 First, all the contributions, which we do, 21:43.000 --> 21:46.000 are part of the open-desk community edition. 21:46.000 --> 21:49.000 We don't fund anything which is behind, 21:49.000 --> 21:52.000 behind some sort of a fence. 21:52.000 --> 21:56.000 That's one thing and the other thing is that everything that we do 21:56.000 --> 21:59.000 is always upstream within the products. 21:59.000 --> 22:03.000 So whenever there is something that we invest into one of the products, 22:03.000 --> 22:06.000 it always also benefits, 22:06.000 --> 22:09.000 or is beneficiary for the entire community. 22:09.000 --> 22:11.000 Next question. 22:11.000 --> 22:13.000 One of the. 22:13.000 --> 22:19.000 Could you maybe talk about your collaboration with France and the less we? 22:19.000 --> 22:24.000 And I also understood that the netlets are entering that collaboration, so. 22:24.000 --> 22:25.000 Yeah. 22:25.000 --> 22:27.000 We had, yeah, thanks. 22:27.000 --> 22:29.000 Thank you, my own card. 22:29.000 --> 22:33.000 The question is in regards to how we work with France and with the Netherlands. 22:33.000 --> 22:36.000 We had a session this morning already on that regard, 22:36.000 --> 22:40.000 and we will have one, the one after the panel. 22:40.000 --> 22:43.000 So it's in half an hour or so. 22:43.000 --> 22:47.000 So you can see the results of our collaboration, so to say. 22:47.000 --> 22:51.000 Basically, we work together on joint projects because we see that digital 22:51.000 --> 22:54.000 sovereignty does not end at once borders. 22:54.000 --> 22:59.000 And you can use the same open source tools in different products and sweet. 22:59.000 --> 23:00.000 Yeah. 23:00.000 --> 23:15.000 So the question is, if we want to do something with other countries, 23:15.000 --> 23:18.000 do we need an umbrella or is it grass roots? 23:18.000 --> 23:25.000 I think so far and it's proven as properly that grass roots is a good way to start that. 23:25.000 --> 23:28.000 But at some point you will need an umbrella. 23:28.000 --> 23:32.000 But the umbrella should not dictate because usually whenever there is an umbrella, 23:32.000 --> 23:36.000 someone in the grass roots or in the bottom sort of phase holding it, 23:36.000 --> 23:38.000 and that should be kept in motion. 23:38.000 --> 23:39.000 That way. 23:39.000 --> 23:43.000 Could you explain to your plans on the espontal chain? 23:43.000 --> 23:45.000 Well. 23:45.000 --> 23:47.000 Exactly. 23:47.000 --> 23:49.000 Exactly. 23:49.000 --> 23:53.000 Currently, I think I will maybe get to back to this one. 23:53.000 --> 23:57.000 The question was to expand on the espontal chain, which is just mentioned. 23:57.000 --> 23:59.000 So what else is the thing? 23:59.000 --> 24:03.000 We currently working on this batch program saying, OK, there is a lot of open source 24:03.000 --> 24:07.000 tooling around which helps us doing analysis and espont creation. 24:07.000 --> 24:13.000 So we use, for example, the open source as the or toolkit or or the three 24:13.000 --> 24:15.000 before containers scanning and all these stuff. 24:15.000 --> 24:20.000 We also using for a software catalog and standard, which is called public 24:20.000 --> 24:21.000 in the summer. 24:21.000 --> 24:25.000 And the ideas we need to bring the results of this running and automated as much as 24:25.000 --> 24:26.000 possible. 24:26.000 --> 24:28.000 And also scaling it up to the eggs. 24:28.000 --> 24:29.000 So make it possible. 24:29.000 --> 24:30.000 That's the reality. 24:30.000 --> 24:35.000 It's get aggregated to something which I really can see in the software catalog and 24:35.000 --> 24:38.000 giving me first impression of this. 24:38.000 --> 24:43.000 For example, OK, the CV is scanned and nothing found for today and for now. 24:43.000 --> 24:44.000 So for example. 24:44.000 --> 24:48.000 But I think we need to expand this quite a lot more because all around this, 24:48.000 --> 24:53.000 having a project like open desk with maybe thousands of entries on the espont. 24:53.000 --> 24:58.000 It's like it's a really huge thing getting it automated and 24:58.000 --> 25:02.000 and day by day generated and having good analysis on this. 25:02.000 --> 25:07.000 So I think there needs to be developed much more on the tool chain for now. 25:07.000 --> 25:09.000 OK, there's many more questions. 25:09.000 --> 25:10.000 Please reach out. 25:10.000 --> 25:11.000 But we have time for one. 25:11.000 --> 25:12.000 One question. 25:12.000 --> 25:13.000 OK, one question. 25:13.000 --> 25:15.000 You decide. 25:15.000 --> 25:16.000 I'll be there. 25:16.000 --> 25:21.000 I guess I want to open desk a project. 25:21.000 --> 25:25.000 It's only for the software. 25:25.000 --> 25:30.000 I always want to say something in our line of settings. 25:30.000 --> 25:31.000 Let's explore. 25:31.000 --> 25:34.000 If you have line also for the open. 25:34.000 --> 25:35.000 The. 25:35.000 --> 25:36.000 The. 25:36.000 --> 25:37.000 The. 25:37.000 --> 25:38.000 The. 25:38.000 --> 25:39.000 The. 25:39.000 --> 25:40.000 The. 25:40.000 --> 25:45.000 The. 25:45.000 --> 25:50.000 The. 25:50.000 --> 25:52.000 The. 25:52.000 --> 25:54.000 The. 25:54.000 --> 25:55.000 The. 25:55.000 --> 25:57.000 I get the idea and maybe that's a good user so the question was whether it's just the web or maybe also an operating system and let's see each other next year. 25:57.000 --> 25:59.000 And then we will talk about that. 25:59.000 --> 26:00.000 And. 26:00.000 --> 26:05.000 Before we go before we go before we go we go we do something really German 26:05.000 --> 26:07.000 And it's called store's lifting. 26:07.000 --> 26:14.000 Please open the door and open the windows and you will see each other on we see each other in the next panel. Thank you guys