Sloan Foundation membership annual meeting 2022. After two years doing that online, we are kind of rusty, so please bear with us. First thing I would like to know, who here is already a Foundation member? Raise your hands.

Okay, please pay attention, look at the other faces. Okay, so the rules in here are simple. If you're not a Foundation member, you can watch, you can ask questions, but you cannot make motions or vote.

If you're a Foundation member, you can make motions, and we need you to make motions at some point. And if we have any vote, we invite you to vote.

So for the last year at the Sloan Conference 2021, the mixed version with part of us in Sorrento part online, we elected a board of directors. I am Eric Andre, I'm the president. Jens Klein, vice president. Kim Paulus, board member. Paul Goulans, board member.

Victor Fernando de Alba, Josh. Andy, introduce yourself. Hey, I'm Andy Lieb, secretary this year. This is the second year that I was actually secretary of the plan board.

And we also have William, that's not on the call yet. And we have a non -voting board member that's Beth Smith. Thank you for all the hard work during this year.

Some board members were also part of other teams, and some had official positions. Jens was liaison to the security team. William was the liaison to the marketing team, and Victor was the liaison to the voting team, even though that sounds strange, right?

In the beginning of the year, we decided on some priorities, and I should have tested that before. Okay, we decided for five priorities. First, communication, addressing all Plone audience, not only developers. Second, embrace hybrid model for all gatherings, meetups, springs, and the conference, and I believe we can see that.

Improve and enhance documentation and marketing positioning of the Plone CMS. And again, I'm going to ask for a round of applause to Steve Purce, Katia, and to Rico Peca. I cannot see anyone in here, please.

A round of applause. And then nurture new participation leadership in the community. And I really hope this works. Okay. And contributor agreement modernization via the adoption of digital signature. We are almost there.

We promise this is going to become a reality pretty soon. We had the membership committee this year. Victor, can you talk a bit about that? Yes, although I haven't prepared anything. But how many members do we have in here this year?

Yeah, we have, I think, four plus three plus three, which is eight, yes.

And we have Alessandro Pisa from Italy, Giulia Giussini, Italy, York, Germany, Lucas Aquino, Brazil, Marcus Hilber, Austria. Michael McFaren, United States, Nilesh Gulia, India, Piernicoli, Italy, Raffaella Vazanella, Brazil, and Stefano Marchetti from Italy.

If you're here, please stand up. Again, there are more of you. One important thing is anyone can nominate themselves to be a Plone Foundation member.

Being a Foundation member is a recognition for all the work you did to the community over the years. That's important. Also, you help us define the future of the community, the future of the Foundation, and it's not related to code. Meaning, if you have access to collective, you're a core developer, and so on and so forth, you're not a Foundation member yet.

But that's an easy path to join. Every year, we renew the membership committee to have new people coming and to do the evaluation of the new applications.

I would like to thank Victor for this amazing year and a key ingredient because I believe it was the first time in a long time we had that many new members. Thank you. We also have this year 43 new contributors. Thank you all. We're not going to name them all.

Yeah, it's 42. 43 in here. Oh yeah, sorry. We need to start counting from zero like normal human beings.

So, the number is 42. Yeah. Also, if someone in your organization works with Plon, please ask them to sign the contributor agreement and help us to make the future of Plon a reality.

We are always looking for new contributors, people that can join us, because in a few years they're going to become Tiberiu and going to commit like crazy and we can rest for a while. Also, we had some Plon events this year. We had two strategic sprints funded.

It was the Beethoven sprint in May. It was a two-city sprint. It happened in Bonn and Bucharest. We had more than, I do not remember the number now, 20 something people there. It was good. It moved lots of things.

Some of us were there. And we also had a Bucharest sprint. It was also in May. It was a week apart from the Beethoven sprint.

Also an initiative. Thank you, Johannes. And these sprints are the ones that the foundation invests money. We publicize more to get as many core developers as we can to move Plon ahead. Want to say something?

I think it's very important to have the strategic sprints and I encourage everyone who thinks about doing a sprint. It's not that much work to organize like a symposium or a conference. It's easy if you have a room, if you get to get people together.

