FWT Meeting minutes 2019-05-14


Eric Steele
Timo Stollenwerk
Alessandro Pisa
Chrissy Wainmwright
Eric Brehault


Decision-making about strategic sprints

Why did the FWT recently declared a Guillotina sprint as strategic?
The Plone Foundation is providing financial support to many sprints every year.
This support can be offered to any sprint involving softwares or frameworks belonging to the Plone Foundation (so it include Zope, Plone, and also Guillotina).
If a sprint is declared strategic, it may get more support.
The Board cannot declare a sprint as strategic, it has to be done by an official team. Obviously, it should be the most relevant one, and as most sprints are about technical Plone developments, the FWT is the one asked to decide if a sprint is strategic or not.
In the case of Guillotina, the decision should belong to the Guillotina team, but as it does not exist yet, we considered the FWT was the most relevant option (considering the technical connections between Plone and Guillotina, like Volto or the Plone RESTAPI).

Next meeting

Next FWT meeting is in two weeks (2019-05-28).

1 Like

Can this be elaborated at length?

Well basically, Plone and Guillotina are both supporting Volto and the Plone RESTAPI, so when a sprint produces some improvements on Volto and/or the RESTAPI, whatever the sprint is originally a Guillotina one or a Plone one, it will benefit to the 2 of them.

1 Like

The development of the Plone REST API and Volto is a joined effort by Plone and Guillotina developers (and many others). Volto runs on both Plone and Guillotina.

It is hard to differentiate between Plone and Guillotina sprints, topics and tasks to be honest. Just take the Toulouse sprint as an example. Ramon, Nathan, and Victor will go to the Toulouse and the Beethoven sprint (one week after Toulouse) and they will basically work on the same topics. Albert will be in Toulouse and he will work on the Volto UX, which is one of the most important things we need to do right now in Volto. Nathan and Ramon (and others) will for sure work on further enhancing the API design of Plone REST API. Ramon was one of the first people I discussed the REST API design with (he basically wrote plone.rest alone tbh) and Guillotina implemented some of the API endpoints before Plone REST API did. Eric was one of the first people that started to work with Plone REST API and his fantastic work on Angular SDK helped shaping Plone REST API.

I understand that it might look like the Plone 6 efforts (plone.restapi + Volto) and Guillotina are seperate things. There are not. The Toulouse and the Beethoven sprint will be two extremely important efforts this year to push Plone 6 further.

We (as the framework team) understand that we did not do a very good job in the past of explaining our strategic sprint decisions. We already discussed how we make the decision process more transparent and we will try to do a better job. I hope Eric's and my comments made things more clear to you.

1 Like

Thank you. Now this is written down somewhere.

Sounds like a win-win free lunch to me.