[servicecomb-website] 01/01: Update contributing.md

[li...@apache.org]

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

littlecui pushed a commit to branch little-cui-patch-1
in repository https://gitbox.apache.org/repos/asf/servicecomb-website.git

commit ffbea890ecce555cf1012beba7659f8dce80bab6
Author: little-cui <su...@qq.com>
AuthorDate: Wed Oct 16 15:24:14 2019 +0800

    Update contributing.md
---
 _developers/contributing.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/_developers/contributing.md b/_developers/contributing.md
index f105732..9e83a76 100755
--- a/_developers/contributing.md
+++ b/_developers/contributing.md
@@ -45,6 +45,7 @@ We recommend to work on the code from  [Github](https://github.com/search?q=org%
 | [Service Center](https://github.com/apache/servicecomb-service-center)               | Service registration and discovery | Go       |
 | [Saga](https://github.com/apache/servicecomb-saga)                                   | Data Eventually Consistency Solution for Microservice | Java     |
 | [Website](https://github.com/apache/servicecomb-website) | ServiceComb Website | Markdown |
+| [Kie](https://github.com/apache/servicecomb-kie) | Service for configuration management | Go |
 
 If you intend to work on the code and provide patches and other work you want to submit to the Apache ServiceComb projects, then you can fork the project on github and work on your own fork. The custom work you do should be done on branches you create, which can then be committed and pushed upstream, and then submitted to Apache ServiceComb as PRs (pull requests). You can find many resources online how to work on github projects and how to submit work to these projects.