Volto Early Adopters Meeting (March 2020)

[tisto]

We did our monthly Volto Early Adopters meeting today with 18 attendees. We hold those meetings every month to help companies and developers that use Volto in production. We also discuss the current roadmap and the next steps for Volto development. Here are the notes from that call:

• Current state (Volto 4):
  • Volto 4 final has been released and used in production: https://www.npmjs.com/package/@plone/volto
  • No major bugs found yet
• Volto 5 Roadmap (https://github.com/plone/volto/projects/16):
  • Bundle Optimization / Lazy loading components (https://github.com/plone/volto/pull/967)
  • DateTime Widgets (https://github.com/plone/volto/issues/678)
  • ResolveUID (https://github.com/plone/plone.restapi/pull/820) -> merged in master, will be released as plone.restapi 7.0.0a1
  • File Content Type (https://github.com/plone/plone.restapi/pull/885) -> merged in master, will be released as plone.restapi 7.0.0a1
  • Link Content Type -> no activity right now
  • Multilingual (https://github.com/plone/volto/issues/724) -> PR open, planned to be merged and releases within the next days
  • -> See full roadmap under https://github.com/plone/volto/projects/16
• Mid-Term Roadmap
  • Dexterity Control Panel (https://github.com/plone/volto/issues/1285) -> Alin will work on this
    • Backend part -> next step documentation PR
    • Frontend part -> shouldn’t be too much work (Rob can help if necessary)
  • Documentation (also Plone 6 Roadmap)
  • Form Builder -> Janina will work on this
    • Backend: PoC (Timo)
    • Frontend: schema widget (Rob)
  • Iterate (checkin/checkout) -> Werkbank / Eau de web / kitconcept are interested in a solution
  • Folder contents Pastanaga -> Alok will work on this
  • Control panels -> Alok will work on this
  • Plone locking -> Alok will work on this
  • Copy blocks / page -> Alok will work on this
    • Tiberiu worked on this but the implementation is too specific to be re-used
  • Content-Type Templates
    • will be part of the DX control panel work from Alin
  • Decoupled frontend loading behavior
    • individual requests might take a different amount of time
    • -> good topic for the Beethoven Sprint
• Improve the “Newbie friendliness” of Volto -> Katja
  • https://github.com/plone/volto/issues/1278
  • Slack vs Gitter vs IRC vs Matrix
    • ask Board/Marketing Team -> Victor
    • ask FWT -> Timo
    • Shut down all other services once a decision has been made
    • Volto will follow whatever Plone community decides
  • voltocms.com website
    • Marketing/strategic decision needs to be made: separate CMS vs Plone frontend (not part of the scope of this meeting)
    • Scope: what content should go on a Volto onboarding site targeted at devs?
    • Steffen will work on a first version, Katja will help/review the contents
  • Volto area on community.plone.org
    • We already have a label, we should just start using it
• Volto Add-ons
  • Name spaces: https://github.com/collective/volto-cookie-banner
  • @collective namespace on npmjs https://www.npmjs.com/org/collective -> board (Victor)
• Volto Customization
  • we will schedule a separate meeting for that

The next Volto Early Adopters meeting will be on April 24th, 2020, at 11:00 CET. The meeting is open to anyone who uses Volto in production or has plans to do so in the future. Please drop us a note or email to tisto@plone.org if you would like to attend.

In addition, we will continue to do our Volto Ask Me Anything calls for any questions you might have about Volto.

[jensens (Jens W. Klein)]

@tisto

Slack vs Gitter vs IRC vs Matrix

This was decided years ago and the decision was Gitter and nothing else. This was communicated and all sites I know of were changed to point there.
There is no further discussion needed.

For BBB some IRC enthusiasts introduced the IRC bridge for the old plone IRC channel to Gitter. This is not needed nor useful for new channels.

If there are still places left were IRC or Slack is mentioned (or Matrix, I heard the first time that this is a thing for Plone), please collect those or try to change it directly with a PR.

I have no idea how to shutdown the old slack Plone channels, whoever is into it, please do so.

[tisto]

Do you have a pointer to this decision or communication? We are happy to follow the community decisions. Though, nobody I talked to, except you and Philip, were aware of this decision. Maybe it would help if the board or the FWT would make an official decision. If we do so we should shut down both IRC and Slack (I can take care of the latter).

[jensens (Jens W. Klein)]

I found this one Alternatives to IRC - and IIRC there were some official decisions afterwards, maybe @polyester or @tkimnguyen know the details here? Btw. FWT is the wrong place for decisions here, it is a topic for the Marketing/Communications Team.