RE: [PROPOSAL] Phoenix for Incubation
+1 (non-binding) for incubation of Phoenix. This is already a very useful project for HBase users, and it will be good to see it driven by a larger community. It may be also be good to get a legal opinion about the name, and/or check for an alternative. There may be some existing software products with this name (e.g. http://www.opwglobal.com/Product.aspx?pid=342). Regards Priyank Rastogi -Original Message- From: James Taylor [mailto:jtay...@salesforce.com] Sent: 14 November 2013 02:14 To: general@incubator.apache.org Subject: [PROPOSAL] Phoenix for Incubation Hi All, We're pleased to share a draft ASF incubation proposal for Phoenix, a SQL layer over HBase, initially developed at Salesforce.com and subsequently open sourced on github (https://github.com/forcedotcom/phoenix). Instead of using Map-reduce to processes queries, it compiles SQL directly into native HBase calls. The complete proposal can be found here: https://wiki.apache.org/incubator/PhoenixProposal, and is also pasted below. Your feedback is greatly appreciated. James == Abstract == Phoenix is an open source SQL query engine for Apache HBase, a NoSQL data store. It is accessed as a JDBC driver and enables querying and managing HBase tables using SQL. == Proposal == Phoenix is an open source SQL skin over HBase delivered as a client-embedded JDBC driver targeting low latency queries over HBase data. Phoenix takes your SQL query, compiles it into a series of HBase scans, and orchestrates the running of those scans to produce regular JDBC result sets. The table metadata is stored in an HBase table and versioned, such that snapshot queries over prior versions will automatically use the correct schema. Direct use of the HBase API, along with coprocessors and custom filters, results in performance on the order of milliseconds for small queries, or seconds for tens of millions of rows. Phoenix interfaces with both Pig and Map-reduce for the input and output of data. == Background == Phoenix initially started as an internal project at Salesforce.com to efficiently analyze big data stored in HBase. It was open sourced on Github about a year ago in Jan 2013. Over time Phoenix, together with HBase as the storage tier, has begun to evolve into a general SQL database with support for metadata management, secondary indexes, joins, query optimization, and multi-tenancy. This is expected to continue as Phoenix implements a cost-based query optimizer and potentially transaction support, and surfaces new HBase security features such as encryption and cell-level security. Phoenix's developer community has also grown to include additional companies such as Intel, who have contributed join support to Phoenix, as well as Hortonworks, who are in the process of porting Phoenix to the 0.96 release of HBase. == Rationale == As usage and the number of contributors to Phoenix has grown, we have sought for a long-term home for the project, and we believe the Apache foundation would be a great fit. Joining Apache would ensure that tried and true processes and procedures are in place for the growing number of organizations interested in contributing to Phoenix. Phoenix is also a good fit for the Apache foundation: Phoenix already interoperates with several existing Apache projects (HBase, Hadoop, Pig). The Phoenix team is familiar with the Apache process and and believes in the Apache mission - the team already includes multiple Apache committers. == Initial Goals == The initial goals will be to move the existing codebase to Apache and integrate with the Apache development process. Once this is accomplished, we plan for incremental development and releases that follow the Apache guidelines. == Current Status == Phoenix has undergone two major and three minor releases (1.0, 1.1, 1.2, 2.0, and 2.1) as well as many patch releases. Phoenix is being used in production by Salesforce.com as well as at other organizations. The Phoenix codebase is currently hosted at github.com, which will form the basis of the Apache git repository. === Meritocracy === The Phoenix project already operates on meritocratic principles. Phoenix has several developers from various organizations outside of Salesforce.com who have contributed major new features. While this process has remained mostly informal, as we do not have an official committer list, an implicit organization exists in which individuals who contribute major components act as maintainers for those modules. If accepted, the Phoenix project would include several of these participants as initial committers. We will work to identify all committers and PPMC members for the project and to operate under the ASF meritocratic principles. === Community === Acceptance into the Apache foundation would bolster the already strong user and developer community around Phoenix. That community includes many contributors from various other companies, and an active mailing list c
Re: Cultivating Outstanding IP Stewards
Hi Benson, On Sun, Nov 17, 2013 at 10:12 PM, Benson Margulies wrote: > If the board were offering us another structural approach, this would > be a different discussion. But, unless I've gotten lost in the torrent > of email, the board isn't offering an alternative. Yep you must have gotten lost. The board _is_ open alternatives and trying some experiments. Roy said this here on general@, several others have said that on board@. Our working assumption should be that they'll ok us trying some things. Also, given the diverse and disparate group that make up the Incubator PMC I hope everyone can try to have an open mind about experiments and not try to block people trying things just because its not what they personally think will work or is the best experiment. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Cultivating Outstanding IP Stewards
On 17/11/13 11:17, Upayavira wrote: On Sun, Nov 17, 2013, at 04:59 AM, Alex Harui wrote: On 11/16/13 8:47 AM, "Upayavira" wrote: Alex, I'm not sure I see the difference between a release auditor and an IPMC member. If someone is sufficiently clued up to audit a release, then they're surely ready to join the Incubator PMC. Am I missing something? To me, there is more responsibility in being on the IPMC, like reviewing proposals for new podlings and voting on their graduation and becoming a mentor. Personally, that's why I don't want to be on the IPMC, but I might be willing to help IP audit a podling's release. Just like some projects don't have all committers on the PMC, a Release Auditor is just someone who can do that specific task, and there is no need to vote them in if they are already on some other TLP PMC because any member of a TLP PMC supposedly knows how to do release auditing. My interest is in a lesser level of involvement, where someone has shown merit within their own PPMC and can get a binding vote there, but no-where else. That feels to me like a very useful intermediate step to have. I agree, except for the no-where else part. If you know how to check a RAT report and have an idea of what should be in the NOTICE files, you should be able to help out any other podling by reviewing their release and casting a binding vote so they can learn how to do that. I'd say that 3 IPMC members must vote to give a person Release Auditor status if they are not already on a TLP PMC. Consider this: I am an the Flex PMC but not the IPMC, but if I join the PPMC of some new podling, why shouldn't I be able to cast a binding vote for that podling's releases? With a two tier model - with PPMC membership granting voting rights on podling releases, then a podling would start with just mentors on its PPMC. If you clearly knew what you were doing, you'd get voted onto the PPMC pretty quickly, and thus you'd be able to vote on your releases. I am concerned that it would be dis-empowering to the incoming community if at least the active and major developers of the podling were not on the PPMC at the start. Andy Upayavira - 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: Cultivating Outstanding IP Stewards
I don’t see how the situation is any worse than it is now, where no one on the project currently has a binding vote on a release. Going from that to “a few” may seem unfair, but we have to start somewhere and we need to keep in mind that this is partly a training exercise, where we need to see people actually demonstrate good judgement on policy matters. Unfortunately this doesn’t solve the bootstrapping issue directly with the first release, unless we use it as a remedy for letting release votes stall. On Nov 18, 2013, at 6:41 AM, Andy Seaborne wrote: > On 17/11/13 11:17, Upayavira wrote: >> >> >> On Sun, Nov 17, 2013, at 04:59 AM, Alex Harui wrote: >>> >>> >>> On 11/16/13 8:47 AM, "Upayavira" wrote: >>> Alex, I'm not sure I see the difference between a release auditor and an IPMC member. If someone is sufficiently clued up to audit a release, then they're surely ready to join the Incubator PMC. Am I missing something? >>> To me, there is more responsibility in being on the IPMC, like reviewing >>> proposals for new podlings and voting on their graduation and becoming a >>> mentor. Personally, that's why I don't want to be on the IPMC, but I >>> might be willing to help IP audit a podling's release. Just like some >>> projects don't have all committers on the PMC, a Release Auditor is just >>> someone who can do that specific task, and there is no need to vote them >>> in if they are already on some other TLP PMC because any member of a TLP >>> PMC supposedly knows how to do release auditing. >>> My interest is in a lesser level of involvement, where someone has shown merit within their own PPMC and can get a binding vote there, but no-where else. That feels to me like a very useful intermediate step to have. >>> I agree, except for the no-where else part. If you know how to check a >>> RAT report and have an idea of what should be in the NOTICE files, you >>> should be able to help out any other podling by reviewing their release >>> and casting a binding vote so they can learn how to do that. I'd say >>> that >>> 3 IPMC members must vote to give a person Release Auditor status if they >>> are not already on a TLP PMC. Consider this: I am an the Flex PMC but >>> not the IPMC, but if I join the PPMC of some new podling, why shouldn't I >>> be able to cast a binding vote for that podling's releases? >> >> With a two tier model - with PPMC membership granting voting rights on >> podling releases, then a podling would start with just mentors on its >> PPMC. If you clearly knew what you were doing, you'd get voted onto the >> PPMC pretty quickly, and thus you'd be able to vote on your releases. > > I am concerned that it would be dis-empowering to the incoming community if > at least the active and major developers of the podling were not on the PPMC > at the start. > > Andy > >> >> Upayavira >> >> - >> 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: Transition Incubator dist area
The artifacts that have been left behind by the TLP's should be moved to archive.apache.org/dist as dist should only contain the most recent releases to not overload the mirrors. I agree that we should send out an email to pmcs@ and give a window for moving the releases over to the correct location. -Jake On Sun, Nov 17, 2013 at 9:58 PM, Marvin Humphrey wrote: > On Sun, Nov 17, 2013 at 2:09 PM, David Crossley > wrote: > > > One thing that would help is to also clear the clutter. > > > > Clutch has been alerting to old releases hanging around. > > http://incubator.apache.org/clutch.html#other > > There are many in that list with the entry: > > "Has graduated, but still has remains on Incubator distribution mirrors." > > Perhaps we should start by sending out requests to all such TLPs? Probably > such requests would get the most attention if they come from the IPMC > Chair. > Something like this? > > Greetings, $TLP developers, > > Infra has asked the Incubator to clean up our distribution area. > Despite > having graduated, your project still has release artifacts there. Can > you > please move them to your own area or remove them, as you deem > appropriate? > > The directory which needs to be emptied out is on people.apache.org, > at > `/dist/$PODLING`. > > Marvin Humphrey > Incubator PMC Chair > > Then, if they don't take care of things in a week or two, we move ahead > with > migrating the artifacts to dist.apache.org, rather than let ourselves be > blocked. > > Marvin Humphrey > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Transition Incubator dist area
On Mon, Nov 18, 2013 at 6:15 AM, Jake Farrell wrote: > The artifacts that have been left behind by the TLP's should be moved to > archive.apache.org/dist as dist should only contain the most recent > releases to not overload the mirrors. I agree that we should send out an > email to pmcs@ and give a window for moving the releases over to the > correct location. This is getting too complicated. The problem of our own dist area requiring complicated configuration is separate from the problem of graduating TLPs leaving a mess behind in the Incubator, and also separate from the problem of TLPs having too many artifacts on the mirrors. Infra has asked us to solve a specific problem, and I want to be responsive to Infra's request. Since no one has volunteered, I'm just going to take care of the dist dir situation myself. There won't be any additional space requirements imposed on the mirrors, though I don't know whether there might be a pointless one-time sync cost caused by file datestamp changes. After that, we can nudge the graduated TLPs to come back and pick up after themselves. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Transition Incubator dist area
On Nov 18, 2013, at 12:38 PM, Marvin Humphrey wrote: > On Mon, Nov 18, 2013 at 6:15 AM, Jake Farrell wrote: >> The artifacts that have been left behind by the TLP's should be moved to >> archive.apache.org/dist as dist should only contain the most recent >> releases to not overload the mirrors. I agree that we should send out an >> email to pmcs@ and give a window for moving the releases over to the >> correct location. > > This is getting too complicated. The problem of our own dist area requiring > complicated configuration is separate from the problem of graduating TLPs > leaving a mess behind in the Incubator, and also separate from the problem of > TLPs having too many artifacts on the mirrors. Infra has asked us to solve a > specific problem, and I want to be responsive to Infra's request. > > Since no one has volunteered, I'm just going to take care of the dist dir > situation myself. There won't be any additional space requirements imposed on > the mirrors, though I don't know whether there might be a pointless one-time > sync cost caused by file datestamp changes. Thanks for taking care of it Marvin. I was planning to volunteer but do not have good internet until Friday. If anything is left over by Friday (11/22), I can volunteer to finish it up then. Suresh > > After that, we can nudge the graduated TLPs to come back and pick up after > themselves. > > Marvin Humphrey > > - > 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: [PROPOSAL] Phoenix for Incubation
A bit late to this, but another enthusiastic +1 for Phoenix. Phoenix is an excellent addition to HBase. Data types, loose coupling between your data schemas and applications making schema evolution easier, speedier scans and a good set of aggregation functions - a lot of convenience for a certain class of applications that need to use HBase. And despite the excellent features it already offers, there is much, much more work to be done here and I think making this a part of the Apache umbrella will incentivize more people to contribute. - Original Message - From: general@incubator.apache.org To: general@incubator.apache.org At: Nov 18 2013 04:34:23 +1 (non-binding) for incubation of Phoenix. This is already a very useful project for HBase users, and it will be good to see it driven by a larger community. It may be also be good to get a legal opinion about the name, and/or check for an alternative. There may be some existing software products with this name (e.g. http://www.opwglobal.com/Product.aspx?pid=342). Regards Priyank Rastogi -Original Message- From: James Taylor [mailto:jtay...@salesforce.com] Sent: 14 November 2013 02:14 To: general@incubator.apache.org Subject: [PROPOSAL] Phoenix for Incubation Hi All, We're pleased to share a draft ASF incubation proposal for Phoenix, a SQL layer over HBase, initially developed at Salesforce.com and subsequently open sourced on github (https://github.com/forcedotcom/phoenix). Instead of using Map-reduce to processes queries, it compiles SQL directly into native HBase calls. The complete proposal can be found here: https://wiki.apache.org/incubator/PhoenixProposal, and is also pasted below. Your feedback is greatly appreciated. James == Abstract == Phoenix is an open source SQL query engine for Apache HBase, a NoSQL data store. It is accessed as a JDBC driver and enables querying and managing HBase tables using SQL. == Proposal == Phoenix is an open source SQL skin over HBase delivered as a client-embedded JDBC driver targeting low latency queries over HBase data. Phoenix takes your SQL query, compiles it into a series of HBase scans, and orchestrates the running of those scans to produce regular JDBC result sets. The table metadata is stored in an HBase table and versioned, such that snapshot queries over prior versions will automatically use the correct schema. Direct use of the HBase API, along with coprocessors and custom filters, results in performance on the order of milliseconds for small queries, or seconds for tens of millions of rows. Phoenix interfaces with both Pig and Map-reduce for the input and output of data. == Background == Phoenix initially started as an internal project at Salesforce.com to efficiently analyze big data stored in HBase. It was open sourced on Github about a year ago in Jan 2013. Over time Phoenix, together with HBase as the storage tier, has begun to evolve into a general SQL database with support for metadata management, secondary indexes, joins, query optimization, and multi-tenancy. This is expected to continue as Phoenix implements a cost-based query optimizer and potentially transaction support, and surfaces new HBase security features such as encryption and cell-level security. Phoenix's developer community has also grown to include additional companies such as Intel, who have contributed join support to Phoenix, as well as Hortonworks, who are in the process of porting Phoenix to the 0.96 release of HBase. == Rationale == As usage and the number of contributors to Phoenix has grown, we have sought for a long-term home for the project, and we believe the Apache foundation would be a great fit. Joining Apache would ensure that tried and true processes and procedures are in place for the growing number of organizations interested in contributing to Phoenix. Phoenix is also a good fit for the Apache foundation: Phoenix already interoperates with several existing Apache projects (HBase, Hadoop, Pig). The Phoenix team is familiar with the Apache process and and believes in the Apache mission - the team already includes multiple Apache committers. == Initial Goals == The initial goals will be to move the existing codebase to Apache and integrate with the Apache development process. Once this is accomplished, we plan for incremental development and releases that follow the Apache guidelines. == Current Status == Phoenix has undergone two major and three minor releases (1.0, 1.1, 1.2, 2.0, and 2.1) as well as many patch releases. Phoenix is being used in production by Salesforce.com as well as at other organizations. The Phoenix codebase is currently hosted at github.com, which will form the basis of the Apache git repository. === Meritocracy === The Phoenix project already operates on meritocratic principles. Phoenix has several developers from various organizations outside of Salesforce.com who have contributed major new features. While this pro
Re: [VOTE] Graduate Ambari from Apache Incubator
+1 for graduation (binding) On Sun, Nov 17, 2013 at 9:52 AM, Arun C. Murthy wrote: > > > > [ ] +1 Graduate Ambari from Incubator > > +1 for graduation (binding) > > thanks, > Arun > > > > On Nov 15, 2013, at 9:12 AM, Yusaku Sako wrote: > > > > This is a call for vote to graduate Ambari from Apache Incubator. > > > > The Apache Ambari project has been incubating since August 2011. > > We have made significant progress with the project during the two years > > of Incubation, adding 27 committers for a total of 36 committers [1], and > > producing 8 releases following ASF policies and guidelines. > > The Apache Ambari community has voted to graduate Ambari as a TLP [2]. > > The community vote results can be found at [3]. > > The discussion thread for the board resolution can be found at [4]. > > > > Please cast your votes: > > > > [ ] +1 Graduate Ambari from Incubator > > [ ] +0 Indifferent to graduation status of Ambari > > [ ] -1 Reject graduation of Ambari from Incubator > > > > This vote will remain open for at least 72 hours from now. > > Please find the proposed board resolution below. > > > > [1] http://people.apache.org/committers-by-project.html#ambari > > [2] http://markmail.org/thread/cp5ajf2uvfl3oj66 > > [3] http://markmail.org/message/l6zss4rgfcs3gvpm > > [4] http://markmail.org/thread/36dplr3pwzmazwmg > > > > Regards, > > Yusaku Sako > > > > ### > > > > X. Establish the Apache Ambari Project > > > > WHEREAS, the Board of Directors deems it to be in the best > > interests of the Foundation and consistent with the > > Foundation's purpose to establish a Project Management > > Committee charged with the creation and maintenance of > > open-source software, for distribution at no charge to > > the public, related to Hadoop cluster management. > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > > Committee (PMC), to be known as the "Apache Ambari Project", > > be and hereby is established pursuant to Bylaws of the > > Foundation; and be it further > > > > RESOLVED, that the Apache Ambari Project be and hereby is > > responsible for the creation and maintenance of software > > related to Hadoop cluster management; > > and be it further > > > > RESOLVED, that the office of "Vice President, Apache Ambari" be > > and hereby is created, the person holding such office to > > serve at the direction of the Board of Directors as the chair > > of the Apache Ambari Project, and to have primary responsibility > > for management of the projects within the scope of > > responsibility of the Apache Ambari Project; and be it further > > > > RESOLVED, that the persons listed immediately below be and > > hereby are appointed to serve as the initial members of the > > Apache Ambari Project: > > > >* Babiichuk Andriy (ababiichuk) > >* Arun Murthy (acmurthy) > >* Aleksandr Kovalenko (akovalenko) > >* Antonenko Aleksandr Igorevich (alexantonenko) > >* Andrii Tkach (atkach) > >* Bernd Fondermann (berndf) > >* Billie Rinaldi (billie) > >* Christopher Douglas (cdouglas) > >* Chad Roberts (croberts) > >* Devaraj Das (ddas) > >* Dmitry Lysnichenko (dmitriusan) > >* Dmytro Sen (dsen) > >* Eric Yang (eyang) > >* Hitesh Shah (hitesh) > >* Jagane Sundar (jagane) > >* Jaimin Jetly (jaimin) > >* Jitendra Pandey (jitendra) > >* John Speidel (jspeidel) > >* Kan Zhang (kzhang) > >* Mahadev Konar (mahadev) > >* Papirkovskyy Myroslav (mpapirkovskyy) > >* Nate Cole (ncole) > >* Oleksandr Diachenko (odiachenko) > >* Owen O’Malley (omalley) > >* Oleg Nechiporenko (onechiporenko) > >* Ramya Sunil (ramya) > >* Varun Kapoor (reznor) > >* Sumit Mohanty (smohanty) > >* Srimanth Gunturi (srimanth) > >* Siddharth Wagle (swagle) > >* Thomas Beerbower (tbeerbower) > >* Suhas (vgogate) > >* Vikram Dixit K (vikram) > >* Vinod Kumar Vavilapalli (vinodkv) > >* Xi Wang (xiwang) > >* Yusaku Sako (yusaku) > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Yusaku Sako > > be appointed to the office of Vice President, Apache Ambari, to > > serve in accordance with and subject to the direction of the > > Board of Directors and the Bylaws of the Foundation until > > death, resignation, retirement, removal or disqualification, > > or until a successor is appointed; and be it further > > > > RESOLVED, that the initial Apache Ambari PMC be and hereby is > > tasked with the creation of a set of bylaws intended to > > encourage open development and increased participation in the > > Apache Ambari Project; and be it further > > > > RESOLVED, that the Apache Ambari Project be and hereby
Re: Transition Incubator dist area
On Mon, Nov 18, 2013 at 11:46 AM, Suresh Marru wrote: > Thanks for taking care of it Marvin. I was planning to volunteer but do not > have good internet until Friday. If anything is left over by Friday (11/22), > I can volunteer to finish it up then. Thanks for the offer Suresh. This is the kind of thing that is best done by a single person getting in a groove, though, so I've just powered through and finished. The following directories have been copied into dist.apache.org/repos/dist/release/incubator: ambari amber chukwa deltaspike droids hcatalog imperius isis jspwiki kafka kato net mesos npanday odftoolkit olio photark s4 stonehenge tashi The only wrinkle was that Kafka had an svn checkout of their docs in there for the 0.7.0 release. I committed the docs but stripped the .svn dirs. If I've done everything right, it should be possible for Infra to flip the switch and use new-style dist.apache.org synchronization at the incubator/ level. It would be nice if we continue on with the cleanup. Should we remove the directories for podlings which have retired? And then there's the matter of dealing with TLPs who still need to link to incubating releases. Jake and I were talking on IRC about giving them a deadline to move needed releases to their own dist area, after which we svn remove their dirs. Two weeks notice seems enough to me, WDYT? Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Ambari from Apache Incubator
+1 (binding) for graduation On Fri, Nov 15, 2013 at 9:12 AM, Yusaku Sako wrote: > This is a call for vote to graduate Ambari from Apache Incubator. > > The Apache Ambari project has been incubating since August 2011. > We have made significant progress with the project during the two years > of Incubation, adding 27 committers for a total of 36 committers [1], and > producing 8 releases following ASF policies and guidelines. > The Apache Ambari community has voted to graduate Ambari as a TLP [2]. > The community vote results can be found at [3]. > The discussion thread for the board resolution can be found at [4]. > > Please cast your votes: > > [ ] +1 Graduate Ambari from Incubator > [ ] +0 Indifferent to graduation status of Ambari > [ ] -1 Reject graduation of Ambari from Incubator > > This vote will remain open for at least 72 hours from now. > Please find the proposed board resolution below. > > [1] http://people.apache.org/committers-by-project.html#ambari > [2] http://markmail.org/thread/cp5ajf2uvfl3oj66 > [3] http://markmail.org/message/l6zss4rgfcs3gvpm > [4] http://markmail.org/thread/36dplr3pwzmazwmg > > Regards, > Yusaku Sako > > ### > > X. Establish the Apache Ambari Project > > WHEREAS, the Board of Directors deems it to be in the best > interests of the Foundation and consistent with the > Foundation's purpose to establish a Project Management > Committee charged with the creation and maintenance of > open-source software, for distribution at no charge to > the public, related to Hadoop cluster management. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > Committee (PMC), to be known as the "Apache Ambari Project", > be and hereby is established pursuant to Bylaws of the > Foundation; and be it further > > RESOLVED, that the Apache Ambari Project be and hereby is > responsible for the creation and maintenance of software > related to Hadoop cluster management; > and be it further > > RESOLVED, that the office of "Vice President, Apache Ambari" be > and hereby is created, the person holding such office to > serve at the direction of the Board of Directors as the chair > of the Apache Ambari Project, and to have primary responsibility > for management of the projects within the scope of > responsibility of the Apache Ambari Project; and be it further > > RESOLVED, that the persons listed immediately below be and > hereby are appointed to serve as the initial members of the > Apache Ambari Project: > > * Babiichuk Andriy (ababiichuk) > * Arun Murthy (acmurthy) > * Aleksandr Kovalenko (akovalenko) > * Antonenko Aleksandr Igorevich (alexantonenko) > * Andrii Tkach (atkach) > * Bernd Fondermann (berndf) > * Billie Rinaldi (billie) > * Christopher Douglas (cdouglas) > * Chad Roberts (croberts) > * Devaraj Das (ddas) > * Dmitry Lysnichenko (dmitriusan) > * Dmytro Sen (dsen) > * Eric Yang (eyang) > * Hitesh Shah (hitesh) > * Jagane Sundar (jagane) > * Jaimin Jetly (jaimin) > * Jitendra Pandey (jitendra) > * John Speidel (jspeidel) > * Kan Zhang (kzhang) > * Mahadev Konar (mahadev) > * Papirkovskyy Myroslav (mpapirkovskyy) > * Nate Cole (ncole) > * Oleksandr Diachenko (odiachenko) > * Owen O’Malley (omalley) > * Oleg Nechiporenko (onechiporenko) > * Ramya Sunil (ramya) > * Varun Kapoor (reznor) > * Sumit Mohanty (smohanty) > * Srimanth Gunturi (srimanth) > * Siddharth Wagle (swagle) > * Thomas Beerbower (tbeerbower) > * Suhas (vgogate) > * Vikram Dixit K (vikram) > * Vinod Kumar Vavilapalli (vinodkv) > * Xi Wang (xiwang) > * Yusaku Sako (yusaku) > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Yusaku Sako > be appointed to the office of Vice President, Apache Ambari, to > serve in accordance with and subject to the direction of the > Board of Directors and the Bylaws of the Foundation until > death, resignation, retirement, removal or disqualification, > or until a successor is appointed; and be it further > > RESOLVED, that the initial Apache Ambari PMC be and hereby is > tasked with the creation of a set of bylaws intended to > encourage open development and increased participation in the > Apache Ambari Project; and be it further > > RESOLVED, that the Apache Ambari Project be and hereby > is tasked with the migration and rationalization of the Apache > Incubator Ambari podling; and be it further > > RESOLVED, that all responsibilities pertaining to the Apache > Incubator Ambari podling encumbered upon the Apache Incubator > Project are hereafter discharged. > > --
helix 0.6.2-incubating
Hi, This is to call for a vote on releasing the following candidate as Apache Helix 0.6.2-incubating. This is the first release candidate of our third release at Apache. Apache Helix is a generic cluster management framework that makes it easy to build partitioned and replicated, fault tolerant and scalable distributed systems. Release notes: http://helix.incubator.apache.org/site-releases/0.6.2-incubating-site/releasenotes/release-0.6.2-incubating.html Our vote thread on helix-dev: http://markmail.org/message/f2odmc7ga2i5qqmh The following IPMC members have voted +1 Patrick Hunt Olivier Lamy Release artifacts: https://repository.apache.org/content/repositories/orgapachehelix-138 Distribution: * binaries: https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.2-incubating/binaries/ * sources: https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.2-incubating/src/ The 0.6.2-incubating release tag https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=74efd57c9f7bcb54cb6007dd34646722d6133340 KEYS file available here: https://dist.apache.org/repos/dist/dev/incubator/helix/KEYS Please vote on the release. The vote will be open for 72 hours. Thanks, The Apache Helix Team - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] helix-0.6.2-incubating
Hi, This is to call for a vote on releasing the following candidate as Apache Helix 0.6.2-incubating. This is the first release candidate of our third release at Apache. Apache Helix is a generic cluster management framework that makes it easy to build partitioned and replicated, fault tolerant and scalable distributed systems. Release notes: http://helix.incubator.apache.org/site-releases/0.6.2-incubating-site/releasenotes/release-0.6.2-incubating.html Our vote thread on helix-dev: http://markmail.org/message/f2odmc7ga2i5qqmh The following IPMC members have voted +1 Patrick Hunt Olivier Lamy Release artifacts: https://repository.apache.org/content/repositories/orgapachehelix-138 Distribution: * binaries: https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.2-incubating/binaries/ * sources: https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.2-incubating/src/ The 0.6.2-incubating release tag https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=74efd57c9f7bcb54cb6007dd34646722d6133340 KEYS file available here: https://dist.apache.org/repos/dist/dev/incubator/helix/KEYS Please vote on the release. The vote will be open for 72 hours. [+1] [0] [-1] Thanks, The Apache Helix Team - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Ambari from Apache Incubator
+1 (binding). G'luck guys! Cheers, Chris ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Owen O'Malley Reply-To: "general@incubator.apache.org" Date: Monday, November 18, 2013 4:14 PM To: "general@incubator.apache.org" Subject: Re: [VOTE] Graduate Ambari from Apache Incubator >+1 for graduation (binding) > > >On Sun, Nov 17, 2013 at 9:52 AM, Arun C. Murthy >wrote: > >> > >> > [ ] +1 Graduate Ambari from Incubator >> >> +1 for graduation (binding) >> >> thanks, >> Arun >> >> >> > On Nov 15, 2013, at 9:12 AM, Yusaku Sako >>wrote: >> > >> > This is a call for vote to graduate Ambari from Apache Incubator. >> > >> > The Apache Ambari project has been incubating since August 2011. >> > We have made significant progress with the project during the two >>years >> > of Incubation, adding 27 committers for a total of 36 committers [1], >>and >> > producing 8 releases following ASF policies and guidelines. >> > The Apache Ambari community has voted to graduate Ambari as a TLP [2]. >> > The community vote results can be found at [3]. >> > The discussion thread for the board resolution can be found at [4]. >> > >> > Please cast your votes: >> > >> > [ ] +1 Graduate Ambari from Incubator >> > [ ] +0 Indifferent to graduation status of Ambari >> > [ ] -1 Reject graduation of Ambari from Incubator >> > >> > This vote will remain open for at least 72 hours from now. >> > Please find the proposed board resolution below. >> > >> > [1] http://people.apache.org/committers-by-project.html#ambari >> > [2] http://markmail.org/thread/cp5ajf2uvfl3oj66 >> > [3] http://markmail.org/message/l6zss4rgfcs3gvpm >> > [4] http://markmail.org/thread/36dplr3pwzmazwmg >> > >> > Regards, >> > Yusaku Sako >> > >> > ### >> > >> > X. Establish the Apache Ambari Project >> > >> > WHEREAS, the Board of Directors deems it to be in the best >> > interests of the Foundation and consistent with the >> > Foundation's purpose to establish a Project Management >> > Committee charged with the creation and maintenance of >> > open-source software, for distribution at no charge to >> > the public, related to Hadoop cluster management. >> > >> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management >> > Committee (PMC), to be known as the "Apache Ambari Project", >> > be and hereby is established pursuant to Bylaws of the >> > Foundation; and be it further >> > >> > RESOLVED, that the Apache Ambari Project be and hereby is >> > responsible for the creation and maintenance of software >> > related to Hadoop cluster management; >> > and be it further >> > >> > RESOLVED, that the office of "Vice President, Apache Ambari" be >> > and hereby is created, the person holding such office to >> > serve at the direction of the Board of Directors as the chair >> > of the Apache Ambari Project, and to have primary responsibility >> > for management of the projects within the scope of >> > responsibility of the Apache Ambari Project; and be it further >> > >> > RESOLVED, that the persons listed immediately below be and >> > hereby are appointed to serve as the initial members of the >> > Apache Ambari Project: >> > >> >* Babiichuk Andriy (ababiichuk) >> >* Arun Murthy (acmurthy) >> >* Aleksandr Kovalenko (akovalenko) >> >* Antonenko Aleksandr Igorevich (alexantonenko) >> >* Andrii Tkach (atkach) >> >* Bernd Fondermann (berndf) >> >* Billie Rinaldi (billie) >> >* Christopher Douglas (cdouglas) >> >* Chad Roberts (croberts) >> >* Devaraj Das (ddas) >> >* Dmitry Lysnichenko (dmitriusan) >> >* Dmytro Sen (dsen) >> >* Eric Yang (eyang) >> >* Hitesh Shah (hitesh) >> >* Jagane Sundar (jagane) >> >* Jaimin Jetly (jaimin) >> >* Jitendra Pandey (jitendra) >> >* John Speidel (jspeidel) >> >* Kan Zhang (kzhang) >> >* Mahadev Konar (mahadev) >> >* Papirkovskyy Myroslav (mpapirkovskyy) >> >* Nate Cole (ncole) >> >* Oleksandr Diachenko (odiachenko) >> >* Owen O¹Malley (omalley) >> >* Oleg Nechiporenko (onechiporenko) >> >* Ramya Sunil (ramya) >> >* Varun Kapoor (reznor) >> >* Sumit Mohanty (smohanty) >> >* Srimanth Gunturi (srimanth) >> >* Siddharth Wagle (swagle) >> >* Thomas Beerbower (tbeerbower) >> >
Re: [VOTE] Graduate Ambari from Apache Incubator
On Fri, Nov 15, 2013 at 9:12 AM, Yusaku Sako wrote: > This is a call for vote to graduate Ambari from Apache Incubator. > > The Apache Ambari project has been incubating since August 2011. > We have made significant progress with the project during the two years > of Incubation, adding 27 committers for a total of 36 committers [1], and > producing 8 releases following ASF policies and guidelines. > The Apache Ambari community has voted to graduate Ambari as a TLP [2]. > The community vote results can be found at [3]. > The discussion thread for the board resolution can be found at [4]. > > Please cast your votes: > > [ ] +1 Graduate Ambari from Incubator > [ ] +0 Indifferent to graduation status of Ambari > [ ] -1 Reject graduation of Ambari from Incubator +1 (binding) Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Retire the Provisionr podling
Hi - We voted [1] to retire the Provisionr podling form the Apache Incubator. Following the retirement guide, it is now time for an IPMC vote to ratify the decision. [ ] +1 Retire the Provisionr podling [ ] +0 Neither here nor there [ ] -1 Do not retire the podling because ... This vote will remain open for at least the next 72 hours. So far we've got 2 votes from IPMC members (not counting my own): * Roman Shaposhnik * Tom White Thanks! [1] http://s.apache.org/xtG [2] http://incubator.apache.org/guides/retirement.html
