This is an automated email from the ASF dual-hosted git repository.
hyunkun pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-dubbo-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 3bca78f Revert "Delete guide_dev.md"
3bca78f is described below
commit 3bca78f071a88fb79220b58ae8bc3a2c841337a2
Author: Huang Yunkun <hty...@gmail.com>
AuthorDate: Wed Oct 31 10:12:12 2018 +0800
Revert "Delete guide_dev.md"
This reverts commit adb1d2927004dcaa0815ed95200aefc0a6d8a44c.
---
docs/zh-cn/developers/guide_dev.md | 66 ++++++++++++++++++++++++++++++++++++++
1 file changed, 66 insertions(+)
diff --git a/docs/zh-cn/developers/guide_dev.md
b/docs/zh-cn/developers/guide_dev.md
new file mode 100644
index 0000000..7063606
--- /dev/null
+++ b/docs/zh-cn/developers/guide_dev.md
@@ -0,0 +1,66 @@
+## Contributing to Dubbo
+
+Dubbo is released under the non-restrictive Apache 2.0 license, and follows a
very standard Github development process, using Github tracker for issues and
merging pull requests into master. If you want to contribute even something
trivial please do not hesitate, but follow the guidelines below.
+
+### Sign the Contributor License Agreement
+Before we accept a non-trivial patch or pull request we will need you to sign
the Contributor License Agreement. Signing the contributor’s agreement does not
grant anyone commit rights to the main repository, but it does mean that we can
accept your contributions, and you will get an author credit if we do. Active
contributors might be asked to join the core team, and given the ability to
merge pull requests.
+
+### Contact
+
+#### Mailing list
+
+The mailing list is the recommended way for discussing almost anything that
related to Dubbo. Please refer to this
[guide](https://github.com/apache/incubator-dubbo/wiki/Mailing-list-subscription-guide)
for detailed documentation on how to subscribe.
+
+-
[d...@dubbo.incubator.apache.org](mailto:dev-subscr...@dubbo.incubator.apache.org):
the develop mailing list, you can ask question here if you have encountered
any problem when using or developing Dubbo.
+-
[comm...@dubbo.incubator.apache.org](mailto:commits-subscr...@dubbo.incubator.apache.org):
all the commits will be sent to this mailing list. You can subscribe to it if
you are interested in Dubbo's development.
+-
[notificat...@dubbo.incubator.apache.org](mailto:notification-subscr...@dubbo.incubator.apache.org):
all the Github [issue](https://github.com/apache/incubator-dubbo/issues)
updates and [pull request](https://github.com/apache/incubator-dubbo/pulls)
updates will be sent to this mailing list.
+
+### Reporting issue
+
+Please follow the
[template](https://github.com/apache/incubator-dubbo/issues/new?template=dubbo-issue-report-template.md)
for reporting any issues.
+
+### Code Conventions
+Our code style is almost in line with the standard java conventions (Popular
IDE's default setting satisfy this), with the following additional restricts:
+* If there are more than 120 characters in current line, start a new line.
+
+* Make sure all new .java files to have a simple Javadoc class comment with at
least a @date tag identifying birth, and preferably at least a paragraph on
what the class is for.
+
+* Add the ASF license header comment to all new .java files (copy from
existing files in the project)
+
+* Make sure no @author tag added to the file you contribute since @author tag
is not used at Apache, other ways such as cvs will record all your
contributions fairly.
+
+* Add some Javadocs and, if you change the namespace, some XSD doc elements.
+
+* A few unit tests should be added for a new feature or an important bugfix.
+
+* If no-one else is using your branch, please rebase it against the current
master (or other target branch in the main project).
+
+* When writing a commit message please follow these conventions, if you are
fixing an existing issue please add Fixes #XXX at the end of the commit message
(where XXX is the issue number).
+
+### Contribution flow
+
+This is a rough outline of what a contributor's workflow looks like:
+
+* Fork the current repository
+* Create a topic branch from where to base the contribution. This is usually
master.
+* Make commits of logical units.
+* Make sure commit messages are in the proper format (see below).
+* Push changes in a topic branch to your forked repository.
+* Follow the checklist in the [pull request
template](https://github.com/apache/incubator-dubbo/blob/master/PULL_REQUEST_TEMPLATE.md)
+* Before you sending out the pull request, please sync your forked repository
with remote repository, this will make your pull request simple and clear. See
guide below:
+```
+git remote add upstream g...@github.com:apache/incubator-dubbo.git
+git fetch upstream
+git rebase upstream/master
+git checkout -b your_awesome_patch
+... add some work
+git push origin your_awesome_patch
+```
+* Submit a pull request to apache/incubator-dubbo and wait for the reply.
+
+Thanks for contributing!
+
+### Code style
+
+We provide a template file
[dubbo_codestyle_for_idea.xml](https://github.com/apache/incubator-dubbo/tree/master/codestyle/dubbo_codestyle_for_idea.xml)
for IntelliJ idea, you can import it to you IDE.
+If you use Eclipse you can config manually by referencing the same file.
\ No newline at end of file
