Governance

goose is an open-source project that operates under a community-driven governance model to ensure transparency, inclusivity, and sustainable development. This page outlines the project's governance structure and provides guidelines for community participation, helping new contributors understand how decisions are made and how they can get involved.

Project Governance Structure

The governance of goose follows a structure common to many open-source projects, emphasizing collaboration while maintaining efficiency. At its core, the project is maintained by a team of core contributors, often referred to as maintainers, who oversee major decisions, code merges, and project direction. This structure promotes accountability and allows for rapid iteration on features like AI automation and extensibility.

Key Components of the Structure

• Core Maintainers: A small group of experienced individuals, including the original creators from Block, holds decision-making authority. They review pull requests, resolve conflicts, and guide the project's roadmap. This design decision ensures that the project aligns with its mission of providing a reliable, extensible AI agent for developers, while preventing fragmentation.

• Contributors: Anyone in the community can contribute code, documentation, or ideas. Contributions are evaluated based on merit, adhering to the project's standards for quality and security. For example, all code submissions must pass automated tests, as seen in the project's CI workflows. This decentralized approach fosters innovation, allowing users to extend features like LLM support or custom distributions through pull requests.

• Decision-Making Process: Major decisions, such as changes to the core architecture or licensing, require consensus among core maintainers. For routine matters, like bug fixes or feature enhancements, decisions are made through community discussions on platforms like Discord. This process balances speed with inclusivity, drawing from the Apache 2.0 license's emphasis on open collaboration.

The governance model draws inspiration from successful open-source projects, prioritizing sustainability. By limiting core decision-makers, goose avoids common pitfalls like decision paralysis, while still encouraging broad participation. For more on how to contribute code or features, see the Contributing page.

Community Participation Guidelines

Community participation is essential to goose's growth, as it relies on diverse input to improve features like workflow automation and API integration. These guidelines outline how individuals can engage effectively, ensuring a positive and productive environment.

Ways to Participate

• Contributing Code and Features: Community members can submit pull requests for new features, bug fixes, or improvements. For instance, extending LLM support might involve adding a new configuration option, as demonstrated in the following example from the project's source code:

// Example of a custom LLM configuration in goose's code
type LLMConfig struct {
    Provider string `json:"provider"` // e.g., "openai" or "custom"
    APIKey   string `json:"api_key"`
    Model    string `json:"model"`    // e.g., "gpt-4"
}

// Users can contribute by adding new providers in similar structs

This code snippet illustrates how configurations are structured, allowing contributors to build on existing patterns for extensibility.

• Reporting Issues and Feedback: Participants can report bugs or suggest enhancements via the project's issue tracker. This helps refine aspects like performance and security, ensuring the project remains robust.

• Discussions and Collaboration: Join community discussions on Discord to share ideas or seek advice. These forums facilitate knowledge sharing, such as best practices for integrating goose with external APIs, as covered in API Integration.

Code of Conduct

All participants must adhere to a code of conduct that promotes respect, inclusivity, and professionalism. This includes being courteous in discussions, giving credit for contributions, and avoiding spam or disruptive behavior. Violations are addressed by core maintainers to maintain a welcoming environment, which is crucial for attracting diverse contributors who enhance features like tutorials and troubleshooting.

By following these guidelines, community members can actively shape goose's evolution, from debugging tools to custom distributions. For detailed steps on getting started, refer to the Contributing and Quickstart pages. This structure not only sustains the project but also aligns with its goal of empowering developers through open-source AI tools.