diff --git a/CHIPS_Alliance-Technical_Charter.pdf b/CHIPS_Alliance-Technical_Charter.pdf deleted file mode 100644 index 07a2d07..0000000 Binary files a/CHIPS_Alliance-Technical_Charter.pdf and /dev/null differ diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index fc00024..93370b3 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,13 +2,13 @@ CHIPS Alliance is a group of open source projects which develop high-quality, open source hardware designs relevant to silicon devices and FPGAs. By creating an open and collaborative environment, CHIPS Alliance shares resources to lower the cost of development. All CHIPS Alliance development occurs on [GitHub](https://github.com/chipsalliance), following open source best practices. -The technical projects under the CHIPS Alliance TSC are supported by the [CHIPS Alliance](https://chipsalliance.org), an independent nonprofit organization with open and neutral governance, hosted under the [Linux Foundation](https://linuxfoundation.org). +The technical projects under the CHIPS Alliance TAC are supported by the [CHIPS Alliance](https://chipsalliance.org), an independent nonprofit organization with open and neutral governance, hosted under the [Linux Foundation](https://linuxfoundation.org). [Learn more about the CHIPS Alliance ยป](https://chipsalliance.org) ## Technical governance -CHIPS Alliance follows industry best practices, with the technical project and its governance distinctly separate from [CHIPS Alliance membership](https://chipsalliance.org/join). The [Technical Charter](https://github.com/chipsalliance/tsc/blob/master/https://technical-charter.chipsalliance.org) establishes the CHIPS Alliance Technical Steering Committee as the body which oversees all technical aspects of the open source project. By contrast, the [CHIPS Alliance Governing Board](https://chipsalliance.org/about/governance/) is responsible for raising and distributing funds to support project activities, and setting policy. While the two groups are separate, they work in close coordination to establish, guide, and support activities that lead to a long-term, sustainable future for CHIPS Alliance. +CHIPS Alliance follows industry best practices, with the technical project and its governance distinctly separate from [CHIPS Alliance membership](https://chipsalliance.org/join). The [Charter](https://participation-agreement.chipsalliance.org/) establishes the CHIPS Alliance Technical Advisory Council (TAC) as the body which oversees all technical aspects of the open source project. By contrast, the [CHIPS Alliance Governing Board](https://chipsalliance.org/about/governance/) is responsible for raising and distributing funds to support project activities, and setting policy. While the two groups are separate, they work in close coordination to establish, guide, and support activities that lead to a long-term, sustainable future for CHIPS Alliance. ### Contributors @@ -18,7 +18,7 @@ Contributors are any members of the open source community who participate in pro Committers are members of the contributor community who have demonstrated an ongoing commitment to the health and sustainability of the CHIPS Alliance project through good citizenship and wise stewardship. These individuals have been elevated to a decision-making role, and responsible for reviewing and merging code from contributors. They may also be involved in the release process or other critical project roles. -The path to committership starts with becoming a contributor to the project. Over time, contributors can prove that they have high commitment to the project. Top contributors may become committers through either a simple majority vote by the existing committers, or by a 2/3 vote of the TSC. An existing committer may be removed in the same manner. +The path to committership starts with becoming a contributor to the project. Over time, contributors can prove that they have high commitment to the project. Top contributors may become committers through either a simple majority vote by the existing committers, or by a 2/3 vote of the TAC. An existing committer may be removed in the same manner. Each potential committer should be nominated prior to the vote. The nomination should include a justification of why that person should become a committer (e.g., code/test/doc contributions, other positive impact to the project & community, etc.). @@ -41,9 +41,9 @@ Committership can be revoked under rare circumstances, such as when a committer #### Ensure your contribution complies with the CHIPS Alliance IP Policy -All contributions to CHIPS Alliance projects must adhere to the [CHIPS Alliance IP policy](https://github.com/chipsalliance/tsc/blob/master/https://technical-charter.chipsalliance.org#7-intellectual-property-policy). +All contributions to CHIPS Alliance projects must adhere to the [CHIPS Alliance IP policy](https://participation-agreement.chipsalliance.org/). -Please review the [Technical Charter](https://technical-charter.chipsalliance.org) to ensure you understand the requirements of the open source project. If you have questions, please [file an issue](https://github.com/chipsalliance/tsc/issues). +Please review the [Charter](https://participation-agreement.chipsalliance.org/) to ensure you understand the requirements of the open source project. If you have questions, please [file an issue](https://github.com/chipsalliance/tsc/issues). #### Sign the CLA diff --git a/README.md b/README.md index 9272dec..a1ca643 100644 --- a/README.md +++ b/README.md @@ -1,39 +1,33 @@ -# CHIPS Alliance Technical Steering Committee (TSC) +# CHIPS Alliance Technical Advisory Council (TAC) -The CHIPS Alliance TSC will be responsible for all technical oversight of the open source project. +The CHIPS Alliance TAC will be responsible for all technical oversight of the open source project. ## Technical Charter and Code of Conduct -The CHIPS Alliance TSC is governed by a [Technical Charter](https://technical-charter.chipsalliance.org), which establishes the Committee and its basic principles and procedures. The charter is designed to provide the TSC the freedom to govern itself in an efficient manner. This document establishes TSC policies and procedures. +The CHIPS Alliance TAC is governed by tha [CHIPS Alliance Charter](https://participation-agreement.chipsalliance.org/), which establishes the Council and its basic principles and procedures. The charter is designed to provide the TAC the freedom to govern itself in an efficient manner. This document establishes TAC policies and procedures. -In addition, as provided under the Technical Charter, CHIPS Alliance has adopted a [Code of Conduct](https://lfprojects.org/policies/code-of-conduct/) that applies to all CHIPS Alliance activities and spaces. +In addition, as provided under the Charter, CHIPS Alliance has adopted a [Code of Conduct](https://lfprojects.org/policies/code-of-conduct/) that applies to all CHIPS Alliance activities and spaces. -## TSC voting members and Graduated projects +## TAC Voting Members and Graduated projects -Per the Technical Charter, on top of any members appointed in the initial bootstrap phase, the TSC will be comprised of one representative from each Graduated project. +Per the Charter, the voting members of the TAC are composed of one representative appointed by each Platinum Member and one representative appointed by the technical oversight body (e.g., a technical steering committee) of each Graduated Project. -The current members of the CHIPS Alliance TSC are: +The current members of the CHIPS Alliance TAC are: -| Name | GitHub | Affiliation | Project | -| -------------------| ------------------------------------------------------- | -----------------------|---------------------------| -| Henry Cook (chair) | [hcook](https://github.com/hcook) | SiFive | (chair) | -| Michael Gielda | [mgielda](https://github.com/mgielda) | Antmicro | (mktg) | -| Henner Zeller | [hzeller](https://github.com/hzeller) | Google | Verible | -| Alain Dargelas | [alainmarcel](https://github.com/alainmarcel) | unaffiliated | Surelog/UHDM | -| Mehdi Saligane | [msaligane](https://github.com/msaligane) | University of Michigan | OpenFASOC | -| Tom Gorochowik | [tgorochowik](https://github.com/tgorochowik) | Antmicro | SV tests / FPGA tool perf | -| Maciej Kurc | [mkurc-ant](https://github.com/mkurc-ant) | Antmicro | FPGA Interchange | -| David Kehlet | [dkehlet](https://github.com/dkehlet) | Intel | AIB | -| Matt Cockrell | [mcockrell-google](https://github.com/mcockrell-google) | Google | RISC-V DV | -| Tom Michalak | [tmichalak](https://github.com/tmichalak) | Antmicro | F4PGA | -| Mikhail Moiseev | [mikhailmoiseev](https://github.com/mikhailmoiseev) | Intel | SystemC compiler | -| Jiuyang Liu | [sequencer](https://github.com/sequencer) | PLCT Lab, ISCAS | Rocket Chip | -The [Technical Charter](https://technical-charter.chipsalliance.org) describes the composition of the TSC. + +| Name | GitHub | Affiliation | Role / Projec | +| ------------------------| ------------------------------------------------------- | -----------------------|---------------------------| +| Stephano Cetola (Chair) | [cetola](https://github.com/cetola) | Intel | Platinum Voting Rep | +| Michael Gielda | [mgielda](https://github.com/mgielda) | Antmicro | Platinum Voting Rep | +| Danny Hua | | Futurewei | Platinum Voting Rep | +| Prabhu Jayanna | | AMD | Platinum Voting Rep | +| Bryan Kelly | [bryankel](https://github.com/Bryankel) | Microsoft | Platinum Voting Rep | +| Mirjana Videnovic-Misic | | Infineon | Platinum Voting Rep | ## Sandbox projects list -In addition to Graduated projects which delegate one member each to the TSC (see the table above), there are also Sandbox projects which are on the path to joining although are not fully/formally incorporated into CHIPS Alliance yet. +In addition to Graduated projects which delegate one member each to the TAC (see the table above), there are also Sandbox projects which are on the path to joining although are not fully/formally incorporated into CHIPS Alliance yet. See [Sandbox projects](./projects/sandbox) for a list of projects currently in Sandbox. @@ -45,7 +39,7 @@ To see an up-to-date list, visit [the Workgroups section of the CHIPS website](h ## Getting oriented -This repo documents the day-to-day policies and procedures of the CHIPS Alliance TSC. It provides a framework for self-governance, and addresses topics too granular for the [Technical Charter](https://technical-charter.chipsalliance.org). +This repo documents the day-to-day policies and procedures of the CHIPS Alliance TAC. It provides a framework for self-governance, and addresses topics too granular for the [Charter](https://participation-agreement.chipsalliance.org/). This repository has the following structure: @@ -58,7 +52,7 @@ Here are some other links to help you find your way: * [An introduction to our collaboration tools](#collaboration-tools) * [Our policies and procedures](#policies-and-procedures) -* [The current voting members of the TSC](#tsc-voting-members-and-graduated-projects) (please note anyone can participate in our [meetings](#calendars-and-meetings) as a non-voting attendee) +* [The current voting members of the TAC](#tac-voting-members-and-graduated-projects) (please note anyone can participate in our [meetings](#calendars-and-meetings) as a non-voting attendee) * [Projects and Workgroups of the CHIPS Alliance](#projects-and-workgroups) Finally, if you need help, please [reach out and ask](#getting-help). @@ -67,7 +61,7 @@ Finally, if you need help, please [reach out and ask](#getting-help). ### Mailing list -The CHIPS Alliance TSC can be reached at [technical-discuss](https://lists.chipsalliance.org/g/technical-discuss). This mailing list is open for anyone to join, and all are welcome to participate in general technical discussions about the project. +The CHIPS Alliance TAC can be reached at [technical-discuss](https://lists.chipsalliance.org/g/technical-discuss). This mailing list is open for anyone to join, and all are welcome to participate in general technical discussions about the project. ### Slack @@ -75,51 +69,39 @@ The CHIPS Alliance maintains a [Slack Workspace](https://slack.chipsalliance.org ### Calendars and meetings -The CHIPS Alliance maintains a [public calendar](https://calendar.chipsalliance.org) for TSC meetings. These meetings are open for anyone to join. +The CHIPS Alliance maintains a [public calendar](https://calendar.chipsalliance.org) for TAC meetings. These meetings are open for anyone to join. CHIPS Alliance uses Zoom for meetings. Because we work in a highly distributed environment and will rarely meet in person, participants are encouraged to use video as appropriate. -To join a TSC meeting: [https://zoom.us/j/96738269957](https://zoom.us/j/96738269957) (pw: chipstsc) ## Projects and Workgroups -The TSC is granted oversight over all CHIPS Alliance technical projects and workgroups. In CHIPS Alliance, similar technical projects are organized into workgroups. Each project is represented within the workgroup's internal governance structure. Likewise, each workgroup selects a member to represent it as a voting member of the TSC, using an open and transparent selection process. +The TAC is granted oversight over all CHIPS Alliance technical projects and workgroups. In CHIPS Alliance, similar technical projects are organized into workgroups. Each project is represented within the workgroup's internal governance structure. ### Mission statements -Each project must have a mission statement ([template](./projects/MISSION_STATEMENT_TEMPLATE.md)) which describes its purpose and governance. Changes to mission statements must be reviewed and approved by the TSC. +Each project must have a mission statement ([template](./projects/MISSION_STATEMENT_TEMPLATE.md)) which describes its purpose and governance. Changes to mission statements must be reviewed and approved by the TAC. ### Lifecycle -Each project is categorized according to a [project lifecycle process](./projects/), managed by the TSC. Projects and workgroups will have different maturity levels, and the lifecycle process seeks to balance their needs and expectations with available resources. +Each project is categorized according to a [project lifecycle process](./projects/), managed by the TAC. Projects and workgroups will have different maturity levels, and the lifecycle process seeks to balance their needs and expectations with available resources. #### Project categories -* **[Sandbox](projects/README.md#sandbox)**: Optional pre-membership stage to help a project prepare for the TSC's consideration. Sandbox projects are not yet part of CHIPS Alliance, but may be allocated TSC resources to help with the process. -* **[Graduated](projects/README.md#graduated)**: A project which has been accepted by the TSC, assigned to a workgroup, met the graduation requirements, and demonstrated sustainable momentum. +* **[Sandbox](projects/README.md#sandbox)**: Optional pre-membership stage to help a project prepare for the TAC's consideration. Sandbox projects are not yet part of CHIPS Alliance, but may be allocated TAC resources to help with the process. +* **[Graduated](projects/README.md#graduated)**: A project which has been accepted by the TAC, assigned to a workgroup, met the graduation requirements, and demonstrated sustainable momentum. * **[Archived](projects/README.md#archived)**: A former Graduated project which has been archived for strategic or practical reasons. #### Workgroup levels -* **Active**: Contains at least one Graduated project, or a majority of the TSC has voted to create the workgroup to collaborate on future projects. +* **Active**: Contains at least one Graduated project, or a majority of the TAC has voted to create the workgroup to collaborate on future projects. * **Archived**: No longer contains any Graduated projects. -The TSC has sole authority over a project's lifecycle stage and workgroup, including the decision to accept or reject project proposals. It also may create or consolidate workgroups at its discretion. +The TAC has sole authority over a project's lifecycle stage and workgroup, including the decision to accept or reject project proposals. It also may create or consolidate workgroups at its discretion. #### Instantiating projects -All projects will go through the onboarding process. At a high level, this includes: - -* Completing a mission statement, which will be hosted in the [projects](./projects) directory. -* Completing a [project application template](./projects/PROJECT_APPLICATION_TEMPLATE.md) through Graduated stage, at least. -* Adding core collaborators to a GitHub team in the CHIPS Alliance organization under [Project Leadership](https://github.com/orgs/chipsalliance/teams/project-leadership/teams). -* Transferring repositories to the CHIPS Alliance. -* Setting up a project mailing list on the CHIPS Alliance domain. -* Adding CHIPS Alliance footers and notices to project websites. -* Designating a representative to the project's workgroup. -* Designating a representative to attend TSC meetings (as a voting member or participant). - -Linux Foundation staff are able to help with this process. +Projects join CHIPS Alliance by following the [Project Lifecycle Process](./projects/README.md). ### Resources @@ -133,29 +115,29 @@ All Graduated projects and Active workgroups can make use of the CHIPS Alliance ### The CHIPS Alliance Commons: Related projects and initiatives -The CHIPS Alliance exists within a rich ecosystem of interrelated projects. While the TSC's first objective is to support the success of CHIPS Alliance projects, it also acknowledges the critical strategic roles played by external open source projects. Collectively, we refer to these projects as "The CHIPS Alliance Commons". +The CHIPS Alliance exists within a rich ecosystem of interrelated projects. While the TAC's first objective is to support the success of CHIPS Alliance projects, it also acknowledges the critical strategic roles played by external open source projects. Collectively, we refer to these projects as "The CHIPS Alliance Commons". -Although these projects remain outside of the CHIPS Alliance organization and its policies, the TSC may recognize these projects in various ways. For example, the TSC can maintain a list of strategic open source projects, or make an effort to include their participants and maintainers in relevant TSC discussions. +Although these projects remain outside of the CHIPS Alliance organization and its policies, the TAC may recognize these projects in various ways. For example, the TAC can maintain a list of strategic open source projects, or make an effort to include their participants and maintainers in relevant TAC discussions. -The CHIPS Alliance TSC is grateful to the broader open source ecosystem, and is looking forward to healthy collaboration within and external to the Alliance. +The CHIPS Alliance TAC is grateful to the broader open source ecosystem, and is looking forward to healthy collaboration within and external to the Alliance. ## Policies and procedures -The CHIPS Alliance TSC is governed by the [Technical Charter](https://technical-charter.chipsalliance.org). The Charter provides a foundational structure for the TSC on topics such as its scope, how to make decisions, and how to make changes to itself. At the same time, it grants the TSC a high degree of freedom when determining how to implement the policies of CHIPS Alliance. +The CHIPS Alliance TAC is governed by the [Charter](https://participation-agreement.chipsalliance.org). The Charter provides a foundational structure for the TAC while granting the TAC a high degree of freedom when determining how to implement the policies of CHIPS Alliance. -The following policies and procedures have been adopted by the TSC. +The following policies and procedures have been adopted by the TAC. ### Reporting security vulnerabilities -All CHIPS Alliance projects **must** have a process for receiving security vulnerability reports. If a project does not have its own process, the default policy is to send a detailed disclosure to [security@lists.chipsalliance.org](mailto:security@lists.chipsalliance.org). This is a confidential mailing list, and the TSC chair and a small group of trusted individuals will review and act upon the report as appropriate. +All CHIPS Alliance projects **must** have a process for receiving security vulnerability reports. If a project does not have its own process, the default policy is to send a detailed disclosure to [security@lists.chipsalliance.org](mailto:security@lists.chipsalliance.org). This is a confidential mailing list, and the TAC chair and a small group of trusted individuals will review and act upon the report as appropriate. ### Voting procedures -The TSC will use voting to make decisions when required by the charter, or when consensus cannot be reached. +The TAC will use voting to make decisions when required by the charter, or when consensus cannot be reached. -Votes may be initiated by any [TSC voting member](#tsc-voting-members-and-graduated-projects) or CHIPS Alliance staff. Except when required otherwise by the charter, votes are decided by a simple majority of all eligible voting members. Unless withdrawn, votes remain open until they meet their acceptance or rejection threshold. +Votes may be initiated by any [TAC voting member](#tac-voting-members-and-graduated-projects) or CHIPS Alliance staff. Except when required otherwise by the charter, votes are decided by a simple majority of all eligible voting members. Unless withdrawn, votes remain open until they meet their acceptance or rejection threshold. -Email votes are strongly preferred because they provide a clear history, although alternate voting systems may be used if they better serve the need of the situation (e.g., OpaVote, CIVS, etc.). Voting outcomes should be recorded in the minutes of the next TSC meeting. It is sufficient to publish the outcome; it is not necesssary to publish how each member voted unless there is unanimous agreement among voting members. +Email votes are strongly preferred because they provide a clear history, although alternate voting systems may be used if they better serve the need of the situation (e.g., OpaVote, CIVS, etc.). Voting outcomes should be recorded in the minutes of the next TAC meeting. It is sufficient to publish the outcome; it is not necesssary to publish how each member voted unless there is unanimous agreement among voting members. Template for initiating an email vote: @@ -170,17 +152,17 @@ Voting members, please vote by replying "Approve", "Reject", or "Abstain". When a vote is related to a PR or issue, apply the labels [vote-required](https://github.com/chipsalliance/tsc/labels/vote-required), [vote-in-progress](https://github.com/chipsalliance/tsc/labels/vote-in-progress), [vote-passed](https://github.com/chipsalliance/tsc/labels/vote-passed), or [vote-rejected](https://github.com/chipsalliance/tsc/labels/vote-rejected) as appropriate. -### Merging PRs into the TSC repository +### Merging PRs into the TAC repository -Pull requests that do not change the charter or governance of the TSC can be merged into this repository provided the following conditions have been met: +Pull requests that do not change the charter or governance of the TAC can be merged into this repository provided the following conditions have been met: * There are no outstanding objections -* There are two approvals by TSC members +* There are two approvals by TAC members * The PR has been open for at least 72 hours -Pull requests that change governance of the TSC (excluding the charter) must be open for at least 14 days, unless consensus is reached in a meeting with quorum of voting members, or an email vote has been passed in favor of the PR, as signified by the [vote-passed](https://github.com/chipsalliance/tsc/labels/vote-passed) label (see [Voting procedures](#voting-procedures) above). +Pull requests that change governance of the TAC (excluding the charter) must be open for at least 14 days, unless consensus is reached in a meeting with quorum of voting members, or an email vote has been passed in favor of the PR, as signified by the [vote-passed](https://github.com/chipsalliance/tsc/labels/vote-passed) label (see [Voting procedures](#voting-procedures) above). -Pull requests that change the charter of the TSC must meet any requirements in the [charter](https://technical-charter.chipsalliance.org). +Pull requests that change the charter of the TAC must meet any requirements in the [charter](https://participation-agreement.chipsalliance.org/). If consensus cannot be reached, a pull request may still be landed after a vote by the Voting members to override outstanding objections. @@ -193,11 +175,11 @@ Special exception is made for pull requests seeking to make any of the following Charter changes cannot be fast-tracked. -To propose fast-tracking a pull request, apply the ***fast-track*** label. Then add a comment that TSC members may upvote. If someone disagrees with the fast-tracking request, remove the label. Do not fast-track the pull request in that case. +To propose fast-tracking a pull request, apply the ***fast-track*** label. Then add a comment that TAC members may upvote. If someone disagrees with the fast-tracking request, remove the label. Do not fast-track the pull request in that case. -The pull request may be fast-tracked if two TSC members approve the fast-tracking request. To land, the pull request itself still needs two TSC member approvals. +The pull request may be fast-tracked if two TAC members approve the fast-tracking request. To land, the pull request itself still needs two TAC member approvals. -TSC members may request fast-tracking of pull requests they did not author. In that case only, the request itself is also one fast-track approval. Upvote the comment anyway to avoid any doubt. +TAC members may request fast-tracking of pull requests they did not author. In that case only, the request itself is also one fast-track approval. Upvote the comment anyway to avoid any doubt. ### Trivial PRs @@ -207,11 +189,11 @@ Trivial PRs that update factual situations can be merged immediately. When openi - Editorial changes. - Updates to team lists. -If a TSC member does not believe the change was trivial, it can be reverted and proposed through the normal PR process. +If a TAC member does not believe the change was trivial, it can be reverted and proposed through the normal PR process. ### IP Policy -The CHIPS Alliance IP policy is contained in the [charter](https://technical-charter.chipsalliance.org), and it applies to all CHIPS Alliance projects unless an exception is explicitly approved by the TSC. +The CHIPS Alliance IP policy is contained in the [Charter](https://participation-agreement.chipsalliance.org/), and it applies to all CHIPS Alliance projects unless an exception is explicitly approved by the TAC. #### Copyright notices @@ -250,9 +232,9 @@ Repositories may be transferred into or created under the CHIPS Alliance organiz * They adhere to the CHIPS Alliance IP policy. * They are directly operated by a CHIPS Alliance project. -* The TSC achieves rough consensus about adding the repository. +* The TAC achieves rough consensus about adding the repository. -Sometimes projects will rely upon other external repositories (e.g., tooling or dependencies). While it is a best practice to work upstream whenever possible, there may be situations where a downstream fork is required. In this situation, rough consensus on the TSC is sufficient to create a new fork. +Sometimes projects will rely upon other external repositories (e.g., tooling or dependencies). While it is a best practice to work upstream whenever possible, there may be situations where a downstream fork is required. In this situation, rough consensus on the TAC is sufficient to create a new fork. Finally, non-technical repositories may be needed for admin purposes, and may be created by staff from time to time. @@ -279,7 +261,7 @@ To help ensure effective repo management, each project should manage a GitHub te #### Archiving repositories -The TSC may choose to move repositories to an archived state, at its own discretion. Most often this will occur if there are concerns about a repository being unmaintained, but may also happen if two efforts are consolidating and one codebase is being kept for archival purposes. +The TAC may choose to move repositories to an archived state, at its own discretion. Most often this will occur if there are concerns about a repository being unmaintained, but may also happen if two efforts are consolidating and one codebase is being kept for archival purposes. ## Getting Help @@ -317,5 +299,3 @@ For any other topics which aren't covered above, please email [operations@chipsa **Copyright CHIPS Alliance Project a Series of LF Projects, LLC.** For web site terms of use, trademark policy and general project policies please see [https://lfprojects.org](https://lfprojects.org). - -https://technical-charter.chipsalliance.org diff --git a/STAGING_PROCESS.md b/STAGING_PROCESS.md index fbf3f7b..31806e5 100644 --- a/STAGING_PROCESS.md +++ b/STAGING_PROCESS.md @@ -18,7 +18,7 @@ Proposals in this stage are written up in the style of the formal policy or prog Proposals in this stage are nearly complete. They may be in a pilot or trial-run mode for a limited audience, or pending legal review. They may be awaiting budget approval. The purpose of this stage is to complete any operational checks, such as acquiring budget, access, or governing board approval if needed, before launching the program. ### Stage 3 - Complete -The proposal is now an adopted policy or program of the CHIPS Alliance TSC, and is owned by the committee or role identified. It is expected that the policy or program will be re-evaluated on some regular basis and deprecated if need be. +The proposal is now an adopted policy or program of the CHIPS Alliance TAC, and is owned by the committee or role identified. It is expected that the policy or program will be re-evaluated on some regular basis and deprecated if need be. ## Staging proposal template diff --git a/projects/MISSION_STATEMENT_TEMPLATE.md b/projects/MISSION_STATEMENT_TEMPLATE.md index 499a41b..ec85171 100644 --- a/projects/MISSION_STATEMENT_TEMPLATE.md +++ b/projects/MISSION_STATEMENT_TEMPLATE.md @@ -1,6 +1,6 @@ # (your project name) Mission Statement -The purpose of this document is to provide a brief introduction to a project or workgroup from a technical, community, or business perspective. The document also connects a project's community leadership and governance with the CHIPS Alliance TSC's governance. +The purpose of this document is to provide a brief introduction to a project or workgroup from a technical, community, or business perspective. The document also connects a project's community leadership and governance with the CHIPS Alliance TAC's governance. ## Guiding Principles (optional) diff --git a/projects/README.md b/projects/README.md index a3398ba..2d71b08 100644 --- a/projects/README.md +++ b/projects/README.md @@ -6,7 +6,7 @@ This governance policy describes how an open source project can formally join th There are three project categories: -* [Sandbox](#sandbox): Optional pre-membership stage to help a project prepare for the TSC's consideration. +* [Sandbox](#sandbox): Optional pre-membership stage to help a project prepare for the TAC's consideration. * [Graduated](#graduated): A project which has met the graduation requirements and demonstrated sustainable momentum. * [Archived](#archived): A former Graduated project which has been archived for strategic or practical reasons. diff --git a/projects/templates/project-application-template.yml b/projects/templates/project-application-template.yml index f48ad48..4efff13 100644 --- a/projects/templates/project-application-template.yml +++ b/projects/templates/project-application-template.yml @@ -8,7 +8,7 @@ project_usage_and_scale: "Brief summary of how widely the project is used e.g. l why_join_chips: "Project's motivation to join CHIPS" mission_statement_link: "Link to project's mission statement" svg_logo_link: "Link to logo in .svg format, if present" -# The primary contact person for the project, will become TSC representative once admitted +# The primary contact person for the project, will become TAC representative once admitted primary_contact: name: "Contact's full name" email: "Contact's work email" diff --git a/proposals/stage-2/README.md b/proposals/stage-2/README.md index 7ef7285..4d417eb 100644 --- a/proposals/stage-2/README.md +++ b/proposals/stage-2/README.md @@ -1,4 +1,4 @@ # Stage 2 proposals -The proposals in this directory are nearly complete, and have been accepted by the TSC and are pending any external checks (budget approval, Governing Board review, etc.). +The proposals in this directory are nearly complete, and have been accepted by the TAC and are pending any external checks (budget approval, Governing Board review, etc.).