WEBVTT 00:00.000 --> 00:09.000 The next vote will be about the Tegat, the Tegat, the Tegat, the Tegat, the Tegat, the 00:09.000 --> 00:13.000 small story of sustainability of the Dors and its main military infantry. 00:13.000 --> 00:15.000 Hello everyone. 00:15.000 --> 00:22.000 I'm going to tell you stories that happened not so long ago in the country, not very far away, actually. 00:22.000 --> 00:29.000 Once upon a time in 2014, it was born Tegat from the Bole Bors of a Spanish company named Khaled 00:29.000 --> 00:31.000 Khaledos. 00:31.000 --> 00:38.000 Tegat soon became a well-bellowed project management tool with a World War user base of over 20 00:38.000 --> 00:40.000 million. 00:40.000 --> 00:48.000 In 2021, the Tegat team took on a new project called Base, the Tegat Next. 00:48.000 --> 00:55.000 Tegat Next was announced as a fully revamped Tegat, keeping key concepts for its predecessor, 00:55.000 --> 00:58.000 but designing a better user experience around. 00:58.000 --> 01:05.000 The focus was on being global, inclusive, and accessible. 01:05.000 --> 01:12.000 But the Khaledos company is a Busybee, and they were also already working on another 01:12.000 --> 01:18.000 product called Penpots, which is a design tool to bring together developers and designers. 01:18.000 --> 01:25.000 By that time, it was just starting to achieve a great success, and it's awesome. 01:25.000 --> 01:27.000 You should write them so. 01:27.000 --> 01:32.000 There eventually reached the decisions that that couldn't keep working on both 01:32.000 --> 01:34.000 product at the same time. 01:34.000 --> 01:41.000 Penpots was chosen as it was believed to feel a more premium gap in the ecosystem. 01:41.000 --> 01:45.000 What did it mean then for a Tegat Next was vision? 01:45.000 --> 01:51.000 I think you knew the answer to that already, or we don't be here today. 01:51.000 --> 01:57.000 At Beri, we are a small French Cooperative, a TV investing open source. 01:57.000 --> 02:03.000 And in 2024, we were working on Tegat internally, training our ends on our own 02:03.000 --> 02:05.000 revamped of the front end. 02:05.000 --> 02:11.000 We decided to reach out to Khaledos, and the informed us that Tegat Next 02:11.000 --> 02:15.000 was actively searching for a new graduate. 02:15.000 --> 02:20.000 We decided to seize this opportunity, and the magic of open source pretty much took 02:20.000 --> 02:22.000 care of the rest. 02:22.000 --> 02:32.000 And that's what Tegat Next was born. 02:32.000 --> 02:34.000 I wasn't sure if that would work. 02:34.000 --> 02:39.000 The philosophy behind Tegat Next is the same as it's Alias Tegat Next, 02:39.000 --> 02:45.000 to build a great tool promoting healthy collaboration and polished methodology. 02:45.000 --> 02:52.000 We have small means, but we dream big, and the team is fully committed to this. 02:52.000 --> 02:57.000 A quick note about our business model, since it's a recurrent question that we get. 02:57.000 --> 02:59.000 Our strategy goes freeway. 02:59.000 --> 03:03.000 One is to have a free pricing on our SaaS. 03:03.000 --> 03:06.000 We have no pay plan, no open core. 03:06.000 --> 03:11.000 We also encourage any actor willing to sponsor the project, obviously. 03:11.000 --> 03:14.000 Two is staying small and focused. 03:14.000 --> 03:16.000 We are fully independent. 03:16.000 --> 03:20.000 And every team member is directly involved in building Tegat Next. 03:20.000 --> 03:26.000 We have no marketing, no sales department, no management player, no investors, 03:26.000 --> 03:27.000 and that's important. 03:27.000 --> 03:32.000 It keeps us small, and it keeps us sane. 03:32.000 --> 03:37.000 And free is, we don't directly provide services, I want to say. 03:37.000 --> 03:45.000 Instead, in the spirit of cooperation, we are building a network of service of professional partners 03:45.000 --> 03:50.000 to provide everything the user could want guaranteed support, 03:50.000 --> 03:54.000 hosting, training, etc. 03:54.000 --> 04:00.000 Then Zui is a protected trademark, and we did that in order to discourage 04:00.000 --> 04:07.000 bad actor for trying to monopolize profits around Tenzu. 04:07.000 --> 04:10.000 So, where are we at today? 04:10.000 --> 04:15.000 I'm happy to say that while we are not as fituri compatible as Tegat quite yet, 04:15.000 --> 04:22.000 Tenzui is already used in the real world by Undreads of Fuser and Content, 04:22.000 --> 04:27.000 and it's only a few months after it's first ever released in the end of September. 04:27.000 --> 04:30.000 And that's awesome. 04:30.000 --> 04:35.000 On Tenzu, we are able to organize the work in different spaces 04:35.000 --> 04:39.000 and assign fine-grained permission to team members. 04:39.000 --> 04:45.000 We have a fully functional combat where you can create stories, assign team members, 04:45.000 --> 04:51.000 add commands, add attachments, and you can have multiple combos 04:51.000 --> 04:55.000 in anything new project. 04:55.000 --> 05:02.000 We already have a dark team, and we have Tenzu, 05:02.000 --> 05:05.000 you are translated in free-long widgets, English, Spanish, and French. 05:05.000 --> 05:11.000 And you can configure your Tenzu instance to connect to desaprototation providers 05:11.000 --> 05:18.600 there's that you want. And as an exclusive announcement, just for us them, as of yesterday 05:18.600 --> 05:29.880 in Tenzu version 2, you can no collaborate in real time on your story. You can, you can see in real 05:29.880 --> 05:36.520 times the changes that are made by other users and as they are making them and you can't 05:36.600 --> 05:41.880 add your own. We are very sure to launch this feature as it is the very first one we added 05:41.880 --> 05:50.520 that really differentiates from the dear old tiger user experience. And Sán's giving a talk 05:50.520 --> 05:55.960 is all about taking risks. No is the time for everything to go to L and Sán's demo are 05:55.960 --> 06:02.280 obviously not risky enough. I will be doing a synchronized demo with my co-workers L to show you 06:02.280 --> 06:27.720 this collaboration goodies. That wasn't what I mean. Of course. I'm sorry. 06:33.240 --> 06:37.240 The demo effect, of course. 06:48.600 --> 06:53.560 So, this is Tenzu. I'm going to show you a project. 07:02.280 --> 07:24.760 So, I'm going to switch to dark mode to show you what this look like. But I'm going to stay 07:24.760 --> 07:33.720 nightmare because for a presentation like mod is more accessible. My co-worker is going to 07:35.000 --> 07:43.320 do some stuff. So, you should see the interface moving like this. Just a story up here. 07:43.560 --> 08:02.520 And disappear. And he assigned me to it and you can see that I receive in real time also 08:02.680 --> 08:13.960 notification. There are multiple compounds there. And if he's doing it is stuff correctly, 08:13.960 --> 08:23.320 yeah, new one. Just up here. And it's going to disappear or so. So, I'm going to what you can 08:23.320 --> 08:30.920 going to show you a bit. You can move around the interface. Different statues is a classical 08:31.000 --> 08:39.000 combo world. And now we're going to open this one to show you a bit the editor of the story. 08:45.800 --> 08:57.240 I'm going to add an image to this. And just drag and drop. And then you have it. And you have 08:57.320 --> 09:03.720 the attachments that was automatically uploaded. And then we're going to show you the live 09:03.720 --> 09:07.880 co-versions that my co-worker already started. You can see is cursor right there. 09:13.720 --> 09:18.680 It's a wizi wig editor with a lot of different customization. 09:19.320 --> 09:27.320 So, you can have table, you can have heading, you can have color, and all the good stuff. 09:29.480 --> 09:31.080 You can also have comments. 09:41.400 --> 09:45.320 And if my co-worker, where I took a month, I'm also going to see it live. 09:45.480 --> 09:59.320 You have different view mode for the story. And you can also move a story to another 09:59.320 --> 10:06.840 can than if you want. So, if I go back to main, my story is no more there. And if I go there, 10:06.840 --> 10:17.320 it's here. You can see which member are proud of your project. You can manage invitation. 10:18.280 --> 10:24.440 And you can recent invitation if you need to, and assign them to specific worlds. Also. 10:26.360 --> 10:31.320 Like I said, we have a fine green permission system. So, you have some pre-made worlds 10:31.400 --> 10:35.640 that you can't edit, and you can customize anything that you need to. 10:42.360 --> 10:49.080 You also have a user profile, obviously, where you can delete your account automatically. 10:49.080 --> 10:52.360 No more email to say, please delete my data. 10:53.000 --> 11:01.480 And we have, like I said, we provide free pricing. So, user can choose to give us 11:03.000 --> 11:17.480 money or not. So, the permission system is making the interface 11:17.720 --> 11:24.280 depending on what you have. Like for this workspace, I have no write permission. So, I can't 11:24.280 --> 11:30.600 create a new project. And if I go back there, my co-worker is going to make me a riddle user. So, 11:30.600 --> 11:37.880 automatically, I have no more access to create a new story. And if I go there, I can't edit anything 11:38.440 --> 11:46.760 if I try to type that won't work. But I can see the world content just not interact with it. 11:46.760 --> 11:53.560 And it's fully in real time. So, user accounts, confused permission because they're 11:53.560 --> 12:04.040 caged. And that's it for the demo. It went well, I think. 12:04.120 --> 12:18.040 Now, that's done. Here is what we'll be working on in 2026. To under the more use case, 12:18.040 --> 12:22.680 especially for user coming from TIGA, we plan to work on adding support for 12:22.680 --> 12:29.160 sub-task, stream, and issues. We don't know yet what forms that we'll take exactly as we plan 12:29.160 --> 12:35.720 to do lots of user research beforehand. And if you are TIGA user, you can help because we are 12:35.720 --> 12:42.840 always looking for volunteers. And the next feature, we are actually working on the right now 12:42.840 --> 12:49.240 is to provide a way from TIGA user to immigrate their project to Tenzu. While Tenzu is still 12:49.240 --> 12:55.880 evolving and not yet on feature parity with TIGA, we still want to provide a way for users to 12:55.880 --> 13:02.680 enjoy it without losing all their artwork. We are planning to design a legacy mode for projects 13:02.680 --> 13:09.560 created from a TIGA export with support for some stuff with not Tenzu equivalent quite yet, 13:09.560 --> 13:16.760 like story point, for example. And as soon as Tenzu provide an equivalent feature, 13:16.760 --> 13:24.440 the data for all previously important migration is going to be backport automatically 13:24.440 --> 13:32.440 to the Tenzu equivalent. And another exclusivity just for us them because we really want to 13:32.440 --> 13:39.160 spoil you today is you get a sneak peek into what this legacy mode we look like. The first step 13:39.160 --> 13:46.600 is this shiny new button that's coming soon and it's actually or a screenshot from our 13:46.600 --> 13:52.840 development environment so we are really working on this right now. Once you're at an export 13:52.840 --> 14:02.120 file you will be able to see in real-time the progress of the importation and this is a mockup 14:02.120 --> 14:08.280 on PENPOT by Zoey. You will then be able to pick and choose which user gets invited to collaborate 14:08.280 --> 14:15.240 with you from the pool of users that were previously parts of the project in TIGA. That's 14:15.240 --> 14:21.400 many different from TIGA importation when you had to add users beforehand. That's not the case here. 14:22.360 --> 14:29.000 And finally you'll be able to see your story with all the informations that we are you are used to 14:29.000 --> 14:39.880 in TIGA. And really by release this interface will evolve and will be replaced with the Tenzu 14:39.880 --> 14:52.840 way of doing stuff. Sorry I lost myself. And users that create project from scratch won't 14:52.840 --> 15:00.840 ever see the things that are specific to TIGA that we need to wait for Tenzu to support it natively. 15:00.840 --> 15:07.880 And this way user experience will converge little by little. Also while on pouring TIGA user to 15:07.880 --> 15:17.960 keep access to the data in advance of Tenzu specific features that we cover those use case. 15:20.520 --> 15:24.840 That's it for now. I want to conclude by saying thank you TIGA. Of course, thank you 15:24.840 --> 15:28.520 Khaledos. Thank you for being here. And thanks open source. 15:54.840 --> 16:12.280 It was thank you for providing all the content of the slides in Mugdon. And actually I'm 16:12.440 --> 16:18.760 iter of video myself. So I would always like to have text translations. I made the effort. 16:21.560 --> 16:26.200 Thank you for your thank you. 16:42.520 --> 16:53.480 And second question, can you let me tell the story of TIGA? First question was about 16:54.040 --> 17:00.040 with the way we get it or that we use. We actually use black nudges which is also used by 17:00.040 --> 17:08.040 last street numeric in inference. So no we didn't build it from scratch. We integrate with it. 17:08.040 --> 17:13.240 And it actually helped us a lot with live collaboration because a lot of stuff was already 17:13.240 --> 17:20.200 done to implement the protocol. The second question was about the shipping room. The story of 17:20.200 --> 17:29.880 the logo. Well, actually the first name ID for Tenzu was Moserschip. Since we talk that Moserschip 17:29.960 --> 17:40.920 will be already too branded with of why not Moserschip with a ship. And then because it was already 17:41.560 --> 17:48.920 still a risky to try to brand our product this way. We talk about other ID. We came to Tenzu 17:48.920 --> 17:56.840 which actually mean celestial map in Japanese. But the ship logo stayed because it was funny and 17:56.920 --> 18:01.000 we want to have those kind of identity of having a fun project. 18:03.400 --> 18:07.560 I would ask that we have a presentation about black nudges. One point is fighting in this 18:07.560 --> 18:13.240 difference as to the front to learn more. Any other question? 18:19.400 --> 18:25.320 Excuse me, last week numeric is the same to sort the kind of scene of the 18:25.320 --> 18:36.520 with the open desk. The question is about last week numeric. It's also collaborative 18:36.520 --> 18:45.640 streets made for public services in France. And we have a lot of common stack with them actually. 18:46.600 --> 18:55.320 But so it made me nervous not because in Belgium you are really doing this. France, Dutch, 18:55.320 --> 19:01.640 and German. So it will be public service. It's fed around for big services which bothered 19:01.640 --> 19:07.640 me to be multilingual. The question is about the multilingual each part of last week numeric. 19:08.600 --> 19:14.840 In thanks in Belgium you have a several long way to Switzerland also. But in France we all only have 19:15.720 --> 19:20.920 French stuff. You will need to ask them because I don't know if last week numeric is multilingual 19:20.920 --> 19:29.640 or not. It's made of several different software that can be used independently of 19:29.640 --> 19:32.840 from last week numeric. So I suppose those are. 19:39.640 --> 19:42.840 I'm completely external from last week numerics. You need to ask them. 19:45.640 --> 19:54.760 I have a minute to say that I've worked with my brothers. We are very proud of that by what 19:54.760 --> 20:02.200 I'm doing with my brothers. And I have a question with how they're about multilingual apps. 20:02.200 --> 20:13.960 And I'm completely into rubies, scram and extrusion. So the question is about the roadmap. Sorry. 20:14.040 --> 20:20.440 And the fact that I didn't give any dates. I'm not going to give date. But yeah, we hope to deliver 20:20.440 --> 20:29.240 this in 2026. Little by little. We do release really regularly and publish about it on this 20:29.240 --> 20:38.120 piece of paper. I think that's it. Thank you.