WEBVTT

00:00.000 --> 00:10.000
Thanks again for joining us.

00:10.000 --> 00:16.000
The next poll will be the 100-day turn-hours advancing European sovereign IT together

00:16.000 --> 00:18.000
with Alexander.

00:18.000 --> 00:23.000
Thank you.

00:23.000 --> 00:25.000
Thanks everybody for joining.

00:25.000 --> 00:29.200
I think it's a topic which we will have at first and now throughout many different

00:29.200 --> 00:32.800
deaf rooms and we always have a different perspective.

00:32.800 --> 00:33.800
It's never the same talk.

00:33.800 --> 00:38.800
It's always something like the topic is or the titles are similar but the outcomes

00:38.800 --> 00:40.800
are always very different.

00:40.800 --> 00:46.000
I think it's really important to everybody to get to know what we are doing actually

00:46.000 --> 00:51.000
to have or to share some history with all of you guys.

00:51.000 --> 00:55.800
And this is the most text that you will ever get from me but it's important to have

00:55.800 --> 00:56.800
it condensed.

00:56.800 --> 01:03.200
I think it's really important that a few years ago sovereignty wasn't a sexy topic back then.

01:03.200 --> 01:09.200
It was something that people started to think about but there was no really exterior vision

01:09.200 --> 01:14.200
or some sort of group which was working all together.

01:14.200 --> 01:19.800
And in 2019 the federal government and Germany decided that they need to have some sort

01:19.800 --> 01:24.600
of a market analysis on how dependent actually their infrastructure would be.

01:24.600 --> 01:30.400
And they figured out that for example I think 95% obviously of all computers have been

01:30.400 --> 01:33.400
using Microsoft tools.

01:33.400 --> 01:41.400
From that there was a yearly race which began in 2020 the different councils which we have

01:41.400 --> 01:47.200
for IT and digital decisions within the government decided that we need some sort of

01:47.200 --> 01:49.000
key principle.

01:49.000 --> 01:54.000
And then the following year also a strategy to found basically Tendis Tendis is a

01:54.000 --> 02:01.000
fully federal yet private company which is owned by the state and Tendis is basically

02:01.000 --> 02:07.600
an typical German bureaucratic abbreviation for a center for digital sovereignty.

02:07.600 --> 02:15.000
Back in 2023 the federal government decided that we should start, we should start funding

02:15.200 --> 02:21.800
actually an initiative back then which was working on tool which was a certain workspace.

02:21.800 --> 02:28.000
And then in 2024 actually when the people at Tendis started operating and also the

02:28.000 --> 02:36.200
colleagues at Dnum the French counterpart also started working on things together.

02:36.200 --> 02:41.000
We decided that we should launch at some point it should not only be a project but actually

02:41.200 --> 02:48.000
product so that so that people understand that it's something serious and at the same time it was

02:48.000 --> 02:55.000
also roughly I think spring of 2024 when France and Germany decided that we should create

02:55.000 --> 03:02.000
the 100-day challenges and we will come to the idea and everything in a second.

03:02.000 --> 03:08.600
Fast forward to last year Netherlands joined us as a third country and now there are even more

03:09.600 --> 03:17.600
countries who are joining us. Just a brief one we had in Vilanst talk we had open desk as a

03:17.600 --> 03:23.600
mention at least but who in this room knows what open desk is? Cool that's really cool.

03:23.600 --> 03:34.600
For those who don't know it yet it's a workspace solution which we are building with the focus of federal

03:34.600 --> 03:39.600
governments. It's really important to understand that it's something that is being conducted by

03:39.600 --> 03:45.600
Tendis but it's actually a big European community standing right behind it. We have open

03:45.600 --> 03:49.600
exchange we have Nordic we have element we have open project which we just heard callaboga

03:49.600 --> 03:56.600
XWiki next cloud you mentioned and then we have also hosting provider and a service provider behind

03:56.600 --> 04:02.600
that and I think on that note and also seeing the partners some of them who are here as well.

