Re: Mentors wanted for Apache Dubbo (incubating)
Very cool project. Would love to act as mentor (went through incubator with a project myself) but I’m not on IPMC. Would try to help in other ways. Keep it up! On Thu, Sep 20, 2018 at 7:34 PM Huxing Zhang wrote: > Hi community, > > The Apache Dubbo project now has two active mentors, and is looking > for new mentors. > > We will be very appreciated if anyone would like to volunteer. > > Below is the brief information: > > Apache Dubbo™ (incubating) is a high-performance, java based open > source RPC framework. > Website: http://dubbo.incubator.apache.org/ > Github: https://github.com/apache/incubator-dubbo > Latest Incubator report: https://wiki.apache.org/incubator/September2018 > > -- > Best Regards！ > Huxing > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Auto-cleaning up Stale PRs
+1. Apache CarbonData will try it to clean invalid pull requests and jira issues, thanks. Regards Liang -- Sent from: http://apache-incubator-general.996316.n3.nabble.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache OpenWhisk (Incubating): python, php and swift runtimes 1.12.0 [RC1]
Hi +1 My checking as below: - incubating in name - DISCLAIMER exits - LICENSE and NOTICE ok - Not exists binary files - Checked all source files including ASF headers - Can compile from source code Regards Liang Vincent S Hou wrote > Dear IPMC members, > > This is a call for vote to release Apache OpenWhisk (Incubating): > OpenWhisk python, php and swift runtimes 1.12.0 [RC1]. > > The Apache OpenWhisk community has voted on and approved a proposal to > release Apache OpenWhisk (Incubating): python, php and swift runtimes, > Version 1.12.0. > > We now kindly request the Incubator PMC members to review and vote on this > incubator release. > > OpenWhisk python, php and swift runtimes vote thread: > https://lists.apache.org/thread.html/d0cefe927585b38597805f5f42cae0f46308f8acf14bfd771295392a@%3Cdev.openwhisk.apache.org%3E > > OpenWhisk python, php and swift runtimes vote result thread: > https://lists.apache.org/thread.html/498e0f18a3d399d6926bc3fd853af5c910d6c17a304c00c9d8f8ace5@%3Cdev.openwhisk.apache.org%3E > > This release comprises of source code distribution only. > > > For OpenWhisk Runtime Python: > The source code artifact of OpenWhisk Runtime Python can be found at: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz > > The SHA-512 checksum for the artifact of OpenWhisk Runtime Python is: > openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz: > CE78C962 05B22F78 0209C597 034684CE 48321E7D 39516DFC 3A93010C BF9CF4D0 > CA2263F6 > 287C9963 60A17082 398A1F61 32745543 0199DEEE 3BFABF6E 5C819230 > which can be found via: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz.sha512 > > The signature of the artifact of OpenWhisk Runtime Python can be found > via: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz.asc > > > For OpenWhisk Runtime PHP: > The source code artifact of OpenWhisk Runtime PHP can be found at: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz > > The SHA-512 checksum for the artifact of OpenWhisk Runtime PHP is: > openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz: > 417DF65E 881BEC2E 6F58F135 45E1C9EA 4C8CA88A 67A31B82 361D6818 796CC605 > 46484A35 > 411E255C B29F1BAD 9298EB57 F89DD64E E340511C EF4ADBCE 948F87DB > which can be found via: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz.sha512 > > The signature of the artifact of OpenWhisk Runtime PHP can be found via: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz.asc > > > For OpenWhisk Runtime Docker: > The source code artifact of OpenWhisk Runtime Docker can be found at: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz > > The SHA-512 checksum for the artifact of OpenWhisk Runtime Docker is: > openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz: > E16164FE 9AD218DF 5ACDA598 BC360A43 B52A9B3F F59B2BF4 429B177B F539804A > 8166AFED > FBA9E0F0 8918EDFC 7A485DA6 545DF3C8 C7924B68 D9DE9C22 99F783AC > which can be found via: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz.sha512 > > The signature of the artifact of OpenWhisk Runtime Docker can be found > via: > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz.asc > > > > KEYS file is available at: > https://www.apache.org/dist/incubator/openwhisk/KEYS > This key has been validated here: > http://pgp.mit.edu/pks/lookup?search=houshengbo=index > > This is the first time that Apache OpenWhisk: python, php and swift > runtimes request for a release, so there is no file of CHANGELOG. > > The documentation on how to verify the artifacts can be found at: > https://cwiki.apache.org/confluence/display/OPENWHISK/How+to+verify+the+release+checklist+and+vote+on+OpenWhisk+modules+under+Apache > > We are currently using the tool called > openwhisk-release(https://github.com/apache/incubator-openwhisk-release) > to release all the modules of OpenWhisk. The instruction for release > managers can be found at: > https://github.com/apache/incubator-openwhisk-release/blob/master/docs/release_instructions.md. > This tool > supports both manual and automated modes to package the source code, sign >
Re: We want to contribute brpc to ASF, looking for champion and mentor ,please help
Hi An interesting project. One question : the project name is confirmed with "brpc"? it means "baidu rpc" ? Just kind reminder : it would be better if you could confirm the name before starting incubating, it would be the lowest cost for your project. Regards Liang -- Sent from: http://apache-incubator-general.996316.n3.nabble.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Mentors wanted for Apache Dubbo (incubating)
Hi community, The Apache Dubbo project now has two active mentors, and is looking for new mentors. We will be very appreciated if anyone would like to volunteer. Below is the brief information: Apache Dubbo™ (incubating) is a high-performance, java based open source RPC framework. Website: http://dubbo.incubator.apache.org/ Github: https://github.com/apache/incubator-dubbo Latest Incubator report: https://wiki.apache.org/incubator/September2018 -- Best Regards！ Huxing - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: We want to contribute brpc to ASF, looking for champion and mentor ,please help
Hi Justin, Given the recent activity around dropping inactive mentors there will be a large need for fresh IPMC members. I think that a general message to members@ with a list of podlings and proposals needing mentors would be a reasonable message. See you in Montreal. Regards, Dave > On Sep 20, 2018, at 2:30 PM, Justin Mclean wrote: > > Hi, > >> The IPMC might be too shallow a pool. Justin, can you email members@ for >> them with a draft of their proposal, perhaps? > > Given they need to understand the incubation process they should probably be > an IPMC member and subscribed to this list. Given the large size of memebers@ > there would probably be some complaints if I emailed it there. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[ANNOUNCE] Apache Gobblin (incubating) 0.13.0 released
We are pleased to announce that Apache Gobblin (incubating) 0.13.0 is released. Gobblin is a distributed data integration framework that simplifies common aspects of big data integration such as data ingestion, replication, organization and lifecycle management for both streaming and batch data ecosystems. The release is available at: https://gobblin.apache.org/download/ On behalf of the Gobblin team, Hung Tran = *DISCLAIMER* Apache Gobblin (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
Re: We want to contribute brpc to ASF, looking for champion and mentor ,please help
Hi, > The IPMC might be too shallow a pool. Justin, can you email members@ for > them with a draft of their proposal, perhaps? Given they need to understand the incubation process they should probably be an IPMC member and subscribed to this list. Given the large size of memebers@ there would probably be some complaints if I emailed it there. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Auto-cleaning up Stale PRs
Will do. -s On Wed, Sep 19, 2018 at 8:02 PM Dave Fisher wrote: > Hi - > > No objections from me. I do ask you let the IPMC know in your podling > report if this results in any controversy from the creators of any > autoclosed pull requests. > > Regards, > Dave > > Sent from my iPhone > > > On Sep 19, 2018, at 6:48 PM, Sid Anand wrote: > > > > Thanks Greg and Ismael! > > -s > > > >> On Wed, Sep 19, 2018 at 6:39 PM Greg Stein wrote: > >> > >> Hello all, > >> > >> The confusion here was "write access to the repository" (not allowed) > >> versus "write access to Pull Requests" (allowed). It took the Beam folks > >> some research to determine that GitHub *does* differentiate between > these > >> two write capabilities (historically, GitHub has not been very granular > >> with permissions). > >> > >> So. When Airflow said Probot Stale needed write access, we took that to > >> mean *code*. > >> > >> After the pointer to Beam, reminding Infra of the research Beam had done > >> (and my enabling of Stale for them) ... we realized that Stale *is* > >> perfectly fine because it doesn't touch the code repository. > >> > >> Probot Stale has been enabled for Airflow. > >> > >> Cheers, > >> Greg Stein > >> Infrastructure Administrator, ASF > >> > >> > >>> On Wed, Sep 19, 2018 at 7:47 PM Sid Anand wrote: > >>> > >>> Ismael, > >>> Thanks for this pointer. I've re-opened my INFRA ticket and referenced > >> your > >>> Apache Beam one. Super helpful.. if we get it enabled, please collect a > >>> beer from anyone in the Apache Airflow community! > >>> > >>> -s > >>> > On Wed, Sep 19, 2018 at 7:39 AM Ismaël Mejía > wrote: > > While I agree that autoclosing PRs can be unwelcoming. I don't see > clearly the argument of INFRA in the ticket. > > > The policy of no-write-access for bots is a requirement by the > foundation legal team. We cannot allow write access to repos without > an > ICLA. > > Labeling and closing the PR in github does not imply write-access from > the bot into the 'real' gitbox repository, so I don't see how this can > be an issue, or are we in a gray area (in case bot automation of > metadata can have legal issues which I doubt since this is not part of > the source distribution). > > As a precedent we had Probot/Stale enabled for Apache Beam so I > suppose that this should be possible for Airflow too. > https://issues.apache.org/jira/browse/INFRA-16589 > > > On Thu, Sep 13, 2018 at 5:55 PM Sid Anand wrote: > > > > Apache Airflow has, at any point, >200 PRs open. During the slower > >>> summer > > months, we've been merging 100-200 PRs a month. We have been growing > >>> the > > community -- we have <600 contributors, ~200 companies using it, and > >>> 20+ > > committers. A person is promoted to "Committer" in recognition for > >> work > > he/she has done without an expectation of future work in maintaining > >>> the > > code base. Hence, minting new committers doesn't always translate > >> into > > greater bench strength where merging PRs is concerned. That said, we > >>> are > > actively adding new committers. The last 4-5 committers we added have > been > > super active maintainers, so the coverage on PRs and questions has > >> been > > getting better. > > > > There are many causes of Cold-case PRs: > > > > 1. Submitter is not actively responding > > 1. One example is that we requested tests and they were never > written > > 2. Discussion ensued on the PR and the submitter did not accept > >>> the > > community's feedback > > 2. Committers didn't get to it in a timely manner and after a > >> while > the > > engagement fell > > > > We are in a better position now to handle (2) -- this was not the > >> case > >>> a > > year ago. We're at least able to keep up with our in-flow of PRs > > week-to-week, but are still having challenges with the > > previously-established backlog. But, (1) is also a contributor to > >> stale > PRs. > > > > We do have a lot of stale PRs to manually handle -- I spent all of > >>> Summer > > 2017 pinging submitters of old PRs and I find myself in the same > >>> position > > now. > > > > Probot/stale is a useful tool. It has legitimate use-cases. A policy > > reflects the health/mentality/approaches of the community. A tool > >> like > this > > enforces the policy. Let's not overlook adoption of what would be a > >>> very > > useful tool to the community due to a meta conversation about > >> policy. I > > think everyone on this list cares about growing a healthy and vibrant > > community. We also care about being efficient with our spare time. > >>> This > > tools can help us manage both. > > > > Also, I am not suggesting that we close JIRA, just stale PRs. JIRAs > >>> need >
Re: We want to contribute brpc to ASF, looking for champion and mentor ,please help
The IPMC might be too shallow a pool. Justin, can you email members@ for them with a draft of their proposal, perhaps? On 9/19/2018 9:16 PM, Tan,Zhongyi wrote: > Hi, JB, > > The proposal on wiki has been Updated. > > Add JB and Kevin as mentors. > > But we still look for champion, can someone help? > > Thanks > > > > 在 2018/9/19 下午1:53， "Jean-Baptiste Onofré" 写入: > >> Hi, >> >> sure. I think we can update the wiki with the proposal. >> >> Thoughts ? >> >> Regards >> JB >> >> On 19/09/2018 04:34, Tan,Zhongyi wrote: >>> Hi，JB， >>> >>> can we invite you as the mentor of brpc？ >>> >>> thanks >>> >>> >>> 在 2018/9/17 下午12:18， "Jean-Baptiste Onofré" 写入: >>> Hi, With great pleasure. I'm not sure I will contribute so much on the code, but I would be more than happy to help and guide the incubation. Regards JB On 17/09/2018 05:21, Tan,Zhongyi wrote: > Hi， JB > > Would you like to be champion for this project？ > > Thanks > > > 在 2018/9/14 下午5:20， "Jean-Baptiste Onofré" 写入: > >> Thanks for the details. It helps. >> >> Let me do a new pass on the proposal. >> >> Regards >> JB >> >> On 14/09/2018 10:19, Tan,Zhongyi wrote: >>> Hi， JB， >>> Below are our answers to your questions， >>> Please check， >>> Thanks. >>> >>> 1. brpc doesn't depend on any other Apache projects. brpc currently >>> depends on the following external project: >>>- leveldb >>>- openssl >>>- protobuf >>>- gperftools (optional) >>>- glog (optional) >>>- gtest >>> >>> 2. brpc is alternative for C++ rpc fcramework，implementations for >>> other >>> languages are not competitive enough (comparing to gRPC) to be >>> opensourced. Besides the basic RPC function, brpc(C++) provides >>> additional features than gRPC: >>>- Clients and servers can talk in multiple protocols: baidu >>> internal >>> protocol, http, thrift, http2(communicable with gRPC, the PR is >>> under >>> reviewing) and tens of other protocols. >>>- Proved better performance in different scenarios, by >>> eliminating >>> locks on hotpaths and using goroutine-like concurrency(bthread) with >>> cache >>> friendly data structures >>>- More useful debugging utilities to help C++ programers build >>> solid >>> online services. >>>- Various access patterns such as one-to-one, one-to-many(fan >>> out), >>> streaming, which simplify implementation of complex distributed >>> services. >>> >>> >>> >>> 在 2018/9/13 下午3:00， "Jean-Baptiste Onofré" 写入: >>> Hi, It's an interesting project. I have two questions: 1. do you have some interactions/dependencies with other Apache projects, especially CXF for instance ? 2. what's the comparison between brpc and gRPC ? An alternative ? Different features ? I might be interested by mentoring the project, I would like to understand exactly the target/purposes. Thanks ! Regards JB On 13/09/2018 08:20, Tan,Zhongyi wrote: > Hi, guys, > > brpc is one open source RPC framework that is very popular in > baidu > and > china. > We want to contribute it to ASF to make it more successful. > And we are looking for champion and mentor for this project, > if anyone would like to volunteer, we will be very appreciated. > > Thanks. > > > Here is the draft for brpc proposal. > > > # brpc Proposal > > ## Abstract > > brpc is an industrial-grade RPC framework for building reliable > and > high-performance services. > > ## Proposal > > We propose to contribute the brpc codebase and associated > artifacts(e.g. documentation etc.) to the Apache Software > Foundation, > and aim to build a wider open community around it in the 'Apache > Way'. > > > ## Background > > The RPC framework used in Baidu before 2014 was developed at 2008 > and > limited in protocols and performance, and there were also serveral > implementations focused on their own scenarios from Baidu's > different > BU. As an infrastructural team in Baidu, we tried to build a new > framework to unify all RPC scenarios inside. The framework was > named > "baidu-rpc" internally the early versions were adopted and online > at > late 2014. The framework was rapidly iterated at 2015-2017, and > thousands kinds of services and almost all core services adopted > it. > And
Re: [DISCUSS] Graduate Apache Servicecomb (incubating) as a TLP
+1 . Glad to see you are ready to graduate. -- Sheng Wu Apache SkyWalking -- Original -- From: "Roman Shaposhnik"; Date: Thu, Sep 20, 2018 02:44 PM To: "general"; Subject: [DISCUSS] Graduate Apache Servicecomb (incubating) as a TLP Hi! after an enthusiastic discussion with the community: https://lists.apache.org/thread.html/3fe85fb22cd1fd2c4e4a2370c03a453448a1ea12735d1e136cae6e79@%3Cdev.servicecomb.apache.org%3E culminating with a positive vote: https://lists.apache.org/thread.html/53f73695f8b504d1ed52e837cff9b8877e98c8a9c88668fc25188aca@%3Cdev.servicecomb.apache.org%3E we'd like to bring this to a discussing at the IPMC. Please see the proposed resolution below and let us know what do you think. A few stats to help with the discussion: 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. [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 Thanks, Roman. 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. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache Servicecomb (incubating) as a TLP
On Thu, Sep 20, 2018 at 8:44 AM Roman Shaposhnik wrote: > ...Please see the proposed resolution below and let us > know what do you think... +1 to the graduation and to the resolution. > ...Please check out Apache Maturity Model Assessment for ServiceComb[4] > for more information... Great example, I found it quite useful in assessing how the podling operates! Added to the examples at https://community.apache.org/apache-way/apache-project-maturity-model.html -Bertrand > [4]https://cwiki.apache.org/confluence/display/SERVICECOMB/Apache+Maturity+Model+Assessment+for+ServiceComb - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[DISCUSS] Graduate Apache Servicecomb (incubating) as a TLP
Hi! after an enthusiastic discussion with the community: https://lists.apache.org/thread.html/3fe85fb22cd1fd2c4e4a2370c03a453448a1ea12735d1e136cae6e79@%3Cdev.servicecomb.apache.org%3E culminating with a positive vote: https://lists.apache.org/thread.html/53f73695f8b504d1ed52e837cff9b8877e98c8a9c88668fc25188aca@%3Cdev.servicecomb.apache.org%3E we'd like to bring this to a discussing at the IPMC. Please see the proposed resolution below and let us know what do you think. A few stats to help with the discussion: 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. [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 Thanks, Roman. 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. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
