Skip to content
Permalink
Browse files
brpc website 1.0 improve zh pages
  • Loading branch information
huxiguo authored and huxiguo committed Feb 16, 2022
1 parent 564a590 commit e93153b9f79306cbb29c16c829339ba0106e308c
Showing 9 changed files with 2,919 additions and 281 deletions.
@@ -55,16 +55,16 @@ The following is the structure of the /content folder in which the files you wil
incubator-brpc-website
- content
| - en
| | - community
| | | - index.md
| | - docs
| | | - community
| | | | - index.md
| | | - DownloadBRPC
| | | | - index.md
| | | - ...
| - zh
| | - community
| | | - index.md
| | - docs
| | | - community
| | | | - index.md
| | | - DownloadBRPC
| | | | - index.md
| | | - ...
BIN +0 Bytes (100%) content/.DS_Store
Binary file not shown.
BIN +0 Bytes (100%) content/en/.DS_Store
Binary file not shown.
BIN +0 Bytes (100%) content/en/docs/.DS_Store
Binary file not shown.
@@ -27,8 +27,7 @@ limitations under the License.
## Apache brpc (incubating) Downloads

Apache brpc (incubating) is released as a source artifact.
We are still working on our first apache release,
hopefully it will be done in Oct 2019.
We are pleased to announce our 1.0.0 release as below.


### Release Candidate
@@ -6,63 +6,6 @@ menu:
main:
weight: 40
description: About bRPC community.