04:02.600 --> 04:09.600
Thanks for that and also thanks to Klimo for organizing this demo maybe a brick.

04:09.600 --> 04:21.600
So we love everybody but it's really important and I think it's key that we also have a federal

04:21.600 --> 04:27.600
ministry for digital transformation right now and state modernization which is supporting Tendis

04:27.600 --> 04:35.600
and also that course. So in 2024 we had last week and we had opened desk to switch which

04:35.600 --> 04:43.600
were about to launch and then we met and we thought that there was like on a political level

04:43.600 --> 04:49.600
people were working on I think two and a half years on the document and then it was signed and then

04:49.600 --> 04:55.600
we said okay let's start working actually together and we figured that we need to have

04:55.600 --> 05:02.600
some sort of a framework in which we work and I think it was like past lunch break or so we said

05:02.600 --> 05:08.600
we need some sort of a fancy title and we decided on working on 100 day challenges.

05:08.600 --> 05:13.600
Up until today nobody really knows who's investing just 100 days whether it's in total,

05:13.600 --> 05:19.600
whether it's whether it's it's country but but we are figuring that out right now it's

05:20.600 --> 05:23.600
maybe we will do a challenge on that as well.

05:23.600 --> 05:30.600
But the idea is to have some sort of a not that bureaucratic but the framework in which we can actually

05:30.600 --> 05:36.600
work together to have some sort of an approval from different governmental bodies to

05:36.600 --> 05:44.600
invest into standards and to develop joint IT solutions. I think it's really important to understand that

05:44.600 --> 05:51.600
for example a federal government it's open source is a complete movement like it's a it's some sort

05:51.600 --> 05:58.600
of a financial nightmare also because you you can't invest into something that is being used

05:58.600 --> 06:02.600
by federal states for example in Germany if you are the federal government and yet open

06:02.600 --> 06:07.600
source is available to everybody and then you have to figure out how to explain to people

06:07.600 --> 06:13.600
that that is actually still legal to do that and now we come to the question in regards to

06:13.600 --> 06:19.600
how to invest in joint projects across borders and that's something that's really

06:19.600 --> 06:25.600
interesting. 100 days challenges which we do have different topics obviously there is AI

06:25.600 --> 06:31.600
we work also on standards not only in regards to what 100 day challenge would be but also on how

06:31.600 --> 06:36.600
we want to work together for example if even if there are two organizations you will still have

06:36.600 --> 06:44.600
just one repository somewhere who owns it what's the community like stuff like that and

06:44.600 --> 06:53.600
from there on when in last year we had the Netherlands joining us we we started to

06:53.600 --> 06:59.600
understand that there were not only technical questions but also sometimes differences or

06:59.600 --> 07:05.600
there's a hard topic in regards to how actually for example three countries can work together

07:05.600 --> 07:11.600
you imagine on like what would be like a big hurdle if you work in a triangle of different

07:11.600 --> 07:22.600
nations like language what else working culture put your mind thanks once again

07:22.600 --> 07:29.600
three people in charge oh if it would be only three I would be really happy

07:29.600 --> 07:39.600
just playing different goals different goals yes processes okay you are all correct yet

07:39.600 --> 07:45.600
the biggest hurdle that we had on providing a trilateral contract was actually the paper and

07:45.600 --> 07:52.600
the folders because every country has a separate set of paper like a type of paper on which you have

07:52.600 --> 07:57.600
to sign documents and also the question of the seal is really difficult and apparently

07:57.600 --> 08:02.600
Germany even has many different seals so that was that was interesting but at the same

08:02.600 --> 08:06.600
time it's really interesting to see that actually everything that you guys said was true

08:06.600 --> 08:13.600
I think it's really interesting to see different organizations even public organizations

08:13.600 --> 08:19.600
working with different languages or finding a common language and also the common understanding

08:19.600 --> 08:25.600
and definition of terms for example I don't know who of you is coming from France

