Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update contributing.md #201

Closed
wants to merge 1 commit into from
Closed

Update contributing.md #201

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
1 change: 1 addition & 0 deletions _developers/contributing.md
View file
Open in desktop
Expand Up @@ -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.