PLIP: Ship Plone with Volto

[tisto]

PLIP (Plone Improvement Proposal)

Ship the next major version of Plone with Volto (aka Plone-React)

Responsible Persons

• Timo Stollenwerk
• Victor Fernandez de Alba
• Rob Gietema

Proposer:

• Timo Stollenwerk

Seconder:

• Victor Fernandez de Alba

Abstract

Volto is considered stable and provides the basic Plone functionality on top of a modern, mature, and future-proof JavaScript framework. We released Volto 1.0.0 in September 2018 and we are using it in production on multiple sites since then.

Motivation

There was a major paradigm change in web technology in recent years where more and more functionality moved from backend systems to the frontend. The emerging frontend libraries stabilized a lot in the past three years and React specifically has been one of the most stable frameworks out there.

Assumptions

We sincerely believe that in order to keep Plone relevant in the CMS market, we have to move to a modern platform. We need to attract new open source developers and JavaScript is the language that has the biggest traction in the web industry right now. ReactJS is one of the (if not the) most popular frameworks and it has proven its stability and maturity in the last few years.

Proposal & Implementation

Ship Plone with Volto as the default frontend in the next major version.

Deliverables

• Volto Documentation
• Volto Training (done)
• Update Plone core docs and include Volto
• Polish the integrator story

Risks

• Volto does not gain enough traction in the Plone community. If that happens, it would be easy to revert the decision and keep things as they are. Volto will just be shipped with Plone and people are free to keep using the traditional Plone UI if they prefer to.

Participants

• Timo Stollenwerk
• Victor Fernandez de Alba
• Rob Gietema

[tisto]

@plone/framework-team please review and give feedback.

[frapell]

Huge +1 from me

[tisto]

At the last FWT meeting, we voted for this PLIP. Though, we did not finalize the vote because we were not complete. @frapell @ebrehault @gforcada would you mind submitting your vote for the next FWT meeting? :)

[htgoebel]

I'm heavily against making a front-end which requires Javascript the default or even mandatory.

For valid security reasons, many user have disabled Javascript: One never knows what code the server delivers and the code might threaten my privacy or even be hostile. Also this is contrary to what e.g. bootstrap 5 is doing: reduce the dependency on JS and use more modern CSS features.

[jensens]

@htgoebel we will have both, so it upon you what to use, classic or Volto. In high security scenarios classic is still there. But today the web w/o JS? Seriously, I doubt Plone will survive w/o adopting modern web.

[tisto]

@htgoebel Volto uses Server Side Rendering to pre-render the JavaScript on the server. A user in the browser with JS disabled will still be able to see the contents of a website, just like with the classic Plone UI. Therefore, there will be no difference in the use case you describe.

[tisto]

The Plone Framework team approved this PLIP in March 2019: https://community.plone.org/t/fwt-meeting-protocol-2019-03-19/8241

[jensens]

License legal problems needs to be solved before merge.

Fact:
According to Plone Framework Components Relicensing Policy all Plone core code needs to be GPL unless the board relicenses it on request to a BSD 3-clause license.

This Foundation Policy Resolution is from 2009 and may not reflect the current needs. Anyway, with the current resolution Volto with its with MIT License can not be merged into Plone core.

[tisto]

@polyester we discussed this when renaming plone-react to Volto, right? Did we decide on MIT or BSD?

[polyester]

We need to update that policy. MIT is the prevailing license in the javascript world, so that would be preferable. @jensens shall we bring a proposal in the next Board meeting?

[jensens]

@polyester yes, we need to discuss it and we may end in updating our current policy.

[tisto]

@polyester @jensens any update on the licensing policy? We got quite a few contributors by now and changing the license might become harder the longer we wait.