This is an automated email from the ASF dual-hosted git repository.
dinglei pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/rocketmq-site.git
The following commit(s) were added to refs/heads/master by this push:
new 54e28d7 update the detail information about RIP
new 0a8c531 Merge pull request #42 from wlliqipeng/master
54e28d7 is described below
commit 54e28d7be536a647cc38e67ccd1633422a79acac
Author: wlliqipeng <[email protected]>
AuthorDate: Thu Jan 17 14:17:29 2019 +0800
update the detail information about RIP
---
_pages/community.md | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/_pages/community.md b/_pages/community.md
index bc7ab73..b23348f 100644
--- a/_pages/community.md
+++ b/_pages/community.md
@@ -16,14 +16,12 @@ excerpt: 'Apache RocketMQ™ is an open source distributed
messaging and streami
# RIP(RocketMQ Improvement Proposals)
In the past, we hoped to add a new feature to RocketMQ by propose a issue on
Github. It's a nice way for a request but not very formal and easy to trace and
manage. So We introduce the RIP(RocketMQ Improvement Proposal) mechanism to
replace the current Feature Request Process.
RIPs should be used for significant user-facing or cross-cutting changes, not
small incremental improvements. When in doubt, if a committer thinks a change
needs an RIP, it does.
+
+# How to contribute
It is easy to start a RIP from sending proposals to mailing lists. And the
whole procedure of a RIP may follow below:
-
-[RIP
Template](https://docs.google.com/document/d/19JssoEGnNp1x9MoXVMoeGCWSBnBdyv97FuGcIH1fV1g/edit#heading=h.nwczedg8v2na)
-
-[RIP-1 MQTT
Bridge](https://docs.google.com/document/d/1G1-aJ74ZTjy_rxtJU3jm_YoICexNTdUVSR9E78K9xlo/edit?usp=sharing)
-
+You can find detailed information about RIP in [RocketMQ Improvement
Proposal](https://github.com/apache/rocketmq/wiki/RocketMQ-Improvement-Proposal),and
all the RIP have migrated to the [RockeMQ
Wiki](https://github.com/apache/rocketmq/wiki)
# Ecosystem