We as a foundation really like to spend money on this to see Plon getting forward. We also support the organization of the Plon Conference 2022. This is something we start doing over the Covid period and help a lot the organizers.

If it's a big if, we announce the next Plon Conference today. It's a if. They are going to have the support from the Plon Foundation. That's important for any other organization that wants to host a Plon Conference and they're like I never did and so on.

There's always a team of people that this year, this team was led by Kim Nghuyen. Thank you, Kim. No, the foundation part. Of course, we had Joel and Martin organizing the conference. They had lots of meetings with us.

Thank you all for organizing this amazing conference. So whoever wants to organize a conference, you have our support.

It also applies to other things, other events. We did lots of evangelism and outreach this year, even considering we came from two years of lockdown and working from home and getting to know each other's place through Zoom.

At this term, we sponsor Open Source Week. It was an event that was organized by Red Turtle in Italy. We sponsored the event to promote Plon in Italy. We also sponsored the Python Web Conference. In March, it was an online event.

I see some familiar faces that were speakers there. We had Plon talks there. We sponsor Engitech, that's a gathering of a sub-community of Plon that works with the legislative branch of Power in Brazil.

We also sponsor and continue to support CMS Garden. I would like to publicly acknowledge the work that Mike has been doing with CMS Garden since a long time. Thank you, Mike. And if you want your local event that's related to Plon or could help us reach a new audience for Plon, please ask for sponsorship.

If it's not related to Plon, it's hard, but take every opportunity you can to

go there and speak and go to your local Python group, Python conference and so on. We had other initiatives. We had World Plon Day 2022. Many cities organized their own smaller events, and we have the coordination from the marketing team led by Hikupeka online.

So we generated more than 24 hours, a little bit less than 24 hours of new video content to Plon.org. Again, I would like to thank and ask for a round of applause to Red Turtle that hosted the most viewed event online.

They had at some point more than 50 or 60 people watching online the event, and they had that for three hours. Again, someone from Red Turtle here. Oh, yeah. Thank you.

We are going to have World Plon Day again next year. More opportunities. We also had the Plon 6 zero adopting meetings, regular, all the classic UI sprints that happen every Wednesday. We had some Plon gov BR online events. Let me see in here. Two series of videos, and we had my favorite Plon moment.

That's the Plon newsroom. Thank you, Phillip. Thank you, Fred. You see, I say or I speak your names all the time. And we also had a second season of the Plon podcast led by our King Niguyen.

Thank you all. Also for sprints, we had the classic UI sprints. It was always nice living in a different time zone, wake up and see that people are talking about Plon for hours already.

Regular zoop sprints, Plon 6, micro sprints, Plon.org sprints, mosaic upgrade sprints and Cerrado sprint in Brazil. That was mostly to create a Plon.org.br and translate Plon to Portuguese.

Also, let's talk a bit about sponsorship. We had Fuvio leading the efforts to get sponsors and maintain our sponsors for the Plon Foundation. This was now transition to King Niguyen. This year's sponsors were Premium Level, Enfold, Emio, Jaskarta, Six Feet Up and Soliton Consulting. Round of applause for them. Thank you.

Standard sponsor, Agile Coach, Cloud 19, Des, Lotte & Vache, Otherweb, Made2Clean, Red Turtle and Zopix.

Thank you all for your continued support. Was the spelling okay for the Dutch one? Des, Lotte, okay. Oh, good. Oh, thank you. And there's something else here at some point. Maybe? Somewhere? Let me reduce here.

There's one thing. Okay, better. And also, we'd like to thank the Plon Foundation Heroes. They are not companies but persons that donate to Plon this year.

So, Cohea Baylor, Eric Steele, Eric O'Andre, Franco Pellegrini, Ian Dodson, Luca Zacchino, Nicolas Zambello, Paul Ruhland, Rico Peko-Xanning and King Niguyen.