08:26.600 --> 08:34.600
cool anyone from the Netherlands cool anyone from Germany and guess what all three nations

08:34.600 --> 08:43.600
have a different definition of what sovereignty is because of history but also of current political

08:43.600 --> 08:49.600
issues I think it's really important that all these differences that we have actually

08:50.600 --> 08:56.600
because we do have a similar goal in which we are all thriving or trying to reach out

08:56.600 --> 09:02.600
and we have a set in regards to how we want to work together and we have and that's

09:02.600 --> 09:11.600
what I really like we have some sort of teams in which people do not really feel or identify

09:11.600 --> 09:17.600
themselves as we are the German part we are the Dutch part we are the French part but they all work

09:17.600 --> 09:24.600
together on the same goal and that's really important to create and to facilitate such

09:24.600 --> 09:29.600
such an environment basically which is usually something where you would see maybe

09:29.600 --> 09:34.600
rivalries or something similar to that.

09:34.600 --> 09:40.600
We did have and we are still continuing on having certain success stories one of them being

09:41.600 --> 09:49.600
docs at two which was on hack and use for a while on number one but we created

09:49.600 --> 09:54.600
or we continued further development on that and also integrated that into our sweet

09:54.600 --> 10:00.600
and we are funding block notes library which is really cool not only to provide

10:00.600 --> 10:05.600
basically further development when it comes to tools but also to libraries I think it's

10:05.600 --> 10:12.600
super important to see how you can reuse the same libraries it's saving costs but

10:12.600 --> 10:17.600
it's also saving or it's improving user experience if you have different tools or

10:17.600 --> 10:21.600
components which are using the same framework right behind it.

10:21.600 --> 10:27.600
Mine below which is the Dutch version of the combination of last written open desk

10:27.600 --> 10:33.600
is also a success story which is really cool for all of us because we are not only

10:33.600 --> 10:39.600
talking about open source but we can actually see how if you want to combine things or

10:39.600 --> 10:46.600
interchange open source sweets how it's actually being conducted and how you can improve

10:46.600 --> 10:48.600
that.

10:48.600 --> 10:52.600
Maybe an outlook on what the teams are working on right now.

10:52.600 --> 11:00.600
We have René from our team who is also in charge of organizing right now the different

11:00.600 --> 11:08.600
challenges which are on this slide all of us are working on on maybe an early stage

11:08.600 --> 11:14.600
of an operating system, a joint operating system and we are working on a showcase in this

11:14.600 --> 11:15.600
year.

11:15.600 --> 11:20.600
I think it's really cool to see global search as a topic which is really difficult if you

11:20.600 --> 11:25.600
have different applications and different search components how you can actually interact

11:25.600 --> 11:29.600
and combine them all together in a joint search bar.

11:29.600 --> 11:33.600
It's really important still, that's what I meant.

11:33.600 --> 11:38.600
We need to document on how we work together and we need to figure out this year we said

11:38.600 --> 11:43.600
like two years is enough and we should figure out what 100 day challenge actually is.

11:43.600 --> 11:51.600
And what we also working on is removing forks which we also did right now because of

11:51.600 --> 11:58.600
basically the speed which we were at in regards to integration of tools in between

11:58.600 --> 12:03.600
each other and that's what we want to do with the force challenge.

12:03.600 --> 12:09.600
I think it's really important to say thanks to the different teams.

12:09.600 --> 12:15.600
That wasn't part of their job description to work in international projects but also a big

12:15.600 --> 12:23.600
thank you to actually to older decision makers and there are more than three who are supporting

12:23.600 --> 12:28.600
us in regards to actually having that sort of a corporation.

12:28.600 --> 12:35.600
It's usually whenever nations are cooperating it's very text heavy and you don't see results

12:35.600 --> 12:36.600
that fast.

12:36.600 --> 12:43.600
In our case we got the approval so to say to have results before the paperwork is done

12:43.600 --> 12:47.600
and that's something that is very unusual.

