Participants:
- Maik Derstappen
- Jan Buruck
- Jens Klein
- Fred van Dijk
- Maurits van Rees
- Peter Mathis
- Johannes Raggam
- Philip Bauer
- Steve Piercy
- Gil Forcada Codinachs
Meeting leads: Jens, Fred, Maurits
Notes: Fred, Steve, Jens
Topics
- Agenda & purpose
- Short meeting
- 2nd ClassicUI Meeting of 2025, held at the Alpine City Sprint (Steve joins remote), more subjects to cover this afternoon.
- Lets disuss possible Classic-UI PLIPs in more detail tomorrow in a separate meeting
- Plone Version Planning 2025
- 6.2 / 7.0 first ideas/planning from our Release Manager for 2025?:
- main topics so far for ClassicUI/backend: templates and native namspaces
- 6.2 alpha ready around May
- 6.2 beta/RC before summer
- 6.2 Final autumnn / before the config
- Welcome Gil ! (Gil arrived at the sprint location)
- Where to post minutes
- post on community.plone.org Minutes of Teams and Foundation Board - Plone Community
at some point in time Board decided to want teams report there (IIRC, Jens) - archive on docs.google.com workspace ploneorg
- post on community.plone.org Minutes of Teams and Foundation Board - Plone Community
- ClassicUI Team lead
- We need a team lead for the represention of our interests in the Plone Communty development Process. We don't need the frequency and scope of current Volto development, but need representation for plips/roadmap and releases. Volunteers for 2025?
- Maik Derstappen
- deputy/support teamlead: Fred van Dijk
- Generic Project management GitHub
- Problem: Plone Contribution avalanche
- AI-generated contributions take too much time from devs to detect and clean up.
- Probably a misunderstanding of the Volto Team on how we want contributors coming in somwhere else than 'contributors team', but let us flesh out the problems first.
- Problem Online first, which Fred brought up, vs. past were contributors where most Offline (sprint/Conf) first.
- First define the problem, the proposal below do not do that, which we need to improve.
We may have more possible solutions than those, probably better.
Usage of orga-membership as status symbol is a problem. - Proposal to remove the Plone GitHub Team Contributors. Request access, if needed.
- Proposal for How to Become a Volto Team member. This could be used as a template for other teams and possibly the Plone GitHub organization.
- There is also prior art on the Collective GitHub organisation. Aplicants need to provide their stake in a issue request before getting access to the Collective with a number of questions. This stopped most of unjust applications.
Fred discusses how the Volto Team does project management. The Volto Team drove the Plone 7 Road Map document, and sought and incorporated feedback. There is now a PLIP in Volto for "Seven" for the next generation of Volto with dozens of sub-issues as PLIP tasks.
When the Plone Foundation funds sprints, it's reasonable that the Plone Foundation advances Plone in a more strategic (directive) manner. Higher or maximum amounts of funding will in the future likely be provided only to sprints that plan to do significant work on strategic PLIPs.
Sprint funding requests can still be done and granted in smaller amounts to promote Plone and the community. However, with limited funds available these requests will likely be weighed by the Foundation board against already planned strategic sprints. This is still in consideration by the Board.
WVTTK - (What further comes to the table, open quick round before we close a meeting)
- PLIP meeting tomorrow, at least 60 minute available time, at the Alpine City Sprint, too big subject for now.
Closed meeting at 14:10