So, round of applause. One thing here. Now we are transitioning the heroes, Plon Foundation Heroes to GitHub sponsorship. So, if you have $5 to spare every month, go there. If you don't and you want to pay as a coffee, donate $10, go there. Do it.

It's quite simple and Paul was in charge of making that happen and doing all the paperwork and understanding the US legal and finance system.

Thank you for that, Paul. And one last topic. We had the nominations open for the new Plon Foundation board. We had seven candidates to seven positions, so we do not have an election this year.

We want to see an election next year. Who did not talk yet? Everyone in here. Andy? No, it's bad for him to talk from there. So, Paul, what are the requirements to be part of the Plon Foundation board?

You have to have an interest to be on the Plon Foundation board. There are no further requirements. You don't need to be a foundation member. Actually, serving on the board is an excellent way of being or contributing and that is seen as a valid contribution to become a foundation member.

But there's no prior requirements other than that you solemnly swear to uphold, to be at the meetings and be in contact with the community. But that's about it. We practically, yeah, we meet every two weeks online.

There is a tradition that it's on Thursdays. But if people are from other time zones, we are perfectly willing to adapt the timing for that. But at the moment, yeah, it's on Thursday evenings for Europe and Thursday afternoons for the US.

But there are no further requirements. You have to learn a few rules. There is like this strange speak of Robert's rules that because we are an American, or yeah, we are an American legal organization.

So you have to do motions with... Actually, I believe we could have a tutorial later on. You're going to learn is really hard. The first time you do that in a public space, people look at you like, what?

So this is it. We had seven nominations. So Ericko, Jens, Kim, Martin Peters, Kim Higuain and William Fenny.

So first thing I would like to do the traditional thing. First of all, thank Victor for all the years on the board, all the hard work. We hope to see you in the board again.

Thanks a lot. It's been an amazing seven years and really changed a lot and a game changer for me. Thanks a lot. And I would like to ask Andy to say a few words.

Yeah, it's you, Andy. Oh, hey. Yeah, this is the last term of the board that I'm probably going to serve. And I just wanted to say that having this meeting every two weeks has actually been such a delight, particularly through the tough times of COVID,

where it was a joy to be able to speak to friends about something that we all care so deeply about. So I would recommend to everyone that if you like talking about clone and related technologies and the people in the community,

that's so special here that you consider running for the board at some time in the future. Thank you, Andy. And now we are going to invite the two new board members to the table.

Again, thank you, Victor. Oh, yeah. And now it's the tutorial moment. So wait a sec. They're going to sit in here unless someone has something really against you. I don't know. Oh, OK.

So we need someone that's a foundation member to make a motion to approve the new board for the 2022 2023 term. Oh, yes. We need someone to second. So, Alexander, second. And now it's the moment you've been all waiting for.

Yeah. So as before, only foundation members can vote. So we're going to ask all in favor, say aye. And then if you are in favor of the motion, you say aye. Don't ask me why. Ask Mr. Robert. It's his rules. And then we're going to ask any opposed say nay.

And if you think like these bunch of clowns know never, then you say nay. And then we're going to ask if there are any abstentions. And if you abstain, you also have to say or you have to raise your hands. So that's the ritual, basically. And if it's too close to call, we will do a headcount.

Otherwise, it's a visual count or an audible count, more or less. And by the objections, if you have very strong objections, you can and then we can have a discussion. Exactly. So let's start. All in favor, say aye. Aye. Any opposed say nay.

Any abstention. So motion passes. This is the board for the next term. William is not here, but he's part of this new board.

And now we open for any additional questions or any additional motions. Anyone wants to ask something? Anyone? Anyone else?

Oh, alrighty, man. Oh, pulling a short. Pulling a short. Yes, man. We are in video. We need to explain that later. So, Philip, motion to adjourn the meeting. Do we have a second?

Oh, Alessandro Pisa was also like this. So let's give to Eric because... No. Alessandro, second. All in favor, say aye. Aye. Any opposed say nay. Any abstention? And that's a wrap. Thank you all.

Yay. Thank you. Thank you all for the trust. And now we have some extra time. Please remember at five o'clock there is everybody's favorite time of the day, namely lightning talks.

