Chapter operation

I would like to provide some time for devs to work on parts of the organisation that they are passionate / inspired by. Which inspired projects like: Frontend Dev Relay, OSRM-Lambda and others. With the goal to later turn that into development time, like AI chapter mentioned. Which would also contribute to personal development. Aside from that i'd like to promote more collaboration and teamwork on big epics. I think it might be good to have all members write/describe a task they really enjoyed and an area they wish to learn more of, and have these shared within the team, so it becomes easier to ask someone for their input or to ask them to help out with part of the task.

Meetings

I actually am happy with the meetings within the team we currently have, however since some of the key stakeholders will be devs from various teams I would likely try to sync with various devs from time to time, making sure we're able to grab low-hanging fruits and help with QoL improvements from time to time. That might mean a semi-regular sync with team/chapter lead, but also an occasional sync with some of the devs. Depending on whether it lies in the nature/desire of my team members would provide some room for them to do the same.

Business need

I would say that the needs we should facilitate in would be:

• uptime/availability

• scalability

• security

However for most of these the dev teams should also contribute.