Please use this topic to suggest agenda items for our weekly meetings.
This week we will be having a Design/UX meeting followed by the weekly Dev meeting.
Please use this topic to suggest agenda items for our weekly meetings.
This week we will be having a Design/UX meeting followed by the weekly Dev meeting.
Comments
I think it MIGHT be nice to spend some time in the developer meeting talking about "distributions" or whatever else we might decide to call them in the future.
Graham Leach is making a strong case that we should talk about "Editions" instead of "Distributions" in a topic in Zulip.
https://backdrop.zulipchat.com/#narrow/stream/218635-Backdrop/topic/Dist...
Also, Kevin has actually created a distribution in our contrib space and he may be requiring us to make some infrastructure decisions/changes in the near future.
I don't believe that BackdropCMS currently accomodates distributions/editions. What needs to happen?
See: https://github.com/backdrop-contrib/express
Specifically, this issue:
https://github.com/backdrop-contrib/express/issues/1
I planning on attending this meeting (kids willing). Because we will be developing this initially as a Pantheon Upstream, we don't actually need Backdrop to change anything. I'm only helping Tim Stalker with the Express Install Profile migration in as much as it overlaps with the work I'm doing to scope out the effort required to upgrade some of the cu.edu sites still on D7.
We're mainly approaching this as an install profile because that's what it is now, but that may not even be necessary or provide a benefit over installing Backdrop w/ a Standard Profile and then enabling a "super" module that triggers the dependency installs.
It would be great for CU staff with Pantheon access to be able to spin up new Backdrop sites from the Pantheon Dashboard without having to authenticate into the CMS post-install and enable additional modules, but that's not an MVP requirement.
For the Outreach committee, I think we should talk about the proposal to create a new Marketing Committee and replace the Outreach meeting with a Community meeting.