Volto Team meeting minutes 2025-03-11

Attendees

  • Steve Piercy
  • Piero Nicolli
  • Victor
  • Alin
  • Tisha

Housekeeping

  • Designate Note Taker - @stevepiercy
  • Designate Time Keeper - @pnicolli
  • Review agenda topics, presenters, and timings - @pnicolli
  • Topics should not exceed 15 minutes of discussion time, as that probably means it is too complex to resolve during this meeting. Ad hoc meetings or sprints may be a better venue.

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.

  • None

New Business

Update the Volto Project Board and Volto Roadmap as needed.

  • Feature/jest to vitest migration #6605
    • https://github.com/plone/volto/pull/6605
    • What is the value to adding this to v18? You can use Vitest now by adding its configuration to your project. Adding it to v18 would allow developers to more easily migrate from Jest to Vitest at their leisure. Jest will be removed completely in v19.
    • Decision: It’s better to add Vitest to v18 now than leaving it out.
  • Get defaultLanguage from the backend @site endpoint #6807
  • Add validator for default_language in language control panel #6811
  • get multilingual settings and available languages from backend #6818
    • https://github.com/plone/volto/pull/6818
    • This is still in progress. It depends on the release of plone.restapi which includes the is_multilingual attribute in the @site endpoint. We can’t force people to upgrade to the latest version of plone.restapi in a minor version. We’ve never done it in the past.
    • We need feedback from @erral and further discussion. We’re leaning towards v19.
  • contextual vocabularies #6236
  • Update documentation to replace jsconfig.json with tsconfig.json for Volto Version 17 #901
  • Fix video block can't be re-selected once it has been clicked on #4147
  • Save edit form as draft using localStorage #4252
  • Are there any other issues or pull requests that should be discussed at the Bucharest sprint? Let’s ask when the minutes are published. To suggest an item for the sprint, you can reply on the Community Forum, jump into the Sprint channel, or reply on any open issue or pull request.
  • GitHub - actions/stale: Marks issues and pull requests that have not had recent interaction
    • Start with a notification asking them if the issue is still valid or fixed.
    • Add the label Stale.
    • After how many months after it was last updated?
    • Don’t want to close issues automatically at this time.
    • Let’s bring it back to the next Volto Team meeting.
2 Likes