The next talk which will be presented by Yuland is about open project, the same software
as the one that is on the t-shirts here, and it's going to title the open project a year
full of updates.
Thank you.
Yeah.
Hello.
I'm B-Land, I'm co-founder and CEO of open project.
I'm very glad to be here again.
It's, I don't know, my fourth time here.
And for those that don't know,
open project quickly, open project is not showing up here.
Oh, shit.
That's why you need to move this.
Yes.
OK.
Right.
I'm speaking in a name of this little bit.
So, yeah.
Really, if I don't have the name, I'll write now.
Did it notice, D-O?
Yeah.
So, L-L-L-L-L-L.
So, my internet name, I have a question.
OK.
L-L-L-L-L.
OK.
Yeah.
OK.
Is that better?
Yeah.
OK.
Thank you very much.
So, for those that don't know, open project yet,
open project is a collaborative project management system,
and which allows, you can think of,
of open project there's something like,
Jira and Trello in one thing, but it's open source.
And it allows to basically do the work from bottom up,
like teams working agile in, in, in, in,
canvas ground manners, or further up in an, in high altitude,
top down, like, you plan ahead of project in gun charts,
and so on, or even further, going the portfolio management,
like, where do you invest your budgets?
It's my fourth time here.
So, last year, what has happened since last year,
is the topic of this talk today.
I want to show you a couple of highlight features
that made it into open project, and also
want to give you a little bit of outlook, what's
about to come, and where we are working on.
What we're working on.
This is just, right, start right with the first feature
that we introduced is automatic work package subjects.
There's something that, you know, like,
2022-25 was basically the year for open project,
where we really went full on to the public sector,
and public sectors, usually big organizations,
they need to structure the work.
They use open project to structure the work and the teams,
and they have recurring tasks, tasks that are similar,
and to keep all and structure,
they want them to be named the same way.
So with automatic workpages titles,
you can set patterns for workpages titles,
like, say, here a sign is started,
finish date offense on, and they get automatically used
for the next workpages that you create of the type.
Very convenient.
Yeah, you don't know that you need it until you have it.
To our commitment to improve accessibility,
we continue to on our dark mode and light mode,
and high contrast, and so on.
And I want to highlight this little feature here
that now you can even have high contrast mode in dark mode,
which, finally, is not only a feature that people with disabilities,
benefit from, but also, not the programmers like me,
we like to have more contrast once in a while.
OK.
I talked about organizing work,
usually that is done in issues and workpages,
and organizing them in projects.
But actually, that's just one part of open projects.
Another thing that is used in the job that a lot of open projects
are meeting agendas.
Meeting agendas is basically like you want to come to a meeting
and be prepared.
And often, I don't know how it's for you,
but organizations, I think, 90% of my meetings,
they're recurring meetings, they're like the stand up,
they're the weekly, they're your fix, you know?
And we kind of cross the work right on the issues.
And I'm like, oh, here's a topic that I should bring
to the next meeting, and I don't want to interrupt right now.
This is why meeting agendas are great.
You just bring the workpackage onto an agenda.
I already presented this last year.
Well, what's now, what's now new is, now you can simply
grab a URL from what can project and subscribe
to all your meetings in your favorite kind of application
by ICO, OK?
So you don't miss any meeting anymore.
We have more features in the meetings module
like a presentation mode that looks a bit like this presentation
here.
So you jump from one agenda item to the next ones.
And there are more features to come over the next,
in the next release.
So just stay tuned, take it out.
Open products also used for IT service management.
And we continuously improve and extend our features
at here.
And one very important thing that we added last year
is the ability to have private or internal comments.
So let's say you have an organization.
You have a team.
You're used to just have add comments to your workpackage,
your issues, your task.
And there you have this thing where you need to ask,
add, do you really do this?
Do you really want to do that?
Or do you have more information on this?
I don't know what to answer.
There's an internal comment, no?
Like it's meant for your colleagues, but not for your clients.
So with just one click, you have the comments,
there's normal, and with just one click here,
it's just visible for you and your colleagues.
Another thing, once you have it, you can't
without anymore.
There are more ITS and features to come 2026,
especially I come to this later about the Lazy and Data
Center exit.
OK, that is now a completely different level.
So up until now, I was talking about the data
daily work, task, and who does what when.
Portfolio management is a layer above.
Portfolio management is when you, for example,
as a public authority, you have a certain budget.
The budget should be used for a strategic goal.
How do you best invest?
So you best invest in order to, you create a set of projects
and that together, hopefully, with these projects,
you will reach a certain strategic goal.
And yeah, 25 or 35 was the year of the public sector.
And we had a portfolio management to open project.
With that comes that you'd not only have projects,
you can now also have portfolios as first class citizen
and programs.
So programs, rep, a set of projects,
and a set of programs can be a portfolio.
Pretty simple, no?
OK, cool.
The good thing about Portfolio is that you can then
check the health of your whole portfolio,
so how is your investment going?
So how good is a achieving or moving towards your strategic goal?
And so every project can have a status,
but Portfolio can have a status in and so on?
Yeah.
But if you manage a portfolio, you also need
to have data on those projects.
Usually, there's something that you do in spreadsheets.
It's another system.
It's not in the system.
So we added a lot of capabilities to add that data
to projects and portfolios inside of our projects.
So that you don't need spreadsheets so much anymore.
These we call project attributes, portfolio attributes,
and so on.
And with the next release, not yet, but we
will have a wizard with which you can
everyone that creates a project ask a certain set of questions
so that they fill in this data so that you
have better comparability between projects.
And to better compare them, even further,
you can say, OK, some of these values
that you attach to project, you give them a number.
And then you can calculate a score.
So you could compare, I don't know, five begins the seven, of course.
But if you have multiple values in you
want to calculate the score out of multiple attributes,
this is what we can do now.
So we can have fields that I've calculated values.
They calculate instantly by setting attributes.
So this is the formula.
You're on the right-hand side.
You see the attributes.
And by setting a certain field,
we will calculate a new score.
And then we can compare one project by another,
if I have this scores.
Scores help to just get a little bit more structure and bit
more comparability.
That was a very huge topic, or a huge feature.
This one is a little one.
This is the one that you come across like 50 times a day.
It's actually the search.
We improved the search a little bit.
So that you can also search for work package type names
and best status in order to better find the work page
that you're always looking for instead of searching
for the gray-level word.
That's my personal passion project for 2025.
We added real-time collaboration to open project.
First on documents, because documents
was the least used module-nopen project.
And it needed to get a little bit of update.
But actually what I wanted to do is I wanted
to get into real-time collaboration.
And documents was the safest place, because nobody really
used it.
Because if you really want to share files,
take next cloud.
So I wanted to get our team up to speed with the technology.
And this is what we came up with.
So you can have documents where people just come together
right together on text, share their thoughts, improve each other
at the same time.
It's actually pretty fun.
It's chaotic.
It's democratic.
It's really cool.
And yeah, so what is actually very interesting about that is,
OK, kid, now we have a place we can quickly write on stuff,
unstructured, structured, later.
You can break it down into work package and so on.
But for me, it's not so much about documents,
because if you say, OK, we can talk about knowledge,
management, and stuff, take XVG.
That's what for me, as a CTO, is really interesting here,
is the editor.
That's block node that we use here.
Use if I are here.
Hey, block node here.
Thanks for the software.
I met you this year ago.
And now we have that software here.
It costs them to hack a thin slater.
That's really, really cool.
What's so nice about it?
It has, well, it's good to the next slide.
Block node rock.
They say, use if says, third to nation, notion-style editor
in minutes.
And I think that's a good sum up of it.
Like you want to have the notion experience
of the modern application.
And I think it really gives that spirit open product.
It's really, really cool.
And what's impressive is also used in big application
bundles, like Open Desk, last week,
mind-be-roll, that newest of those.
And yeah, that makes it interesting,
because we also, we bring open project
as a component to those bundles, not yet last week.
Let's see.
But Open Desk and mind-be-roll, for example,
or next cloud hub.
And when we bring open project as a component,
we see it as a component to a bundle,
we also think integrations.
And if those applications or other applications
in that bundle, if they use block node,
it becomes so much simpler to integrate open project,
because let's say extending the slash command.
Some feature that you would need to implement
for every application, implemented once.
Provided as an extension, publish it,
and everyone who wants to integrate
with Open Project can just grab it if they use block node.
Actually, it has a GPL license, so very nice.
Yes.
Yeah, to be fair, that's just the beginning.
I actually want to have real-time collaboration
on work packages, because that is where
all the work is managed of Open Project,
where the real matter is that we are people
work with.
For that, we need to migrate more stuff
from the old editors, you get it at a five.
Or more crores, and so on.
It takes a bit more time.
It needs to be more stable.
We need to get the experience in that we are
let we're taking now with documents.
Talking about Open Project as a component.
That is not my passion project, that's my purpose project.
I see that we as a Open Source ecosystem,
we need to provide our applications in a way
that they become components in a bigger setting.
So the bigger setting here, our application
bundles, like next Cloud Hub, open Desk,
mind-be-roll, you name it, last week.
And for this, we application providers,
we need to be pluggable.
What does it mean to be pluggable?
Pluggable means that it's easy to integrate it
into the operations, so you to roll out, to deploy it.
So on the Kubernetes cluster, with home charts,
it's standardized easy ways just to spin it up,
to do the backups, everything is very smooth.
People don't need to learn about Open Project,
although they're multiple services and databases
and caching and whatever.
It's all there.
Now with HocusPocus, for Block node also,
another service is in, but people don't need to know
that there's complexity.
Just take the home chart, spin it up, and off you go.
So I think every application should provide this.
If not, work on it, please.
The other thing is, OK, being a good citizen
in terms of login logout, or IDC, as Snowwood standard,
you most applications have that, at least to some extent.
That's pretty good.
Sing a sign on, yes, of course.
Sing the logout.
I assure you, have it.
The next very important thing is skin.
Skin is for user provisioning.
So that is, OK, if you have a central place
where you want to get people into application bundle
and then you're like creating accounts,
and then you want to make sure that they're
an open project and the next cloud and an x-viki
at the same time, or you want to lock those users
because they leave your organization.
Skin is the way to go, because it's almost immediate.
It is fast, it is standardized.
Don't go the other way anymore, just do it.
It's one time investment, but then you
have an industry standard, and you're easy to plug in,
and you're good citizen in the ecosystem.
The other ones, this, like jet token, structured,
authentication authorization, and token exchange
would make it easy to communicate between applications.
I know we application providers
we often think just in our own realm,
but we need to think integrated.
So our applications need to be able to talk
with other application back-ends in the name
of the current user that the user is over there.
So let's talk in your sense.
Question?
Talking about skills, as the server
played a bit different from sending it.
So it was a big applause for the guy
in the names of sending it.
Yeah, thank you.
So my brother was just mentioning that this
given integration was sponsored by Sendis.
Cool.
OK, you can set it up.
OK.
Now this is actually the big topic for 2026.
As you might have heard about, Adelaide is saying,
we kill the data center, which is basically running your
Adelaide instance on your own machine.
They say you can only go to the cloud, to their cloud.
The end of data center is March 2029.
And yeah, I don't know what they're thinking,
but many organizations don't have the option.
If you're, let's take an extreme example.
If you're a secret service, you don't put your data
into the cloud of someone else, right?
You don't do it.
So that's a worldwide problem.
And organizations all over the world approach us.
OK, can you provide an alternative?
Can you be a replacement of Jira?
And for this, we partner with ButxViki,
because they do the alternative for confluence,
and we do the alternative to Jira, and we integrate.
Yeah, basically that means that we can link
X-Viki pages with work packages back and forth.
So you can navigate just as you use to with Jira issues
and confluence pages.
You can extend the, yeah, you can use a lot of macros
on the X-Viki side that you also familiar
from confluence, like work package tables,
breakdown charts, and graphs.
Yeah, this will be released by the end of June,
and stay tuned on that one.
Yeah, so you have a Jira instance, how do you continue?
How do you get out of that situation?
Then you probably want to carry over all the jewels
that you have created over the last couple of years,
which are basically Jira issues in the history.
So by the end of Q1 this year, we're going to release
a migration tool.
You just put it in the application key of Jira,
and it will pull the data in, and you will choose,
okay, I want to migrate this in this project,
and you have the issues, the projects, the attachments,
the comments.
This will be all done by the end of Q1,
and then we will extend it over the year
to have relationships covered and more,
more structures taking over from Jira to open product.
We also are working on, let's say,
how to say this best.
Jira, when people work with Jira,
they are so much into this how to erase this,
how I know it, we want to continue like this.
And, yeah, Jira has a certain style of HR product management,
how to plan sprints, and how to manage the backlog.
So we will take the good parts of it,
and you have to try to come up even with a better experience.
So we're working on this right now,
and expect a couple of releases with iterations
of improvements.
And then the further Jira fundamental
that will come throughout the year,
it's starting with speaking work package identifiers,
like where you first have the project identifier,
and then a sequence number.
So that's already coming in Q1.
So that's also very soon.
We will work on,
we will work on automations.
So we get the feedback that configuring workflows
is easier and Jira than an open project.
So we will work on this.
We will also work on our first steps of automations,
like, okay, if this and that scenarios,
and yeah, we will also make it easier for project
to come up with their own structures
and their own set-ups, configurations independent
of the big central that is somewhat of people
that you don't know and you don't know
how to ask them to approach them,
to give them more autonomy in the project itself.
So please stay tuned.
This will be an exciting year,
and just remember as an open source ecosystem
integrated real stronger.
Thank you.