I want to ask something else to all Foundation members that are here. Please answer the Plan Foundation census. And William, Franco, and there's somebody else, please don't answer again. Because I see familiar faces that, oh, you need to... Oh, I'm going to do...

And then I see Franco going there every time and we know. Where is this? I'm going to send a link. Actually, as far as I know, at least people are answering the same way twice or three times. So it's fine. No one has a different view from one week to the other.

What? Oh, the next event, if we know. Yeah, if we know that. Nobody knows.

And actually, there's still time. If you want to organize, you have a few minutes to allow us. Man, I already told you, I don't know. No, there will be a closing session after lightning talks and that is traditionally the moment where also the next one is announced. There's no arguing with tradition. Bye, Andy. Yeah, Andy's there. He's saying bye.

Bye, everybody. Bye, Andy. Since we have some time, I thought we'd just do the sprint announcements now so we don't have more time for the lightning talks. So if we have additional minutes. Okay. Yeah. Come again? Sure. Enjoy that.

What's happening here? How do I stop?

So if you are a sprint topic leader, I'll ask you to come up to the stage and quickly introduce your topic. But first, some organizational stuff about the sprint. So sprints are Saturday and Sunday. Different from like other conferences, the sprint location is not here. It's not near here.

It's about a half hour bus ride. Getting there by public bus is not really easy. It's probably doable or having a cab is also doable. Yes. Yeah. Sorry.

But the one on Plonkonf is right. Why did you click on the link to the same document that you were already looking at?

That link is correct. Okay. That link is just wrong. I'll just delete it. Sorry. Good. Thank you. Still, I wonder. Okay.

So the link, if you ever wonder, the link is in the schedule, sprint. There's this and there's also some minimal information. I'll add some more. So since the sprint location is not here and not near here, it's half an hour bus ride. As I said, there's going to be a bus organized for all the sprinters.

But to figure out if the bus is big enough or if we need a whole fleet of buses, we'll need to know how many people will actually come to the sprint. So I'm going to ask for a show of hands who will be at the sprint tomorrow. That is Saturday. Hands up.

Okay. Can someone approximately count that? 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 29, 30. So probably 30 people so that you know that maybe 5 more.

I don't know some people who are running around. So that was Saturday. I'm not asking for Sunday now. First of all, because you have your travel planning to do. The bus leaves at 9 o'clock, at 9.30 in the morning near the Hotel Ibis.

It's not far from here so we are here. Teatro, no, that's actually not here but we are close to here. And the bus is here and the Hotel Ibis where a lot of people are staying, I know not everyone is staying here, is here. So it's like, it's not far away. So that is where you need to be at 9.30 in the morning.

We can have a discussion so this is not a board meeting. Nobody can pull us short. If someone says this is non-human, we should do this at 10 o'clock. That's okay but 9.30 I think is doable. Is that okay?

Hi, thank you. Okay, we'll do that at 9.30. We'll leave at the Sprint location which is the office of Immio which graciously offered their own offices at 6 o'clock. So we'll be here after like 6.30 in time for walking around, going back to the office, having beers and drinks.

So Sunday the same thing will happen but I know a lot of people will have to leave on Sunday, including me. So I'll ask again. Okay, additional information. There is going to be a couple of cars. That's not a fleet of cars. But if people need to leave, say, Sunday 3 o'clock,

they need to be at the train station in Namur or somewhere else, that is okay. We can manage that depending on how many people are there. So that needs that. So please add your name here and say I need to be in Namur at 3 o'clock, for example. Then we can manage transport there

because it wouldn't make sense to do the bus thing. So saying that, who's going to come on Sunday morning 9 o'clock to the Sprint? 9 o'clock, 9.30 to the Sprint. Hands up now. Considerably less. One, two, three, four, five.

That is very few people. Six. TBRU, I saw you. So that's Sunday. That's going to be a slow spring. Not a problem.

