Volto Team meeting notes - 2021-06-22 - 2022-01-18

2022-01-18

Attendees

  • Víctor
  • Nicola
  • Giulia
  • Tiberiu
  • Mikel
  • Alin
  • David Ichim
  • Jakob

Agenda

2022-01-04

Attendees

  • Katja
  • Tiberiu
  • Ross
  • Alin
  • Jakob
  • Mikel
  • Steve Piercy
  • Víctor

Agenda

2021-12-21

Attendees

  • Victor
  • Katja
  • Tiberiu
  • Alec
  • Ross
  • Timo
  • Nilesh
  • Alin

Agenda

2021-12-07

Attendees

  • Victor
  • Nicola
  • Alin
  • Tiberiu
  • David Bain
  • Katja

Agenda

2021-11-23

Attendees

  • Victor
  • Alin
  • Alec
  • Nicola
  • Nilesh
  • Mikel
  • Katja
  • David Bain
  • Claudia
  • Andrei

Agenda

2021-11-09

Attendees

  • Victor
  • Timo
  • Alin
  • Tiberiu
  • Nicola
  • David
  • Nilesh
  • Piero
  • Alec
  • Jens

Agenda

2021-10-12

Attendees

  • Victor
  • Timo
  • Alin
  • Alex
  • Tiberiu
  • David
  • Katja
  • Piero

Agenda

  • Modern Image Scales PLIP (Support for modern image scales (Plone 6) · Issue #3279 · plone/Products.CMFPlone · GitHub)
    • What image scales do we want in Plone 6?
    • Do we want the same image scales that Plone Classic uses?
    • We are not using
      • tile 64:64
      • icon 32:32
      • listing 16:16
    • We` are purging the Plone classic
  • Teaser Block
    • Existing implementations
      • kitconcept (part of grid-block)
      • redturtle (2 implementations)
      • eau de web/eea (use kitconcept grid block)
    • We want the teaser block in core in the long run
    • -> move teaser from @kitconcept/volto-blocks-grid to Core
    • -> Variant option (e.g. card) allows to plug in new variants
  • Grid Block
    • Existing implementations
      • kitconcept
        • focus is simplicity, ease of use, re-use existing blocks as subblocks
        • uses array to store “subblocks”
      • redturtle
        • simple, subblock approach
      • eau de web / eea
        • multi-dimensional, re-use engine, higher-level-component, wrapper for block, uses components that are in Volto core
    • -> our ideal core block will have the UX from kitconcept with the technical infrastructure of the eea block
  • Listing block uses fullobjects
  • Listing block performance issues (not: query)
  • plone.volto
    • 3.0.0a2 released (clone of kitconcept.volto)
    • 3.1.0a1 released (with a new image_field indexer)
  • New Seamless mode
    • The seamless mode was introduced in Volto 13
    • kitconcept was experiencing issues in the demo site and the ploneconf site
      • we worked on this because seamless makes docker deployments easier
      • issues
        • chrome caches the last calls to the site
          • you see json on the cache request
          • hard to overcome
        • hit the back button shows json
        • can lead to cache poisoning when using cloudflare etc. that ignores the vary header
        • request a private image in Volto, the request goes directly to plone and shows a login form
    • redturtle put it into production on a small site, no major issues so far
    • Re-think seamless mode
    • Deprecate old seamless mode?
      • in the long run, there should be one default way of doing things (both for plone.rest and Volto)
      • “seamless mode” should just become the default and does not need its own way
      • new traversal method should become the default for plone.restapi as well (in the long run)
    • we will use the new traversal for the ploneconf site
    • kitconcept will start using it and others should do the same
    • bake the ++ traversal into Volto as a default
      • allow people to add a configuration option to keep the old behavior
  • plone.restapi 7.x.x branch
    • needs lots of backports
    • eau de web is main consumer (Plone 4 sites that run with Volto)
    • redturtle has a couple sites, not for Volto
    • Timo is happy to hand over responsibilities for plone.restapi 7.x.x, either as “release monkey”, that just does releases or entirely (that would need to be discussed with the release team though)
    • we need to make sure plone.restapi 7.x.x does not introduce any breaking changes though (otherwise it would need to become plone.restapi 8 and collide with the 8 branch)
  • Plone Conference / Fanzone
    • Most of the team members will meet in Sorrento!
  • POSTPONED: How can we mark a package to support Volto 12/14, Plone 6/7/8?
    • Python
    • JS

2021-09-28

Attendees

  • Timo
  • Tiberiu
  • Alin
  • Victor
  • Erico

Agenda

  • Volto talks at Ploneconf (Érico)
  • Volto 14 (Victor)
    • release strategy (plan to have a final ready for the conference and Plone 6 alpha 1)
    • postpone login/logout PR that we had to roll back, give it more time
    • features
      • locking
      • new 18n structure / plone-scripts package
      • search block
  • Guillotina support
  • Package Naming Guidelines
    • Package Naming
      • volto-XXX
      • volto-XXX-block (no: volto-XXX-blocks, no volto-blocks-XXX)
      • volto-XXX-widget (no: volto-XXX-widgets)
    • Package Keywords
      • volto
      • plone
      • react
      • volto-addon
      • volto-block
      • volto-widget
  • Search Block
    • EEA use case:
      • make it generic so that we don’t have to customize it for all clients
      • many websites for eea, re-use templates
    • What do we want to ship by default in Plone 6? we will discuss this in Sorrento
  • Slate Editor
    • Next big thing after Volto 14
    • Plone 6 will be released with Slate as default editor
  • Postponed

2021-09-14

Attendees

  • Timo Stollenwerk
  • Alin Voinea
  • Víctor Fernández de Alba
  • Nicola Zambello
  • Katja
  • Nilesh
  • Tiberiu Ichim
  • David Ichim
  • Alec Ghica

Agenda

  • Volto status (Victor)
    • Volto 14.0.0 alpha 1-3 are out
      • Locking (alpha1)
      • Zope Auth improvements (alpha2)
      • Reverted auth (alpha3) PR is fine, we need to figure out the issues that came up
  • Plone 6 (Timo)
  • Ploneconf Fanzone (PLOG) Plone Conference Fanzone Sorrento 2021 — Plone: Enterprise Level CMS - Free and OpenSource - Community Driven - Secure
    • redturtle will send 3-4 people
    • kitconcept will send 7 people
    • eau de web: most likely not possible to send people
    • rohberg (Katja) will be there
    • we could set up a video conference setup to do hybrid meetings
    • topics
      • slate
      • migration
      • default blocks vs add-on blocks
  • Plone 6 Conference Trainings
    • Erico - Deploying Volto - 4h
    • Nicola - Volto Hands-On - 4h
    • Volto Add-ons - Tiberiu/Victor
    • Jakob/Alok - React/Volto
    • Katja/Philip: Mastering Plone 6
  • Plone 6 Conference Talks
    • Plone 6 (Timo)
    • Styleguides and Quanta (Victor)
    • What’s new in Volto (dev perspective) (Victor)
    • Cypress Testing (wanted)
    • Volto-Add-ons (Nilesh, Alex, Andrei)
    • Volto add-ons testing (Nilesh)
    • Showcase talks
      • redturtle
      • kitconcept
    • Volto, different aspects (Nicola)
    • Volto-Slate
    • Lightning-Talks
      • showcase (Katja)
  • Plone 6 Micro-Sprints
    • Thursday afternoons, every second week: 15:00-18:00
  • Plone 6 Add-ons
    • Naming conventions
      • namespace
        • @plone/
        • @collectiveXXX/
        • @eeacms/
        • @kitconcept/
        • @rohberg/
      • namespace python vs js
        • @plone/volto-blocks-XXX plone.volto-blocks-XXX
        • volto-bookmarks collective.bookmarks
        • volto-form-builder / volto-form-builder
        • @plone/volto-form-builder / plone.volto-form-builder
      • prefix
        • volto-
        • plone-
      • blocks / widgets (DONE)
        • question: use blocks/widgets prefix/suffix or not?
        • blocks/widgets is optional, so you can leave that out if your add-on is more
      • volto-XXX (eau-de-web
      • volto-XXX-block (eau-de-web
      • volto-blocks-XXX (kitconcept)
    • Collaboration on add-ons
      • @plone-collective vs collective (python)
        • plone-collective: npm and github reserved
        • possibility to control who can publish under this namespace
      • @plone-addons
      • @plone-contrib
      • @volto/ -> collective ownership of release permissions (possible security issues)
        • Only plone/collective members can publish here
      • collective-XXX
        • Entire world can publish under this names
      • come up with a completely new name
    • Collective

2021-08-31

Attendees

  • Timo Stollenwerk
  • Alin Voinea
  • Tiberiu Ichim
  • David Ichim
  • Nicola Zambello
  • Katja Süss
  • Erico Andrei
  • Mikel Larreategi
  • Fred van Dijk
  • Víctor Fernández de Alba

Agenda

2021-08-17

Attendees

  • Timo
  • Victor
  • Tiberiu
  • Érico
  • Alin
  • Alex
  • Daniela
  • Nilesh
  • Katja

Meeting Notes

2021-07-20

Attendees

  • Víctor
  • David Ichim
  • Timo
  • Alin
  • Alec
  • Tibi
  • Ross
  • Érico
  • Nilesh
  • Nicola

Meeting Notes

2021-07-06

Attendees

  • Víctor
  • Nicola
  • Piero
  • Timo
  • Katja
  • Nilesh
  • Alec Ghica
  • ...

Meeting Notes

  • Selects refactor, any suggestion?
    • Move to a more tested, saner implementation
    • The widgets only take care of specific use cases (from p.restapi json schema)
    • If they have an edge case, then craft an specific component for it (eg. Users/Groups)
  • p.restapi more expressive in json schema serialization (some PRs ongoing already)
    • More to come/required?
    • File/Image differentiation?
  • Storybook upgraded to latest version
  • Importance of the development flow
    • implementation
    • unit
    • cypress
    • storybook
    • docs
    • is it ok how it work in SSR?
  • Todo
  • : Document KGS in Volto README and docs
  • Working copy demo

2021-06-22

Attendees

  • Victor

  • Tiberiu

  • Nicola

  • Ross

  • Piero

  • Giulia

  • Nilesh

  • Mikel

  • ...

Meeting Notes

Mikel: i18n status: I have run a simple Volto i18n audit installing a buildout.coredev-6.0 buildout with the latest released volto. I configured both Plone and Volto in spanish (both Plone and Volto are fully translated into spanish) and checked if all screen messages are shown translated. The result is that everything is properly translated except some items that also in Plone are not translated (some workflow state name or transitions and “logged in users” string in sharing screen). I would say that what we have now is OK. I have asked Gil Forcada (he volunteered at community.plone.org) to set up a Jenkins job to check the translation status of Volto like it is done nowadays for classic Plone, see https://jenkins.plone.org/view/Translations/

1 Like

Plone Foundation Code of Conduct