with just a little bit of information about Quave for people who are unfamiliar with it, for people who haven't heard of it before, what is Quave? Yeah, yeah, we've been going for a long time now. But yeah, I hope there's still people new to Quave that are listening and watching this. So Quave is a knowledge sharing platform and a community platform that we built on top of Bloom. So I used to refer to that as

social internet, but I found that people have really like old fashioned associations with the word internet. So it's not that, it's not that stale box in the corner. It's far more sexy than that. So think of it as a community platform that enables knowledge sharing within a company or within a wider community.

Cool. And you mentioned that it was spinning around for a while. So can you just tell a little bit more about that? How did it get started? Who started it? When was that? Yeah, I used to go to Sorrento, to the announcement in Sorrento. And I think it was in 2011 that I started coding a microblog platform within the microblog component within Bloom. And

that was before Twitter became the mess that it is today. It was still sexy at that stage. And I wanted to have something like Twitter in Bloom, like an activity stream. Something that is different from just content, which is documents. So something that really affords social interactions and quick interactions. So I started building that and that got people

interested. And also, I think a lot of that happened at Sorrento. We started networking around that. And from that emerged the Plone Internet Consortium a few years later, where we had an alliance of, I think it was nine Plone companies, where we said, let's work together

and take the best internet components that everyone has and fuse them into a single product suite on top of Plone. So that became Plone Internet and that later evolved into Quave with the additional branding and keep developing it all the time.

Cool. And that's just kind of continued that same consortium with people, members leaving and coming, et cetera. It's a much tougher market than I anticipated for sure, personally. So the lead times in the business are really long. So we saw most partners actually dropping off.

Like, you know, a lot of people invested in that product, but they weren't able to to bring it to market successfully. So in the end, it's mainly SysLab that is pushing the solution that my company goes in. So together, we're still carrying Quave forward. And that's going well.

But, you know, it's a pity that not more companies are still involved in that. Right, right, right. And so what are you folks doing with Quave now? That's a lot. So I'm not closely involved in SysLab's clients. I know they're working for several universities. They have some industrial clients. And we also have a number

of NGOs and public sector clients. And personally, like in my company, I'm working with the public sector mainly currently. So that's an agency in the Netherlands that is active in the healthcare sector. And in Belgium, I'm working with a Belgian service provider to public sector

bodies, basically. And then we just got approached by the blown foundation actually to provide a supported Quave installation for the blown foundation. And then run that. So that's being prepared right now. It's not live yet,

but that will come this year. Cool. You mentioned having a number of clients in the public sector. Are there particular benefits to using Quave in the public sector? I think, yeah, those apply for all open source deployments, I guess, which is you get longevity.

Whatever happens to your supplier, you can actually take control of that deployment by yourself. So you know that we always have a viable access strategy with open source. On the plus side, it's cost effective typically. And we also see like a cultural match, certainly in Belgium with the people there who are used to working with open source. And for them,

it's just a no brainer to do this with Quave because it just fits their existing knowledge. It fits their infrastructure. It fits how they do things. And do I remember right that Plonus is used in a number of cities, small cities and towns in

Belgium? Or am I mixing that up? Yeah, no, that's actually that's my main focus nowadays. It's working with Emile, which is sort of like a shared service center for Belgium, French speaking, Belgian government agencies. Yeah, municipalities mostly, but they also work with other types of agencies. And they have a product portfolio that they make available, which is all loan based or

mostly loan based. They also have some audio applications. So they have a whole suite of applications that they make available on a SaaS basis for their clients. And now I have been working with them and I'm working intensely with them to bring Quave to all of their clients. So

Quavers is now part of their product portfolio. And municipalities can subscribe to Quave and you know, get a roll out of Quaver there. Cool. That's, that's quite exciting to do that. Yes. Yeah. And, and the municipalities are using it essentially for government functions like posting meeting information and law laws and notices and that kind of thing. Is that

generally what Plonus is used for in those governments? It's more traditional. And though most municipalities, they use it for documents repository, like for human resource management, like, you know, what's your holiday allowance typically. And so, so a lot of reference documentation and also they're trying, you know,

so Quavers is designed to support a shift to a more bottom up organization and they're consciously using it as that as well. So they, they, they, they get Quave because it then enables the employees to, to talk more horizontally amongst themselves. And for them, it then fits within

the wider product portfolio where Emio has, they have their own meeting product, for example, where they do all the actual meeting notes. So those, those are outside of Quave. And we're going to use Quave also as a portal, like as the central hub to access all those other applications. So it's going to be like your entry point into the whole network of applications. So I hope we'll get