12:47.600 --> 12:53.600
I think it's super important that we keep that kind of spirit right now.

12:53.600 --> 12:59.600
We also got support by the European Commission to establish some sort of a structure

12:59.600 --> 13:05.600
underlying these challenges and to have also some sort of a legal body to actually work together

13:05.600 --> 13:11.600
because once there is code there is also certain dependencies if a government is using them

13:11.600 --> 13:18.600
and we want to ensure that there is not really like some sort of government change or so

13:18.600 --> 13:25.600
which can be in the way that we have and it's really interesting like one last anecdote

13:25.600 --> 13:33.600
maybe we always thought about sovereignty in regards to when we started with that from a German perspective

13:33.600 --> 13:40.600
that we need to think about what kind of contingency there would be and then we had France as a partner

13:40.600 --> 13:48.600
we thought that's maybe something stable to have that and then the Dutch government also joined us

13:48.600 --> 13:59.600
and maybe if you re-vind or so the last 18 months or so all three governments had government changes within six months

13:59.600 --> 14:06.600
and that shows but the project is still continuing and it's really important to see that you need partners

14:06.600 --> 14:13.600
and you need to have some sort of stability to also provide from a public perspective and ecosystem

14:13.600 --> 14:17.600
and to continue to work on certain topics.

14:17.600 --> 14:26.600
If you want to know more about some of the tools but also some of the components which we have we also have a deafening which is happening right now

14:26.600 --> 14:33.600
the colleagues from France will explain a different side of the story like the playbook of it in 15 minutes

14:33.600 --> 14:41.600
so if you want to go run otherwise you can also visit all the websites of the tools and I'm here for a few more questions

14:41.600 --> 14:46.600
thanks

14:54.600 --> 14:58.600
Okay so the question is what's the difference between open desk and last week

14:59.600 --> 15:08.600
I would say we have like an overlap of maybe 65% or so of all the components but we have a completely different approach

15:08.600 --> 15:14.600
whereas last week is building and supporting tools by themselves

15:14.600 --> 15:20.600
we rely on the different partners that we have within the network

15:20.600 --> 15:28.600
and everything that we are requesting or supporting is always going into the upstream components of the products

15:28.600 --> 15:30.600
yes

15:30.600 --> 15:34.600
Open OS versus UOS

15:34.600 --> 15:38.600
Why do you just exist already?

15:38.600 --> 15:42.600
The question is open OS versus UOS

15:42.600 --> 15:46.600
Open desk is also a bunch or a bundle of different products

15:47.600 --> 15:56.600
We still keep their names. We are looking into UOS you can see or I think he was just right now in our deafroom

15:56.600 --> 16:01.600
UOS is something that we are definitely looking into it's a community-based project

16:01.600 --> 16:11.600
Yet at the same time we are looking into the idea of UOS at the same time we see certain hurdles in regards to the choice of the underlying operating system

16:12.600 --> 16:14.600
So technical differences?

16:14.600 --> 16:16.600
Yep but also the country

16:16.600 --> 16:17.600
Nudo

16:17.600 --> 16:22.600
The question is so this organization looks a lot like an innovation lab

16:22.600 --> 16:25.600
a place where a lot of innovation can happen

16:25.600 --> 16:28.600
two questions for that one is

16:28.600 --> 16:35.600
isn't there how can actually other open source communities participate to that innovation lab

16:35.600 --> 16:38.600
which I think could also help make use of it

16:38.600 --> 16:42.600
but this thing companies instead of trying to reinvent things sometimes

16:42.600 --> 16:44.600
maybe make use of things that already exists

16:44.600 --> 16:46.600
that other people are already working on

16:46.600 --> 16:48.600
because there is innovation all around UOS

16:48.600 --> 16:51.600
The second question is

16:51.600 --> 16:55.600
isn't there also a risk that it creates a lot of innovation

16:55.600 --> 17:00.600
and doesn't focus on maintenance of a lot of components

