Yep. Hi. Yeah, nice to see you. You're doing a long series, the Beethoven Sprint. Exactly, yeah. I mean, I haven't been there since like the beginning, but yeah, I think I'll at least be there for a while.

Neither have I. So I look back a bit and I found this presentation back from 2017, which as far as I can find, that's the first Beethoven Sprint organized, where, well, I can safely say what we now use in Plone 6 as the default front-end photo was kind of started at the

company you now work for, and I also work for part-time since April at Kidconcept. But the headless CMS it was called. And I looked a bit further in the presentation of 2018, it was called Plone React. And in 2019, the third Beethoven Sprint, there the name photo

pops up. And I'm really curious, maybe I can dig in the heads of some people by interviewing them and asking a bit more about those early days. So we have the fourth Beethoven Sprint. So tell me a bit more. Yeah, I think so. Probably the fourth. I think it's the fourth now.

Yeah, as we both noticed, we weren't there for the first two, I guess. I only joined Kidconcept in 2018, and I think rather late that year. Therefore, I hadn't had the chance

to go to the first Sprint there. So everything we're going to tell you is linked on Plone.org on the main website. So if you go to the Plone.org, there's now the announcement for Will Plone Day, as we will air this on Plone Day, this small talk to present a Sprint. But if you go down there, there will be community news, latest news, latest news, community. And there it is, Beethoven Sprint.

Go, go, go. Click. Yeah, I think we need a more prominent place there, I guess. Yes. Yeah, we can move it up, I think, after Will Plone Day, after this recording. Yeah, sure. There's your contacts, and here's the real website, a strategic Plone Sprint on Plone 6, 1 and 7, organized by Kidconcept. Kidconcept, tell me a little bit more about Kidconcept,

Jacob. Yeah, well, we're a lovely, not that small anymore company based mostly in Bonn. I wouldn't say mostly because in Bonn, at the moment, I think only five people, and the rest of

us is like spread out everywhere. And we have quite a few like familiar faces working with us. As Fred already mentioned, yeah, since a couple of days at time of recording, I think. Yes, indeed. Also him. Great to have you on the team.

Thank you. Yeah, and we have Timo, who's like all over the place with Plone, and Erico, and Victor, and plenty, plenty of more great people. You see, yeah, most of them, or pretty much all

of them will also attend this sprint on our participant list on the website that you can see here. Please be aware this list is not completely final and also not up to date yet. But as you can see, we'll have plenty of people there. Also, yeah, now that we're looking

at the website, shout out to our great sponsors, Plone Foundation, Red Turtle from Italy and other work from Romania, who sent over the best guys to also take part in this sprint.

Yes, so it's indeed a strategic sprint. It's sponsored by the Plone Foundation to help with organizing it financially. And let's talk a bit more about the subjects because strategic sprints tend to do strategic sprints for Plone, and the better sprint hasn't been

shy of, I think, being a strategic sprint from the beginning. What is this year the main topics? I think from the head of my mind, it will be the next Plone release, the next small minor Plone release, 6.1, because we've had 6.0 in December. So what are some of the

things that we already know that people will be working on for 6.1? So as you already mentioned, like, Beethoven's sprint more or less is the birthplace of Volto. You react frontend for Plone to bring the Plone stack up to date with all the latest

technology. And this is also the goal for this year, to push Plone forward and forward and forward. We're working towards the Plone 6.1 release. That might actually happen this year. I'm not sure. I think so. I think it will be aimed for Autumn.

And we'll also aim even further and start working on Plone 7 even, which I'm not sure whether there's already a release date set or not. In the end, probably it's done when it's done. 7 will be further away. 7 will be at least 2024, I think.

Yeah, definitely. So one of the things, the teaser block got its way into Plone 6.0. It was added to the Volto combining Volto release. Now I have to be very impolite because I wrote the news

items myself for the patch releases. I think in 6.03 also we added the Volto release there was 4.06. I think there we had the teaser block, but there's another bigger block coming in hopefully for Plone 6.1, but it still needs a lot of love and also discussion, the container row gridlock.

Exactly. That's something that Victor primarily, and I think also Tiberiu for a big part have been working on since quite a while. I'm not sure. We already have a grid block, I think as an add-on. It's not in Volto Core yet as far as I'm aware. The grid block was a

great addition already to Volto because that's what it says. It allows you to create grids and deviate from this standard one column layout that we have. Now the plan is to take

