update Core Developer -> maintainer

Author: Therecanbeonlyone1969

community/contributors.md

@@ -31,7 +31,7 @@ Technical contributors either are working on architecture or developing code...b
 
 ## Core Developers <a href="#maintainers" id="maintainers"></a>
 
-Once you've done some work as a Member, you may wish to become a **Core developer** and have a direct hand in deciding what work is merged to the Main/Master Branch to become official Baseline technology and specifications.
+Once you've done some work as a Member, you may wish to become a **Maintainer** and have a direct hand in deciding what work is merged to the Main/Master Branch to become official Baseline technology and specifications.
 
 ### What do core developers do? <a href="#what-do-maintainers-do" id="what-do-maintainers-do"></a>
 
@@ -49,11 +49,11 @@ They can/should also contribute in the following ways:
 * Working with the community to help with adoption
 * Presenting the project and key technologies to the public (in-person, webinar, videos, articles, etc...)
 
-## How to become a core developer? <a href="#how-to-become-a-maintainer" id="how-to-become-a-maintainer"></a>
+## How to become a maintainer? <a href="#how-to-become-a-maintainer" id="how-to-become-a-maintainer"></a>
 
-There are two ways to become a core developer: You are asked by a current core developer, or you make request to an existing core developer to become one.&#x20;
+There are two ways to become a maintainer: You are asked by a current maintainer, or you make request to an existing maintainer to become one.&#x20;
 
-With either path you become a "provisional core developer". As such you will need to show consistent contributions of code and/or specifications to the project. This can be in the form of pull requests that get merged into master. Or it can be in the form of technical specification, system architecture and related artifacts that guide the development activities of others.
+With either path you become a "provisional maintainer". As such you will need to show consistent contributions of code and/or specifications to the project. This can be in the form of pull requests that get merged into master. Or it can be in the form of technical specification, system architecture and related artifacts that guide the development activities of others.
 
 All provisional core developers that focus on code development (over standards) must meet with the existing core developers and demonstrate they are capable of the following:
 
@@ -62,11 +62,11 @@ All provisional core developers that focus on code development (over standards)
 * Explaining the components of the system architecture
 * Walking through the code and explain the baseline process
 
-Once the provisional core developer demonstrates their capabilities, the existing core developers will vote during the next scheduled core developer meeting to give the prospect full core developer status. Members must vote with 2/3rds majority to add a core developer. Voting that results in a tie or potentially other issue will be brought to the TSC for review.
+Once the provisional maintainer demonstrates their capabilities, the existing core developers will vote during the next scheduled maintainer meeting to give the prospect full maintainer status. Members must vote with 2/3rds majority to add a maintainer. Voting that results in a tie or potentially other issue will be brought to the TSC for review.
 
 ## What is expected of core developers? <a href="#what-is-expected-of-maintainers" id="what-is-expected-of-maintainers"></a>
 
-In general, a core developer needs to:
+In general, a maintainer needs to:
 
 * be an expert in one or more fields related to the project
 * be an expert in finding and engaging the advice of other experts
@@ -92,16 +92,16 @@ There are currently no regular meetings.&#x20;
 
 Meeting signups are maintained on the "Join the Community" page on https://baseline-protocol.org.
 
-## How to stop being a core developer? <a href="#how-to-stop-being-a-maintainer" id="how-to-stop-being-a-maintainer"></a>
+## How to stop being a maintainer? <a href="#how-to-stop-being-a-maintainer" id="how-to-stop-being-a-maintainer"></a>
 
 Any of the following ways:
 
 * You stop reviewing PR's, responding to messages, answering emails, and/or generally ghost the project.
 * You are disrespectful towards anyone in the community and/or involved in the project.
 * You are disruptive to the general process of maintaining the project, meetings, discussions, issues, or other.
-* You notify the other core developers  you would like to relinquish your core developer status.
+* You notify the other core developers  you would like to relinquish your maintainer status.
 
-Two-thirds of all current core developers constitute a quorum for a meeting involving a question of removal. A simple majority vote from core developers attending the meeting is required to remove a core developer, but the TSC may be brought in to arbitrate if the core developer to be removed or any other core developer wishes to dispute the action. (See [Governance](https://github.com/ethereum-oasis-op/baseline/blob/main/docs/governance/governance.md) for details.)
+Two-thirds of all current core developers constitute a quorum for a meeting involving a question of removal. A simple majority vote from core developers attending the meeting is required to remove a maintainer, but the TSC may be brought in to arbitrate if the maintainer to be removed or any other maintainer wishes to dispute the action. (See [Governance](https://github.com/ethereum-oasis-op/baseline/blob/main/docs/governance/governance.md) for details.)
 
 ### BLIPs
 
@@ -136,7 +136,7 @@ The iCLA happens automatically when people submit a pull request, or they can ac
 
 ### Core Developers and Commit Rules <a href="#maintainers-and-commit-rules" id="maintainers-and-commit-rules"></a>
 
-Merging to Master requires review by THREE Core Developers. The TSC seeded the initial set of Core Developers. Now, any active Member can become a Core Developer. Core Developers may add more Core Developers by rough consensus, and the TSC may step in to resolve cases where this process fails.
+Merging to Master requires review by THREE Core Developers. The TSC seeded the initial set of Core Developers. Now, any active Member can become a Maintainer. Core Developers may add more Core Developers by rough consensus, and the TSC may step in to resolve cases where this process fails.
 
 ## Specifications Contributors <a href="#specifications-contributors" id="specifications-contributors"></a>
 

community/members.md

@@ -46,6 +46,6 @@ Any member may request a confidential review of another member to determine whet
 
 Once you are a member, you can:
 
-1. Become a [Core Developer ](broken-reference)responsible for governing the contributions that get merged to the official master branch;
+1. Become a [Maintainer ](broken-reference)responsible for governing the contributions that get merged to the official master branch;
 2. Get elected to the [Technical Steering Committee](../docs/governance/technical-steering-committee.md), accountable for architecture and governance of the core developers;
 3. Or, just write awesome code, specifications, docs and communications.

docs/baseline-protocol/the-baseline-protocol.md

@@ -16,7 +16,7 @@ The high level description and specification for a global public Mainnet are [he
 
 The Baseline Protocol can perform its core tasks on the current public Ethereum network at a rate that is reasonably expected to be sufficient for work in supply chain, B2B contracting, CRM, and other domains that involve coordinating records between legally separate entities.
 
-Eth2 will further extend the range of applications that baselining can serve at acceptable levels of performance and reliability. The Baseline Protocol community will align closely with Ethereum and work through the EEA and the Ethereum Foundation to supply the Ethereum core developer community with ideas, user stories and requirements to help see Eth2 evolve into a platform well-suited to baselining.
+Eth2 will further extend the range of applications that baselining can serve at acceptable levels of performance and reliability. The Baseline Protocol community will align closely with Ethereum and work through the EEA and the Ethereum Foundation to supply the Ethereum maintainer community with ideas, user stories and requirements to help see Eth2 evolve into a platform well-suited to baselining.
 
 ## Which Systems of Record Can We _Baseline?_ <a href="#which-systems-of-record-can-we-baseline" id="which-systems-of-record-can-we-baseline"></a>
 

docs/community/community-leaders/maintainers.md

@@ -10,7 +10,7 @@ description: >-
 
 Anyone is welcome to join the Baseline Core Developers to develop technical advancements or even just engage in technical discussions that take place.
 
-### How to become a Baseline Core Developer? <a href="#how-to-become-a-maintainer" id="how-to-become-a-maintainer"></a>
+### How to become a Baseline Maintainer? <a href="#how-to-become-a-maintainer" id="how-to-become-a-maintainer"></a>
 
 Sign up to join the Baseline Core Developers[ **here**](https://www.baseline-protocol.org/get-involved/) \*\*\*\* to receive the calendar invites and access to the Google Drive resources.
 
@@ -32,9 +32,9 @@ Baseline Protocol Maintainers are Baseline Core Developers with advanced Github
 
 ### How to become a Baseline Maintainer? <a href="#how-to-become-a-maintainer" id="how-to-become-a-maintainer"></a>
 
-A Baseline Core Developer can become a Baseline Maintainer by doing the following,
+A Baseline Maintainer can become a Baseline Maintainer by doing the following,
 
-* Being an active Baseline Core Developer by actively attending the bi-weekly meetings
+* Being an active Baseline Maintainer by actively attending the bi-weekly meetings
 * Making a contribution to the Baseline Protocol through [**BLIP work**](https://github.com/ethereum-oasis-op/baseline-blips), [**progressing the roadmap**](https://github.com/ethereum-oasis-op/baseline/blob/main/Baseline%20Protocol%20-%202022%20Roadmap.pdf), or other efforts
 * Then completing the [**Pull\_Request\_Template** ](https://github.com/ethereum-oasis-op/baseline/blob/main/.github/PULL\_REQUEST\_TEMPLATE.md)in its entirety to add users Github ID to the [**Code Owners file**](https://github.com/ethereum-oasis-op/baseline/blob/main/.github/CODEOWNERS)&#x20;
 * The current Maintainers (listed Code Owners) will be assigned to review the Pull Request, and the PR will be merged once **two** Maintainers approve the request
@@ -54,17 +54,17 @@ To retain Maintainer permissions and status, Baseline Maintainers are required t
 * Be welcoming to others in the community who are using or interested in the protocol
 * Contribute in ways that substantially improve the quality of the project and the experience of people who use it
 
-## How to stop being a Baseline Core Developer or Maintainer? <a href="#how-to-stop-being-a-maintainer" id="how-to-stop-being-a-maintainer"></a>
+## How to stop being a Baseline Maintainer or Maintainer? <a href="#how-to-stop-being-a-maintainer" id="how-to-stop-being-a-maintainer"></a>
 
-To step away from being a Baseline Core Developer, you can notify the other core developers you would like to relinquish your core developer status.
+To step away from being a Baseline Maintainer, you can notify the other core developers you would like to relinquish your maintainer status.
 
 What can take away your Core Dev status?
 
 * You stop reviewing PR's, responding to messages, answering emails, and/or generally ghost the project.
 * You are disrespectful towards anyone in the community and/or involved in the project.
 * You are disruptive to the general process of maintaining the project, meetings, discussions, issues, or other.
 
-Two-thirds of all current Maintainers constitute a quorum for a meeting involving a question of removal. A simple majority vote from Maintainers is required to remove a Baseline Core Dev, but the TSC may be brought in to arbitrate if the Baseline Core Developer to be removed or any other Baseline Core Developer wishes to dispute the action. See [**Governance**](../../governance/governance.md#charter-baseline-open-source-project-governance) \*\*\*\* for details.
+Two-thirds of all current Maintainers constitute a quorum for a meeting involving a question of removal. A simple majority vote from Maintainers is required to remove a Baseline Core Dev, but the TSC may be brought in to arbitrate if the Baseline Maintainer to be removed or any other Baseline Maintainer wishes to dispute the action. See [**Governance**](../../governance/governance.md#charter-baseline-open-source-project-governance) \*\*\*\* for details.
 
 ## How do Baseline Core Developers organize? <a href="#how-maintainers-organize" id="how-maintainers-organize"></a>
 
@@ -74,8 +74,8 @@ The Baseline Core Developers talk in the [**'05-bl-core-devs' channel in Slack**
 
 The Baseline Maintainers use a private 'maintainers' channel in Slack that members with Maintainer status are added to.
 
-### Baseline Core Developer Meetings <a href="#weekly-meetings" id="weekly-meetings"></a>
+### Baseline Maintainer Meetings <a href="#weekly-meetings" id="weekly-meetings"></a>
 
-There are bi-weekly Baseline Core Developer _meetings_ where members can new or open [**Baseline Improvement Proposals (BLIPs)**](https://github.com/ethereum-oasis-op/baseline-blips), open repo issues and pull requests, roadmap items grant projects, and more.
+There are bi-weekly Baseline Maintainer _meetings_ where members can new or open [**Baseline Improvement Proposals (BLIPs)**](https://github.com/ethereum-oasis-op/baseline-blips), open repo issues and pull requests, roadmap items grant projects, and more.
 
-Members with Maintainer status are required to join Baseline Core Developer meetings, as outlined in the terms above.
+Members with Maintainer status are required to join Baseline Maintainer meetings, as outlined in the terms above.