[incubator-dubbo.wiki] branch master updated: Updated Dubbo extension guide (markdown)

[wa...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

wangxin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-dubbo.wiki.git


The following commit(s) were added to refs/heads/master by this push:
     new 5e1f1e3  Updated Dubbo extension guide (markdown)
5e1f1e3 is described below

commit 5e1f1e3b302b5300b871b45c97618dd52f009acc
Author: Xin Wang <xi...@gmail.com>
AuthorDate: Mon Nov 19 22:42:50 2018 +0800

    Updated Dubbo extension guide (markdown)
---
 Dubbo-extension-guide.md | 36 +-----------------------------------
 1 file changed, 1 insertion(+), 35 deletions(-)

diff --git a/Dubbo-extension-guide.md b/Dubbo-extension-guide.md
index 2b867c1..b95d037 100644
--- a/Dubbo-extension-guide.md
+++ b/Dubbo-extension-guide.md
@@ -1,35 +1 @@
-Dubbo Use microkernel + plugin design pattern. Microkernel is only responsible for assembling plugins, the functions of Dubbo are implemented by extension points(plugins), which means that all functions of Dubbo can be replaced by user customized extension.
-
-## Dubbo Ecosystem
-
-We recommend you to put extension to Dubbo [ecosystem](https://github.com/dubbo). Using this pattern will keep the core repository cleaner and decrease the maintains work. With less code also speed up core repository build process.
-
-## Dependency
-Implement your own Dubbo extension, in general is just dependence on API jar correspond to what you want.
-For example:
-```xml
-<dependency>
-    <groupId>org.apache.dubbo</groupId>
-    <artifactId>dubbo-serialization-api</artifactId>
-    <version>${dubbo.version}</version>
-</dependency>
-```
-
-## Src Guide
-Usually, implement special extension, just need reference the [Developer Guide](http://dubbo.apache.org/#/docs/dev/build.md?lang=en-us) docs. Implement necessary interface and adapt extension to dubbo. Besides, some others should be considered:
-1. Well tested. You should write unit test and mock test to eliminate potential bugs.
-2. No warning, if some warning cannot to avoid, use @SuppressWarnings to suppress it, but do not abuse it.
-3. README. Add necessary readme to show how to use your extension, and something to take notice.
-4. License. Make sure of use Apache License 2.0.
-
-## Notify the Community
-1. Commit your code to [GitHub](https://github.com).
-2. Join the mail list (recommended). [HowTo](https://github.com/apache/incubator-dubbo/wiki/Mailing-list-subscription-guide)
-2. Send email to dev@incubator.dubbo.apache.org to notify the community
-3. Usually, after sending email, community will discuss your extension, and Administrators of dubbo group will contact you for transfer project to dubbo ecosystem.
-
-## Transfer Project to Dubbo Group
-1. Administrators of dubbo group will ask you, grant your project owner to dubbo.
-2. Administrators of dubbo group will create a new project under dubbo group and invite you join the project.
-3. Once you accept the invitation, you can transfer your project to new project under dubbo group.
-4. Existing members of dubbo group will do the code review. After that you may make some improvement to code.
\ No newline at end of file
+Dubbo extension guide has been migrated to http://dubbo.apache.org/en-us/docs/developers/contributor-guide/dubbo-extension-guide_dev.html
\ No newline at end of file