WEBVTT

00:00.000 --> 00:09.480
Let's start again. So my name is Julius, I work for next slot and I want to talk a bit about

00:09.480 --> 00:15.720
the next. Office mainly with a focus on how we work together with Colabra and the Libra Office

00:15.720 --> 00:24.560
community to build the web office integration into next cloud. For those that aren't aware,

00:24.560 --> 00:29.240
just I keep that brief because I guess most people know what next slot is. We are a content

00:29.240 --> 00:35.880
collaboration platform, fully free and open source. Every code is available to everyone. We

00:35.880 --> 00:42.040
have different components. We have class-to-five management group where mail calendar, next

00:42.040 --> 00:50.920
or talk as a video and chat platform and of course next office as one key component there.

00:50.920 --> 00:56.240
Where we work together with Colabra to build that and this is how our next office looks

00:56.240 --> 01:04.960
like. If you've seen Colabra online before, it looks quite familiar. We have a couple of adjustments

01:04.960 --> 01:12.400
there to fit a bit more into the next cloud user interface and UI that we have. Different

01:12.400 --> 01:20.480
I can set slightly more simplified user interface but generally the software is the same and of

01:20.480 --> 01:28.720
course we make advantage of all the advanced features that Colabra online has. As mentioned,

01:28.720 --> 01:35.680
we work closely together with Colabra. I get a bit more into that later on like how our teams

01:35.680 --> 01:43.280
work together because I think that's also one important part that probably still happens

01:43.280 --> 01:49.360
not often enough that open source projects work together or closely together. Of course,

01:49.360 --> 01:58.160
everything is based on the office as kind of the core for all the nice document editing there.

02:00.160 --> 02:08.080
I want to highlight a few features or integration works that we did together in the past

02:08.720 --> 02:17.760
roughly past year. One of that is a feature that Colabra recently added is an API for

02:17.760 --> 02:27.360
document extraction of information and transfer transformation of documents. This is API work that

02:27.360 --> 02:36.880
most of the data from Colabra online did online and the process core. It allows, it gives us

02:36.880 --> 02:43.120
a rest API where you can send a document to and then you will get like a structured JSON data

02:43.120 --> 02:50.000
with the content of the document. Can be images embedded, can be like paragraphs or slides,

02:50.000 --> 02:55.440
you get like all the different elements that are there and then the second part of this API is

02:55.440 --> 03:04.080
that there is a transformation endpoint so you are able to pass document and then do certain changes

03:04.080 --> 03:11.920
on it and that all from an external party like from next time for example. As of right now,

03:12.000 --> 03:19.920
there is like a way to for filling out forms with content controls. There is support for all

03:19.920 --> 03:26.880
kind of different controls that are there in documents. There is the ability to read and write

03:26.880 --> 03:34.000
chart data. You can set document properties if you want to add copyright information or certain things

03:34.960 --> 03:42.880
and the most recent addition is that you can actually do changes to presentation slides.

03:42.880 --> 03:51.040
I get a bit more into that later. First of all, this is a bit of how we make use of this

03:51.040 --> 03:59.680
API instead of next slots for the content controls. We added the ability that if you have a template

03:59.760 --> 04:06.960
you start creating a new document with basically render all the content controls that are in the

04:06.960 --> 04:12.800
document as like a nice form that users can fill out. You basically just like enter the information

04:12.800 --> 04:19.680
then you will end up with a nice detailed document there. The second part is that within next

04:19.680 --> 04:25.520
slide we integrate with another open source tool, a windmill for building more complex

04:25.520 --> 04:30.800
automations and this is where the API imports really become powerful because you can build like

04:30.800 --> 04:39.280
all kind of workflows for like company processes, processes in public administrations where one

04:39.280 --> 04:44.720
aspect then for example could be to generate a PDF out of a form with data that comes from other

04:45.600 --> 04:52.160
systems. This is where it really becomes more powerful. Put on transforming slides that was

04:52.160 --> 04:59.200
the most recent addition so it's a command queue that you can basically pass any commands that should

04:59.200 --> 05:11.280
be executed on that specific file. So there are slides, commands select certain slides to change

05:11.360 --> 05:18.640
layout to set text on it. Just so you have an idea that's from the documentation of collaborative.

05:18.640 --> 05:26.240
So you can basically rearrange the slides at new slides in there and then set the text and we

05:26.240 --> 05:33.600
want to basically experiment with this to be able to generate slides in experiment with LLMs also

05:34.480 --> 05:39.840
because there's like I mean AI is a huge topic. There's probably no way around that anymore. So

05:40.160 --> 05:47.120
we also want to get involved in that part and this is kind of the groundwork done by

05:47.120 --> 05:58.240
by collaborative. Yeah that's kind of like there are APIs as mentioned. They can be used

05:58.240 --> 06:03.520
either on collaborative side or we as next are also exposed them and of course we're regular

06:03.520 --> 06:07.680
discussing all the future use cases because they could be a lot more things that you can

06:07.760 --> 06:12.880
transform documents to like spreadsheets we haven't looked into yet what exactly you could do with

06:12.880 --> 06:22.480
those so there's likely more to come there. One other aspect as I mentioned AI is a topic we are

06:22.480 --> 06:29.440
in next log integrating with all kind of different AI platforms we're most focusing on the ones

06:29.440 --> 06:37.600
that are somewhat open so we also have a rating system for AI there but this is all kind

06:37.600 --> 06:41.840
of optionally in next log you will always have the ability to enable that if you wanted and if not

06:41.840 --> 06:51.120
then there's no involvement of any AI and this is also where we integrated our dynamic AI system

