incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <>
Subject [VOTE] Accept ServiceComb into the Apache Incubator
Date Tue, 14 Nov 2017 06:15:14 GMT
Hi All,

I would like to start a VOTE to bring the ServiceComb project in as an
Apache incubator podling.

The ASF voting rules are described:

A vote for accepting a new Apache Incubator podling is a majority vote for
which only Incubator PMC member votes are binding.

This vote will run for at least 72 hours. Please VOTE as follows
[] +1 Accept ServiceComb into the Apache Incubator
[] +0 Abstain.
[] -1 Do not accept ServiceComb into the Apache Incubator because ...

The proposal is listed below, but you can also access it on the wiki:

Best regards,

Willem Jiang

= ServiceComb Proposal =

== Abstract ==

ServiceComb is a microservice framework that provides a set of tools and
components to make development and deployment of cloud applications easier.
It provides functionalities such as service contract enforcement, service
registration, service discovery, load balance, service reliability (latency
and fault tolerance, flow control and graceful degradation, handler chain
tracing), eventual data consistency and so forth.

== Proposal ==

The goal of this proposal is to bring the existing ServiceComb codebase and
existing developers into the Apache Software Foundation (ASF) in order to
build a vibrant, diverse and self-governed open source community around the
So far the major contributors to the project have been affiliated with
Huawei and Huawei is planning to continue market and sell the Cloud Service
Engine leveraging the ServiceComb framework.
ServiceComb is currently a registered trademark owned by Huawei, and Huawei
is happy to donate this trademark to Apache.

Huawei is submitting this proposal to donate the Service source code and
associated artifacts (documentation, web site content, wiki, etc.) to the
Apache Software Foundation Incubator under the Apache License, Version 2.0
and is asking Incubator PMC to establish an open source community. These
artifacts are currently available on GitHub at and include:
 * Java Chassis: a multi-protocol (RPC & Restful) microservice framework
which adopts contract-first design
 * Service Center: a service registry that enforces service contract upon
service registration and discovery
 * Saga: a distributed coordinator to achieve eventual data consistency
based on the paper "Sagas" by Hector Garcia-Molina and Kenneth Salem
 *  the website repo of ServiceComb.
 * The other projects will be moved to another place if ServiceComb is
accepted by Apache as an incubator project.

== Background ==

Microservices is a variant of the service-oriented architecture (SOA)
architectural style that structures an application as a collection of
loosely coupled services. ServiceComb is an open source microservice
framework initiated as part of Huawei CSE projects (Cloud Service Engine)
which was developed in 2015. It is a part of ServiceStage of Huawei Public
Cloud which is one-stop PaaS platform for enterprises and developers.
Besides ServiceStage, it’s  also used in the Huawei Core Network IOT
Platform and Huawei consumer cloud. The number of  companies using
ServiceComb to develop their enterprise applications, they are,,,,, and the
number is over 5 and counting.

== Rationale ==

ServiceComb has been developed as a total, open source solution for
developing cloud native applications. So far ServiceComb has existed as a
GitHub project with committers mostly working for Huawei. We feel that
moving it to a neutral organization like Apache, with its strong governance
model, is expected to help get more contributions from various
organizations and developers, who may be concerned by exclusive control of
ServiceComb by Huawei.

== Initial Goals ==

Our initial goals are to bring ServiceComb into the ASF, transition
internal engineering processes into the open, and foster a collaborative
development model according to the "Apache Way." Huawei and the current
contributors to ServiceComb plan to develop new functionality in an open,
community-driven way. To get there, the existing internal build, test and
release processes will be refactored to support open development.

 1. More specifically, our initial plan of moving ServiceComb to ASF is
focused on:
 2. open up the governance model in order to simplify and streamline
contributions from the community
 3. move the existing codebase to Apache
 4. integrate with the Apache development process
 5. ensure all dependencies are compliant with Apache License version 2.0
 6. incremental development and releases per Apache guideline

== Current Status ==

=== Meritocracy ===

We intend to substantially expand the initial developer and user community
by running the project in line with the "Apache Way". Users and new
contributors will be treated with respect and welcomed. By participating in
the community and providing quality patches/support that move the project
forward, they will earn merit. They will also  be encouraged to provide
non-code contributions (documentation, events, community management, etc.)
and will gain merit for doing so. Those with a proven support and quality
track record will be encouraged to become committers and PMC members.

=== Community ===
ServiceComb core java sdk is developed by Huawei Cloud team, and is widely
used inside Huawei. It also includes developers from other companies like
Movitech, Qianmi,, using ServiceComb to develop MicroServices.

=== Core Developers ===
The core developers are a diverse group of developers, some of whom  are
already experienced open source developers.  There are at least one Apache
Member as well as a number of experienced developers.
 * Ning Jiang,, Apache Member, project architect.
 * Qi Zhang,, project architect
 * Xiang Yin,, Java Chassis, Saga core developer
 * JiMin Wu,, Java Chassis core developer
 * Bao Liu,, Java Chassis core developer
 * Sukesh A C,, Java Chassis developer
 * Mohammad Asif Siddiqui,,
ServiceCenter core developer
 * Yihua Cui,, ServiceCenter core developer

=== Alignment ===
We have looked upon Apache as a model for building a strong developer
community and worked to absorb its essence and adopt its best practices.
There are quite a number of Apache projects we want to integrate with, such
as Apache Camel, Apache ActiveMQ, in order to build a sophisticated
MicroService solution for the user.

== Known Risks ==

