changes project name

CODE-OF-CONDUCT.md

@@ -1,4 +1,3 @@
-<img src="artwork/eea-oneline.png" width="400">
 
 # Contributor Covenant Code of Conduct
 

GOVERNANCE.md

@@ -1,27 +1,27 @@
 <img src="artwork/eea-oneline.png" width="400">
 
-# EEA Community Projects Governance
+# Ethereum OASIS Open Project Governance
 
-This document defines the EEA Community Project's community governance per [OASIS Open Projects Governance Policy](https://github.com/oasis-open-projects/documentation/blob/master/policy/project-governance.md).
+This document defines the Ethereum OASIS Open Project's community governance per [OASIS Open Projects Governance Policy](https://github.com/oasis-open-projects/documentation/blob/master/policy/project-governance.md).
 
 # Our Goal
-Our primary goal is to provide a neutral forum for diverse stakeholders to create high-quality specifications that facilitate Ethereum’s longevity, interoperability, and ease of integration. The EEA Community Projects intend to develop clear, open standards, high-quality documentation, and shared test suites that facilitate new features and enhancements to the Ethereum protocol.
+Our primary goal is to provide a neutral forum for diverse stakeholders to create high-quality specifications that facilitate Ethereum’s longevity, interoperability, and ease of integration. The Ethereum OASIS Open Project intend to develop clear, open standards, high-quality documentation, and shared test suites that facilitate new features and enhancements to the Ethereum protocol.
 
 ## Overview
 
-The **EEA Community Projects** community is governed by this document and in accordance with [OASIS Open Project Rules](https://www.oasis-open.org/policies-guidelines/open-projects-process/). The purpose of this document is to definine how community should work together to achieve its technical goals.
+The **Ethereum OASIS Open Project** community is governed by this document and in accordance with [OASIS Open Project Rules](https://www.oasis-open.org/policies-guidelines/open-projects-process/). The purpose of this document is to definine how community should work together to achieve its technical goals.
 
-EEA Community Projects aims to work by lazy consensus within each TSC, as described under [Decision Making](#decision-making) below.  Each TSC is responsible for determining when it has lazy consensus. 
+The Ethereum OASIS Open Project aims to work by lazy consensus within each TSC, as described under [Decision Making](#decision-making) below.  Each TSC is responsible for determining when it has lazy consensus. 
 
 Within a TSC, those who show up and do the work get to make the decisions.
 
 The TSC should be open to changing decisions based on new information, if a consensus emerges to make such a change.
 
 ## Code Repositories
 
-The following code repositories are governed by the **EEA Community Projects** community and maintained under the project namespace:
+The following code repositories are governed by the **Ethereum OASIS Open Project** community and maintained under the project namespace:
 
-* **[EEA Community Projects repository](https://github.com/eea-oasis/oasis-open-project):** The main repository.
+* **[Ethereum OASIS Open Project repository](https://github.com/eea-oasis/oasis-open-project):** The main repository.
 * **[baseline](https://github.com/eea-oasis/baseline)**
 * **[baseline-website-v2](https://github.com/eea-oasis/baseline-website-v2)**
 * **[L2](https://github.com/eea-oasis/L2)**
@@ -120,7 +120,7 @@ Note that the PGB may permit the formation or continuation of a TSC that does no
 
 ### TSC funding
 
-EEA Community Projects supports all of its TSCs.  However, if a TSC would like additional resources, beyond those provided by default by OASIS, to support its initiatives, it may seek additional funding.
+Ethereum OASIS Open Project supports all of its TSCs.  However, if a TSC would like additional resources, beyond those provided by default by OASIS, to support its initiatives, it may seek additional funding.
 
 Any Sponsor may provide additional funding through OASIS that is designated for a specific TSC to allocate.  Non-Sponsors may contribute additional funding as described in [Non-Sponsor TSC funding](#non-sponsor-tsc-funding).
 
@@ -129,15 +129,15 @@ Programs designed to solicit grants may be specific to individual TSCs.
 In all cases,
 * Grantors must be informed, before funds are committed, of any fees that will be deducted from their grants.
 * No advance vote or approval by the PGB is required to accept a grant or allocate the funds.  However, the TSC must give advance notice to the PGB before disbursement of any funds.
-* Either OASIS or the PGB may veto the acquisition or use of such funding at any time for any reason.  A statement to this effect must be included on any grants form. The intent of this requirement is to ensure that the acquisition and use of any such funding is consistent with the overall goals of OASIS and the EEA Community Projects.
+* Either OASIS or the PGB may veto the acquisition or use of such funding at any time for any reason.  A statement to this effect must be included on any grants form. The intent of this requirement is to ensure that the acquisition and use of any such funding is consistent with the overall goals of OASIS and the Ethereum OASIS Open Project.
 * The TSC determines where to direct the funds collected, either directly or via a process they establish.  Note that Grantors have no direct control over use of funds within a TSC and thus cannot use this funding mechanism to direct priorities within the TSC.
-* The TSC and its projects may not use the OASIS or EEA Community Projects names when seeking or using additional funding unless the PGB has been notified in advance.  
+* The TSC and its projects may not use the OASIS or Ethereum OASIS Open Project names when seeking or using additional funding unless the PGB has been notified in advance.  
 
-If a TSC chooses to seek funding outside of the OASIS funding path, they still must not use the OASIS, EEA Community Projects, or TSC project names when seeking or using additional funding unless the PGB has been notified in advance.
+If a TSC chooses to seek funding outside of the OASIS funding path, they still must not use the OASIS, Ethereum OASIS Open Project, or TSC project names when seeking or using additional funding unless the PGB has been notified in advance.
 
 #### Non-Sponsor TSC funding
 
-Non-Sponsors of the EEA Community Projects may fund grants at any time and in any amount. After deducting any administration fees assessed by the transaction processor, 25% of the proceeds  will be used to fund Core Services, including marketing, with the remainder available for allocation by the TSC.
+Non-Sponsors of the Ethereum OASIS Open Project may fund grants at any time and in any amount. After deducting any administration fees assessed by the transaction processor, 25% of the proceeds  will be used to fund Core Services, including marketing, with the remainder available for allocation by the TSC.
 
 Grantors must be informed, before funds are committed, of the 25% assessment for Core Services. 
 

IPR-STATEMENT.md

@@ -1,4 +1,4 @@
-<img src="artwork/eea-oneline.png" width="400">
+
 
 # IPR Statement
 

PROJECT-GOVERNING-BOARD.md

@@ -1,12 +1,11 @@
-<img src="artwork/eea-oneline.png" width="400">
 
-# EEA Community Projects Governing Board (PGB)
+# Ethereum OASIS Open Project Governing Board (PGB)
 
-The Project Governing Board sets overall strategic direction for the EEA Community Projects and formally approves released work products.
+The Project Governing Board sets overall strategic direction for the Ethereum OASIS Open Project and formally approves released work products.
 
-PGB members include representatives of [EEA Community Projects sponsor organizations](https://github.com/eea-oasis/managed-open-project/blob/main/SPONSORS.md) and representatives from the community at-large who serve on the Technical Steering Committee.
+PGB members include representatives of [Ethereum OASIS Open Project sponsor organizations](https://github.com/eea-oasis/managed-open-project/blob/main/SPONSORS.md) and representatives from the community at-large who serve on the Technical Steering Committee.
 
-The members of the EEA Community Projects Project Governing Board are listed at https://eea-oasis.github.io/managed-open-project/
+The members of the Ethereum OASIS Open Project Project Governing Board are listed at https://eea-oasis.github.io/managed-open-project/
 
 <!-- * Daniel Burnett, Enterprise Ethereum Alliance ([@burnburn](https://github.com/burnburn))
 * Tas Dienes, Ethereum Foundation ([@tasdienes](https://github.com/tasdienes))

PROJECT_CHARTER.md

@@ -1,24 +1,23 @@
-<img src="artwork/eea-oneline.png" width="400">
 
-# EEA Community Projects Charter 
+# Ethereum OASIS Open Project Charter 
 
 ## 1. Project Name
 
-EEA Community Projects
+Ethereum OASIS Open Project
 
 ## 2. Abstract
 
-EEA Community Projects, a Managed OASIS Open Project, exists to provide a neutral forum for diverse stakeholders to create high-quality specifications that facilitate Ethereum’s longevity, interoperability, and ease of integration. EEA Community Projects intends to develop clear, open standards, high-quality documentation, and shared test suites that facilitate new features and enhancements to the Ethereum protocol.
+Ethereum OASIS Open Project, a Managed OASIS Open Project, exists to provide a neutral forum for diverse stakeholders to create high-quality specifications that facilitate Ethereum’s longevity, interoperability, and ease of integration. Ethereum OASIS Open Project intends to develop clear, open standards, high-quality documentation, and shared test suites that facilitate new features and enhancements to the Ethereum protocol.
 
 ## 3. Purpose and Scope
 
 The EIP process has led to a rich diverse engagement of developers in improving Ethereum - this decentralized ability of all to contribute ideas and features is a benefit to the ecosystem. This process has also led to EIPs of varying specificity, application, and quality, which presents a challenge to developers and organizations looking to adopt the most interoperable standards. 
 
-The EEA Community Projects seek to address this problem and improve the interoperability of implementations for all. Working within a process that is predictable, fair, transparent, and time-tested, the EEA Community Projects will provide a forum for producing standards in a style familiar to corporate contributors. Additionally, we wish for an Ethereum standard to be able to be blessed as more canonical among the sometimes mutually-exclusive EIPs. Finally, we also wish to ease the transition of technology and standards from Mainnet to private and/or permissioned chains such as those from the Enterprise Ethereum Alliance.
+The Ethereum OASIS Open Project seek to address this problem and improve the interoperability of implementations for all. Working within a process that is predictable, fair, transparent, and time-tested, the Ethereum OASIS Open Project will provide a forum for producing standards in a style familiar to corporate contributors. Additionally, we wish for an Ethereum standard to be able to be blessed as more canonical among the sometimes mutually-exclusive EIPs. Finally, we also wish to ease the transition of technology and standards from Mainnet to private and/or permissioned chains such as those from the Enterprise Ethereum Alliance.
 
 ## 4. Business Benefits
 
-The EEA Community Projects is for:
+The Ethereum OASIS Open Project is for:
 * developers who wish to contribute to and shape the development of Ethereum.
 * developers who wish to integrate Ethereum with other projects.
 * project managers who wish to have a hand in Ethereum standards governance.
@@ -34,7 +33,7 @@ Common reasons for following this project are:
 
 * [Bitcoin Improvement Proposals](https://bitcoincore.org/en/bips/) --- Bitcoin Core is usually more conservative in the upgrades they push forward, but ideas which start in Bitcoin will often make their way into the EIP or EEA Communitty Projects.
 
-* [Ethereum Improvement Proposals](https://eips.ethereum.org) --- The Ethereum EIP process is less structured than the OASIS process---essentially anyone can create an EIP.  This sometimes creates confusion as different clients implement different EIPs.  One goal of the EEA Community Projects is to reduce the number of competing standards.  Exactly the right complementary relationship between EIPs and the EEA Community Projects will be determined as we go.
+* [Ethereum Improvement Proposals](https://eips.ethereum.org) --- The Ethereum EIP process is less structured than the OASIS process---essentially anyone can create an EIP.  This sometimes creates confusion as different clients implement different EIPs.  One goal of the Ethereum OASIS Open Project is to reduce the number of competing standards.  Exactly the right complementary relationship between EIPs and the Ethereum OASIS Open Project will be determined as we go.
 
 * [Ethereum Classic Improvement Proposals](https://github.com/ethereumproject/ECIPs) --- The equivalent of the EIP process for [Ethereum Classic](https://ethereumclassic.org/).
 

README.md

@@ -1,19 +1,19 @@
 
 # Ethereum OASIS Open Project
 
-EEA Community Projects, an OASIS Managed Open Project, exists to provide a neutral forum for diverse stakeholders to create high-quality specifications that facilitate Ethereum’s longevity, interoperability, and ease of integration. The EEA Community Projects intend to develop clear, open standards, high-quality documentation, and shared test suites that facilitate new features and enhancements to the Ethereum protocol.
+The Ethereum OASIS Open Project exists to provide a neutral forum for diverse stakeholders to create high-quality specifications that facilitate Ethereum’s longevity, interoperability, and ease of integration. The Ethereum OASIS Open Project intend to develop clear, open standards, high-quality documentation, and shared test suites that facilitate new features and enhancements to the Ethereum protocol.
 
 For more information on the goals of this effort, see the [project charter](./PROJECT_CHARTER.md).
 
-You can also sign up for [the EEA Community Projects email group](https://lists.oasis-open-projects.org/g/eea-community-projects) to receive occasional official notifications and discussions.
+You can also sign up for [the Ethereum OASIS Open Project email group](https://lists.oasis-open-projects.org/g/eea-community-projects) to receive occasional official notifications and discussions.
 
 ## Governance
-The EEA Community Projects operate under the terms of the [OASIS Open Project Rules](https://github.com/oasis-open-projects/documentation/blob/master/board-docs/open-projects-rules.md), its [Project Governance Document](https://github.com/eea-oasis/managed-open-project/blob/master/GOVERNANCE.md) and the applicable license(s) specified in [LICENSE.md](./LICENSE).
+The Ethereum OASIS Open Project operate under the terms of the [OASIS Open Project Rules](https://github.com/oasis-open-projects/documentation/blob/master/board-docs/open-projects-rules.md), its [Project Governance Document](https://github.com/eea-oasis/managed-open-project/blob/master/GOVERNANCE.md) and the applicable license(s) specified in [LICENSE.md](./LICENSE).
 
-It is overseen by the [EEA Community Projects Governing Board](PROJECT-GOVERNING-BOARD.md).
+It is overseen by the [Ethereum OASIS Open Project Governing Board](PROJECT-GOVERNING-BOARD.md).
 
 ## List of projects & TSCs
-Each EEA Community Project is managed by a Technical Steering Committee and overseen by the Project Governing Board.
+There are several Technical Steering Committees under the umbrella of the Open Project. Each TSC is overseen by the Project Governing Board.
 
 * Baseline Protocol
   * repo:
@@ -49,7 +49,7 @@ Each EEA Community Project is managed by a Technical Steering Committee and over
   * Governance document:-->
 
 ## Contributing
-Everyone is welcome to contribute to EEA Community Projects - you do not need to be a "member" of anything to submit a technical contribution or get involved with any of the above project communities. Details on how to contribute to EEA Community Projects can be found on the respective repositories listed above.
+Everyone is welcome to contribute to Ethereum OASIS Open Project - you do not need to be a "member" of anything to submit a technical contribution or get involved with any of the above project communities. Details on how to contribute to Ethereum OASIS Open Project can be found on the respective repositories listed above.
 
 ### CLA & Non-assert signatures required
 All technical contributions must be accompanied by a Contributor's License Agreement. This requirement allows our work to advance through de jure standards development stages in forums such as EC or ISO. You will get a prompt to sign this document when you submit a pull request to a project repository, or you can sign [here](https://cla-assistant.io/eea-oasis/managed-open-project). If you are contributing on behalf of your employer, you must also sign the ECLA [here](https://www.oasis-open.org/open-projects/cla/entity-cla-20210630/).

SPECIFICATION-DOCUMENT-REQUIREMENTS.md

@@ -1,4 +1,4 @@
-# EEA Community Projects
+# Ethereum OASIS Open Project
 
 
 ## Criteria for publishing specification documents