You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 18, 2023. It is now read-only.
Any crate added to iroh will need to use a license compatible with ours. Any PR that introduces a new crate will require additional review time to audit the crate being introduced, including rationale on why you chose *this* crate, and what alternatives you considered willl speed up the review process.
97
+
Any crate added to beetle will need to use a license compatible with ours. Any PR that introduces a new crate will require additional review time to audit the crate being introduced, including rationale on why you chose *this* crate, and what alternatives you considered willl speed up the review process.
98
98
99
99
Crate lists in `Cargo.toml` files must be kept alphabetically sorted.
100
100
101
101
## <aname="prs"></a> Pull Request Guidelines
102
102
103
103
The tests must pass and you must get an approval from someone on the Iroh team before you can merge your PR.
104
104
105
-
Depending on your permissions in the `iroh` repo, you may not have the the ability to "request a review". Instead, please tag your selected reviewers in the PR itself (using the `@`) and specify that you would like them to review. If you are a member of our discord community, you can and should ping your reviewer(s) there as well.
105
+
Depending on your permissions in the `beetle` repo, you may not have the the ability to "request a review". Instead, please tag your selected reviewers in the PR itself (using the `@`) and specify that you would like them to review. If you are a member of our discord community, you can and should ping your reviewer(s) there as well.
106
106
107
-
If you don't know who to tag for review, here are some good guidelines. For any markdown documentations changes, tag `ramfox` or `b5`. If your PR solves an issue that someone else created, tag that person in review. If it's an issue you have created, tag team members who have been discussing the issue. Otherwise, create the PR and note that you aren't sure who to tag! Someone will drop in to give you guidance. If you are apart of our discord community, ask who should be tagged in the `iroh` channel.
107
+
If you don't know who to tag for review, here are some good guidelines. For any markdown documentations changes, tag `ramfox` or `b5`. If your PR solves an issue that someone else created, tag that person in review. If it's an issue you have created, tag team members who have been discussing the issue. Otherwise, create the PR and note that you aren't sure who to tag! Someone will drop in to give you guidance. If you are apart of our discord community, ask who should be tagged in the `beetle` channel.
108
108
109
109
### A note about our current CI testing set up
110
110
111
-
The MacOS testing infrastructure currently does not work on forked branches of `iroh`. If you are working on a forked branch, you will notice that the MacOS tests on your PRs will always fail (because they will not run). This is the only case where you may have a "failing" test and still merge your PR.
111
+
The MacOS testing infrastructure currently does not work on forked branches of `beetle`. If you are working on a forked branch, you will notice that the MacOS tests on your PRs will always fail (because they will not run). This is the only case where you may have a "failing" test and still merge your PR.
112
112
113
113
### Merging
114
114
@@ -163,7 +163,7 @@ Must be one of the following:
163
163
164
164
### Scope
165
165
166
-
The scope could be anything specifying place of the commit change. For example, if I am refactoring something in the `iroh` package, I may start my commit with "refactor(iroh)".
166
+
The scope could be anything specifying place of the commit change. For example, if I am refactoring something in the `beetle` package, I may start my commit with "refactor(beetle)".
167
167
168
168
You can use `*` when the change affects more than a single scope.
169
169
@@ -192,7 +192,7 @@ A detailed explanation can be found in this [document][commit-message-format].
Iroh is a next-generation implementation of the Interplanetary File System ([IPFS](https://ipfs.io)) for Cloud & Mobile platforms.
9
9
10
10
IPFS is a networking protocol for exchanging _content-addressed_ blocks of immutable data. “Content-addressed” means referring to data by the *hash of its content*, which makes the reference unique and verifiable. These two properties make it possible to get data from *any* node in the network that speaks the IPFS protocol, including IPFS content being served by other implementations of IPFS.
11
11
12
-
This repo is a common core for three distributions of iroh:
12
+
This repo is a common core for three distributions of beetle:
13
13
14
-
-**Iroh Cloud:** core features of iroh split into configurable microservices, optimized for running at datacenter scale.
15
-
-**Iroh One:** A select set of iroh cloud features packaged as a single binary for simplified deployment.
14
+
-**Iroh Cloud:** core features of beetle split into configurable microservices, optimized for running at datacenter scale.
15
+
-**Iroh One:** A select set of beetle cloud features packaged as a single binary for simplified deployment.
16
16
-**Iroh Mobile:** iOS & Android libraries that bring efficient data distribution to mobile apps.
17
17
18
-
Here is an [install guide](https://iroh.computer/install).
18
+
Here is an [install guide](https://beetle.computer/install).
19
19
20
20
## Working on Iroh
21
21
Check out the [CONTRIBUTOR docs](./CONTRIBUTOR.md) to get familiar with ways you can contribute to the Iroh project. The [DEVELOPERS docs](./DEVELOPERS.md) will help you get starting with building and developing Iroh.
@@ -26,7 +26,7 @@ A full suite of automated benchmarks is in the works. [this talk](https://www.yo
26
26
27
27
## Who's behind this?
28
28
29
-
[Iroh](https://iroh.computer) is built & maintained by [number 0](https://n0.computer). We're a founder-backed startup hell-bent on building efficient distributed systems software.
29
+
[Iroh](https://beetle.computer) is built & maintained by [number 0](https://n0.computer). We're a founder-backed startup hell-bent on building efficient distributed systems software.
0 commit comments