# AGNTCY, a Series of LF Projects: Contributing Guide Welcome to AGNTCY! We’re excited to welcome you to our community. Keep reading to learn more about how we’re building the Internet of Agents and where you can contribute. ## AGNTCY’s Mission AGNTCY aims to create a common infrastructure layer for AI agent-to-agent collaboration across the complete multi-agent software lifecycle: from discovery and identification, to communication, deployment, observability, and evaluation. This open, interoperable ecosystem aims to securely and seamlessly unite AI agents together, regardless of their provided framework, vendor or platform. ## Purpose and Charter Read more about the “why” behind AGNTCY via the [Operating Model document](OPERATING_MODEL.md). ## Code of Conduct AGNTCY has adopted the [Contributor Covenant](https://www.contributor-covenant.org/), ensuring a welcoming and respectful community. Please make sure to read and observe the [Code of Conduct](CODE_OF_CONDUCT.md) while participating in the project. ## Start Contributing! AGNTCY contains various sub-projects that you’re able to browse and interact with via Issues, Pull Requests, and Discussions in the overall project. Across AGNTCY, all new inbound code contributions must be accompanied by a Developer Certificate of Origin, or [DCO](http://developercertificate.org), sign-off. You must include a sign-off in the commit message of your Pull Request for it to be accepted. The format for a sign-off is: ``` Signed-off-by: Random J Developer ``` Each sub-project has their own CONTRIBUTING.md file where you can read up on the scope of the sub-project, how they complete reviews or submit bug reports, etc. ## Roles and Governance | Role | Responsibilities | Requirements | Defined By | | ---- | ---------------- | ------------ | ---------- | | Adopter | For those using and/or evangelizing AGNTCY in their organization | Your company name in the AGNTCY adopter list on GitHub | Companies that support AGNTCY through use of affiliated projects and shared belief in an open, interoperable Internet of Agents | | Contributor | Active contributor in the community, reviewer of PRs | Evidence of multiple contributions to AGNTCY projects | Members of GitHub organization | | Committer | Code review and approvals, help set project direction and priorities, possible Working Group lead | Highly experienced active contributor, author, and reviewer of a project | [CODEOWNERS](https://help.github.com/en/articles/about-code-owners) in GitHub, GitHub Team | | Technical Steering Committee | Responsible for all technical oversight of AGNTCY and its sub-projects | Core maintainer-based membership | Noted in org-level [CONTRIBUTING.md](#technical-steering-committee-members), GitHub Team | You can read more detail about each role in the [Operating Model document](OPERATING_MODEL.md). ### Technical Steering Committee Members Current TSC members in alphabetical order: - John Cardente (Dell Technologies, @jcardente-dell) - Kevin Cogan (Red Hat, @kevincogan) - Luca Muscariello (Cisco, @muscariello) - John Parello (Cisco, @jparello) - Anant Patel (Oracle, @AnantPatel44) - Todd Segal (Google Cloud, @ToddSegal) - Hema Seshadri (Akamai) - Marcelo Yannuzi (Cisco, @mayannuz) Emeritus TSC members: - Michael Clifford (Red Hat, @MichaelClifford) - Egor Pushkin (Oracle, @egorpushkin) ## Working Groups Working groups exist to delegate technical decision-making across the complete multi-agent software lifecycle: they are responsible for the design and implementation of large architectural aspects of the overall AGNTCY project. Working groups operate with a fair amount of autonomy within the broader scope of the project. The [Technical Steering Committee](#technical-steering-committee-members) is responsible for approving the creation of working groups to handle specific scopes of authority, spanning several sub-projects. The processes that govern working group formation, operation, and dissolution are defined per the [working group processes](WORKING-GROUP-PROCESSES.md) documentation. Contributions made under the direction and authority of working groups are expected to conform to the same processes defined in the AGNTCY [Operating Model](OPERATING_MODEL.md) document. For more information about our working groups, including leadership roles and scope definition, please see our [Working Groups](working-groups/WORKING-GROUPS.md) documentation. ## Community Engagement Alongside collaborating via GitHub with Issues, PRs, and Discussions, we welcome you to our Slack Workspace and Discord communities to continue discussing AGNTCY and its sub-projects. Join us at [agntcy.slack.com](https://agntcy.slack.com/archives/C0893S6D284) -- [AGNTCY Slack self join link](https://join.slack.com/t/agntcy/shared_invite/zt-3xozr6nzq-i6LXv2P8l2kVW4_Prnny2w). Component Discord communities: [SLIM](https://discord.gg/hdTDzBQe7D) and [Agent Directory (DIR)](https://discord.gg/FbEnSHXD34). To join the various community meetings that have been set up by AGNTCY working groups, see the [AGNTCY meeting calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/agntcy?view=week). ## License Distributed under the Apache 2.0 License. See [LICENSE](LICENSE.md) for more information. Copyright AGNTCY Contributors (https://github.com/agntcy).