@@ -1,55 +1,52 @@
-name: "👋 Get Involved"
-description: "Introduce yourself and tell us how you'd like to contribute to OurSQL Foundation."
-title: "Get Involved: [Your Name / Organization]"
+name: "Get Involved"
+description: "Tell us who you are and what you'd like to work on."
+title: "Get involved: [your name or org]"
 labels: ["get-involved"]
 body:
   - type: markdown
     attributes:
       value: |
-        ## Welcome to OurSQL Foundation 👋
+        Open this issue, fill in what's relevant, and we'll pick up the conversation here.
 
-        Thanks for your interest in getting involved! This form helps us understand who you are and how we can work together. There are no wrong answers — every kind of participation matters.
-
-        Fill in as much or as little as you're comfortable sharing. We'll follow up in this issue.
+        You don't need a finished proposal. "I run MySQL at $company and want to understand what the foundation is doing" is a perfectly good starting point.
 
   - type: dropdown
     id: role
     attributes:
-      label: "Who are you?"
-      description: "Pick the description that fits best."
+      label: "What do you do?"
       options:
         - Developer / Software Engineer
         - Database Administrator (DBA)
         - DevOps / SRE / Platform Engineer
         - Architect / Tech Lead
         - Engineering Manager / CTO
         - Researcher / Academic
-        - Open Source Maintainer
-        - Company / Organization representative
+        - Open source maintainer
+        - Company or organization representative
         - Other
     validations:
       required: true
 
   - type: checkboxes
     id: participation
     attributes:
-      label: "How would you like to participate?"
-      description: "Check everything that interests you — you can always change your mind later."
+      label: "How do you want to contribute?"
+      description: "Check whatever applies. You can change direction later."
       options:
-        - label: "Contributing code or technical work"
-        - label: "Testing and quality assurance"
+        - label: "Writing code or doing technical work"
+        - label: "Testing"
         - label: "Writing documentation or blog posts"
-        - label: "Community building and outreach"
+        - label: "Community work and outreach"
         - label: "Advocating for open source MySQL licensing"
         - label: "Representing my company or organization"
         - label: "Sponsoring or funding foundation work"
-        - label: "Participating in governance discussions"
-        - label: "Just staying informed for now"
+        - label: "Participating in governance"
+        - label: "Staying informed for now"
 
   - type: textarea
     id: background
     attributes:
-      label: "Tell us a bit about yourself"
+      label: "Background"
       description: "What do you work on? What's your history with MySQL-compatible databases?"
       placeholder: "I've been running MySQL in production for X years, currently working on..."
     validations:
@@ -59,25 +56,25 @@ body:
     id: interest
     attributes:
       label: "What brought you here?"
-      description: "What problem or opportunity made you interested in OurSQL Foundation?"
+      description: "A specific problem, a licensing concern, a project you maintain — whatever it is."
       placeholder: "I care about this because..."
     validations:
       required: false
 
   - type: input
     id: organization
     attributes:
-      label: "Organization (optional)"
-      description: "Company, project, or community you represent or want to mention."
+      label: "Organization"
+      description: "Company, project, or community — if relevant."
       placeholder: "Acme Corp / my-oss-project / independent"
     validations:
       required: false
 
   - type: input
     id: links
     attributes:
-      label: "Links (optional)"
-      description: "GitHub profile, LinkedIn, personal site — whatever you'd like to share."
+      label: "Links"
+      description: "GitHub profile, personal site, anything useful."
       placeholder: "https://github.com/yourhandle"
     validations:
       required: false
@@ -86,6 +83,4 @@ body:
     attributes:
       value: |
         ---
