How to Open-Source an Internal Tool: Lessons from Block's Goose Donation to the Linux Foundation

Overview

Internal tools can evolve into powerful external services—think Amazon's cloud becoming AWS. Block's Goose, a coding agent originally built for internal use, followed a similar path. After granting all 12,000 employees access, Block open-sourced Goose under a permissive license. However, the journey didn't end there. Block soon faced governance hurdles: trademark ownership remained with the company, hindering enterprise adoption. The solution? Donate Goose to a neutral foundation. This tutorial explains why Block chose the Agentic AI Foundation (AAIF)—a sub-organization under the Linux Foundation—and provides a step-by-step guide for any organization considering a similar move. You'll learn how to navigate governance, trademark transfers, and foundation selection based on Block's real-world experience.

Prerequisites

• An open-source project with a permissive license (e.g., Apache 2.0, MIT) and a community of users/contributors.
• Legal clearance to relicense or transfer trademarks; consult your legal team.
• Corporate buy-in from leadership and engineering teams.
• Basic knowledge of open-source foundations (e.g., Linux Foundation, Apache Software Foundation) and their governance models.

Step-by-Step Instructions

Step 1: Assess Governance Gaps

Block's first challenge was lack of transparency in governance. Goose wasn't fully open because Block still owned its trademarks. Enterprises hesitated to adopt a tool controlled by a single company. To avoid this, evaluate your project's governance:

• Identify ownership: List all assets (trademarks, domain names, copyrights) still held by your company.
• Survey adopters: Ask enterprise users if governance concerns block adoption.
• Document dependencies: Note any proprietary components in the codebase.

Example checklist:
- Trademark registered? ☐
- Contributing guidelines exist? ☐
- Decision-making process clear? ☐

Step 2: Engage Potential Partners

Block spoke with the Model Context Protocol (MCP) team, the Goose Crew, and Anthropic (MCP creators). They discovered a shared vision for agentic AI governance. Reach out to:

• Related open-source communities (e.g., MCP, Agents.MD).
• Foundations that host similar projects.
• Vendors or users invested in the tool's success.

Form a steering committee to discuss a neutral home. Document agreements in a Memorandum of Understanding (MOU).

Step 3: Choose the Right Foundation

Block evaluated several foundations but chose the Agentic AI Foundation (AAIF), an arm of the Linux Foundation. Factors to consider:

• Neutrality: Foundation should have no single corporate sponsor dominating decisions.
• Brand management: Ensure the foundation can handle trademark transfers and enforce usage policies.
• Community size: Larger foundations offer better exposure and support (e.g., Linux Foundation).
• Expediency: AAIF launched quickly because it started with a trio of tools (Goose, MCP, Agents.MD).

Common foundation options:

Foundation	Best For
Apache Software Foundation	Strict governance, long-term incubation
Linux Foundation	Vendor-neutral, large projects, sub-foundations
Eclipse Foundation	Java-centric, strong IP management

Step 4: Transfer Trademarks and IP

Block owned Goose's trademarks, which hampered enterprise adoption. To transfer:

1. Assign trademarks: Execute a trademark assignment agreement with the foundation.
2. Sub-license code: Relicense the codebase under a neutral entity like the foundation's copyright holder.
3. Update documentation: Change all references from "Block's Goose" to "Goose (a Linux Foundation project)".

Sample license header update:
/* Copyright 2025 Agentic AI Foundation. Licensed under Apache 2.0 */

Step 5: Set Up Governance Policies

With the foundation now owning the IP, establish transparent governance:

• Technical Steering Committee (TSC): Composed of contributors from different organizations (AWS, Anthropic, Block, etc.).
• Code of Conduct: Adopt a standard (e.g., Contributor Covenant).
• Contribution process: Require CLA (Contributor License Agreement) signatures via the foundation.
• Release management: Use semantic versioning and release managers voted by the TSC.

Step 6: Announce and Migrate

Block publicly announced the donation via a blog post and at an MCP developer event. Best practices:

• Coordinate announcement with the foundation's marketing team.
• Update repository URLs to the foundation's GitHub organization.
• Redirect old documentations and package registries.
• Hold an AMA (Ask Me Anything) for the community.

Common Mistakes

Mistake 1: Donating Without Addressing Trademark Ownership

Block learned that retaining trademarks created "headwinds." Enterprises need assurance that the project won't be forked or controlled by one vendor. Always transfer trademarks to the foundation.

Mistake 2: Choosing a Foundation Too Quickly

Don't pick a foundation just because it's popular. Block spoke with MCP, Goose Crew, and Anthropic before aligning with AAIF. Evaluate multiple options and involve community voices.

Mistake 3: Neglecting Legal Costs

Trademark transfers, licensing audits, and CLA management can be expensive. Budget for legal fees early—expect $10,000–$50,000 depending on complexity.

Mistake 4: Forgetting to Update all Artifacts

After migration, check every place the project name appears: Twitter handles, Docker images, npm packages. Use a script to find stale references.

Summary

Block's donation of Goose to the Linux Foundation's Agentic AI Foundation illustrates the importance of neutral governance for open-source projects. By following these six steps—assessing governance gaps, engaging partners, choosing a foundation, transferring IP, setting up policies, and announcing—you can avoid the pitfalls Block encountered. The result? A project that can truly take flight, unencumbered by corporate ownership. Remember: transparency speeds adoption, and a foundation is your launchpad.