06:51.120 --> 06:56.240
the next log assistant into collaborative you can just click a button and then get access to whatever

06:56.240 --> 07:04.720
LLMs you have integrated there. Next one is one example that has been around for quite a while in

07:04.720 --> 07:13.520
collaborative online like a five conversion API quite simple we made use of that already for

07:14.320 --> 07:21.360
yeah for years just for generating previous files but we actually now also integrated that into

07:21.360 --> 07:26.800
the user interface make it easier for users to convert files right from the file listing without even

07:26.880 --> 07:36.640
opening the full office UI and yeah there's more work ongoing like we want to make the setup

07:36.640 --> 07:44.000
easier because that's I think most like majority of issues that we get reported and see in the internet

07:44.000 --> 07:49.760
is about problems with the setup and people get errors that they don't understand so we want to

07:49.760 --> 07:57.040
really want to make that easier we're trying to catch more and more scenarios where connectivity

07:57.040 --> 08:05.040
could fail and with recent work from Miven from collaborative we actually close to last gaps or

08:05.920 --> 08:10.800
we can do now also can check the connectivity from collaborative to next cloud and basically

08:10.880 --> 08:19.760
can cover the full chain of where network connectivity could go wrong and yeah I mean that's just

08:19.760 --> 08:26.400
like how we try to expose the user interface so we try to give more hints on where things go wrong

08:26.400 --> 08:32.960
and then point people to the right documentation or ideally you just give them a hint on what they

08:32.960 --> 08:40.720
need to change immediately yeah I mean there's a lot more happening you heard a couple of things from

08:40.800 --> 08:47.680
Michael all the great features that are ongoing in collaboratively office performance improvements on

08:47.680 --> 08:53.920
both sides on collaborative but also with the next cloud where we make opening files faster

08:54.640 --> 09:02.480
reduce overhead in the browser and on the server there yeah I think a couple of that was already mentioned

09:03.040 --> 09:08.800
we're planning to look into more deeper integration of slide templates that's maybe also one

09:08.800 --> 09:13.680
interesting thing so you can have all the templates that you have the next cloud right with in

09:13.680 --> 09:25.520
your sidebar of your impress in the browser yeah and generally a lot of bug fixing but I wanted to

09:25.520 --> 09:32.240
also talk a bit about like how we collaborate as to communities to software companies that are there

09:32.320 --> 09:42.320
we are yeah like closely working together our engineers having regular or basically weekly meetings

09:42.320 --> 09:48.320
together where we just exchange on what kind of bugs have been reported on either sides what is kind

09:48.320 --> 09:58.160
of common problems that we run into we do like feature code development where one party comes up

09:58.160 --> 10:04.800
with an idea and then we drive that together forward we also do shared code contributions so

10:05.600 --> 10:11.200
collaborative people are committing changes on our code base on the next local base and the other way

10:11.200 --> 10:17.760
around so we're really trying to help each other there with like the ability that everyone can

10:17.760 --> 10:26.480
provide and there's a lot of good exchange of ideas there like especially this weekly call is really

10:26.560 --> 10:35.200
beneficial I think it's nice to stay in contact to also get insights from how other open source communities

10:35.200 --> 10:43.840
work I think this is really something that isn't happening enough and yeah like if there is any

10:43.840 --> 10:49.200
open source project where you think you can work together definitely try to get in more contact

10:49.200 --> 10:54.640
we've talked to the people and I think being around here for them is kind of the best place to start

10:54.640 --> 11:01.680
it yeah a couple of other things our designers also or usability people are also in

11:01.680 --> 11:08.080
regular exchange we do usability testing both with customers but also with end users

11:09.920 --> 11:17.440
or home users and we also have regular design reviews because in the next time we have quite an

11:17.440 --> 11:25.920
open design team let's say so also people from the community can come to our design team and

11:25.920 --> 11:32.160
ask for reviews of their apps or their the work they're doing get feedback on that so this is

11:32.160 --> 11:40.240
something where we also spread further than the the next our community and also like interact with

11:40.400 --> 11:47.040
collaborative there sometimes we also align with users where it makes sense because if you do

11:47.040 --> 11:51.600
like both work on a feature then you also want to you're probably going to make more

11:52.800 --> 11:59.040
more impact if you announce that together and maybe one thing to mention that something

11:59.040 --> 12:03.120
that collaborative has that I find quite nice is they have a weekly community meeting

12:03.760 --> 12:09.440
call where people can just join get involved just just listen to what's going on

12:10.640 --> 12:16.000
think that yeah something we don't have a next up but I find that quite quite good and quite

12:16.000 --> 12:23.040
interesting to join from time to time yeah and last but least just wanted to

12:24.560 --> 12:30.400
mention that we're of course open for any contributions we work together we have external

12:30.400 --> 12:36.080
contributors as well both next lot and collaborative online have dedicated pages for how you can

12:36.720 --> 12:42.960
do your first contribution we have good first issues like that give you an easy start easy task

12:42.960 --> 12:50.640
into doing a code contribution but also others like translations are reporting issues that's

12:50.640 --> 13:00.480
all valuable things and yeah I think if we work together more between open source projects we can

13:00.480 --> 13:07.920
actually make a bigger impact because yeah just like the synergies we work together and yeah

13:07.920 --> 13:11.920
I mean in general if there are any ideas you want to talk about feel free to

13:12.640 --> 13:19.040
address them share them with us and yeah looking forward to maybe have some additional

13:19.040 --> 13:25.840
contributions there and that was it from my site thank you

