Skip to content

Commit 27a0142

Browse files
authored
OpenEthereum rebranding (#31)
1 parent 698fa6e commit 27a0142

File tree

716 files changed

+4881
-4110
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

716 files changed

+4881
-4110
lines changed

.cargo/config

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
11
[target.x86_64-pc-windows-msvc]
2-
# Link the C runtime statically ; https://github.com/paritytech/parity-ethereum/issues/6643
2+
# Link the C runtime statically ; https://github.com/openethereum/openethereum/issues/6643
33
rustflags = ["-Ctarget-feature=+crt-static"]

.github/CODE_OF_CONDUCT.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@
22

33
## 1. Purpose
44

5-
A primary goal of Parity is to be inclusive to the largest number of contributors, with the most varied and diverse backgrounds possible. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, ability, ethnicity, socioeconomic status, and religion (or lack thereof).
5+
A primary goal of OpenEthereum is to be inclusive to the largest number of contributors, with the most varied and diverse backgrounds possible. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, ability, ethnicity, socioeconomic status, and religion (or lack thereof).
66

77
This code of conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.
88

9-
We invite all those who participate in Parity to help us create safe and positive experiences for everyone.
9+
We invite all those who participate in OpenEthereum to help us create safe and positive experiences for everyone.
1010

1111
## 2. Open Source Citizenship
1212

@@ -63,7 +63,7 @@ Additionally, community organizers are available to help community members engag
6363

6464
## 7. Addressing Grievances
6565

66-
If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify Parity Technologies with a concise description of your grievance. Your grievance will be handled in accordance with our existing governing policies.
66+
If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify OpenEthereum Technologies with a concise description of your grievance. Your grievance will be handled in accordance with our existing governing policies.
6767

6868
## 8. Scope
6969

@@ -73,7 +73,7 @@ This code of conduct and its related procedures also applies to unacceptable beh
7373

7474
## 9. Contact info
7575

76-
You can contact Parity via Email: [email protected]
76+
You can contact OpenEthereum via Email: [email protected]
7777

7878
## 10. License and attribution
7979

.github/CONTRIBUTING.md

+11-11
Original file line numberDiff line numberDiff line change
@@ -2,31 +2,31 @@
22

33
## Do you have a question?
44

5-
Check out our [Basic Usage](https://wiki.parity.io/Basic-Usage), [Configuration](https://wiki.parity.io/Configuring-Parity-Ethereum), and [FAQ](https://wiki.parity.io/FAQ) articles on our [wiki](https://wiki.parity.io/)!
5+
Check out our [Basic Usage](https://openethereum.github.io/wiki/Basic-Usage), [Configuration](https://openethereum.github.io/wiki/Configuring-OpenEthereum), and [FAQ](https://openethereum.github.io/wiki/FAQ) articles on our [wiki](https://openethereum.github.io/wiki)!
66

77
See also frequently asked questions [tagged with `parity`](https://ethereum.stackexchange.com/questions/tagged/parity?sort=votes&pageSize=50) on Stack Exchange.
88

99
## Report bugs!
1010

1111
Do **not** open an issue on Github if you think your discovered bug could be a **security-relevant vulnerability**. Please, read our [security policy](../SECURITY.md) instead.
1212

13-
Otherwise, just create a [new issue](https://github.com/paritytech/parity-ethereum/issues/new) in our repository and state:
13+
Otherwise, just create a [new issue](https://github.com/openethereum/openethereum/issues/new) in our repository and state:
1414

15-
- What's your Parity Ethereum version?
15+
- What's your OpenEthereum version?
1616
- What's your operating system and version?
17-
- How did you install Parity Ethereum?
17+
- How did you install OpenEthereum?
1818
- Is your node fully synchronized?
1919
- Did you try turning it off and on again?
2020

2121
Also, try to include **steps to reproduce** the issue and expand on the **actual versus expected behavior**.
2222

2323
## Contribute!
2424

25-
If you would like to contribute to Parity Ethereum, please **fork it**, fix bugs or implement features, and [propose a pull request](https://github.com/paritytech/parity-ethereum/compare).
25+
If you would like to contribute to OpenEthereum, please **fork it**, fix bugs or implement features, and [propose a pull request](https://github.com/openethereum/openethereum/compare).
2626

2727
### Labels & Milestones
2828

29-
We use [labels](https://github.com/paritytech/parity-ethereum/labels) to manage PRs and issues and communicate the state of a PR. Please familiarize yourself with them. Furthermore we are organizing issues in [milestones](https://github.com/paritytech/parity-ethereum/milestones). Best way to get started is to a pick a ticket from the current milestone tagged [`easy`](https://github.com/paritytech/parity-ethereum/labels/Q2-easy%20%F0%9F%92%83) and get going, or [`mentor`](https://github.com/paritytech/parity-ethereum/labels/Q1-mentor%20%F0%9F%95%BA) and get in contact with the mentor offering their support on that larger task.
29+
We use [labels](https://github.com/openethereum/openethereum/labels) to manage PRs and issues and communicate the state of a PR. Please familiarize yourself with them. Furthermore we are organizing issues in [milestones](https://github.com/openethereum/openethereum/milestones). Best way to get started is to a pick a ticket from the current milestone tagged [`easy`](https://github.com/openethereum/openethereum/labels/Q2-easy%20%F0%9F%92%83) and get going, or [`mentor`](https://github.com/openethereum/openethereum/labels/Q1-mentor%20%F0%9F%95%BA) and get in contact with the mentor offering their support on that larger task.
3030

3131
### Rules
3232

@@ -35,22 +35,22 @@ There are a few basic ground-rules for contributors (including the maintainer(s)
3535
* **No pushing directly to the master branch**.
3636
* **All modifications** must be made in a **pull-request** to solicit feedback from other contributors.
3737
* Pull-requests cannot be merged before CI runs green and two reviewers have given their approval.
38-
* Contributors should adhere to the [Parity Ethereum Style Guide](https://wiki.parity.io/Parity-Ethereum-Style-Guide).
38+
* Contributors should adhere to the [Parity Ethereum Style Guide](https://openethereum.github.io/wiki/Parity-Ethereum-Style-Guide).
3939

4040
### Recommendations
4141

42-
* **Non-master branch names** *should* be prefixed with a short name moniker, followed by the associated Github Issue ID (if any), and a brief description of the task using the format `<GITHUB_USERNAME>-<ISSUE_ID>-<BRIEF_DESCRIPTION>` (e.g. `gavin-123-readme`). The name moniker helps people to inquiry about their unfinished work, and the GitHub Issue ID helps your future self and other developers (particularly those who are onboarding) find out about and understand the original scope of the task, and where it fits into Parity Ethereum [Projects](https://github.com/paritytech/parity-ethereum/projects).
42+
* **Non-master branch names** *should* be prefixed with a short name moniker, followed by the associated Github Issue ID (if any), and a brief description of the task using the format `<GITHUB_USERNAME>-<ISSUE_ID>-<BRIEF_DESCRIPTION>` (e.g. `gavin-123-readme`). The name moniker helps people to inquiry about their unfinished work, and the GitHub Issue ID helps your future self and other developers (particularly those who are onboarding) find out about and understand the original scope of the task, and where it fits into Parity Ethereum [Projects](https://github.com/openethereum/openethereum/projects).
4343
* **Remove stale branches periodically**
4444

4545
### Preparing Pull Requests
4646

47-
* If your PR does not alter any logic (e.g. comments, dependencies, docs), then it may be tagged [`insubstantial`](https://github.com/paritytech/parity-ethereum/pulls?q=is%3Aopen+is%3Apr+label%3A%22A2-insubstantial+%F0%9F%91%B6%22).
47+
* If your PR does not alter any logic (e.g. comments, dependencies, docs), then it may be tagged [`insubstantial`](https://github.com/openethereum/openethereum/pulls?q=is%3Aopen+is%3Apr+label%3A%22A2-insubstantial+%F0%9F%91%B6%22).
4848

49-
* Once a PR is ready for review please add the [`pleasereview`](https://github.com/paritytech/parity-ethereum/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+label%3A%22A0-pleasereview+%F0%9F%A4%93%22+) label.
49+
* Once a PR is ready for review please add the [`pleasereview`](https://github.com/openethereum/openethereum/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+label%3A%22A0-pleasereview+%F0%9F%A4%93%22+) label.
5050

5151
### Reviewing Pull Requests*:
5252

53-
* At least two reviewers are required to review PRs (even for PRs tagged [`insubstantial`](https://github.com/paritytech/parity-ethereum/pulls?q=is%3Aopen+is%3Apr+label%3A%22A2-insubstantial+%F0%9F%91%B6%22)).
53+
* At least two reviewers are required to review PRs (even for PRs tagged [`insubstantial`](https://github.com/openethereum/openethereum/pulls?q=is%3Aopen+is%3Apr+label%3A%22A2-insubstantial+%F0%9F%91%B6%22)).
5454

5555
When doing a review, make sure to look for any:
5656

.github/ISSUE_TEMPLATE.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
_Before filing a new issue, please **provide the following information**._
22

3-
- **Parity Ethereum version**: 0.0.0
3+
- **OpenEthereum version**: 0.0.0
44
- **Operating system**: Windows / MacOS / Linux
55
- **Installation**: homebrew / one-line installer / built from source
66
- **Fully synchronized**: no / yes

Cargo.lock

+75-75
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

Cargo.toml

+8-5
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,13 @@
11
[package]
2-
description = "Parity Ethereum client"
3-
name = "parity-ethereum"
2+
description = "OpenEthereum"
3+
name = "openethereum"
44
# NOTE Make sure to update util/version/Cargo.toml as well
5-
version = "2.5.13"
5+
version = "3.0.1"
66
license = "GPL-3.0"
7-
authors = ["Parity Technologies <[email protected]>"]
7+
authors = [
8+
"OpenEthereum developers",
9+
"Parity Technologies <[email protected]>"
10+
]
811

912
[dependencies]
1013
blooms-db = { path = "util/blooms-db" }
@@ -110,7 +113,7 @@ path = "parity/lib.rs"
110113

111114
[[bin]]
112115
path = "parity/main.rs"
113-
name = "parity"
116+
name = "openethereum"
114117

115118
[profile.test]
116119
lto = false

0 commit comments

Comments
 (0)