Board Report of ServiceComb

2019-05-28 Thread Willem Jiang
Hi Team,

We need to submit the quarterly Board Report, so I just created a draft for it.
Please let me know if I missed something.

## Description:
 - a microservice framework that provides a set of tools and
components to make development and deployment of cloud applications
easier.

## Issues:
 - there are no issues requiring board attention at this time

## Activity:
 - ServiceComb PMC just finished last around release on April
 - ServiceComb PMC created two subproject:
   * kie (for configuration mata data management)
   * fence (for Restful Service Security)

## Health report:
 -  The mails and development activity are as good as usual.

## PMC changes:

 - Currently 16 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Aray Chenchu Sukesh on Wed Oct 17 2018

## Committer base changes:

 - Currently 19 committers.
 - Lei Zhang was added as a committer on Tue Apr 02 2019

## Releases:

 - ServiceComb Java Chassis 1.2.0 was released on Sat Apr 13 2019
 - ServiceComb Java-Chassis 1.2.1 was released on Sun May 19 2019
 - ServiceComb-Pack 0.4.0 was released on Sat Apr 06 2019
 - ServiceComb-Service-Center was released on Sat Apr 06 2019

## Mailing list activity:

 - The dev discussion is good, but we just find the subscribers drop recently.
 NOTE:
 * It looks like some of users were just unsubscribe from dev list
recently, I will dig more about it.
 * The issue mail number is dropped as we did some version clean up in
the first quarter of this year.

 - dev@servicecomb.apache.org:
- 110 subscribers (down -41 in the last 3 months):
- 269 emails sent to list (284 in previous quarter) by 20 people,
divided into 49 topics.

 - iss...@servicecomb.apache.org:
- 8 subscribers (up 0 in the last 3 months):
- 547 emails sent to list (911 in previous quarter) by 14 people,
divided into 190 topics.

## JIRA activity:

 - 120 JIRA tickets created in the last 3 months
 - 115 JIRA tickets closed/resolved in the last 3 months


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


Re: [PROPOSAL]create a new project for servicecomb toolkit

2019-05-28 Thread Bin Ma
Thanks for your suggestions, I will get the scenarios you provided and put
into the roadmap of the toolkit to consider how to implement.


Best Wishes & Regards
---
Mabin



Liubao (A)  于2019年5月28日周二 上午9:52写道:

> Very glad to hear this proposal. I have a draft idea[1] of contract based
> software engineering based on tools.
> And a brief idea[2] of managing contract of all microservices by web.
>
>
> [1] https://bbs.huaweicloud.com/blogs/c998f257673711e9bd5a7ca23e93a891
> [2] https://zhuanlan.zhihu.com/p/64064246
>
>
> -邮件原件-
> 发件人: Bin Ma [mailto:mabin1...@gmail.com]
> 发送时间: 2019年5月27日 11:00
> 收件人: dev@servicecomb.apache.org
> 主题: [PROPOSAL]create a new project for servicecomb toolkit
>
> Hi All,
>
> In the process of supporting users to do micro-service transformation, we
> encountered the following problems:
> 1. For users who integrate multi-vendor applications, because the
> development languages, habits, and frameworks of different vendors are
> different, the entire system data and service standards are inconsistent,
> users are difficult to integrate, and it is difficult to manage and control
> the final delivery quality.
> 2. For users who have evolved from legacy systems to microservices
> architectures, additional learning and understanding of the
> microservices-related framework details is required before the
> microservices project can be designed, built, and developed according to
> the selected microservices framework. For users, Need to be distracted to
> focus on things outside the business.
>
> Based on the above reasons, combined with ServiceComb's service contract
> management capabilities, we have implemented a contract-based microservice
> development toolkit[1] with the goal of rapidly building microservices
> projects based on popular microservices frameworks and programming models,
> and supporting the automatic generation of contracts,code and documentation
> to help users reduce micro-service entry costs, focus on business
> development, and improve legacy system reconfiguration and development
> efficiency during the microservice transformation phase.
>
> The framework and basic function of toolkit has been finished [1]
>
> The function of the toolkit is as follows:
> 1. Code extraction service contract
> In applications developed based on the SpringMVC/POJO/JAX-RS model,
> one-click generation of service contract files conforming to the OpenAPI
> specification.
> 2. Service Contract Generation Micro Service Engineering Enter a service
> contract that conforms to the OpenAPI specification, one-click generation
> of a microservice project with ServiceComb/SpringCloud/Swagger as the base
> microservice framework and SpringMVC/POJO/JAX-RS or SpringBoot as
> programming model .
> 3. Service contract and code consistency check Verify that the actual
> implementation of the application (such as the data and service API) is
> consistent with the agreed service contract description.
> 4. Service contract / code generation document Enter a service contract
> that conforms to the OpenAPI specification, one-click generation of a
> document in html/word/pdf format.
>
> [1] https://github.com/MabinGo/toolkit
>
>
> Best Wishes & Regards
> ---
> Mabin
>