Plone 6 Coordination Meeting - 2022-07-07

[esteele (Eric Steele)]

Attending:

• Eric Steele - Release Management
• Maurits van Rees - Release Management
• Mikel Larreategi - Translations
• Philip Bauer - Training
• Steve Piercy - Documentation
• Rikupekka Oksanen - Marketing

Notes:

• Training: No updates. Working on trainers for the conference.
• I18n: Dutch and Italian translations for 6 are in progress. Mikel needs to look at documentation on translations, there are 2 PRs opened (Volto and Classic), need to check them.
• Documentation
  • First draft of installation docs. Still needs some work.
  • What’s the next priority?
    • Upgrade guide
      • Volto docs are solid
      • Working on backend, classic
      • Needs a meta-document to link together the various upgrade guides
      • If existing 5.2 content is going to be reused
        • Needs to be converted from restructured text. Ping Steve or someone else in the documentation channel on Discord, we are pretty responsive. But Steve can do the automatic conversion for all old documentation in one branch, so anyone can copy from that.
        • Content needs to be evaluated to make sure it’s valid for Plone 6. Who is best to cover the various sections?
          • Philip is volunteering
      • Upgrading the Backend – Backend — Plone Documentation v6.0-dev
      • Plone 6 upgrade guide – Deployment of Plone — Plone Documentation v6.0-dev
• Marketing
  • Meeting today
  • Create news item about new alpha release
  • Decide when next plone.org sprint will happen
  • What should the principal focus for Plone 6 marketing be next?
• Release
  • What’s holding up a beta release?
    • Classic is ready for beta
    • Volto is waiting for Slate editor, documentation, upgrade steps to Slate
  • Post to community about what beta means, what sorts of changes are valid

[stevepiercy]

@esteele

Upgrade guide

• Volto docs are solid
• Working on backend, classic
• Needs a meta-document to link together the various upgrade guides

I created an issue to track this:

Upgrading Guide

[stevepiercy]

@esteele

If existing 5.2 content is going to be reused

• Needs to be converted from restructured text. Ping Steve or someone else in the documentation channel on Discord, we are pretty responsive. But Steve can do the automatic conversion for all old documentation in one branch, so anyone can copy from that.
• Content needs to be evaluated to make sure it’s valid for Plone 6. Who is best to cover the various sections?
  • Philip is volunteering

I completed conversion of Plone 5.2 reStructuredText documentation to MyST. See `5.2-myst` branch of Plone Documentation now available to fill gaps in Plone 6 Documentation.