So that you know about catering and stuff. You don't have to add your name if you attend and your numbers since we know them now approximately at least. So probably on Sunday maybe we don't do a bus but just a couple of private cars. I don't know. You just decide that. Okay. Having said that, what is a Sprint?

Hands up if you've never been to a Sprint but are coming on Saturday. That's cool. You've never been to a Sprint? That doesn't make sense. Yes, I will.

Yeah, he's coming. TBRU. Yeah, yeah, I will. So a Sprint is a collaborative effort to improve Plone in any way possible. So by collaborative that's the key word here. You don't work alone unless you really want to. But you don't work alone and don't have like only a core developer here,

a core developer here and the newbie is all there and there. That doesn't work like that. Pair up with someone who is maybe more experienced than you or knows something that you don't know, has an editor that you might want to learn about, showed something during a talk that you want to learn about.

Leave your comfort zone because these people are friendly and that is the perfect place to learn stuff. So that is a very strong wish that we have and it's a perfect opportunity to actually do that. So pick a topic.

I know we always have stuff that we need to have finished because the release is coming up but it would be great if not everyone works on the things that he's always working on. Broaden your horizon. If you're not a developer you're very welcome to join the Sprint anyway.

As I said, in any way possible. Translations, user testing, accessibility testing, speed testing. You can do that in your browser without any additional skills. Documentation, that's like topic number one anyway. Marketing, everything that helps improve Plone is welcome.

Even like coming there and ranting about things that are bad so we can find out how to improve them. So that being said, Steve can you say just very quickly what the main topics about documentation are?

We have a bunch of little ones but the big ones that we really want to get done are just releasing Plone 6 docs so that instead of typing 6.dev we just go to

docs.plone.org and you get version 6 docs. We want to also start using years in the training docs so that we don't have trainings that are just obsolete and no longer work. We'll archive those but we'll still be able to get to those.

Decommissioning the Hego site which is like a splash page that nobody really updates anymore. And then have the training site have its own homepage.

And updating the critical pieces of installation, maintaining and employing Plone 6. We have a really excellent base but it could use some user testing so if you wanted to kick the tires on that documentation we'd really appreciate it. And I think those are the big ones.

We have a whole big huge list of issues on the project board. Most of those are porting already converted to Mist. Syntax the 5.2 documentation and so that step's already been done.

We just need to have people curate it and move it over into the 6 branch and then release it. Thank you, Steve. Hand that over to Mikkel. Don't give it to Mikkel because he's leaving. But he is available online to help you when you want to do translations.

So we still have a couple of languages that are less than perfect coverage wise. So doing that is rather easy if you speak English and the target language. So do that.

Then marketing. Riku Pekka, do you want to say a couple of words? Thanks. And like a great leader I will leave the sprint early but leave others to do the work. But fortunately there is something already planned out if I show it here.

So two things or maybe three things. There is a technical side. So other one is Plone.org of course to build it and there is the technical side. If someone can get me a running Plone 6 site with the theme that was already built that would be really amazing. So that's one thing that if someone can help.

And then there's also lots of content work. And if you haven't been following the little details of the Plone.org renewal, there is the earliest print documentations and this mural design which you should definitely check out and see what kind of stuff there already is in place and what kind of thinking behind the new site.

And then there are a couple of other content things that you can go through and maybe help with. And yeah, marketing Plone 6, that's part of the Plone.org renewal. But if you can think about things and there are a list of things that you can actually do if you have the time.

And thanks to all the participants tomorrow that are actually here doing the job. So thank you.

We have a bunch of things we have talked during the Volta Team meeting. Three that I would personally like to see happen. And they are quite attainable for the duration of the sprint.

And tomorrow we can take a look. These are the drag and drop support for nested blocks. The other is the teaser block. And the third one is the column row groups block. And yeah, oh, someone, there's not, POC typing multiple stashes.

Oh, okay, Michael, you have said that. Yeah, okay, that's another nice thing to take a look at. Yeah, for the first three ones, there are already, there is already a PR. There are already PRs, right?

And someone can take over because the job has already been started. There's another great topic that is Plone.org, the front end part, that there is another big one. So probably we will need blocks, we will need things there.

