You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@MrTango just wondering why this package ended up in the plone namespace and not in the collective. Even though this definitely is a useful feature, I guess we don't plan to ship this with Plone itself at any point, correct? Or did I miss a PLIP?
I can imagine there might be other options and approaches to export to PDF in the future and then this package would be considered to be the "definite one" just because of its name.
IMHO the plone namespace should be preserved for core packages and packages that are planned to be shipped with core at some point (and approved by the FWT).
I know we made exceptions when it comes to widgets in the past but that differs from an add-on like this...
The text was updated successfully, but these errors were encountered:
@MrTango just wondering why this package ended up in the plone namespace and not in the collective. Even though this definitely is a useful feature, I guess we don't plan to ship this with Plone itself at any point, correct? Or did I miss a PLIP?
I can imagine there might be other options and approaches to export to PDF in the future and then this package would be considered to be the "definite one" just because of its name.
IMHO the plone namespace should be preserved for core packages and packages that are planned to be shipped with core at some point (and approved by the FWT).
I know we made exceptions when it comes to widgets in the past but that differs from an add-on like this...
The text was updated successfully, but these errors were encountered: