跳到主要內容

Building MySQL Together with the Open Source Community

Building MySQL Together with the Open Source Community

MySQL has always been shaped by a broad ecosystem of users, developers, DBAs, contributors, partners, and open source communities around the world.
As MySQL continues to evolve, the MySQL Community is entering a new phase: one focused on innovation, while also providing transparency, and deeper participation and collaboration.
Transparency remains important, but participation and contribution is what turns feedback into action.
That is why Oracle and the MySQL Community are working on new ways to make it easier for developers, users, and contributors to share ideas, discuss technical proposals, follow the roadmap, and help shape the future direction of MySQL.

A New Era of MySQL Community Engagement

MySQL’s 30-year milestone has become more than a celebration. It has also been an opportunity to define a renewed approach to community collaboration, innovation, and participation.
As described in the February New Era of MySQL Community Engagement blog, Oracle is focusing this next phase on three connected areas: bringing more developer-focused innovation into MySQL Community Edition, strengthening the surrounding ecosystem of tools, frameworks, and connectors, and increasing transparency and collaboration so more community voices can help guide and contribute to MySQL’s evolution.
This approach is designed to make participation more practical. Community members should be able to understand the roadmap, see where discussions are happening, provide feedback earlier, and engage through public discussions, GitHub, Early Access testing, and more user group, and contributor-focused events.
The goal is not only to share more information, but to create clearer ways for users and contributors to help shape the future of MySQL through ideas, testing, documentation, feature proposals, and code contributions.

Governance and Community Participation

The MySQL Community engagement plan also includes a more visible governance model. It defines clearer roles and paths for contributors, committers, project leads, aTechnical Steering Committee, and Vulnerability Group for security related work, while preserving the quality, security, compatibility, and stability that MySQL users expect.
For the community, this means a more structured way to participate: participate in roadmap discussions, raise feature requests, join design conversations, test Early Access builds, provide production feedback, and contribute documentation or code.
Governance is about making collaboration easier to understand so feedback can move from discussion toward practical next steps.

From Public Discussions to Contributor Summits

The MySQL Public Discussion series over the last few monts has created a regular space for the community to learn about ongoing MySQL Community initiatives, ask questions, and share feedback.
In May 2026, the first MySQL Contributor Summit brought together Oracle engineers, customers, partners, and members of the open source community for a full day of technical collaboration focused on the future of MySQL.
The Summit included discussions around the MySQL Community Roadmap, including the four areas of focus: AI/cloud integration, performance/observability, DBA/developer experience, and extensibility. More importantly, it created a forum where contributors could bring forward ideas, discuss challenges, and help shape the next steps for MySQL together.
The next MySQL Contributor Summit will take place in Broomfield, Colorado, on August 5–6**, 2026. The focus will be on continuing the discussion from the first Summit, reviewing technical proposals, discussing design ideas, and identifying practical next steps for community-driven collaboration.
GitHub as a Collaboration Hub
A major part of the MySQL Community engagement model includes expanded use of GitHub.
GitHub connects this engagement model with everyday collaboration: feature requests, technical discussions, roadmap visibility and feedback, wiki updates, and follow-up actions can all happen in a place that is visible to the broader community.
The MySQL Community GitHub space is the place for community participation, including:
• GitHub Discussions for open technical conversations
• GitHub Issues for feature requests and proposals
• the MySQL Community Roadmap
• the MySQL Community Wiki
• guidance for contributors and community participants
This gives the community a clearer path to share feedback, propose ideas, follow roadmap-related discussions, and participate in technical conversations.

MySQL Community Roadmap
MySQL Community Roadmap: connecting feedback, discussions, and future priorities.

Whether someone wants to submit a feature request, comment on a proposal, provide feedback from production experience, help with testing, or follow upcoming MySQL Community development, GitHub is the central place to collaborate.

Regional Community Outreach: Taiwan and COSCUP

Community engagement is not only happening online.
In-person conversations remain an important part of building trust, understanding regional needs, and connecting the global MySQL Community with local users and contributors.
This summer, MySQL Community engagement continued across Asia through a series of regional conversations with local communities. Heather VanCura, Vice President of External Standards and Community Engagement at Oracle, met with MySQL users, developers, community leaders, customers, universities, media, and open source ecosystem participants in Japan, Korea, and Taiwan.
In Japan, the MySQL User Group Japan / MyNA community hosted a meetup focused on MySQL Community engagement, Contributor Summit feedback, and perspectives from the local community. The visit also included a joint community roundtable with AWS in Tokyo, media conversations, and a visit to a local science and technology institute hosted by Hokkaido Java User Group leader and Professor Hiroto Yamakawa.
In Korea, Heather met with the MySQL community, customers, and media to discuss the next phase of MySQL Community participation, including open governance, GitHub-based collaboration, the Community Roadmap, and MySQL 9.7 LTS.
In Taiwan, the July 10 joint user group event was originally planned as an in-person meetup, but due to the typhoon, it was moved online. Even with the change in format, the discussion continued and provided another opportunity to connect with the Taiwan MySQL community around MySQL updates, community collaboration, and future participation.

mysql_japac_photo_triptych copy
MySQL Community conversations across Japan, Korea, and Taiwan.

The conversation will continue in Taipei on August 7, 2026, one day before COSCUP, with a MySQL Community Meetup with Ryusuke Kajiyama as a speaker. The meetup will include updates from MySQL 26.7, including improvements across InnoDB, replication, Group Replication, OpenSSL 3.5 post-quantum cryptography support, upgrade and compatibility check progress reporting, and the Thread Pool Plugin in MySQL Community Server.
The meetup will also include a discussion about the latest MySQL Community direction, governance, GitHub collaboration, roadmap transparency, and how users and contributors can share ideas, join technical discussions, and help shape the future of MySQL.
COSCUP is a strong open source community event, and it is a great opportunity to continue this conversation with developers, contributors, students, open source communities, and technology users in Taiwan.

Participation Can Take Many Forms

Contributing to MySQL includes more than contributing code.
Community participation can include many different activities, such as:
• testing Early Access releases
• sharing feedback on features and roadmap priorities
• reporting bugs and reproducible issues
• proposing improvements
• joining GitHub Discussions
• reviewing design proposals
• contributing documentation or examples
• sharing production experience
• organizing or speaking at local meetups
• helping new users and contributors get involved
Every form of participation helps improve the quality, usability, and direction of MySQL.

What Comes Next

The future of MySQL Community engagement will continue to focus on practical collaboration, clearer governance, and more regional opportunities to connect with users and contributors.
Public discussions, GitHub Discussions, feature requests, design proposals, Early Access builds, Contributor Summits, user groups, and regional outreach activities are all part of the same direction: making it easier for the community to participate earlier and more meaningfully.
Oracle and the MySQL Community are building the future of MySQL together.
We invite developers, DBAs, users, contributors, students, community organizers, and open source enthusiasts to join the conversation, share feedback, and help shape what comes next.

Join the Conversation

Explore the MySQL Community GitHub repository, follow the MySQL Community Roadmap, join discussions, and look for MySQL Community activities near you.
If you are attending COSCUP or based in Taiwan, we hope to meet you in Taipei and continue the conversation in person.
Building MySQL together starts with participation.

See Also

留言

這個網誌中的熱門文章

為什麼電視直播比賽總是比網路快?看低延遲串流如何搶秒數

  大多時候,你在網路上看的 Live 直播串流,其實不是與現實世界完全同步的即時轉播,先看看以下這些場景,相信對你來說並不陌生。 NBA 冠軍賽才正看到精彩處,隔壁鄰居卻突然爆出一陣歡呼,原來,用電視觀賞同一場比賽的他們,比你早 30 秒歡呼慶祝三分球入網,不小心點開社群媒體,更發現朋友們早已發文熱烈討論比賽結果。 就像電影被暴雷一樣,少了即時參與的驚喜感、提早知道結局,觀看直播活動的樂趣頓時大打折扣。 或是,收看跨年演唱會時,正當你興高采烈倒數最後 30 秒時,才發現,窗外的慶祝煙火已經此起彼落,大家都已經跨入新的一年,只有你還停留在前一年。 雖然從絕對時間來看,這些狀況都僅有延遲短短幾秒鐘,但在體感上,觀賞體驗卻大受影響,用「失之毫釐,差之千里」來形容再恰當不過。 使用直播串流時,為什麼你的世界總是比別人慢幾秒?原因正是「串流延遲」。 從攝影機到觀眾螢幕的層層關卡 串流延遲,指的是攝影機拍到影像後,直到觀眾端螢幕出現畫面的時間差。 一般來說,有線電視直播約延遲 5 到 10 秒,而 YouTube、LINE、Twitch 等多數 OTT 平台,延遲大多介於 15 秒至 30 秒,距離延遲秒數低於 3 秒的「超低延遲」(Ultra Low Latency)標準,還有一大段距離,這也讓現有直播內容的互動效果有限。 但想克服延遲並不容易,光是一段畫面要從現場攝影機,傳到電腦和手機螢幕,中間所需流程多到難以想像。 KKStream 執行副總李卓軒 Kevin C.H. Lee 解釋,這流程大致包含一開始的攝影機收取影音訊號,接著需轉換訊號、傳輸、上傳雲端、加密、備份,傳到終端裝置後再解碼,最後才是播放。 這整段「螢幕到螢幕」的過程,就像是將包裹從A點運送到B點,只要中間有幾個環節耽誤,就會讓整體運送時間不斷疊加。「每個步驟都要優化,只要有個點延遲很高,加總起來就無法達到超低延遲的標準,這需要很強的技術掌控力。」Kevin 說。 另一個挑戰則在於,由於各大終端裝置原廠(如Apple、Google)雖然有提供低延遲串流相對應的規範,但並未說明實際的執行細節,因此串流技術業者只能自己摸索。 受限於技術瓶頸,目前大多數的直播串流服務,只能在延遲、直播規模和影像品質三者間取捨。例如,常見的視訊會議軟體,像是 Zoom、Google Meet,雖然延遲相對低,但參與人數上...

