Combine existing meetings and revisit cadence to increase efficiency
Ways forward
Need to see how things look in January 2023
Lot of things are undecided at this moment, which makes it hard for this group to make decisions as well
The new TSC will also need to set scope and goals, which would affect this team as well, if it keeps existing
2023 is very uncertain, including people's ability to participate in the community with dedicated time to contribute
Should this team keep existing as is?
The group on today's call is in an agreement to involve the new TSC
Make sure they're aware of the existing resources that this group has been working on
Make the TSC aware of the scope and duties of this group and support them with having the responsibilities distributed among the active contributors
See if there are people who are available and motivated to keep up an organized group or activity?
How we can help the new TSC to keep caring for the community and contributors in a centralized way (dedicated team) or as a shared responsibility for all contributors?
Roadmap and responsibilities
Community-driven development and maintenance of processes will be key
Processes will need to be minimal and efficient to help people accommodate, ie: less meetings and more efficient ways of (semi-)async communication
Agreement:
Focus on documenting and making this group's resources available to the newly forming TSC
Contributor guide
List of activities
Values and focus areas
Stop running the organized meetings for now and let the new TSC decide how they would like to approach the responsibilities that this group has been having
Next steps
AP (Ildiko)
Make sure that the Confluence wiki has all pointers and resources that the community can use
Write up a "wrap-up" email to let people know that we stop having meetings and point them to communication channels such as Slack and the available resources