Attendees
- Steve Piercy
- Víctor
- Piero
- Rob
- Jakob Kahl
- David Ichim
- Timo
Agenda/Notes
- Managing newcomers [Steve Piercy and David Ichim]
- Create a new section, For students and learners by stevepiercy · Pull Request #1618 · plone/documentation · GitHub
- Blocking a user from your organization - GitHub Docs
- Locking conversations - GitHub Docs
- Assigning issues and pull requests to other GitHub users
- Managing labels - GitHub Docs - Apply labels "42 lvl: moderate", "43 lvl: complex", or "03 type: feature (plip)" per Work with GitHub issues.
- https://www.youtube.com/watch?v=5nY_cy8zcO4 [David Ichim] open source isn’t free mentorship, we need quality contributions not spam quantity
- UI tests and screenshot tools [Steve]
- Volto uses Cypress for tests.
- @polyester has a proof of concept for taking screenshots of the Volto demo site with Cypress, but has hit a wall with getting it to work with Docker containers.
- Classic UI currently uses robot.framework and Selenium for tests. They are not happy with this setup.
- No one wants to rewrite tests for a new framework, but the tradeoff may be worth the investment in time.
- Classic UI Team and Documentation Team are evaluating Playwright for both running UI tests and taking screenshots of the UIs for documentation.
- Playwright works with both Python and JavaScript frameworks, whereas Cypress works only with JavaScript. Read a detailed comparison analysis at Cypress vs Playwright: A Detailed Comparison | LambdaTest published 2023-09-19.Cypress vs Playwright: A Detailed Comparison | LambdaTest
- Another interesting read: On Migrating from Cypress to Playwright · mtlynch.io
Discussion
The community has put a lot of effort in Cypress, getting the right dynamic, CI integration, learning the caveats and how it does work. There are dozens of hours invested and hard learn know how. Classic UI can benefit of all this, right away. Not willing to take advantage of this, is just non-sense. Cypress can test Classic as well as Playwright, the fact that it has a bridge library is not an advantage at all. The fact that Playwright relies in Selenium is a disadvantage. Migrating to Playwright just because M$ has sponsored some people to write nice posts about it is non sense, and the community does not have bandwith for it. What it would be common sense would be that the community agrees on one tool, and abide to it. Dispersing our resources this way leads to nothing valuable.
- Documentation [Steve]
- Should we delete Developer roadmap? I think it is redundant to everything under Contributing to Volto. (Discussion) Steve will ask Tiberiu whether it is worth keeping or redundant.
- [docs] Reorganize content in README.md Reorganize README, merging content into authoritative locations by stevepiercy · Pull Request #5511 · plone/volto · GitHub (Needs review)
- Lots of open Volto installation docs issues (Volunteer, pretty please!)
- GSoD ideas: (FYI)
- End user docs for both Volto and Classic UI
- Automate screenshots
- Document how to automate screenshots
- Audit, propose, and update installation and contributing docs
- GSOC2023 project: User and groups control panel status [GSOC] User and Group Control panel by rahilhastu · Pull Request #4974 · plone/volto · GitHub Feedback on the PR wanted.
- Object browser condition on maximum size bugfix: wrong conditional proprieties on ObjectBrowser by Wagner3UB · Pull Request #4190 · plone/volto · GitHub Needs review, and backport to 17 and 16.
- Beethoven Sprint 2024
Event Content Type Improvements: [DRAFT] PLIP #TBD: Enhance timezone, date, and time support in event content types · Issue #5629 · plone/volto · GitHub