-        By submitting this issue, your name and any information you provide will be publicly visible on GitHub. Only share what you're comfortable making public.
-
-        We'll respond in this thread. You can also reach us at [hello@oursql.org](mailto:hello@oursql.org).
+        This issue is public. Only share what you're comfortable with. You can also reach us at [hello@oursql.org](mailto:hello@oursql.org).
@@ -1,2 +1,59 @@
-# Website
-Website repository
+# OurSQL Foundation
+
+OurSQL Foundation is a vendor-neutral nonprofit dedicated to the advancement and sustainability of open source MySQL-compatible database technologies.
+
+This repository contains the source for [oursqlfoundation.com](https://oursqlfoundation.com) — a Hugo static site published via GitHub Pages.
+
+## Run it locally
+
+The site uses Hugo (extended version). Install it first.
+
+**macOS:**
+```bash
+brew install hugo
+```
+
+**Other platforms:** see [gohugo.io/installation](https://gohugo.io/installation/).
+
+Clone the repository:
+
+```bash
+git clone git@github.com:OurSQLFoundation/OurSQLFoundation.git
+cd OurSQLFoundation
+```
+
+Start the dev server:
+
+```bash
+hugo server -D
+```
+
+Open [localhost:1313](http://localhost:1313) in your browser.
+
+## Make changes with Claude Code
+
+Add the project folder to [Claude Code](https://claude.ai/code). Then describe what you want changed — a new blog post, a copy edit, a layout tweak. Claude reads the Hugo project structure directly and edits the right files.
+
+Run `hugo server -D` to verify the result at [localhost:1313](http://localhost:1313) before committing.
+
+## Contribute
+
+Work in a branch, not on `main`:
+
+```bash
+git checkout -b your-branch-name
+```
+
+Make your changes, then commit and push:
+
+```bash
+git add .
+git commit -m "describe what you changed"
+git push origin your-branch-name
+```
+
+Open a pull request on GitHub. Keep PRs focused — one change per PR makes review faster.
+
+## Get involved
+
+Not sure where to start? [Open an issue](https://github.com/OurSQLFoundation/OurSQLFoundation/issues/new?template=get-involved.yml) and tell us who you are and what you'd like to work on.
@@ -1,31 +1,32 @@
 ---
 title: "About OurSQL Foundation"
-description: "Learn about our mission, values, and vision for the MySQL-compatible open source ecosystem."
+description: "OurSQL Foundation is a vendor-neutral nonprofit for the MySQL-compatible open source ecosystem — who we are, what we do, and how governance works."
 ---
 
 OurSQL Foundation is a vendor-neutral nonprofit dedicated to the advancement and sustainability of open source MySQL-compatible database technologies.
 
 ## Mission
 
-We exist to ensure that the MySQL-compatible database ecosystem remains open, community-driven, and sustainable — free from the control of any single vendor.
+The MySQL-compatible ecosystem — MySQL, MariaDB, Vitess, TiDB, and the tooling around them — runs a significant share of the world's production databases. Governance of that ecosystem has always been fragmented or vendor-controlled. Key decisions happen behind closed doors. Licensing shifts without community input. Maintainers carry costs that no one coordinates to share.
 
-Our work spans governance, advocacy, infrastructure support, and community building across the entire MySQL-compatible open source stack: MySQL, Percona Server, MariaDB, Vitess, TiDB, and beyond.
+OurSQL Foundation is a neutral home where developers, DBAs, and organizations can work on those problems without any single vendor setting the agenda.
 
-## Why OurSQL Foundation?
+## What we work on
 
-The MySQL ecosystem powers a significant portion of the world's databases. Yet the governance structures, licensing models, and sustainability mechanisms for key projects have long been fragmented or vendor-controlled.
-
-OurSQL Foundation was created to change that — to provide a neutral home where developers, companies, DBAs, and community members can collaborate on the future of MySQL-compatible technology without fear of lock-in or agenda capture.
+- **Governance advocacy** — pushing for open, documented decision-making across MySQL-compatible projects
+- **Licensing** — advocating for permissive, stable licenses that users and contributors can rely on
+- **Infrastructure** — funding shared tooling, testing environments, and critical maintenance work
+- **Maintainer support** — helping sustain the people who keep these projects running
 
 ## Values
 
-- **Openness** — All work happens in public. Decisions are transparent and documented.
-- **Neutrality** — No single company or interest controls outcomes.
-- **Sustainability** — We invest in maintainers, infrastructure, and long-term project health.
-- **Inclusivity** — The MySQL community is global and diverse. We reflect that.
+- **Openness** — all work happens in public; decisions are documented and auditable
+- **Neutrality** — no single company or interest controls outcomes
+- **Sustainability** — we invest in maintainers, infrastructure, and long-term project health
+- **Inclusivity** — the MySQL community spans the world; the foundation reflects that
 
 ## Governance {#governance}
 
-OurSQL Foundation operates under an open governance model. Details on membership, voting, and working groups will be published as the foundation structure matures.
+OurSQL Foundation operates under an open governance model. Membership, voting procedures, and working group charters will be published as the structure develops. Nothing is decided in private.
 
-Interested in getting involved? [Open an issue on GitHub →](https://github.com/OurSQLFoundation/OurSQLFoundation/issues/new?template=get-involved.yml)
+If you want to shape how the foundation is built, [open an issue on GitHub](https://github.com/OurSQLFoundation/OurSQLFoundation/issues/new?template=get-involved.yml) and tell us what you'd like to work on.
@@ -3,54 +3,48 @@ title: "An Open Letter to Oracle: The MySQL Community Speaks"
 date: 2026-05-10
 author: "OurSQL Foundation"
 tags: ["Open Letter", "MySQL", "Community"]
-description: "Members of the MySQL community have addressed Oracle with an open letter calling for a vendor-neutral foundation to govern the MySQL ecosystem. Here is what it says and why it matters."
+description: "Members of the MySQL community sent Oracle a formal letter asking for vendor-neutral governance of the MySQL ecosystem. Here is what it says and what happened next."
 image: "/blog/open-letter.png"
 ---
 
 {{< figure src="/blog/open-letter.png" alt="Open Letter to Oracle: Invitation to Discuss the Future of the MySQL Ecosystem" class="post-hero-image" >}}
 
-In early March 2026, members of the MySQL community formally presented Oracle with an open letter proposing the establishment of a vendor-neutral, nonprofit foundation to support the MySQL ecosystem. Oracle declined to participate but reaffirmed its "commitment to transparency and community engagement."
+In March 2026, members of the MySQL community formally presented Oracle with an open letter proposing a vendor-neutral, nonprofit foundation to support the MySQL ecosystem. Oracle declined to participate but reaffirmed its "commitment to transparency and community engagement."
 
-The letter, now open for community signatures at [letter.3306-db.org](https://letter.3306-db.org/), makes a case that has been building quietly for years.
+The letter is now open for signatures at [letter.3306-db.org](https://letter.3306-db.org/).
 
-## What the Letter Says
+## What the letter says
 
-The letter identifies five structural challenges facing MySQL today:
+Five problems. All of them real if you've worked with MySQL-compatible databases at any scale.
 
-**1. Declining competitiveness.** PostgreSQL is attracting a growing share of new projects, driven by its open development model, active community, and modern feature set. MySQL risks being seen as legacy technology not by technical merit, but by governance and momentum.
+**Declining competitiveness.** PostgreSQL is taking a growing share of new projects. Not because of raw technical superiority — because its development model is open, its community is active, and contributors can see their work land. MySQL risks looking like legacy technology by governance, not by merit.
 
-**2. Transparency deficit.** MySQL development happens largely behind closed doors. The public roadmap is minimal. Security bugs go untracked in public. Contributors have little visibility into what is being worked on, or why.
+**Transparency deficit.** MySQL development happens behind closed doors. The public roadmap is thin. Security bugs go untracked in public. If you contribute, you have little visibility into whether or when your work moves forward.
 
-**3. Contribution barriers.** The process for submitting and reviewing code is described as opaque and discouraging. Talented contributors walk away. Work gets duplicated across forks instead of flowing upstream.
+**Contribution barriers.** The code review and merge process is opaque. Talented contributors walk away. Work gets duplicated across forks instead of flowing upstream where it would benefit everyone.
 
-**4. Technical gaps.** MySQL lacks capabilities that have become table stakes for modern applications — native vector search being a clear example as AI workloads become central to new development.
+**Technical gaps.** Native vector search is one example. As AI workloads become central to new development, MySQL is missing capabilities that users now expect from a modern database.
 
-**5. Community stagnation.** The developer community around MySQL is aging. New developers are not being drawn in at the rate needed to sustain long-term ecosystem health. Fragmentation across competing distributions makes the problem worse.
+**Community stagnation.** The developer base is aging. New developers are not joining fast enough to sustain the ecosystem long-term. Fragmentation across distributions makes coordination harder than it needs to be.
 
-## Three Paths Forward
+## Three paths forward
 
-The letter proposes three governance models, ranging in Oracle's involvement:
+The letter proposed three governance models, ranging by how much Oracle participates:
 
-- **Oracle-led** — Oracle establishes a trade association following established open source governance patterns, maintaining strategic control while distributing operational responsibility
-- **Collaborative** — Industry partners manage operations while Oracle holds a principal board position, with trademark licensing for nonprofit advocacy and community work
-- **Independent** — Community partners form a separate entity focused on advocacy and ecosystem coordination, with optional Oracle participation
+- **Oracle-led** — Oracle establishes a trade association following established open source patterns, maintaining strategic control while sharing operational responsibility
+- **Collaborative** — industry partners manage operations; Oracle holds a principal board seat and licenses the trademark for nonprofit advocacy work
+- **Independent** — community partners build a separate entity focused on advocacy and ecosystem coordination; Oracle can join or not
 
-The request was simple: align on a direction by end of March.
+The ask was simple: align on a direction by end of March.
 
-## Where Things Stand
+## What happened
 
-Oracle said no. Or more precisely, Oracle said not yet — reaffirming commitment to the community without committing to structural change.
+Oracle said no. Or more precisely: not yet — reaffirming community commitment without committing to structural change.
 
-That answer, while not surprising, clarifies something important: if the MySQL ecosystem is going to have the governance structures it needs, the community will have to build them.
+That answer clarifies something. If the MySQL ecosystem is going to have the governance structures it needs, the community will build them without waiting for permission.
 
-## Why This Matters
+## Why this matters to you
 
-The letter is not an attack on MySQL. It is a defense of it. The people who signed it and the people continuing to sign it are MySQL users, operators, contributors, and advocates who want to see the ecosystem thrive for the next twenty years — not decline quietly.
-
-A vendor-neutral foundation does not replace Oracle's stewardship of MySQL. It complements it. It provides a home for the community work, the advocacy, the contribution infrastructure, and the coordination that no single company — including Oracle — should own alone.
-
-## Sign the Letter
-
-The letter is open for signatures from individuals and organizations. If you work with MySQL-compatible databases and you believe the ecosystem deserves stronger community governance, add your name.
+If you run MySQL-compatible databases in production, the governance of those projects affects your licensing options, your ability to contribute upstream, and the long-term health of the tools you depend on. The letter is one place to make that stake visible.
 
 [**Sign the open letter →**](https://letter.3306-db.org/)