[ANN] New ServiceComb committer: Zhu Chen(陈铸)
Please join me and the rest of the ServiceComb PMC members in welcoming our new ServiceComb committer: Zhu Chen(陈铸). Zhu Chen has been around the ServiceComb almost a year by contributing patches for servicecomb-service-center, servicecomb-mesher, servicecomb-website and discussion techniques issue in the mailing list. Recently he contributed key features such as Syncer and SC-Client to servicecomb-service-center and commit on it frequently. Congratulations to Zhu Chen ! Welcome! The Apache ServiceComb PMC.
Re: [Announce] New committer of ServiceComb
Congratulations ! Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Zheng Feng 于2020年5月14日周四 上午10:27写道： > Congratulations ! > > Willem Jiang 于2020年5月9日周六 下午6:39写道： > > > Hi, > > > > I want to introduce humingcheng (Github ID: humingcheng[1]) as a new > > committer of ServiceComb. He is one of the main author of > > servicecomb-mesher and has been around the ServiceComb almost a year > > by contributing patches for servicecomb-service-center, > > servicecomb-mesher and servicecomb-kie. > > Welcome humingcheng :) > > > > [1]http://github.com/humingcheng > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > >
Re: [VOTE] Release Apache ServiceComb Toolkit version 0.1.0
+1 Binding Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Mohammad Asif Siddiqui 于2019年8月28日周三 下午2:18写道： > +1 Binding > > Checks Done : > - Ran Rat tool for license check > - Checked git tag againt the commit ID > - Hashes and Signature is good > - Ran mvn clean install on source code provided in svn > > Note: We are not releasing the binary in this release? Just the source > code? > > Regards > Asif > > On 2019/08/27 08:33:44, Bin Ma wrote: > > Hi All, > > > > This is a call for Vote to release Apache ServiceComb Toolkit version > 0.1.0 > > > > > > Release Candidate : > > > https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-toolkit/0.1.0/rc-01/ > > > > > > Staging Repository : > > > https://repository.apache.org/content/repositories/orgapacheservicecomb-1403 > > > > > > Release Tag : > > https://github.com/apache/servicecomb-toolkit/releases/tag/0.1.0 > > > > Release CommitID : 88fae512717b632a4f37f0fcce16b75d59143cea > > > > Release Notes : > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12345703 > > > > > > Keys to verify the Release Candidate : > > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS > > > > Voting will start now ( Tuesday, 27nd August, 2019) and will remain open > > for at-least 72 hours, Request all PMC members to give their vote. > > > > [ ] +1 Release this package as 0.1.0 > > [ ] +0 No Opinion > > [ ] -1 Do not release this package because > > > > On the behalf of ServiceComb Team > > > > > > Best Wishes & Regards > > --- > > Mabin > > >
[ANN] New ServiceComb committer:Ma Bin(马彬)
Please join me and the rest of the ServiceComb PMC members in welcoming our new ServiceComb committer: Ma Bin(马彬). Ma Bin has been doing contribution in the ServiceComb community for more than two years, include three parts, a. Contributed ServiceComb code, include code in java-chassis, saga and website, Recently donate his servicecomb-toolkit[2] to servicecomb and commit on it frequently. b. Introduced ServiceComb to our first batch of users and support them to use it. c. Did Speeches to promote the ServiceComb more than 30 times in many different places. Congratulations to Tian Xiaoliang! Welcome! The Apache ServiceComb PMC.
Re: [VOTE]Service mesh proposal
+1 binding Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Willem Jiang 于2019年6月21日周五 下午5:12写道： > FYI， here is the discussion[1] about the proposal. The mesher is > github repo is here[2] > [1] > https://lists.apache.org/thread.html/c74eada900fedec03410e40c9aaafe5416c20996256c1f4ed4ec5e71@%3Cdev.servicecomb.apache.org%3E > [2]https://github.com/go-mesh/mesher > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Fri, Jun 21, 2019 at 4:41 PM Xiaoliang Tian > wrote: > > > > Hi All, > >this is a call for vote to bring service mesh called "mesher" into > > Apache Software Foundation (ASF) as ServiceComb's sub-project. > > > > > > Voting will start now ( Wednesday, 5th June, 2019) and will > > remain open for at-least 72 hours, Request all PMC members to > > give their vote. > > [ ] +1 Accept > > [ ] +0 No Opinion > > [ ] -1 Reject because... >
[VOTE][RESULT] Having a booth and Holding an Apache ServiceComb Meetup as a Co-located Event, in KubeCon & CloudNativeCon Summit China 2019
We are glad to announce that ServiceComb community has approved Having a booth and Holding an Apache ServiceComb Meetup as a Co-located Event, in KubeCon & CloudNativeCon Summit China 2019, with the following results: +1 binding: 5(Willem Jiang, Liubao, Feng Zhen, Yao Haishi, Asif) +1 non-binding: 1(Mabin) Vote Thread : https://www.mail-archive.com/dev@servicecomb.apache.org/msg06159.html Thanks. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb
[VOTE]Have a booth and Holding an Apache ServiceComb Meetup as a Co-located Event, in KubeCon & CloudNativeCon Summit China 2019
Hi All, This is a call for Vote to have a Apache ServiceComb booth and hold an Apache ServiceComb Meetup as a Co-located Event , in KubeCon & CloudNativeCon Summit China 2019, as discussed in the proposal [1]. Voting will start now (Tuesday, 11th June, 2019) and will remain open for at-least 72 hours, Request PMC members and contributors to give their vote. [ ] +1 Accept [ ] +0 No Opinion [ ] -1 Reject because... [1] http://mail-archives.apache.org/mod_mbox/servicecomb-dev/201906.mbox/%3CCAH9eK8QEtrgPF9jqwZO%2BKRk9gEMd_U2DYMe2wAgBC30gD-Sc%2Bg%40mail.gmail.com%3E Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb
Re: Proposal for Holding an Apache ServiceComb Meetup as a Co-located Event in KubeCon & CloudNativeCon Summit China 2019
OK, thanks for reminding me. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Willem Jiang 于2019年6月11日周二 上午6:56写道： > As there are lot of positive response about this proposal, @Zen Lin > do you mind start the vote now? > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Mon, Jun 10, 2019 at 10:08 AM Zen Lin > wrote: > > > > This is a Proposal for holding a Co-Located Event in KubeCon & > > CloudNativeCon Summit China 2019 to help building ServiceComb's > community. > > > > My suggestion is to hold a Meetup named "Apache ServiceComb Meetup Hosted > > by Huawei", to share technologies and user cases of ServiceComb. > > Because the time is tight, I have already talked to Huawei to get free > > resources and sposorship for the meetup. > > > > Details of the plan is listed below, > > - What is the topic focus of the event? > > Topics are focused on Apache Way related topics, user-practices > > /technologies topics of Apache ServiceComb . > > - Who is organising the event? > > PMCs of ServiceComb (incubating) are the organizer > > - When is the event? > > June 24 > > - How many attendees are expected? > > 60~100 > > - How much PMC involvement is there already? > > 3 > > - Which marks are requested? > > Two marks are requested, > > 1. Name of "Apache ServiceComb Meetup " > > 2. "Powered By" Apache logo of Apache ServiceComb > > - Is this for profit or non-profit? (See "Event Profits And Donations")? > > non-profit. > > > > By the way, I also suggest to have a booth about Apache ServiceComb in > > KubeCon & CloudNativeCon Summit China 2019. > > > > Now, I would like to get suggestions from you guys, If it is agreed , I > am > > going to create a vote for it. > > > > > > Best Regards, > > --- > > Zen Lin > > zenlintechnofr...@gmail.com > > Focused on Micro Service and Apache ServiceComb >
Re: [PROPOSAL]a new project mesher for servicecomb
+1, I think Adding Mesher to ServiceComb can complement ServiceComb's multi-language support. But as liubao said, if Mesher added in ServiceComb, could you provide a planing of mesher, including relationship with Istio, which part using istio, and why there are a new proxy named mesher. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Xiaoliang Tian 于2019年6月10日周一 下午6:15写道： > 1. mesher is a part of servicecomb and servicecom is focusing on language > framework, mesher is the reinforcement of servicecomb to make servicecomb > complete。 also mesher can work with istio, but it is not valuable to > servicecomb,. > 2. already support user set swagger file to mesher > 3, will do > > Liubao (A) 于2019年6月10日周一 下午6:05写道： > > > Hi, this seems a good idea. But this is a big topic, I just have > following > > questions to discuss with > > > > 1. What's the relationship between mesher and istio? As I know, istio is > > an excellent framework for service discovery and governance, and is very > > extensible. Can mesher work with istio or act as part of it? > > 2. Will mesher make some gread features like SWAGGER base API metadata > > registration? This metadata can be used for discovery and governance, > which > > is quite like servicecomb did. > > 3. Does mesher have plan to change the configurations to accommandate to > > servicecomb-java-chassis configurations style, to make them work like a > > whole? > > > > -邮件原件- > > 发件人: Xiaoliang Tian [mailto:xiaoliang.t...@gmail.com] > > 发送时间: 2019年6月10日 14:11 > > 收件人: dev@servicecomb.apache.org > > 主题: [PROPOSAL]a new project mesher for servicecomb > > > > Hi All, > > > > Service mesh is a solution for microservice, mesher is a service mesh > > implementation. > > > > if servicecomb introduce mesher, it will get some benifits. > > > > 1. user of servicecomb can choose any language and leverage same service > > center and govenance policy. > > > > 2. user can gain better performance by using java chassis and mesher, > than > > user use service mesh solution only. > > > > the first one is most important reason why service mesh is important to > > service comb > > > > The mesher feature has been finished [1] > > > > there is the list of features: > > 1. service discovery, load balancing, circuit breaker, rate limiting, > most > > of features that java chassis has 2. An admin API to expose runtime > > imformation of mesher 3. support grpc and http1 and http2 4. support > > transparent TLS communication 5. run as a sidecar proxy for a service 6. > a > > sidecar injector to automattically inject mesher into k8s pod > > > > [1] https://github.com/go-mesh/mesher > > > > Regards > > >
Re: Announce of new ServiceComb PMC member
Congratulations. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb wjm wjm 于2019年6月10日周一 下午2:08写道： > Congratulations > > Liubao (A) 于2019年6月10日周一 上午11:26写道： > > > Congratulations to Yao Haishi. > > > > -邮件原件- > > 发件人: Zhang Lei [mailto:zhang_...@boco.com.cn] > > 发送时间: 2019年6月10日 11:05 > > 收件人: dev@servicecomb.apache.org > > 主题: Re: Announce of new ServiceComb PMC member > > > > Congratulations. > > > > Lei Zhang > > > > > 在 2019年6月10日，上午10:53，Willem Jiang 写道： > > > > > > It is very rewarding to see that most of the contributors who became > > > committers continue to stay involved. Therefore, in recognition of > > > their continued contribution, the Apache ServiceComb PMC invited > > > recently a committer to join the PMC, be even more involved and take a > > > greater responsibility in shaping the future of the ServiceComb > > > project. > > > > > > Please join me to welcome Yao Haishi as new Apache ServiceComb PMC > > > member. Many thanks for your past contributions and we look forward to > > > the same commitment in the future. > > > > > > Willem Jiang > > > > > > On behalf of the ServiceComb PMC > > > > >
Proposal for Holding an Apache ServiceComb Meetup as a Co-located Event in KubeCon & CloudNativeCon Summit China 2019
This is a Proposal for holding a Co-Located Event in KubeCon & CloudNativeCon Summit China 2019 to help building ServiceComb's community. My suggestion is to hold a Meetup named "Apache ServiceComb Meetup Hosted by Huawei", to share technologies and user cases of ServiceComb. Because the time is tight, I have already talked to Huawei to get free resources and sposorship for the meetup. Details of the plan is listed below, - What is the topic focus of the event? Topics are focused on Apache Way related topics, user-practices /technologies topics of Apache ServiceComb . - Who is organising the event? PMCs of ServiceComb (incubating) are the organizer - When is the event? June 24 - How many attendees are expected? 60~100 - How much PMC involvement is there already? 3 - Which marks are requested? Two marks are requested, 1. Name of "Apache ServiceComb Meetup " 2. "Powered By" Apache logo of Apache ServiceComb - Is this for profit or non-profit? (See "Event Profits And Donations")? non-profit. By the way, I also suggest to have a booth about Apache ServiceComb in KubeCon & CloudNativeCon Summit China 2019. Now, I would like to get suggestions from you guys, If it is agreed , I am going to create a vote for it. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb
Re: [VOTE] Toolkit donation proposal
+1 (binding) Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Liubao (A) 于2019年6月10日周一 上午9:09写道： > +1 > > -邮件原件- > 发件人: Willem Jiang [mailto:willem.ji...@gmail.com] > 发送时间: 2019年6月6日 19:03 > 收件人: dev > 主题: Re: [VOTE] Toolkit donation proposal > > My +1 (binding), it's great to see that we bring more tools to help user > to build their applications. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Thu, Jun 6, 2019 at 6:57 PM Bin Ma wrote: > > > > Hi All, > > > > This is a call for a Vote to bring Toolkit[1] codebase into the Apache > > Software Foundation (ASF) as ServiceComb's sub-project. > > > > Reference: the mail thread link for the previous discussion[2]. > > > > Voting will start now ( Wednesday, 5th June, 2019) and will remain > > open for at-least 72 hours, Request all PMC members to give their > > vote. > > > > [ ] +1 Accept > > [ ] +0 No Opinion > > [ ] -1 Reject because... > > > > [1] https://github.com/MabinGo/toolkit > > [2] > > https://lists.apache.org/thread.html/bba43e0116160dbdc7d1443c995a2b6fd > > c72f5e4e91f1e5208afc230@%3Cdev.servicecomb.apache.org%3E# > > > > > > Best Wishes & Regards > > --- > > Mabin >
Re: [PROPOSAL]create a new project for servicecomb toolkit
+1 It is quite important to provide a contract tool kit in microservice field. I have one question that, this repo only contains the tools related to contract, or it also contains other tools in future? I mean, this will affact the naming of the repo. Any thoughts? Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb wjm wjm 于2019年5月29日周三 下午9:15写道： > +1 > > Bin Ma 于2019年5月28日周二 下午7:37写道： > > > 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 > > > > > >
[Service-center Syncer] A basic minimal runnable version of Syncer
Hi guys, I have create a PR[1] for adding basic minimal runnable version of Service-center Syncer AS I wrote in the PR message, You can reference to README.md [2] to get what is Service-center Syncer. The current Syner has a P2P network to ensure that different Service-centers can perform peer-to-peer data synchronization when needed. When data needs to be synchronized between Service-centers, Syner establishs a point-to-point channel through GRPC to ensure that the less impact on network load. I am going to make syncer to support the following capabilities in the coming PR, - Support for other service registration and discovery centers, such as SpringCloud Eureka, Istio, etc. - Enhance the reliability of the Syner itself, Syner lifecycle management. Reference to TODO.md[3] to get future plans for Syncer. It is worth noting that both Syncer and Service-center are loosely coupled in the code and there runtime, therefore, Syncer will not affect the current Service-center. The PR is a little big, but it is just a minimal runnable one version, it could be reasonable small in the coming PRs, so please help to review it. I write this mail to get your opinions, if you have any idea, please feel free to let me know in here or on github PR[1]. Thanks very much. [1] https://github.com/apache/servicecomb-service-center/pull/548 [2] https://github.com/zenlint/servicecomb-service-center/blob/master/syncer/README.md [3] https://github.com/zenlint/servicecomb-service-center/blob/master/syncer/TODO.md Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb
Re: [Service-center Syncer] A basic minimal runnable version of Syncer
By the way, please feel free to let me know if there is anyone would like to contribute to Service-center Syncer. That is welcome. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Zen Lin 于2019年5月21日周二 下午1:44写道： > Hi guys, > I have create a PR[1] for adding basic minimal runnable version of > Service-center Syncer > AS I wrote in the PR message, > You can reference to README.md [2] to get what is Service-center Syncer. > > The current Syner has a P2P network to ensure that different > Service-centers can perform peer-to-peer data synchronization when needed. > > When data needs to be synchronized between Service-centers, Syner > establishs a point-to-point channel through GRPC to ensure that the less > impact on network load. > > I am going to make syncer to support the following capabilities in the > coming PR, > >- Support for other service registration and discovery centers, such >as SpringCloud Eureka, Istio, etc. >- Enhance the reliability of the Syner itself, Syner lifecycle >management. > > Reference to TODO.md[3] to get future plans for Syncer. > > It is worth noting that both Syncer and Service-center are loosely coupled > in the code and there runtime, therefore, Syncer will not affect the > current Service-center. > The PR is a little big, but it is just a minimal runnable one version, it > could be reasonable small in the coming PRs, so please help to review it. > I write this mail to get your opinions, if you have any idea, please feel > free to let me know in here or on github PR[1]. > > Thanks very much. > > [1] https://github.com/apache/servicecomb-service-center/pull/548 > [2] > https://github.com/zenlint/servicecomb-service-center/blob/master/syncer/README.md > [3] > https://github.com/zenlint/servicecomb-service-center/blob/master/syncer/TODO.md > > > Best Regards, > --- > Zen Lin > zenlintechnofr...@gmail.com > Focused on Micro Service and Apache ServiceComb >
Re: [VOTE]create a new project servicecomb-fence
+1 Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb yhs0092 于2019年5月21日周二 上午10:13写道： > +1 Good idea! > > > Yours sincerely > > > Yao Haishi > yhs0...@163.com > > > On 5/20/2019 22:15，wjm wjm wrote： > +1 > > Liubao (A) 于2019年5月20日周一 下午8:28写道： > > Thank you for your kindly reminding. This is a call for a vote. > > -邮件原件- > 发件人: Willem Jiang [mailto:willem.ji...@gmail.com] > 发送时间: 2019年5月20日 19:24 > 收件人: dev > 主题: Re: [PROPOSAL]create a new project servicecomb-fence > > @Liubao， > > +1 for the proposal. > > If it's a vote, please add [VOTE] to the subject. > We also need to add the mail thread link for the previous discussion[1]. > > [1] > > https://lists.apache.org/thread.html/ace9961a86ab94c877d4601740d2170b977cda8228c45c79dcba4a97@%3Cdev.servicecomb.apache.org%3E > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > > On Thu, May 16, 2019 at 5:22 PM Liubao (A) wrote: > > Hi all, > > As we discussed before , we will create a new project to provide > authentication and authorization support for java-chassis, and > servicecomb-fence is the name. > > Please feel free to vote or leave any suggestions. > > >
Re: [ANN] New ServiceComb committer: Zhang Lei (张磊）
Congratulations! Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb zhaojun 于2019年4月2日周二 下午12:53写道： > Congratulations~ > > -- > Zhao Jun > Apache Sharding-Sphere & ServiceComb > > > > On Apr 2, 2019, at 11:11 AM, wjm wjm wrote: > > > > Congratulations~ > > > > bismy 于2019年4月2日周二 上午10:46写道： > > > >> Great! > >> > >> > >> > >> > >> -- 原始邮件 -- > >> 发件人: "Sure"; > >> 发送时间: 2019年4月2日(星期二) 上午10:18 > >> 收件人: "dev"; > >> > >> 主题: 回复：[ANN] New ServiceComb committer: Zhang Lei (张磊） > >> > >> > >> > >> Congratulations! > >> > >> > >> > >> > >> -- 原始邮件 -- > >> 发件人: Willem Jiang > >> 发送时间: 2019年4月1日 23:19 > >> 收件人: dev > >> 主题: 回复：[ANN] New ServiceComb committer: Zhang Lei (张磊） > >> > >> > >> > >> Sorry, there is a typo in the first mail. The first sentence should be: > >> > >> Please join me and the rest of the ServiceComb PPMC members in welcoming > >> our > >> new ServiceComb committer: Zhang Lei (张磊). > >> > >> Willem Jiang > >> > >> Twitter: willemjiang > >> Weibo: 姜宁willem > >> > >> On Mon, Apr 1, 2019 at 10:53 PM Willem Jiang > >> wrote: > >>> > >>> Please join me and the rest of the ServiceComb PPMC members in > welcoming > >> our > >>> new ServiceComb committer: Zhang Lei (赵俊). > >>> > >>> Zhang Lei contribute the ServiceComb earlier this year， he is active > >>> contributor on pack project and the mailing list, and we look > >>> forward to many more contributions in the future. > >>> > >>> Congratulations to Zhang Lei! Welcome! > >>> > >>> Willem Jiang > >>> > >>> Twitter: willemjiang > >>> Weibo: 姜宁willem > >
Re: [VOTE]Tracking the Github issue discussions to dev@servicecomb.apache.org
If there is no one knows how the Infra team track the github notification to commits list, I am going to ask the Infra team for the details, and will help to research the feasibility of separation. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Zen Lin 于2019年1月15日周二 上午11:56写道： > Is there anyone knows how Infra group track the github notification to > comm...@servicecomb.apache.org? > If it is using github API, it is work to seperate github issue. > > Best Regards, > --- > Zen Lin > zenlintechnofr...@gmail.com > Focused on Micro Service and Apache ServiceComb > > > Willem Jiang 于2019年1月15日周二 上午11:44写道： > >> We cannot just redirect the question to the Infra team without doing >> the research first. >> My suggestion is we need to do some research to figure out how to >> separate the github issue notification from the github notification >> stream. >> Then we can give the Infra team instructions to do the work with their >> admin right. >> If we cannot get there, we could consider to disable the github issue >> function to let user use mail to ask questions directly. >> >> Willem Jiang >> >> Twitter: willemjiang >> Weibo: 姜宁willem >> >> On Tue, Jan 15, 2019 at 9:54 AM Zen Lin >> wrote: >> > >> > Yeah, >> > If we track the github issue to dev mail, we can watch the issue >> > contents in the dev mailing list. >> > If you want your reply can posted to the github issue, you can >> > reply the mail sent by github, in that way, the reply can be posted >> > on issue and also be sent to the dev mailing list. >> > >> > Anyway, as Willem said, we now have tracked the github >> > notification to comm...@servicecomb.apache.org, we just need >> > to seperate them from the github notification. >> > >> > Hi Willem, >> > As I known, this will be implemented by Apache Infra group. >> > What about to create a vote for this, and then I will create an >> > issue to Apache Infra, >> > or just create a mail to copy to infrastructure-...@apache.org >> > >> > Best Regards, >> > --- >> > Zen Lin >> > zenlintechnofr...@gmail.com >> > Focused on Micro Service and Apache ServiceComb >> > >> > >> > Willem Jiang 于2019年1月15日周二 上午9:27写道： >> > >> > > I don't think we can bridge the dev mail to the github issue, but it >> > > makes sense that to send the notification or the github issue to the >> > > dev mailing list. >> > > Now we need to figure out if we can seperate the github notification >> > > by checking if it comes from github issues. >> > > >> > > Willem Jiang >> > > >> > > Twitter: willemjiang >> > > Weibo: 姜宁willem >> > > >> > > On Mon, Jan 14, 2019 at 10:00 PM Zheng Feng >> wrote: >> > > > >> > > > I wonder if it can only watch the github issues by using the dev >> mailing >> > > > list or we can reply the thread and it could be posted to the github >> > > issue >> > > > automatically ? >> > > > >> > > > Zen Lin 于2019年1月14日周一 下午8:38写道： >> > > > >> > > > > How about to create a new proposal discussion for split github >> issue >> > > track >> > > > > from commits mailing list to dev mailing list? >> > > > > I think discussion in github issue is quite different from >> commits, >> > > they >> > > > > are similar to the contents in the dev list. >> > > > > >> > > > > Best Regards, >> > > > > --- >> > > > > Zen Lin >> > > > > zenlintechnofr...@gmail.com >> > > > > Focused on Micro Service and Apache ServiceComb >> > > > > >> > > > > >> > > > > Willem Jiang 于2019年1月14日周一 下午8:20写道： >> > > > > >> > > > > > Actually we already had the vote[1] of moving the github >> > > notifications >> > > > > > into the commits mailing list to avoiding flooding the dev >> mailing >> > > > > > list . Here is the discussion of it[2]. Now the user questions >> in the >> > > > > > github issue are tracked in the commits mailing list. >> > > > > > >> > > > > > [1] >> > > > >
Re: [VOTE]Tracking the Github issue discussions to dev@servicecomb.apache.org
Is there anyone knows how Infra group track the github notification to comm...@servicecomb.apache.org? If it is using github API, it is work to seperate github issue. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Willem Jiang 于2019年1月15日周二 上午11:44写道： > We cannot just redirect the question to the Infra team without doing > the research first. > My suggestion is we need to do some research to figure out how to > separate the github issue notification from the github notification > stream. > Then we can give the Infra team instructions to do the work with their > admin right. > If we cannot get there, we could consider to disable the github issue > function to let user use mail to ask questions directly. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Tue, Jan 15, 2019 at 9:54 AM Zen Lin > wrote: > > > > Yeah, > > If we track the github issue to dev mail, we can watch the issue > > contents in the dev mailing list. > > If you want your reply can posted to the github issue, you can > > reply the mail sent by github, in that way, the reply can be posted > > on issue and also be sent to the dev mailing list. > > > > Anyway, as Willem said, we now have tracked the github > > notification to comm...@servicecomb.apache.org, we just need > > to seperate them from the github notification. > > > > Hi Willem, > > As I known, this will be implemented by Apache Infra group. > > What about to create a vote for this, and then I will create an > > issue to Apache Infra, > > or just create a mail to copy to infrastructure-...@apache.org > > > > Best Regards, > > --- > > Zen Lin > > zenlintechnofr...@gmail.com > > Focused on Micro Service and Apache ServiceComb > > > > > > Willem Jiang 于2019年1月15日周二 上午9:27写道： > > > > > I don't think we can bridge the dev mail to the github issue, but it > > > makes sense that to send the notification or the github issue to the > > > dev mailing list. > > > Now we need to figure out if we can seperate the github notification > > > by checking if it comes from github issues. > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Mon, Jan 14, 2019 at 10:00 PM Zheng Feng wrote: > > > > > > > > I wonder if it can only watch the github issues by using the dev > mailing > > > > list or we can reply the thread and it could be posted to the github > > > issue > > > > automatically ? > > > > > > > > Zen Lin 于2019年1月14日周一 下午8:38写道： > > > > > > > > > How about to create a new proposal discussion for split github > issue > > > track > > > > > from commits mailing list to dev mailing list? > > > > > I think discussion in github issue is quite different from commits, > > > they > > > > > are similar to the contents in the dev list. > > > > > > > > > > Best Regards, > > > > > --- > > > > > Zen Lin > > > > > zenlintechnofr...@gmail.com > > > > > Focused on Micro Service and Apache ServiceComb > > > > > > > > > > > > > > > Willem Jiang 于2019年1月14日周一 下午8:20写道： > > > > > > > > > > > Actually we already had the vote[1] of moving the github > > > notifications > > > > > > into the commits mailing list to avoiding flooding the dev > mailing > > > > > > list . Here is the discussion of it[2]. Now the user questions > in the > > > > > > github issue are tracked in the commits mailing list. > > > > > > > > > > > > [1] > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/833356d5dd8901f5d51e94b12d48f9dcb816d29f50b38d46915f8e9e@%3Cdev.servicecomb.apache.org%3E > > > > > > [2] > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/95f538f676326bd2cb1a06cf278c4076352b987bfbabad6c6ae247bc@%3Cdev.servicecomb.apache.org%3E > > > > > > > > > > > > > > > > > > Willem Jiang > > > > > > > > > > > > Twitter: willemjiang > > > > > > Weibo: 姜宁willem > > > > > > > > > > > > On Mon, Jan 14, 2019 at 8:05 PM Willem Jiang < > willem.ji...@gmail.com > &g
Re: [VOTE]Tracking the Github issue discussions to dev@servicecomb.apache.org
Yeah, If we track the github issue to dev mail, we can watch the issue contents in the dev mailing list. If you want your reply can posted to the github issue, you can reply the mail sent by github, in that way, the reply can be posted on issue and also be sent to the dev mailing list. Anyway, as Willem said, we now have tracked the github notification to comm...@servicecomb.apache.org, we just need to seperate them from the github notification. Hi Willem, As I known, this will be implemented by Apache Infra group. What about to create a vote for this, and then I will create an issue to Apache Infra, or just create a mail to copy to infrastructure-...@apache.org Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Willem Jiang 于2019年1月15日周二 上午9:27写道： > I don't think we can bridge the dev mail to the github issue, but it > makes sense that to send the notification or the github issue to the > dev mailing list. > Now we need to figure out if we can seperate the github notification > by checking if it comes from github issues. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Mon, Jan 14, 2019 at 10:00 PM Zheng Feng wrote: > > > > I wonder if it can only watch the github issues by using the dev mailing > > list or we can reply the thread and it could be posted to the github > issue > > automatically ? > > > > Zen Lin 于2019年1月14日周一 下午8:38写道： > > > > > How about to create a new proposal discussion for split github issue > track > > > from commits mailing list to dev mailing list? > > > I think discussion in github issue is quite different from commits, > they > > > are similar to the contents in the dev list. > > > > > > Best Regards, > > > --- > > > Zen Lin > > > zenlintechnofr...@gmail.com > > > Focused on Micro Service and Apache ServiceComb > > > > > > > > > Willem Jiang 于2019年1月14日周一 下午8:20写道： > > > > > > > Actually we already had the vote[1] of moving the github > notifications > > > > into the commits mailing list to avoiding flooding the dev mailing > > > > list . Here is the discussion of it[2]. Now the user questions in the > > > > github issue are tracked in the commits mailing list. > > > > > > > > [1] > > > > > > > > https://lists.apache.org/thread.html/833356d5dd8901f5d51e94b12d48f9dcb816d29f50b38d46915f8e9e@%3Cdev.servicecomb.apache.org%3E > > > > [2] > > > > > > > > https://lists.apache.org/thread.html/95f538f676326bd2cb1a06cf278c4076352b987bfbabad6c6ae247bc@%3Cdev.servicecomb.apache.org%3E > > > > > > > > > > > > Willem Jiang > > > > > > > > Twitter: willemjiang > > > > Weibo: 姜宁willem > > > > > > > > On Mon, Jan 14, 2019 at 8:05 PM Willem Jiang > > > > > wrote: > > > > > > > > > > First we need to know the common process of building the > consensus[1] > > > in > > > > Apache. > > > > > Normally if we have some proposal, we discuss it first to build a > > > > > common consensus, then we start the vote[2]. > > > > > > > > > > So let's discuss about this proposal first. > > > > > > > > > > [1]https://community.apache.org/committers/consensusBuilding.html > > > > > [2]https://community.apache.org/committers/voting.html > > > > > > > > > > > > > > > Willem Jiang > > > > > > > > > > Twitter: willemjiang > > > > > Weibo: 姜宁willem > > > > > > > > > > On Mon, Jan 14, 2019 at 7:03 PM Zen Lin < > zenlintechnofr...@gmail.com> > > > > wrote: > > > > > > > > > > > > Hi Community, > > > > > > > > > > > > Although we have proposed to use JIRA as many times as possible, > > > there > > > > are > > > > > > still many people using our Github issue. > > > > > > Many users have been hoping to use the Github issue. > > > > > > > > > > > > So I propose to track the contents of the Github issue to our > dev > > > > mail so > > > > > > that the community can better coordinate and discuss, so as not > to > > > > miss the > > > > > > management of the Github issue. > > > > > > This is a call for vote of tracking Github issue to > > > > > > dev@servicecomb.apache.org mail list. > > > > > > > > > > > > Voting is starting now ( 14th Jan, 2018) and will remain open for > > > next > > > > 72 > > > > > > hours. > > > > > > > > > > > > [ ] +1 Track Github issue discussions to mail list > > > > > > dev@servicecomb.apache.org > > > > > > [ ] +0 No Opinion > > > > > > [ ] -1 Do not track Github issue discussions to the mail list > > > > > > dev@servicecomb.apache.org > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > --- > > > > > > Zen Lin > > > > > > zenlintechnofr...@gmail.com > > > > > > Focused on Micro Service and Apache ServiceComb > > > > > > > >
Re: [VOTE]Tracking the Github issue discussions to dev@servicecomb.apache.org
How about to create a new proposal discussion for split github issue track from commits mailing list to dev mailing list? I think discussion in github issue is quite different from commits, they are similar to the contents in the dev list. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Willem Jiang 于2019年1月14日周一 下午8:20写道： > Actually we already had the vote[1] of moving the github notifications > into the commits mailing list to avoiding flooding the dev mailing > list . Here is the discussion of it[2]. Now the user questions in the > github issue are tracked in the commits mailing list. > > [1] > https://lists.apache.org/thread.html/833356d5dd8901f5d51e94b12d48f9dcb816d29f50b38d46915f8e9e@%3Cdev.servicecomb.apache.org%3E > [2] > https://lists.apache.org/thread.html/95f538f676326bd2cb1a06cf278c4076352b987bfbabad6c6ae247bc@%3Cdev.servicecomb.apache.org%3E > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Mon, Jan 14, 2019 at 8:05 PM Willem Jiang > wrote: > > > > First we need to know the common process of building the consensus[1] in > Apache. > > Normally if we have some proposal, we discuss it first to build a > > common consensus, then we start the vote[2]. > > > > So let's discuss about this proposal first. > > > > [1]https://community.apache.org/committers/consensusBuilding.html > > [2]https://community.apache.org/committers/voting.html > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Mon, Jan 14, 2019 at 7:03 PM Zen Lin > wrote: > > > > > > Hi Community, > > > > > > Although we have proposed to use JIRA as many times as possible, there > are > > > still many people using our Github issue. > > > Many users have been hoping to use the Github issue. > > > > > > So I propose to track the contents of the Github issue to our dev > mail so > > > that the community can better coordinate and discuss, so as not to > miss the > > > management of the Github issue. > > > This is a call for vote of tracking Github issue to > > > dev@servicecomb.apache.org mail list. > > > > > > Voting is starting now ( 14th Jan, 2018) and will remain open for next > 72 > > > hours. > > > > > > [ ] +1 Track Github issue discussions to mail list > > > dev@servicecomb.apache.org > > > [ ] +0 No Opinion > > > [ ] -1 Do not track Github issue discussions to the mail list > > > dev@servicecomb.apache.org > > > > > > > > > Best Regards, > > > --- > > > Zen Lin > > > zenlintechnofr...@gmail.com > > > Focused on Micro Service and Apache ServiceComb >
[VOTE]Tracking the Github issue discussions to dev@servicecomb.apache.org
Hi Community, Although we have proposed to use JIRA as many times as possible, there are still many people using our Github issue. Many users have been hoping to use the Github issue. So I propose to track the contents of the Github issue to our dev mail so that the community can better coordinate and discuss, so as not to miss the management of the Github issue. This is a call for vote of tracking Github issue to dev@servicecomb.apache.org mail list. Voting is starting now ( 14th Jan, 2018) and will remain open for next 72 hours. [ ] +1 Track Github issue discussions to mail list dev@servicecomb.apache.org [ ] +0 No Opinion [ ] -1 Do not track Github issue discussions to the mail list dev@servicecomb.apache.org Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb
Re: Board Report of ServiceComb
+1 Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb wjm wjm 于2018年12月5日周三 下午11:07写道： > +1 > > Willem Jiang 于2018年12月5日周三 下午6:06写道： > > > Hi Asif, > > > > Thanks for the suggestion. I will updated the board report with the > > new version of introduction. > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Tue, Dec 4, 2018 at 2:04 PM Mohammad Asif Siddiqui > > wrote: > > > > > > +1 > > > > > > Suggestion : I guess we can re-visit and update the description of > > ServiceComb.( ServiceComb is a full stack microservice framework which > > provides a set of SDK's, Service Registry and Transaction Management > > Services for rapid development of Cloud native applications.) > > > > > > Regards > > > Asif > > > > > > On 2018/12/03 15:18:41, Jean-Baptiste Onofré wrote: > > > > +1 > > > > > > > > it looks good to me. > > > > > > > > Thanks, > > > > Regards > > > > JB > > > > > > > > On 03/12/2018 09:44, Willem Jiang wrote: > > > > > Hi Team, > > > > > > > > > > Here is the draft of the board report this month (We need to submit > > it > > > > > to the board before 12 Dec). Please let me know if any thing is > > > > > missing or you have any questions about it. > > > > > > > > > > ## 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 did the first around graduate release this > month. > > > > > - We began to hold the online community meeting[1] to discuss > about > > > > > the roadmap of the project. > > > > > - ServiceComb saga will be rename to pack[2] to provide the TCC > and > > > > > Saga supports in the pack architecture > > > > > > > > > > [1] > > > https://cwiki.apache.org/confluence/display/SERVICECOMB/Community+Meeting > > > > > [2] > > > https://lists.apache.org/thread.html/b80d907cdc4585cea32c3b0258a1b6338bb3ab95118593a928bcfbd6@%3Cdev.servicecomb.apache.org%3E > > > > > > > > > > ## Health report: > > > > > - The mails and commits activity are as good as usual. > > > > > > > > > > ## PMC changes: > > > > > > > > > > - Currently 16 PMC members. > > > > > - No new PMC members added in the last 3 months > > > > > > > > > > ## Committer base changes: > > > > > > > > > > - Currently 18 committers. > > > > > - New committers: > > > > > - Haishi Yao was added as a committer on Tue Nov 13 2018 > > > > > - Jun Zhao was added as a committer on Tue Nov 13 2018 > > > > > > > > > > ## Releases: > > > > > > > > > > - ServiceComb Saga 0.2.1 on Nov 24, 2018 > > > > > - ServiceComb Java-Chassis 1.1.0 on Dec 1, 2018 > > > > > - ServiceComb Service-Center 1.1.0 on Dec 1, 2018 > > > > > > > > > > ## Mailing list activity: > > > > > > > > > > - dev@servicecomb.apache.org: > > > > > - This month, there were 197 emails sent by 25 people, divided > > > > > into 27 topics > > > > > - 130 subscribers (up 19 in the last 3 months): > > > > > - 485 emails sent to list (535 in previous quarter) > > > > > > > > > > - iss...@servicecomb.apache.org: > > > > > - 8 subscribers (up 0 in the last 3 months): > > > > > - 2145 emails sent to list (2737 in previous quarter) > > > > > > > > > > > > > > > ## JIRA activity: > > > > > > > > > > - 176 JIRA tickets created in the last 3 months > > > > > - 179 JIRA tickets closed/resolved in the last 3 months > > > > > > > > > > > > > > > > > > > > Willem Jiang > > > > > > > > > > Twitter: willemjiang > > > > > Weibo: 姜宁willem > > > > > > > > > > > > > -- > > > > Jean-Baptiste Onofré > > > > jbono...@apache.org > > > > http://blog.nanthrax.net > > > > Talend - http://www.talend.com > > > > > > >
Re: ServiceComb Community Meeting
Hi Once you done the necessary content, I will write an article to anounce it to let more people know. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Mohammad Asif Siddiqui 于2018年11月22日周四 下午2:58写道： > Here is the first initial page I created in the wiki [1], please review > and update as required and also people who don't have permissions to edit > or comment on the page can request Willem to add the permission. > > [1] > https://cwiki.apache.org/confluence/display/SERVICECOMB/Community+Meeting > > > Regards > Asif > > On 2018/11/22 06:44:26, Willem Jiang wrote: > > How about we start a page in the wiki page list the topics we want to > talk? > > If there are some user or other people want to join we could change > > the time if we need. > > > > I just had a face 2 face talk with some guys from JingDong yesterday. > > We are planning to hold the weekly meeting for the development of the > > ServiceComb Saga and the release plan and git repo name change > > recently. I think we can start from these topics to see if it goes > > well. > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Thu, Nov 22, 2018 at 2:17 PM Mohammad Asif Siddiqui > > wrote: > > > > > > Hello All, > > > > > > I guess everyone is okay with this idea of having community meeting > bi-weekly for all ServiceComb projects so let's have our first community > meeting in the first week of December after 1.1.0 Release. > > > > > > Any suggestions for the Day and Time as lot of people will be joining > the meeting from different time zone and also any volunteers to organize > this meeting? > > > > > > Regards > > > Asif > > > > > > On 2018/11/20 13:59:52, Willem Jiang wrote: > > > > Yeah, we can use the Apache wiki page, it's easy for everyone to > > > > access and share the ideas. > > > > Current we don't open for comment and edit for avoid the spam. We can > > > > give the edit right the people who interesting about it. > > > > > > > > Willem Jiang > > > > > > > > Twitter: willemjiang > > > > Weibo: 姜宁willem > > > > > > > > On Tue, Nov 20, 2018 at 6:57 PM Mohammad Asif Siddiqui > > > > wrote: > > > > > > > > > > Hi All, > > > > > > > > > > It's a good idea to hold a bi-weekly meeting either in Zoom[1] or > Skype where all the people involved in the community can come together and > project owners can give a short update on what's going on in the project > what is the future plan and discuss any issues or help needed from the > community. > > > > > > > > > > Whereas agenda is concerned, we can put this in the Community > engagement section in our ServiceComb website which will be accessible from > everywhere and people not having the permission to edit the agenda can add > the comments on that page, rather we can also use cwiki[2] for this. > > > > > > > > > > This can be an open meeting where anyone can attend these meeting > and in my opinion at-least one owner of each project should attend the > meeting to give an update on the project stats. After meeting MOM can be > published on our website. This can give a clear transparency to our > ServiceComb community and more people will be willing to join and > contribute to our community. > > > > > > > > > > [1] https://zoom.us/ > > > > > [2] https://cwiki.apache.org/confluence/display/ServiceComb > > > > > > > > > > Just my 2 cents > > > > > > > > > > Regards > > > > > Asif > > > > > On 2018/11/20 10:16:21, Zheng Feng wrote: > > > > > > yeah. exactly but I think if the google document could be access > in China > > > > > > without the OpenVPN ? > > > > > > > > > > > > Willem Jiang 于2018年11月20日周二 上午10:11写道： > > > > > > > > > > > > > Yeah, I agree with you. I think we can setup the agenda in > the Google > > > > > > > document just like the MicroProfile LRA Hangout Agenda[1] to > talk > > > > > > > about the detail development plan of ServiceComb with the > community. > > > > > > > > > > > > > > [1] > > > > > > > > https://docs.google.com/document/d/1HBPiXpsXcQp9T8Je
Re: [VOTE] Release Apache ServiceComb Saga version 0.2.1
+1 binding. Check release notes. Check Notice/License exists. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb wjm wjm 于2018年11月26日周一 下午4:20写道： > +1 binding > > > Checks Done: > - release notes > - binaries and maven repos > > DeanLee <82529...@qq.com> 于2018年11月24日周六 下午3:43写道： > > > +1 non binding > > > > > > > > > > Checks List: > > > > - Signatures and hashes is ok > > > > - Able to run saga-spring-cloud-demo demo with the instruction from > README > > > > - NOTICE/LICENSE is present > > > > > > > > > > Regards > > > > Dean Lee > > > > -- 原始邮件 -- > > 发件人: "Mohammad Asif Siddiqui"; > > 发送时间: 2018年11月24日(星期六) 中午1:06 > > 收件人: "dev"; > > > > 主题: Re: [VOTE] Release Apache ServiceComb Saga version 0.2.1 > > > > > > > > Hi All, > > > > Thanks All for verifying and voting for this release, this vote is closed > > now and we will declare the results soon. > > > > Regards > > Asif > > > > On 2018/11/20 15:35:59, Mohammad Asif Siddiqui > > wrote: > > > Hi All, > > > > > > This is a call for Vote to release Apache ServiceComb Saga version > > 0.2.1 > > > > > > Release Notes : > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12344453 > > > > > > > > Release Candidate : > > > https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-saga/0.2.1/rc-01/ > > > > > > Staging Repository : > > > https://repository.apache.org/content/repositories/orgapacheservicecomb-1346/ > > > > > > Release Tag : > > https://github.com/apache/servicecomb-saga/releases/tag/0.2.1 > > > > > > Release CommitID : 1484592d6fc84a33ffb7510969437ba448277e82 > > > > > > Keys to verify the Release Candidate : > > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS > > > > > > Voting will start now ( Tuesday, 20th November, 2018) and will remain > > open for at-least 72 hours, Request all PMC members to give their vote. > > > > > > [ ] +1 Release this package as 0.2.1 > > > [ ] +0 No Opinion > > > [ ] -1 Do not release this package because > > > > > > On the behalf of ServiceComb Team > > > Mohammad Asif Siddiqui > > > >
Re: [VOTE] Release Apache ServiceComb Service-Center version 1.1.0 [RC-02]
+1 binding. Check making release kit from source. Notice/License exists. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Willem Jiang 于2018年11月26日周一 下午4:41写道： > +1 binding. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Sat, Nov 24, 2018 at 12:41 AM Mohammad Asif Siddiqui > wrote: > > > > Hi All, > > > > This is a call for a Vote to release Apache ServiceComb Service-Center > version 1.1.0 [RC-02] > > > > Release Notes : > https://github.com/apache/servicecomb-service-center/blob/master/docs/release/releaseNotes-1.1.0.md > > > > Release Candidate : > https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-service-center/1.1.0/rc-02/ > > > > Release Tag : > https://github.com/apache/servicecomb-service-center/releases/tag/1.1.0 > > > > Release CommitID : 49428294a99f2a475203a7ceb04ce8d5754feb77 > > > > Keys to verify the Release Candidate : > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS > > > > Guide to build the release from source : > https://github.com/apache/servicecomb-service-center/tree/master/scripts/release > > > > Voting will start now ( Friday, 23rd November, 2018) and will remain > open for at-least 72 hours, Request all PMC members to give their vote. > > > > [ ] +1 Release this package as 1.1.0 > > [ ] +0 No Opinion > > [ ] -1 Do not release this package because > > > > On the behalf of ServiceComb Team > > Mohammad Asif Siddiqui >
Re: ServiceComb Community Meeting
Hi Willem, That is exactly what I mean. I am not sure is there any other place we can access without OpenVPN just as Zheng said? Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Zheng Feng 于2018年11月20日周二 下午6:23写道： > yeah. exactly but I think if the google document could be access in China > without the OpenVPN ? > > Willem Jiang 于2018年11月20日周二 上午10:11写道： > > > Yeah, I agree with you. I think we can setup the agenda in the Google > > document just like the MicroProfile LRA Hangout Agenda[1] to talk > > about the detail development plan of ServiceComb with the community. > > > > [1] > > > https://docs.google.com/document/d/1HBPiXpsXcQp9T8JeoT-IDs-EblZX1SxuTV5qjUPzwrM/edit?ouid=101568241178421126357=docs_home=true > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > On Tue, Nov 20, 2018 at 3:43 PM Zheng Feng wrote: > > > > > > Thanks Zen Lin, I think you might be missing the link for the itcast ? > > > > > > I agree it is very important to let the more committers to know what we > > are > > > doing and what we will do. So the monthly online meeting sounds helpful > > and > > > we should prepare the agenda before the meeting and to know what the > > > community is concerned. Maybe we could share this agenda online and > > anyone > > > could be able to add the items to discuss. > > > > > > Thanks, > > > Zheng Feng > > > > > > Zen Lin 于2018年11月20日周二 上午7:16写道： > > > > > > > I am preparing a Apache ServiceComb Meetup about on Dec 23th. > > > > The Meetup will be held with itcast [1]. > > > > We are just doing a discussion of draft plan last week. > > > > Maybe we can have a 1 hour conference to meet F2F with our committers > > to > > > > discuss about how to develop the community and carrying out the > > Roadmap. > > > > > > > > Besides, I think we can have a online meetup with committers each > > month, > > > > anyone who are concerning about Apache ServiceComb can join the > meetup > > to > > > > discuss the Roadmap. Thus we can always update the Roadmap. We have > no > > need > > > > to care how many committers will join the meetup, but just let us > start > > > > it. I believe that as long as we keep doing it, more and more > > developers > > > > will join in. > > > > > > > > Anyway, What I concern is that many developers want to know what can > I > > do > > > > and what will the community want the next, that is what we called > > roadmap. > > > > > > > > Any thoughts? > > > > > > > > Best Regards, > > > > --- > > > > Zen Lin > > > > zenlintechnofr...@gmail.com > > > > Focused on Micro Service and Apache ServiceComb > > > > > > > > > > > > cherrylzhao 于2018年11月20日周二 上午11:38写道： > > > > > > > > > If we can post the time, face to face meeting(skype) is better. > > > > > Also we can send the meeting summary to the mailing list. > > > > > > > > > > > On Nov 20, 2018, at 10:07 AM, Willem Jiang < > willem.ji...@gmail.com > > > > > > > > wrote: > > > > > > > > > > > > Hi, > > > > > > > > > > > > I had a talk with Asif recently about the community meeting > > recently. > > > > > > I think it's a great idea which could help us get touch with the > > > > > > community contributor and help them to know better about our > > project > > > > > > development plan. In this way we could help more developer or > user > > to > > > > > > know better about our code and we can know better about the user > > case > > > > > > at the same time. > > > > > > > > > > > > It could be a simple meeting in the Gitter (we just need to post > > the > > > > > > time to let everyone know we are online for it) or even face to > > face > > > > > > meeting for the meetup. > > > > > > > > > > > > Any thoughts? I'm really appreciate the effort that everyone put > on > > > > > > the community. > > > > > > > > > > > > > > > > > > Willem Jiang > > > > > > > > > > > > Twitter: willemjiang > > > > > > Weibo: 姜宁willem > > > > > > > > > > > > > > > > >
Re: ServiceComb Community Meeting
Hi willem, Yeah, I will send the draft of course. But I don't think we are off the topic, we are just talking about shall we holding a online meetup of Apache ServiceComb. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Willem Jiang 于2018年11月20日周二 下午4:04写道： > It may off the topic. > Before the vote, it's always good to hear some inputs from the community. > So please send out the draft before calling the vote. > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Tue, Nov 20, 2018 at 3:48 PM Zen Lin > wrote: > > > > Hi Zheng, > > Link of itcast http://www.itcast.cn/ <http://www.itcast.cn/> . > > I am just discussing with them, once we have a carried out draft plan, I > > will come here to call a vote for the meetup. > > > > > > Best Regards, > > --- > > Zen Lin > > zenlintechnofr...@gmail.com > > Focused on Micro Service and Apache ServiceComb > > > > > > Zheng Feng 于2018年11月20日周二 下午3:43写道： > > > > > Thanks Zen Lin, I think you might be missing the link for the itcast ? > > > > > > I agree it is very important to let the more committers to know what > we are > > > doing and what we will do. So the monthly online meeting sounds > helpful and > > > we should prepare the agenda before the meeting and to know what the > > > community is concerned. Maybe we could share this agenda online and > anyone > > > could be able to add the items to discuss. > > > > > > Thanks, > > > Zheng Feng > > > > > > Zen Lin 于2018年11月20日周二 上午7:16写道： > > > > > > > I am preparing a Apache ServiceComb Meetup about on Dec 23th. > > > > The Meetup will be held with itcast [1]. > > > > We are just doing a discussion of draft plan last week. > > > > Maybe we can have a 1 hour conference to meet F2F with our > committers to > > > > discuss about how to develop the community and carrying out the > Roadmap. > > > > > > > > Besides, I think we can have a online meetup with committers each > month, > > > > anyone who are concerning about Apache ServiceComb can join the > meetup to > > > > discuss the Roadmap. Thus we can always update the Roadmap. We have > no > > > need > > > > to care how many committers will join the meetup, but just let us > start > > > > it. I believe that as long as we keep doing it, more and more > developers > > > > will join in. > > > > > > > > Anyway, What I concern is that many developers want to know what can > I do > > > > and what will the community want the next, that is what we called > > > roadmap. > > > > > > > > Any thoughts? > > > > > > > > Best Regards, > > > > --- > > > > Zen Lin > > > > zenlintechnofr...@gmail.com > > > > Focused on Micro Service and Apache ServiceComb > > > > > > > > > > > > cherrylzhao 于2018年11月20日周二 上午11:38写道： > > > > > > > > > If we can post the time, face to face meeting(skype) is better. > > > > > Also we can send the meeting summary to the mailing list. > > > > > > > > > > > On Nov 20, 2018, at 10:07 AM, Willem Jiang < > willem.ji...@gmail.com> > > > > > wrote: > > > > > > > > > > > > Hi, > > > > > > > > > > > > I had a talk with Asif recently about the community meeting > recently. > > > > > > I think it's a great idea which could help us get touch with the > > > > > > community contributor and help them to know better about our > project > > > > > > development plan. In this way we could help more developer or > user to > > > > > > know better about our code and we can know better about the user > case > > > > > > at the same time. > > > > > > > > > > > > It could be a simple meeting in the Gitter (we just need to post > the > > > > > > time to let everyone know we are online for it) or even face to > face > > > > > > meeting for the meetup. > > > > > > > > > > > > Any thoughts? I'm really appreciate the effort that everyone put > on > > > > > > the community. > > > > > > > > > > > > > > > > > > Willem Jiang > > > > > > > > > > > > Twitter: willemjiang > > > > > > Weibo: 姜宁willem > > > > > > > > > > > > > > > > > >
Re: ServiceComb Community Meeting
I am preparing a Apache ServiceComb Meetup about on Dec 23th. The Meetup will be held with itcast [1]. We are just doing a discussion of draft plan last week. Maybe we can have a 1 hour conference to meet F2F with our committers to discuss about how to develop the community and carrying out the Roadmap. Besides, I think we can have a online meetup with committers each month, anyone who are concerning about Apache ServiceComb can join the meetup to discuss the Roadmap. Thus we can always update the Roadmap. We have no need to care how many committers will join the meetup, but just let us start it. I believe that as long as we keep doing it, more and more developers will join in. Anyway, What I concern is that many developers want to know what can I do and what will the community want the next, that is what we called roadmap. Any thoughts? Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb cherrylzhao 于2018年11月20日周二 上午11:38写道： > If we can post the time, face to face meeting(skype) is better. > Also we can send the meeting summary to the mailing list. > > > On Nov 20, 2018, at 10:07 AM, Willem Jiang > wrote: > > > > Hi, > > > > I had a talk with Asif recently about the community meeting recently. > > I think it's a great idea which could help us get touch with the > > community contributor and help them to know better about our project > > development plan. In this way we could help more developer or user to > > know better about our code and we can know better about the user case > > at the same time. > > > > It could be a simple meeting in the Gitter (we just need to post the > > time to let everyone know we are online for it) or even face to face > > meeting for the meetup. > > > > Any thoughts? I'm really appreciate the effort that everyone put on > > the community. > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > >
Re: [ANN] New ServiceComb committer: Zhao Jun (赵俊)
Congratulations! Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Sure 于2018年11月13日周二 下午5:07写道： > Congratulations ! > > > -- 原始邮件 -- > 发件人: wjm wjm > 发送时间: 2018年11月13日 17:06 > 收件人: dev > 主题: 回复：[ANN] New ServiceComb committer: Zhao Jun (赵俊)
Re: [ANN] New ServiceComb committer: Yao Haishi (姚海石)
Congratulations ! Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Sure 于2018年11月13日周二 下午5:07写道： > Congratulations ! > > > > > -- 原始邮件 -- > 发件人: wjm wjm > 发送时间: 2018年11月13日 17:06 > 收件人: dev > 主题: 回复：[ANN] New ServiceComb committer: Yao Haishi (姚海石) > > > > Congratulation > > Mohammad Asif Siddiqui 于2018年11月13日周二 下午4:19写道： > > > Congratulations Yao Haishi > > > > Regards > > Asif > > > > On 2018/11/13 02:46:53, Willem Jiang wrote: > > > Please join me and the rest of the ServiceComb PPMC members in > welcoming > > our > > > new ServiceComb committer: Yao Haishi (姚海石). > > > > > > Yao Haishi contribute the ServiceComb more than a year, he is active > > > contributor on java-chassis, doc and the mailing list, and we look > > > forward to many more > > > contributions in the future. > > > > > > Congratulations to Yao Haishi ! Welcome! > > > > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > >
Re: Congratulations on becoming a TLP!
Thanks for the guiding work from our mentors, I actually learn lots of from your speech and your mails in ASF mail group. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Willem Jiang 于2018年10月21日周日 上午8:42写道： > Yeah, it's a great team work. > We really appreciate the help from our mentors. > > Regards, > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Sat, Oct 20, 2018 at 1:27 PM Jean-Baptiste Onofré > wrote: > > > > Congrats to the whole team ! > > > > Regards > > JB > > > > On 20/10/2018 07:20, Roman Shaposhnik wrote: > > > Hi! > > > > > > as you all probably are aware by know, this week ASF's board > > > of directors passed a resolution to establish a ServiceComb TLP. > > > My major congratulations to the entire community! It was a great > > > journey with only a few small steps left. > > > > > > There's a series of tasks that you now need to drive to completion > > > to formalize your TLP status. You can take a look at how some > > > of my previous podlings have done it (look up all the sub jiras): > > >https://issues.apache.org/jira/browse/MADLIB-1112 > > > or you can follow the official guid: > > >https://incubator.apache.org/guides/transferring.html > > > > > > If you have any questions -- please don't hesitate to ask any of > > > the [former ;-)] mentors. > > > > > > Thanks, > > > Roman. > > > > > > > -- > > Jean-Baptiste Onofré > > jbono...@apache.org > > http://blog.nanthrax.net > > Talend - http://www.talend.com >
Re: [PPMCS] Podling project logos wanted
Hi, Daniel, Willem, I find that we have upload the servicecomb logo to the place [1], please help to check wheather it is statisfy the requirement? [1] http://apache.org/logos/#servicecomb Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Willem Jiang 于2018年9月16日周日 下午9:41写道： > We can our ServiceComb logo into the website. > Current I didn't have svg files in my hand, so please let me know > about the logo files. > I'd be happy to upload these logo file to Apache website. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > > -- Forwarded message - > From: Daniel Gruno > Date: Tue, Aug 28, 2018 at 6:10 PM > Subject: [PPMCS] Podling project logos wanted > To: > > > Hello, beautiful Apache podlings! > > I am looking for podling project logos for use in the central logo site, > located at http://www.apache.org/logos/ > > Assuming your project does not yet have their logo there yet ( you can > check for podlings at http://www.apache.org/logos/#incubating ), if you > could please commit your logo(s) or have me assist you in this, that > would be awesome. The process for getting your logo(s) displayed on the > site is detailed at http://www.apache.org/logos/about.html > > With warm regards, > Daniel. > > PS: While this was sent to the PPMCS, please feel free to share it with > your dev@ lists, if you need assistance from the broader community. > > PPS: do not use 'incubator-' in your logo names, just call it nemo.eps, > netbeans.svg or whatever your podling DNS name is. >
Re: [VOTE] Graduate Apache ServiceComb (incubating)
+1 binding Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Yang Bo 于2018年9月14日周五 下午4:32写道： > +1 (binding) > > On Fri, Sep 14, 2018 at 3:58 PM Willem Jiang > wrote: > > > Please vote on the proposal for ServiceComb graduation to TLP to submit > to > > the Incubator PMC. > > > > Vote: > > [ ] +1 - Recommend Graduation of Apache ServiceComb as a TLP > > [ ] -1 - Do not recommend graduation of Apache ServiceComb because …. > > > > This vote will stay open for at least 72 hours. > > > > > > > > Establish the Apache ServiceComb Project > > > > WHEREAS, the Board of Directors deems it to be in the best interests of > > the Foundation and consistent with the Foundation's purpose to establish > > a Project Management Committee charged with the creation and maintenance > > of open-source software, for distribution at no charge to the public, > > related to a microservice framework that provides a set of tools and > > components to make development and deployment of cloud applications > > easier. > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > (PMC), to be known as the "Apache ServiceComb Project", be and hereby is > > established pursuant to Bylaws of the Foundation; and be it further > > > > RESOLVED, that the Apache ServiceComb Project be and hereby is > > responsible for the creation and maintenance of software related to a > > microservice framework that provides a set of tools and components to > > make development and deployment of cloud applications easier; and be it > > further > > > > RESOLVED, that the office of "Vice President, Apache ServiceComb" be and > > hereby is created, the person holding such office to serve at the > > direction of the Board of Directors as the chair of the Apache > > ServiceComb Project, and to have primary responsibility for management > > of the projects within the scope of responsibility of the Apache > > ServiceComb Project; and be it further > > > > RESOLVED, that the persons listed immediately below be and hereby are > > appointed to serve as the initial members of the Apache ServiceComb > > Project: > > > > * Aray Chenchu Sukesh > > * Bao Liu > > * Eric Lee > > * Jean-Baptiste Onofré > > * Jimin Wu > > * Linzhinan > > * Mohammad Asif Siddiqui > > * Qi Zhang > > * Roman Shaposhnik > > * Timothy Chen > > * Willem Ning Jiang > > * Yang Bo > > * Yihua Cui > > * Yin Xiang > > * Zheng Feng > > * zhengyangyong > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Willem Ning Jiang be > > appointed to the office of Vice President, Apache ServiceComb, to serve > > in accordance with and subject to the direction of the Board of > > Directors and the Bylaws of the Foundation until death, resignation, > > retirement, removal or disqualification, or until a successor is > > appointed; and be it further > > > > RESOLVED, that the Apache ServiceComb Project be and hereby is tasked > > with the migration and rationalization of the Apache Incubator > > ServiceComb podling; and be it further > > > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > > ServiceComb podling encumbered upon the Apache Incubator PMC are > > hereafter discharged. > > > > Regards, > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > > -- > Best Regards, > Yang. >
Re: [DRAFT] Graduation resolution proposal
+1 In the past year, we have made a lot of efforts in community promotion and technological innovation and optimization. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Kirin Wang 于2018年9月13日周四 上午9:42写道： > +1 > Happy to see the achievements of ServiceComb > > Willem Jiang 于2018年9月12日周三 下午9:52写道： > > > As ServiceComb community discussed for the graduation for a while[1] > > and all the committer are OK to be the member of PMC[2]. > > > > Now we have the developer team[3] from Huawei, Talend, Stealth, > > Hyperpilot, RedHat, JingDong,Tencent, Syswin, PICC, Changhong, > > Cainiao. > > > > 3300+ commits on development of three subproject. > > 1350+ PRs on the Github > > 171 contributors > > 800+ issues created > > 700+ issues resolved > > > > dev has 113 subscribers > > 208 emails sent by 28 people, divided into 30 topics in last month > > > > Please check out Apache Maturity Model Assessment for ServiceComb[4] > > for more information. > > > > I just draft our graduation resolution proposal here. Please comment it. > > > > NOTE > > * I'm proposing myself as initial PMC chair -- Please comment if > community > > is onboard with this or propose other persons as well > > > > [1] > > > https://lists.apache.org/thread.html/8e59fef1a9eae9ee90808114b3abbdfdf8c6f24442d7575ee04f5100@%3Cdev.servicecomb.apache.org%3E > > [2] > > > https://lists.apache.org/thread.html/2d1e7f17f15fc8ec0d4d293798991e93127534be9cc13334336d228f@%3Cdev.servicecomb.apache.org%3E > > [3]https://servicecomb.incubator.apache.org/developers/team/ > > [4] > > > https://cwiki.apache.org/confluence/display/SERVICECOMB/Apache+Maturity+Model+Assessment+for+ServiceComb > > > > > > > > Establish the Apache ServiceComb Project > > > > WHEREAS, the Board of Directors deems it to be in the best interests of > > the Foundation and consistent with the Foundation's purpose to establish > > a Project Management Committee charged with the creation and maintenance > > of open-source software, for distribution at no charge to the public, > > related to a microservice framework that provides a set of tools and > > components to make development and deployment of cloud applications > > easier. > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > (PMC), to be known as the "Apache ServiceComb Project", be and hereby is > > established pursuant to Bylaws of the Foundation; and be it further > > > > RESOLVED, that the Apache ServiceComb Project be and hereby is > > responsible for the creation and maintenance of software related to a > > microservice framework that provides a set of tools and components to > > make development and deployment of cloud applications easier; and be it > > further > > > > RESOLVED, that the office of "Vice President, Apache ServiceComb" be and > > hereby is created, the person holding such office to serve at the > > direction of the Board of Directors as the chair of the Apache > > ServiceComb Project, and to have primary responsibility for management > > of the projects within the scope of responsibility of the Apache > > ServiceComb Project; and be it further > > > > RESOLVED, that the persons listed immediately below be and hereby are > > appointed to serve as the initial members of the Apache ServiceComb > > Project: > > > > * Aray Chenchu Sukesh > > * Bao Liu > > * Eric Lee > > * Jean-Baptiste Onofré > > * Jimin Wu > > * Linzhinan > > * Mohammad Asif Siddiqui > > * Qi Zhang > > * Roman Shaposhnik > > * Timothy Chen > > * Willem Ning Jiang > > * Yang Bo > > * Yihua Cui > > * Yin Xiang > > * Zheng Feng > > * zhengyangyong > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Willem Ning Jiang be > > appointed to the office of Vice President, Apache ServiceComb, to serve > > in accordance with and subject to the direction of the Board of > > Directors and the Bylaws of the Foundation until death, resignation, > > retirement, removal or disqualification, or until a successor is > > appointed; and be it further > > > > RESOLVED, that the Apache ServiceComb Project be and hereby is tasked > > with the migration and rationalization of the Apache Incubator > > ServiceComb podling; and be it further > > > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > > ServiceComb podling encumbered upon the Apache Incubator PMC are > > hereafter discharged. > > > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > >
Re: [DISCUSS] Heading to graduation
FYI, To the ServiceComb trademark transferring, the donor counsel has sent the transferring contract to Brand VP, and waiting for replying. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Zen Lin 于2018年9月11日周二 下午2:40写道： > Good News, thanks to Willem's hard work. > > Best Regards, > --- > Zen Lin > zenlintechnofr...@gmail.com > Focused on Micro Service and Apache ServiceComb > > > Willem Jiang 于2018年9月10日周一 下午7:54写道： > >> Hi， >> >> Here are the resolution document which is based on the feedback of >> moving the whole committer to ServiceComb PMC. >> Please let me know if you have any question about this document. >> >> Establish the Apache ServiceComb Project >> >> WHEREAS, the Board of Directors deems it to be in the best interests of >> the Foundation and consistent with the Foundation's purpose to establish >> a Project Management Committee charged with the creation and maintenance >> of open-source software, for distribution at no charge to the public, >> related to a microservice framework that provides a set of tools and >> components to make development and deployment of cloud applications >> easier. >> >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee >> (PMC), to be known as the "Apache ServiceComb Project", be and hereby is >> established pursuant to Bylaws of the Foundation; and be it further >> >> RESOLVED, that the Apache ServiceComb Project be and hereby is >> responsible for the creation and maintenance of software related to a >> microservice framework that provides a set of tools and components to >> make development and deployment of cloud applications easier; and be it >> further >> >> RESOLVED, that the office of "Vice President, Apache ServiceComb" be and >> hereby is created, the person holding such office to serve at the >> direction of the Board of Directors as the chair of the Apache >> ServiceComb Project, and to have primary responsibility for management >> of the projects within the scope of responsibility of the Apache >> ServiceComb Project; and be it further >> >> RESOLVED, that the persons listed immediately below be and hereby are >> appointed to serve as the initial members of the Apache ServiceComb >> Project: >> >> * Aray Chenchu Sukesh >> * Bao Liu >> * Eric Lee >> * Jean-Baptiste Onofré >> * Jimin Wu >> * Linzhinan >> * Mohammad Asif Siddiqui >> * Qi Zhang >> * Roman Shaposhnik >> * Timothy Chen >> * Willem Ning Jiang >> * Yang Bo >> * Yihua Cui >> * Yin Xiang >> * Zheng Feng >> * zhengyangyong >> >> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Willem Ning Jiang be >> appointed to the office of Vice President, Apache ServiceComb, to serve >> in accordance with and subject to the direction of the Board of >> Directors and the Bylaws of the Foundation until death, resignation, >> retirement, removal or disqualification, or until a successor is >> appointed; and be it further >> >> RESOLVED, that the initial Apache ServiceComb PMC be and hereby is >> tasked with the creation of a set of bylaws intended to encourage open >> development and increased participation in the Apache ServiceComb >> Project; and be it further >> >> RESOLVED, that the Apache ServiceComb Project be and hereby is tasked >> with the migration and rationalization of the Apache Incubator >> ServiceComb podling; and be it further >> >> RESOLVED, that all responsibilities pertaining to the Apache Incubator >> ServiceComb podling encumbered upon the Apache Incubator PMC are >> hereafter discharged. >> >> >> Willem Jiang >> >> Twitter: willemjiang >> Weibo: 姜宁willem >> On Thu, Sep 6, 2018 at 8:31 AM Willem Jiang >> wrote: >> > >> > I already send out a mail to the private mailing list. But it could >> > be more fair to let the existing committers make their own choice. >> > I will send out separate a mail to the dev to make sure they are >> informed. >> > >> > >> > Willem Jiang >> > >> > Twitter: willemjiang >> > Weibo: 姜宁willem >> > >> > On Thu, Sep 6, 2018 at 7:03 AM Roman Shaposhnik >> wrote: >> > > >> > > On Wed, Sep 5, 2018 at 3:47 PM, Willem Jiang >> wrote: >> > > > There are some committer who moves on to the other job and don't >> spend >> > > > much time on this project. >> > > > I'd happy to send a mail for them to ask if they are still want to >> > > > join us. It could be great if they can still contribute to project. >> > > >> > > I typically find it very useful to have an email explaining the >> > > responsiblilities >> > > of the PMC membership sent out right before the graduation asking >> existing >> > > committers if they'd be interested in those responsibilities. >> > > >> > > Thanks, >> > > Roman. >> >
Re: [DISCUSS] Heading to graduation
Good News, thanks to Willem's hard work. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Willem Jiang 于2018年9月10日周一 下午7:54写道： > Hi， > > Here are the resolution document which is based on the feedback of > moving the whole committer to ServiceComb PMC. > Please let me know if you have any question about this document. > > Establish the Apache ServiceComb Project > > WHEREAS, the Board of Directors deems it to be in the best interests of > the Foundation and consistent with the Foundation's purpose to establish > a Project Management Committee charged with the creation and maintenance > of open-source software, for distribution at no charge to the public, > related to a microservice framework that provides a set of tools and > components to make development and deployment of cloud applications > easier. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache ServiceComb Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache ServiceComb Project be and hereby is > responsible for the creation and maintenance of software related to a > microservice framework that provides a set of tools and components to > make development and deployment of cloud applications easier; and be it > further > > RESOLVED, that the office of "Vice President, Apache ServiceComb" be and > hereby is created, the person holding such office to serve at the > direction of the Board of Directors as the chair of the Apache > ServiceComb Project, and to have primary responsibility for management > of the projects within the scope of responsibility of the Apache > ServiceComb Project; and be it further > > RESOLVED, that the persons listed immediately below be and hereby are > appointed to serve as the initial members of the Apache ServiceComb > Project: > > * Aray Chenchu Sukesh > * Bao Liu > * Eric Lee > * Jean-Baptiste Onofré > * Jimin Wu > * Linzhinan > * Mohammad Asif Siddiqui > * Qi Zhang > * Roman Shaposhnik > * Timothy Chen > * Willem Ning Jiang > * Yang Bo > * Yihua Cui > * Yin Xiang > * Zheng Feng > * zhengyangyong > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Willem Ning Jiang be > appointed to the office of Vice President, Apache ServiceComb, to serve > in accordance with and subject to the direction of the Board of > Directors and the Bylaws of the Foundation until death, resignation, > retirement, removal or disqualification, or until a successor is > appointed; and be it further > > RESOLVED, that the initial Apache ServiceComb PMC be and hereby is > tasked with the creation of a set of bylaws intended to encourage open > development and increased participation in the Apache ServiceComb > Project; and be it further > > RESOLVED, that the Apache ServiceComb Project be and hereby is tasked > with the migration and rationalization of the Apache Incubator > ServiceComb podling; and be it further > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > ServiceComb podling encumbered upon the Apache Incubator PMC are > hereafter discharged. > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > On Thu, Sep 6, 2018 at 8:31 AM Willem Jiang > wrote: > > > > I already send out a mail to the private mailing list. But it could > > be more fair to let the existing committers make their own choice. > > I will send out separate a mail to the dev to make sure they are > informed. > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Thu, Sep 6, 2018 at 7:03 AM Roman Shaposhnik > wrote: > > > > > > On Wed, Sep 5, 2018 at 3:47 PM, Willem Jiang > wrote: > > > > There are some committer who moves on to the other job and don't > spend > > > > much time on this project. > > > > I'd happy to send a mail for them to ask if they are still want to > > > > join us. It could be great if they can still contribute to project. > > > > > > I typically find it very useful to have an email explaining the > > > responsiblilities > > > of the PMC membership sent out right before the graduation asking > existing > > > committers if they'd be interested in those responsibilities. > > > > > > Thanks, > > > Roman. >
Re: Invitation of the ServiceComb PMC
Yes Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb wjm wjm 于2018年9月6日周四 上午10:01写道： > Yes > > bismy 于2018年9月6日周四 上午9:19写道： > > > Yes > > > > > > > > > > -- 原始邮件 -- > > 发件人: "willem.jiang"; > > 发送时间: 2018年9月6日(星期四) 上午9:00 > > 收件人: "dev"; > > > > 主题: Invitation of the ServiceComb PMC > > > > > > > > Hi Committers > > > > As the discussion of "Heading to graduation" [1], we want to setup > > the PMC as part of ServiceComb graduation resolution. So we'd like to > > confirm whether you want to remain as a Project Management Committees > > (PMC) member of Apache ServiceComb project? > > > > I just quote some roles description of PMC from How it works of > Apache[2]. > > If you just heard about PMC, please spend some time to read about the > > role of PMC and understand the responsibilities, and let me know if > > you have any question about it. > > > > " The role of the PMC from a Foundation perspective is oversight. The > > main role of the PMC is not code and not coding - but to ensure that > > all legal issues are addressed, that procedure is followed, and that > > each and every release is the product of the community as a whole. > > That is key to our litigation protection mechanisms. > > > > Secondly the role of the PMC is to further the long term development > > and health of the community as a whole, and to ensure that balanced > > and wide scale peer review and collaboration does happen. Within the > > ASF we worry about any community which centers around a few > > individuals who are working virtually uncontested. We believe that > > this is detrimental to quality, stability, and robustness of both code > > and long term social structures." > > > > If you'd like to be the member of ServiceComb PMC, it's welcome and > > please *respond** 'Yes'* in this thread, or *respond 'No'* if you are > > not interested in any more. > > > > This thread will be available for at least 72 hours, after that, we > > will send individual confirm emails. > > > > [1] > > > https://lists.apache.org/thread.html/3753af01adc9f0db65949565851f66816e1932dde028b99ee7a7c14e@%3Cdev.servicecomb.apache.org%3E > > [2]http://www.apache.org/foundation/how-it-works.html#pmc > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem >
Re: [DISCUSS] Q & A of website issue
To my opinion, if we have faqs, we should make sure there is a search entry that can search questions directly by keyword. Usually, opensource projects use google search embeded into the website, but I am not sure if the google search can search out them. If we can not reach that, I suggest we just list them within the user guide, thus when users use user guide, they can also get the corresponding faqs. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb DeanLee <82529...@qq.com> 于2018年9月5日周三 下午4:21写道： > Hi all, >I want to translate Q & A of the website for English as blew, but > here is a problem. > http://servicecomb.incubator.apache.org/cn/faqs/ >For now, we have two pages of Q(another one in UserGuide). >Should we merge it together or keep it split as before > > https://docs.servicecomb.io/java-chassis/en_US/question-and-answer/question_answer.html > > > Best Regards, > Dean
Re: [DISCUSS] Heading to graduation
Hi Roman, You can find the latest roster on the deverlopers part of the website[1]. [1] http://servicecomb.incubator.apache.org/developers/team/ Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Roman Shaposhnik 于2018年9月5日周三 上午8:56写道： > On Tue, Sep 4, 2018 at 4:55 AM, Jean-Baptiste Onofré > wrote: > > Hi, > > > > Basically, we should ask to the current PPMC if they agree to become PMC. > > > > Regarding the PMC Chair, I'm proposing Willem as Chair. He's driving the > > graduation, active on the project since the beginning, and a great asset > > for the foundation generally speaking. > > +1 to the above! > > btw, what's the current PMC roster vs. committer roster? I mean, > what's the latest on that? > > Thanks, > Roman. >
Re: [DISCUSS] Heading to graduation
Willem Jiang are doing lots of works on technical guide and Apache Way guide, I would like to recommend he to be the PMC Chair. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Kirin Wang 于2018年9月4日周二 下午2:29写道： > +1 > Willem did a lot in building the community > > Lance Ju 于2018年9月4日周二 下午2:26写道： > > > +1 > > > > Mohammad Asif Siddiqui 于2018年9月4日周二 下午1:42写道： > > > > > +1 > > > > > > On Tue, Sep 4, 2018 at 8:59 AM Sure wrote: > > > > > > > +1 > > > > > > > > > > > > -- Original -- > > > > From: wjm wjm > > > > Date: Tue,Sep 4,2018 11:20 AM > > > > To: dev > > > > Subject: Re: [DISCUSS] Heading to graduation > > > > > > > > > > > > > > > > +1 > > > > > > > > 郑扬勇 <342906...@qq.com> 于2018年9月4日周二 上午10:54写道： > > > > > > > > > +1 > > > > > > > > > > > > > > > > > > > > -- 原始邮件 -- > > > > > 发件人: "bismy"; > > > > > 发送时间: 2018年9月4日(星期二) 上午9:26 > > > > > 收件人: "willem.jiang"; > > > > > > > > > > 主题: 回复： [DISCUSS] Heading to graduation > > > > > > > > > > > > > > > > > > > > I recommend Willem Jiang to be the PMC Chair. > > > > > > > > > > > > > > > > > > > > > > > > > -- 原始邮件 -- > > > > > 发件人: "willem.jiang"; > > > > > 发送时间: 2018年9月3日(星期一) 下午4:10 > > > > > 收件人: "dev"; > > > > > > > > > > 主题: Re: [DISCUSS] Heading to graduation > > > > > > > > > > > > > > > > > > > > Hi Team, > > > > > > > > > > For the resolution proposal[1], we need to figure out PMC and PMC > > > Chair > > > > of > > > > > the ServiceComb for the board. > > > > > Normally we just move our PPMC member to the PMC, and we need to > > figure > > > > out > > > > > the PMC Chair. > > > > > > > > > > [1] > > > > > > https://incubator.apache.org/guides/graduation.html#preparing_a_charter > > > > > > > > > > > > > > > > > > > > Willem Jiang > > > > > > > > > > Twitter: willemjiang > > > > > Weibo: 姜宁willem > > > > > > > > > > On Thu, Aug 16, 2018 at 12:32 PM, Jean-Baptiste Onofré < > > > j...@nanthrax.net> > > > > > wrote: > > > > > > > > > > > Hi Willem, > > > > > > > > > > > > thanks for the update. > > > > > > > > > > > > The maturity model assessment draft looks overall good to me. > > > > > > > > > > > > I will add the resolution proposal draft on the wiki as well. > > > > > > > > > > > > Regards > > > > > > JB > > > > > > > > > > > > On 15/08/2018 11:09, Willem Jiang wrote: > > > > > > > With the ServiceComb java-chassis 1.0.0-incubating and > > > service-center > > > > > > > 1.0.0-incubating release officially out. > > > > > > > We believe it is time to discuss what requirements remains to > > > > consider > > > > > > > graduation to the TLP. > > > > > > > > > > > > > > I just updated the ServiceComb Project Status for it: > > > > > > > > > > > > > > http://servicecomb.incubator.apache.org/ > > > > > > > > > > > > > > Apache ServiceComb entered incubation in November of 2017, > > > > ServiceComb > > > > > > > community learned a lot about how to do things in Apache ways. > > > > > > > Now we are a very helpful and engaged community, ready to help > on > > > all > > > > > > > questions from the ServiceComb Community. > > > > > > > We are making consensus decisions through the discussion in the > > > > mailing > > > > > > > list
Re: [ANN] New ServiceComb PPMC: Feng Zheng (冯征）
Congratulations. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Lance Ju 于2018年9月4日周二 下午2:26写道： > Congratulations! > > 郑扬勇 <342906...@qq.com> 于2018年9月4日周二 上午10:53写道： > > > Congratulations! > > > > > > > > > > -- 原始邮件 -- > > 发件人: "willem.jiang"; > > 发送时间: 2018年8月31日(星期五) 晚上10:53 > > 收件人: "dev"; > > > > 主题: [ANN] New ServiceComb PPMC: Feng Zheng (冯征） > > > > > > > > Please join me and the rest of the ServiceComb PPMC members in welcoming > > our > > new ServiceComb PPMC member Feng Zheng. > > > > Feng Zheng does lots of contributions to the Saga since earlier this year > > and he did a good bridge work between ServiceComb and RedHat transaction > > related projects. > > > > Congratulations to Feng Zheng! Welcome! > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem >
Re: [ANN] New ServiceComb PPMC: Zheng Yangyong (郑扬勇）
Congratulations. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb 郑扬勇 <342906...@qq.com> 于2018年9月4日周二 上午10:51写道： > Thanks :) > > -- 原始邮件 -- > 发件人: "willem.jiang"; > 发送时间: 2018年8月31日(星期五) 晚上10:58 > 收件人: "dev"; > > 主题: [ANN] New ServiceComb PPMC: Zheng Yangyong (郑扬勇） > > > > Please join me and the rest of the ServiceComb PPMC members in welcoming > our > new ServiceComb PPMC member Zheng Yangyong. > > Zheng Yangyong does lots of contributions to the Java Chassis, Saga since > last August and helps users to solve their daily problems with > ServiceComb. > > Congratulations to Zheng Yangyong! Welcome! > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem
Re: [ANN] New ServiceComb PPMC: Lin Zhinan (林志南）
My pleasure, thanks for trust. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb 郑扬勇 <342906...@qq.com> 于2018年9月4日周二 上午10:52写道： > Congratulations! > > > -- 原始邮件 -- > 发件人: "willem.jiang"; > 发送时间: 2018年8月31日(星期五) 晚上11:01 > 收件人: "dev"; > > 主题: [ANN] New ServiceComb PPMC: Lin Zhinan (林志南） > > > > Please join me and the rest of the ServiceComb PPMC members in welcoming > our > new ServiceComb PPMC member Lin Zhinan. > > Lin Zhinan does lots of contributions to the ServiceComb later last year > and he already did lot of PPMC work such as helping us to hold the meetup > events. > > Congratulations to Lin Zhinan! Welcome! > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem
Re: [DISCUSS]Add Vendor Sources Code In SC project
+1 to include source code into vendor folders, and it is better to update the release script of excluding the vendor directories at the same time. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Sure 于2018年8月25日周六 下午10:25写道： > Using glide or dep tool can achieve the effect of generating vendor. > > As sc already used glide to manage package and go mod is still the > experimental feature in go 1.11, > i think there is no need to changed it, we can just push the source code > to repo. > > > > > > -- 原始邮件 -- > 发件人: "Xiaoliang Tian"; > 发送时间: 2018年8月25日(星期六) 晚上6:02 > 收件人: "dev"; > > 主题: Re: [DISCUSS]Add Vendor Sources Code In SC project > > > > I have tired go mod today, it is a good tool. consider about it > > glide is never a option, because it is recommending user to use dep. > > Mohammad Asif Siddiqui 于2018年8月25日周六 下午5:57写道： > > > +1 > > > > We can add the vendor to SC folder, this will ease out the development of > > SC specially in China region where GFC blocks the downloading of google > > libs. > > > > Regards > > Asif > > > > > > On Sat, 25 Aug 2018, 3:22 pm Yang Bo, wrote: > > > > > +1 > > > > > > As for the Apache compliance, It's OK to include the vendor source code > > in > > > our repository. We can update the release script and exclude the vendor > > > directory when releasing. > > > > > > On Sat, Aug 25, 2018 at 4:20 PM Kirin Wang > > > wrote: > > > > > > > +1 > > > > But may be we need to confirm if there are Apache compliance issue > > about > > > > it ? > > > > > > > > Xiaoliang Tian 于2018年8月25日周六 上午10:48写道： > > > > > > > > > +1 Agree > > > > > the truth is go project can easily go into a dep hell and there is > no > > > dep > > > > > tool can manage the complicated deps > > > > > > > > > > checkout how go project does > > > > > https://github.com/istio/istio/tree/master/vendor > > > > > https://github.com/coreos/etcd/tree/master/vendor > > > > > > > > > > dep management is torturing go developers now > > > > > > > > > > Sure 于2018年8月25日周六 上午10:39写道： > > > > > > > > > > > Developers from China complain it is hard to go get the 3rd > depends > > > > > source > > > > > > code of sc. > > > > > > I suggest add these source code in vendor directory in sc > project, > > > like > > > > > > Istio and etcd project do. > > > > > > > > > > > > > > > > > > -- > > > Best Regards, > > > Yang. > > > > >
[RESULT] [VOTE] Hold an event called Apache ServiceComb (incubating) Meetup as a Co-located Event in HC 2018, Shanghai, China, OCT 12.
Hi All, We are glad to announce that ServiceComb community has approved Holding an event called Apache ServiceComb (incubating) Meetup as a Co-located Event in HC 2018 Shanghai, China, OCT 12, with the following results: +1 binding: 4(Willem Jiang, Liubao, Wu Jimin, Sure) +1 non-binding: 5(Zhongyuan Zhou, Dean Lee, Yangyong Zheng, Yang Bo, Lance Ju) Vote Thread : https://www.mail-archive.com/dev@servicecomb.apache.org/msg05116.html Thanks All for helping us to discuss and vote for holding the event. On the behalf of ServiceComb Team Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb
Re: [ANN] New ServiceComb committer: Yang Bo (杨波)
Congratulations! Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Kirin Wang 于2018年8月24日周五 上午11:28写道： > Congratulations! > > Willem Ning Jiang 于2018年8月24日周五 上午11:27写道： > > > Please join me and the rest of the ServiceComb PPMC members in welcoming > > our > > new ServiceComb committer: Yang Bo (杨波). > > > > Yang Bo starts to contribute on ServiceComb project earlier this > > year. He help us fix lots of License related issues in, and updates > > the website with his new ideas. He is also active in the mailing list, > > and we look forward to many more contributions in the future. > > > > Congratulations to Yang Bo! Welcome! > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > >
[VOTE] Holding an Apache ServiceComb (incubating) Meetup as a Co-located Event in HC 2018 Shanghai, China, OCT 12.
Hi All, This is a call for Vote to hold an Apache ServiceComb (incubating) Meetup as a Co-located Event in HC 2018 Shanghai, China, OCT 12. As discussed in the meetup proposal [1], we have plan to hold an Apache ServiceComb (incubating) Meetup, details are listed bellow, - What is the topic focus of the event? Topics are focused on Apache Way related topics， user-practices /technologies topics of Apache ServiceComb (incubating). - Who is organising the event? PMCs of ServiceComb (incubating) are the organizer - When is the event? OCT 12 - How many attendees are expected? 80~120 - How much PMC involvement is there already? 5 - Which marks are requested? Two marks are requested, 1. Name of "Apache ServiceComb Incubating " 2. "Powered By" Apache Incubator logo of Apache ServiceComb (incubating) - Is this for profit or non-profit? (See "Event Profits And Donations")? non-profit. - Who will do speech for Apache Way related? We are inviting Roman and J M for to help doing the sharing. [1] https://www.mail-archive.com/dev@servicecomb.apache.org/msg05081.html Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb
Re: [DISCUSS]add The Sources Panel In Schema Test
+1 It will be a nice feature to help debugging. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Willem Jiang 于2018年8月23日周四 下午4:21写道： > Yeah, it's a convice feature for the developer to use. > +1 to put it into 1.1.0 roadmap. > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Thu, Aug 23, 2018 at 11:48 AM, Sure wrote: > > > Now, shema test in the sc frontend does not contain the schema source, > > then the developer can not debug it coveniently. > > So, I suggest add a source panel to shema test >
Re: [DISCUSSION] add Github button in navigation banner of servicecomb website
+1 to kiring's idea. By the way, I think the website cannot adaptive itself is a bug from the website framework.This could be fixed later from the framework site. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Lance Ju 于2018年8月23日周四 下午5:13写道： > Thanks, Kirin, I see the result. > I test the web page under Chrome's developer mode(Phone simulator), the top > banner shows only a "Chinese" button, and a "More" menu where "Github" is > included, I think it makes sense. > By the way, there is also a Github link in the bottom banner's "Community" > block, if the user can't get the GitHub link at first sight, the one in the > bottom would also be helpful. > > Willem Jiang 于2018年8月23日周四 上午9:18写道： > > > I don't think we can keep adding the links to the upper banner, if the > > screen size is smaller, we cannot guarantee all the links are displayed. > > How about we can add the github repo links just after latest release > links. > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Thu, Aug 23, 2018 at 9:06 AM, Kirin Wang > > wrote: > > > > > Hi lance: > > > > > > you can view my test website: https://wangkirin.github.io/ > to > > > see > > > the result > > > > > > Lance Ju 于2018年8月22日周三 下午9:36写道： > > > > > > > I can't see the banner, would you share the images' URL, Kirin? > > > > > > > > Willem Jiang 于2018年8月22日周三 上午10:50写道： > > > > > > > > > We have the github reference here[1], and it could be great that > we > > > have > > > > > some banner for all the repos that we have in the home page. > > > > > > > > > > http://servicecomb.incubator.apache.org/developers/ > > > > > > > > > > > > > > > Willem Jiang > > > > > > > > > > Twitter: willemjiang > > > > > Weibo: 姜宁willem > > > > > > > > > > On Wed, Aug 22, 2018 at 9:34 AM, Kirin Wang < > wangqilint...@gmail.com > > > > > > > > wrote: > > > > > > > > > > > Hi team: > > > > > > Now , the first way most people know about our project is > > the > > > > > > website "http://servicecomb.incubator.apache.org/; , but some > feed > > > > back > > > > > > from users show that there is no clear entrance of our Github > code > > > > > > repository in it, so may be we should put it in a conspicuous > > > place, I > > > > > > think the navigation banner may be a good choice. I tried in my > > > > personal > > > > > > repo and the result as shown below: > > > > > > > > > > > > English Version: > > > > > > [image: image.png] > > > > > > > > > > > > Chinese Version: > > > > > > [image: image.png] > > > > > > > > > > > > What do you think about that? > > > > > > > > > > > > > > > > > > > > >
Proposal for holding a Apache ServiceComb(incubating) meetup as a Co-Located Event in HC 2018
This is a Proposal for holding a Co-Located Event in HC 2018[1] to help building ServiceComb's community. HC 2018 is a conference hosted by Huawei, have nearly 1000 summits and forums, and more than 2000+ developers will join it. My suggestion is to hold a Meetup named "Apache ServiceComb (incubating) Meetup", to share technologies and user cases of ServiceComb.We are also inviting Roman and J M to join the meetup to have speech about ASF on the meetup. I have already talked to Huawei to get free resources for the meetup. I would like to listen your suggestions from you guys, If agreed, I am goting to start a vote thread with detail event plan and brand request for it. [1] https://www.huawei.com/en/press-events/events/huaweiconnect2018?ic_medium=hwdc_source=ebg_event_EEBGHQ189103S=ebgevent Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb
Re: [ANN] New ServiceComb committer: Lin Zhinan (林志南）
Thanks to ServiceComb PPMC's trust and invitation. I have Involved in community building of ServiceComb, and I am going keep on work on it. By the way, I have got lots of useful help from the articles in ASF, something like Guide to Successful Community Building [1]. Also so many nice guys and ASF Community elites have helped me, thanks. [1] https://incubator.apache.org/guides/community.html Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Zheng Feng 于2018年8月20日周一 下午10:47写道： > Congratulations and welcome on board ! > > 2018-08-20 22:33 GMT+08:00 wjm wjm : > > > Congratulations ~ > > > > 2018-08-20 17:09 GMT+08:00 bismy : > > > > > Congratulations & welcome to join ServiceComb > > > > > > > > > -- 原始邮件 -- > > > 发件人: "willem.jiang"; > > > 发送时间: 2018年8月20日(星期一) 下午4:11 > > > 收件人: "dev"; > > > > > > 主题: [ANN] New ServiceComb committer: Lin Zhinan (林志南） > > > > > > > > > > > > Please join me and the rest of the ServiceComb PPMC members in > welcoming > > > our > > > new ServiceComb committer: Lin Zhinan (林志南). > > > > > > Lin Zhinan contribute the ServiceComb since last year, you may heard > him > > a > > > lot if you checkout the mailing list or attend ServiceComb offline > meetup > > > , and > > > we look forward to many more contributions in the future. > > > > > > Congratulations to Lin Zhinan! Welcome! > > > > > > > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > >
Re: [VOTE] Proposal for holding an Apache ServiceComb (Incubating) Meetup in Bangalore, India
+1 non-binding Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Mohammad Asif Siddiqui 于2018年8月1日周三 上午12:40写道： > Hi All, > > This is a call for a Vote to hold Apache ServiceComb (incubating) Meetup > Hosted by Huawei India at Huawei Bangalore Office. > > As discussed in the meetup proposal [1], we have plan to hold Apache > ServiceComb (incubating) Meetup, details are listed bellow, > > - What is the topic focus of the event? > > Topics are focused on > microservices-ecosystem/microservices-development/ecosystem of Apache > ServiceComb (incubating) > > - Who is organising the event? > > PMCs of ServiceComb (incubating) are the organizer > > - When is the event? > > 11th August, 2018 (10:00 AM to 14:00 PM) > > - How many attendees are expected? > > 60~100 > > - How much PMC involvement is there already? > > 2 > > - Which marks are requested? > > Two marks are requested, > 1. Name of "Apache ServiceComb Incubating Meetup Hosted by Huawei" > 2. "Powered By" Apache Incubator logo of Apache ServiceComb (incubating) > > - Is this for profit or non-profit? (See "Event Profits And Donations")? > > non-profit. > > Voting will start now (Tuesday, 31st July 2018) and will remain open for > atleast 72 hours. Request all PPMC members to give their vote. > > [1] > https://lists.apache.org/thread.html/f6db3ab0f7634170db9b68986eaed3bea7768990c9f62e7bae857dc3@%3Cdev.servicecomb.apache.org%3E > > > Regards > Asif >
Re: [VOTE] Proposal for holding an ServiceComb Meetup in Bangalore, India
Hi Because ServiceComb is a Apache incubating project, so once you use ServiceComb, you are using a Apache Brandon. So that means this VOTE also include requesting permission from our PPMCs for using of Apache ServiceComb (incubating) . Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Mohammad Asif Siddiqui 于2018年7月30日周一 下午3:32写道： > Hi All, > > After a very positive discussion on holding a ServiceComb Meetup in > Bangalore in dev@servicecomb.apache.org [1] I would like to call for a > vote from all PPMC member to approve this meetup. Meetup details are given > below: > > Meetup Name: "Introduction to Microservices Development and ServiceComb" > > When : 11th August, 2018 > > Where: Huawei India Office > > Who all will join : 100+ developers/users who are using/interested in > Microservices > > Talks: > 1. Introduction to Microservices and competitive landscape(External > Speaker) > 2. New Framework for Microservices:ServiceComb (Krishna/Sanil) > 3. Service Discovery:Service-Center (Asif) > 4. Microservice Development Kit:Java-Chassis (Sukesh) > 5. Demo and Hands on workshop for ServiceComb (Become an apache > contributor today) > > Duration: 3-4 hours > > Note : Since this a small generalized meetup for Microservices so we > won't be using any Apache Brands/Logos hence there might be no approval > required from Apache Brand Management. > > [1] > https://lists.apache.org/thread.html/f6db3ab0f7634170db9b68986eaed3bea7768990c9f62e7bae857dc3@%3Cdev.servicecomb.apache.org%3E > > > Regards > Asif >
Re: 【Proposal】Close ServiceComb group on github
I took some notes inline your message as follows. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Willem Jiang 于2018年7月27日周五 下午5:41写道： > For the seckill I will set it readonly, I think Zhengyangyong personal > project. > I will close the spring-cloud-servicecomb-plugins repo shortly. > Zen: How about zhengyangyong's opinion , I think we would not keep this repo in any official groups, so please deal with it, how about keep it as your personal project? > > For the ServiceComb-Company-WorkShop > <https://github.com/ServiceComb/ServiceComb-Company-WorkShop>, I need to > be > added into huaweicse group to do the transfer work. Zen: Liubao is the owner of huaweicse. > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Fri, Jul 27, 2018 at 4:16 PM, Zen Lin > wrote: > > > Thanks. > > How to deal with these three repos, > > [1] https://github.com/ServiceComb/ServiceComb-Company-WorkShop > > [2] https://github.com/ServiceComb/spring-cloud-servicecomb-plugins > > [3] https://github.com/ServiceComb/seckill > > > > Can anyone who have the permission of https://github.com/ServiceComb > help > > to deal with them? > > Transfer the Company repo [1] to huaweicse. > > Close the spring-cloud-servicecomb-plugins repo [2]. > > Transfer the seckill [3] to personal workspace or huaweicse. > > > > Best Regards, > > --- > > Zen Lin > > zenlintechnofr...@gmail.com > > Focused on Micro Service and Apache ServiceComb > > > > > > Willem Jiang 于2018年7月26日周四 下午8:47写道： > > > > > FYI, > > > I just transfer those repos into go-chassis group. > > > > > > https://github.com/ServiceComb/go-chassis > > > > > > https://github.com/ServiceComb/cse-collector > > > > > > https://github.com/ServiceComb/go-cc-client > > > > > > https://github.com/ServiceComb/go-archaius > > > > > > https://github.com/ServiceComb/go-sc-client > > > > > > https://github.com/ServiceComb/paas-lager > > > > > > https://github.com/ServiceComb/http-client > > > > > > https://github.com/ServiceComb/auth > > > > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Wed, Jul 25, 2018 at 4:13 PM, Zen Lin > > > wrote: > > > > > > > Hi Guys, > > > > > > > > As we known, Apache ServiceComb (incubating) is in the "Near > > Graduation" > > > > status. > > > > There still a ServiceComb group on the github [1], projects under > this > > > > group is not in the incubator scope of ServiceComb now, my suggestion > > is > > > to > > > > close this group. > > > > > > > > I have gone though the projects and find out the corresponding > > > maintainers > > > > , please transfer the project to other place but not ServiceComb, as > > > > follows, > > > > > > > > Maintainer: Shawn > > > > https://github.com/ServiceComb/go-chassis > > > > > > > > https://github.com/ServiceComb/cse-collector > > > > > > > > https://github.com/ServiceComb/go-cc-client > > > > > > > > https://github.com/ServiceComb/go-archaius > > > > > > > > https://github.com/ServiceComb/go-sc-client > > > > > > > > https://github.com/ServiceComb/paas-lager > > > > > > > > https://github.com/ServiceComb/http-client > > > > > > > > https://github.com/ServiceComb/auth > > > > > > > > Maintainer: Willem > > > > https://github.com/ServiceComb/spring-cloud-servicecomb-plugins > > > > > > > > https://github.com/ServiceComb/seckill > > > > > > > > https://github.com/ServiceComb/incubator-servicecomb-website > > > > > > > > Maintainer: Asif > > > > https://github.com/ServiceComb/incubator-servicecomb-service-center > > > > > > > > To the project below, it is a official demo of servicecomb, I am not > > sure > > > > how to deal with this, any thoughts? > > > > https://github.com/ServiceComb/ServiceComb-Company-WorkShop > > > > > > > > > > > > [1] https://github.com/ServiceComb <https://github.com/ServiceComb> > > > > > > > > Best Regards, > > > > --- > > > > Zen Lin > > > > zenlintechnofr...@gmail.com > > > > Focused on Micro Service and Apache ServiceComb > > > > > > > > > >
Re: 【Proposal】Close ServiceComb group on github
Thanks. How to deal with these three repos, [1] https://github.com/ServiceComb/ServiceComb-Company-WorkShop [2] https://github.com/ServiceComb/spring-cloud-servicecomb-plugins [3] https://github.com/ServiceComb/seckill Can anyone who have the permission of https://github.com/ServiceComb help to deal with them? Transfer the Company repo [1] to huaweicse. Close the spring-cloud-servicecomb-plugins repo [2]. Transfer the seckill [3] to personal workspace or huaweicse. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Willem Jiang 于2018年7月26日周四 下午8:47写道： > FYI, > I just transfer those repos into go-chassis group. > > https://github.com/ServiceComb/go-chassis > > https://github.com/ServiceComb/cse-collector > > https://github.com/ServiceComb/go-cc-client > > https://github.com/ServiceComb/go-archaius > > https://github.com/ServiceComb/go-sc-client > > https://github.com/ServiceComb/paas-lager > > https://github.com/ServiceComb/http-client > > https://github.com/ServiceComb/auth > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Wed, Jul 25, 2018 at 4:13 PM, Zen Lin > wrote: > > > Hi Guys, > > > > As we known, Apache ServiceComb (incubating) is in the "Near Graduation" > > status. > > There still a ServiceComb group on the github [1], projects under this > > group is not in the incubator scope of ServiceComb now, my suggestion is > to > > close this group. > > > > I have gone though the projects and find out the corresponding > maintainers > > , please transfer the project to other place but not ServiceComb, as > > follows, > > > > Maintainer: Shawn > > https://github.com/ServiceComb/go-chassis > > > > https://github.com/ServiceComb/cse-collector > > > > https://github.com/ServiceComb/go-cc-client > > > > https://github.com/ServiceComb/go-archaius > > > > https://github.com/ServiceComb/go-sc-client > > > > https://github.com/ServiceComb/paas-lager > > > > https://github.com/ServiceComb/http-client > > > > https://github.com/ServiceComb/auth > > > > Maintainer: Willem > > https://github.com/ServiceComb/spring-cloud-servicecomb-plugins > > > > https://github.com/ServiceComb/seckill > > > > https://github.com/ServiceComb/incubator-servicecomb-website > > > > Maintainer: Asif > > https://github.com/ServiceComb/incubator-servicecomb-service-center > > > > To the project below, it is a official demo of servicecomb, I am not sure > > how to deal with this, any thoughts? > > https://github.com/ServiceComb/ServiceComb-Company-WorkShop > > > > > > [1] https://github.com/ServiceComb <https://github.com/ServiceComb> > > > > Best Regards, > > --- > > Zen Lin > > zenlintechnofr...@gmail.com > > Focused on Micro Service and Apache ServiceComb > > >
Re: [DISCUSS] Proposal for holding an ServiceComb Meetup in Bangalore, India
+1 It looks it will help promoting the community. And reminding as follows, please go through the small-events [1] and the branding policy [2] to ensure you have strictly compliance Apache rules. Then, you can create a vote for the event in dev@servicecomb mail group [3]. [1]http://community.apache.org/events/small-events.html [2]http://www.apache.org/foundation/marks/events.html [3] https://www.mail-archive.com/dev@servicecomb.apache.org/msg03436.html Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Mohammad Asif Siddiqui 于2018年7月25日周三 下午9:18写道： > Hi All, > > As a Bangalore is known as a Sillicon Valley of India which is a home for > millions of developers so we wanted to host a ServiceComb Meetup in > Bangalore to promote ServiceComb as a Microservice Solution and increase > user/developer base in India. Here are the details of the meetup: > > Meetup Name: "Introduction to Microservices Development and ServiceComb" > > When : 11th August, 2018 > > Where: Huawei India Office > > Who all will join : 100+ developers/users who are using/interested in > Microservices > > Talks: > 1. Introduction to Microservices and competitive landscape(External > Speaker) > 2. New Framework for Microservices:ServiceComb (Krishna/Sanil) > 3. Service Discovery:Service-Center (Asif) > 4. Microservice Development Kit:Java-Chassis (Sukesh) > 5. Demo and Hands on workshop for ServiceComb > > Duration: 3-4 hours > > Any thoughts? > > Regards > Asif >
Re: 【Proposal】Close ServiceComb group on github
OK , got it. I think we can suggest the author to transfer the repos to huaweicse for temporary, and we also can create issues to track removing huawei-related informations. I am going to create it. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Bin Ma 于2018年7月26日周四 上午9:33写道： > Currently, Scaffold_CRM Demo [1],Company Demo [2] and Seckill [3] are > popular with users. > It is useful to create a sub project to host these demos before closing > ServiceComb organization. > > [1] https://github.com/zhengyangyong/scaffold > [2] https://github.com/ServiceComb/ServiceComb-Company-WorkShop > [3] https://github.com/ServiceComb/seckill > > > Best Wishes & Regards > --- > Mabin > > > > Willem Jiang 于2018年7月26日周四 上午8:06写道： > > > ServiceComb-Company-WorkShop has some stuff relates to Huawei cloud, so > we > > don't put it as a sub project as the Apache ServiceComb. > > If we have more demo project come out, we may consider to create sub > > project in Apache. > > For those demo or personal projects, we need to go through the donation > > process before we move them into Apache. > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Wed, Jul 25, 2018 at 10:20 PM, Zen Lin > > wrote: > > > > > Summarize: > > > Scaffold_CRM Demo [1], which shows how to use servicecomb scaffold to > > > develop a CRM application. > > > Company Demo [2], which shows how to use servicecomb to develop a > > ordinary > > > microservices application. > > > start.servicecomb.io, which is the cold generator website of > > servicecomb. > > > > > > [1] https://github.com/zhengyangyong/scaffold > > > <https://github.com/zhengyangyong/scaffold> > > > [2] https://github.com/ServiceComb/ServiceComb-Company-WorkShop > > > [3] https://github.com/wangkirin/initializr > > > > > > Anymore? > > > > > > Hi Willem, JB, > > > We do not know how to keep these official demos and tools in a Apache > > > project usually. > > > A centralized repository for Demos or tools? something like > > > https://github.com/apache/servicecomb-demos? > > > > > > Best Regards, > > > --- > > > Zen Lin > > > zenlintechnofr...@gmail.com > > > Focused on Micro Service and Apache ServiceComb > > > > > > > > > Jean-Baptiste Onofré 于2018年7月25日周三 下午8:54写道： > > > > > > > Should not be on Apache gitbox ? > > > > > > > > Regards > > > > JB > > > > > > > > Le 25 juil. 2018 à 11:13, à 11:13, Willem Jiang < > > willem.ji...@gmail.com> > > > > a écrit: > > > > >Yeah, we can just transfer the repo to another group. > > > > >If the user use the older URL to access the repo, github can > redirect > > > > >the > > > > >request to the new transfer URL. > > > > > > > > > > > > > > >Willem Jiang > > > > > > > > > >Twitter: willemjiang > > > > >Weibo: 姜宁willem > > > > > > > > > >On Wed, Jul 25, 2018 at 4:47 PM, Yang Bo wrote: > > > > > > > > > >> +1 for removing the ServiceComb organization. > > > > >> > > > > >> Some issues: > > > > >> The go-chassiss and related forked third parties are still hosted > on > > > > >this > > > > >> group. We should migrate those first before closing. > > > > >> > > > > >> > > > > >> On Wed, Jul 25, 2018 at 4:45 PM Willem Jiang < > > willem.ji...@gmail.com> > > > > >> wrote: > > > > >> > > > > >> > I think we just need to find a home for > > > > >> > https://github.com/ServiceComb/ServiceComb-Company-WorkShop > > > > >> > > > > > >> > huaweicse could be a way to go. > > > > >> > > > > > >> > > > > > >> > Willem Jiang > > > > >> > > > > > >> > Twitter: willemjiang > > > > >> > Weibo: 姜宁willem > > > > >> > > > > > >> > On Wed, Jul 25, 2018 at 4:25 PM, bismy wrote: > > > > >> > > > > > >> > > +1. > &
Re: 【Proposal】Close ServiceComb group on github
Summarize: Scaffold_CRM Demo [1], which shows how to use servicecomb scaffold to develop a CRM application. Company Demo [2], which shows how to use servicecomb to develop a ordinary microservices application. start.servicecomb.io, which is the cold generator website of servicecomb. [1] https://github.com/zhengyangyong/scaffold <https://github.com/zhengyangyong/scaffold> [2] https://github.com/ServiceComb/ServiceComb-Company-WorkShop [3] https://github.com/wangkirin/initializr Anymore? Hi Willem, JB, We do not know how to keep these official demos and tools in a Apache project usually. A centralized repository for Demos or tools? something like https://github.com/apache/servicecomb-demos? Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Jean-Baptiste Onofré 于2018年7月25日周三 下午8:54写道： > Should not be on Apache gitbox ? > > Regards > JB > > Le 25 juil. 2018 à 11:13, à 11:13, Willem Jiang > a écrit: > >Yeah, we can just transfer the repo to another group. > >If the user use the older URL to access the repo, github can redirect > >the > >request to the new transfer URL. > > > > > >Willem Jiang > > > >Twitter: willemjiang > >Weibo: 姜宁willem > > > >On Wed, Jul 25, 2018 at 4:47 PM, Yang Bo wrote: > > > >> +1 for removing the ServiceComb organization. > >> > >> Some issues: > >> The go-chassiss and related forked third parties are still hosted on > >this > >> group. We should migrate those first before closing. > >> > >> > >> On Wed, Jul 25, 2018 at 4:45 PM Willem Jiang > >> wrote: > >> > >> > I think we just need to find a home for > >> > https://github.com/ServiceComb/ServiceComb-Company-WorkShop > >> > > >> > huaweicse could be a way to go. > >> > > >> > > >> > Willem Jiang > >> > > >> > Twitter: willemjiang > >> > Weibo: 姜宁willem > >> > > >> > On Wed, Jul 25, 2018 at 4:25 PM, bismy wrote: > >> > > >> > > +1. > >> > > Does huawei has an organization to hosting these contents? Maybe > >we can > >> > > move them all there. And I have an organization to host temporary > >> > contents. > >> > > https://github.com/huaweicse > >> > > > >> > > > >> > > -- 原始邮件 -- > >> > > 发件人: "Zen Lin"; > >> > > 发送时间: 2018年7月25日(星期三) 下午4:13 > >> > > 收件人: "dev"; > >> > > 抄送: "Xiaoliang Tian"; > >> > > 主题: 【Proposal】Close ServiceComb group on github > >> > > > >> > > > >> > > > >> > > Hi Guys, > >> > > > >> > > As we known, Apache ServiceComb (incubating) is in the "Near > >> Graduation" > >> > > status. > >> > > There still a ServiceComb group on the github [1], projects under > >this > >> > > group is not in the incubator scope of ServiceComb now, my > >suggestion > >> is > >> > to > >> > > close this group. > >> > > > >> > > I have gone though the projects and find out the corresponding > >> > maintainers > >> > > , please transfer the project to other place but not ServiceComb, > > as > >> > > follows, > >> > > > >> > > Maintainer: Shawn > >> > > https://github.com/ServiceComb/go-chassis > >> > > > >> > > https://github.com/ServiceComb/cse-collector > >> > > > >> > > https://github.com/ServiceComb/go-cc-client > >> > > > >> > > https://github.com/ServiceComb/go-archaius > >> > > > >> > > https://github.com/ServiceComb/go-sc-client > >> > > > >> > > https://github.com/ServiceComb/paas-lager > >> > > > >> > > https://github.com/ServiceComb/http-client > >> > > > >> > > https://github.com/ServiceComb/auth > >> > > > >> > > Maintainer: Willem > >> > > https://github.com/ServiceComb/spring-cloud-servicecomb-plugins > >> > > > >> > > https://github.com/ServiceComb/seckill > >> > > > >> > > https://github.com/ServiceComb/incubator-servicecomb-website > >> > > > >> > > Maintainer: Asif > >> > > > >https://github.com/ServiceComb/incubator-servicecomb-service-center > >> > > > >> > > To the project below, it is a official demo of servicecomb, I am > >not > >> sure > >> > > how to deal with this, any thoughts? > >> > > https://github.com/ServiceComb/ServiceComb-Company-WorkShop > >> > > > >> > > > >> > > [1] https://github.com/ServiceComb > ><https://github.com/ServiceComb> > >> > > > >> > > Best Regards, > >> > > --- > >> > > Zen Lin > >> > > zenlintechnofr...@gmail.com > >> > > Focused on Micro Service and Apache ServiceComb > >> > > > >> > > >> > >> > >> -- > >> Best Regards, > >> Yang. > >> >
Re: 【Proposal】Close ServiceComb group on github
Yeah, Got what you mean. My question is if we sure we will have more servicecomb demo in future, could we have a place in Apache to keep these Demos? But not anything about huaweixxx. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Willem Jiang 于2018年7月25日周三 下午4:45写道： > I think we just need to find a home for > https://github.com/ServiceComb/ServiceComb-Company-WorkShop > > huaweicse could be a way to go. > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Wed, Jul 25, 2018 at 4:25 PM, bismy wrote: > > > +1. > > Does huawei has an organization to hosting these contents? Maybe we can > > move them all there. And I have an organization to host temporary > contents. > > https://github.com/huaweicse > > > > > > -- 原始邮件 -- > > 发件人: "Zen Lin"; > > 发送时间: 2018年7月25日(星期三) 下午4:13 > > 收件人: "dev"; > > 抄送: "Xiaoliang Tian"; > > 主题: 【Proposal】Close ServiceComb group on github > > > > > > > > Hi Guys, > > > > As we known, Apache ServiceComb (incubating) is in the "Near Graduation" > > status. > > There still a ServiceComb group on the github [1], projects under this > > group is not in the incubator scope of ServiceComb now, my suggestion is > to > > close this group. > > > > I have gone though the projects and find out the corresponding > maintainers > > , please transfer the project to other place but not ServiceComb, as > > follows, > > > > Maintainer: Shawn > > https://github.com/ServiceComb/go-chassis > > > > https://github.com/ServiceComb/cse-collector > > > > https://github.com/ServiceComb/go-cc-client > > > > https://github.com/ServiceComb/go-archaius > > > > https://github.com/ServiceComb/go-sc-client > > > > https://github.com/ServiceComb/paas-lager > > > > https://github.com/ServiceComb/http-client > > > > https://github.com/ServiceComb/auth > > > > Maintainer: Willem > > https://github.com/ServiceComb/spring-cloud-servicecomb-plugins > > > > https://github.com/ServiceComb/seckill > > > > https://github.com/ServiceComb/incubator-servicecomb-website > > > > Maintainer: Asif > > https://github.com/ServiceComb/incubator-servicecomb-service-center > > > > To the project below, it is a official demo of servicecomb, I am not sure > > how to deal with this, any thoughts? > > https://github.com/ServiceComb/ServiceComb-Company-WorkShop > > > > > > [1] https://github.com/ServiceComb <https://github.com/ServiceComb> > > > > Best Regards, > > --- > > Zen Lin > > zenlintechnofr...@gmail.com > > Focused on Micro Service and Apache ServiceComb > > >
Re: 【Proposal】Close ServiceComb group on github
It is a nice choice, But I think it is free for the maintainers to transfer the projects to anywhere, that is not the scope of ServiceComb. To the community, we only demand the maintainers to transfer out there projects. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb bismy 于2018年7月25日周三 下午4:31写道： > +1. > Does huawei has an organization to hosting these contents? Maybe we can > move them all there. And I have an organization to host temporary contents. > https://github.com/huaweicse > > > -- 原始邮件 ---------- > 发件人: "Zen Lin"; > 发送时间: 2018年7月25日(星期三) 下午4:13 > 收件人: "dev"; > 抄送: "Xiaoliang Tian"; > 主题: 【Proposal】Close ServiceComb group on github > > > > Hi Guys, > > As we known, Apache ServiceComb (incubating) is in the "Near Graduation" > status. > There still a ServiceComb group on the github [1], projects under this > group is not in the incubator scope of ServiceComb now, my suggestion is to > close this group. > > I have gone though the projects and find out the corresponding maintainers > , please transfer the project to other place but not ServiceComb, as > follows, > > Maintainer: Shawn > https://github.com/ServiceComb/go-chassis > > https://github.com/ServiceComb/cse-collector > > https://github.com/ServiceComb/go-cc-client > > https://github.com/ServiceComb/go-archaius > > https://github.com/ServiceComb/go-sc-client > > https://github.com/ServiceComb/paas-lager > > https://github.com/ServiceComb/http-client > > https://github.com/ServiceComb/auth > > Maintainer: Willem > https://github.com/ServiceComb/spring-cloud-servicecomb-plugins > > https://github.com/ServiceComb/seckill > > https://github.com/ServiceComb/incubator-servicecomb-website > > Maintainer: Asif > https://github.com/ServiceComb/incubator-servicecomb-service-center > > To the project below, it is a official demo of servicecomb, I am not sure > how to deal with this, any thoughts? > https://github.com/ServiceComb/ServiceComb-Company-WorkShop > > > [1] https://github.com/ServiceComb <https://github.com/ServiceComb> > > Best Regards, > --- > Zen Lin > zenlintechnofr...@gmail.com > Focused on Micro Service and Apache ServiceComb
【Proposal】Close ServiceComb group on github
Hi Guys, As we known, Apache ServiceComb (incubating) is in the "Near Graduation" status. There still a ServiceComb group on the github [1], projects under this group is not in the incubator scope of ServiceComb now, my suggestion is to close this group. I have gone though the projects and find out the corresponding maintainers , please transfer the project to other place but not ServiceComb, as follows, Maintainer: Shawn https://github.com/ServiceComb/go-chassis https://github.com/ServiceComb/cse-collector https://github.com/ServiceComb/go-cc-client https://github.com/ServiceComb/go-archaius https://github.com/ServiceComb/go-sc-client https://github.com/ServiceComb/paas-lager https://github.com/ServiceComb/http-client https://github.com/ServiceComb/auth Maintainer: Willem https://github.com/ServiceComb/spring-cloud-servicecomb-plugins https://github.com/ServiceComb/seckill https://github.com/ServiceComb/incubator-servicecomb-website Maintainer: Asif https://github.com/ServiceComb/incubator-servicecomb-service-center To the project below, it is a official demo of servicecomb, I am not sure how to deal with this, any thoughts? https://github.com/ServiceComb/ServiceComb-Company-WorkShop [1] https://github.com/ServiceComb <https://github.com/ServiceComb> Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb
Re: [ANN] New ServiceComb committer: Feng Zheng (冯征)
Congratulations, our community are developing healthy. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Jean-Baptiste Onofré 于2018年7月24日周二 上午12:10写道： > Welcome aboard ! > > Regards > JB > > Le 23 juil. 2018 à 16:16, à 16:16, Willem Jiang > a écrit: > >Please join me and the rest of the ServiceComb PPMC members in > >welcoming our > >new ServiceComb committer: Feng Zheng (冯征). > > > >Feng Zheng contribute the ServiceComb since this Jan, he is active > >contributor on saga and the mailing list, and we look forward to many > >more > >contributions in the future. > > > >Congratulations to Feng Zheng ! Welcome! > > > >Willem Jiang > > > >Twitter: willemjiang > >Weibo: 姜宁willem >
Re: Discussion about java chassis roadmap
I am sorry I can not get the information about which version will fix these issues. Shall we fix all these epic issues in release 1.0.0, or other later release. Or we will break these epic issues into smaller one ,and then mark which part of the issues will be fixed in release 1.0.0? Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb wjm wjm 于2018年7月23日周一 上午8:45写道： > adjust roadmap, remove SCB-759, add SCB-770: > > [SCB-748 <https://issues.apache.org/jira/browse/SCB-748>] ServiceComb > engine resource optimize > [SCB-756 <https://issues.apache.org/jira/browse/SCB-756>] improve > development phase flexibility > > [SCB-719 <https://issues.apache.org/jira/browse/SCB-719>] automated > integration testing support complex processes > > [SCB-757 <https://issues.apache.org/jira/browse/SCB-757>] provide common > governance match mechanism > > [SCB-749 <https://issues.apache.org/jira/browse/SCB-749>] mybatis for > reactive mode > [SCB-758 <https://issues.apache.org/jira/browse/SCB-758>] extract core > engine not depend on springremove > > [SCB-770 <https://issues.apache.org/jira/browse/SCB-770>] invoke 3rd > RESTful service > > 2018-07-20 11:21 GMT+08:00 bismy : > > > Agree with this order. And SCB-748 SCB-756 is related, should take most > > priority. > > > > > > > > > > -- 原始邮件 -- > > 发件人: "wjm wjm"; > > 发送时间: 2018年7月19日(星期四) 下午4:29 > > 收件人: "dev"; > > > > 主题: Re: Discussion about java chassis roadmap > > > > > > > > Sort by importance: > > > > [SCB-748 <https://issues.apache.org/jira/browse/SCB-748>] ServiceComb > > engine resource optimize > > [SCB-756 <https://issues.apache.org/jira/browse/SCB-756>] improve > > development phase flexibility > > > > [SCB-719 <https://issues.apache.org/jira/browse/SCB-719>] automated > > integration testing support complex processes > > > > [SCB-757 <https://issues.apache.org/jira/browse/SCB-757>] provide common > > governance match mechanism > > > > [SCB-749 <https://issues.apache.org/jira/browse/SCB-749>] mybatis for > > reactive mode > > [SCB-758 <https://issues.apache.org/jira/browse/SCB-758>] extract core > > engine not depend on spring > > > > 2018-07-19 16:20 GMT+08:00 wjm wjm : > > > > > infact all of them are very very big task > > > once we decided to start them, we must create subtasks. > > > > > > now, we just need to decide what tasks will be start? > > > > > > 2018-07-19 15:44 GMT+08:00 Willem Jiang : > > > > > >> Yeah, as we are heading to ServiceComb 1.0.0. It's the time for us to > > make > > >> some plan for the new release. > > >> Jimin, I think 719 and 758 are very big task, I think we may need to > > >> create some small tasks to break down them a bit. > > >> > > >> > > >> Willem Jiang > > >> > > >> Twitter: willemjiang > > >> Weibo: 姜宁willem > > >> > > >> On Thu, Jul 19, 2018 at 10:34 AM, wjm wjm wrote: > > >> > > >> > we need to plan roadmap for the next stage > > >> > i create below issues to trace what i think is important. > > >> > please feel free to add your opinions/new isses/ and so on > > >> > > > >> > [SCB-719 <https://issues.apache.org/jira/browse/SCB-719>] automated > > >> > integration testing support complex processes > > >> > > > >> > > > >> > [SCB-748 <https://issues.apache.org/jira/browse/SCB-748>] > ServiceComb > > >> > engine resource optimize > > >> > > > >> > [SCB-756 <https://issues.apache.org/jira/browse/SCB-756>] improve > > >> > development phase flexibility > > >> > > > >> > [SCB-757 <https://issues.apache.org/jira/browse/SCB-757>] provide > > >> common > > >> > governance match mechanism > > >> > > > >> > [SCB-749 <https://issues.apache.org/jira/browse/SCB-749>] mybatis > for > > >> > reactive mode > > >> > > > >> > [SCB-758 <https://issues.apache.org/jira/browse/SCB-758>] extract > > core > > >> > engine not depend on spring > > >> > > > >> > > > > > > > > >
Re: Re: [DISCUSS]Shall we upgrade Java-chassis to support Spring Boot2
+1 to Willem's suggestion. Could someone ask yaohaishi to create a issue track for this, upgrade to support Spring Boot2. And when he find an actual issue on testing it, can create a sub issue under the issue of "upgrade to support Spring Boot2". Thus, Mabin and the users can know the detail progress or report what issue they meet through the issue. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Willem Jiang 于2018年7月20日周五 下午4:40写道： > SCB-758 is a big task. I don't think we need to wait for it done to > support Spring Boot 2.x. > Yaohaishi already did some test on it, we just need to keep fix the actual > issue we find > > my suggestion is we support Spring Boot 1.x by default, and add a Spring > Boot 2.x profile to the user who want to use Spring Boot 2.x. > > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Fri, Jul 20, 2018 at 4:25 PM, Bin Ma wrote: > > > Currently I have recommended user like Chuanzhi Boke to develop based on > > the spring boot1.x version to ensure that user development is not > blocked. > > > > I agree with bimsy's idea,users' demands and scenes are clear,an task > > should be created to trace. > > > > As I know, SCB-758(https://issues.apache.org/jira/browse/SCB-758) is a > > task > > to remove the dependency of java-chassis on spring, I'm not sure if this > > task is completed first, and it is more helpful to support the > springboot2 > > ? > > > > 2018-07-20 11:24 GMT+08:00 Willem Jiang : > > > > > From the Spring Boot2 migration guide[1], the class package and name > was > > > changed. > > > > > > We may need to create different module to handle the class package > change > > > issue. > > > > > > [1] > > > https://github.com/spring-projects/spring-boot/wiki/ > > > Spring-Boot-2.0-Migration-Guide#embedded-containers-package-structure > > > > > > > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Fri, Jul 20, 2018 at 10:29 AM, yhs0092 wrote: > > > > > > > I tried to upgrade Java-Chassis to support SpringBoot2 before, but > > > failed. > > > > > > > > > > > > There are two problems. The first one is in our bean.xml file， the > xsd > > > > file is imported like below: > > > > ``` > > > > classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd > > > > ``` > > > > but 3.0 version xsd file does not exist anymore. > > > > > > > > This is still resolvable, but for the second problem, I still haven't > > > > found a way to resolve it. > > > > > > > > > > > > When my service demo is started, an error occurs: > > > > ``` > > > > 2018-03-13 22:57:18.396 WARN 6 --- [ main] > > > > ConfigServletWebServerApplicationContext : Exception encountered > > during > > > > context initialization - cancelling refresh attempt: > > > > org.springframework.beans.factory.BeanDefinitionStoreException: > Failed > > > to > > > > parse configuration class [org.apache.servicecomb. > > > > springboot.starter.transport.RestServletInitializer]; nested > exception > > > is > > > > java.io.FileNotFoundException: class path resource > > > > [org/springframework/boot/context/embedded/ > > > AbstractConfigurableEmbeddedServletContainer.class] > > > > cannot be opened because it does not exist > > > > ``` > > > > Because AbstractConfigurableEmbeddedServletContainer is removed in > > > > SpringBoot2, and our RestServletInitializer is extended from this > > class, > > > > maybe we cannot upgrade to SpringBoot2 by simply change the maven > > > > dependency. > > > > And once we refactor our RestServletInitializer, the java-chassis may > > not > > > > be compatible with SpringBoot1. > > > > > > > > > > > > > > > > 在 2018-07-20 08:57:05，"wjm wjm" 写道： > > > > >not enough, must exclude old spring also > > > > > > > > > >2018-07-20 6:44 GMT+08:00 Willem Jiang : > > > > > > > > > >> How about let user override the version of Spring Boot in their > > > > application > > > > >> and give it a try. > > > > >> Just like what we do with
Re: [DISCUSS]Simplify Dynamic Config (Apollo) Integration Test in Java Chassis
+1 to using this way to reduce load of integration testing. But I am also interested in what Yangbo mentioned, "apollo is too complex a system for our use case". My doubt is is there any way to reduce this complex, any user guide blog for it? Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb YangYongZheng <342906...@qq.com> 于2018年7月18日周三 上午11:24写道： > Yes, we only need test integration mechanism, not Apollo itself > > > Best Regards! > YangYongZheng > > > -邮件原件- > 发件人: Yang Bo [mailto:oaky...@gmail.com] > 发送时间: 2018年7月18日 11:13 > 收件人: dev@servicecomb.apache.org > 主题: Re: [DISCUSS]Simplify Dynamic Config (Apollo) Integration Test in Java > Chassis > > For the purpose of testing this is OK. But the real problem here is that > apollo is too complex a system for our use case. > > > On Wed, Jul 18, 2018 at 11:01 AM 郑扬勇 wrote: > > > Hi all： > >We had integration with Apollo for support dynamic config in Java > > Chassis, our CI will pull up apollo docker containers for test > > (nobodyiam/apollo-quick-start and lijasonvip/apollodb), this step is > > very slow and easy failed. > >I found that we are only use apollo openapi ( > > https://github.com/ctripcorp/apollo/wiki/Apollo%E5%BC%80%E6%94%BE%E5%B > > 9%B3%E5%8F%B0) to get configurations from it, code below : > > > > private static RestTemplate rest = new RestTemplate(); > > ResponseEntity exchange = rest.exchange(composeAPI(), > > HttpMethod.GET, entity, String.class); > > > > It is a general http GET request, so I think we only need start up a > > http server and direct return a default configuration content for this > > url in order to simulate the apollo server, that is enough. > > > >Any thoughts? > > > > Best Regards & Thanks! > > Yangyong Zheng > > > > -- > Best Regards, > Yang. > > > >
Re: [DISCUSS] Service-Center Docker images version numbering
+1 Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb wjm wjm 于2018年7月18日周三 上午10:18写道： > +1 > > 2018-07-18 10:05 GMT+08:00 Yang Bo : > > > +1 for this. And I also suggest to run both the service-center and > frontend > > in the docker image. > > > > On Tue, Jul 17, 2018 at 9:25 PM Mohammad Asif Siddiqui < > > asifdxtr...@apache.org> wrote: > > > > > Hi All, > > > > > > There was an issue raised in github[1] of service-center regarding the > > > images of SC in docker hub for which we need your feedback. > > > > > > Problem : Currently there are no docker images of service-center which > > > reflects the current state of the service-center. We only make docker > > > images when we cut new version and also update the "latest" tag at that > > > time. If someone(like Java-Chassis and Saga CI) wants to test their > > changes > > > with the latest Service-Center then they have to either wait for a new > > > version to be released or make there own docker image which might be > > > sometimes difficult. > > > > > > Solution : For every successful merge to Service-Center the CI will > make > > a > > > new docker image and push it to Dockerhub with the "latest" tag. > > Whenever a > > > new version is cut then we will make a new tag with the version number. > > So > > > the Service-Center tags will look like: > > > "latest" : Always represents the latest state of the Service-Center in > > > github repo. > > > "VersionNumer"(like 1.0.0) : This will be created whenever a new > version > > is > > > released. > > > > > > CI's which are using the SC docker hub images can always use the latest > > tag > > > for their test as well as recent versions of the service-center to > check > > > backward compatibility. > > > > > > Since Java-Chassis and Saga CI's uses these SC docker images very > > > frequently in their test so we want to know the opinion on this from > > > maintainers of Java-Chassis and Saga. > > > > > > [1] > > > https://github.com/apache/incubator-servicecomb-service- > > center/issues/277 > > > > > > Regards > > > Asif > > > > > > > > > -- > > Best Regards, > > Yang. > > >
Re: [DISCUSS] Proposal for Re-Design of Service-Center Frontend
+1 Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Willem Jiang 于2018年7月17日周二 下午3:33写道： > I cannot agree with you more about it. > We need to avoid this kind of situation in our further development. > Before we start writing the code, it's quite important that we need to send > a heads up or proposal to let others know about it. > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Tue, Jul 17, 2018 at 3:22 PM, wjm wjm wrote: > > > ok > > > > but i think it's better raise proposal before start work on it. > > > > 2018-07-17 15:04 GMT+08:00 Willem Jiang : > > > > > It‘s no harm if the development is down. We just need to get more feed > > > back from the community and consider to merge the UI to the new UI. > > > For the UI, there are some License stuff of java script library we need > > to > > > care about. We may need to address this issue before CSE UI is open > > > sourced. > > > > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Tue, Jul 17, 2018 at 1:36 PM, Mohammad Asif Siddiqui < > > > asifdxtr...@apache.org> wrote: > > > > > > > Hi Guyz, > > > > > > > > The development of these design was already done before and that's > the > > > > reason we were able to show the snapshots of the new UI. The code is > > > ready > > > > to be merged but before merging we decided to come here and discuss > > about > > > > this UI for people opinion. Since most of the people are concerned > > about > > > > the effort needed to re-design this UI, so I would like to tell that > > > > development is already done. > > > > > > > > So in my opinion we can merge this change to make the UI better and > > > > whenever ServiceComb-UI gets opensourced then we can plan to merge > some > > > of > > > > these designs to the ServiceComb-UI. > > > > > > > > Any thoughts? > > > > > > > > Regrds > > > > Asif > > > > > > > > On 2018/07/16 10:57:00, Zen Lin wrote: > > > > > Hi all, > > > > > As we known, CSE is a initial commercial product of servicecomb > and > > we > > > > > have tried our best to ask CSE to open source ServiceComb-UI to > > > stronger > > > > > servicecomb and let servicecomb service users better. > > > > > But I think the discuss should focused on what's difference > between > > > > > servicecenter UI positioning and servicecomb UI positioning. > > > > > > > > > > If we sure the functionality of servicecenter UI is a subset of of > > > > > servicecomb UI which will be opensourceed future, and Asif have > > willing > > > > to > > > > > keep on developing and maintaining a servicenter UI, will will have > > two > > > > UI > > > > > in future, I think that is allowed with a opensource project also. > > > > > > > > > > Therefore, to my opinion, I think we can focused on discussing > > > > > servicecenter-UI's position, something like, what functionality for > > > > > service-center UI is reasonable? > > > > > > > > > > > > > > > Best Regards, > > > > > --- > > > > > Zen Lin > > > > > zenlintechnofr...@gmail.com > > > > > Focused on Micro Service and Apache ServiceComb > > > > > > > > > > > > > > > wjm wjm 于2018年7月16日周一 下午12:43写道： > > > > > > > > > > > maybe we can change our mind to: make sure new feathers all in > > > > > > ServiceComb-UI, not design a new one. > > > > > > > > > > > > 2018-07-16 12:41 GMT+08:00 wjm wjm : > > > > > > > > > > > > > as i said that, Proposal of new SC frontend seems to be a > subset > > of > > > > > > > ServiceComb-UI > > > > > > > if that's true, i think we no need to spend time to do one > thing > > > > with two > > > > > > > way. > > > > > > > > > > > > > > 2018-07-16 11:58 GMT+08:00 Mohammad Asif Siddiqui < > > > > > > asifdxtr...@apache.org> > > > > > > > : > >
Re: [DISCUSS] Proposal for Re-Design of Service-Center Frontend
+1, to my opinion, agree with Asif. And @Asif, do you mean all of the features you mentioned here can be concluded in release 1.0.0? As we known , Version 1.0.0 will be released in this end of month. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Mohammad Asif Siddiqui 于2018年7月17日周二 下午1:36写道： > Hi Guyz, > > The development of these design was already done before and that's the > reason we were able to show the snapshots of the new UI. The code is ready > to be merged but before merging we decided to come here and discuss about > this UI for people opinion. Since most of the people are concerned about > the effort needed to re-design this UI, so I would like to tell that > development is already done. > > So in my opinion we can merge this change to make the UI better and > whenever ServiceComb-UI gets opensourced then we can plan to merge some of > these designs to the ServiceComb-UI. > > Any thoughts? > > Regrds > Asif > > On 2018/07/16 10:57:00, Zen Lin wrote: > > Hi all, > > As we known, CSE is a initial commercial product of servicecomb and we > > have tried our best to ask CSE to open source ServiceComb-UI to stronger > > servicecomb and let servicecomb service users better. > > But I think the discuss should focused on what's difference between > > servicecenter UI positioning and servicecomb UI positioning. > > > > If we sure the functionality of servicecenter UI is a subset of of > > servicecomb UI which will be opensourceed future, and Asif have willing > to > > keep on developing and maintaining a servicenter UI, will will have two > UI > > in future, I think that is allowed with a opensource project also. > > > > Therefore, to my opinion, I think we can focused on discussing > > servicecenter-UI's position, something like, what functionality for > > service-center UI is reasonable? > > > > > > Best Regards, > > --- > > Zen Lin > > zenlintechnofr...@gmail.com > > Focused on Micro Service and Apache ServiceComb > > > > > > wjm wjm 于2018年7月16日周一 下午12:43写道： > > > > > maybe we can change our mind to: make sure new feathers all in > > > ServiceComb-UI, not design a new one. > > > > > > 2018-07-16 12:41 GMT+08:00 wjm wjm : > > > > > > > as i said that, Proposal of new SC frontend seems to be a subset of > > > > ServiceComb-UI > > > > if that's true, i think we no need to spend time to do one thing > with two > > > > way. > > > > > > > > 2018-07-16 11:58 GMT+08:00 Mohammad Asif Siddiqui < > > > asifdxtr...@apache.org> > > > > : > > > > > > > >> Hi Sure, > > > >> > > > >> If this new ServiceComb-UI(as per your mail) is opensourced then > will > > > the > > > >> exsisting service-center frontend deprecated?, If NO then I still > > > believe > > > >> it's a good thought to upgrade the exsisting Service-Center > frontend. > > > >> > > > >> Regards > > > >> Asif > > > >> > > > >> On 2018/07/16 00:51:06, "Sure" wrote: > > > >> > -1 > > > >> > > > > >> > > > > >> > we will publish the cse-UI in servicecomb(named servicecomb-UI may > > > be), > > > >> this’s the unified console of sc,cc and monitoring. So we just need > to > > > cost > > > >> a little of time to fix bugs of SC-UI. > > > >> > > > > >> > > > > >> > The sericecomb-UI will be more valuable in the future > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > 发自我的iPhone > > > >> > > > > >> > -- Original -- > > > >> > From: Mohammad Asif Siddiqui > > > >> > Date: Fri,Jul 13,2018 7:55 PM > > > >> > To: dev > > > >> > Cc: krishna.m.kumar , sanil.kumar < > > > >> sanil.ku...@huawei.com>, vinaym > > > >> > Subject: Re: [DISCUSS] Proposal for Re-Design of Service-Center > > > Frontend > > > >> > > > > >> > > > > >> > > > > >> > Hi All, > > > >> > > > > >> > As we have continously put an effort to improve the > S
Re: [DISCUSS]Shall Java Chassis support random port
I think i got what wjm means "not safety", usually, we will add an disclaimer at the feature in this situation, something like, when setting port to 0, the port will be random assigned , the security-related matters introduced by this are the responsibility of the user. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb wjm wjm 于2018年7月13日周五 上午10:54写道： > for some production, they must provide communication matrix to final > customers before deploy software. > > but in this time they DO NOT use port 0 feature just no problem. > so it's a false proposition > but to debate this problem with those peoples will waste a lot of > time.. > > 2018-07-13 10:34 GMT+08:00 Willem Jiang : > > > The "not safety" explain doesn't make sense. > > With the help of service-center, we can find out the port finally. > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Fri, Jul 13, 2018 at 10:11 AM, wjm wjm wrote: > > > > > in fact, customer not set port to 0 means disable it, i don't think we > > need > > > a option. > > > > > > "not safety" means, if customer set port to 0, they can not know which > > port > > > will be used > > > sigh, so strange.. > > > > > > 2018-07-13 9:46 GMT+08:00 Willem Jiang : > > > > > > > Can we add an option for it? > > > > In this way we can disable it when there is security issue we need to > > > take > > > > care. > > > > > > > > > > > > Willem Jiang > > > > > > > > Twitter: willemjiang > > > > Weibo: 姜宁willem > > > > > > > > On Fri, Jul 13, 2018 at 9:34 AM, Kirin Wang > > > > > wrote: > > > > > > > > > +1 ， > > > > > I think is a good feature, > > > > > @wjm Could you provide more information about the safety issue? > > that > > > > is > > > > > a interesting topic. > > > > > > > > > > wjm wjm 于2018年7月13日周五 上午9:30写道： > > > > > > > > > > > +1 > > > > > > > > > > > > when cse project start, i implement this feature, but teams said > > that > > > > is > > > > > > not safe.. > > > > > > at last we delete the feature. > > > > > > > > > > > > 2018-07-13 9:23 GMT+08:00 郑扬勇 : > > > > > > > > > > > > > Hi: > > > > > > > Like spring-boot server.port=0, Java Chassis can support > random > > > > port: > > > > > > > > > > > > > > servicecomb: > > > > > > > rest: > > > > > > > address: 0.0.0.0:0 > > > > > > > highway: > > > > > > > address: 0.0.0.0:0 > > > > > > > > > > > > > > Best Regards & Thanks! > > > > > > > > > > > > > > > > > > > > >
Re: [DISCUSS] Heading to graduation
To the ServiceComb trademark, the donor counsel are contacting with trademark VP for transferring details, it looks good till now. Any progress, I will post here. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Jean-Baptiste Onofré 于2018年7月13日周五 下午4:16写道： > It sounds good ! > > In the mean time, I'm moving forward on the assessment document and > preparing the resolution. > > I will send an update during the weekend. > > Regards > JB > > On 13/07/2018 09:44, Willem Jiang wrote: > > Yeah, we are heading to TLP. > > > > Current we are planing release ServiceComb Service-Center 1.0.0, > > SerivceComb Java-Chassis 1.0.0 this month. > > The ServiceComb trademark transfer process looks good. > > And we make consensus decisions through the discussion - vote process. > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Sun, Jul 8, 2018 at 1:59 PM, Jean-Baptiste Onofré > > wrote: > > > >> Hi all, > >> > >> Last week, Willem and I had a long discussion about the status of the > >> ServiceComb podling. > >> > >> IMHO, we are almost ready for graduation. > >> > >> We worked on the maturity assessment doc: > >> > >> > https://cwiki.apache.org/confluence/display/SERVICECOMB/Apache+Maturity+ > >> Model+Assessment+for+ServiceComb > >> > >> So, it looks good to me, I'm doing a new pass on the assessment model > >> providing some details on some topics, but overall good. > >> > >> I wanted to have your inputs about that (heading to TLP). > >> > >> Thoughts ? > >> > >> Regards > >> JB > >> -- > >> Jean-Baptiste Onofré > >> jbono...@apache.org > >> http://blog.nanthrax.net > >> Talend - http://www.talend.com > >> > > > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com >
Re: An idea to manage both servicecomb & other frameworks' configs in an unified way
Agree with Willem, it sounds good to providing a user story to show a whole picture. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Willem Jiang 于2018年7月16日周一 上午10:20写道： > Hi, Lance, > > I think you provide a tool that can convert the old ServiceComb > configuration into Istio related setting files, am I right? > > It could save some time of user if they want to migrate to Istio. But I'd > like to see a user story to show us a whole picture. > You can take a look at this[1] as an example. > > [1] > > https://developer.okta.com/blog/2018/07/11/ci-cd-spring-boot-jenkins-x-kubernetes > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Fri, Jul 13, 2018 at 3:44 PM, Lance Ju wrote: > > > Hi, gang! > > > > I'm thinking about handling configs of both ServiceComb and other > > frameworks(like Istio), then provide a unified solution for config > > management, to support the hybrid solution scenario(like, user use > > ServiceComb and Istio at the same time). > > > > So the first thing to do is to make sure that the chassis configs > have > > an equivalent mapping of other frameworks. Currently, I'm testing the > rate > > limit configs between ServiceComb and Istio, it's working. I write a demo > > about this at https://github.com/crystaldust/configcomb, receive a > > chassis.yaml, read the Flowcontrol field, then convert it to Istio rate > > limit rules and apply the rules in a kubernetes cluster. It should also > > work the opposite way. > > > > By doing so, it is possible to provide a unified solution for config > > management, any ideas? > > >
Re: [DISCUSS] Proposal for Re-Design of Service-Center Frontend
Hi all, As we known, CSE is a initial commercial product of servicecomb and we have tried our best to ask CSE to open source ServiceComb-UI to stronger servicecomb and let servicecomb service users better. But I think the discuss should focused on what's difference between servicecenter UI positioning and servicecomb UI positioning. If we sure the functionality of servicecenter UI is a subset of of servicecomb UI which will be opensourceed future, and Asif have willing to keep on developing and maintaining a servicenter UI, will will have two UI in future, I think that is allowed with a opensource project also. Therefore, to my opinion, I think we can focused on discussing servicecenter-UI's position, something like, what functionality for service-center UI is reasonable? Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb wjm wjm 于2018年7月16日周一 下午12:43写道： > maybe we can change our mind to: make sure new feathers all in > ServiceComb-UI, not design a new one. > > 2018-07-16 12:41 GMT+08:00 wjm wjm : > > > as i said that, Proposal of new SC frontend seems to be a subset of > > ServiceComb-UI > > if that's true, i think we no need to spend time to do one thing with two > > way. > > > > 2018-07-16 11:58 GMT+08:00 Mohammad Asif Siddiqui < > asifdxtr...@apache.org> > > : > > > >> Hi Sure, > >> > >> If this new ServiceComb-UI(as per your mail) is opensourced then will > the > >> exsisting service-center frontend deprecated?, If NO then I still > believe > >> it's a good thought to upgrade the exsisting Service-Center frontend. > >> > >> Regards > >> Asif > >> > >> On 2018/07/16 00:51:06, "Sure" wrote: > >> > -1 > >> > > >> > > >> > we will publish the cse-UI in servicecomb(named servicecomb-UI may > be), > >> this’s the unified console of sc,cc and monitoring. So we just need to > cost > >> a little of time to fix bugs of SC-UI. > >> > > >> > > >> > The sericecomb-UI will be more valuable in the future > >> > > >> > > >> > > >> > > >> > > >> > > >> > 发自我的iPhone > >> > > >> > -- Original -- > >> > From: Mohammad Asif Siddiqui > >> > Date: Fri,Jul 13,2018 7:55 PM > >> > To: dev > >> > Cc: krishna.m.kumar , sanil.kumar < > >> sanil.ku...@huawei.com>, vinaym > >> > Subject: Re: [DISCUSS] Proposal for Re-Design of Service-Center > Frontend > >> > > >> > > >> > > >> > Hi All, > >> > > >> > As we have continously put an effort to improve the Service-Center UI > to > >> > make it more usable and user friendly, going forwards I would like to > >> > propose some major changes in the Design of frontend. Some of those > >> changes > >> > will include : > >> > > >> > 1. Update Dashboard to have a more better snapshot of what > >> > entities/resources are present in the Service-Center env. > >> > 2. A place holder in Dashboard to contain the basic User Guide/FAQ for > >> > ServiceComb. > >> > 3. Add a new page for showing the list of instances which are > currently > >> > running and registered in service-center. > >> > 4. Add a new page for showing the topology of Microservices, this page > >> will > >> > describe the relationship between the different microservices and some > >> > metadata of the microservices. > >> > 5. Advanced search criteria for Service and Instance List. > >> > > >> > Here is the Snapshot[1] of the changes we are planning to do. > >> > > >> > Most of the features development have been completed and we are > >> planning to > >> > put this change in the 1.0.0 release of Service-Center. > >> > > >> > Any thought on this? > >> > > >> > [1] > >> > https://github.com/apache/incubator-servicecomb-service-cent > >> er/wiki/Service-Center-UI-Re-design > >> > > >> > Regards > >> > Asif > >> > > > > >
Re: [DISCUSS] about integration test
ServiceComb is an open source project that has been adopted for a variety of commercial scenarios. As wrote in the report, at least more than 10 users have used ServiceComb for commercial use. Therefore, our integration testing will be more and more comprehensive and huge, it is a good idea to resolve this problem, but directly separating the inheritance test to the independent project will cause some problems: 1. This is contrary to the ordinary practice of open source projects, causing the unconsistent experience for our developers. 2. When the developers commmit, they will need to commit to both projects, which will affect the uniform traceability of the test code and function code. 3. The results of the integration test will lag, which will have an impact on the community's timely feedback when submitting the function code. So my suggestion is whether it can be compromised: Select out the time-consuming parts of the integration test and then reduce the run cycle, but don't strip it into separate branches. Any other thoughts? Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb wjm wjm 于2018年7月10日周二 上午9:41写道： > currently we embed integration test with PR CI > > but: > 1.we will add more and more integration test case > 2.test time will be more and more longer > 3.integration test should include work with multiple SC versions > 4... > > so, maybe it's better that make integration test to be a independent > project, and run it once a day at least > > some other idea of integration test: > https://issues.apache.org/jira/browse/SCB-719 > > what's your suggestion? >
[DISCUSS] Detail design for linking servicecomb-java-chassis-doc to users of website.
As Liubao have renew a user docs in https://huaweicse.github.io/servicecomb-java-chassis-doc/. My suggestion is to replace the user part of website to this docs, details are: 1. Create several items in http://servicecomb.incubator.apache.org/users/ , each item corresponds to a project, such as java-chassis, saga, servicecenter 2. Change https://huaweicse.github.io/servicecomb-java-chassis-doc/ to https://servicecomb.incubator.apache,org/servicecomb-java-chassis-doc/ <https://huaweicse.github.io/servicecomb-java-chassis-doc/> 3. link https://servicecomb.incubator.apache,org/servicecomb-java-chassis-doc/ <https://huaweicse.github.io/servicecomb-java-chassis-doc/> to the Java-chassis item under http://servicecomb.incubator.apache.org/users/ If we do it like this way , we also should change user docs of the saga and servicecenter to gitbook to keep the user experience consistent. By the way, I also create a JIRA issue [1] to track this. Any thoughts please feel free to discuss here. [1] https://issues.apache.org/jira/browse/SCB-721 Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb
Re: Podling Report Reminder - July 2018
Hi JB, Willem, I just gone through our report, but found there are even no any place mentioned our contributing of the website but other project's report conclude the website part. As we known, website is the most important part of our community projects, so could we add our contributes of website to the community report? Maybe something like, How has the project developed since the last report? (2018-04) * Java Chassis merged with 102 PRs by 16 contributors. * Service Center merged with 58 PRs by 6 contributors . * Saga merged with 48 PRs by 14 contributors. * * Website http://servicecomb.incubator.apache.org/ <http://servicecomb.incubator.apache.org/> merged with xx PRs by xx contributors. * * 70 mails send by 19 people on the dev@ list (2018-04) * 156 mails sent by 17 people on the dev@ list （2018-05） * 97 mails send by 23 people on the dev@ list (2018-06) Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Zen Lin 于2018年7月5日周四 下午5:25写道： > Hi, > Some guys have have shared ServiceComb in some opensource activities, I > am not sure whether these could be suitable to as a part of report? as > follows, > > How has the community developed since the last report?(2018-04) > * The community get the second release out: > service-center 1.0.0-m2, java-chassis 1.0.0-m2 and saga 0.2.0 > * The community hold a meetup in Beijing at Jun 27. > > http://servicecomb.incubator.apache.org/docs/apache-servicecomb-incubating-day-report/ > > * * Shared ServiceComb in several opensource activities,* > *Shared topic "ServiceComb Introduction" in SpringCloud China > Community Salon by Yangbo at April 21. > https://mp.weixin.qq.com/s/Zd-ab37Gu6GG0LwgHc_0OQ > <https://mp.weixin.qq.com/s/Zd-ab37Gu6GG0LwgHc_0OQ>* > *Shared topic "practice of Saga" in Qcon 2018 conference By Willem at > April 22. https://mp.weixin.qq.com/s/HfLvNvbnE8DrM3n-DXgRQQ > <https://mp.weixin.qq.com/s/HfLvNvbnE8DrM3n-DXgRQQ>* > *Shared Topic "ServiceComb in Devops" in OSC microservices Meetup by > Yangbo at May 27. > https://www.oschina.net/question/3799215_2280790?from=timeline > <https://www.oschina.net/question/3799215_2280790?from=timeline>* > > * There are about 6 departments of Huawei are using ServiceComb and > other 8 companies are using ServiceComb. > > Best Regards, > --- > Zen Lin > zenlintechnofr...@gmail.com > Focused on Micro Service and Apache ServiceComb > > > Willem Jiang 于2018年7月4日周三 下午10:30写道： > >> Hi JB. >> >> Thanks for pointing that out. I just updated the status to "near >> graduation" >> >> >> >> Willem Jiang >> >> Twitter: willemjiang >> Weibo: 姜宁willem >> >> On Mon, Jul 2, 2018 at 4:15 PM, Jean-Baptiste Onofré >> wrote: >> >> > Hi >> > >> > Thanks for the update. I think we can update the status to "near >> > graduation". >> > >> > I'm planning to work today and tomorrow on a plan and resolution to move >> > forward on graduation. >> > >> > Regards >> > JB >> > >> > Le 2 juil. 2018 à 10:10, à 10:10, Willem Jiang >> a >> > écrit: >> > >Hi Team >> > > >> > >I just update the project report like this , please review it and feel >> > >free >> > >to add what I'm missing. >> > >We may need to add a report link for the workshop which we hold last >> > >week. >> > > >> > >BTW, we get more and more contributors to the projects, which is good >> > >sign >> > >to see. Please keep up this good work. >> > > >> > > >> > >ServiceComb has been incubating since 2017-11-22. >> > > >> > >Three most important issues to address in the move towards graduation: >> > > >> > > 1. Community building >> > > 2. Project visibility >> > > 3. Trademark transfer >> > > >> > >Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >> > >aware of? >> > > >> > > NO >> > > >> > >How has the community developed since the last report?(2018-04) >> > > * The community get the second release out, service-center 1.0.0-m2, >> > >java-chassis 1.0.0-m2 and saga 0.2.0 >> > > * The community hold a day workshop in Beijing at Jun 27. >> > > >> > >How has the project developed since the last report? (2018-04) >> > > * Java Chassis merged with 102 PRs by 16 contributors. >&g
Suggest to share your CFP of KubeCon -CloudNativeCon China 2018 in dev@servicecomb
Hi guys, As I known , some guys are wish to help sharing servicecomb within Cloud native field in KubeCon -CloudNativeCon China 2018, and parts of you have submitted a proposal. It is so nice of you guys to help community and cloud native promotion. I suggest to out put you abstract of proposal here, to let the community and PPMCs know. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb
Re: Podling Report Reminder - July 2018
Hi, Some guys have have shared ServiceComb in some opensource activities, I am not sure whether these could be suitable to as a part of report? as follows, How has the community developed since the last report?(2018-04) * The community get the second release out: service-center 1.0.0-m2, java-chassis 1.0.0-m2 and saga 0.2.0 * The community hold a meetup in Beijing at Jun 27. http://servicecomb.incubator.apache.org/docs/apache-servicecomb-incubating-day-report/ * * Shared ServiceComb in several opensource activities,* *Shared topic "ServiceComb Introduction" in SpringCloud China Community Salon by Yangbo at April 21. https://mp.weixin.qq.com/s/Zd-ab37Gu6GG0LwgHc_0OQ <https://mp.weixin.qq.com/s/Zd-ab37Gu6GG0LwgHc_0OQ>* *Shared topic "practice of Saga" in Qcon 2018 conference By Willem at April 22. https://mp.weixin.qq.com/s/HfLvNvbnE8DrM3n-DXgRQQ <https://mp.weixin.qq.com/s/HfLvNvbnE8DrM3n-DXgRQQ>* *Shared Topic "ServiceComb in Devops" in OSC microservices Meetup by Yangbo at May 27. https://www.oschina.net/question/3799215_2280790?from=timeline <https://www.oschina.net/question/3799215_2280790?from=timeline>* * There are about 6 departments of Huawei are using ServiceComb and other 8 companies are using ServiceComb. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb Willem Jiang 于2018年7月4日周三 下午10:30写道： > Hi JB. > > Thanks for pointing that out. I just updated the status to "near > graduation" > > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Mon, Jul 2, 2018 at 4:15 PM, Jean-Baptiste Onofré > wrote: > > > Hi > > > > Thanks for the update. I think we can update the status to "near > > graduation". > > > > I'm planning to work today and tomorrow on a plan and resolution to move > > forward on graduation. > > > > Regards > > JB > > > > Le 2 juil. 2018 à 10:10, à 10:10, Willem Jiang > a > > écrit: > > >Hi Team > > > > > >I just update the project report like this , please review it and feel > > >free > > >to add what I'm missing. > > >We may need to add a report link for the workshop which we hold last > > >week. > > > > > >BTW, we get more and more contributors to the projects, which is good > > >sign > > >to see. Please keep up this good work. > > > > > > > > >ServiceComb has been incubating since 2017-11-22. > > > > > >Three most important issues to address in the move towards graduation: > > > > > > 1. Community building > > > 2. Project visibility > > > 3. Trademark transfer > > > > > >Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > > >aware of? > > > > > > NO > > > > > >How has the community developed since the last report?(2018-04) > > > * The community get the second release out, service-center 1.0.0-m2, > > >java-chassis 1.0.0-m2 and saga 0.2.0 > > > * The community hold a day workshop in Beijing at Jun 27. > > > > > >How has the project developed since the last report? (2018-04) > > > * Java Chassis merged with 102 PRs by 16 contributors. > > > * Service Center merged with 58 PRs by 6 contributors . > > > * Saga merged with 48 PRs by 14 contributors. > > > * 70 mails send by 19 people on the dev@ list (2018-04) > > > * 156 mails sent by 17 people on the dev@ list （2018-05） > > > * 97 mails send by 23 people on the dev@ list (2018-06) > > > > > >How would you assess the podling's maturity? > > >Please feel free to add your own commentary. > > > > > > [ ] Initial setup > > > [ ] Working towards first release > > > [*] Community building > > > [ ] Nearing graduation > > > [ ] Other: > > > > > >Date of last release: > > > > > > 2018-06-22 Java Chassis 1.0.0-m2 > > > 2018-06-22 Service Center 1.0.0-m2 > > > 2018-06-22 Saga 0.2.0 > > > > > >When were the last committers or PPMC members elected? > > > 2018-06-08 Zheng yangyong was elected as committer. > > > 2018-06-11 Li Dagang(Eric) was elected as committer. > > > > > > > > >Willem Jiang > > > > > >Twitter: willemjiang > > >Weibo: 姜宁willem > > > > > >On Thu, Jun 28, 2018 at 5:41 AM, wrote: > > > > > >> Dear podling, > > >> > > >> This email was sent by an automated system on behalf of t
[ANNOUNCE] Meetups of Apache ServiceComb (incubating) Day at June 27th as a LC3 co-located event, Beijing China
Hi all, ServiceComb community are going to hold a meetup called Apache ServiceComb (incubating) Day at June 27th as a co-located event with LC3 2018, Beijing China, detailed agendas are listed here, ServiceComb website [1] and LC3 website [2]. And we also have a ServiceComb booth there from June 25th to June 27th during the LC3 conference. Detailed prepare work can find in dev@servicecomb mail list [3][4]. [1] http://servicecomb.incubator.apache.org/docs/ apache-servicecomb-incubating-day/ [2] https://lc32018.sched.com/event/EzNj [3] https://www.mail-archive.com/dev@servicecomb.apache.org/msg04624.html [4] https://www.mail-archive.com/dev@servicecomb.apache.org/msg04696.html Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb
[ANN] [Apache ServiceComb (incubating) Day] Detailed agenda has been updated to ServiceComb website, serveral popular medias are helping to promote it.
Hi all, As we announced before, meetup of "Apache ServiceComb (incubating) Day" will be held on June 27th [1]. I have updated the detailed agenda to our website [2]. Please do not hesitate to contact me if you have any question about the Meetup. By the way, we are trying our best to promote our project and community, such as, A PPT ont the booth to show ServiceComb community, A demo ont the booth to show using ServiceComb to build microservices easily, A back ground picture on the booth to show ServiceComb vision, Brochures, gifts, T-shirts to users and developers, Meetup live layout planning, Live broadcast preparing, Inviting Specified persons from ServiceComb users, etc. And I am also very happy to share that OSC [3], kaiyuanshe [4], itdks [5], developer.huawei [6] and other popular medias are helping our community to promote our meetup. Thanks to all the guys who help the community promotion, especially thanks to Wangkirin. [1] https://www.mail-archive.com/dev@servicecomb.apache.org/msg04624.html [2] http://servicecomb.incubator.apache.org/docs/apache-servicecomb-incubating-day/ [3] https://mp.weixin.qq.com/s/Kluwl2EGLKUjn5fnqXItsQ [4] https://mp.weixin.qq.com/s/e_5X2rtKU-e7-pZuC_H2bw [5] https://mp.weixin.qq.com/s/G5jyaLGnYEclXrIrTkLVDw [6] https://mp.weixin.qq.com/s/abAEfsCBfAbdfkxuHGiUKQ Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb
Re: [DISCUSSION] How to migrate configurations from cse to servicecomb prefix
If we consider a smooth transition for customers of the commercial version
of ServiceComb, then we can consider compatibility of keep both of prefix
cse and prefix servicecomb within a certain period， and also provide a
convention tool.
Best Regards,
---
Zen Lin
zenlintechnofr...@gmail.com
Focused on Micro Service and Apache ServiceComb
2018-06-14 8:50 GMT+08:00 Zen Lin :
> +1 to wjm's suggestion.
> I think keep two prefix in ServiceComb will confuse the users.
> Anyway, CSE is just a one of the business implement from a business
> company, it has nothing to do with ServiceComb in a way.
> If we reserve the old prefix now, and we also have to change it in near
> future to keep ServiceComb is ServiceComb.
>
> Providing a conversion tool is a good idea which allow users easily adapt
> to the new release.
> Tool will be loosely coupled with the ServiecComb but Module will be part
> of the core of the ServiceComb, I suggest we avoiding to keep anything
> about cse in ServiceComb core.
>
> If providing a configuration changing module that is based on the
> consideration of different configuration centers in future, I think it
> would be feasible, but not based on the consideration of how to deal with
> cse prefix in ServiceComb.
>
> Also, The idea of print error messages is good also, but this is another
> topic, something like "how to make logs friendly and usable".
>
>
> Best Regards,
> ---
> Zen Lin
> zenlintechnofr...@gmail.com
> Focused on Micro Service and Apache ServiceComb
>
> 2018-06-13 16:04 GMT+08:00 Yang Bo :
>
>> +1 for wjm's idea.
>> The ultimate goal is to use servicecomb.* everywhere in code and
>> configurations.
>> We can provide a compatible layer to read the cse.* configurations and
>> merge them into servicecomb.* and use serviccomb.* elsewhere in the code.
>>
>> Perhaps we can also provide a tool to transform all configuration files
>> from cse.* to servicecomb.* to help user migrate, this should be quite
>> simple.
>>
>> On Wed, Jun 13, 2018 at 2:57 PM Willem Jiang
>> wrote:
>>
>> > Hi，
>> >
>> > I think we can borrow some idea from Spring Boot.
>> > There are some configuration change between Spring Boot 2 and Spring
>> Boot
>> > 1.
>> > Spring Boot provides configuration change module to the mapping thing,
>> or
>> > print error message for the changed properties.
>> >
>> > Any thought?
>> >
>> >
>> > Willem Jiang
>> >
>> > Twitter: willemjiang
>> > Weibo: 姜宁willem
>> >
>> > On Wed, Jun 13, 2018 at 11:08 AM, bismy wrote:
>> >
>> > > Hi,
>> > >
>> > >
>> > > Currently we duplicate configurations for servicecomb prefix to cse
>> > > prefix, and in code we can read configurations by cse prefix. That is:
>> > > 1. Config file using servicecomb.x.y, can read in code with
>> > > getProperty("servicecomb.x.y") and getProperty("cse.x.y")
>> > > 2. Config file using cse.x.y, can read in code with
>> > getProperty("cse.x.y")
>> > >
>> > >
>> > > If we use cse prefix in code, this is the most portable way to read
>> both
>> > > cse.x.y and servicecomb.x.y configurations.
>> > >
>> > >
>> > > However, this will leading us to write code always using cse, this is
>> not
>> > > our intention. We are asking users/developers to using servicecomb
>> > > gradually.
>> > >
>> > >
>> > > I suggest we use servicecomb prefix when adding new configuration
>> items.
>> > > But there maybe some axtra work users need to do. For example,
>> > >
>> > >
>> > > One user's project using cse prefix:
>> > >
>> > >
>> > > cse:
>> > >function:
>> > > a: false
>> > > b: false
>> > >
>> > >
>> > > And when we add a new configuration item: servicecomb.funciton.c,
>> users
>> > > must change the configuration file to one of the following:
>> > >
>> > >
>> > > servicecomb:
>> > > function:
>> > > a: false
>> > > b: false
>> > > c: false
>> > >
>> > >
>> > >
>> > >
>> > > or
>> > > cse:
>> > >function:
>> > > a: false
>> > > b: false
>> > >
>> > > servicecomb:
>> > > function:
>> > > c: false
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > I think we need to encourage users using servicecomb when upgrading,
>> and
>> > > developers to use servicecomb prefix when adding new configuration
>> > items.
>> > >
>> > >
>> > > Any idea?
>> >
>>
>>
>> --
>> Best Regards,
>> Yang.
>>
>
>
Re: [DISCUSSION] How to migrate configurations from cse to servicecomb prefix
+1 to wjm's suggestion.
I think keep two prefix in ServiceComb will confuse the users.
Anyway, CSE is just a one of the business implement from a business
company, it has nothing to do with ServiceComb in a way.
If we reserve the old prefix now, and we also have to change it in near
future to keep ServiceComb is ServiceComb.
Providing a conversion tool is a good idea which allow users easily adapt
to the new release.
Tool will be loosely coupled with the ServiecComb but Module will be part
of the core of the ServiceComb, I suggest we avoiding to keep anything
about cse in ServiceComb core.
If providing a configuration changing module that is based on the
consideration of different configuration centers in future, I think it
would be feasible, but not based on the consideration of how to deal with
cse prefix in ServiceComb.
Also, The idea of print error messages is good also, but this is another
topic, something like "how to make logs friendly and usable".
Best Regards,
---
Zen Lin
zenlintechnofr...@gmail.com
Focused on Micro Service and Apache ServiceComb
2018-06-13 16:04 GMT+08:00 Yang Bo :
> +1 for wjm's idea.
> The ultimate goal is to use servicecomb.* everywhere in code and
> configurations.
> We can provide a compatible layer to read the cse.* configurations and
> merge them into servicecomb.* and use serviccomb.* elsewhere in the code.
>
> Perhaps we can also provide a tool to transform all configuration files
> from cse.* to servicecomb.* to help user migrate, this should be quite
> simple.
>
> On Wed, Jun 13, 2018 at 2:57 PM Willem Jiang
> wrote:
>
> > Hi，
> >
> > I think we can borrow some idea from Spring Boot.
> > There are some configuration change between Spring Boot 2 and Spring Boot
> > 1.
> > Spring Boot provides configuration change module to the mapping thing, or
> > print error message for the changed properties.
> >
> > Any thought?
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Wed, Jun 13, 2018 at 11:08 AM, bismy wrote:
> >
> > > Hi,
> > >
> > >
> > > Currently we duplicate configurations for servicecomb prefix to cse
> > > prefix, and in code we can read configurations by cse prefix. That is:
> > > 1. Config file using servicecomb.x.y, can read in code with
> > > getProperty("servicecomb.x.y") and getProperty("cse.x.y")
> > > 2. Config file using cse.x.y, can read in code with
> > getProperty("cse.x.y")
> > >
> > >
> > > If we use cse prefix in code, this is the most portable way to read
> both
> > > cse.x.y and servicecomb.x.y configurations.
> > >
> > >
> > > However, this will leading us to write code always using cse, this is
> not
> > > our intention. We are asking users/developers to using servicecomb
> > > gradually.
> > >
> > >
> > > I suggest we use servicecomb prefix when adding new configuration
> items.
> > > But there maybe some axtra work users need to do. For example,
> > >
> > >
> > > One user's project using cse prefix:
> > >
> > >
> > > cse:
> > >function:
> > > a: false
> > > b: false
> > >
> > >
> > > And when we add a new configuration item: servicecomb.funciton.c, users
> > > must change the configuration file to one of the following:
> > >
> > >
> > > servicecomb:
> > > function:
> > > a: false
> > > b: false
> > > c: false
> > >
> > >
> > >
> > >
> > > or
> > > cse:
> > >function:
> > > a: false
> > > b: false
> > >
> > > servicecomb:
> > > function:
> > > c: false
> > >
> > >
> > >
> > >
> > >
> > > I think we need to encourage users using servicecomb when upgrading,
> and
> > > developers to use servicecomb prefix when adding new configuration
> > items.
> > >
> > >
> > > Any idea?
> >
>
>
> --
> Best Regards,
> Yang.
>
Re: [VOTE] Release Apache ServiceComb Saga (incubating) version 0.2.0
+1 non-binding Checked followings passed, Build from source. README.md. Release Notes. Notice. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb 2018-06-11 11:47 GMT+08:00 Yang Bo : > +1 non-binding > > On Mon, Jun 11, 2018 at 11:46 AM, Yang Bo wrote: > > > > > > > 1. Release name OK > > 2. GPG signature and checksum OK > > 3. Rat check OK > > 4. Basic function test OK > > 5. Build from source OK > > 6. README OK > > 7. DISCLAIMER, NOTICE, LICENSE OK > > > > On Mon, Jun 11, 2018 at 9:04 AM, Willem Jiang > > wrote: > > > >> +1 (binding) > >> > >> I checked: > >> - incubating in binary and src kit name > >> - signatures and hashes correct > >> - LICENSE is fine (third party jars versions are updated) > >> - NOTICE is OK but has wrong year please fix > >> - no unexpected binary files > >> - source files have headers > >> - can build the kit from source with any error > >> - can run the demo with the instruction of README > >> > >> > >> Willem Jiang > >> > >> Twitter: willemjiang > >> Weibo: 姜宁willem > >> > >> > >> > >> > >> Willem Jiang > >> > >> Twitter: willemjiang > >> Weibo: 姜宁willem > >> > >> On Fri, Jun 8, 2018 at 2:29 PM, Mohammad Asif Siddiqui < > >> asifdxtr...@apache.org> wrote: > >> > >> > Hi All, > >> > > >> > This is a call for Vote to release Apache ServiceComb Saga > (Incubating) > >> > version 0.2.0 > >> > > >> > Release Notes : https://issues.apache.org/ > jira/secure/ReleaseNote.jspa? > >> > projectId=12321626=12342425 > >> > > >> > Release Candidate : https://dist.apache.org/repos/dist/dev/incubator/ > >> > servicecomb/incubator-servicecomb-saga/0.2.0/rc-01/ > >> > > >> > Staging Repository : https://repository.apache.org/ > >> content/repositories/ > >> > orgapacheservicecomb-1271/ > >> > > >> > Release Tag : https://github.com/apache/incubator-servicecomb-saga/ > >> > releases/tag/0.2.0 > >> > > >> > Release CommitID : 1f3c3d1e61a6c7f40df479a43d28b54f335d84ac > >> > > >> > Keys to verify the Release Candidate : https://dist.apache.org/repos/ > >> > dist/dev/incubator/servicecomb/KEYS > >> > > >> > Voting will start now ( Friday, 8th June, 2018) and will remain open > for > >> > next 72 hours, Request all PPMC members to give their vote. > >> > > >> > [ ] +1 Release this package as 0.2.0 > >> > [ ] +0 No Opinion > >> > [ ] -1 Do not release this package because > >> > > >> > On the behalf of ServiceComb Team > >> > Mohammad Asif Siddiqui > >> > > >> > > >> > > > > > > > > -- > > Best Regards, > > Yang. > > > > > > -- > Best Regards, > Yang. >
Re: [ANN] New ServiceComb committer: Eric Lee (李达港）
Congratulations Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb 2018-06-11 9:31 GMT+08:00 Yang Bo : > Congrats! > > On Mon, Jun 11, 2018 at 8:51 AM, wjm wjm wrote: > > > Congratulations ~ > > > > 2018-06-10 15:31 GMT+08:00 Willem Jiang : > > > > > Please join me and the rest of the ServiceComb PPMC members in > welcoming > > > our > > > new ServiceComb committer: Eric Lee (李达港). > > > > > > Eric Lee contribute the ServiceComb since last Jun, he is active > > > contributor on saga, java-chassis and website. and we look forward to > > many > > > more contributions in the future. > > > > > > Congratulations to Eric ! Welcome! > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > > > > -- > Best Regards, > Yang. >
Re: [ANN] New ServiceComb committer: Zheng Yangyong (郑扬勇）
Congratulations to Zheng Yangyong. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb 2018-06-08 9:34 GMT+08:00 Willem Jiang : > Please join me and the rest of the ServiceComb PPMC members in welcoming > our > new ServiceComb committer: Zheng Yangyong (郑扬勇). > > Yangyong is active ServiceComb contributor since July 2017. He has > contributed to the project in different ways (website, email, examples, and > much more) > and we look forward to many more contributions in the future. > > Congratulations to Yangyong! Welcome! > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem >
Re: [Discuss] Should we clean up vendor/github.com/go-ecosystem for ServiceCenter
+1 to Yang Bo's suggestion, Forked to your own github organization, then used in ServiceCenter as a vendor referenced to your forked brench. The problem introduced by this approach is that the cloner needs to maintain its own branch, but if you modified the libraries, no way to escape maintaining your branch(your modifyings). Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb 2018-06-07 14:18 GMT+08:00 Yang Bo : > If we do have modified those libraries, it's better we make a fork of them > on github and the use the forks. > > It's still better that we use them directly as is to ease later upgrade and > do the work in our code through wrappers. > > On Thu, Jun 7, 2018 at 11:32 AM, Willem Jiang > wrote: > > > If we changed the code, we should move it third party directory. > > @Asif @Cuiyihua Could you double check with YangBo？ > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Thu, Jun 7, 2018 at 10:29 AM, Yang Bo wrote: > > > > > Hi All, > > > > > > Currently we store github.com/go-ecosystem/grpc-gateway and > > > go-grpc-prometheus under the vendor directory. > > > > > > The vendor directory should only contain manifest file and all other > code > > > should be fetched from third party repository. > > > > > > If we have made some modification to those libraries, then we need to > > move > > > them to a proper place. > > > > > > -- > > > Best Regards, > > > Yang. > > > > > > > > > -- > Best Regards, > Yang. >
Re: [Discuss] Should we clean up vendor/github.com/go-ecosystem for ServiceCenter
I think it is better to decoupled package it if we want to add something enhanced, but not just only modified it and then keep in the third-party. Anyway , third-party is not a regular and recommended way to using golang libraries. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb 2018-06-07 11:32 GMT+08:00 Willem Jiang : > If we changed the code, we should move it third party directory. > @Asif @Cuiyihua Could you double check with YangBo？ > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Thu, Jun 7, 2018 at 10:29 AM, Yang Bo wrote: > > > Hi All, > > > > Currently we store github.com/go-ecosystem/grpc-gateway and > > go-grpc-prometheus under the vendor directory. > > > > The vendor directory should only contain manifest file and all other code > > should be fetched from third party repository. > > > > If we have made some modification to those libraries, then we need to > move > > them to a proper place. > > > > -- > > Best Regards, > > Yang. > > >
Re: The Apache ServiceComb community are planing to hold an event called Apache ServiceComb (incubating) Day
Hi ASF Trademarks & Brand Management, I am happy to say that Meetup of Apache ServiceComb (incubating) Day has been listed on LC3 website [1] and community's website [2]. [1] https://www.lfasiallc.com/events/lc3-2018/features-and-add-ons/co-located-events/ [2] http://servicecomb.incubator.apache.org/docs/apache-servicecomb-incubating-day/ Thanks for your help. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb 2018-04-11 17:22 GMT+08:00 Zen Lin <zenlintechnofr...@gmail.com>: > Hi ASF Trademarks & Brand Management, ASF Marketing & Publicity, > > The ServiceComb community have plan to hold an event called "Apache > ServiceComb (incubating) Day" hosted by Huawei Cloud, as a Co-located > Event in LC3 2018 Asia. > The proposal has been approved by PPMCs through voting in maillist[1]. > > I have been working with Sally on holding the event, our plan is as > followings, > 1. Topics on the event are focused on user-pratices, technologies and > ecosystem of Apache ServiceComb (incubating). All of the topics with > limited time are happening at the same day and same location , just seems > like a series of Meetups. > 2. PMCs of ServiceComb (incubating) are the organizer of the event, and 5 > PMCs involve there already. > 3. The event will be hold in one day Between Jun 25, 2018 and Jun 27, > 2018, maybe in Jun 26, 2018. > 4. About 60 to 100 attendees are expected. > 5. We are planing to send you the link to the event pages when ready. > > Have we missed anything yet? > If we do missed something, please help to let me know, thanks very much. > > > > [1] https://lists.apache.org/list.html?dev@servicecomb.apache. > org:lte=1M:Hold%20an%20event%20called%20Apache%20ServiceComb > > > <https://lists.apache.org/list.html?dev@servicecomb.apache.org:lte=1M:Hold%20an%20event%20called%20Apache%20ServiceComb> > > > <https://lists.apache.org/list.html?dev@servicecomb.apache.org:lte=1M:Hold%20an%20event%20called%20Apache%20ServiceComb> > > > <https://lists.apache.org/list.html?dev@servicecomb.apache.org:lte=1M:Hold%20an%20event%20called%20Apache%20ServiceComb> > Best Regards > --- > Zen Lin > > > > > <https://lists.apache.org/list.html?dev@servicecomb.apache.org:lte=1M:Hold%20an%20event%20called%20Apache%20ServiceComb> > > > >
[ANNOUNCE] Meetup of Apache ServiceComb (incubating) Day will be held on June 27th, the notice has been listed on our website and LC3 website.
Hi Dear guys, Last time, we discussed [1] and called a vote [2] for holding Apache ServiceComb (incubating) Day Meetup, and approved by our PMCs [3]. Now, I am very happy to announce that the notice of Apache ServiceComb (incubating) Day Meetup has been listed on the LC3 2018 website [4], the event will be held on June 27th. I also listed it on our news section on the ServiceComb website [5]. Thanks to all of the support from speakers and volunteers. Let us meet up in Beijing and enjoy it. [1] https://www.mail-archive.com/dev@servicecomb.apache.org/msg03298.html [2] https://www.mail-archive.com/dev@servicecomb.apache.org/msg03436.html [3] https://www.mail-archive.com/dev@servicecomb.apache.org/msg03558.html [4] https://www.lfasiallc.com/events/lc3-2018/features-and-add-ons/co-located-events/ [5] http://servicecomb.incubator.apache.org/docs/apache-servicecomb-incubating-day/ <http://servicecomb.incubator.apache.org/docs/apache-servicecomb-incubating-day/> Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb
Re: Third party jar and License check
Yeah , thanks to Willem. I am sorry I just continuous focused on the community promotion, thus I lacked of experience about the release. Maybe in future, I will try to learn about that once I have time. I think some guys that have contributed on the previous release can help the community to do this, thus I created a JIRA issue [1] to track this. [1] https://issues.apache.org/jira/browse/SCB-608 Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb 2018-05-24 8:40 GMT+08:00 Willem Jiang <willem.ji...@gmail.com>: > We have a release guide[1] for the release processing. > We can add a check list section for verifying the kit. Please feel free to > send a PR for it. > > [1]https://servicecomb.incubator.apache.org/developers/release-guide/ > > > Willem Jiang > > Blog: http://willemjiang.blogspot.com (English) > http://jnn.iteye.com (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > On Wed, May 23, 2018 at 7:56 PM, Zen Lin <zenlintechnofr...@gmail.com> > wrote: > > > I suggest adding a action, black crow scanning. > > And also , shall we comb out what should be check carefully first > according > > to the first release prepare, then put it to our website. > > Thus we can just check it step by step accroding to the checklist when we > > release the next version. > > > > Hi Yangbo, > > To the latest release, we have find some easily misunderstanding places > in > > the Apache rules, we can output a blog about that then put it to the > Apache > > blog, thus to help other Apache incubating projects. > > > > Best Regards, > > --- > > Zen Lin > > zenlintechnofr...@gmail.com > > Focused on Micro Service and Apache ServiceComb > > > > 2018-05-23 16:22 GMT+08:00 Willem Jiang <willem.ji...@gmail.com>: > > > > > Hi team, > > > > > > As we are heading to a new release, let me share a tools from the > > recently > > > release check in the incubator generic mailing list. > > > > > > I point out some License issue[1] by checking the third party jars, > > pulsar > > > did a quick fix[2] with a new script. I highly recommend that we can > > > leverage this script to avoid the same mistake. > > > > > > Any thought？ > > > > > > [1] > > > https://lists.apache.org/thread.html/ac5d0ae4367c7d11153444adc6317e > > > bdd4aa93f51adcba7d548f8097@%3Cgeneral.incubator.apache.org%3E > > > > > > [2]https://github.com/apache/incubator-pulsar/pull/1820 > > > > > > > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > >
Re: Using roadmap tag for the JIRA
+1 It is a so good idea. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb 2018-05-24 11:38 GMT+08:00 Willem Jiang <willem.ji...@gmail.com>: > Hi Team, > > As JIRA[1] provides the tags for us to lookup issue. My suggestion is we > put the roadmap tag to the issues that we plan to do in the next few > month. In this way we can build up dynamic road map for the developer to > check out. > > [1]http://issues.apache.org/jira/browse/SCB > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem >
Re: Please Update the JIRA Status for Preparing the Next Release
Hi Yangbo, I found that few guys response to this topic so far, I am not sure wheather they are busy on coding to forget to do this, or they just considered have no need to update. My suggestion is to contact persons which owned the issues through our Gitter tomorrow, thus you can get response to make sure. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb 2018-05-23 20:01 GMT+08:00 Zen Lin <zenlintechnofr...@gmail.com>: > Yeah, it is nice. > Hi mabin , > I know someone interested in ServiceComb have contact you to consult how > to contribute to the Apache ServiceComb. > Perhaps, you can use these issues[1] to help them start the trip. > > [1] https://issues.apache.org/jira/browse/SCB-500?jql=projec > t%20%3D%20SCB%20AND%20status%20%3D%20Open%20AND%20fixVersio > n%20in%20(EMPTY%2C%20java-chassis-1.0.0-m2)%20AND%20labels%20%3D%20newbie > > Best Regards, > --- > Zen Lin > zenlintechnofr...@gmail.com > Focused on Micro Service and Apache ServiceComb > > 2018-05-23 15:13 GMT+08:00 Willem Jiang <willem.ji...@gmail.com>: > >> I did some clean up on the Java Chassis 1.0.0-m2 and found out there are >> bunch of JIRAs are a good start for the user who want to help. >> I start a page of contribution[1] which has the link of these newbie >> JIRAs[2]. >> >> [1]http://servicecomb.incubator.apache.org/developers/contributing >> [2] >> https://issues.apache.org/jira/browse/SCB-500?jql=project% >> 20%3D%20SCB%20AND%20status%20%3D%20Open%20AND%20fixVersion% >> 20in%20(EMPTY%2C%20java-chassis-1.0.0-m2)%20AND%20labels%20%3D%20newbie >> >> >> Willem Jiang >> >> Blog: http://willemjiang.blogspot.com (English) >> http://jnn.iteye.com (Chinese) >> Twitter: willemjiang >> Weibo: 姜宁willem >> >> On Wed, May 16, 2018 at 5:30 PM, Yang Bo <oaky...@gmail.com> wrote: >> >> > Hi All, >> > >> > We will release the next version of ServiceComb in late June, and the >> > feature freeze will happen in the end of May. >> > >> > I checked all the undone issues of SCB project on apache JIRA today. And >> > assigned fixVersions to some of the issues. >> > >> > Please check the issues you report or assigned and update them >> > accordingly. If the fixVersions is incorrect, please update it. >> > >> > There are many issues that is unassigned, please assign them or modify >> the >> > fixVersions to the next release.(1.0.0 for SC and Chassis, 0.3.0 for >> Saga). >> > >> > The attachment is a list of all issues. Please update them by >> 2018/05/18. >> > >> > >> > >> > -- >> > Best Regards, >> > Yang. >> > >> > >
Re: Please Update the JIRA Status for Preparing the Next Release
Yeah, it is nice. Hi mabin , I know someone interested in ServiceComb have contact you to consult how to contribute to the Apache ServiceComb. Perhaps, you can use these issues[1] to help them start the trip. [1] https://issues.apache.org/jira/browse/SCB-500?jql= project%20%3D%20SCB%20AND%20status%20%3D%20Open%20AND% 20fixVersion%20in%20(EMPTY%2C%20java-chassis-1.0.0-m2)% 20AND%20labels%20%3D%20newbie Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb 2018-05-23 15:13 GMT+08:00 Willem Jiang <willem.ji...@gmail.com>: > I did some clean up on the Java Chassis 1.0.0-m2 and found out there are > bunch of JIRAs are a good start for the user who want to help. > I start a page of contribution[1] which has the link of these newbie > JIRAs[2]. > > [1]http://servicecomb.incubator.apache.org/developers/contributing > [2] > https://issues.apache.org/jira/browse/SCB-500?jql= > project%20%3D%20SCB%20AND%20status%20%3D%20Open%20AND% > 20fixVersion%20in%20(EMPTY%2C%20java-chassis-1.0.0-m2)% > 20AND%20labels%20%3D%20newbie > > > Willem Jiang > > Blog: http://willemjiang.blogspot.com (English) > http://jnn.iteye.com (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > On Wed, May 16, 2018 at 5:30 PM, Yang Bo <oaky...@gmail.com> wrote: > > > Hi All, > > > > We will release the next version of ServiceComb in late June, and the > > feature freeze will happen in the end of May. > > > > I checked all the undone issues of SCB project on apache JIRA today. And > > assigned fixVersions to some of the issues. > > > > Please check the issues you report or assigned and update them > > accordingly. If the fixVersions is incorrect, please update it. > > > > There are many issues that is unassigned, please assign them or modify > the > > fixVersions to the next release.(1.0.0 for SC and Chassis, 0.3.0 for > Saga). > > > > The attachment is a list of all issues. Please update them by 2018/05/18. > > > > > > > > -- > > Best Regards, > > Yang. > > >
Re: Third party jar and License check
I suggest adding a action, black crow scanning. And also , shall we comb out what should be check carefully first according to the first release prepare, then put it to our website. Thus we can just check it step by step accroding to the checklist when we release the next version. Hi Yangbo, To the latest release, we have find some easily misunderstanding places in the Apache rules, we can output a blog about that then put it to the Apache blog, thus to help other Apache incubating projects. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb 2018-05-23 16:22 GMT+08:00 Willem Jiang <willem.ji...@gmail.com>: > Hi team, > > As we are heading to a new release, let me share a tools from the recently > release check in the incubator generic mailing list. > > I point out some License issue[1] by checking the third party jars, pulsar > did a quick fix[2] with a new script. I highly recommend that we can > leverage this script to avoid the same mistake. > > Any thought？ > > [1] > https://lists.apache.org/thread.html/ac5d0ae4367c7d11153444adc6317e > bdd4aa93f51adcba7d548f8097@%3Cgeneral.incubator.apache.org%3E > > [2]https://github.com/apache/incubator-pulsar/pull/1820 > > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem >
Re: [ANNOUNCE] Yangbo Will Make a Speech about Apache ServiceComb (incubating) on OSC MeetUp in Shanghai on 27th May
Hi All, The link about the Event that Yang Bo will attend and share the ServiceComb project has already been posted on the OSC website [1]. Besides, in order to promote the speech, I have posted a notice on the ServiceComb weChat subscription number [2]. [1] https://www.oschina.net/event/2279800 [2] https://mp.weixin.qq.com/s/GgiFNl6b5OneLQavrBTG2g Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb 2018-05-16 20:12 GMT+08:00 Zen Lin <zenlintechnofr...@gmail.com>: > Hi, > > I am happy to share a good news, Yanbo is going to make a speech about our > project to promote the community, on OSChina MeetUp, in Shanghai, on 27th > May. > > The topic is, > Design Considerations of DevOps for Microservices Solution in Apache > ServiceComb (incubating) > > Draft introduction to the topic is, > With the rapid development of technologies/theories such as container, > cloud, agile, and DevOps, the microservice architecture has become > mainstream today. The Apache ServiceComb (incubating) has reached the good > performance, high reliability and other good results in the traditional > enterprises when they transformation to CloudNative and building > microservices in CloudNative enterprises. The topic is to share how the > Apache ServiceComb (incubating) project is considered for the user's best > DevOps experience in the microservice architecture when design a > microservice framework. > > Anyway , I am going to share the OSChina meetup link When the organizer > hangs out the activitie online. > > > Best Regards, > --- > Zen Lin > zenlintechnofr...@gmail.com > Focused on Micro Service and Apache ServiceComb >
Re: [VOTE] Decide which scheme to be used in the T-shirt that used in community promotion
+ A non-binding Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb 2018-05-21 10:39 GMT+08:00 DeanLee <82529...@qq.com>: > Hi All, > > We are going to make a batch of T-shirts used in community promotion. > Now, we have 2 schemes for the T-shirts with different design, scheme A > and scheme B. > > This is a call for Vote to decide which scheme to be used in the T-shirts. > You can find 2 schemes reference to https://github.com/microDevOps > /T-shirt/blob/master/README.md. > > Please feel free to vote, maybe you can get the T-shirt with your choice > in the future. > > Please vote accordingly: > [ ] +A scheme A > [ ] +B scheme B > > > Best Regards, > --- > Zen Lin > zenlintechnofr...@gmail.com > Focused on Micro Service and Apache ServiceComb >
Re: [VOTE]create a new project incubator-servicecomb-docs to host documentations for servicecomb components
+1 non-binding And an idea to suggest here, we can invite people from our community wechat group to jion in the document work,something like what jimisong is doing in promoting istio in China. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb 2018-05-18 9:05 GMT+08:00 Kirin Wang <wangqilint...@gmail.com>: > +1 non-binding > good idea to place our documents in a specific repo > > 2018-05-18 7:31 GMT+08:00 Willem Jiang <willem.ji...@gmail.com>: > > > +1 to host the our user reference doc in the same git repo. > > > > > > Willem Jiang > > > > Blog: http://willemjiang.blogspot.com (English) > > http://jnn.iteye.com (Chinese) > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Thu, May 17, 2018 at 7:20 PM, bismy <bi...@qq.com> wrote: > > > > > Hi All, > > >I am going to create a new project named > "incubator-servicecomb-docs". > > > This project will host documentations for servicecomb components. And > > this > > > projects may contains following subfolders. > > > > > > > > > -- > > >-java-chassis-reference-cn > > >-java-chassis-reference-en > > >-service-center-reference-cn > > >-service-center-reference-en > > >-saga-reference-cn > > >-saga-reference-en > > > > > >And so no. > > > > > > > > > We have found a excellent tool to develop Markdown docs using > gitbook, > > > and these contents are organised in gitbook structure, as an example, I > > > merged temporary contents here > > > > > > -- https://github.com/apache/incubator-servicecomb-java- > > > chassis/tree/gh-pages > > > > > > > > > What's the difference of the project between "incubator-servicecomb- > > website" > > > ? > > > > > > > > > -- This project only contains MarkDown sources for individual > > > projects and will be compiled and integrate to "incubator-servicecomb- > > website" > > > by a scripts periodically. And "incubator-servicecomb-website" acts > like > > > a website framework. > > > > > > > > > > > > > > > Please vote if we can create this project, and from the start, we may > > only > > > have java-chassis-reference-cn, more contents will be added in future > by > > > PRs. > > >
Re: [Discussion] collect suggestions about Servicecomb T-shirt design draft
Hi DeanLee, I could not get what you mean by 'suggestion for T-shirt design'. Do you mean you want to collect slogon to be used in the T-shirt that will be using in the community promotion? Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb 2018-05-17 17:52 GMT+08:00 DeanLee <82529...@qq.com>: > Any suggestion and idea to share, please feel free to discuss. > > Logo > > Front > > Back > Regards > Dean >
[ANNOUNCE] Yangbo Will Make a Speech about Apache ServiceComb (incubating) on OSC MeetUp in Shanghai on 27th May
Hi, I am happy to share a good news, Yanbo is going to make a speech about our project to promote the community, on OSChina MeetUp, in Shanghai, on 27th May. The topic is, Design Considerations of DevOps for Microservices Solution in Apache ServiceComb (incubating) Draft introduction to the topic is, With the rapid development of technologies/theories such as container, cloud, agile, and DevOps, the microservice architecture has become mainstream today. The Apache ServiceComb (incubating) has reached the good performance, high reliability and other good results in the traditional enterprises when they transformation to CloudNative and building microservices in CloudNative enterprises. The topic is to share how the Apache ServiceComb (incubating) project is considered for the user's best DevOps experience in the microservice architecture when design a microservice framework. Anyway , I am going to share the OSChina meetup link When the organizer hangs out the activitie online. Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb
Error Report Received When Sending a mail through dev@
Hi, When I sent out a mail through the dev@ mail list, I received a error reply as following, I think it is maybe because of someone have unsubscribed the mail list. I think it should not report error in this situation, could anyone help to fix it? postmas...@outlook.com 18:03 (3分钟前) 发送至 我 *newmx36.qq.com <http://newmx36.qq.com/> rejected your message to the following email addresses:* liujichun1...@qq.com Your message couldn't be delivered. When Office 365 tried to send the message, the external email server returned the error below. This is probably due to a problem or policy setting on the recipient's email system. Check the error for information about the problem. The error might tell you what went wrong and how to fix it. For example, if it says the message was blocked due to a potential virus, try sending the message again without attachments. *For Email Admins* This error was reported by an email server outside Office 365, and if the sender is unable to fix the problem by modifying their message then it's likely that it's a problem that only the recipient's email admin can fix. 1. *Check the error for information about the problem.* The error might tell you what went wrong and provide clues for how to fix it. For example, if it says the message was rejected due a Sender Policy Framework (SPF) issue then you'll have to work with your domain registrar to properly configure your SPF record. 2. *Check the error for information about where the problem is happening.* For example, look for a domain name like contoso.com. This tells you which organization was responsible for the error. The recipient's email server could be causing the problem, or it could be due to a third-party service that your organization or the recipient's organization is using to process or filter email messages. 3. *If you can't fix the problem, contact the responsible party's email admin.* This could be the recipient's email admin, your smart host service admin, or someone similar. Provide them with the error code and error message from this non-delivery report (NDR) to help them troubleshoot the issue. Unfortunately, Office 365 support is unlikely to be able to help with these kinds of externally reported errors. *newmx36.qq.com <http://newmx36.qq.com/> gave this error:Remote server returned an error -> 550 Mailbox not found. http://service.mail.qq.com/cgi-bin/help?subtype=1&=20022&=1000728 <http://service.mail.qq.com/cgi-bin/help?subtype=1&=20022&=1000728> * Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb
