RFC #106: Wagtail 6.5* and 6.6* roadmap updates

[thibaudcolas]

View the RFC in HTML. Once reviewed with enough feedback and approved by the core team, those changes will go live on the Wagtail Roadmap.

6.5* and 6.6*: Provisional version numbers. See our Release schedule for more info.

[thibaudcolas]

This is now ready for review :)

[Stormheg]

Looks like 6.5 is shaping up to be one for the benefit of headless users 👍

Couple of questions, no objections

[thibaudcolas]

Thank you for the feedback @Stormheg! There are a few elements of my answers I’ll want to move within the RFC contents but I’ll leave them as comments for now for others ’ benefit. I brought this to last week’s core team meeting briefly, and yesterday’s with a few more details, so marking this as "Final Comment Period". There’s lots of time for comments, I’ll be looking at updating our roadmap towards the second half of the month assuming we get enough feedback by then.

[thibaudcolas]

I’ve updated the RFC based on feedback (thank you @Stormheg for the excellent questions!). Unfortunately I’ve also moved "Headless preview & userbar" from the Wagtail 6.5* release to "Future" as I didn’t realise we’re not clear yet when this can go ahead. Could still be 6.5* but it’s better for us to commit to fewer things that are more firm.

More reviews/ feedback very welcome!

[lb-]

Is it worth splitting the headless preview and headless userbar into two items?

Maybe it's possible to merge the headless preview package into core as a somewhat easier first step. This may help set up some momentum for headless usage, even if it's one less dependency.

[thibaudcolas]

Good shout, thank you @lb-!

[Stormheg]

LGTM

[thibaudcolas]

Thank you @Stormheg! Other feedback to date has only been positive so I’ll move forward with the corresponding public roadmap changes. If anyone has further feedback about any of the points, we can still make changes later.

[thibaudcolas]

I have added a "sponsored" label to our roadmap items in GitHub following @Stormheg’s question. That label is in addition to the existing "needs sponsorship" and "needs contributions" labels, to increase transparency a bit. We normally showcase sponsored work in the release notes – that label will make this same information more visible and available earlier.

I’ve spent a bit of time retroactively labelling past roadmap items. And added the label to our Google Summer of Code, Google Season of Docs, and Outreachy projects. Not sure if that’s helpful or no but "we" do receive funding for those in some ways so I guess that counts?

• GSoC projects are financially supported by Google, with a $1.5-3k stipend for contributors, and $500 for the Wagtail org
• Season of Docs (one project) was supported by Google, going entirely to our contributor.
• Our Outreachy participations were supported by Torchbox and the Outreachy general fund, with $7k stipends for contributors.