|
1 | 1 | # Agent2Agent (A2A) Governance |
2 | 2 |
|
3 | | -**The Agent to Agent project is governed by the Technical Steering Committee. The Committee has seven seats, each held by the following companies:** |
| 3 | +The Agent2Agent project is governed by the Technical Steering Committee. The Committee has eight seats, each held by the following companies: |
4 | 4 |
|
5 | | -1. Google - Todd Segal, Principal Engineer - [@ToddSegal](https://github.com/ToddSegal) |
6 | | -2. Microsoft - Darrel Miller, Partner API Architect - [@darrelmiller](https://github.com/darrelmiller) |
7 | | -3. Cisco - Luca Muscariello, Principal Engineer - [@muscariello](https://github.com/muscariello) |
8 | | -4. Amazon Web Services - Nicholas Aldridge, Principal Engineer - [@000-000-000-000-000](https://github.com/000-000-000-000-000) |
9 | | -5. Salesforce - Sam Sharaf, Sr. Director Product Management - [@samuelsharaf](https://github.com/samuelsharaf) |
10 | | -6. ServiceNow - Sean Hughes, AI Ecosystem Director - [@hughesthe1st](https://github.com/hughesthe1st) |
11 | | -7. SAP - Sivakumar N., Vice President - [LinkedIn](https://www.linkedin.com/in/siva-kumar-n/) |
| 5 | +| Company | Representative | Title | Contact | |
| 6 | +| :--- | :--- | :--- | :--- | |
| 7 | +| **Google** | Todd Segal | Principal Engineer | [@ToddSegal](https://github.com/ToddSegal) | |
| 8 | +| **Microsoft** | Darrel Miller | Partner API Architect | [@darrelmiller](https://github.com/darrelmiller) | |
| 9 | +| **Cisco** | Luca Muscariello | Principal Engineer | [@muscariello](https://github.com/muscariello) | |
| 10 | +| **Amazon Web Services** | Nicholas Aldridge | Principal Engineer | [@000-000-000-000-000](https://github.com/000-000-000-000-000) | |
| 11 | +| **Salesforce** | Sam Sharaf | Sr. Director Product Management | [@samuelsharaf](https://github.com/samuelsharaf) | |
| 12 | +| **ServiceNow** | Sean Hughes | AI Ecosystem Director | [@hughesthe1st](https://github.com/hughesthe1st) | |
| 13 | +| **SAP** | Sivakumar N. | Vice President | [LinkedIn](https://www.linkedin.com/in/siva-kumar-n/) | |
| 14 | +| **IBM Research** | Kate Blair | Director of Incubation | [@geneknit](https://github.com/geneknit) | |
12 | 15 |
|
13 | 16 | ## Mission and Scope of the Project |
14 | 17 |
|
15 | | -1. The mission of the Project is to help AI agents across different ecosystems communicate with each other. The Project includes collaborative development of the following components: |
16 | | - 1. the Agent2Agent Protocol (the "Protocol"); |
17 | | - 2. a SDK for designing implementations of the Protocol and related software components; and |
18 | | - 3. documentation and other artifacts related to the Project. |
| 18 | +1. The mission of the Project is to help AI agents across different ecosystems communicate with each other. The Project includes collaborative development of the following components: |
| 19 | + |
| 20 | + 1. the Agent2Agent Protocol (the "Protocol"); |
| 21 | + |
| 22 | + 2. a SDK for designing implementations of the Protocol and related software components; and |
| 23 | + |
| 24 | + 3. documentation and other artifacts related to the Project. |
| 25 | + |
19 | 26 | 2. The scope of the Project includes collaborative development under the Project License (as defined herein) supporting the mission, including documentation, testing, integration and the creation of other artifacts that aid the development, deployment, operation or adoption of the open source project. |
20 | 27 |
|
21 | 28 | ## Technical Steering Committee |
22 | 29 |
|
23 | 30 | 1. The Technical Steering Committee (the "TSC") will be responsible for all technical oversight of the open source Project. |
24 | | -2. TSC Composition |
25 | | - a. "Startup Phase." At the inception of the Project, each organization listed in the [`GOVERNANCE`](GOVERNANCE.md) file in the governance repository of the Project will have the right to appoint (and remove and replace) one employee to serve as a voting member of the TSC. |
26 | | - b. "Steady State." The TSC will decide upon a "steady state" composition of the TSC (whether by election, sub-project technical leads, or other method as determined by the TSC) for composition of the TSC from the date that is 18 months following the inception of the Project, or at such other point as determined by the TSC. |
27 | | -The TSC may choose an alternative approach for determining the voting members of the TSC, and any such alternative approach will be documented in the GOVERNANCE file. Any meetings of the Technical Steering Committee are intended to be open to the public, and can be conducted electronically, via teleconference, or in person. |
| 31 | +2. **TSC Composition** |
| 32 | + |
| 33 | + a. **"Startup Phase."** At the inception of the Project, each organization listed in the [`GOVERNANCE`](GOVERNANCE.md) file in the governance repository of the Project will have the right to appoint (and remove and replace) one employee to serve as a voting member of the TSC. |
| 34 | + |
| 35 | + b. **"Steady State."** The TSC will decide upon a "steady state" composition of the TSC (whether by election, sub-project technical leads, or other method as determined by the TSC) for composition of the TSC from the date that is 18 months following the inception of the Project, or at such other point as determined by the TSC. |
| 36 | + |
| 37 | + c. The TSC may choose an alternative approach for determining the voting members of the TSC, and any such alternative approach will be documented in the GOVERNANCE file. Any meetings of the Technical Steering Committee are intended to be open to the public, and can be conducted electronically, via teleconference, or in person. |
| 38 | + |
28 | 39 | 3. TSC projects generally will involve Contributors and Maintainers. The TSC may adopt or modify roles so long as the roles are documented in the CONTRIBUTING file. Unless otherwise documented: |
29 | | - a. Contributors include anyone in the technical community that contributes code, documentation, or other technical artifacts to the Project; |
30 | | - b. Maintainers are Contributors who have earned the ability to modify ("commit") source code, documentation or other technical artifacts in a project's repository; and |
31 | | - c. A Contributor may become a Maintainer by a vote of the TSC. A Maintainer may be removed by a vote of the TSC. |
32 | | - d. Participation in the Project through becoming a Contributor and Maintainer is open to anyone so long as they abide by the terms of this Charter. |
33 | | -4. The TSC may (1) establish work flow procedures for the submission, approval, and closure/archiving of projects, (2) set requirements for the promotion of Contributors to Maintainer status, as applicable, and (3) amend, adjust, refine and/or eliminate the roles of Contributors, and Maintainer, and create new roles, and publicly document any TSC roles, as it sees fit. |
| 40 | + |
| 41 | + a. **Contributors** include anyone in the technical community that contributes code, documentation, or other technical artifacts to the Project; |
| 42 | + |
| 43 | + b. **Maintainers** are Contributors who have earned the ability to modify ("commit") source code, documentation or other technical artifacts in a project's repository; and |
| 44 | + |
| 45 | + c. A Contributor may become a Maintainer by a vote of the TSC. A Maintainer may be removed by a vote of the TSC. |
| 46 | + |
| 47 | + d. Participation in the Project through becoming a Contributor and Maintainer is open to anyone so long as they abide by the terms of this Charter. |
| 48 | +4. The TSC may: |
| 49 | + 1. establish work flow procedures for the submission, approval, and closure/archiving of projects, |
| 50 | + 2. set requirements for the promotion of Contributors to Maintainer status, as applicable, and |
| 51 | + 3. amend, adjust, refine and/or eliminate the roles of Contributors, and Maintainer, and create new roles, and publicly document any TSC roles, as it sees fit. |
34 | 52 | 5. The TSC may elect a TSC Chair, who will preside over meetings of the TSC and will serve until their resignation or replacement by the TSC. |
35 | | -6. Responsibilities: The TSC will be responsible for all aspects of oversight relating to the Project, which may include: |
36 | | - 1. coordinating the technical direction of the Project; |
37 | | - 2. approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to a sub-project's scope); |
38 | | - 3. organizing sub-projects and removing sub-projects; |
39 | | - 4. creating sub-committees or working groups to focus on cross-project technical issues and requirements; |
40 | | - 5. appointing representatives to work with other open source or open standards communities; |
41 | | - 6. establishing community norms, workflows, issuing releases, and security issue reporting policies; |
42 | | - 7. approving and implementing policies and processes for contributing (to be published in the [`CONTRIBUTING`](CONTRIBUTING.md) file) and coordinating with the series manager of the Project (as provided for in the Series Agreement, the "Series Manager") to resolve matters or concerns that may arise as set forth in Section 7 of this Charter; |
43 | | - 8. discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; and |
44 | | - 9. coordinating any marketing, events, or communications regarding the Project. |
45 | | - |
46 | | -## TSC Voting |
| 53 | +6. **Responsibilities:** The TSC will be responsible for all aspects of oversight relating to the Project, which may include: |
| 54 | + 1. coordinating the technical direction of the Project; |
| 55 | + 2. approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to a sub-project's scope); |
| 56 | + 3. organizing sub-projects and removing sub-projects; |
| 57 | + 4. creating sub-committees or working groups to focus on cross-project technical issues and requirements; |
| 58 | + 5. appointing representatives to work with other open source or open standards communities; |
| 59 | + 6. establishing community norms, workflows, issuing releases, and security issue reporting policies; |
| 60 | + 7. approving and implementing policies and processes for contributing (to be published in the [`CONTRIBUTING`](CONTRIBUTING.md) file) and coordinating with the series manager of the Project (as provided for in the Series Agreement, the "Series Manager") to resolve matters or concerns that may arise as set forth in Section 7 of this Charter; |
| 61 | + 8. discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; and |
| 62 | + 9. coordinating any marketing, events, or communications regarding the Project. |
| 63 | + |
| 64 | +### TSC Voting |
47 | 65 |
|
48 | 66 | While the Project aims to operate as a consensus-based community, if any TSC decision requires a vote to move the Project forward, the voting members of the TSC will vote on a one vote per voting member basis. |
| 67 | + |
49 | 68 | Quorum for TSC meetings requires at least fifty percent of all voting members of the TSC to be present. The TSC may continue to meet if quorum is not met but will be prevented from making any decisions at the meeting. Except as provided in Section 7.c. and 8.a, decisions by vote at a meeting require a majority vote of those in attendance, provided quorum is met. Decisions made by electronic vote without a meeting require a majority vote of all voting members of the TSC. |
50 | 69 |
|
| 70 | +### TSC Meetings |
| 71 | + |
| 72 | +Our hope is that the first TSC meeting will be held in August 2025. Once the TSC representatives are finalized, scheduling will begin. In the interim we have drafted a [working doc for TSC Meeting Agendas](https://docs.google.com/document/d/1Dx6qYfCjSChHKRMwLJcvtDjq6igYTAKFW9Vg1IMPCUk/view). |
| 73 | + |
51 | 74 | ## Project Communications |
52 | 75 |
|
53 | | -The A2A project utilizes Discord for chat conversations about the project. All are welcome and encouraged to join the [A2A Discord](http://discord.gg/a2aprotocol). Discussion is encouraged however we do remind the community that chat is ephemeral, and not all members of the project are active in chat at the same time. Therefore, any discussions about feature proposals, significant changes to the project architecture or governance, etc. should be held in GitHub with adequate notice and time for comment. Look for specifics on that timing coming soon as the TSC ramps up. Just keep in mind - our goal is that GitHub is the source of truth for significant project decisions. |
54 | | -Additional communication avenues will likely be added - stay tuned. |
| 76 | +The A2A project utilizes Discord for chat conversations about the project. All are welcome and encouraged to join the [A2A Discord](http://discord.gg/a2aprotocol). Discussion is encouraged however we do remind the community that chat is ephemeral, and not all members of the project are active in chat at the same time. |
55 | 77 |
|
56 | | -## TSC Meetings |
| 78 | +Therefore, any discussions about feature proposals, significant changes to the project architecture or governance, etc. should be held in GitHub with adequate notice and time for comment. Look for specifics on that timing coming soon as the TSC ramps up. Just keep in mind - our goal is that GitHub is the source of truth for significant project decisions. |
57 | 79 |
|
58 | | -Our hope is that the first TSC meeting will be held in August 2025. Once the TSC representatives are finalized, scheduling will begin. In the interim we have drafted a [working doc for TSC Meeting Agendas](https://docs.google.com/document/d/1Dx6qYfCjSChHKRMwLJcvtDjq6igYTAKFW9Vg1IMPCUk/view). |
| 80 | +Additional communication avenues will likely be added - stay tuned. |
0 commit comments