Re: Committer/PPMC votes
Interesting. Foundation-wise, all our votes are Majority Voting (new member vote, board vote (ish), votes by the board themselves, omnibus voting). There's little expectation/requirement of consensus. Jakarta/Commons wise new committer votes felt that way (Majority); however both of those were large PMCs. Disagreement was more likely than on a smaller PMC so the reality was that we needed Majority instead of Consensus. The mantra was always "votes on code (technical) had veto, everything else was majority". But it was also, to your point, a strong culture to avoid relying on majority-overrule of a veto. Thus new release votes always felt like Consensus voting even if the rule says Majority voting. I think the release voting ( https://www.apache.org/foundation/voting.html#ReleaseVotes ) is similar to new committer votes. It's Majority Voting, but the Release Manager does hold a veto. I'd expect a PMC Chair to have a similar role in a new committer vote. "As Chair I consider the -1 from Alice to be a blocking veto; we need to discuss more". That doesn't work with Podlings though as there's no (local) buck-stops-here chair. It feels like there's an inconsistency between https://www.apache.org/foundation/voting.html and https://community.apache.org/newcommitter.html . Either we update newcommitter.html to explain that it's a Majority vote, but explain how unusual it should be to see -1 after discussion; or voting.html needs updating to explain that most (or all?) projects use Consensus voting to add committers (and presumably PMC members too). On most projects using consensus voting for committers/pmc; it feels that it's hard to tell the difference. If there are no -1s, a consensus and majority vote look the same. :) Hen On Thu, Jun 21, 2018 at 5:48 PM, Justin Mclean wrote: > > Hi, > > Way back when each project having a set of bylaws/guidelines was > fashionable I looked through them and there is some variation but a -1 on a > committer or PMC member is generally treated as a veto. That being said any > objections should really come up in the discussion stage (and hopefully > mitigated) before a vote is called so a -1 vote should be rare. If you look > at [1] [2] you see that consensus voting allows for a veto (with a reason) > and AFAIK most projects use consensus approval when adding committers/PMC > members. It may be some don’t realise this as a -1 has never come up. > > Thanks, > Justin > > 1. https://www.apache.org/foundation/voting.html > 2. https://www.apache.org/foundation/glossary.html#ConsensusApproval > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Committer/PPMC votes
Hi, > Agreed. It does not discuss having a [DISCUSS] thread before the [VOTE]. It > is important to do that because then an objection (-1) can be discussed > properly. There can be many reasons that a PMC member might object and these > need to expressed. Not doing so might lose PMC members and hurt the community. > > I wanted to give this advice recently and was rather disappointed that I > could not find documentation about an actual [DISCUSS] thread. Perhaps this? [1] Justin 1. https://community.apache.org/committers/voting.html#preparing-for-a-vote - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Committer/PPMC votes
Hi, Way back when each project having a set of bylaws/guidelines was fashionable I looked through them and there is some variation but a -1 on a committer or PMC member is generally treated as a veto. That being said any objections should really come up in the discussion stage (and hopefully mitigated) before a vote is called so a -1 vote should be rare. If you look at [1] [2] you see that consensus voting allows for a veto (with a reason) and AFAIK most projects use consensus approval when adding committers/PMC members. It may be some don’t realise this as a -1 has never come up. Thanks, Justin 1. https://www.apache.org/foundation/voting.html 2. https://www.apache.org/foundation/glossary.html#ConsensusApproval - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Committer/PPMC votes
> On Jun 21, 2018, at 5:20 PM, Hen wrote: > > I’m wondering what a -1 means on a committer vote. > > https://community.apache.org/newcommitter.html says “and no vetoes”, while > https://www.apache.org/foundation/voting.html does not list a new committer > vote as a “technical” vote. > > My assumption is that the rules for voting for an Apache member are the > same as for voting for a PMC member or a committer. Ideally there are no > -1s, but at the end of the day it’s a majority vote. > > ie: I think newcommitter.html is buggy. Agreed. It does not discuss having a [DISCUSS] thread before the [VOTE]. It is important to do that because then an objection (-1) can be discussed properly. There can be many reasons that a PMC member might object and these need to expressed. Not doing so might lose PMC members and hurt the community. I wanted to give this advice recently and was rather disappointed that I could not find documentation about an actual [DISCUSS] thread. Regards, Dave > > Thoughts? > > Hen signature.asc Description: Message signed with OpenPGP
Committer/PPMC votes
I’m wondering what a -1 means on a committer vote. https://community.apache.org/newcommitter.html says “and no vetoes”, while https://www.apache.org/foundation/voting.html does not list a new committer vote as a “technical” vote. My assumption is that the rules for voting for an Apache member are the same as for voting for a PMC member or a committer. Ideally there are no -1s, but at the end of the day it’s a majority vote. ie: I think newcommitter.html is buggy. Thoughts? Hen
[RESULT] [VOTE] Release Apache ServiceComb Java-Chassis (Incubating) version 1.0.0-m2
Hello All, We are glad to announce that vote to release Apache ServiceComb Java-Chassis (incubating) 1.0.0-m2 has passed with following results: +1 binding : 3 (Willem Jiang, Jean-Baptiste Onofre, Mick Semb Wever) Vote Thread : https://lists.apache.org/thread.html/c4d7cb5b0f0e7693c8cee8b8c8cd1bc79b84392b7dfe50ffc96a6ca0@%3Cgeneral.incubator.apache.org%3E We will be publishing the release shortly and send the announcement. Thanks All for helping us to verify this release. On the behalf of ServiceComb Team Mohammad Asif Siddiqui - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ServiceComb Java-Chassis (Incubating) version 1.0.0-m2
Hello All, This vote is closed now, we will publish the results shortly. Thanks All for the participation in this vote. Regards Asif On 2018/06/18 16:10:07, Mohammad Asif Siddiqui wrote: > Hi All, > > This is a call for vote to release Apache ServiceComb Java-Chassis > (Incubating) version 1.0.0-m2 > > Apache ServiceComb (Incubating) Community has voted and approved the release. > > > Vote Thread : > https://lists.apache.org/thread.html/587081b895bf02d69bea82a24760fa59cb93f50dbe07064d0e630d4a@%3Cdev.servicecomb.apache.org%3E > > > Result Thread : > https://lists.apache.org/thread.html/c9e5c5289c26f82e9c4b9046f097ba5f9a863e3376836d9ad72ef134@%3Cdev.servicecomb.apache.org%3E > > > Release Notes : > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12342355 > > > Release Candidate : > https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-java-chassis/1.0.0-m2/rc-02/ > > > Staging Repo : > https://repository.apache.org/content/repositories/orgapacheservicecomb-1303/ > > Release Tag : > https://github.com/apache/incubator-servicecomb-java-chassis/releases/tag/1.0.0-m2 > > > Release CommitID : 95e87f4791218c45ddb9b8eed0a4073873432034 > > Keys to verify the Release Candidate : > https://dist.apache.org/repos/dist/dev/incubator/servicecomb/KEYS > > Voting will start now ( Monday, 18th June, 2018) and will remain open for > atleast 72 hours, Request all IPMC members to give their vote. > > [ ] +1 Release this package as 1.0.0-m2 > [ ] +0 No Opinion > [ ] -1 Do not release this package because > > On the behalf of ServiceComb Team > Mohammad Asif Siddiqui > > > - > 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: Looking for Champion
Looks great! On Thu, Jun 21, 2018 at 5:06 AM Li,De(BDG) wrote: > We have a general Plan or Roadmap: > > 1. Find out the code, modules, components which duplicates of Impala; > 2. Determine the features which could be merged to Impala under Impala > community support. > 3, Define clearly the interface between the query engine and other > components, such as the storage engine, metadata management, mysql server, > load and export modules, web server and so on. > 4. Separate the Impala query engine from Palo. > > > Best Regards, > Reed > > On 2018/6/19 下午9:48， "Jim Apple" wrote: > > >> > >> I'm not sure if Palo is just a storage system but definitely we will > >> separate query engine from Palo. > >> > > > >That's great news, and I think it will benefit users of Impala and Palo. > > > > > >> Of cource, as you mentioned, "this could be a lot of work", so it will > >> take a long time and we also hope that Impala community could support > >>us. > >> > > > >Yes, I expect so. > >
Re: Looking for Champion
We have a general Plan or Roadmap: 1. Find out the code, modules, components which duplicates of Impala; 2. Determine the features which could be merged to Impala under Impala community support. 3, Define clearly the interface between the query engine and other components, such as the storage engine, metadata management, mysql server, load and export modules, web server and so on. 4. Separate the Impala query engine from Palo. Best Regards, Reed On 2018/6/19 下午9:48， "Jim Apple" wrote: >> >> I'm not sure if Palo is just a storage system but definitely we will >> separate query engine from Palo. >> > >That's great news, and I think it will benefit users of Impala and Palo. > > >> Of cource, as you mentioned, "this could be a lot of work", so it will >> take a long time and we also hope that Impala community could support >>us. >> > >Yes, I expect so.
Re: Looking for Champion
Hi Dave, We have a new name Doris, so we will rename Palo to Doris. I have updated proposal as following: #Apache Doris ##Abstract Doris is a MPP-based interactive SQL data warehousing for reporting and analysis. ##Proposal We propose to contribute the Doris codebase and associated artifacts (e.g. documentation, web-site content etc.) to the Apache Software Foundation, and aim to build an open community around Doris’s continued development in the ‘Apache Way’. ###Overview of Doris Doris’s implementation consists of two daemons: Frontend (FE) and Backend (BE). **Frontend daemon** consists of query coordinator and catalog manager. Query coordinator is responsible for receiving users’ sql queries, compiling queries and managing queries execution. Catalog manager is responsible for managing metadata such as databases, tables, partitions, replicas and etc. Several frontend daemons could be deployed to guarantee fault-tolerance, and load balancing. **Backend daemon** stores the data and executes the query fragments. Many backend daemons could also be deployed to provide scalability and fault-tolerance. A typical Doris cluster generally composes of several frontend daemons and dozens to hundreds of backend daemons. Users can use MySQL client tools to connect any frontend daemon to submit SQL query. Frontend receives the query and compiles it into query plans executable by the Backend. Then Frontend sends the query plan fragments to Backend. Backend will build a query execution DAG. Data is fetched and pipelined into the DAG. The final result response is sent to client via Frontend. The distribution of query fragment execution takes minimizing data movement and maximizing scan locality as the main goal. ##Background At Baidu, Prior to Doris, different tools were deployed to solve diverse requirements in many ways. And when a use case requires the simultaneous availability of capabilities that cannot all be provided by a single tool, users were forced to build hybrid architectures that stitch multiple tools together, but we believe that they shouldn’t need to accept such inherent complexity. A storage system built to provide great performance across a broad range of workloads provides a more elegant solution to the problems that hybrid architectures aim to solve. Doris is the solution. Doris is designed to be a simple and single tightly coupled system, not depending on other systems. Doris provides high concurrent low latency point query performance, but also provides high throughput queries of ad-hoc analysis. Doris provides bulk-batch data loading, but also provides near real-time mini-batch data loading. Doris also provides high availability, reliability, fault tolerance, and scalability. ##Rationale Doris mainly integrates the technology of Google Mesa and Apache Impala. Mesa is a highly scalable analytic data storage system that stores critical measurement data related to Google's Internet advertising business. Mesa is designed to satisfy complex and challenging set of users’ and systems’ requirements, including near real-time data ingestion and query ability, as well as high availability, reliability, fault tolerance, and scalability for large data and query volumes. Impala is a modern, open-source MPP SQL engine architected from the ground up for the Hadoop data processing environment. At present, by virtue of its superior performance and rich functionality， Impala has been comparable to many commercial MPP database query engine. Mesa can satisfy the needs of many of our storage requirements, however Mesa itself does not provide a SQL query engine; Impala is a very good MPP SQL query engine, but the lack of a perfect distributed storage engine. So in the end we chose the combination of these two technologies. Learning from Mesa’s data model, we developed a distributed storage engine. Unlike Mesa, this storage engine does not rely on any distributed file system. Then we deeply integrate this storage engine with Impala query engine. Query compiling, query execution coordination and catalog management of storage engine are integrated to be frontend daemon; query execution and data storage are integrated to be backend daemon. With this integration, we implemented a single, full-featured, high performance state the art of MPP database, as well as maintaining the simplicity. ##Current Status Doris has been an open source project on GitHub (https://github.com/baidu/palo). ###Meritocracy Doris has been deployed in production at Baidu and is applying more than 200 lines of business. It has demonstrated great performance benefits and has proved to be a better way for reporting and analysis based big data. Still We look forward to growing a rich user and developer community. ###Community Doris seeks to develop developer and user communities during incubation. ###Core Developers * Ruyue Ma (https://github.com/maruyue, maru...@baidu.com) *
Re: [ANNOUNCE] Apache SINGA (incubating) 1.2.0 released
Dear Craig and sebb, Thank you. The download page is fixed now. Best regards, Moaz On Fri, Jun 15, 2018 at 5:14 PM sebb wrote: > Also you only need one KEYS link, and there should be a description of > how to use KEYS + sig or hash to verify the downloads. > > On 15 June 2018 at 14:12, Craig Russell wrote: > > Dear Singa project, > > > > Please update your download page to add links to the ASC signature files > for each of the artifacts. > > > > Regards, > > > > Craig > > > >> On Jun 14, 2018, at 6:51 PM, Moaz Reyad wrote: > >> > >> We are pleased to announce that SINGA (incubating) 1.2.0 is released. > >> > >> SINGA is a general distributed deep learning platform for training big > deep > >> learning models over large datasets. It is designed with an intuitive > >> programming model based on the layer abstraction. SINGA supports a wide > >> variety of popular deep learning models. > >> > >> The release is available at: > >> http://singa.apache.org/en/downloads.html > >> > >> The main features of this release include: > >> > >> -Implement autograd (currently support MLP model) > >> -Upgrade PySinga to support Python 3 > >> -Improve the Tensor class with the stride field > >> -Upgrade cuDNN from V5 to V7 > >> -Add VGG, Inception V4, ResNet, and DenseNet for ImageNet > classification > >> -Create alias for conda packages > >> -Complete documentation in Chinese > >> -Add instructions for running SINGA on Windows > >> -Update the compilation, CI > >> > >> We look forward to hearing your feedback, suggestions and contributions > to > >> the project. > >> > >> On behalf of the SINGA team, > >> Moaz Reyad > > > > Craig L Russell > > c...@apache.org > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > >
Re: [VOTE] Release Apache ServiceComb Java-Chassis (Incubating) version 1.0.0-m2
+1 (binding) Casting my vote on IPMC. Regards JB On 18/06/2018 18:10, Mohammad Asif Siddiqui wrote: > Hi All, > > This is a call for vote to release Apache ServiceComb Java-Chassis > (Incubating) version 1.0.0-m2 > > Apache ServiceComb (Incubating) Community has voted and approved the release. > > > Vote Thread : > https://lists.apache.org/thread.html/587081b895bf02d69bea82a24760fa59cb93f50dbe07064d0e630d4a@%3Cdev.servicecomb.apache.org%3E > > > Result Thread : > https://lists.apache.org/thread.html/c9e5c5289c26f82e9c4b9046f097ba5f9a863e3376836d9ad72ef134@%3Cdev.servicecomb.apache.org%3E > > > Release Notes : > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12342355 > > > Release Candidate : > https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-java-chassis/1.0.0-m2/rc-02/ > > > Staging Repo : > https://repository.apache.org/content/repositories/orgapacheservicecomb-1303/ > > Release Tag : > https://github.com/apache/incubator-servicecomb-java-chassis/releases/tag/1.0.0-m2 > > > Release CommitID : 95e87f4791218c45ddb9b8eed0a4073873432034 > > Keys to verify the Release Candidate : > https://dist.apache.org/repos/dist/dev/incubator/servicecomb/KEYS > > Voting will start now ( Monday, 18th June, 2018) and will remain open for > atleast 72 hours, Request all IPMC members to give their vote. > > [ ] +1 Release this package as 1.0.0-m2 > [ ] +0 No Opinion > [ ] -1 Do not release this package because > > On the behalf of ServiceComb Team > Mohammad Asif Siddiqui > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT] [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m2
Hello All, We are glad to announce that vote to release Apache ServiceComb Service-Center (incubating) 1.0.0-m2 has passed with following results: +1 binding : 3 (Willem Jiang, Luke Han, Mick Semb Wever) Vote Thread : https://lists.apache.org/thread.html/8c824f26ac1133d7dbac074fd0f4d3f42576dbcf2ab7722e8654f14b@%3Cgeneral.incubator.apache.org%3E We will be publishing the release shortly and send the announcement. Thanks All for helping us to verify this release. On the behalf of ServiceComb Team Mohammad Asif Siddiqui - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT] [VOTE] Release Apache ServiceComb Saga (incubating) version 0.2.0
Hello All, We are glad to announce that vote to release Apache ServiceComb Saga (incubating) 0.2.0 has passed with the following results: +1 binding : 3 (Willem Jiang, Luke Han, Mick Semb Wever) Vote Thread : https://lists.apache.org/thread.html/5bf8a551450f25c226ec2139448512ea1b272182eb1476a216de5465@%3Cgeneral.incubator.apache.org%3E We will be publishing the release shortly and send the announcement. Thanks All for helping us to verify this release. On the behalf of ServiceComb Team Mohammad Asif Siddiqui - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m2
Hello All, This vote is closed now, we will publish the results shortly. Thanks All for the participation in this vote. Regards Asif On 2018/06/12 08:36:01, Mohammad Asif Siddiqui wrote: > Hello All, > > This is a call for vote to release Apache ServiceComb Service-Center > (Incubating) version 1.0.0-m2. > Apache ServiceComb (Incubating) Community has voted and approved the release > > > Vote Thread : > https://lists.apache.org/thread.html/2c979af45fd37ecf944c783844240f3874b96713997f2fc2a0bd71fc@%3Cdev.servicecomb.apache.org%3E > > > Result Thread : > https://lists.apache.org/thread.html/2b7548c13deec4f563c41d3cc6daab16fd3b691ec9b48bd54caad2d8@%3Cdev.servicecomb.apache.org%3E > > > Release Notes : > https://github.com/apache/incubator-servicecomb-service-center/blob/master/docs/release/releaseNotes-1.0.0-m2.md > > > Release Candidate : > https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-service-center/1.0.0-m2/rc-01/ > > > Release Tag : > https://github.com/apache/incubator-servicecomb-service-center/releases/tag/1.0.0-m2 > > > Release CommitID : b913a2de1b5f7fb2a42ac719fe5891d5f46f349d > > Keys to verify the Release Candidate : > https://dist.apache.org/repos/dist/dev/incubator/servicecomb/KEYS > > Guide to build the release from source : > https://github.com/apache/incubator-servicecomb-service-center/tree/master/scripts/release > > > Voting will start now(Tuesday, 12th June, 2018) and will remain open for next > 72 hours, Request all IPMC members to give their vote. > > [ ] +1 Release this package as 1.0.0-m2 > [ ] +0 No Opinion > [ ] -1 Do not release this package because... > > On the behalf of ServiceComb Team > Mohammad Asif Siddiqui > > > - > 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] Release Apache ServiceComb Saga (incubating) version 0.2.0
Hello All, This vote is closed now, we will publish the results shortly. Thanks All for the participation in this vote. Regards Asif On 2018/06/12 09:12:02, Mohammad Asif Siddiqui wrote: > Hello All, > > This is a call for vote to release Apache ServiceComb Saga (Incubating) > version 0.2.0 > > Apache ServiceComb (Incubating) Community has voted and approved the release. > > > Vote Thread : > https://lists.apache.org/thread.html/fd0c4593d8574563e1a247cf2bed5a72d66a317472e4d9ee597433fc@%3Cdev.servicecomb.apache.org%3E > > > Result Thread : > https://lists.apache.org/thread.html/77f0360d12ca2352c9052a112ba0e4f06c028132909f84d71eca3bcd@%3Cdev.servicecomb.apache.org%3E > > > 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 Repo : > 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 ( Tuesday, 12th June, 2018) and will remain open for > next 72 hours, We request all IPMC 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 > > > - > 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
