WEBVTT 00:00.000 --> 00:12.600 The next talk which will be presented by Yuland is about open project, the same software 00:12.600 --> 00:18.520 as the one that is on the t-shirts here, and it's going to title the open project a year 00:18.520 --> 00:19.520 full of updates. 00:19.520 --> 00:20.520 Thank you. 00:20.520 --> 00:21.520 Yeah. 00:21.520 --> 00:23.520 Hello. 00:24.400 --> 00:28.600 I'm B-Land, I'm co-founder and CEO of open project. 00:28.600 --> 00:31.320 I'm very glad to be here again. 00:31.320 --> 00:34.560 It's, I don't know, my fourth time here. 00:34.560 --> 00:37.400 And for those that don't know, 00:37.400 --> 00:41.920 open project quickly, open project is not showing up here. 00:45.440 --> 00:46.480 Oh, shit. 00:49.480 --> 00:51.040 That's why you need to move this. 00:51.040 --> 00:52.040 Yes. 00:53.000 --> 00:53.800 OK. 00:57.800 --> 00:59.040 Right. 00:59.040 --> 01:01.680 I'm speaking in a name of this little bit. 01:01.680 --> 01:02.880 So, yeah. 01:02.880 --> 01:06.200 Really, if I don't have the name, I'll write now. 01:06.200 --> 01:07.440 Did it notice, D-O? 01:07.440 --> 01:08.200 Yeah. 01:08.200 --> 01:08.800 Yeah. 01:08.800 --> 01:09.800 Yeah. 01:09.800 --> 01:10.800 Yeah. 01:10.800 --> 01:11.800 Yeah. 01:11.800 --> 01:12.800 Yeah. 01:12.800 --> 01:13.800 Yeah. 01:13.800 --> 01:18.800 So, L-L-L-L-L-L. 01:18.800 --> 01:28.800 So, my internet name, I have a question. 01:34.800 --> 01:36.800 OK. 01:36.800 --> 01:37.800 L-L-L-L-L. 01:37.800 --> 01:38.800 OK. 01:38.800 --> 01:39.800 OK. 01:39.800 --> 01:40.800 OK. 01:40.800 --> 01:41.800 Yeah. 01:41.800 --> 01:43.800 OK. 01:43.800 --> 01:44.800 Is that better? 01:44.800 --> 01:45.800 Yeah. 01:45.800 --> 01:46.800 OK. 01:46.800 --> 01:47.800 Thank you very much. 01:48.800 --> 01:50.600 So, for those that don't know, open project yet, 01:50.600 --> 01:54.400 open project is a collaborative project management system, 01:54.400 --> 01:59.040 and which allows, you can think of, 01:59.040 --> 02:00.600 of open project there's something like, 02:00.600 --> 02:05.000 Jira and Trello in one thing, but it's open source. 02:05.000 --> 02:08.400 And it allows to basically do the work from bottom up, 02:08.400 --> 02:11.160 like teams working agile in, in, in, in, 02:11.160 --> 02:16.360 canvas ground manners, or further up in an, in high altitude, 02:16.360 --> 02:19.960 top down, like, you plan ahead of project in gun charts, 02:19.960 --> 02:23.480 and so on, or even further, going the portfolio management, 02:23.480 --> 02:25.160 like, where do you invest your budgets? 02:29.960 --> 02:31.120 It's my fourth time here. 02:31.120 --> 02:34.480 So, last year, what has happened since last year, 02:34.480 --> 02:37.560 is the topic of this talk today. 02:37.560 --> 02:40.280 I want to show you a couple of highlight features 02:40.280 --> 02:43.040 that made it into open project, and also 02:43.040 --> 02:45.480 want to give you a little bit of outlook, what's 02:45.480 --> 02:48.680 about to come, and where we are working on. 02:48.680 --> 02:49.640 What we're working on. 02:53.760 --> 02:57.600 This is just, right, start right with the first feature 02:57.600 --> 03:02.600 that we introduced is automatic work package subjects. 03:02.600 --> 03:04.440 There's something that, you know, like, 03:04.440 --> 03:06.760 2022-25 was basically the year for open project, 03:06.760 --> 03:10.320 where we really went full on to the public sector, 03:10.320 --> 03:13.560 and public sectors, usually big organizations, 03:13.560 --> 03:15.640 they need to structure the work. 03:15.640 --> 03:18.360 They use open project to structure the work and the teams, 03:18.360 --> 03:22.240 and they have recurring tasks, tasks that are similar, 03:22.240 --> 03:23.720 and to keep all and structure, 03:23.720 --> 03:26.080 they want them to be named the same way. 03:26.080 --> 03:29.720 So with automatic workpages titles, 03:29.720 --> 03:33.400 you can set patterns for workpages titles, 03:33.400 --> 03:35.400 like, say, here a sign is started, 03:35.400 --> 03:39.840 finish date offense on, and they get automatically used 03:39.840 --> 03:44.120 for the next workpages that you create of the type. 03:44.120 --> 03:46.800 Very convenient. 03:46.800 --> 03:49.640 Yeah, you don't know that you need it until you have it. 03:52.280 --> 03:54.720 To our commitment to improve accessibility, 03:54.720 --> 03:59.040 we continue to on our dark mode and light mode, 03:59.040 --> 04:01.040 and high contrast, and so on. 04:01.040 --> 04:04.480 And I want to highlight this little feature here 04:04.480 --> 04:08.440 that now you can even have high contrast mode in dark mode, 04:08.440 --> 04:15.440 which, finally, is not only a feature that people with disabilities, 04:19.200 --> 04:23.440 benefit from, but also, not the programmers like me, 04:23.440 --> 04:27.400 we like to have more contrast once in a while. 04:27.400 --> 04:29.040 OK. 04:29.040 --> 04:31.520 I talked about organizing work, 04:31.520 --> 04:34.320 usually that is done in issues and workpages, 04:34.320 --> 04:36.800 and organizing them in projects. 04:36.880 --> 04:39.600 But actually, that's just one part of open projects. 04:39.600 --> 04:42.480 Another thing that is used in the job that a lot of open projects 04:42.480 --> 04:44.080 are meeting agendas. 04:44.080 --> 04:47.600 Meeting agendas is basically like you want to come to a meeting 04:47.600 --> 04:49.280 and be prepared. 04:49.280 --> 04:51.480 And often, I don't know how it's for you, 04:51.480 --> 04:54.800 but organizations, I think, 90% of my meetings, 04:54.800 --> 04:56.960 they're recurring meetings, they're like the stand up, 04:56.960 --> 05:00.040 they're the weekly, they're your fix, you know? 05:00.040 --> 05:04.480 And we kind of cross the work right on the issues. 05:04.480 --> 05:06.440 And I'm like, oh, here's a topic that I should bring 05:06.440 --> 05:09.440 to the next meeting, and I don't want to interrupt right now. 05:09.440 --> 05:10.840 This is why meeting agendas are great. 05:10.840 --> 05:14.520 You just bring the workpackage onto an agenda. 05:14.520 --> 05:16.920 I already presented this last year. 05:16.920 --> 05:21.440 Well, what's now, what's now new is, now you can simply 05:21.440 --> 05:25.480 grab a URL from what can project and subscribe 05:25.480 --> 05:28.360 to all your meetings in your favorite kind of application 05:28.360 --> 05:29.880 by ICO, OK? 05:29.880 --> 05:33.480 So you don't miss any meeting anymore. 05:33.480 --> 05:35.800 We have more features in the meetings module 05:35.800 --> 05:39.200 like a presentation mode that looks a bit like this presentation 05:39.200 --> 05:39.920 here. 05:39.920 --> 05:42.640 So you jump from one agenda item to the next ones. 05:42.640 --> 05:45.840 And there are more features to come over the next, 05:45.840 --> 05:47.440 in the next release. 05:47.440 --> 05:49.000 So just stay tuned, take it out. 05:52.560 --> 05:55.600 Open products also used for IT service management. 05:55.600 --> 05:58.800 And we continuously improve and extend our features 05:58.800 --> 06:00.040 at here. 06:00.040 --> 06:04.840 And one very important thing that we added last year 06:04.840 --> 06:08.640 is the ability to have private or internal comments. 06:08.640 --> 06:10.200 So let's say you have an organization. 06:10.200 --> 06:10.880 You have a team. 06:10.880 --> 06:14.400 You're used to just have add comments to your workpackage, 06:14.400 --> 06:16.160 your issues, your task. 06:16.160 --> 06:17.840 And there you have this thing where you need to ask, 06:17.840 --> 06:19.840 add, do you really do this? 06:19.840 --> 06:20.960 Do you really want to do that? 06:20.960 --> 06:22.920 Or do you have more information on this? 06:22.920 --> 06:24.640 I don't know what to answer. 06:24.640 --> 06:25.880 There's an internal comment, no? 06:25.880 --> 06:28.960 Like it's meant for your colleagues, but not for your clients. 06:28.960 --> 06:33.640 So with just one click, you have the comments, 06:33.640 --> 06:36.560 there's normal, and with just one click here, 06:36.560 --> 06:40.760 it's just visible for you and your colleagues. 06:40.760 --> 06:43.280 Another thing, once you have it, you can't 06:43.280 --> 06:46.280 without anymore. 06:46.280 --> 06:49.000 There are more ITS and features to come 2026, 06:49.000 --> 06:53.560 especially I come to this later about the Lazy and Data 06:53.560 --> 06:56.400 Center exit. 06:56.400 --> 07:00.440 OK, that is now a completely different level. 07:00.440 --> 07:03.600 So up until now, I was talking about the data 07:03.600 --> 07:07.360 daily work, task, and who does what when. 07:07.360 --> 07:09.840 Portfolio management is a layer above. 07:09.840 --> 07:13.440 Portfolio management is when you, for example, 07:13.440 --> 07:16.080 as a public authority, you have a certain budget. 07:16.080 --> 07:19.800 The budget should be used for a strategic goal. 07:19.800 --> 07:21.960 How do you best invest? 07:21.960 --> 07:26.520 So you best invest in order to, you create a set of projects 07:26.520 --> 07:28.800 and that together, hopefully, with these projects, 07:28.800 --> 07:32.880 you will reach a certain strategic goal. 07:32.880 --> 07:36.840 And yeah, 25 or 35 was the year of the public sector. 07:36.840 --> 07:40.080 And we had a portfolio management to open project. 07:40.080 --> 07:42.680 With that comes that you'd not only have projects, 07:42.680 --> 07:46.520 you can now also have portfolios as first class citizen 07:46.520 --> 07:47.840 and programs. 07:47.840 --> 07:51.320 So programs, rep, a set of projects, 07:51.320 --> 07:55.920 and a set of programs can be a portfolio. 07:55.920 --> 07:57.080 Pretty simple, no? 07:57.080 --> 07:59.240 OK, cool. 07:59.240 --> 08:05.960 The good thing about Portfolio is that you can then 08:05.960 --> 08:07.960 check the health of your whole portfolio, 08:07.960 --> 08:10.160 so how is your investment going? 08:10.160 --> 08:16.160 So how good is a achieving or moving towards your strategic goal? 08:16.160 --> 08:18.320 And so every project can have a status, 08:18.320 --> 08:22.320 but Portfolio can have a status in and so on? 08:22.320 --> 08:23.320 Yeah. 08:23.320 --> 08:25.840 But if you manage a portfolio, you also need 08:25.840 --> 08:29.240 to have data on those projects. 08:29.240 --> 08:33.520 Usually, there's something that you do in spreadsheets. 08:33.520 --> 08:34.600 It's another system. 08:34.600 --> 08:35.680 It's not in the system. 08:35.680 --> 08:38.560 So we added a lot of capabilities to add that data 08:38.560 --> 08:41.800 to projects and portfolios inside of our projects. 08:41.800 --> 08:46.160 So that you don't need spreadsheets so much anymore. 08:46.160 --> 08:49.280 These we call project attributes, portfolio attributes, 08:49.280 --> 08:50.520 and so on. 08:50.520 --> 08:54.160 And with the next release, not yet, but we 08:54.160 --> 08:58.320 will have a wizard with which you can 08:58.320 --> 09:01.320 everyone that creates a project ask a certain set of questions 09:01.320 --> 09:03.400 so that they fill in this data so that you 09:03.400 --> 09:05.320 have better comparability between projects. 09:10.360 --> 09:12.320 And to better compare them, even further, 09:12.320 --> 09:14.040 you can say, OK, some of these values 09:14.040 --> 09:18.600 that you attach to project, you give them a number. 09:18.600 --> 09:21.080 And then you can calculate a score. 09:21.080 --> 09:26.520 So you could compare, I don't know, five begins the seven, of course. 09:26.520 --> 09:28.280 But if you have multiple values in you 09:28.280 --> 09:32.920 want to calculate the score out of multiple attributes, 09:32.920 --> 09:35.280 this is what we can do now. 09:35.280 --> 09:40.640 So we can have fields that I've calculated values. 09:40.640 --> 09:43.480 They calculate instantly by setting attributes. 09:43.480 --> 09:45.480 So this is the formula. 09:45.480 --> 09:46.280 You're on the right-hand side. 09:46.280 --> 09:47.920 You see the attributes. 09:47.920 --> 09:50.840 And by setting a certain field, 09:50.840 --> 09:54.680 we will calculate a new score. 09:54.680 --> 09:57.320 And then we can compare one project by another, 09:57.320 --> 09:58.840 if I have this scores. 09:58.840 --> 10:01.400 Scores help to just get a little bit more structure and bit 10:01.400 --> 10:02.240 more comparability. 10:06.440 --> 10:11.600 That was a very huge topic, or a huge feature. 10:11.600 --> 10:13.040 This one is a little one. 10:13.040 --> 10:16.280 This is the one that you come across like 50 times a day. 10:16.280 --> 10:18.920 It's actually the search. 10:18.920 --> 10:20.640 We improved the search a little bit. 10:20.640 --> 10:24.920 So that you can also search for work package type names 10:24.920 --> 10:29.360 and best status in order to better find the work page 10:29.360 --> 10:31.920 that you're always looking for instead of searching 10:31.920 --> 10:32.720 for the gray-level word. 10:36.640 --> 10:42.240 That's my personal passion project for 2025. 10:42.240 --> 10:45.680 We added real-time collaboration to open project. 10:45.680 --> 10:47.880 First on documents, because documents 10:47.880 --> 10:50.280 was the least used module-nopen project. 10:50.280 --> 10:52.600 And it needed to get a little bit of update. 10:52.600 --> 10:54.320 But actually what I wanted to do is I wanted 10:54.320 --> 10:56.680 to get into real-time collaboration. 10:56.680 --> 11:00.120 And documents was the safest place, because nobody really 11:00.120 --> 11:02.840 used it. 11:02.840 --> 11:05.880 Because if you really want to share files, 11:05.880 --> 11:06.920 take next cloud. 11:06.920 --> 11:15.120 So I wanted to get our team up to speed with the technology. 11:15.120 --> 11:17.040 And this is what we came up with. 11:17.040 --> 11:20.240 So you can have documents where people just come together 11:21.200 --> 11:25.680 right together on text, share their thoughts, improve each other 11:25.680 --> 11:26.840 at the same time. 11:26.840 --> 11:27.960 It's actually pretty fun. 11:27.960 --> 11:28.760 It's chaotic. 11:28.760 --> 11:29.640 It's democratic. 11:29.640 --> 11:32.480 It's really cool. 11:32.480 --> 11:36.880 And yeah, so what is actually very interesting about that is, 11:36.880 --> 11:41.000 OK, kid, now we have a place we can quickly write on stuff, 11:41.000 --> 11:43.160 unstructured, structured, later. 11:43.160 --> 11:46.920 You can break it down into work package and so on. 11:46.920 --> 11:48.960 But for me, it's not so much about documents, 11:48.960 --> 11:51.320 because if you say, OK, we can talk about knowledge, 11:51.320 --> 11:54.520 management, and stuff, take XVG. 11:54.520 --> 11:57.960 That's what for me, as a CTO, is really interesting here, 11:57.960 --> 12:00.600 is the editor. 12:00.600 --> 12:02.920 That's block node that we use here. 12:02.920 --> 12:05.000 Use if I are here. 12:05.000 --> 12:07.360 Hey, block node here. 12:07.360 --> 12:08.200 Thanks for the software. 12:15.200 --> 12:17.000 I met you this year ago. 12:17.000 --> 12:20.560 And now we have that software here. 12:20.560 --> 12:23.840 It costs them to hack a thin slater. 12:23.840 --> 12:25.960 That's really, really cool. 12:25.960 --> 12:27.400 What's so nice about it? 12:27.400 --> 12:30.360 It has, well, it's good to the next slide. 12:30.360 --> 12:32.600 Block node rock. 12:32.600 --> 12:39.080 They say, use if says, third to nation, notion-style editor 12:39.080 --> 12:39.640 in minutes. 12:39.640 --> 12:43.040 And I think that's a good sum up of it. 12:43.040 --> 12:45.000 Like you want to have the notion experience 12:45.000 --> 12:47.520 of the modern application. 12:47.520 --> 12:50.040 And I think it really gives that spirit open product. 12:50.040 --> 12:52.680 It's really, really cool. 12:52.680 --> 12:57.560 And what's impressive is also used in big application 12:57.560 --> 13:00.040 bundles, like Open Desk, last week, 13:00.040 --> 13:03.680 mind-be-roll, that newest of those. 13:03.680 --> 13:06.040 And yeah, that makes it interesting, 13:06.040 --> 13:09.440 because we also, we bring open project 13:09.440 --> 13:13.520 as a component to those bundles, not yet last week. 13:13.520 --> 13:14.800 Let's see. 13:14.800 --> 13:16.600 But Open Desk and mind-be-roll, for example, 13:16.600 --> 13:18.440 or next cloud hub. 13:18.440 --> 13:22.560 And when we bring open project as a component, 13:22.560 --> 13:24.160 we see it as a component to a bundle, 13:24.160 --> 13:26.600 we also think integrations. 13:26.600 --> 13:29.320 And if those applications or other applications 13:29.320 --> 13:34.320 in that bundle, if they use block node, 13:34.320 --> 13:37.560 it becomes so much simpler to integrate open project, 13:37.560 --> 13:40.120 because let's say extending the slash command. 13:40.120 --> 13:42.120 Some feature that you would need to implement 13:42.120 --> 13:44.880 for every application, implemented once. 13:44.880 --> 13:47.360 Provided as an extension, publish it, 13:47.360 --> 13:48.720 and everyone who wants to integrate 13:48.720 --> 13:54.200 with Open Project can just grab it if they use block node. 13:54.200 --> 13:58.880 Actually, it has a GPL license, so very nice. 13:58.880 --> 14:00.080 Yes. 14:00.080 --> 14:07.760 Yeah, to be fair, that's just the beginning. 14:07.760 --> 14:09.680 I actually want to have real-time collaboration 14:09.680 --> 14:11.720 on work packages, because that is where 14:11.720 --> 14:14.160 all the work is managed of Open Project, 14:14.160 --> 14:18.480 where the real matter is that we are people 14:18.480 --> 14:21.440 work with. 14:21.440 --> 14:23.880 For that, we need to migrate more stuff 14:23.880 --> 14:26.400 from the old editors, you get it at a five. 14:26.400 --> 14:27.520 Or more crores, and so on. 14:27.520 --> 14:28.680 It takes a bit more time. 14:28.680 --> 14:29.840 It needs to be more stable. 14:29.840 --> 14:33.480 We need to get the experience in that we are 14:33.480 --> 14:35.920 let we're taking now with documents. 14:35.920 --> 14:44.200 Talking about Open Project as a component. 14:44.200 --> 14:49.840 That is not my passion project, that's my purpose project. 14:49.840 --> 14:53.080 I see that we as a Open Source ecosystem, 14:53.080 --> 14:55.160 we need to provide our applications in a way 14:55.160 --> 14:58.000 that they become components in a bigger setting. 14:58.000 --> 15:00.360 So the bigger setting here, our application 15:00.360 --> 15:02.920 bundles, like next Cloud Hub, open Desk, 15:02.920 --> 15:05.760 mind-be-roll, you name it, last week. 15:05.760 --> 15:09.400 And for this, we application providers, 15:09.400 --> 15:12.840 we need to be pluggable. 15:12.840 --> 15:15.480 What does it mean to be pluggable? 15:15.480 --> 15:18.920 Pluggable means that it's easy to integrate it 15:18.920 --> 15:23.880 into the operations, so you to roll out, to deploy it. 15:23.880 --> 15:27.440 So on the Kubernetes cluster, with home charts, 15:27.440 --> 15:31.640 it's standardized easy ways just to spin it up, 15:31.640 --> 15:35.360 to do the backups, everything is very smooth. 15:35.360 --> 15:37.320 People don't need to learn about Open Project, 15:37.320 --> 15:41.040 although they're multiple services and databases 15:41.040 --> 15:42.760 and caching and whatever. 15:42.760 --> 15:43.920 It's all there. 15:43.920 --> 15:45.800 Now with HocusPocus, for Block node also, 15:45.800 --> 15:48.560 another service is in, but people don't need to know 15:48.560 --> 15:49.920 that there's complexity. 15:49.920 --> 15:53.560 Just take the home chart, spin it up, and off you go. 15:53.560 --> 15:57.120 So I think every application should provide this. 15:57.120 --> 15:59.880 If not, work on it, please. 15:59.880 --> 16:02.280 The other thing is, OK, being a good citizen 16:02.280 --> 16:08.720 in terms of login logout, or IDC, as Snowwood standard, 16:08.720 --> 16:11.640 you most applications have that, at least to some extent. 16:11.640 --> 16:14.400 That's pretty good. 16:14.400 --> 16:16.040 Sing a sign on, yes, of course. 16:16.040 --> 16:17.960 Sing the logout. 16:17.960 --> 16:20.240 I assure you, have it. 16:20.240 --> 16:23.040 The next very important thing is skin. 16:23.040 --> 16:25.360 Skin is for user provisioning. 16:25.360 --> 16:27.640 So that is, OK, if you have a central place 16:27.640 --> 16:32.920 where you want to get people into application bundle 16:32.920 --> 16:35.400 and then you're like creating accounts, 16:35.400 --> 16:36.600 and then you want to make sure that they're 16:36.600 --> 16:40.240 an open project and the next cloud and an x-viki 16:40.240 --> 16:45.400 at the same time, or you want to lock those users 16:45.400 --> 16:48.240 because they leave your organization. 16:48.240 --> 16:52.040 Skin is the way to go, because it's almost immediate. 16:52.040 --> 16:54.840 It is fast, it is standardized. 16:54.840 --> 16:58.240 Don't go the other way anymore, just do it. 16:58.240 --> 17:00.880 It's one time investment, but then you 17:00.880 --> 17:05.120 have an industry standard, and you're easy to plug in, 17:05.120 --> 17:08.000 and you're good citizen in the ecosystem. 17:08.000 --> 17:11.600 The other ones, this, like jet token, structured, 17:11.600 --> 17:13.960 authentication authorization, and token exchange 17:13.960 --> 17:17.520 would make it easy to communicate between applications. 17:17.520 --> 17:18.960 I know we application providers 17:18.960 --> 17:21.360 we often think just in our own realm, 17:21.360 --> 17:24.440 but we need to think integrated. 17:24.440 --> 17:27.200 So our applications need to be able to talk 17:27.200 --> 17:29.880 with other application back-ends in the name 17:29.880 --> 17:32.880 of the current user that the user is over there. 17:32.880 --> 17:34.920 So let's talk in your sense. 17:34.920 --> 17:35.920 Question? 17:35.920 --> 17:38.440 Talking about skills, as the server 17:38.440 --> 17:41.080 played a bit different from sending it. 17:41.080 --> 17:43.440 So it was a big applause for the guy 17:43.440 --> 17:45.680 in the names of sending it. 17:45.680 --> 17:48.120 Yeah, thank you. 17:48.120 --> 17:52.680 So my brother was just mentioning that this 17:52.680 --> 17:55.400 given integration was sponsored by Sendis. 17:55.400 --> 17:56.400 Cool. 17:59.400 --> 18:01.120 OK, you can set it up. 18:01.120 --> 18:02.120 OK. 18:02.120 --> 18:04.560 Now this is actually the big topic for 2026. 18:07.880 --> 18:11.240 As you might have heard about, Adelaide is saying, 18:11.240 --> 18:14.440 we kill the data center, which is basically running your 18:14.440 --> 18:18.080 Adelaide instance on your own machine. 18:18.080 --> 18:22.280 They say you can only go to the cloud, to their cloud. 18:23.240 --> 18:26.600 The end of data center is March 2029. 18:26.600 --> 18:30.200 And yeah, I don't know what they're thinking, 18:30.200 --> 18:33.000 but many organizations don't have the option. 18:33.000 --> 18:36.400 If you're, let's take an extreme example. 18:36.400 --> 18:39.880 If you're a secret service, you don't put your data 18:39.880 --> 18:41.800 into the cloud of someone else, right? 18:41.800 --> 18:43.160 You don't do it. 18:43.160 --> 18:46.080 So that's a worldwide problem. 18:46.080 --> 18:50.360 And organizations all over the world approach us. 18:50.360 --> 18:53.440 OK, can you provide an alternative? 18:53.440 --> 18:56.280 Can you be a replacement of Jira? 18:56.280 --> 19:00.080 And for this, we partner with ButxViki, 19:00.080 --> 19:02.880 because they do the alternative for confluence, 19:02.880 --> 19:05.480 and we do the alternative to Jira, and we integrate. 19:13.360 --> 19:16.000 Yeah, basically that means that we can link 19:16.000 --> 19:20.600 X-Viki pages with work packages back and forth. 19:20.600 --> 19:24.120 So you can navigate just as you use to with Jira issues 19:24.120 --> 19:26.400 and confluence pages. 19:26.400 --> 19:30.480 You can extend the, yeah, you can use a lot of macros 19:30.480 --> 19:33.000 on the X-Viki side that you also familiar 19:33.000 --> 19:36.840 from confluence, like work package tables, 19:36.840 --> 19:40.720 breakdown charts, and graphs. 19:40.720 --> 19:44.000 Yeah, this will be released by the end of June, 19:44.000 --> 19:46.200 and stay tuned on that one. 19:52.160 --> 19:56.000 Yeah, so you have a Jira instance, how do you continue? 19:56.000 --> 19:58.480 How do you get out of that situation? 19:58.480 --> 20:02.080 Then you probably want to carry over all the jewels 20:02.080 --> 20:04.080 that you have created over the last couple of years, 20:04.080 --> 20:07.080 which are basically Jira issues in the history. 20:07.080 --> 20:11.960 So by the end of Q1 this year, we're going to release 20:11.960 --> 20:13.320 a migration tool. 20:13.320 --> 20:16.360 You just put it in the application key of Jira, 20:16.360 --> 20:18.800 and it will pull the data in, and you will choose, 20:18.800 --> 20:20.920 okay, I want to migrate this in this project, 20:20.920 --> 20:23.600 and you have the issues, the projects, the attachments, 20:23.600 --> 20:24.840 the comments. 20:24.840 --> 20:27.920 This will be all done by the end of Q1, 20:29.280 --> 20:31.600 and then we will extend it over the year 20:31.600 --> 20:36.600 to have relationships covered and more, 20:37.840 --> 20:41.080 more structures taking over from Jira to open product. 20:41.960 --> 20:47.880 We also are working on, let's say, 20:47.880 --> 20:50.640 how to say this best. 20:50.640 --> 20:52.720 Jira, when people work with Jira, 20:52.720 --> 20:55.120 they are so much into this how to erase this, 20:55.120 --> 20:57.920 how I know it, we want to continue like this. 20:57.920 --> 21:02.280 And, yeah, Jira has a certain style of HR product management, 21:02.280 --> 21:06.280 how to plan sprints, and how to manage the backlog. 21:06.280 --> 21:09.640 So we will take the good parts of it, 21:09.640 --> 21:14.640 and you have to try to come up even with a better experience. 21:14.840 --> 21:16.720 So we're working on this right now, 21:16.720 --> 21:20.680 and expect a couple of releases with iterations 21:20.680 --> 21:22.160 of improvements. 21:24.200 --> 21:25.800 And then the further Jira fundamental 21:25.800 --> 21:27.560 that will come throughout the year, 21:27.560 --> 21:31.240 it's starting with speaking work package identifiers, 21:31.240 --> 21:34.400 like where you first have the project identifier, 21:34.400 --> 21:36.080 and then a sequence number. 21:36.080 --> 21:37.520 So that's already coming in Q1. 21:37.520 --> 21:39.320 So that's also very soon. 21:39.320 --> 21:43.240 We will work on, 21:45.680 --> 21:47.960 we will work on automations. 21:47.960 --> 21:51.800 So we get the feedback that configuring workflows 21:51.800 --> 21:53.840 is easier and Jira than an open project. 21:53.840 --> 21:54.960 So we will work on this. 21:54.960 --> 21:59.280 We will also work on our first steps of automations, 21:59.280 --> 22:03.800 like, okay, if this and that scenarios, 22:03.800 --> 22:07.560 and yeah, we will also make it easier for project 22:07.560 --> 22:09.960 to come up with their own structures 22:09.960 --> 22:13.200 and their own set-ups, configurations independent 22:13.200 --> 22:15.240 of the big central that is somewhat of people 22:15.240 --> 22:16.840 that you don't know and you don't know 22:16.840 --> 22:19.200 how to ask them to approach them, 22:19.200 --> 22:22.480 to give them more autonomy in the project itself. 22:24.240 --> 22:26.120 So please stay tuned. 22:26.120 --> 22:27.720 This will be an exciting year, 22:29.280 --> 22:33.400 and just remember as an open source ecosystem 22:33.400 --> 22:35.000 integrated real stronger. 22:35.000 --> 22:35.840 Thank you. 22:37.560 --> 22:38.560 Thank you. 22:38.560 --> 22:39.560 Thank you. 22:39.560 --> 22:41.560 Thank you. 22:41.560 --> 22:42.560 Thank you.