From Internal Tool to Open-Source Powerhouse: A Guide to Navigating Governance and Foundation Donation

Overview

When your internal tool gains traction beyond your organization, it can feel like you’ve stumbled onto something big. That’s exactly what happened at Block (the fintech company behind Square and Cash App) with Goose, an AI coding agent initially built for internal use. After open-sourcing Goose under a permissive license, Block faced unexpected headwinds: the project was technically free, but because Block retained trademarks and governance, enterprises were hesitant to adopt. The solution? Donate Goose to a neutral foundation. This guide walks through the journey of Goose from internal tool to a project housed under the Linux Foundation’s Agentic AI Foundation (AAIF). You’ll learn the prerequisites for considering a foundation donation, step-by-step instructions based on Block’s real experience, and common pitfalls to avoid. Whether you’re managing an internal tool that might become an external success or simply curious about open-source governance, this tutorial will equip you with actionable insights.

From Internal Tool to Open-Source Powerhouse: A Guide to Navigating Governance and Foundation Donation — Source: thenewstack.io

Prerequisites

Before you consider donating a project to a foundation, ensure your organization has these elements in place:

Open-source readiness: The codebase should be modular, documented, and free of proprietary secrets. Goose was already open-sourced under a permissive license, which demonstrates initial preparation.
Community traction: Have real users outside your company. Goose saw rapid early adoption, making it attractive to a foundation.
Commitment to neutrality: Leadership must accept that a foundation will control trademarks and governance. Block’s head of open-source, Manik Surtani, championed this shift.
Foundation alignment: Research foundations that align with your project’s domain. Goose’s AI agent focus made the Linux Foundation’s new AAIF a natural fit, especially when combined with MCP and Agents.MD.

Step-by-Step Instructions

Step 1: Assess Your Governance Gap

After open-sourcing Goose, Block faced “headwinds” due to a lack of transparency in governance. The biggest issue: Block still owned the trademarks, which hampered enterprise adoption. Identify your governance gaps: Are you the sole decision-maker? Do you control the brand? Is there a clear contribution process? Document these before proceeding.

Step 2: Explore Foundation Options

Talk to foundations that already host similar projects. Surtani discussed with the MCP team (from Anthropic) and the broader MCP community. The Linux Foundation had just launched the Agentic AI Foundation (AAIF), which was looking for founding projects. Expediency played a role: launching the AAIF with Goose, MCP, and Agents.MD allowed quick momentum. Compare foundation rules, fees, and level of support.

Step 3: Transfer Intellectual Property

You’ll need to assign copyrights and trademarks to the foundation. For Goose, Block transferred the codebase and trademarks to the AAIF. This requires legal work: draft a contribution agreement, ensure no third-party IP conflicts, and get board approval. Use a standard contributor license agreement (CLA) if your project already has external contributors.

Step 4: Establish Governance Model

Work with the foundation to define a transparent governance structure. For AAIF, the initial technical oversight committee (TOC) included representatives from Block, Anthropic, and the MCP community. Create documents that outline:

How maintainers are elected
Decision-making processes (e.g., lazy consensus)
Release schedule and security policies

Example governance snippet (markdown):

# Governance for Goose
- **Project Lead**: Elected annually by TOC
- **Commits**: Requires two approvals from maintainers
- **Trademark Use**: Must follow LF brand guidelines

This replaces arbitrary Block control with a community-owned framework.

Step 5: Announce and Onboard Community

Prepare a joint announcement with the foundation. Highlight the benefits: neutral governance, trademark protection for users, and long-term sustainability. Surtani’s interview with The New Stack exemplifies this outreach. Update your README, website, and documentation to reflect the new home. Mention the foundation’s legal entity in all licensing headers.

Step 6: Transition Operations

Set up new CI/CD pipelines under the foundation’s infrastructure. Migrate issue tracking, code repositories, and mailing lists. For Goose, the code moved to a repository under the AAIF organization on GitHub. Ensure continuous operations during the transition: no service disruption for existing users.

Common Mistakes

Based on Block’s experience and other similar projects, avoid these errors:

Retaining trademarks: If you keep the brand, enterprises will worry you could revoke usage. Block’s initial grip on Goose trademarks was the primary barrier to adoption. Donate everything to the foundation.
Choosing the wrong foundation: Not all foundations are created equal. Pick one with domain expertise and a supportive community. Goose succeeded because AAIF was purpose-built for AI agent tools.
Lack of community consultation: Engage with existing contributors and users before the move. Surprising them can create resistance. In Goose’s case, early talks with MCP stakeholders smoothed the transition.
Underestimating legal costs: Transferring IP requires lawyers. Budget for this upfront.
Moving too slowly: Surtani cited expediency as a reason for launching AAIF quickly. A drawn-out transfer can cause community atrophy.

Summary

Goose’s journey from Block’s internal tool to a cornerstone of the Linux Foundation’s Agentic AI Foundation illustrates a proven path for open-source success. The key lesson: governance matters. By ceding control of trademarks and decision-making to a neutral foundation, Block unlocked enterprise trust and community growth. This guide outlined six steps—assess, explore, transfer, govern, announce, transition—and highlighted pitfalls like retaining trademarks or choosing a mismatched foundation. If you’re currently incubating an internal tool with external potential, begin the governance conversation early. Talk to foundations, prepare your IP, and be ready to let go. The result? A project that can truly soar, just like Goose.

Tags: