Attendees
- Alessandro
- Franco
- Timo
- Rodrigo
- Chrissy
- Eric
Topics
PLIPs
PLIP process
-
As decided at the Ferrara Plone conference, a PLIP can now be submitted and approved without an implementer or without an implementation description (our objective is to encourage people to submit interesting idea even though they can't implement it themselves).
-
The FWT approval is about the feature. Is it interesting? Is it making Plone better? Does it deserve to be in core? But it does not imply the FWT approval regarding the implementation.
-
When a PLIP is implemented, the FWT assigns one of the members as champion, the champion will provide support to the implementer, verify the code implementation, test the feature, and check the documentation. If the champion has a doubt, the rest of the FWT can be involved in the review process.
-
If the PLIP review is satisfactory, the PLIP is merged.
Important remark: When the FWT approaches a PLIP, it is assigned to a Plone version. But it is only indicative, if the implementation is delayed, or is not satisfactory, the PLIP might be moved to a future version. A pending PLIP cannot be a blocker for a release (unless a team decided otherwise specifically).
Note: everybody can read PLIP reviews, they are written as GitHub comments on the PLIP issue using a specific template named “PLIP review”:
PLIP: Remove portal_quickinstaller in Plone 6.0
Maurits implemented it almost entirely. Alessandro offers to be the champion for this PLIP, he will start the review soon.
Maintainer for https://plone.org/community/framework
The FWT page on plone.org was outdated.
Kim kindly fixed it. We will ask him to give edit rights to Eric on that page so we can maintain it by ourselves.
Next meeting
Next FWT meeting is in two weeks (2020-07-07).