I disagree with the first sentence in the first paragraph. The FWT does not exist or function, and telling developers to contact /dev/null
is doubleplus ungood. Victor already handles Volto PLIPs, and it sounds like Classic UI is going to do the same, but I don't know about Products.CMFPlone unless one of its release managers steps up and agrees to take on that responsibility (as if they don't have enough to do already!). @erral says go with the Steering Circle as a first point of contact. I'm going with that in the docs PR for now, until we have a chance to discuss and decide over time, and I'll update it again.
I mostly agree with the second paragraph, and I documented such in the PR. That is, except sometimes Volto and Classic UI PLIPs touch backend bits and pieces. Instead of "only" affecting a frontend, I would go with "primarily" affecting it. Is that reasonable?
Yup, that's in the PR.
I discovered it in a Community Forum post while researching the status of the FWT. Here it is:
I added the PLIPs board to the docs PR, as it seems to be the centralized location for PLIPs which replaced a Google Sheet.
I think so going forward. I updated the PLIP issue templates in Volto and Products.CMFPlone to automatically add the label 03 type: feature (plip)
. Example: Automatically set the label to `03 type: feature (plip)` for PLIPs by stevepiercy · Pull Request #3982 · plone/Products.CMFPlone · GitHub. And checking this GitHub help article, it is possible:
projects: "plone/47"
I'll submit another PR for that. Thanks for the idea!
I don't know about retroactively, though. You can search for all open PLIPs not in Volto and CMFProducts.Plone. Then you can go to each of the 37 PLIPs, and add them to the project board. Or if one repo has a lot of PLIPs, you can go to that repo and search for the label 03 type: feature (plip)
and add them in bulk. Or someone could write a script that interacts with the GitHub API to do the same.