a lot of traffic and a lot of visibility in that way as well. Cool. Cool. You, you, you mentioned Open Source as being a part of this. Is that, is there that sort of a cultural fit for specialty, or is it more a cost benefit analysis kind of thing? Why is Open Source, the Open Source model particularly useful in the, in this community of clouds?

Well for Emio, they are a blown shop. Basically they have a lot of blown expertise. So for them, it just makes a lot of sense to do it like that. Yeah. Yeah. That makes sense. I often feel like there are certain sectors that the Open Source model

really appeals to like education and government. So that makes sense. Yeah. And for them, it's like, so, so culturally, these are, these are people and organizations who are used to like co-investing. So the whole premise of, of Emio itself is like, let's, let's get together and, you know, fund Open Source applications for,

you know, for the public good. So that you can share, you can share the costs across multiple municipalities and, and you get the benefits of having a, you know, well-designed, well-run application. Right. And that applies to Quake as well in this context. So, so for them, it's natural. They're not, they're not competing against each other. So they can easily see like, okay, if we pull the money,

like we're all going to be richer in a way. Right. Right. Yeah. That's how it works. So it's really probably a good situation. And is that community of, of municipalities, is that sort of the portfolio of, of products that you mentioned, is that called Camunes Plon or is that something of the past? I remember that

name. The name rings a bell, but I don't remember the context. So that's something different. Oh, okay. Yeah, I guess it was. And I was not involved, like in the old long offer initiative. So maybe. Right. Yeah, it might, it might. Plon has a long history for sure. Yes. Yes. We all do by now.

Yeah. So you mentioned that you've been active now with, with these new clients and new heightened interest in Quave. So tell us a little bit about the new features that you've been working on, what you've been doing, what you've been adding to Quave recently. Yeah. So some of the stuff actually, so what I, what I did for Inmio, a lot of that is not even

visible to end users, which is maybe not that sexy, but you know, for Plon people, it might be interesting to, to hear about that because like we're, we've built a completely Dockerized Quave DevOps pipeline so that we can run the Quave in a Docker based environment for Inmio,

which doesn't sound very sexy, but was, it was a lot of work to make that work. And in terms of user facing features. Yeah. I just look at our release log and it's, there's a lot going on, but it's difficult to, to capture that in a sexy headline. Well, the one thing that jumps out is that we've been working on a new notification system within Quave

so that if something happens that you are interested in, or, you know, we expect that you were interested in, you, you can subscribe to that and you will, you will get notifications via email, but also via push messages or like in the browser, if you're looking at Quave. So that makes it easier for people to keep track of Quave. And it also is useful in situations

where, so if it's your internet, it's basically your homepage, if you come in, but also typically fits in a situation where it's between organizations, where it's like a sharing platform between other organizations. And in that case, as an employee, it's not your natural homepage. It's not something you easily go to. And in those scenarios, email is really

valuable in getting you notified, like, Hey, something interesting is going on in the Quave installation that you're a member of, go over and have a look at what's going on there. So that, that increases, that increases a lot of visibility as well and, and usage of Quave. And other than that, we're constantly working on, on tuning features and, and, you know,

expanding little, little nooks and polishing the stuff all over the place. You know, when I started, I never thought it would, like, it never ends. You know, you'd think at some stage the product is finished, but you know, the backlog just keeps, you know, it just keeps giving its, yeah. Expectations continue to change. Yeah, yeah. There's always, there's always

interesting stuff to do and stuff that needs doing to make clients happy. Yeah, yeah. Well, great. Any final parting words you want to leave with folks to peak their interest in Quave or, or, or anything at all? Well, I would actually say like, I saw a, a

poll on Macedon the other day where people are asking like, what are interesting communities that you've been a member of? And I would say like Plone Rocks, the community. I mean, the product as well, but you know, the community is just superb and that would be my parting words, like Plone Rocks. Yep, for sure. And all, all folks listening to this should definitely get

involved and consider coming to the upcoming conference, which is... See you all, see you all in Basquiat. I know, so awesome that we'll be able to, well, for me, I didn't go last year and this will be my first, many years. It will be mine again as well after many years. So it's going to be great to meet everybody. Yeah.

Yeah. Well, great. Well, thank you so much for sharing the Quave news and that's it for our World Plumb Day session. Thanks everyone. Thank you for having me and have a great World Plumb Day. Yes.