Update emails and PegaSys references (#2732)

Author: timbeiko

CLA.md

@@ -1,10 +1,10 @@
 Sign the CLA
 =============
 
-This page is the step-by-step guide to signing the Consensys AG
-Individual Contributor License Agreement. 
+This page is the step-by-step guide to signing the Consensys Software Inc.
+Individual Contributor License Agreement.
 
-1. First and foremost, read [the current version of the CLA]. 
+1. First and foremost, read [the current version of the CLA].
    It is written to be as close to plain English as possible.
 
 2. Make an account on [GitHub] if you don't already have one.
@@ -13,7 +13,7 @@ Individual Contributor License Agreement.
    pre-requisite requiring to you read and sign the CLA.
 
 If you have any questions, you can reach us on [Discord].
- 
+
 [Discord]: https://discord.gg/7hPv2T6
 [GitHub]: https://github.com/
 [the current version of the CLA]: https://gist.github.com/rojotek/978b48a5e8b68836856a8961d6887992

CODE-OF-CONDUCT.md

@@ -55,7 +55,7 @@ further defined and clarified by project maintainers.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at [private@pegasys.tech]. All
+reported by contacting the project team at [private[email protected]]. All
 complaints will be reviewed and investigated and will result in a response that
 is deemed necessary and appropriate to the circumstances. The project team is
 obligated to maintain confidentiality with regard to the reporter of an incident.
@@ -71,4 +71,4 @@ This Code of Conduct is adapted from the [Contributor Covenant], version 1.4,
 available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
 
 [Contributor Covenant]: https://www.contributor-covenant.org
-[private@pegasys.tech]: mailto:private@pegasys.tech
+[private[email protected]]: mailto:private[email protected]

CONTRIBUTING.md

@@ -12,19 +12,19 @@ Welcome to the Teku repository!  The following is a set of guidelines for contri
 [How to contribute](#how-to-contribute)
   * [Your first code contribution](#your-first-code-contribution)
   * [Reporting bugs](#reporting-bugs)
-  
+
 [Style Guides](#style-guides)
   * [Java Style Guide](#java-code-style-guide)
   * [Coding Conventions](#coding-conventions)
   * [Git Commit Messages & Pull Request Messages](#git-commit-messages--pull-request-messages)
 
 ## Code of Conduct
 
-This project and everyone participating in it is governed by the [Teku Code of Conduct](CODE-OF-CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [private@pegasys.tech].
+This project and everyone participating in it is governed by the [Teku Code of Conduct](CODE-OF-CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [private[email protected]].
 
 ## I just have a quick question
 
-You'll find us on [Discord] and that's the fastest way to get an answer. 
+You'll find us on [Discord] and that's the fastest way to get an answer.
 
 ## How To Contribute
 
@@ -88,7 +88,7 @@ Explain the problem and include additional details to help maintainers reproduce
 Provide more context by answering these questions:
 
 * **Did the problem start happening recently** (e.g. after updating to a new version of the software) or was this always a problem?
-* If the problem started happening recently, **can you reproduce the problem in an older version of the software?** What's the most recent version in which the problem doesn't happen? 
+* If the problem started happening recently, **can you reproduce the problem in an older version of the software?** What's the most recent version in which the problem doesn't happen?
 * **Can you reliably reproduce the issue?** If not, provide details about how often the problem happens and under which conditions it normally happens.
 
 Include details about your configuration and environment:
@@ -105,7 +105,7 @@ Include details about your configuration and environment:
 
 ## Java Code Style Guide
 
-We use Google's Java coding conventions for the project. To reformat code, run: 
+We use Google's Java coding conventions for the project. To reformat code, run:
 
 ```
 ./gradlew spotlessApply
@@ -122,6 +122,6 @@ We have a set of [coding conventions](https://wiki.hyperledger.org/display/BESU/
 * Provide a summary on the first line with more details on additional lines as needed
 * Reference issues and pull requests liberally
 
-[private@pegasys.tech]: mailto:private@pegasys.tech
+[private[email protected]]: mailto:private[email protected]
 [Discord]: https://discord.gg/7hPv2T6
 [CLA.md]: /CLA.md

GOVERNANCE.md

@@ -1,12 +1,12 @@
 # Overview
-This project is led by a benevolent dictator (PegaSys) and managed by the community. That is, the community actively contributes to the day-to-day maintenance of the project, but the general strategic line is drawn by the benevolent dictator. In case of disagreement, they have the last word. It is the benevolent dictator’s job to resolve disputes within the community and to ensure that the project is able to progress in a coordinated way. In turn, it is the community’s job to guide the decisions of the benevolent dictator through active engagement and contribution.
+This project is led by a benevolent dictator (ConsenSys) and managed by the community. That is, the community actively contributes to the day-to-day maintenance of the project, but the general strategic line is drawn by the benevolent dictator. In case of disagreement, they have the last word. It is the benevolent dictator’s job to resolve disputes within the community and to ensure that the project is able to progress in a coordinated way. In turn, it is the community’s job to guide the decisions of the benevolent dictator through active engagement and contribution.
 
 # Principles
 
 The community adheres to the following principles:
 * Open: Teku is open source. See repository guidelines and CLA, below.
 * Welcoming and respectful: See Code of Conduct, below.
-* Transparent and accessible: Work and collaboration should be done in public. 
+* Transparent and accessible: Work and collaboration should be done in public.
 * Merit: Ideas and contributions are accepted according to their technical merit and alignment with project objectives and design principles.
 
 # Code of Conduct
@@ -27,11 +27,11 @@ All contributors must sign the CLA, as described in [CLA.md].
 
 This document was influenced by the following:
 - Kubernetes community-membership.md, available at [kub community membership].
-- Kubernetes governance.md, available at [kub governance]  
-- OSSWatch Benevolent Dictator Governance Model, available at [oss watch benevolent dictator].  
+- Kubernetes governance.md, available at [kub governance]
+- OSSWatch Benevolent Dictator Governance Model, available at [oss watch benevolent dictator].
 
 [CLA.md]: /CLA.md
-[community membership]: /community-membership.md 
+[community membership]: /community-membership.md
 [code of conduct]: /CODE-OF-CONDUCT.md
 [oss watch benevolent dictator]: http://oss-watch.ac.uk/resources/benevolentdictatorgovernancemodel
 [kub community membership]: https://raw.githubusercontent.com/kubernetes/community/master/community-membership.md

SECURITY.md

@@ -5,6 +5,6 @@
 If you think you have discovered a security issue in Teku, we'd love to hear from you. We will take
 all security bugs seriously and if confirmed upon investigation we will patch it within a reasonable
 amount of time and release a public security bulletin discussing the impact and credit the discoverer.
- 
-To report a security bug, email a description of the flaw and any related information 
+
+To report a security bug, email a description of the flaw and any related information
 (e.g. reproduction steps, version) to  [[email protected]](mailto:[email protected]).

community-membership.md

@@ -8,9 +8,9 @@ this project.
 | Everyone | none | anybody with a belly button
 | Member | everyone who contributes - code or otherwise | Teku GitHub org member
 | Approver | approve accepting contributions | write permissions on master
-| Project Sponsor | contribute developer resources | PegaSys
-| Project Evangelist | promote the project | PegaSys
-| Benevolent Dictator | decision tie-breaker | PegaSys
+| Project Sponsor | contribute developer resources | ConsenSys
+| Project Evangelist | promote the project | ConsenSys
+| Benevolent Dictator | decision tie-breaker | ConsenSys
 
 ## Everyone
 Any person from the public is able to access the code.  The standard permissions grant the ability to view the code, view open bugs, access the wiki, download binaries, view CI results and comment on pull requests.
@@ -82,7 +82,7 @@ Code approvers are members that have signed an ICLA and have been granted additi
 ## Project Sponsor
 The Project Sponsor role provides a user with the ability to contribute additional developer resources to the project.  Project Sponsors must sign the ICLA.
 
-**Defined by:** PegaSys
+**Defined by:** ConsenSys
 
 ### Requirements
 - Signed ICLA, as described in [CLA.md]
@@ -94,7 +94,7 @@ The Project Sponsor role provides a user with the ability to contribute addition
 
 ## Project Evangelist
 The Project Evangelist role is for those who wish to promote the project to the outside world, but not actively contribute to it.  
-**Defined by:** PegaSys
+**Defined by:** ConsenSys
 
 ### Requirements
 - Includes all of the requirements of a Member user