17:00.600 --> 17:06.600
and that there is a risk of creating creating and creating too much versus

17:06.600 --> 17:09.600
the need for maintenance of professional solution

17:09.600 --> 17:11.600
What should you take on that?

17:11.600 --> 17:16.600
So two questions one is how can I try to paraphrase it?

17:16.600 --> 17:20.600
How can the community participate in the 100-day challenges?

17:20.600 --> 17:23.600
What's the first one let me try to answer on that?

17:23.600 --> 17:31.600
We have or last December so two months ago a European consortium on digital goods

17:31.600 --> 17:34.600
or digital comments was founded

17:34.600 --> 17:39.600
and which the community will be also taking a big part in supporting

17:39.600 --> 17:42.600
and maintaining and also being funded by that

17:42.600 --> 17:45.600
that's something that is being ramped up right now as we speak

17:45.600 --> 17:52.600
that's one thing the other one in regards to building versus maintaining products

17:52.600 --> 17:55.600
I think it's really interesting right now for us to see

17:55.600 --> 17:59.600
that if there are many or if there are different teams joining us

17:59.600 --> 18:07.600
how can we keep the creation level so to say maybe at the same pace

18:07.600 --> 18:13.600
but divert it into different teams so that people do not lose focus on providing

18:13.600 --> 18:18.600
a good tool which needs to be maintained at the same time

18:18.600 --> 18:23.600
There was a hand

18:23.600 --> 18:28.600
which you had spawned on different issues of sovereignty

18:28.600 --> 18:30.600
and maybe especially

18:30.600 --> 18:34.600
well

18:34.600 --> 18:38.600
So the question is the differences of sovereignty

18:38.600 --> 18:42.600
I'm not I think this is not the building for political sciences

18:42.600 --> 18:44.600
but there is one right next door

18:44.600 --> 18:49.600
but if you have some spare time just

18:50.600 --> 18:54.600
have a look at the definitions of autonomy and sovereignty in the different countries

18:54.600 --> 18:59.600
maybe that's a hint for an AI or so

19:00.600 --> 19:03.600
Both of these questions may be more funding

19:03.600 --> 19:06.600
but different general impact

19:06.600 --> 19:08.600
why is the status of New York and New York

19:08.600 --> 19:13.600
because we know that New York and New York is severely used

19:13.600 --> 19:15.600
in Microsoft based products so

19:15.600 --> 19:19.600
how they support you or is there a new way

19:19.600 --> 19:24.600
that is going to make sense but they should view

19:25.600 --> 19:31.600
So the question is how the European Union is playing a role in that

19:31.600 --> 19:35.600
the European consortium on digital comments

19:35.600 --> 19:38.600
is I think the answer of the European Union in that regard

19:38.600 --> 19:43.600
is going to be funded and supported by the European Union

19:43.600 --> 19:45.600
as well as the countries who are participating in that

19:45.600 --> 19:52.600
and I think the European Union is taking a good role of a facilitator

19:54.600 --> 19:56.600
and I think the European Union is going to be funded

19:56.600 --> 19:58.600
and I think the European Union is going to be funded

19:58.600 --> 20:00.600
and I think the European Union is going to be funded

20:00.600 --> 20:02.600
and I think the European Union is going to be funded

20:02.600 --> 20:04.600
and I think the European Union is going to be funded

20:04.600 --> 20:06.600
and I think the European Union is going to be funded

20:06.600 --> 20:08.600
and I think the European Union is going to be funded

20:08.600 --> 20:10.600
and I think the European Union is going to be funded

20:10.600 --> 20:12.600
and I think the European Union is going to be funded

20:12.600 --> 20:14.600
and I think the European Union is going to be funded

20:14.600 --> 20:16.600
and I think the European Union is going to be funded

20:16.600 --> 20:18.600
and I think the European Union is going to be funded

20:18.600 --> 20:20.600
and I think the European Union is going to be funded

20:20.600 --> 20:22.600
and I think the European Union is going to be funded