Re: We want to contribute brpc to ASF, looking for champion and mentor ,please help
Hi Zhongyi Tan, With Daffofil, Doris and eCharts I am mentoring three projects. I will watch this one as there are some similar challenges, but I don’t think I have time to Mentor this one. (I may pick up one other who have lost an inactive mentor.) All the best, Dave Sent from my iPhone > On Sep 17, 2018, at 9:11 PM, Tan,Zhongyi wrote: > > Thanks，Kevin. > > Your help is very appreciated. > We will add you to mentor list. > > > 在 2018/9/17 下午6:52， "Kevin A. McGrail" 写入: > >> Tan, I would be happy to help mentor this project as well. >> >>> On 9/17/2018 12:18 AM, Jean-Baptiste Onofré wrote: >>> 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 in 2017, we opensourced it as "brpc" and hope to get more adoptions and contributions from outside. At the time of opensourcing, there're more than 1
Re: We want to contribute brpc to ASF, looking for champion and mentor ,please help
Thanks，Kevin. Your help is very appreciated. We will add you to mentor list. 在 2018/9/17 下午6:52， "Kevin A. McGrail" 写入: >Tan, I would be happy to help mentor this project as well. > >On 9/17/2018 12:18 AM, Jean-Baptiste Onofré wrote: >> 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 >>> in 2017, we opensourced it as "brpc" and hope to get more adoptions >>> and >>> contributions from outside. At the time of opensourcing, there're >>>more >>> than 1 million instances inside Baidu using baidu-rpc (not counting >>> clients). >>> >>> >>> ## Rationale >>> >>> brpc has been approved inside baidu, since many high performance >>>core >>> services are using it. >>> And since its open source, it has been adopted by several other >>> companies, including Iqiyi, Didi, Sougou, BiliBili etc. >>> >>> ## Current Status >>> >>> brpc has been an open source project on GitHub >>> (https://github.com/brpc/brpc) since 2017. >>> >>> Currently
Re: [VOTE] Apache Gobblin 0.13.0 release RC2
Hi, I have removed the binary distribution from 0.13.0-rc2. Please see https://dist.apache.org/repos/dist/dev/incubator/gobblin/apache-gobblin-incubating-0.13.0-rc2/. Hung. From: Justin Mclean Sent: Monday, September 17, 2018 4:15:13 PM To: general@incubator.apache.org Subject: Re: [VOTE] Apache Gobblin 0.13.0 release RC2 Hi, > Thanks. Can we update the binary release with LICENSE, NOTICE and > DISCLAIMER without going through creating a new RC? IMO no, but ask your mentors on what they think or just release the source (once you get enough votes). Note also that the binary LICENSE and NOTICE files are likely to be significantly different to the source one, [1] Thanks, Justin 1. http://www.apache.org/dev/licensing-howto.html#binary - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Retire Gearpump podling
+1. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sun, Sep 16, 2018 at 5:32 PM Manu Zhang wrote: > > Hi mentors, > > The Gearpump podling has voted to retire from incubation. Here are the > relevant discussion and vote threads from the dev list. The vote passed > unanimously with 6 +1s. > > DISCUSS: > https://lists.apache.org/thread.html/77946cfff4557cf10c13c2d35fc165223583e58c2f7705319acabcf4@%3Cdev.gearpump.apache.org%3E > VOTE: > https://lists.apache.org/thread.html/03fc0421bb425f79d623863335bc2b81e4b6c77a169f508aadce7785@%3Cdev.gearpump.apache.org%3E > > Please vote to ratify this request for retirement. It will be open for at > least 72 hours. > > Thanks, > Manu Zhang - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Email to be sent to inactive mentors
On 17 September 2018 at 23:02, Dave Fisher wrote: > A mapping is made on id.apache.org and shown on whimsy. A patch to add a > github username column to the roster page in whimsy would make life easier. Please raise an enhancement JIRA . > Regards, > Dave > > Sent from my iPhone > >> On Sep 17, 2018, at 2:24 PM, Ted Dunning wrote: >> >> Indeed. >> >> And even if it seems obvious, that isn't always obviously correct. >> Establishing a mapping or using an Apache ID is important. >> >>> On Mon, Sep 17, 2018 at 4:45 PM Dave Fisher wrote: >>> >>> Github id does not often equal Apache id. It is not always obvious. >>> >>> Regards, >>> Dave >>> >>> Sent from my iPhone >>> On Sep 17, 2018, at 12:35 PM, Ted Dunning wrote: Obviously, lots of informational activity occurs off the mailing list. A great example is answering questions on stack overflow. And ApacheCon >>> talks which actually led to certain decisions being made should definitely be echoed back to the mailing list. But apart from all of that GitHub issues should definitely be mirrored >>> back to the mailing list. There's no way to justify that an issue tracker is not echoed back. > On Mon, Sep 17, 2018, 14:05 Julian Hyde wrote: > > By that argument there’s no point speaking at ApacheCon. Because it > doesn’t happen on a mailing list. > > So let’s not be so strict. > > Clearly there are many ways that a mentor can assist. Some of them are >>> not > measurable (such as having a phone call). But I think any measurable > activity should count. > > Julian > > >> On Sep 17, 2018, at 8:55 AM, sebb wrote: >> >> On 17 September 2018 at 12:10, Justin Mclean >>> > wrote: >>> Hi, >>> Maybe I am missing something here, but how would GitHub contributions > contribute to mentoring? >>> >>> Well I thought it wouldn't which is why I didn’t include it, but as > some projects use GitHub issues a lot, so some stuff tends to get >>> discussed > there rather than on the dev list. >> >> "If it did not happen on a mailing list then it did not happen" >> If the GitHub issues are not being copied to the mailing lists, then >> again I don't see how that contributes to the mentoring process. >> >>> There’s a few other factors in this case, but I think it’s on it way >>> to > being sorted. I'll bring it to the mentors attention and see what they > think. (Sorry for being obtuse, but this is a public list.) >> >>> 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 >> > > > - > 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 >>> >>> > > > - > 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
Re: [VOTE] Apache Gobblin 0.13.0 release RC2
Hi, > Thanks. Can we update the binary release with LICENSE, NOTICE and > DISCLAIMER without going through creating a new RC? IMO no, but ask your mentors on what they think or just release the source (once you get enough votes). Note also that the binary LICENSE and NOTICE files are likely to be significantly different to the source one, [1] Thanks, Justin 1. http://www.apache.org/dev/licensing-howto.html#binary - 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): OpenWhisk catalog and apigateway 0.9.0 [RC1]
Hi, +1 (binding) I checked: - incubating in name - signatures sand hashed correct - DISCLAIMER exists - LICENSE and NOTICE correct - No unexpected binary files - all source file have ASF header, but I noticed a number of .js files don’t have the full header. Any reason for this? - could compile but it doesn’t do much (but I assume that is expected) Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Gobblin 0.13.0 release RC2
Thanks. Can we update the binary release with LICENSE, NOTICE and DISCLAIMER without going through creating a new RC? Those warnings are known. Thanks, Abhishek On Mon, Sep 17, 2018 at 3:58 PM Justin Mclean wrote: > Hi, > > +1 (binding) to the source release but -1 (binding) to the binary release > as it is missing LICENSE, NOTICE and DISCLAIMER. > > I checked: > - incubating in name > - hashes and signatures good > - DISCLAIMER exists > - LICENSE and NOTICE fine > - all source files have ASF headers > - no unexpected binary files > - can compile from source > > BTW I got a number of warnings along these lines when building, I assume > this is a known issue and OK? > javadoc: warning - Error fetching URL: > https://hive.apache.org/javadocs/r1.0.1/api/ > > Thanks, > Justin > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Apache Gobblin 0.13.0 release RC2
Hi, +1 (binding) to the source release but -1 (binding) to the binary release as it is missing LICENSE, NOTICE and DISCLAIMER. I checked: - incubating in name - hashes and signatures good - DISCLAIMER exists - LICENSE and NOTICE fine - all source files have ASF headers - no unexpected binary files - can compile from source BTW I got a number of warnings along these lines when building, I assume this is a known issue and OK? javadoc: warning - Error fetching URL: https://hive.apache.org/javadocs/r1.0.1/api/ Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[ANNOUNCE] Apache MXNet (incubating) 1.3.0 Release
Hello all, The Apache MXNet (incubating) Community announces the availability of Apache MXNet (incubating) 1.3.0! Release blog post: https://blogs.apache.org/mxnet/entry/announcing-apache-mxnet-incubating-1 https://medium.com/apache-mxnet/announcing-apache-mxnet-1-3-0-484ea78c22ad Apache MXNet (incubating) is a deep learning framework designed for both efficiency and flexibility. It allows you to mix symbolic and imperative programming to maximize efficiency and productivity. This release improves usability, performance, and interoperability. A full list of the changes in this release can be found in the release notes: https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+%28incubating%29+1.3.0+Release+Notes A Link to the Download is here: https://www.apache.org/dyn/closer.cgi/incubator/mxnet/1.3.0 If you prefer to build from source and experiment with various compile-time configuration options, use this link to get the instructions: http://mxnet.incubator.apache.org/install/index.html Or You can download and play with MXNet easily using one of the options below: 1. The Pip packages can be found here: https://pypi.python.org/pypi/mxnet 2. The Docker Images can be found here: https://hub.docker.com/r/mxnet/python/ Links in Maven to the published Scala packages: https://repository.apache.org/content/repositories/releases/org/apache/mxnet/ https://repository.apache.org/#nexus-search;quick~org.apache.mxnet and to the experimental Clojure packages: https://repository.apache.org/content/repositories/releases/org/apache/mxnet/contrib/clojure/ The release tag used for the 1.3.0 release is: https://github.com/apache/incubator-mxnet/tree/1.3.0 Some more MXNet Resources: 1. Issues: https://github.com/apache/incubator-mxnet/issues 2. Wiki: https://cwiki.apache.org/confluence/display/MXNET If you want to learn more about MXNet visit http://mxnet.incubator.apache.org/ Finally, you are welcome to join and also invite your friends to the dynamic and growing MXNet community by subscribing to d...@mxnet.incubator.apache.org Acknowledgments: We would like to thank everyone who contributed to the 1.3.0 release: Aaron Markham, Abhinav Sharma, access2rohit, Alex Li, Alexander Alexandrov, Alexander Zai, Amol Lele, Andrew Ayres, Anirudh Acharya, Anirudh Subramanian, Ankit Khedia, Anton Chernov, aplikaplik, Arunkumar V Ramanan, Asmus Hetzel, Aston Zhang, bl0, Ben Kamphaus, brli, Burin Choomnuan, Burness Duan, Caenorst, Cliff Woolley, Carin Meier, cclauss, Carl Tsai, Chance Bair, chinakook, Chudong Tian, ciyong, ctcyang, Da Zheng, Dang Trung Kien, Deokjae Lee, Dick Carter, Didier A., Eric Junyuan Xie, Faldict, Felix Hieber, Francisco Facioni, Frank Liu, Gnanesh, Hagay Lupesko, Haibin Lin, Hang Zhang, Hao Jin, Hao Li, Haozhi Qi, hasanmua, Hu Shiwen, Huilin Qu, Indhu Bharathi, Istvan Fehervari, JackieWu, Jake Lee, James MacGlashan, jeremiedb, Jerry Zhang, Jian Guo, Jin Huang, jimdunn, Jingbei Li, Jun Wu, Kalyanee Chendke, Kellen Sunderland, Kovas Boguta, kpmurali, Kurman Karabukaev, Lai Wei, Leonard Lausen, luobao-intel, Junru Shao, Lianmin Zheng, Lin Yuan, lufenamazon, Marco de Abreu, Marek Kolodziej, Manu Seth, Matthew Brookhart, Milan Desai, Mingkun Huang, miteshyh, Mu Li, Nan Zhu, Naveen Swamy, Nehal J Wani, PatricZhao, Paul Stadig, Pedro Larroy, perdasilva, Philip Hyunsu Cho, Pishen Tsai, Piyush Ghai, Pracheer Gupta, Przemyslaw Tredak, Qiang Kou, Qing Lan, qiuhan, Rahul Huilgol, Rakesh Vasudevan, Ray Zhang, Robert Stone, Roshani Nagmote, Sam Skalicky, Sandeep Krishnamurthy, Sebastian Bodenstein, Sergey Kolychev, Sergey Sokolov, Sheng Zha, Shen Zhu, Sheng-Ying, Shuai Zheng, slitsey, Simon, Sina Afrooze, Soji Adeshina, solin319, Soonhwan-Kwon, starimpact, Steffen Rochel, Taliesin Beynon, Tao Lv, Thom Lane, Thomas Delteil, Tianqi Chen, Todd Sundsted, Tong He, Vandana Kannan, vdantu, Vishaal Kapoor, wangzhe, xcgoner, Wei Wu, Wen-Yang Chu, Xingjian Shi, Xinyu Chen, yifeim, Yizhi Liu, YouRancestor, Yuelin Zhang, Yu-Xiang Wang, Yuan Tang, Yuntao Chen, Zach Kimberg, Zhennan Qin, Zhi Zhang, zhiyuan-huang, Ziyue Huang, Ziyi Mu, Zhuo Zhang. … and thanks to all of the Apache MXNet community supporters, spreading knowledge and helping to grow the community! Thanks! Apache MXNet (incubating) Team ___ DISCLAIMER: Apache MXNet (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the name of Apache Incubator PMC. 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: [VOTE] Apache Gobblin 0.13.0 release RC2
Sure, I will ping them. Meanwhile, would love it if others can also review :) Regards, Abhishek On Mon, Sep 17, 2018 at 3:35 PM Justin Mclean wrote: > Hi, > > Your mentors are IPMC and can vote on this release, perhaps you could ask > them. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Apache Gobblin 0.13.0 release RC2
Hi, Your mentors are IPMC and can vote on this release, perhaps you could ask them. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Gobblin 0.13.0 release RC2
Ping. Can someone help us review and vote :) Regards Abhishek On Tue, Sep 11, 2018 at 2:59 PM Abhishek Tiwari wrote: > +1 > > Abhishek > > On Tue, Sep 11, 2018 at 2:51 PM Hung Tran wrote: > >> Adding some CCs since the message was not received. >> >> Hung. >> -- >> *From:* Hung Tran >> *Sent:* Monday, September 10, 2018 9:51:31 PM >> *To:* general@incubator.apache.org >> *Subject:* [VOTE] Apache Gobblin 0.13.0 release RC2 >> >> The Apache Gobblin community has voted on and approved the release of >> Apache Gobblin 0.13.0 (incubating): >> >> >> https://www.mail-archive.com/dev@gobblin.incubator.apache.org/msg02175.html >> >> Results: >> 3 binding +1 votes >> No 0 votes >> No -1 votes >> >> The feedback from previous release candidates has been addressed: >> >> RC1 thread: >> https://www.mail-archive.com/general@incubator.apache.org/msg64403.html >> Resolution: >> Removed the binary release tar from the source release tar. >> >> I'd like to call a vote in general to approve the release. >> >> The source release candidate RC2 with convenience binaries can be >> downloaded here: >> https://dist.apache.org/repos/dist/dev/incubator/gobblin/apache-gobblin >> -incubating-0.13.0-rc2/ >> >> The artifacts (i.e. JARs) corresponding to this release candidate can be >> found here: >> https://repository.apache.org/content/repositories/orgapachegobblin-1007 >> >> This has been signed with PGP key 0x9BB772F1,corresponding to >> hut...@apache.org, which is included in the repository's KEYS file ( >> https://dist.apache.org/repos/dist/release/incubator/gobblin/KEYS). This >> key can be found on keyservers, such as: >> http://pgp.mit.edu/pks/lookup?op=get=0x9BB772F1 >> >> >> The release candidate has been tagged with release-0.13.0-rc2. >> I've also created a branch 0.13.0. >> >> >> For reference, here is a list of all closed JIRAs tagged with 0.13.0: >> https://issues.apache.org/jira/issues/?filter=12343492 >> >> For a summary of the changes in this release, see: >> https://github.com/apache/incubator-gobblin/blob/0.13.0/CHANGELOG.md >> >> Please review and vote. The vote will be open for at least 72 hours. >> >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >> >> Thanks, >> Hung, on behalf of the Apache Gobblin PPMC >> >> >>
RE: Mentor capactity of the incubator
For my part I remain an IPMC member, while not having the time to mentor, because I take mentorship extremely seriously. If I'm not going to be able to read (or at least scan) every mail thread during the early days and be ready to respond quickly at key stages of the process then I'm not willing to sign up. What this translates to is I'll only step up when the project has personal interest to me. A number of times in recent months I have "nearly" thrown my hat into the ring, only to step back when I see that there are already mentors on the project that I trust to do a good job. Ross -Original Message- From: Greg Stein Sent: Sunday, September 16, 2018 4:29 AM To: general@incubator.apache.org Subject: Re: Mentor capactity of the incubator On Sun, Sep 16, 2018 at 2:18 AM Justin Mclean wrote: >... > For IPMC members who are unable to be a mentor I’m curious to know > what the reasons are, I’m sure that “not having the time" is probably > the number one reason, but are is there any thing else stopping member > (in particular first time ones) from coming forward and volunteering? > For myself, it is because I conflate my personal time into my job time, working on Infra-related stuff. I've found that I cannot distinguish my ASF time between the two aspects, so cannot reliably provide dedicated ASF time to personal stuff. I remain on the IPMC, however, because I *do* find that I can be responsive to Incubator-related concerns. (and I do the same for other ASF projects; responsive time, rather than allocated time) Cheers, -g - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Email to be sent to inactive mentors
A mapping is made on id.apache.org and shown on whimsy. A patch to add a github username column to the roster page in whimsy would make life easier. Regards, Dave Sent from my iPhone > On Sep 17, 2018, at 2:24 PM, Ted Dunning wrote: > > Indeed. > > And even if it seems obvious, that isn't always obviously correct. > Establishing a mapping or using an Apache ID is important. > >> On Mon, Sep 17, 2018 at 4:45 PM Dave Fisher wrote: >> >> Github id does not often equal Apache id. It is not always obvious. >> >> Regards, >> Dave >> >> Sent from my iPhone >> >>> On Sep 17, 2018, at 12:35 PM, Ted Dunning wrote: >>> >>> Obviously, lots of informational activity occurs off the mailing list. A >>> great example is answering questions on stack overflow. And ApacheCon >> talks >>> which actually led to certain decisions being made should definitely be >>> echoed back to the mailing list. >>> >>> But apart from all of that GitHub issues should definitely be mirrored >> back >>> to the mailing list. There's no way to justify that an issue tracker is >>> not echoed back. >>> On Mon, Sep 17, 2018, 14:05 Julian Hyde wrote: By that argument there’s no point speaking at ApacheCon. Because it doesn’t happen on a mailing list. So let’s not be so strict. Clearly there are many ways that a mentor can assist. Some of them are >> not measurable (such as having a phone call). But I think any measurable activity should count. Julian > On Sep 17, 2018, at 8:55 AM, sebb wrote: > > On 17 September 2018 at 12:10, Justin Mclean >> wrote: >> Hi, >> >>> Maybe I am missing something here, but how would GitHub contributions contribute to mentoring? >> >> Well I thought it wouldn't which is why I didn’t include it, but as some projects use GitHub issues a lot, so some stuff tends to get >> discussed there rather than on the dev list. > > "If it did not happen on a mailing list then it did not happen" > If the GitHub issues are not being copied to the mailing lists, then > again I don't see how that contributes to the mentoring process. > >> There’s a few other factors in this case, but I think it’s on it way >> to being sorted. I'll bring it to the mentors attention and see what they think. (Sorry for being obtuse, but this is a public list.) > >> 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 > - 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 >> >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Email to be sent to inactive mentors
Indeed. And even if it seems obvious, that isn't always obviously correct. Establishing a mapping or using an Apache ID is important. On Mon, Sep 17, 2018 at 4:45 PM Dave Fisher wrote: > Github id does not often equal Apache id. It is not always obvious. > > Regards, > Dave > > Sent from my iPhone > > > On Sep 17, 2018, at 12:35 PM, Ted Dunning wrote: > > > > Obviously, lots of informational activity occurs off the mailing list. A > > great example is answering questions on stack overflow. And ApacheCon > talks > > which actually led to certain decisions being made should definitely be > > echoed back to the mailing list. > > > > But apart from all of that GitHub issues should definitely be mirrored > back > > to the mailing list. There's no way to justify that an issue tracker is > > not echoed back. > > > >> On Mon, Sep 17, 2018, 14:05 Julian Hyde wrote: > >> > >> By that argument there’s no point speaking at ApacheCon. Because it > >> doesn’t happen on a mailing list. > >> > >> So let’s not be so strict. > >> > >> Clearly there are many ways that a mentor can assist. Some of them are > not > >> measurable (such as having a phone call). But I think any measurable > >> activity should count. > >> > >> Julian > >> > >> > >>> On Sep 17, 2018, at 8:55 AM, sebb wrote: > >>> > >>> On 17 September 2018 at 12:10, Justin Mclean > > >> wrote: > Hi, > > > Maybe I am missing something here, but how would GitHub contributions > >> contribute to mentoring? > > Well I thought it wouldn't which is why I didn’t include it, but as > >> some projects use GitHub issues a lot, so some stuff tends to get > discussed > >> there rather than on the dev list. > >>> > >>> "If it did not happen on a mailing list then it did not happen" > >>> If the GitHub issues are not being copied to the mailing lists, then > >>> again I don't see how that contributes to the mentoring process. > >>> > There’s a few other factors in this case, but I think it’s on it way > to > >> being sorted. I'll bring it to the mentors attention and see what they > >> think. (Sorry for being obtuse, but this is a public list.) > >>> > 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 > >>> > >> > >> > >> - > >> 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 > >
Re: Email to be sent to inactive mentors
On Mon, Sep 17, 2018 at 4:43 PM Justin Mclean wrote: > Hi, > > > But apart from all of that GitHub issues should definitely be mirrored > back > > to the mailing list. There's no way to justify that an issue tracker is > > not echoed back. > > They were not being, but that’s being changed, and the mentor is now > signed up to the dev list where they were not before. > That is awesome progress. > Mentoring is different to the PPMC making decisions, and while it best for > it to be in an open and archived place, I don't think all mentoring > activity has to be on the mailing list. > That is sooo very true. Particularly with personality issues, it can be enormously better to coach quietly in the background. The desired outcome is constructive behavior in public. Private coaching can let the personality in question demonstrate a pattern of doing better in public which can set the entire community on a better track. Having the mentor be a highly visible player in that can be highly counter productive especially if the mentor is going to leave the community after graduation. > I still have some concerns about the amount of off-list communication but > that a separate issue. Indeed. And that is a great opportunity to mentor the mentor so that they can better mentor the community.
Re: Email to be sent to inactive mentors
Github id does not often equal Apache id. It is not always obvious. Regards, Dave Sent from my iPhone > On Sep 17, 2018, at 12:35 PM, Ted Dunning wrote: > > Obviously, lots of informational activity occurs off the mailing list. A > great example is answering questions on stack overflow. And ApacheCon talks > which actually led to certain decisions being made should definitely be > echoed back to the mailing list. > > But apart from all of that GitHub issues should definitely be mirrored back > to the mailing list. There's no way to justify that an issue tracker is > not echoed back. > >> On Mon, Sep 17, 2018, 14:05 Julian Hyde wrote: >> >> By that argument there’s no point speaking at ApacheCon. Because it >> doesn’t happen on a mailing list. >> >> So let’s not be so strict. >> >> Clearly there are many ways that a mentor can assist. Some of them are not >> measurable (such as having a phone call). But I think any measurable >> activity should count. >> >> Julian >> >> >>> On Sep 17, 2018, at 8:55 AM, sebb wrote: >>> >>> On 17 September 2018 at 12:10, Justin Mclean >> wrote: Hi, > Maybe I am missing something here, but how would GitHub contributions >> contribute to mentoring? Well I thought it wouldn't which is why I didn’t include it, but as >> some projects use GitHub issues a lot, so some stuff tends to get discussed >> there rather than on the dev list. >>> >>> "If it did not happen on a mailing list then it did not happen" >>> If the GitHub issues are not being copied to the mailing lists, then >>> again I don't see how that contributes to the mentoring process. >>> There’s a few other factors in this case, but I think it’s on it way to >> being sorted. I'll bring it to the mentors attention and see what they >> think. (Sorry for being obtuse, but this is a public list.) >>> 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 >>> >> >> >> - >> 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
Re: Email to be sent to inactive mentors
Hi, > But apart from all of that GitHub issues should definitely be mirrored back > to the mailing list. There's no way to justify that an issue tracker is > not echoed back. They were not being, but that’s being changed, and the mentor is now signed up to the dev list where they were not before. Mentoring is different to the PPMC making decisions, and while it best for it to be in an open and archived place, I don't think all mentoring activity has to be on the mailing list. I still have some concerns about the amount of off-list communication but that a seperate issue. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Email to be sent to inactive mentors
Obviously, lots of informational activity occurs off the mailing list. A great example is answering questions on stack overflow. And ApacheCon talks which actually led to certain decisions being made should definitely be echoed back to the mailing list. But apart from all of that GitHub issues should definitely be mirrored back to the mailing list. There's no way to justify that an issue tracker is not echoed back. On Mon, Sep 17, 2018, 14:05 Julian Hyde wrote: > By that argument there’s no point speaking at ApacheCon. Because it > doesn’t happen on a mailing list. > > So let’s not be so strict. > > Clearly there are many ways that a mentor can assist. Some of them are not > measurable (such as having a phone call). But I think any measurable > activity should count. > > Julian > > > > On Sep 17, 2018, at 8:55 AM, sebb wrote: > > > > On 17 September 2018 at 12:10, Justin Mclean > wrote: > >> Hi, > >> > >>> Maybe I am missing something here, but how would GitHub contributions > contribute to mentoring? > >> > >> Well I thought it wouldn't which is why I didn’t include it, but as > some projects use GitHub issues a lot, so some stuff tends to get discussed > there rather than on the dev list. > > > > "If it did not happen on a mailing list then it did not happen" > > If the GitHub issues are not being copied to the mailing lists, then > > again I don't see how that contributes to the mentoring process. > > > >> There’s a few other factors in this case, but I think it’s on it way to > being sorted. I'll bring it to the mentors attention and see what they > think. (Sorry for being obtuse, but this is a public list.) > > > >> 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 > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Email to be sent to inactive mentors
By that argument there’s no point speaking at ApacheCon. Because it doesn’t happen on a mailing list. So let’s not be so strict. Clearly there are many ways that a mentor can assist. Some of them are not measurable (such as having a phone call). But I think any measurable activity should count. Julian > On Sep 17, 2018, at 8:55 AM, sebb wrote: > > On 17 September 2018 at 12:10, Justin Mclean wrote: >> Hi, >> >>> Maybe I am missing something here, but how would GitHub contributions >>> contribute to mentoring? >> >> Well I thought it wouldn't which is why I didn’t include it, but as some >> projects use GitHub issues a lot, so some stuff tends to get discussed there >> rather than on the dev list. > > "If it did not happen on a mailing list then it did not happen" > If the GitHub issues are not being copied to the mailing lists, then > again I don't see how that contributes to the mentoring process. > >> There’s a few other factors in this case, but I think it’s on it way to >> being sorted. I'll bring it to the mentors attention and see what they >> think. (Sorry for being obtuse, but this is a public list.) > >> 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 > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Pulsar Release 2.1.1-incubating Candidate 1
The vote is now closed for Pulsar Release 2.1.1-incubating Candidate with 3 +1s and no -1s. Binding +1s: * Dave Fisher * Jim Jagielski * Willem Jiang Thank you, On Fri, Sep 14, 2018 at 11:38 AM Jerry Peng wrote: > Can other mentors and members of the incubator PMC review the release > please. Thank you! > > Best, > > Jerry > > On Thu, Sep 13, 2018 at 7:16 AM Jim Jagielski wrote: > >> +1 on release... and +1 on removing the SHA-1s >> >> > On Sep 11, 2018, at 7:34 PM, Henk P. Penning wrote: >> > >> > On Wed, 12 Sep 2018, Jerry Peng wrote: >> > >> >> Date: Wed, 12 Sep 2018 00:31:35 +0200 >> >> From: Jerry Peng >> >> To: general@incubator.apache.org >> >> Cc: d...@pulsar.incubator.apache.org >> >> Subject: [VOTE] Pulsar Release 2.1.1-incubating Candidate 1 >> >> This is the first release candidate for Apache Pulsar, version >> >> 2.1.1-incubating. >> > >> >> Source and binary files: >> >> >> https://dist.apache.org/repos/dist/dev/incubator/pulsar/pulsar-2.1.1-incubating-candidate-1/ >> > >> >> SHA-1 checksums: >> > >> > Hi, >> > >> > SHA-1 checksum files shouldn't be publish checksums anymore. >> > >> > https://www.apache.org/dev/release-distribution#sigs-and-sums >> > >> > Please remove ; the vote may continue. >> > >> > Thanks ; regards, >> > >> > Henk Penning >> > >> > _ >> > Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ >> > Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ >> > Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ >> > http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ >> > >> >> 506c172b13c1581f9b52769a4c6594541628b928 >> >> apache-pulsar-2.1.1-incubating-bin.tar.gz >> >> de3a74449a78d0713998544237dde59765ee121f >> >> apache-pulsar-2.1.1-incubating-src.tar.gz >> >> 1d38554e58cfd733fc2d54ec1442747daeb8fc1b >> >> apache-pulsar-io-connectors-2.1.1-incubating-bin.tar.gz >> >> >> >> Maven staging repo: >> >> >> https://repository.apache.org/content/repositories/orgapachepulsar-1026 >> >> >> >> The tag to be voted upon: >> >> v2.1.1-incubating-candidate-1 68faf85083025b29bb6ab39028a1d467bd3d5217 >> >> >> https://github.com/apache/incubator-pulsar/releases/tag/v2.1.1-incubating-candidate-1 >> >> >> >> Pulsar's KEYS file containing PGP keys we use to sign the release: >> >> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS >> >> >> >> Please download the the source package, and follow the README to build >> and >> >> run the Pulsar standalone service. >> >> >> >> Here is a guide for validating a release candidate: >> >> >> https://github.com/apache/incubator-pulsar/wiki/Release-Candidate-Validation >> >> >> >>
Re: Mentor capactity of the incubator
I'm interested in being a mentor at some point, though I'd prefer to help with a project in a domain I'm experienced with. On Sun, 16 Sep 2018 at 10:26, Willem Jiang wrote: > Hi > > From my podling experience, it's really hard for a new podling > project to find a mentor by himself, so sometime new podling project > just ask help in the mailing list. > The warm hearted mentors who response the mail will be put put into > the podling proposal, and we never ask them about if they have time to > perform the duty of mentor. > Maybe we can setup a reminder email once the mentor is adding to the > podling project to let him know about the role, duties, and how much > time he need to put into the Podling project. In this way, we may > reduce the inactive mentor situations in the future. > > But how much time do we need to spend for mentoring the project. From > my experience, there are some work for the project initial setup and > release mentoring, but other time,the mentor just need to keep an eye > on the project and response the question from Podling projects. But > it could be different from project to project, so please add your > comments here. > > BTW, it's hard for the podling project to ask for release checking as > there are only few IPMC members vote the release kit. If we talk about > the Mentor capacity, IMO we need to take this issue into > consideration. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Sun, Sep 16, 2018 at 3:18 PM Justin Mclean > wrote: > > > > Hi, > > > > We have a large number of IPMC members (280+). I wondering if any IPMC > members could indicate if they have any capacity/free cycles and a > willingness for mentoring projects. It looks like we are going to have a > number of inactive mentors step down in the near future and we may end up > with some podlings only having one or two mentors. Three mentors seems to > the the number that works best. > > > > Of course I understand it may have to be the right sort of project, but > I’m just trying the gauge the current mentor capacity of the incubator, so > if you think you could be a mentor if the right project came along then > please indicate it here. > > > > For IPMC members who are unable to be a mentor I’m curious to know what > the reasons are, I’m sure that “not having the time" is probably the number > one reason, but are is there any thing else stopping member (in particular > first time ones) from coming forward and volunteering? > > > > The mentor capacity we have may in the future have an impact on if and > how often we accept new podlings. I'd hate to turn away podlings, but if we > can’t effectively mentor them I’m not sure what else we can do. anyone have > any ideas? > > > > For myself currently I could only realistically mentor one more project. > > > > 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 > > -- Matt Sicker
Re: [VOTE] Retire Gearpump podling
+1 On Mon, 17 Sep 2018 at 04:33, Justin Mclean wrote: > +1 > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Matt Sicker
Re: Email to be sent to inactive mentors
On 17 September 2018 at 12:10, Justin Mclean wrote: > Hi, > >> Maybe I am missing something here, but how would GitHub contributions >> contribute to mentoring? > > Well I thought it wouldn't which is why I didn’t include it, but as some > projects use GitHub issues a lot, so some stuff tends to get discussed there > rather than on the dev list. "If it did not happen on a mailing list then it did not happen" If the GitHub issues are not being copied to the mailing lists, then again I don't see how that contributes to the mentoring process. > There’s a few other factors in this case, but I think it’s on it way to being > sorted. I'll bring it to the mentors attention and see what they think. > (Sorry for being obtuse, but this is a public list.) > 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
Re: Email to be sent to inactive mentors
Hi, > Maybe I am missing something here, but how would GitHub contributions > contribute to mentoring? Well I thought it wouldn't which is why I didn’t include it, but as some projects use GitHub issues a lot, so some stuff tends to get discussed there rather than on the dev list. There’s a few other factors in this case, but I think it’s on it way to being sorted. I'll bring it to the mentors attention and see what they think. (Sorry for being obtuse, but this is a public list.) Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Email to be sent to inactive mentors
On 17 September 2018 at 02:39, Justin Mclean wrote: > Hi, > > Current 1/3 of those asked have responded with: > -17 mentors have asked to retire/step down > - 3 will continue (including one who asked to step down but changed their > mind and has been added back) > > Of the total above 1 mentor was miss-identified as missing as they are mostly > active in GitHub and not on the mailing list. Maybe I am missing something here, but how would GitHub contributions contribute to mentoring? Or are you just looking for any activity rather than mentoring activity itself? > 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
Re: We want to contribute brpc to ASF, looking for champion and mentor ,please help
Tan, I would be happy to help mentor this project as well. On 9/17/2018 12:18 AM, Jean-Baptiste Onofré wrote: > 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 >> in 2017, we opensourced it as "brpc" and hope to get more adoptions >> and >> contributions from outside. At the time of opensourcing, there're more >> than 1 million instances inside Baidu using baidu-rpc (not counting >> clients). >> >> >> ## Rationale >> >> brpc has been approved inside baidu, since many high performance core >> services are using it. >> And since its open source, it has been adopted by several other >> companies, including Iqiyi, Didi, Sougou, BiliBili etc. >> >> ## Current Status >> >> brpc has been an open source project on GitHub >> (https://github.com/brpc/brpc) since 2017. >> >> Currently it has more than 7.3k stars, 1.6k forks, and is one of the >> most popular repositories in topic of rpc category in GitHub rpc >> catelogy. >> It has been widely used in Baidu, with 1,000,000+ instances and >> thousands kinds of services. >> Besides, many other companies have already used it also, such as >> Iqiyi,
Re: [VOTE] Retire Gearpump podling
+1 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE]- Release Apache Weex (Incubating) 0.19.0 [RC4]
Here are the vote threads of RC4. Vote: https://lists.apache.org/thread.html/cdfd9cc5b9ade0bd86fc35a8e56fb76d45b1a785b1025de67f5b@%3Cdev.weex.apache.org%3E Vote Result: https://lists.apache.org/thread.html/935ccb2ee4ccfe7a9e775aabb155770dd1b7157fcc89ed0369b92998@%3Cdev.weex.apache.org%3E Best Regards, Hanks Zhang
