Notes and actions from Contributor Summit 2

Very brief notes

• Many were not aware of threads in mysql-server with active spec discussion. Partly we lost the link from the "roadmap proposal tickets" to tickets in mysql-server capturing weeks of design work.
• A strong core constituency emerging from hyperscalers and their RDS services: Several talks about issues that become problems/annoying at scale. One or sometimes two cloud teams had already patches in production. For example: Dealing with 50 GB - 150 GB transactions.

Actions

• Henrik to establish a weekly newsletter (possibly AI generated?) highlighting the most active proposals or projects and links to where to find them
  • Distribution at least: Community Slack, create new channel, Linkedin group. (How about: A blog? mailing list?)
• Lilly: Consider creating a good old mailing list for general project discussion
  • In the mean time, use community slack, standardize on rooms.
• Henrik: Update Developer and Contributor Guides. Should reflect phase 2 flow of patches. Consider moving them to this wiki.
  • issue https://github.com/mysql/mysql-community/issues/112
• Scott: Continue developing metrics about the project (Henrik could help, overlaps with 1st point)
• Henrik, Seema: Continue evolving the github workflow and tooling, in particular how o write and review worklog designs.
• We saved the chat from the summit, should we publish it somewhere?