Volto Team meeting notes 2025-01-28

Announcements Minutes of Teams and Foundation Board
1

Volto Team meeting notes 2025-01-28

Attendees

  • Steve Piercy
  • Timo Stollenwerk
  • Alok Kumar
  • Nilesh
  • David Ichim
  • Jakob
  • Dylan
  • Victor
  • Jefferson
  • Mikel Larreategi

Housekeeping

  • Designate Note Taker - @stevepiercy
  • Designate Time Keeper - @djay (@stevepiercy as backup)
  • Review agenda topics, presenters, and timings - @timekeeper

Agenda/Notes

Old Business

These items are updates from previous meetings. Usually they are information only, and don’t require further discussion. Occasionally they may require further discussion and clarification.

  1. Copyright Infringement Investigation - @stevepiercy - Information

    1. This was submitted to the Board, which met on Thu, Jan 23, 2025. They will handle communications with the affected parties.

  2. Proposal to remove the Plone GitHub organization Contributors Team - @stevepiercy - Information

    1. https://docs.google.com/document/d/1x60efw5mReIHeIrTf8vI2vf2n_4Jggj17yYBAGd9pBU/edit?tab=t.0
    2. Please ask for access to review, and I will grant it. Announced to Volto Team, AI Team, and Steering Circle for their feedback. Please provide your feedback. Thank you!

  3. Added boring-cyborg to Volto repo and created appropriate messages for first-timers. - @stevepiercy - Information

    1. Example: #issue-6202Update Edit.jsx by harshanmateti · Pull Request #6623 · plone/volto · GitHub
    2. Configuration: volto/.github/boring-cyborg.yml at main · plone/volto · GitHub
    3. Suspension of first-timer PR reviews in docs: Contributing to Volto — Plone Documentation v6
    4. Could not find a way to automatically flag PRs from members of the Volto or Volto Accessibility Teams. Not supported by boring-cyborg.
    5. Don't encourage or require first-time contributors to sign the PCA before submitting a pull request: Don't encourage or require first-time contributors to sign the PCA be… by stevepiercy · Pull Request #1838 · plone/documentation · GitHub

New Business

Update the Volto Project Board and Volto Roadmap as needed.

  1. PLIPs to review

    1. PLIP: Stacked container block settings so subschema blocks (slider, accordian etc) are easier/powerful by being containers · Issue #6569 · plone/volto · GitHub - stacked container settings - @djay - Discussion

      1. As an example, use the sidebar to dive deeper into the structure.
      2. Proposes to standardize the data structure.
      3. Why should nesting be used in the UI, as nesting adds complexity?
      4. Kitconcept attempted to generalize the data structure across all blocks, but was not successful. The trade-off was that generalization made simple blocks convoluted, or complex blocks lacking general implementations.
      5. This PLIP is too complex to resolve in a Volto Team meeting. Needs deeper analysis to be understandable. More discussion needed.

    2. PLIP: TUS reliable large uploads with simpler file upload UI in volto and better feedback on slow connections · Issue #5423 · plone/volto · GitHub - new upload UI

      1. Tabled along with item 1.c. More discussion needed.

    3. PLIP: New feature hide and show Volto blocks · Issue #6559 · plone/volto · GitHub - show/hide blocks

      1. We need to have a PLIP process for UI/UX implementations that is different from the standard PLIP process. We realized that UI/UX PLIPs are usually too complex to discuss during the brief Volto Team meetings. See also item 4.
      2. New feat 17 hide show blocks by SaraBianchi · Pull Request #6556 · plone/volto · GitHub PR for v17

  2. PRs to review

    1. Fix slate RichTextwidget to allow support slate extensions - Nilesh - Review
      1. Fix slate RichTextwidget to allow support slate extensions refs#6570 by nileshgulia1 · Pull Request #6586 · plone/volto · GitHub
      2. Refs: Allow passing slate extensions to RichTextWidget · Issue #6570 · plone/volto · GitHub
    2. Stop generating sitemap.xml.gz - Mikel - Review
      1. Stop generating sitemap.xml.gz (#6561) by reebalazs · Pull Request #6562 · plone/volto · GitHub
      2. Refs: Do not deliver the old sitemap.xml.gz · Issue #6561 · plone/volto · GitHub
      3. Mikel will do some testing on a small site to see whether the redirect concept works, and report back. If it works and maintains compatibility, then it can go into 18, else it will be a breaking change and added in Volto 19.
      4. We need the sitemap feature to be documented.
    3. Show working copy links based on backend actions - Wesley/David - Review
      1. Show working copy links based on backend actions by wesleybl · Pull Request #6393 · plone/volto · GitHub
      2. From David: I won’t be able to come to the meeting. I think this should be pretty uncontroversial, it makes sure these actions are based on whether plone.app.iterate is installed in the backend, instead of based on a frontend setting. Could someone please review?
    4. Document how to migrate projects to Cookieplone - @stevepiercy - Review
      1. Document how to migrate projects to Cookieplone by stevepiercy · Pull Request #6626 · plone/volto · GitHub

  3. Review new issues

    1. Feature: History view and changes improvements · Issue #6584 · plone/volto · GitHub - @stevepiercy - Discussion
      1. Tabled
    2. Feature: support History for home page · Issue #6590 · plone/volto · GitHub - @stevepiercy - Discussion
      1. Tabled

  4. Clarify PLIP Triage and review process - Discussion

    1. Added a new Issue Type of “PLIP”. Sign in to GitHub · GitHub
    2. Issue created at PLIP Process for User Interfacing Changing PLIPs · Issue #6628 · plone/volto · GitHub.
    3. Review existing process at Plone Improvement Proposals (PLIPs) — Plone Documentation v6 and amend as needed with a PR.
    4. Steve will create an ad-hoc private discord channel for live meetings and chat, and invite interested parties. Contact Steve to request an invitation.
    5. See also items 1.b and 1.c.

  5. Create a process to nominate members of Plone Developers or Volto Teams on GitHub - @stevepiercy - Discussion

    1. Has signed PCA.
    2. Has had at least X pull requests merged within Y years.
    3. Has reviewed Z pull requests.
    4. Other potential criteria:
      1. Has attended a Plone Sprint or Conference
      2. Currently hosting a Plone site
      3. Create a Plone project that is publicly available
      4. Created an add-on
      5. Volto Team members may nominate new members.
      6. Timo, Steve Piercy will draft requirements and eventually publish in Documentation. Draft: Become a Volto Team member