the roadmap looks pretty interesting but I have a huge concern right now as something is missing from it: when are we expecting to fix the resource registry situation?
also here I have some other comments:
- we need to release faster with less features
- Plone 5.2 looks pretty fine as everything seems to be ready
- Plone 5.3 features still look not well defined
- Plone 5.4 features look nice, we can probably release this features in 5.3 instead:
recycle bin: is a must have, perhaps should be initially in the form of an add-on to make it simpler to maintain
image/file/video repositories: can you please elaborate more on what does this means?
quick add: can you please elaborate more on what does this means?
content quality check: again, pretty interesting but must come also in the form of an extensible add-on; it's pretty important for developers and integrators to be able to extend easily the quality checks; also we need to define which quality checks will be included by default
some other things I want to bring to discussion:
decouple the web syndication code from the core, to make it easier to make this feature optional in the future; let's face it: web syndication as we know it has been slowly dying and RESTAPI will speed this up; this is from the Wikipedia:
Several major sites such as Facebook and Twitter previously offered RSS feeds but have reduced or removed support. Additionally, widely used readers such as Shiira, FeedDemon, and Google Reader have been discontinued having cited declining popularity in RSS. RSS support was removed in OS X Mountain Lion's versions of Mail and Safari, although the features were partially restored in Safari 8. As of August 2015, Mozilla Firefox and Internet Explorer include RSS support by default, while Google Chrome and Microsoft Edge do not. Additionally, reader services such as Feedly provide synchronization between desktop RSS readers and mobile devices.
decouple the social media integration code from the core, to make it easier to maintain; some of you already know that I was against of including this feature in the core from the very beginning. IMO, the feature implementation is naïve, complex (it even depends on the syndication code), not easy to fix or extend, and it even includes support for proprietary "standards" like the so called Twitter Cards.
Social Media integration is not easy (just take a look the code of our sc.social.like add-on) and it also involves content quality checks that are outside from the scope of the current Plone 5 core implementation.
just to give you an example: in the past 2 days I've being working to fix a bug in our code that is caused by a wrong interpretation of what Facebook's Open Graph canonical URL (the
og:url property) is meant to be. after reviewing the Plone 5 code, in order to make our add-on compatible with it, I came into the conclusion that I'm just going to hide the viewlets associated with social media in Plone 5 and replace them with our implementation.
besides that, we need to:
to be continued…