Skip to content

Commit 2991e80

Browse files
mhuckapavoljuhas
andauthored
Update docs to use [email protected] (#6804)
* Update docs to use [email protected] The Code of Conduct still referred people to Bálint, so that needed to be changed. Also, it seems like a good idea to mention the maintainers' address in the top-level README file. * Don't need md formatting for email addresses on GitHub Turns out GH automatically links email addresses. * Update README.rst Co-authored-by: Pavol Juhas <[email protected]> --------- Co-authored-by: Pavol Juhas <[email protected]>
1 parent 7096acd commit 2991e80

File tree

2 files changed

+12
-8
lines changed

2 files changed

+12
-8
lines changed

CODE_OF_CONDUCT.md

+6-7
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ representative at an online or offline event. Representation of a project may be
5353
further defined and clarified by project maintainers.
5454

5555
This Code of Conduct also applies outside the project spaces when the Project
56-
Steward has a reasonable belief that an individual's behavior may have a
56+
Stewards have a reasonable belief that an individual's behavior may have a
5757
negative impact on the project or its community.
5858

5959
## Conflict Resolution
@@ -69,12 +69,11 @@ dispute. If you are unable to resolve the matter for any reason, or if the
6969
behavior is threatening or harassing, report it. We are dedicated to providing
7070
an environment where participants feel welcome and safe.
7171

72-
Reports should be directed to [email protected], the Project Steward for
73-
Cirq. It is the Project Steward’s duty to receive and address reported
74-
violations of the Code of Conduct. They will then work with a committee
75-
consisting of representatives from the Open Source Programs Office and the
76-
Google Open Source Strategy team. If for any reason you are uncomfortable
77-
reaching out to the Project Steward, please email [email protected].
72+
Reports should be directed to [email protected],
73+
the project stewards at Google Quantum AI. They will then work with a committee
74+
consisting of representatives from the Open Source Programs Office and the
75+
Google Open Source Strategy team. If for any reason you are uncomfortable
76+
reaching out to the Project Stewards, please email [email protected].
7877

7978
We will investigate every complaint, but you may not receive a direct response.
8079
We will use our discretion in determining when and how to follow up on reported

README.rst

+6-1
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,6 @@ Please read our `code of conduct <https://github.com/quantumlib/cirq/blob/main/C
102102
**Cirq Cynque** is our weekly meeting for contributors to discuss upcoming features, designs, issues, community and status of different efforts.
103103
To get an invitation please join the `cirq-dev email list <https://groups.google.com/forum/#!forum/cirq-dev>`__ which also serves as yet another platform to discuss contributions and design ideas.
104104

105-
106105
See Also
107106
--------
108107

@@ -118,4 +117,10 @@ For a powerful quantum circuit simulator that integrates well with Cirq, we reco
118117

119118
Finally, `ReCirq <https://github.com/quantumlib/ReCirq>`__ contains real world experiments using Cirq.
120119

120+
Contact
121+
-------
122+
123+
For any questions or concerns not addressed here, please feel free to reach out to
124+
125+
121126
Cirq is not an official Google product. Copyright 2019 The Cirq Developers

0 commit comments

Comments
 (0)