WEBVTT 00:00.000 --> 00:19.000 Hello everybody, nice to meet you. I will quickly myself and Benjamin, but before this presentation 00:19.000 --> 00:27.240 may be just a fun fact. We just, the situation is quite obvious today, we have to imagine 00:27.240 --> 00:36.040 how we could take the opportunity to find a solution, to disfight, which has been in for 00:36.040 --> 00:42.360 few years. So what do we speak from? I'm the director of the strategy of Twig, the AI, which 00:42.360 --> 00:53.320 is an open source workplace developed by Gina Gohar and Samuel. I'm leading the last 00:53.320 --> 00:59.280 suite project for the French government, so that's a digital workspace, we're trying 00:59.280 --> 01:08.920 to give to our state agents about 3 million agents. 01:08.920 --> 01:17.240 So I think it's better here. So mail and it's not here that I will learn you some 01:17.480 --> 01:22.760 mail is still at the core of a workplace because the mail is still the main vector to interact 01:22.760 --> 01:29.560 with the outside of an organization. So it's still very, very, very important, but the mail integration 01:29.560 --> 01:35.000 is still not satisfying. Of course, when you speak, you imagine about integration, regarding mail, 01:35.000 --> 01:42.280 you think about contacts, agenda, but you have also to consider files and those files today are 01:42.360 --> 01:50.600 in a drive. So you want to be able to pick and to deposit an attachment from or into your drive 01:50.600 --> 01:55.480 where the notifications, because when you are in a video, you don't expect your mail to send you 01:55.480 --> 02:00.520 pop-ups on your screen that will be shared with everybody that you are sharing the video. 02:01.720 --> 02:10.840 It's about AI, you expect your mail to use some platform AI tools, for instance, a kind of copilot 02:10.920 --> 02:17.800 to help you produce new content for your mail, but it's about navigation, you expect to have 02:17.800 --> 02:24.360 something more integrated, integrated through the whole workplace and not only through the mail. 02:25.880 --> 02:31.800 And this integration should be at the core of our preoccupation today, I think, because there's 02:31.880 --> 02:44.200 an historical opportunity to kick out Microsoft. First, this geopolitical situation that is so 02:44.200 --> 02:53.800 abuse today, I don't know how to limit the vehicle. So the geopolitical situation, but also 02:54.760 --> 03:01.400 maturity of free and open source services, which has been never been so important and relevant. 03:03.560 --> 03:11.240 The problem of those services is that we cannot completely compete against Microsoft because 03:13.400 --> 03:19.800 open solutions are still silos. You have good drive, you have good calendars, you have good solutions 03:19.800 --> 03:27.480 for video, but creating a workplace is not about adding an SSO over few good silos. 03:28.680 --> 03:36.440 And I think that the structure of the open source ecosystem is by design in charge of developing 03:36.440 --> 03:45.480 good verticals, good silos, and we lack transversality. So to kick Microsoft, SSO over a bunch of 03:45.480 --> 03:49.800 services and not enough, and we need to provide a smart platform experience. 03:51.400 --> 03:58.840 So what do we mean by this smart platform experience? Let's go into an example of what we did 03:58.840 --> 04:08.600 between twake and the suite. To imagine what we could do as a standard to make it easy, to orchestrate 04:08.680 --> 04:17.160 different services into a coherent workplace. So we'll try to make a demo without demo effect. 04:22.360 --> 04:28.920 So here we have a drive, a completely classical drive with the recent sharing, 04:28.920 --> 04:35.480 all you can navigate through your documents. And in the other end, you have another application, 04:35.560 --> 04:43.000 Docs, which is part of the suite, which is a notion killer, an application in which you can easily 04:43.000 --> 04:57.400 add some rich context, with some alert, this is another, but this application is not taking 04:57.400 --> 05:05.800 application as its own way to classify your documents or notes. It's a own way to share your notes. 05:06.920 --> 05:12.600 Whereas it's precisely the role of a drive, and here you see that we made this integration, 05:12.600 --> 05:21.080 so that in the drive we can create documents and notes, which is the same as the one that you have 05:21.160 --> 05:29.480 into Docs, but with the file integration, so for instance, in this note, I can modify the sharing 05:29.480 --> 05:42.520 rights, I can add a date, an expiration date, to today, and I can enter this note, but this 05:42.520 --> 05:49.640 note integrated into the platform. So it means that if, for instance, I change the title, 05:53.320 --> 06:00.680 this title is modified also, I will, it will be easier to be seen like that. You see that in the 06:00.680 --> 06:08.920 drive, the title is updated. You have a platform level description of the data of the metadata of each 06:09.320 --> 06:16.040 object, so that when there's an event into the Doc, this event is spread across the platform, 06:16.040 --> 06:24.120 so that it can be taken into account everywhere. So here it was about the title of the note, 06:24.120 --> 06:30.680 but if I click on share, here it's not the sharing system of Docs which is displayed, 06:30.680 --> 06:35.960 but it's the platform sharing system which is displayed, so that you can see that you have exactly 06:35.960 --> 06:46.360 the same parameters as in the drive. So the drive is no, the way to classify and share your notes, 06:46.360 --> 06:51.880 even if at the beginning, those two applications were designed completely separately. 06:54.520 --> 07:03.640 And we go even further by adding this contextual bar, so that you know that this document is part of 07:03.640 --> 07:10.120 this folder where you have other documents, that you can also navigate through very quickly, 07:10.120 --> 07:16.200 or even activate some features, such as Rina, Amy, movie, or doing whatever you want in 07:16.200 --> 07:22.440 interior classification system. So you no longer have two different applications, you have a platform 07:22.440 --> 07:27.240 which helps the services to provide an integrated service. 07:27.720 --> 07:35.720 Another important point is that you can see that the top bar here is at the platform level, 07:35.720 --> 07:41.560 so that you can navigate through the whole platform, having access to your user account 07:42.840 --> 07:49.480 parameters, and you can also access to other last few apps, because I was showing Docs, 07:49.480 --> 07:57.160 but also a video and grist, so that you have this ease of interaction across all the services. 07:59.080 --> 08:06.760 So this was a brief quick overview of what could be done, but you will see that the scope 08:06.760 --> 08:11.720 of what we need to orchestrate to provide a platform experience is quite broad, 08:12.680 --> 08:19.400 because of course, the idea is not to develop some specific code for each integration, 08:19.400 --> 08:26.040 but to have a standard that would normalize how different services could interact. 08:27.320 --> 08:31.560 So there's quite a lot of interesting subjects, functional and technical, 08:32.280 --> 08:36.920 authentication, user management, common settings, navigation, application packaging, 08:37.000 --> 08:42.200 platform level, data and metadata management, shareings, 08:42.200 --> 08:51.160 inter-applications, features, AI, vault for end-to-end, and mobile and desktop experience. 08:51.160 --> 08:57.560 So I go very quickly through each of them, DM is not to say that we have design and understood 08:57.560 --> 09:04.200 all that should be done to the standard, but it to show you that verse very deep and interesting 09:04.920 --> 09:10.280 subject that we could dive together, because in the end it's not just about technical, 09:10.280 --> 09:18.920 but it's about creating an ecosystem. So authentication, that's the most classical point, 09:18.920 --> 09:24.680 there's not much to say about authentication, whereas user management is more deep, 09:24.680 --> 09:31.400 you want to share some user profiles across your different services, for instance, some feature flags, 09:32.360 --> 09:41.000 some groups, some domains, some support parameters, the common settings, when you modify the 09:41.000 --> 09:49.240 language, some display, a theme, for instance, some quota or whatever, regarding the individual, 09:49.240 --> 09:55.960 you expect it service to be aware of these modifications. Navigation is very important, 09:55.960 --> 10:03.960 because it's the user experience clearance, which is underneath, so of course the top bar has 10:03.960 --> 10:09.960 shown you, but common home, from where you access all your services, the application grid, 10:10.840 --> 10:18.840 the access to the common settings or the contacts, the way to communicate to users, the global search, etc. 10:19.800 --> 10:28.600 Application packaging, DM is that an application that has not been even designed to be integrated 10:28.600 --> 10:38.440 with this approach, with this standard, could be deployed into the platform. So having a kind of 10:38.440 --> 10:46.440 package, and we made it by using some eye frames and some SSO tokens, so that an already existing 10:46.440 --> 10:54.840 app can be very easily integrated into the platform. We need to broadcast events when 10:55.640 --> 11:01.240 metadata, which is modified, so that all the apps can be updated, you know, during the demo, 11:01.240 --> 11:06.200 there was this moment when I modified the title and it was spread across the old platform in a 11:06.200 --> 11:14.520 real time. The sharing, so that you have one common sharing system across the platform, not one 11:14.600 --> 11:24.120 per service. Interrupts, so if you imagine in the mail, in the mail you may expect to pick a file from 11:24.120 --> 11:37.080 the drive or to join a document to your mail, but you can also want, I didn't, you could also want to have 11:37.240 --> 11:45.720 AI tools that are platform, which are developed by the platform, and that can be provided to 11:45.720 --> 11:52.920 all the editors, for instance, kind of copilot, but that you can leverage in any editor of your platform 11:52.920 --> 12:02.440 into your office of humans or mail editor, end-to-end encryption in a workplace will be more 12:02.520 --> 12:12.120 important. Managing secret for the user is very difficult, so the need for a workplace is to manage 12:12.120 --> 12:21.400 one single secret for the user, which may be possible for the platform to unlock a vault for 12:21.400 --> 12:32.280 all the client secrets of the different service, which need client secret, and regarding mobile 12:32.360 --> 12:36.840 experience, you can expect the platform to provide one single app for synchronization, 12:36.840 --> 12:42.680 authentication, for all the different mobile apps that can be connected into the workplace. 12:44.760 --> 12:57.160 Last but not least, the governance, it's about being able to find a denominator of solutions. 12:57.720 --> 13:05.880 That's why the expectation is to develop a consortium that can be at the beginning of an ecosystem 13:05.880 --> 13:14.760 of independent services, and in the end to be able to provide user experience and 13:14.760 --> 13:21.880 no further in the market, which is even higher of what Microsoft can provide. 13:22.840 --> 13:29.320 So thank you very much for your attention. Here is the contact. We would like to organize 13:29.880 --> 13:38.040 discussion, not only discussion, in the coming today or tomorrow, so please connect and add your name, 13:38.040 --> 13:47.000 so that we can set up a room and have this discussion in quite quick. We have already some 13:47.080 --> 13:52.920 very interesting people who want to participate, so I think it would be very interesting and 13:52.920 --> 13:54.840 looking forward to to see you. 14:05.800 --> 14:13.000 Yes, and the question is in fact most important. The idea is not to present 14:13.800 --> 14:23.080 the result, but more trajectories that must be fed with your questions and ideas. 14:24.120 --> 14:28.600 So do you have some questions or suggestions on how to proceed? 14:31.160 --> 14:32.200 What can I install? 14:36.200 --> 14:36.920 Can you repeat? 14:43.960 --> 14:47.960 What can I download and install? What's ready? 14:48.840 --> 14:55.720 What you can deploy an install? For no, we have just made this proof of concept with less heat, 14:56.600 --> 15:05.240 so it's a grist and docs and video, but we want to go further so that what we did is not just 15:05.240 --> 15:12.680 a specific code, but can be defined at a standard so that the modifications we made could be done by 15:12.680 --> 15:20.120 any other apps, a little bit like you know WOPI, if you are aware of this where of this standard, 15:21.800 --> 15:31.400 so that we could have an open project integrated into the high so that you could leverage 15:31.400 --> 15:36.840 further, to activate additional content. 16:01.400 --> 16:07.320 my year because we are discussing the same problem with the big statewide death of the 16:07.320 --> 16:12.360 drug need. So some of this platforms we take care of, but also his coalition. We have 16:12.360 --> 16:18.040 next long drive, or next change for polarization, or talking our things. And that the 16:18.040 --> 16:23.400 moment we solve it on the case by case basis, because time is an issue also a bit of 16:23.400 --> 16:28.920 activity is now all of this platform. So really looking forward to participate. 16:28.920 --> 16:33.480 No, we are not really question, but thank you for thinking about that in a pretty much 16:33.480 --> 16:36.920 holistic way. Okay, thank you very much. 16:36.920 --> 16:42.760 I'll be with that. Okay. And I'm repressed to be question. Are you really aiming for something 16:42.760 --> 16:48.200 that can be deployed? That can be downloaded and deployed by other organizations, 16:48.200 --> 16:54.680 or are you aiming to provide basically software as a service? No, no, no, fully open source. 16:54.680 --> 17:03.480 First standard. Sorry. Do we plan to provide only such solution, or some code that can be 17:03.480 --> 17:08.920 deployed by anyone? Yes, definitely it's the second option. We want first to define a standard 17:08.920 --> 17:15.080 so a specification and then an implementation, because that could be done by different people. 17:15.080 --> 17:19.960 And maybe to answer you, because you said something very interesting, it's about the time. 17:20.040 --> 17:27.720 And when time is limited, the short way is to do some specific code. 17:28.760 --> 17:34.920 But we have the chance that I offended Kozyklad, which we have been merged with 17:34.920 --> 17:43.480 Twake by Yena Gra, and Kozyklad, as it's Earth, was made to make it easy to deploy new services. 17:44.440 --> 17:50.440 In fact, from a different angle, we add to struggle with this problem. And that's why 17:50.440 --> 17:57.480 what I showed you is only five days of work. In fact, it was very short. It doesn't mean that 17:57.480 --> 18:03.880 everything is at a standard level. But it means that we add the concept to make it easy. 18:04.120 --> 18:13.640 Maybe the approach we have is the other way around that we have the same approach as you. 18:13.640 --> 18:19.720 We have a lifetime, we have little money, but we try to make something that works. And by doing 18:19.720 --> 18:25.720 something that works, we realize that maybe not everybody agrees on what we should do, and not 18:25.720 --> 18:31.240 every software is the same to install, because like for example, in dogs, you have sub-documents 18:32.120 --> 18:39.160 and a drive has sub-documents as well. I mean sub-folders. And so maybe you need to think of it. 18:39.160 --> 18:48.200 But when you insert sub-documents inside the drive, there's an issue that it just doesn't work. 18:48.200 --> 18:54.280 Like this, so you need to think how do you want to solve this? Do you want a single tree structure 18:54.280 --> 18:59.720 that is shared? And then you go further, or should we do a graph? Like the Z&Z bar approach? 19:01.240 --> 19:09.720 And so at the moment, we know that this works for Twake. And maybe like Open Project is here 19:09.720 --> 19:15.240 that is doing also integration. Open Desk, Integrated Docs as well in Open Project. 19:16.440 --> 19:21.400 And so we are sure of nothing, but we have done some proof of concepts of several things. 19:21.400 --> 19:27.560 And so we want to have this group of people who did things, and who are ready to now think of 19:28.520 --> 19:35.960 do we have a standard? And should we have several ways to integrate dogs in another software? 19:37.160 --> 19:44.520 Thanks for the extent of like, there are really difficult questions with rights, with trees, and trees, and stuff like this. 19:44.520 --> 19:50.760 So we need a group bigger than just us to think of this. And we also work with Open Desk. 19:50.760 --> 19:57.320 So we know that it's difficult to find the way to find the time and the brains to really 19:57.560 --> 20:01.640 think of something and make it a real standard. I don't know if it helps what I said, but 20:03.640 --> 20:09.800 even if time is limited, to complete, we need to organize a platform experience. 20:10.360 --> 20:19.800 Otherwise, we are isolated silos with an SSO, and we will not. So we need to devote to invest time in this need. 20:20.760 --> 20:25.400 From the experience of integrating Open Project to into Open Desk, 20:25.400 --> 20:29.880 I can only say that it's very important that we have these roles of the integrators. 20:29.880 --> 20:36.200 Like, these roles can do something that we as module and component providers can not do. 20:36.200 --> 20:41.800 Because we cannot really say, hey, other component providers, please help us integrate us with you. 20:41.800 --> 20:47.560 So easy, it's too costly. It's much easier if we stay in our own silent and prove our own 20:48.200 --> 20:53.000 product rather than talking to the other person. But you as the integrators, you can do a very 20:53.000 --> 20:58.280 important thing. It's obvious that you need to integrate. And you can bring the power and the 20:58.280 --> 21:03.960 leverage and the money and whatever the political pressure or the need to bring us together and 21:03.960 --> 21:09.800 to work together. There's something that is new here in this ecosystem that we have these new 21:09.880 --> 21:15.880 players, like last week, Open Desk, MindView will, they really set new, you 21:17.560 --> 21:22.600 will say, let's think, they mean set new interests and new motivations. 21:22.600 --> 21:28.840 And these are very important that these organizations become very stable and reliable. 21:31.400 --> 21:38.440 Completely agree. And just, I want to voice up that stuff. It's really hard. And like, 21:38.520 --> 21:42.840 we are two years in the making and I think we didn't crack it. We didn't crack it. So we also need 21:42.840 --> 21:50.040 you guys. And maybe we need an event just for this, like a sprint where we go somewhere for two days 21:50.040 --> 21:58.840 and just crack it on something as basic as menu bar. What is the Jason that we want to agree on? 21:58.840 --> 22:02.040 Maybe it's something really pragmatic. 22:08.440 --> 22:14.520 You read an article where she's teaching people where it's like, what is the short coming? So 22:14.520 --> 22:18.360 after the success would move, what is the short coming? And this integration was actually 22:18.360 --> 22:24.120 singled out as one predominant factor. And my question actually would be, if you look at what 22:24.120 --> 22:29.160 is, you know, you said, like, okay, we need to start off in a way to, you know, not just be stuck on 22:29.160 --> 22:33.320 Microsoft and financial energy. So first of all, what would be the benchmark for you? I mean, 22:33.320 --> 22:38.040 there's a thing that came to my mind when I, when I listen to that, first of all, things like 22:38.040 --> 22:43.240 these advanced systems, you might have in Outlook or a little bit of some slack and stuff like that. 22:43.240 --> 22:48.600 So we said, also what you see is copier and also how is it related to stuff like MCP or, like, 22:48.600 --> 22:54.040 you know, an eye-based interfaces, which help you integrate applications. So I was thinking 22:54.040 --> 23:00.040 like really rich, you eye-based integration of these things. 23:00.920 --> 23:13.000 Can you, yeah, I didn't, no, I can I refresh. You ask if the for us the next step is mainly 23:13.000 --> 23:23.000 on the UX integration or also on the data side with AI and obviously both. And I will say that 23:23.000 --> 23:31.000 the target of the workplace until now was just to make it easy to, to ease the access to the services. 23:32.040 --> 23:39.400 Whereas with AI, the aim is to leverage the knowledge, the knowledge of all the documents of the 23:39.400 --> 23:47.640 workplace, to augment the productivity. So it's UX is the previous train. 23:48.280 --> 24:00.920 It's easier, it's quite urban. Yeah, and maybe the back end, talking to each other is the hard part 24:00.920 --> 24:08.680 because you have trust involved. And like from now to June with open days, you know, so 24:08.680 --> 24:17.240 our Dutch colleagues, we will be working on a global find. So these are stuff that it's a micro-service 24:18.040 --> 24:25.880 that we need. And when we take each stand-alone application, that doesn't give you a global 24:25.880 --> 24:36.360 find for your suite. So it's also, we also need some micro-services that don't make sense alone, 24:37.640 --> 24:43.880 but that we need to define. So this will be, there will be some back end standards to people 24:43.960 --> 24:52.040 to index your content. And there will be some front end to have to be able to serve all these search 24:53.240 --> 25:00.920 experience on the apps. So that's everything is integrated, but we need to be very pragmatic 25:01.480 --> 25:07.800 and use cases. Like a user wants is in an email and he wants to get a file from a drive. 25:08.680 --> 25:16.920 What's the standard? Someone is in video in the video conferencing and they made a recording 25:16.920 --> 25:22.440 and the video conferencing should push the recording to your drive. But before that, you need to pick 25:22.440 --> 25:29.160 a folder in the drive where you want your video to be recorded and the video conferencing software 25:29.160 --> 25:35.880 should not be able to read all your files. It should be given securely access to only this folder. 25:36.760 --> 25:45.320 It's hard and we need to see it as user use cases. Like don't try to because it's infinite. 25:46.040 --> 25:52.440 And then we can compete with any compete. We can have alternatives to this big player.