COSCUP x UbuCon Asia 2026 錄取攤位公告/Full List of Accepted Community Booths at COSCUP x UbuCon Asia 2026

Full List of Accepted Community Booths at COSCUP x UbuCon Asia 2026 COSCUP x UbuCon Asia 2026 Booth now release. See which community you can meet on COSCUP x UbuCon Asia 2026. No. Community Introduction 01 UbuCon Asia HackMD 02 Ubuntu Community & Ubuntu-TW HackMD 03 Cloud Native Taiwan User Group x WasmEdge HackMD 04 Automotive Grade Linux HackMD 05 Ruby Taiwan HackMD 06 Wikimedia Movement in AI Era HackMD 07 t2linux HackMD 08 Twinkle AI HackMD 09 Taiwan JVM Team HackMD 10 Interledger Foundation HackMD 11 SITCON Student Information Technology Conference HackMD 12 OpenEverest HackMD 13 WordPress Taiwan Community HackMD 14 OSPN (Open Source People Network) Japan HackMD 15 GolangTW HackMD 16 opencocon distribution HackMD 17 Open Culture Foundation HackMD 18 GDG TW (Google Developers Groups Taiwan) HackMD 19 FediDev KR & FediLUG (Japan) HackMD 20 Blockchain and Distributed Ledger HackMD 21 Open-EP (E-Paper) Community HackMD 22 FOSS for All HackMD 23 ...

你的程式碼,你的硬體,你的 AI。掌握你的晶片未來。Your code, your hardware, your AI. Own your silicon future.

在 Tenstorrent,我們從晶片設計的最底層開始打造一切。我們不只採用 RISC-V,更將我們的擴充指令集規格全數公開。指令集架構 (ISA) 與硬體架構也完全開源。整個軟體堆疊,從韌體 (firmware)、運算核心 (compute kernels) 到編譯器,全都放在 GitHub 上,並採用你真正能用的授權條款 (Apache 2.0 / GPL)。我們的下一代晶片 Blackhole,旨在掃除傳統設計的低效率,讓你直接掌控資料流 (dataflow),實現更高的速度與電源效率。 Blackhole p150 (單晶片,次世代架構): 32G 記憶體,512GB/s 頻寬 387 TFLOPS (BFP8) / 774 TFLOPS (FP8) 大規模可程式化 RISC-V 核心陣列 算子函式庫、編譯器,整個軟體堆疊 — 全部開源 (OSS) 以原生 CCL 達成真正的多卡擴充,拒絕使用 PCIe workaround $1399 Wormhole n300 (雙晶片,經市場驗證的成熟架構): 24G 記憶體,576GB/s 頻寬 262 TFLOPS (BFP8) / 466 TFLOPS (FP8) 大規模可程式化 RISC-V 核心陣列 算子函式庫、編譯器,整個軟體堆疊 — 全部開源 (OSS) 以原生 CCL 達成真正的多卡擴充,拒絕使用 PCIe 土炮 $1499 現已上市。 立即在官網購買運算卡,或在我們的雲端平台上體驗。 如果你受夠了嚴苛的 EULA (使用者授權合約) 或處處受限的記憶體;又或者,你一直想親自動手,深入探索驅動你類神經網路的 C++ 程式碼;甚至想挑戰組合語言,親眼見證它...