Re: [DISCUSS] [VOTE] HCatalog to Graduate and become part of Apache Hive
Thanks Alan, I'm still wondering why the Hive PMC feel mentoring inside the PMC is appropriate but not the IPMC. Please understand I'm not saying I'm for or against the proposal. I'm trying to understand it so that I can form an opinion as an IPMC member. Ross Sent from a mobile device, please excuse mistakes and brevity On 20 Feb 2013 18:22, "Alan Gates" wrote: > The project was named Howl when it was proposed, so the proposal is at > http://wiki.apache.org/incubator/HowlProposal > > Alan. > > On Feb 20, 2013, at 2:31 AM, Ross Gardler wrote: > > > I'm brought to this thread byt he board report but my response here is as > > an IPMC member. My comment on the board report is quite different, it is > > "I've read the thread on general@ and feel that the IPMC should make a > > clear recommendation to the board in this and similar cases. The IPMC > > discussion seems to be healthy and productive." > > > > So, as a an IPMC member I have a few open questions [inline]... > > > > > > On 11 February 2013 18:20, Alan Gates wrote: > > > >> > >> > > Also, it has been agreed that each HCatalog committer will be provided > with > >> a mentor from the Hive community to help him/her learn the rest of Hive, > >> with the goal of becoming a committer on Hive within six months. The > >> submodule state is transitionary, not an end point. > >> > >> > > Why was this"mentoring" not done as part of the incubation process since > > building the right community structure for graduation (along with IP > > clearance) is the main role of the incubation process? Was Hive the > > sponsoring project for this proposal? If not why not? > > > > I ask these questions because HCatlog is making a very strong case that > any > > other option for graduation is not appropriate. At the same time we are > > being told by the Hive PMC that the mentoring of the committers is > > incomplete since they have insufficient merit within Hive to be trusted > to > > be full members of that project. > > > > it also concerns me that in this same month the IPMC board report says > "The > > main concern of the incubator continues to be the quality and reliability > > of supervision... The supply of mentoring seems, still, to exceed > demand." > > > > Why is it that the Hive PMC feels it is able to provide "mentoring" > within > > their own PMC through the creation of what some people see as > > an umbrella project, but not here in the IPMC? > > > > Finally, why can't I find the HCatalog proposal in my mail client, > markmail > > or the wiki (not had coffee yet, feel free to call me [insert adjective]) > > > > Ross > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
[CANCEL][VOTE] Release Apache VXQuery Incubating 0.2 (RC1)
Thanks for the review. I am cancelling the vote to address the issues that sebb identified and to create a new RC. Till On Feb 22, 2013, at 7:50 AM, sebb wrote: > On 22 February 2013 06:56, Till Westmann wrote: >> Please verify and vote on the first release candidate for our first release >> apache-vxquery-0.2-incubating-RC1. >> Since this is our first release we would appreciate a thorough review. >> >> The tag to be voted on is >> >> https://svn.apache.org/repos/asf/incubator/vxquery/tags/apache-vxquery-0.2-incubating-RC1 > > NOTICE says: > Apache VXQuery > Copyright 2001-2008 The Apache Software Foundation > > I think that's probably wrong. > > There are README files under / and under docs/ > > The latter should probably be merged into / > > It would be helpful if the README file included a brief description of > the software. > > src/main/assembly/source.xml does not have an AL header. > > A lot of files don't have the correct SVN eol properties. See separate > JIRA issue > https://issues.apache.org/jira/browse/VXQUERY-84 > > >> The artifacts, md5s, and signatures are at: > > sigs and md5 are OK, but the md5 format is non-standard and may not be > supported by all automatic hash checkers. > > Since the hashes are all in separate files, there is no need for the > file name to be present. > But if it is, it should be on the same line as the hash, which does > not need embedded spaces. > > For example, see > > https://dist.apache.org/repos/dist/release/httpd/httpd-2.4.4.tar.gz.[md5|sha1] > >> http://people.apache.org/~tillw/apache-vxquery-0.2-incubating-RC1/ > > The site pages don't appear to have any download links. > > The developer tips page mentions "Hyracks" without any explanation as > to what that is. > >> and the KEYS file containing the PGP keys used to sign the release can >> currently be found at >> >> https://dist.apache.org/repos/dist/release/incubator/vxquery/KEYS >> >> The RAT reports for the are at >> http://people.apache.org/~tillw/apache-vxquery-0.2-incubating-RC1/site/vxquery-core/rat-report.html >> http://people.apache.org/~tillw/apache-vxquery-0.2-incubating-RC1/site/vxquery-cli/rat-report.html >> http://people.apache.org/~tillw/apache-vxquery-0.2-incubating-RC1/site/vxquery-xtest/rat-report.html >> >> The vote on vxquery-dev passed [1] with >> >> +1 (binding) >> Vinayak Borkar >> Mike Carey >> Paul Fremantle (IPMC) >> Jochen Wiedmann (IPMC) >> >> +1 (non-binding) >> Eldon Carman >> >> -1 >> none >> >> Please vote >> [ ] +1 release this package as apache-vxquery-0.2-incubating >> [ ] -1 do not release this package because ... >> >> Thanks, >> Till >> >> >> [1] >> http://mail-archives.apache.org/mod_mbox/incubator-vxquery-dev/201302.mbox/%3c038dfec4-7e89-4595-9838-d8f45e7b4...@westmann.org%3e >> - >> 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: [DISCUSS] [VOTE] HCatalog to Graduate and become part of Apache Hive
I think that's a question for the Hive PMC. I have some guesses, but it seemd more appropriate to let them speak for themselves. For some history you can take a look at http://mail-archives.apache.org/mod_mbox/hive-dev/201211.mbox/%3CC648B9DE-2088-465E-8FA1-590D5E192093%40hortonworks.com%3E which is the initial discussion between HCat and Hive. AFAIK none of the Hive PMC are on the IPMC, so you may need to mail private@hive or dev@hive to get their feedback. Alan. On Feb 23, 2013, at 2:43 AM, Ross Gardler wrote: > Thanks Alan, > > I'm still wondering why the Hive PMC feel mentoring inside the PMC is > appropriate but not the IPMC. > > Please understand I'm not saying I'm for or against the proposal. I'm > trying to understand it so that I can form an opinion as an IPMC member. > > Ross > > Sent from a mobile device, please excuse mistakes and brevity > On 20 Feb 2013 18:22, "Alan Gates" wrote: > >> The project was named Howl when it was proposed, so the proposal is at >> http://wiki.apache.org/incubator/HowlProposal >> >> Alan. >> >> On Feb 20, 2013, at 2:31 AM, Ross Gardler wrote: >> >>> I'm brought to this thread byt he board report but my response here is as >>> an IPMC member. My comment on the board report is quite different, it is >>> "I've read the thread on general@ and feel that the IPMC should make a >>> clear recommendation to the board in this and similar cases. The IPMC >>> discussion seems to be healthy and productive." >>> >>> So, as a an IPMC member I have a few open questions [inline]... >>> >>> >>> On 11 February 2013 18:20, Alan Gates wrote: >>> >>> Also, it has been agreed that each HCatalog committer will be provided >> with a mentor from the Hive community to help him/her learn the rest of Hive, with the goal of becoming a committer on Hive within six months. The submodule state is transitionary, not an end point. >>> Why was this"mentoring" not done as part of the incubation process since >>> building the right community structure for graduation (along with IP >>> clearance) is the main role of the incubation process? Was Hive the >>> sponsoring project for this proposal? If not why not? >>> >>> I ask these questions because HCatlog is making a very strong case that >> any >>> other option for graduation is not appropriate. At the same time we are >>> being told by the Hive PMC that the mentoring of the committers is >>> incomplete since they have insufficient merit within Hive to be trusted >> to >>> be full members of that project. >>> >>> it also concerns me that in this same month the IPMC board report says >> "The >>> main concern of the incubator continues to be the quality and reliability >>> of supervision... The supply of mentoring seems, still, to exceed >> demand." >>> >>> Why is it that the Hive PMC feels it is able to provide "mentoring" >> within >>> their own PMC through the creation of what some people see as >>> an umbrella project, but not here in the IPMC? >>> >>> Finally, why can't I find the HCatalog proposal in my mail client, >> markmail >>> or the wiki (not had coffee yet, feel free to call me [insert adjective]) >>> >>> Ross >> >> >> - >> 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: [DISCUSS] [VOTE] HCatalog to Graduate and become part of Apache Hive
FYI, at this point based on Benson and Roy's feedback I have been considering this vote closed and passed. We're moving forward with the details of merging the two, which will include winding down the incubator project. Mail has been sent to dev@hive and hcatalog-dev to propose the details of the path forward. Alan. On Feb 23, 2013, at 2:43 AM, Ross Gardler wrote: > Thanks Alan, > > I'm still wondering why the Hive PMC feel mentoring inside the PMC is > appropriate but not the IPMC. > > Please understand I'm not saying I'm for or against the proposal. I'm > trying to understand it so that I can form an opinion as an IPMC member. > > Ross > > Sent from a mobile device, please excuse mistakes and brevity > On 20 Feb 2013 18:22, "Alan Gates" wrote: > >> The project was named Howl when it was proposed, so the proposal is at >> http://wiki.apache.org/incubator/HowlProposal >> >> Alan. >> >> On Feb 20, 2013, at 2:31 AM, Ross Gardler wrote: >> >>> I'm brought to this thread byt he board report but my response here is as >>> an IPMC member. My comment on the board report is quite different, it is >>> "I've read the thread on general@ and feel that the IPMC should make a >>> clear recommendation to the board in this and similar cases. The IPMC >>> discussion seems to be healthy and productive." >>> >>> So, as a an IPMC member I have a few open questions [inline]... >>> >>> >>> On 11 February 2013 18:20, Alan Gates wrote: >>> >>> Also, it has been agreed that each HCatalog committer will be provided >> with a mentor from the Hive community to help him/her learn the rest of Hive, with the goal of becoming a committer on Hive within six months. The submodule state is transitionary, not an end point. >>> Why was this"mentoring" not done as part of the incubation process since >>> building the right community structure for graduation (along with IP >>> clearance) is the main role of the incubation process? Was Hive the >>> sponsoring project for this proposal? If not why not? >>> >>> I ask these questions because HCatlog is making a very strong case that >> any >>> other option for graduation is not appropriate. At the same time we are >>> being told by the Hive PMC that the mentoring of the committers is >>> incomplete since they have insufficient merit within Hive to be trusted >> to >>> be full members of that project. >>> >>> it also concerns me that in this same month the IPMC board report says >> "The >>> main concern of the incubator continues to be the quality and reliability >>> of supervision... The supply of mentoring seems, still, to exceed >> demand." >>> >>> Why is it that the Hive PMC feels it is able to provide "mentoring" >> within >>> their own PMC through the creation of what some people see as >>> an umbrella project, but not here in the IPMC? >>> >>> Finally, why can't I find the HCatalog proposal in my mail client, >> markmail >>> or the wiki (not had coffee yet, feel free to call me [insert adjective]) >>> >>> Ross >> >> >> - >> 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] Accept Apache Knox Hadoop Gateway Project into the Incubator
Hi folks, With 10 binding +1 votes, this vote has passed. Thanks to everyone who voted. Devaraj. +1 (binding) On Feb 15, 2013, at 11:22 AM, Devaraj Das wrote: > Hi Folks, > > Thanks for participating in the discussion. I'd like to call a VOTE > for acceptance of Apache Knox Hadoop Gateway Project into the > Incubator. The vote will close on Feb 22 at 6:00 p.m. > > [ ] +1 Accept Apache Knox Hadoop Gateway Project into the Incubator > [ ] +0 Don't care. > [ ] -1 Don't accept Apache Knox Hadoop Gateway Project into the > Incubator because... > > Full proposal is pasted at the bottom of this email, and the > corresponding wiki is http://wiki.apache.org/incubator/knox. Only > VOTEs from Incubator PMC members are binding. > > Here's my +1 (binding). > > Thanks, > Devaraj. > > - > > Knox Gateway Proposal > > Abstract > > Knox Gateway is a system that provides a single point of secure access > for Apache Hadoop clusters. > > Proposal > > The Knox Gateway (“Gateway” or “Knox”) is a system that provides a > single point of authentication and access for Apache Hadoop services > in a cluster. The goal is to simplify Hadoop security for both users > (i.e. who access the cluster data and execute jobs) and operators > (i.e. who control access and manage the cluster). The Gateway runs as > a server (or cluster of servers) that serve one or more Hadoop > clusters. > > Provide perimeter security to make Hadoop security setup easier > Support authentication and token verification security scenarios > Deliver users a single cluster end-point that aggregates capabilities > for data and jobs > Enable integration with enterprise and cloud identity management environments > > Background > > An Apache Hadoop cluster is presented to consumers as a loose > collection of independent services. This makes it difficult for users > to interact with Hadoop since each service maintains it’s own method > of access and security. As well, for operators, configuration and > administration of a secure Hadoop cluster is a complex and many Hadoop > clusters are insecure as a result. > > The goal of the project is to provide coverage for all existing Hadoop > ecosystem projects. In addition, the project will be extensible to > allow for new and/or proprietary Hadoop components without requiring > changes to the gateway source code. The gateway is expected to run in > a DMZ environment where it will provide controlled access to these > Hadoop services. In this way Hadoop clusters can be protected by a > firewall and only limited access provided through the firewall for the > gateway. The authentication components of the gateway will be modular > and extensible such that it can be integrated with existing security > infrastructure. > > Rationale > > Organizations that are struggling with Hadoop cluster security result > in a) running Hadoop without security or b) slowing adoption of > Hadoop. The Gateway aims to provide perimeter security that integrates > more easily into existing organizations’ security infrastructure. > Doing so will simplify security for these organizations and benefit > all Hadoop stakeholders (i.e. users and operators). Additionally, > making a dedicated perimeter security project part of the Apache > Hadoop ecosystem will prevent fragmentation in this area and further > increase the value of Hadoop as a data platform. > > Current Status > > Prototype available, developed by the list of initial committers. > > Meritocracy > > We desire to build a diverse developer community around Gateway > following the Apache Way. We want to make the project open source and > will encourage contributors from multiple organizations following the > Apache meritocracy model. > > Community > > We hope to extend the user and developer base in the future and build > a solid open source community around Gateway. Apache Hadoop has a > large ecosystem of open source projects, each with a strong community > of contributors. All project communities in this ecosystem have an > opportunity to participate in the advancement of the Gateway project > because ultimately, Gateway will enable the security capabilities of > their project to be more enterprise friendly. > > Core Developers > > Gateway is currently being developed by several engineers from > Hortonworks - Kevin Minder, Larry McCay, John Speidel, Tom Beerbower > and Sumit Mohanty. All the engineers have deep expertise in > middleware, security & identity systems and are quite familiar with > the Hadoop ecosystem. > > Alignment > > The ASF is a natural host for Gateway given that it is already the > home of Hadoop, Hive, Pig, HBase, Oozie and other emerging big data > software projects. Gateway is designed to solve the security > challenges familiar to the Hadoop ecosystem family of projects. > > Known Risks > > Orphaned products & Reliance on Salaried Developers > > The core developers plan to work full time on the project. We believe > that this project will be of general i