Development has been sponsored mostly by one single company. To facilitate
the full transition of the project to the Apache Way governance model,
development must shift towards the meritocracy-centric model of growing a
community of contributors balanced with the needs for extreme stability and
core implementation coherency.

=== Orphaned Products ===
Huawei is fully committed to ServiceComb. Moreover, Huawei has a vested
interest in making ServiceComb succeed by driving its close integration
with other ASF projects. We expect this to further reduce the risk of
orphaning the product.

=== Inexperience with Open Source ===
Huawei has been developing and using open source software since a long
time. Some committer have a proven track record in open source at Apache.
Additionally, several ASF veterans agreed to mentor the project and are
listed in this proposal. The project will rely on their guidance and
collective wisdom to accelerate the transition of the entire team of
initial committers towards practicing the Apache Way.

=== Reliance on Salaried Developers ===
Most of the contributors are paid to work in Huawei Cloud Team. While they
might wander from their current employers, they are unlikely to venture far
from their core expertise and thus will continue to be engaged with the
project no matter who their current employers are.

===  Relationship with other Apache products ===
ServiceComb is not related with other Apache products directly.

=== An excessive fascination with the Apache brand ===
While we intend to leverage the Apache ‘branding’ when talking to other
projects as a testament of our project’s ‘neutrality’, we have no plans for
making use of Apache brand in press releases nor posting billboards
advertising acceptance of ServiceComb into Apache Incubator.

=== Documentation ===

The following documentation is relevant to this proposal. Relevant portion
of the documentation will be contributed to the Apache ServiceComb project.

ServiceComb Website:

=== Initial Source ===

=== Source and Intellectual Property Submission Plan ===
As soon as ServiceComb is approved to join Apache Incubator, the source
code will be transitioned via the Software Grant Agreement onto ASF
infrastructure and in turn made available under the Apache License, version
2.0. We know of no legal encumberments that would inhibit the transfer of
source code to the ASF.

=== External Dependencies ===

1. ServiceComb java-chassis depends on some Apache projects:
 * Commons Lang
 * Commons Codec
 * httpClient
 * CXF
 * Tomcat
 * Maven

and other open source projects (organized by license)

 * Netty
 * Spring
 * Spring-Boot
 * Zipkin
 * brave
 * protostuff
 * Jackson
 * Swagger
 * vertx
 * Netflix ribbon
 * Netflix hystrix
 * rxjava
 * Google guava
 * Google guice
 * Aspectj
 * Okhttp
 * hibernate-validator

 * Javassist
 * MIT
 * Mockito
 * SLF4J
 * Bridge-method-annotation
 * EPL 1.0
 * JUnit
 * Logback

2.ServiceComb Saga depends on some Apache projects:
 * Commons IO
 * Commons lang
 * Maven

And other open source projects (organized by license)
 * servicecomb-java-chassis
 * awaitility
 * kamon
 * disruptor
 * rest-assured
 * wiremock
 * Aspectj

 * Javassist

 * Mockito
 * SLF4J
 * Bridge-method-annotation

EPL 1.0:
 * JUnit
 * Logback

As all dependencies are managed using Apache Maven, none of the external
libraries need to be packaged in a source distribution.

3.ServiceComb Service-Center depends on
Open-Source Projects(Organized by License)

BSD 3-Clause

BSD 2-Clause


Copyright (c) 2013, The GoGo Authors.

Copyright 2010 The Go Authors.

Service-Center Frontend depends on
Open-Source Projects(Organized by License)
 * angular
 * angular-animate
 * angular-aria
 * angular-material-data-table
 * angular-material
 * angular-messages
 * angular-mocks
 * angular-resource
 * angular-route
 * angular-sanitize
 * angular-swagger-ui
 * angular-translate-loader-static-files
 * angular-translate
 * angular-ui-bootstrap
 * angular-ui-router
 * bootstrap-less-only
 * bootstrap-sass-official
 * chart.js
 * Components-font-awesome
 * mmumshad/angular-yamljs
 * jeremyfa/yaml.js

 * Json-formatter

 * Angular-charts.js
 * JS Foundation
 * jQuery

== Required Resources ==
=== Mailing Lists ===
 * (moderated subscriptions)

=== Source Control ===

=== Issue Tracking ===
JIRA Project ServiceComb

=== Initial Committers ===
 * Ning Jiang
 * Qi Zhang
 * Xiang Yin
 * JiMin Wu
 * Bao Liu
 * Mohammad Asif Siddiqui
 * Sukesh A C
 * Yihua Cui
 * Roman Shaposhnik
 * Jean-Baptiste Onofre
 * Timothy Chen

=== Additional Interested Contributors ===
 * Jian Zhang
 * Bing Wang
 * Ven Jiang
 * GeekTJS
 * Li Zhou
 * Haiwei Zhang
 * Yetiea

=== Affiliations ===
 * Huawei: Ning Jiang, Qi Zhang, Xiang Yin, JiMin Wu, Bao Liu, Sukesh A C,
Mohammad Asif Siddiqui, Yihua Cui
 * Stealth: Roman Shaposhnik
 * Talend: Jean-Baptiste Onofré
 * Hyperpilot: Timothy Chen

=== Sponsors ===
 * Roman Shaposhnik[]
Nominated Mentors
 * Roman Shaposhnik[]
 * Jean-Baptiste Onofre []
 * Timothy Chen[]

=== Sponsoring Entity ===
 * We are requesting the Incubator to sponsor this project.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message