Aug 25, 2026 @ 15h UTC
Attending: Guido, Tania, Astrid, Rikupekka, Armin, Brian
Items from last meeting:
- next.plone.org
- Update: Idea: to run old and new simultaneously with redirect magic -> could be done but does not “spark joy”. Or to publish version 1 first that has case study content type, but not all the new content types? Discuss further at next week's next.plone.org meeting.
- Erico is working on the super content type - id.plone.org. Should help a lot with wider Admin and Infrastructure stuff once implemented. Adding this work to the current STA fund application.
- Something for ploneconf goodie bag? Showed mockup.
- Stats on current plone.org -> significant rise on site visitors from 2024 to 2026
- Case studies to be added to current plone.org: continue adding eg Did we just make the fastest Plone site?
- Community recognition - waiting for footer layout from CR team.
- Ploneconf update: Come on buy your tickets now. Confirmed keynote. Pushing hard on local reachout. Foundation Member meeting scheduling discussed. Asked for quick tutorial on how tech event content type works.
- Sovereign Tech agency: at point of adding PLIPS/pieces of work to add to the list and connect to hrs (and euros) - in last stretch of the application.
- Mack has sent Nick case study/studies. Who feels like tackling this? See email.
- Buzzsprout mothballing/cancellation - no movement
- Tune Up Day: 21 Aug - recap: was ok. Next is on 18 Sept, just before PloneConf
- AMA with Plone Conference organizers - on YouTube - like, comment, subscribe, rewatch.
- FrOSCon was last weekend.
- Google analytics vs Matomo - how about a talk on this in future? Have a look at Matomo stats in general. Security issue sent to security team.
- A reusable “Plone Conference 2026 Story Engine” (Armin) - in a gitlab repo. - A story about the story to create stories from stories in the ploneconference repo as PR#106. The 10 story posts were merged in conf repo by Guido.
- Recommendation: How to be notified of all @PloneCMS posts: Linkedin has a bell icon under the banner at top right of an organisation or member. Make sure you hit the bell and choose “always” for notification under @PloneCMS to avoid missing any posts to like, share, repost or the best: actively comment under the post or as commented reposting. Interact with people interacting with the posts. Draw questions, suck them in (this increases relevance in their circles of followers to make the interaction show up. Not “because of the algorithm”, but because of “relevance” for the “audience” – This is what the algorithm is (or should be) after. Other bells are better known (the youtube bell!). Share your knowledge for other media with the team. Mention the bell in your engagement posts, and suggested wording (example, please improve and vary): “Do you want to make sure you do not miss any stories why digital sovereignty using Plone saved businesses and organisations all over the world over decades? After following the profile of @Plone CMS – better hit the linkedin bell at the top right under the banner image that now shows up and make sure you choose “always” to see EVERY post, not only what Linkedin decides.
New items:
- Discord - how about a channel for editors? (See Maira’s query, which is very editor specific). Coffee bar-like
- Discord channels for Plone Conf 2026 need some cleanup
- Accessibility team for Volto. Wagner & Brian. Also submitting workpackage for STA fund application. Suggestion to have an AMA with Wagner, Brian and others (Karel) about accessibility
Thanks all!
Meeting ends: 16:08h UTC
Next meeting: 8 Sept 2026 @14h UTC