If anybody, yeah, I guess that tomorrow we will take a look at everything that is missing. All right. Practical joking here. Add-ons, I added that, I'm not going to work on that unless, just putting that out, if someone has an add-on that he's using in 5.2, for example, but he wants to have working in 6.

Me and others are available to help you. There are not many things you have to do unless you have a lot of JavaScript stuff then Alin, Hannes or others can help, since he just had to do that chore, Alin, I mean.

Next one, David, do you want something about the test, say something about testing?

Next is Mockup. Hannes, are you there? I just saw you, but there you are.

Can you switch on the mic for Hannes? Is it? Mockup, the JavaScript stack of Plone, many tests are failing here, so that is one part which I want to work on.

And also Frank recently just said that the cache groups for the chunks could be optimized because currently when you load 10 EMCs, a lot of small files are downloaded, instead could be optimized and we for sure find something else. Also the documentation is something, I added that point to the documentation group.

And yeah, I think it helps. Okay, Alexander, do you want to say something about Zope and Plone security packages? Where are you? I can't see you. Thanks. Yeah, there are still some of the packages in the Zope Foundation that for some other projects are necessary

that are still not ported to Python 3 fully, so there are some open pull requests, some work to do on it, working on that. Also preparing restricted Python for the Python 3.11 support, so that we can go on that.

And then there are some config scripts in the Zope Foundation that they apply now to all Zope Foundation packages for some more convenient way that all packages act the same on testing, linting and so on.

So we're working on that. Cool. Just to put that out, since this is not, hey Alexander is working on that, so that's going to be fixed. Sorry, this is basically a cry for help. Not specifically from him, but join him and Hannes and David and everyone else on this topic if you're interested.

Even if you're totally new to that, I'm certain you're going to learn something. Flip, you want to say something about Volto speedrun upgrade, please? Yes, this is basically a real world example of getting a non-profit put onto Volto.

We are actually at 527, maybe even 528 Python 3, and I would like to see how fast you can take from there to Volto. And bring some input back into maybe quick install processes for other people to share that.

Please also the migration process. No, I do migration-less stuff. I just slap stuff together. It says right there, technical debt, you just have to document it. So this is actually truly a speedrun. This is, you know, we will take on as much debt as possible to get this done.

And I want to see what happens. Yes, we can migrate if you want, but there is nothing to migrate. Rich text? You don't use rich text? We don't, maybe we do. Do you use links and images? We use images, we use links.

Then we have something to migrate, yes. Thank you, Philip, for offering to help migrate this site. I'll show you where the button is. So, Volto seamless mode. John. Thank you, yeah. So this is a thing I've been working on a little bit with Tiberiu.

So it's just to get multiple hosts running through the same Volto instance, so a bit like VHM in Plone. So if you've got the same code base that you want to run on multiple sites, that's the way it's going to work. Proof of concept is kind of working. There's lots of little fixes to be done.

There's a bunch of places in Volto that's using sort of the old way that we'll need to migrate across. It needs to be tested properly, and yeah, we need to do some load testing on it. So, yeah, that's it. Thank you. Great. Last but not least. No, not last, sorry. Mike.

Yeah, I will probably either work a bit on pop templates for REST API serializer. I started there a while ago. I need to finish that up. Maybe even some mosaic tile support, whatever. I'm not 100% sure, or just cleaning up existing tiles.

So if anybody wants to improve pop templates or Plone CLI, join me. Good. So I'll be working on buildout. Moritz has submitted a PR and he cannot run the test, almost.

So which means documentation needs to be written that I plan to do and that we can work on together. How to run the test suite of buildout and hopefully accept Moritz pull request. So it will be work on buildout so that we can eventually get a 3.0 without any RC.

Thank you. So thanks for all these interesting topics. Remember, we meet at 9.30 where the blue sign is floating in the air. There's not going to be a blue sign. Just imagine that next to the Pizza Hut for breakfast.

Okay. We have a 15-minute break to get coffee and I don't know whatever and then we do the lighting talks, I guess. Thank you.