main_channels:
- title: >
<a href="https://twitter.com/grpcio" target="_blank" rel="noopener"><i class="fab
fa-twitter"></i>&nbsp;Twitter</a>
desc: >
Follow us at [@grpcio][] for real-time news on blogs posts, events, and
more.
- title: >
<a href="https://groups.google.com/forum/#!forum/grpc-io" target="_blank" rel="noopener"><i class="fab fa-google"></i>&nbsp;Google Group</a>
desc: >
Join the [grpc-io][] forum to ask questions and get the latest
developer news, including [gRFCs][].
other_channels:
- title: >
<a href="https://gitter.im/grpc/grpc"
target="_blank" rel="noopener"><i class="fab
fa-gitter"></i>&nbsp;Gitter</a>
desc: >
Chat with other gRPC developers in the
[`grpc/grpc`](https://gitter.im/grpc/grpc) community.
- title: >
<a href="https://stackoverflow.com/questions/tagged/grpc+protoc"
target="_blank" rel="noopener"><i class="fab
fa-stack-overflow"></i>&nbsp;Stack Overflow</a>
desc: >
Ask technical questions about [gRPC][grpc-tag] & [protoc,][protoc-tag] and
find answers.
- title: >
<a href="https://www.reddit.com/r/grpc/"
target="_blank" rel="noopener"><i class="fab
fa-reddit"></i>&nbsp;Reddit</a>
desc: >
Consult the [`r/grpc`](https://www.reddit.com/r/grpc/) subreddit for
discussions related to gRPC.
community_resources:
- title: >
<a href="https://www.meetup.com/gRPCio/"
target="_blank" rel="noopener"><i class="fab
fa-meetup"></i>&nbsp;Meetup</a>
desc: >
Mark your [calendars][calendar] and
join us [online][gRPCio] for project updates, live demos, and more.
- title: >
<a href="https://bit.ly/grpcmeetings"
target="_blank" rel="noopener"><i class="fas
fa-file-alt"></i>&nbsp;Meeting doc</a>
desc: >
Consult the [gRPC Community Meeting Working Doc][meeting-doc] for meeting
details.
- title: >
<a href="https://www.youtube.com/channel/UCrnk1HWelWnYtF78YZX80fg"
target="_blank" rel="noopener"><i class="fab
fa-youtube"></i>&nbsp;YouTube</a>
desc: >
Missed a meeting? No problem. Visit the [gRPC channel][grpc-youtube] for
meeting videos.
---
<!--
{% comment %}
@@ -83,9 +26,6 @@ limitations under the License.
{% endcomment %}
-->

<br/><br/><br/>


## Apache brpc (incubating) Community

Every volunteer project obtains its strength from the people involved in it. We invite you to participate as much or as little as you choose.
@@ -117,7 +57,7 @@ Before submitting an issue, please:

* Verify that the bug does in fact exist.
* Search the issue tracker to verify there is no existing issue reporting the bug you've found.
* Consider tracking down the bug yourself in the Wink's source and submitting a patch along with your bug report. This is a great time saver for the Wink developers and helps ensure the bug will be fixed quickly.
* Consider tracking down the bug yourself in the bRPC's source and submitting a patch along with your bug report. This is a great time saver for the bRPC developers and helps ensure the bug will be fixed quickly.



@@ -24,23 +24,21 @@ See the License for the specific language governing permissions and
limitations under the License.
{% endcomment %}
-->
## Apache brpc (incubating) Downloads
## 下载 Apache bRPC (incubating)

Apache brpc (incubating) is released as a source artifact.
We are still working on our first apache release,
hopefully it will be done in Oct 2019.
Apache brpc(孵化)作为源工件发布。我们很高兴宣布我们的1.0.0版本已经发布如下了!


### Release Candidate
### 候选版本
<!--when pass vote, we can change it back to Release Artifacts
-->
<table class="table table-hover sortable">
<thead>
<tr>
<th><b>Name</b></th>
<th><b>Archive</b></th>
<th><b>SHA-512</b></th>
<th><b>Signature</b></th>
<th><b>名字</b></th>
<th><b>存档</b></th>
<th><b>加密算法</b></th>
<th><b>签名</b></th>
</tr>
</thead>
<tbody>
@@ -66,18 +64,8 @@ hopefully it will be done in Oct 2019.
</tbody>
</table>

Choose a source distribution in either *tar* or *zip* format,
and [verify](https://www.apache.org/dyn/closer.cgi#verify)
using the corresponding *pgp* signature (using the committer file in
[KEYS](https://downloads.apache.org/incubator/brpc/KEYS)).
If you cannot do that, the *md5* hash file may be used to check that the
download has completed OK.
选择*tar**zip*格式的源发行版,并使用相应的*pgp*签名(使用[密钥](https://downloads.apache.org/incubator/brpc/KEYS)中的提交者文件)进行[验证](https://www.apache.org/dyn/closer.cgi#verify)。如果您无法做到这一点,可以使用*md5*哈希文件检查下载是否已完成。

For fast downloads, current source distributions are hosted on mirror servers;
older source distributions are in the
[archive](https://archive.apache.org/dist/incubator/brpc/).
If a download from a mirror fails, retry, and the second download will likely
succeed.
为了快速下载,当前的源发行版托管在镜像服务器上;较旧的源发行版在[存档](https://archive.apache.org/dist/incubator/brpc/)中。如果从镜像下载失败,请重试,第二次下载可能会成功。

For security, hash and signature files are always hosted at
[Apache](https://www.apache.org).
为了安全起见,哈希文件和签名文件始终托管在[Apache](https://www.apache.org)上。
@@ -8,63 +8,6 @@ menu:
main:
weight: 40
description: 关于Apache bRPC社区。

main_channels:
- title: >
<a href="https://twitter.com/grpcio" target="_blank" rel="noopener"><i class="fab
fa-twitter"></i>&nbsp;Twitter</a>
desc: >
Follow us at [@grpcio][] for real-time news on blogs posts, events, and
more.
- title: >
<a href="https://groups.google.com/forum/#!forum/grpc-io" target="_blank" rel="noopener"><i class="fab fa-google"></i>&nbsp;Google Group</a>
desc: >
Join the [grpc-io][] forum to ask questions and get the latest
developer news, including [gRFCs][].
other_channels:
- title: >
<a href="https://gitter.im/grpc/grpc"
target="_blank" rel="noopener"><i class="fab
fa-gitter"></i>&nbsp;Gitter</a>
desc: >
Chat with other gRPC developers in the
[`grpc/grpc`](https://gitter.im/grpc/grpc) community.
- title: >
<a href="https://stackoverflow.com/questions/tagged/grpc+protoc"
target="_blank" rel="noopener"><i class="fab
fa-stack-overflow"></i>&nbsp;Stack Overflow</a>
desc: >
Ask technical questions about [gRPC][grpc-tag] & [protoc,][protoc-tag] and
find answers.
- title: >
<a href="https://www.reddit.com/r/grpc/"
target="_blank" rel="noopener"><i class="fab
fa-reddit"></i>&nbsp;Reddit</a>
desc: >
Consult the [`r/grpc`](https://www.reddit.com/r/grpc/) subreddit for
discussions related to gRPC.
community_resources:
- title: >
<a href="https://www.meetup.com/gRPCio/"
target="_blank" rel="noopener"><i class="fab
fa-meetup"></i>&nbsp;Meetup</a>
desc: >
Mark your [calendars][calendar] and
join us [online][gRPCio] for project updates, live demos, and more.
- title: >
<a href="https://bit.ly/grpcmeetings"
target="_blank" rel="noopener"><i class="fas
fa-file-alt"></i>&nbsp;Meeting doc</a>
desc: >
Consult the [gRPC Community Meeting Working Doc][meeting-doc] for meeting
details.
- title: >
<a href="https://www.youtube.com/channel/UCrnk1HWelWnYtF78YZX80fg"
target="_blank" rel="noopener"><i class="fab
fa-youtube"></i>&nbsp;YouTube</a>
desc: >
Missed a meeting? No problem. Visit the [gRPC channel][grpc-youtube] for
meeting videos.
---
<!--
{% comment %}
@@ -85,61 +28,58 @@ limitations under the License.
{% endcomment %}
-->

<br/><br/><br/>


## Apache brpc (incubating) Community
## Apache brpc (孵化) 社区

Every volunteer project obtains its strength from the people involved in it. We invite you to participate as much or as little as you choose.
每个志愿者项目的力量都来自参与其中的人。我们邀请您尽可能多或少地参与。

You can:
你可以:

* Use our project and provide a feedback.
* Provide us with the use-cases.
* Report bugs and submit patches.
* Contribute code, testcase, documentation.
* 使用我们的项目并提供反馈。
* 向我们提供用例。
* 报告错误并提交补丁。
* 贡献代码、测试用例和文档。

Visit the [Contributing] page for more information.
更多有关信息,请访问[贡献]页面。

### Mailing list
### 邮件列表

Get help using bRPC or contribute to the project on our mailing lists:
使用bRPC获取帮助或在我们的邮件列表中为项目做出贡献:

* [dev@brpc.apache.org](dev@brpc.apache.org) is for people who want to contribute code to bRPC. [subscribe](mailto:dev-subscribe@brpc.apache.org?subject=send%20this%20email%20to%20subscribe), [unsubscribe](mailto:dev-unsubscribe@brpc.apache.org?subject=send%20this%20email%20to%20unsubscribe), [archives](https://www.mail-archive.com/dev@brpc.apache.org/)
* [commits@brpc.apache.org](commits@brpc.apache.org) is for commit messages and patches to bRPC. [subscribe](mailto:commits-subscribe@brpc.apache.org?subject=send%20this%20email%20to%20subscribe), [unsubscribe](mailto:commits-unsubscribe@brpc.apache.org?subject=send%20this%20email%20to%20unsubscribe), [archives](https://www.mail-archive.com/commits@brpc.apache.org/)
* [dev@brpc.apache.org](dev@brpc.apache.org)适用于希望为bRPC贡献代码的人。[订阅](mailto:dev-subscribe@brpc.apache.org?subject=send%20this%20email%20to%20subscribe), [取消订阅](mailto:dev-unsubscribe@brpc.apache.org?subject=send%20this%20email%20to%20unsubscribe), [存档](https://www.mail-archive.com/dev@brpc.apache.org/)
* [commits@brpc.apache.org](commits@brpc.apache.org)用于向bRPC提交消息和修补程序。[订阅](mailto:commits-subscribe@brpc.apache.org?subject=send%20this%20email%20to%20subscribe), [取消订阅](mailto:commits-unsubscribe@brpc.apache.org?subject=send%20this%20email%20to%20unsubscribe), [存档](https://www.mail-archive.com/commits@brpc.apache.org/)


### Issue tracker
### 问题追踪

#### Bug Reports
#### Bug报告

Found bug? Enter an issue in the [Issue Tracker](https://github.com/apache/incubator-brpc/issues).
发现bug? 在[问题追踪](https://github.com/apache/incubator-brpc/issues)页面中提交问题。

Before submitting an issue, please:
在提交问题之前,请:

* Verify that the bug does in fact exist.
* Search the issue tracker to verify there is no existing issue reporting the bug you've found.
* Consider tracking down the bug yourself in the Wink's source and submitting a patch along with your bug report. This is a great time saver for the Wink developers and helps ensure the bug will be fixed quickly.
* 验证该错误是否确实存在。
* 搜索问题追踪器,以确认没有报告您发现的错误的现有问题。
* 考虑自己在bRPC的源代码中跟踪bug并提交一个补丁和bug报告。这对bRPC开发人员来说是一个很好的省时方法,并且有助于确保bug能够快速修复。



#### Feature Requests
#### 功能请求

Enhancement requests for new features are also welcome. The more concrete and rationale the request is, the greater the chance it will incorporated into future releases.
我们也欢迎对新功能的增强请求。请求越具体,理由越充分,它被纳入未来版本的可能性就越大。

[https://github.com/apache/incubator-brpc/issues](https://github.com/apache/incubator-brpc/issues)


### Source Code
### 源代码

The project sources are accessible via the [source code repository](https://github.com/apache/incubator-brpc) which is on github.
可以通过github上的[源代码库](https://github.com/apache/incubator-brpc)访问项目源代码。


### Website Source Code
### 网站源代码

The project website sources are accessible via the [website source code repository](https://github.com/apache/incubator-brpc-website) which is on github also.
可以通过github上的[网站源代码库](https://github.com/apache/incubator-brpc-website)访问项目网站源代码。

### bRPC Team Members
### bRPC团队成员

<table class="table table-hover">
<tr>

0 comments on commit e93153b

Please sign in to comment.