that thing even further and create more complex grid-like layouts that also support rows and therefore make responsiveness way more easy. I've not been that long in the Plone community

yet, but I suppose it might be a little bit similar to Mosaic. I'm not sure, maybe Fred. Yeah, we've had a lot of composite page editors as I called them after a while. We did a podcast

on them somewhere last year where we discussed 4 or 5. Indeed, Mosaic was one of them. Volto has this vertical storyline within the blocks layout and the grid block, but also other add-on blocks that have been created before the last three years can allow you to go sideways

or do indeed more interesting things or insert whole grids and change things there. That's one big topic. Another thing I saw coming back from Plone 6.1 is the Quanta toolbar. Quanta was already something that Victor as the Volto release manager already presented one or two conferences ago. I think at the first discussion there was already in 2021.

He presented much more at the conference in Namur. What I see now is that at least part of the Quanta experience, the toolbar is also aimed to hopefully arrive already in Plone 6.1, which needs some work. And then the big Quanta stuff, the whole picture will hopefully be a part of

Plone 7. Exactly. As you mentioned, Quanta is the whole new theming story, complete rework of the Plone front-end theme made by Albert... What's his last name?

Casado, from my heart. But... Casado. Casado. Casado. Yeah. Actually, a great thing is that he'll actually be around for the sprint. Oh, cool.

We haven't seen him in quite a while, because he's a busy person. But we managed for Beethoven's sprint, because we really want to push not only the development side, but also strategic planning and the overall layout discussion. We actually invited Irina Escudé, who also worked for a

bit on Volto, as far as I'm aware, and Albert Casado, who was the original creator of Pasta Naga UI, which is the basic theme that we use for current Volto. And also Quanta, which is really exciting to get a complete whole new theming story, way more streamlined in there.

So then we have like two big ones. Well, another one I really look forward to is the Plone Distributions, which we started in Innsbruck, because I think that Beethoven is like the second

in-year big strategic sprint. We had the first one in Innsbruck in February, where also a lot of work was already done on Volto, like the teaser block that got merged into the Plone 6-0 series. So Plone Distributions will be part of the story. How can we indeed create also Volto distributions, for example, for demo sites and for other stuff set up? Can you mention some other

things that people have already given you information they want to work on? Let me have a quick look at our list. I think we already went over the big points. One thing that we

always need to mention is sprints are not only for development and talking, but also documentation, documentation, documentation. Steve already added himself to the list of remote sprinters. And as we all know, yeah, we'll do our best to kick our asses to get the documentation and

training part progressed. So we'll definitely plan to work on that as well. Then there is the upcoming Google Summer of Code this year. We have quite a few projects proposed

for Plone. And I think at the sprint, yeah, we'll take first steps to get them going. I'm not sure about the deadlines and schedule there, if we'll already have like the final

selection of candidates by the sprint. I think so. There's very some interesting topic for Google Summer of Code, like modernizing the data fetching API I see here. Now Volto is tied to using Redox, which was started at the beginning. And this is what I understand. I'm not an expert

here as well, but it is an alternative or a more flexible generic way instead of using Redox technology. Yeah, exactly. Wait a sec. What was it called? Yeah, I forgot the name. I have to click the link.

Me as well, but there's better stuff. Give me three seconds. I'll figure it out. Well, another, I'll talk about another GZOC one. Indeed, React moved already some years ago to move to functional components instead of the class-based components. And that's also a Google

Summer of Code subject that will probably also be touched at the sprint. And as you said, Jacob, it's documentation, documentation, documentation, but it's also documentation about our roadmap, which will be another important sprint topic in May in the Beethoven sprint, getting our roadmap

freshed up, getting indeed people talking about what should be in Plone 6.1, should there be a Plone 6.2, and indeed what you said before, Plone 7, will it be 24, 25? So those things are indeed stuff that we normally, it's coding and it's documenting and it's designing small things,

but these statistical things happen at sprints like the Beethoven sprint. Exactly. I mean, it's always better to take those decisions in person than only remote. So always lovely to meet up as people.

And as we found out the hard way doing these kinds of discussions, remote only is also very tough. We had almost pretty much two years of that already. So to mention a few other topics

that people want to work on, there's talk about the relation control panel, which is already in the Plone 6 classic UI one, but since a lot of control panels are automatically converted and available in the Volta front end, but if there's special UX on the screens, you need to do extra work. So the relations control panel will need some love for that to work. People want to

work on improving drag and drop support, site maps. If you start doing really large websites, like you have with some customers at concept that are really large intranets, research portals, and other publication sites for really big institutions, then your site map is breaking

down. So also I've heard, so that's indeed something that has to be worked on to allow very large sites to have a representative site map. I mean, that's what's Plone tailored for big sites, right? Yeah. That's also what we need to support, but you only find the education if you start using them. And very interesting topic I also saw here. Yeah. A better image upload

widgets. Yeah. I mean, I more or less implemented that in Innsbruck already based on code from

Victor into Tiberio, I think. But that still needs some parliament. Yeah. A little bit more love. I have a little bit of a problem that I like to do stuff on sprints and then it's like 90% finished. And then I get home and I don't, you know, you know that really you don't find

the time to actually sit down again and finish it properly. So thank you for your confession. So there are 29 other people at the sprint that know that you're going to finish that image upload widget in May. I mean, I could also just maybe try to get it done before and surprise everyone.

That's safer. That's safer. Yeah. So you mentioned remote. Steve will be sprinting remote. Others will be sprinting remote as well. It will be very busy. Exactly. I think at the time of recording, we're pretty much booked out already. We have about 30 participants and are really

like in a rush to somehow organize some more space around our office. Because for those of you who already have been there, it's not huge. It's a fine office for a company like a concept with

also people working remote. But indeed, if you start to organize and people come, then it's and you have to find a space. I know you've done a lot of effort to search for more space in the surroundings, ask around at the university or other. But it's really difficult. At the moment, we didn't have luck with that yet. Current planners because we have a lovely garden up on

next to our office. If we have good weather, we'll just do most of the sprinting outside. And currently, we're preparing like a big tent as a backup for the garden. So that will hopefully work out. I know we're a lovely community but does not need to get

too cuddly in there. No, no, no. Last year, the garden was great. But indeed, we were lucky with the weather. So plan B to have a tent indeed for backup sounds like a plan because then we can really use the space and be with 30 people there. But indeed, unfortunately,

it will be very difficult more. So remote sprinting is possible. And knowing from your equipment and the motivation there, we will do our best to accommodate remote splinters as much as possible. Absolutely. So yeah, if you still want to take part in the sprint and

yeah, want to contribute to the further Chrome development, feel free to just approach me or any other of the sprint organizers, namely Timo, and ask to be put on the list for remote splinters.

I think most of the remote stuff will happen via Discord during the sprint. If there are any changes, we'll let you know in advance. Yeah, we'll have daily stand-ups, daily wrap-ups, depending on your time zone. And we'll try to have people also online monitoring the channels

and grabbing people if there's a question from a remote sprinter or the other way around. Indeed, indeed. My idea was maybe to pick one or two people from the organizer's team who will regularly check if everything's all right with remote sprinters so no one

feels left alone somewhere. Also, yeah, what I wanted to mention, it's not really the first time that we have plenty of remote sprinters because I think it was the last sprint that was

last year with the people in Bucharest sprinting as well. So we had a double sprint in Bond, Bucharest. Yes, that's the AutoWeb office in Bucharest, the second one. Yes, we had it on the last TV. After a while, those sprints start to...

That was only last year. Yeah, therefore, we already have quite some experience because then the sprint is completely split up between two locations. It's half remote for each half anyways. Okay, so wrap-up, I think. I guess so.

Bed-over sprint, May 18th, May 15th, and I should be... May 15th, Monday is the traveling day, right? So the sprint, the full thing starts at Tuesday and people can start and mingle and arrive on Monday. Anyone who gets there on Monday can already start. We'll be around

at the office. I plan to travel on Monday, but the first stand-up and the real big planning, I think, will then be done on Tuesday morning. I guess so, yeah. Yeah, yeah. All right. So to you, last words as the organizer.

Usually, I'd say please all come and attend, but as mentioned, we are already quite packed, but please join us online and maybe we'll be the biggest sprint in Flown history. Probably not because they're like conference sprints. Yeah, that's hard to beat a conference

sprint like, for example, Van der Muur, but one of the strategic sprints, Beethoven, has been very important and will be very important. If you look now at the subjects, it's certainly something not to miss, either on-site, live, or joining us remotely from May 15th to May 19th. Okay, Jacob, thank you so much for presenting,

for talking about the sprint, and see you there next month. Yeah, see you there. Yeah, see you next. Bye-bye. Bye. And people, have a nice World Plone Day.