Joining IPMC member
Hi, I just noticed that Mentor must be members of the Incubator PMC[1]. Regarding MRQL podling, I'm not only Champion but also want to be a Mentor for MRQL project. Please add me to IPMC. 1. http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Apache Ambari (incubating) 1.2.1 Release Candidate RC1.
Thanks to feedback from general@incubator we have updated the release artifacts with the following fixes: 1. Fixed NOTICE.txt 2. Fixed KEYS file. 3. Removed pyc files in my svn tree (unfortunately ran mvn test before building last time). 4. mvn apache-rat:check passes. The exclude files are files that cannot have Apache Headers since it breaks the run time. 5. Website has been updated (http://incubator.apache.org/ambari/ to fix all the issues mentioned earlier - thanks to Yusaku). 6. Release artifacts now use md5 and sha1. The staging Staging site is: http://people.apache.org/~mahadev/ambari-1.2.1-incubating-rc1/ with user docs at: http://incubator.apache.org/ambari/1.2.1/installing-hadoop-using-ambari/content/index.html and dev docs at: https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development SVN source tag: https://svn.apache.org/repos/asf/incubator/ambari/tags/release-1.2.1-rc1 PGP release keys (signed using 8EE2F25C) http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x0DFF492D8EE2F25C One can look into the issues fixed in this release at https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%20%221.2.1%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) thanks mahadev - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Joining IPMC member
Edward, are you not familiar with our custom of handling personnel matters on private lists? It has not always been that way, but do you understand why virtually all ASF projects adhere to that convention now? Marvin Humphrey On Wed, Mar 13, 2013 at 11:15 PM, Edward J. Yoon edwardy...@apache.org wrote: Hi, I just noticed that Mentor must be members of the Incubator PMC[1]. Regarding MRQL podling, I'm not only Champion but also want to be a Mentor for MRQL project. Please add me to IPMC. 1. http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor -- Best Regards, Edward J. Yoon @eddieyoon - 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: Joining IPMC member
Yes, I think I'm not familiar with handling issues like personnel, and somewhat emotional person. However, I want to helping people who want to contribute to ASF or collaborate with ASF projects in the future. On Thu, Mar 14, 2013 at 3:46 PM, Marvin Humphrey mar...@rectangular.com wrote: Edward, are you not familiar with our custom of handling personnel matters on private lists? It has not always been that way, but do you understand why virtually all ASF projects adhere to that convention now? Marvin Humphrey On Wed, Mar 13, 2013 at 11:15 PM, Edward J. Yoon edwardy...@apache.org wrote: Hi, I just noticed that Mentor must be members of the Incubator PMC[1]. Regarding MRQL podling, I'm not only Champion but also want to be a Mentor for MRQL project. Please add me to IPMC. 1. http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor -- Best Regards, Edward J. Yoon @eddieyoon - 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 -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Joining IPMC member
understand why virtually all ASF projects adhere to that convention now? P.S., It's been 6 years since I uploaded my first patch on HBase. I still don't know many things but I'm continuously learning from you guys ;-) On Thu, Mar 14, 2013 at 4:07 PM, Edward J. Yoon edwardy...@apache.org wrote: Yes, I think I'm not familiar with handling issues like personnel, and somewhat emotional person. However, I want to helping people who want to contribute to ASF or collaborate with ASF projects in the future. On Thu, Mar 14, 2013 at 3:46 PM, Marvin Humphrey mar...@rectangular.com wrote: Edward, are you not familiar with our custom of handling personnel matters on private lists? It has not always been that way, but do you understand why virtually all ASF projects adhere to that convention now? Marvin Humphrey On Wed, Mar 13, 2013 at 11:15 PM, Edward J. Yoon edwardy...@apache.org wrote: Hi, I just noticed that Mentor must be members of the Incubator PMC[1]. Regarding MRQL podling, I'm not only Champion but also want to be a Mentor for MRQL project. Please add me to IPMC. 1. http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor -- Best Regards, Edward J. Yoon @eddieyoon - 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 -- Best Regards, Edward J. Yoon @eddieyoon -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Missing Report
As a new podling, Tez is scheduled to report this month; but, there is no report completed in the wiki. If possible, please add your report to the wiki [1] before the end of Friday. [1]: http://wiki.apache.org/incubator/March2013 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Wave - Missing Report
Wave is scheduled to report this month; but, there is no report completed in the wiki. If possible, please add your report to the wiki [1] before the end of Friday. [1]: http://wiki.apache.org/incubator/March2013 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Looking for a volunteer to finalize the March report
I have added a draft commentary to the report in the wiki. Since we had no shepherd self-organization, I am asking for an immediate set of volunteers who can review the podlings and provide shepherd comments before Friday evening, when I will send the report to the board on Benson's behalf. If you have time and are willing, reply to this thread with which podlings you would like to review and add your name to the wiki. Additionally, there are quite a few reports that need mentor sign-off. All mentors, please review your podling reports and add your X. On Wed, Mar 13, 2013 at 5:28 PM, Matt Franklin m.ben.frank...@gmail.com wrote: Working on it now. Will have it ready in the morning for review comment and will submit it to the board on Friday. -Matt On Mon, Mar 11, 2013 at 9:52 AM, Benson Margulies bimargul...@gmail.com wrote: Thanks! On Mon, Mar 11, 2013 at 7:28 AM, Matt Franklin m.ben.frank...@gmail.comwrote: On Monday, March 11, 2013, Benson Margulies wrote: If no one else is willing to take this on, I will finalize the report on Wednesday 13 March in the EDT evening, and it will contain what it contains at that moment. I can do it. On Sat, Mar 9, 2013 at 2:39 PM, Benson Margulies bimargul...@gmail.com javascript:; wrote: Folks, I will be travelling the week of 18 March, with somewhat uncertain networking and state of jet lag. Would someone else be willing to tie off the report and deliver it to the board's doorstep? --benson - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Looking for a volunteer to finalize the March report
I can give some Shepherd notes for Wave. I am sorry to ask, but is there any docs what specifically i have to do as a Shepherd or is it just an giving an impression on how life goes? On Thu, Mar 14, 2013 at 2:24 PM, Matt Franklin m.ben.frank...@gmail.com wrote: I have added a draft commentary to the report in the wiki. Since we had no shepherd self-organization, I am asking for an immediate set of volunteers who can review the podlings and provide shepherd comments before Friday evening, when I will send the report to the board on Benson's behalf. If you have time and are willing, reply to this thread with which podlings you would like to review and add your name to the wiki. Additionally, there are quite a few reports that need mentor sign-off. All mentors, please review your podling reports and add your X. On Wed, Mar 13, 2013 at 5:28 PM, Matt Franklin m.ben.frank...@gmail.com wrote: Working on it now. Will have it ready in the morning for review comment and will submit it to the board on Friday. -Matt On Mon, Mar 11, 2013 at 9:52 AM, Benson Margulies bimargul...@gmail.com wrote: Thanks! On Mon, Mar 11, 2013 at 7:28 AM, Matt Franklin m.ben.frank...@gmail.comwrote: On Monday, March 11, 2013, Benson Margulies wrote: If no one else is willing to take this on, I will finalize the report on Wednesday 13 March in the EDT evening, and it will contain what it contains at that moment. I can do it. On Sat, Mar 9, 2013 at 2:39 PM, Benson Margulies bimargul...@gmail.com javascript:; wrote: Folks, I will be travelling the week of 18 March, with somewhat uncertain networking and state of jet lag. Would someone else be willing to tie off the report and deliver it to the board's doorstep? --benson - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Joining IPMC member
On Mar 14, 2013, at 3:26 AM, Edward J. Yoon edwardy...@apache.org wrote: understand why virtually all ASF projects adhere to that convention now? P.S., It's been 6 years since I uploaded my first patch on HBase. I still don't know many things but I'm continuously learning from you guys ;-) Hi Edward, I do not think any one is questioning your credibility as a committer, or pmc member. I think Marvin hit it right and straight forward way. At ASF one of the few things (and primarily the only thing) like adding to a PMC is handled on private lists. Given that you have been contributing since 6 years you are certainly expected to know it. It is not healthy to side track the issue with your contributions or citing emotional reasons. Suresh On Thu, Mar 14, 2013 at 4:07 PM, Edward J. Yoon edwardy...@apache.org wrote: Yes, I think I'm not familiar with handling issues like personnel, and somewhat emotional person. However, I want to helping people who want to contribute to ASF or collaborate with ASF projects in the future. On Thu, Mar 14, 2013 at 3:46 PM, Marvin Humphrey mar...@rectangular.com wrote: Edward, are you not familiar with our custom of handling personnel matters on private lists? It has not always been that way, but do you understand why virtually all ASF projects adhere to that convention now? Marvin Humphrey On Wed, Mar 13, 2013 at 11:15 PM, Edward J. Yoon edwardy...@apache.org wrote: Hi, I just noticed that Mentor must be members of the Incubator PMC[1]. Regarding MRQL podling, I'm not only Champion but also want to be a Mentor for MRQL project. Please add me to IPMC. 1. http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor -- Best Regards, Edward J. Yoon @eddieyoon - 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 -- Best Regards, Edward J. Yoon @eddieyoon -- Best Regards, Edward J. Yoon @eddieyoon - 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 a volunteer to finalize the March report
On Thu, Mar 14, 2013 at 12:24 PM, Christian Grobmeier grobme...@gmail.com wrote: I can give some Shepherd notes for Wave. I am sorry to ask, but is there any docs what specifically i have to do as a Shepherd or is it just an giving an impression on how life goes? Thanks! There are no docs ATM. What we have been doing is looking at the podling (mail lists, etc) to get a feel for how the community is progressing toward graduation and providing feedback. You can see prior shepherd feedback in previous reports and e-mails to general@ On Thu, Mar 14, 2013 at 2:24 PM, Matt Franklin m.ben.frank...@gmail.com wrote: I have added a draft commentary to the report in the wiki. Since we had no shepherd self-organization, I am asking for an immediate set of volunteers who can review the podlings and provide shepherd comments before Friday evening, when I will send the report to the board on Benson's behalf. If you have time and are willing, reply to this thread with which podlings you would like to review and add your name to the wiki. Additionally, there are quite a few reports that need mentor sign-off. All mentors, please review your podling reports and add your X. On Wed, Mar 13, 2013 at 5:28 PM, Matt Franklin m.ben.frank...@gmail.com wrote: Working on it now. Will have it ready in the morning for review comment and will submit it to the board on Friday. -Matt On Mon, Mar 11, 2013 at 9:52 AM, Benson Margulies bimargul...@gmail.com wrote: Thanks! On Mon, Mar 11, 2013 at 7:28 AM, Matt Franklin m.ben.frank...@gmail.comwrote: On Monday, March 11, 2013, Benson Margulies wrote: If no one else is willing to take this on, I will finalize the report on Wednesday 13 March in the EDT evening, and it will contain what it contains at that moment. I can do it. On Sat, Mar 9, 2013 at 2:39 PM, Benson Margulies bimargul...@gmail.com javascript:; wrote: Folks, I will be travelling the week of 18 March, with somewhat uncertain networking and state of jet lag. Would someone else be willing to tie off the report and deliver it to the board's doorstep? --benson - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - 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 a volunteer to finalize the March report
On Thu, Mar 14, 2013 at 5:29 PM, Matt Franklin m.ben.frank...@gmail.com wrote: On Thu, Mar 14, 2013 at 12:24 PM, Christian Grobmeier grobme...@gmail.com wrote: I can give some Shepherd notes for Wave. I am sorry to ask, but is there any docs what specifically i have to do as a Shepherd or is it just an giving an impression on how life goes? Thanks! There are no docs ATM. What we have been doing is looking at the podling (mail lists, etc) to get a feel for how the community is progressing toward graduation and providing feedback. You can see prior shepherd feedback in previous reports and e-mails to general@ Thank you, that is enough information. I will provide some feedback on Wave soon. Cheers On Thu, Mar 14, 2013 at 2:24 PM, Matt Franklin m.ben.frank...@gmail.com wrote: I have added a draft commentary to the report in the wiki. Since we had no shepherd self-organization, I am asking for an immediate set of volunteers who can review the podlings and provide shepherd comments before Friday evening, when I will send the report to the board on Benson's behalf. If you have time and are willing, reply to this thread with which podlings you would like to review and add your name to the wiki. Additionally, there are quite a few reports that need mentor sign-off. All mentors, please review your podling reports and add your X. On Wed, Mar 13, 2013 at 5:28 PM, Matt Franklin m.ben.frank...@gmail.com wrote: Working on it now. Will have it ready in the morning for review comment and will submit it to the board on Friday. -Matt On Mon, Mar 11, 2013 at 9:52 AM, Benson Margulies bimargul...@gmail.com wrote: Thanks! On Mon, Mar 11, 2013 at 7:28 AM, Matt Franklin m.ben.frank...@gmail.comwrote: On Monday, March 11, 2013, Benson Margulies wrote: If no one else is willing to take this on, I will finalize the report on Wednesday 13 March in the EDT evening, and it will contain what it contains at that moment. I can do it. On Sat, Mar 9, 2013 at 2:39 PM, Benson Margulies bimargul...@gmail.com javascript:; wrote: Folks, I will be travelling the week of 18 March, with somewhat uncertain networking and state of jet lag. Would someone else be willing to tie off the report and deliver it to the board's doorstep? --benson - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - 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 -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Graduate CloudStack from Incubator
Apache CloudStack entered the Incubator in April of 2012. We have made significant progress with the project since moving over to Apache. We have 31 committers and 13 PPMC members listed on our status page at [1], not including the 8 mentors that helped guide our community through incubation. 16 of the committers and 7 of the PPMC members were added after the podling was formed. One mentor joined the project after the podling started. 3 of the initial committers that were not in the initial PPMC have now joined the PPMC. 7 of our mentors will be remaining with the project as it transitions into a TLP. We have verified that Apache CloudStack is a suitable name [2], and the CloudStack marks are being donated from Citrix to the ASF. We completed two releases (Apache CloudStack 4.0.0-incubating and Apache CloudStack 4.0.1-incubating) and are currently preparing for two more (4.0.2 and 4.1.0). Our community has created a set of bylaws for the project [3]. The community of Apache CloudStack is active, healthy, and growing and has demonstrated the ability to self-govern using accepted Apache practices. After holding a discussion [4][5], the Apache CloudStack community subsequently voted overwhelmingly to graduate [6], collecting 55 +1 votes (including 4 from IPMC members), and no +0 or -1 votes. IPMC members voting +1 in the project-level thread are: * Mohammad Nour El-Din (IPMC/mentor) [7] * Noah Slater (IPMC/mentor) [8] * Alex Karasulu (IPMC/mentor) [9] * Brett Porter (IPMC/mentor) [10] Please cast your votes: [ ] +1 Graduate Apache CloudStack from Apache Incubator [ ] +0 Indifferent to graduation status of Apache CloudStack [ ] -1 Reject graduation of Apache CloudStack from Apache Incubator because... -chip [1] http://incubator.apache.org/projects/cloudstack.html [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23 [3] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html [4] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E [5] http://markmail.org/message/3nluchj5q5waguws [6] http://markmail.org/message/ntf777ctbhdytijp [7] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E [8] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E [9] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E [10] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E Proposed Resolution: X. Establish the Apache CloudStack 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 providing and supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache CloudStack Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache CloudStack Project be and hereby is responsible for the creation and maintenance of software related to providing and supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms. RESOLVED, that the office of Vice President, Apache CloudStack 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 CloudStack Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache CloudStack 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 CloudStack Project: * Joe Brockmeier j...@apache.org * Will Chan willc...@apache.org * Chip Childers chipchild...@apache.org * Mohammad Nour El-Din mn...@apache.org * Sebastien Goasguen seb...@apache.org * Matt Richard Hogstrom hogst...@apache.org * Wido den Hollander wid...@apache.org * Alex Huang ahu...@apache.org * Jim Jagielski j...@apache.org * Alex Karasulu akaras...@apache.org * John Kinsella j...@apache.org * Kevin Kluge kl...@apache.org * Olivier Lamy ol...@apache.org * David Nalley ke4...@apache.org * Brett Porter br...@apache.org * Noah Slater nsla...@apache.org * Marcus Sorensen mlsoren...@apache.org * Edison Su edi...@apache.org * Hugo Trippaers h...@apache.org * Chiradeep Vittal chirad...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Chip Childers be appointed to the office of
Re: [VOTE] Graduate CloudStack from Incubator
+1 (I figure a second vote from me can't hurt...) On 14 March 2013 16:47, Chip Childers chip.child...@sungard.com wrote: Apache CloudStack entered the Incubator in April of 2012. We have made significant progress with the project since moving over to Apache. We have 31 committers and 13 PPMC members listed on our status page at [1], not including the 8 mentors that helped guide our community through incubation. 16 of the committers and 7 of the PPMC members were added after the podling was formed. One mentor joined the project after the podling started. 3 of the initial committers that were not in the initial PPMC have now joined the PPMC. 7 of our mentors will be remaining with the project as it transitions into a TLP. We have verified that Apache CloudStack is a suitable name [2], and the CloudStack marks are being donated from Citrix to the ASF. We completed two releases (Apache CloudStack 4.0.0-incubating and Apache CloudStack 4.0.1-incubating) and are currently preparing for two more (4.0.2 and 4.1.0). Our community has created a set of bylaws for the project [3]. The community of Apache CloudStack is active, healthy, and growing and has demonstrated the ability to self-govern using accepted Apache practices. After holding a discussion [4][5], the Apache CloudStack community subsequently voted overwhelmingly to graduate [6], collecting 55 +1 votes (including 4 from IPMC members), and no +0 or -1 votes. IPMC members voting +1 in the project-level thread are: * Mohammad Nour El-Din (IPMC/mentor) [7] * Noah Slater (IPMC/mentor) [8] * Alex Karasulu (IPMC/mentor) [9] * Brett Porter (IPMC/mentor) [10] Please cast your votes: [ ] +1 Graduate Apache CloudStack from Apache Incubator [ ] +0 Indifferent to graduation status of Apache CloudStack [ ] -1 Reject graduation of Apache CloudStack from Apache Incubator because... -chip [1] http://incubator.apache.org/projects/cloudstack.html [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23 [3] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html [4] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E [5] http://markmail.org/message/3nluchj5q5waguws [6] http://markmail.org/message/ntf777ctbhdytijp [7] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E [8] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E [9] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E [10] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E Proposed Resolution: X. Establish the Apache CloudStack 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 providing and supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache CloudStack Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache CloudStack Project be and hereby is responsible for the creation and maintenance of software related to providing and supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms. RESOLVED, that the office of Vice President, Apache CloudStack 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 CloudStack Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache CloudStack 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 CloudStack Project: * Joe Brockmeier j...@apache.org * Will Chan willc...@apache.org * Chip Childers chipchild...@apache.org * Mohammad Nour El-Din mn...@apache.org * Sebastien Goasguen seb...@apache.org * Matt Richard Hogstrom hogst...@apache.org * Wido den Hollander wid...@apache.org * Alex Huang ahu...@apache.org * Jim Jagielski j...@apache.org * Alex Karasulu akaras...@apache.org * John Kinsella j...@apache.org * Kevin Kluge kl...@apache.org * Olivier Lamy ol...@apache.org * David Nalley ke4...@apache.org * Brett Porter br...@apache.org * Noah Slater nsla...@apache.org * Marcus Sorensen
Re: [PROPOSAL] Ivory - Hadoop data management and processing platform
+1, this is a great addition! On Mar 13, 2013, at 10:00 AM, Srikanth Sundarrajan wrote: = Ivory Proposal = == Abstract == Ivory is a data processing and management solution for Hadoop designed for data motion, coordination of data pipelines, lifecycle management, and data discovery. Ivory enables end consumers to quickly onboard their data and its associated processing and management tasks on Hadoop clusters. == Proposal == Ivory will enable easy data management via declarative mechanism for Hadoop. Users of Ivory platform simply define infrastructure endpoints, data sets and processing rules declaratively. These configurations are expressed in such a way that the dependencies between these entities are explicitly described. This information about inter-dependencies between various entities allows Ivory to orchestrate and manage various data management functions. The key use cases that Ivory addresses are: * Data Motion * Process orchestration and scheduling * Policy-based Lifecycle Management * Data Discovery * Operability/Usability With these features it is possible for users to onboard their data sets with a comprehensive and holistic understanding of how, when and where their data is managed across its lifecycle. Complex functions such as retrying failures, identifying possible SLA breaches or automated handling of input data changes are now simple directives. All the administrative functions and user level functions are available via RESTful APIs. CLI is simply a wrapper over the RESTful APIs. == Background == Hadoop and its ecosystem of products have made storing and processing massive amounts of data commonplace. This has enabled numerous organizations to gain valuable insights that they never could have achieved in the past. While it is easy to leverage Hadoop for crunching large volumes of data, organizing data, managing life cycle of data and processing data is fairly involved. This is solved adequately well in a classic data platform involving data warehouses and standard ETL (extract-transform-load) tools, but remains largely unsolved today. In addition to data processing complexities, Hadoop presents new sets of challenges and opportunities relating to management of data. Data Management on Hadoop encompasses data motion, process orchestration, lifecycle management, data discovery, etc. among other concerns that are beyond ETL. Ivory is a new data processing and management platform for Hadoop that solves this problem and creates additional opportunities by building on existing components within the Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop DistCp etc.) without reinventing the wheel. Ivory has been in production at InMobi, going on its second year and has been managing hundreds of feeds and processes. Ivory is being developed by engineers employed with InMobi, Hortonworks and Yahoo!. This platform addition will increase the adoption of Apache Hadoop by driving data management tractable for end users. We are therefore proposing to make Ivory an Apache open source project. == Rationale == The Ivory project aims to improve the usability of Apache Hadoop. As a result Apache Hadoop will grow its community of users by increasing the places Hadoop can be utilized and the use cases it will solve. By developing Ivory in Apache we hope to gather a diverse community of contributors, helping to ensure that Ivory is deployable for a broad range of scenarios. Members of the Hadoop development community will be able to influence Ivory’s roadmap, and contribute to it. We believe having Ivory as part of the Apache Hadoop ecosystem will be a great benefit to all of Hadoop's users. == Current Status == Ivory is widely deployed in production within InMobi and moving on to its second year. A version with a valuable set of features is developed by the list of initial committers and is hosted on github. === Meritocracy === Our intent with this incubator proposal is to start building a diverse developer community around Ivory following the Apache meritocracy model. We have wanted to make the project open source and encourage contributors from multiple organizations from the start. We plan to provide plenty of support to new developers and to quickly recruit those who make solid contributions to committer status. === Community === We are happy to report that the initial team already represents multiple organizations. We hope to extend the user and developer base further in the future and build a solid open source community around Ivory. === Core Developers === Ivory is currently being developed by three engineers from InMobi – Srikanth Sundarrajan, Shwetha G S, and Shaik Idris, two Hortonworks employees – Sanjay Radia and Venkatesh Seetharam. In addition, two Yahoo! employees, Rohini Palaniswamy and Thiruvel Thirumoolan, are also involved. Srikanth, Shwetha and Shaik are the original
Re: [VOTE] Graduate CloudStack from Incubator
Top-posting since this is a long letter and you just need to see whether it's +1 or -1 ;) So here: +1 (non-binding). I've seen your work flow from an infra perspective, and it seems vibrant and well oiled, and I'm pleased to see this vote. You're an easy team to work with (that is my opinion at least), always give feedback, and aren't afraid of using bleeding edge tools (even those written by me), which speaks warmly of your ability to adjust to new surroundings. With regards, Daniel. On 03/14/2013 05:47 PM, Chip Childers wrote: Apache CloudStack entered the Incubator in April of 2012. We have made significant progress with the project since moving over to Apache. We have 31 committers and 13 PPMC members listed on our status page at [1], not including the 8 mentors that helped guide our community through incubation. 16 of the committers and 7 of the PPMC members were added after the podling was formed. One mentor joined the project after the podling started. 3 of the initial committers that were not in the initial PPMC have now joined the PPMC. 7 of our mentors will be remaining with the project as it transitions into a TLP. We have verified that Apache CloudStack is a suitable name [2], and the CloudStack marks are being donated from Citrix to the ASF. We completed two releases (Apache CloudStack 4.0.0-incubating and Apache CloudStack 4.0.1-incubating) and are currently preparing for two more (4.0.2 and 4.1.0). Our community has created a set of bylaws for the project [3]. The community of Apache CloudStack is active, healthy, and growing and has demonstrated the ability to self-govern using accepted Apache practices. After holding a discussion [4][5], the Apache CloudStack community subsequently voted overwhelmingly to graduate [6], collecting 55 +1 votes (including 4 from IPMC members), and no +0 or -1 votes. IPMC members voting +1 in the project-level thread are: * Mohammad Nour El-Din (IPMC/mentor) [7] * Noah Slater (IPMC/mentor) [8] * Alex Karasulu (IPMC/mentor) [9] * Brett Porter (IPMC/mentor) [10] Please cast your votes: [ ] +1 Graduate Apache CloudStack from Apache Incubator [ ] +0 Indifferent to graduation status of Apache CloudStack [ ] -1 Reject graduation of Apache CloudStack from Apache Incubator because... -chip [1] http://incubator.apache.org/projects/cloudstack.html [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23 [3] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html [4] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E [5] http://markmail.org/message/3nluchj5q5waguws [6] http://markmail.org/message/ntf777ctbhdytijp [7] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E [8] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E [9] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E [10] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E Proposed Resolution: X. Establish the Apache CloudStack 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 providing and supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache CloudStack Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache CloudStack Project be and hereby is responsible for the creation and maintenance of software related to providing and supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms. RESOLVED, that the office of Vice President, Apache CloudStack 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 CloudStack Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache CloudStack 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 CloudStack Project: * Joe Brockmeier j...@apache.org * Will Chan willc...@apache.org * Chip Childers chipchild...@apache.org * Mohammad Nour El-Din mn...@apache.org *
Re: [DISCUSS] Graduation of Apache Onami
Hello, maybe my e-mail has not been seen. Any comments from the IPMC? If not, I will discuss the next steps with the Onami devs. Cheers Christian On Sun, Mar 10, 2013 at 12:04 PM, Christian Grobmeier grobme...@gmail.com wrote: Hi all, Apache Onami entered incubation before more than 3 months. Since then the community has proven to be pretty active and healthy. A look on the status page shows that a few releases have been made: http://incubator.apache.org/projects/onami.html Two minor ones (parent pom), two component releases. Another minor release is currently being voted on. Three new committers were added in the past weeks. SVNSearch shows, there is clearly one guy who is outstanding in his motivation, but others do commit as well: http://svnsearch.org/svnsearch/repos/ASF/search?path=%2Fincubator%2Fonami Mailinglist Archives show the Community is discussing in public: http://mail-archives.apache.org/mod_mbox/incubator-onami-dev/ There is only one item left on the status page, which is the podling name search. Since we have had some efforts in that area already, we do not expect any surprises. Here is the issue we created recently and expect to be closed soon: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-27 That said, the community consists of new Apache-people and some more experienced Apache-people. I do not see any problem regarding developing the Apache-way. With all that in mind, I do not see a reason this podling needs to stay any longer in the Incubator (given the podling name search is resolved). Are there any objections from the rest of the incubator to start with the graduation preparations and finally vote? Cheers, Christian -- http://www.grobmeier.de https://www.timeandbill.de -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate CloudStack from Incubator
+1 Dan On Mar 14, 2013, at 12:47 PM, Chip Childers chip.child...@sungard.com wrote: Apache CloudStack entered the Incubator in April of 2012. We have made significant progress with the project since moving over to Apache. We have 31 committers and 13 PPMC members listed on our status page at [1], not including the 8 mentors that helped guide our community through incubation. 16 of the committers and 7 of the PPMC members were added after the podling was formed. One mentor joined the project after the podling started. 3 of the initial committers that were not in the initial PPMC have now joined the PPMC. 7 of our mentors will be remaining with the project as it transitions into a TLP. We have verified that Apache CloudStack is a suitable name [2], and the CloudStack marks are being donated from Citrix to the ASF. We completed two releases (Apache CloudStack 4.0.0-incubating and Apache CloudStack 4.0.1-incubating) and are currently preparing for two more (4.0.2 and 4.1.0). Our community has created a set of bylaws for the project [3]. The community of Apache CloudStack is active, healthy, and growing and has demonstrated the ability to self-govern using accepted Apache practices. After holding a discussion [4][5], the Apache CloudStack community subsequently voted overwhelmingly to graduate [6], collecting 55 +1 votes (including 4 from IPMC members), and no +0 or -1 votes. IPMC members voting +1 in the project-level thread are: * Mohammad Nour El-Din (IPMC/mentor) [7] * Noah Slater (IPMC/mentor) [8] * Alex Karasulu (IPMC/mentor) [9] * Brett Porter (IPMC/mentor) [10] Please cast your votes: [ ] +1 Graduate Apache CloudStack from Apache Incubator [ ] +0 Indifferent to graduation status of Apache CloudStack [ ] -1 Reject graduation of Apache CloudStack from Apache Incubator because... -chip [1] http://incubator.apache.org/projects/cloudstack.html [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23 [3] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html [4] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E [5] http://markmail.org/message/3nluchj5q5waguws [6] http://markmail.org/message/ntf777ctbhdytijp [7] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E [8] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E [9] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E [10] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E Proposed Resolution: X. Establish the Apache CloudStack 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 providing and supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache CloudStack Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache CloudStack Project be and hereby is responsible for the creation and maintenance of software related to providing and supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms. RESOLVED, that the office of Vice President, Apache CloudStack 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 CloudStack Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache CloudStack 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 CloudStack Project: * Joe Brockmeier j...@apache.org * Will Chan willc...@apache.org * Chip Childers chipchild...@apache.org * Mohammad Nour El-Din mn...@apache.org * Sebastien Goasguen seb...@apache.org * Matt Richard Hogstrom hogst...@apache.org * Wido den Hollander wid...@apache.org * Alex Huang ahu...@apache.org * Jim Jagielski j...@apache.org * Alex Karasulu akaras...@apache.org * John Kinsella j...@apache.org * Kevin Kluge kl...@apache.org * Olivier Lamy ol...@apache.org * David Nalley ke4...@apache.org * Brett Porter br...@apache.org * Noah Slater nsla...@apache.org * Marcus Sorensen
Re: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
I think that this vote should be invalidated. Are the five binding votes from IPMC members? It is not 5. Also, should proposals with only 1 valid Mentor be acceptable? If two members of the IPMC step forward to Mentor MRQL I might change my mind. Regards, Dave On Mar 12, 2013, at 2:12 AM, Edward J. Yoon wrote: The VOTE has passed with 5 binding +1's and no -1s. I'll start the work to get the podling started. Thank you. On Sun, Mar 10, 2013 at 3:48 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: +1 from me (binding). Good luck! Cheers, Chris On 3/6/13 9:04 AM, Leonidas Fegaras fega...@cse.uta.edu wrote: Dear ASF members, I would like to call for a VOTE for acceptance of MRQL into the Incubator. The vote will close on Monday March 11, 2013. [ ] +1 Accept MRQL into the Apache incubator [ ] +0 Don't care. [ ] -1 Don't accept MRQL into the incubator because... Full proposal is pasted below and the corresponding wiki is http://wiki.apache.org/incubator/MRQLProposal Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Sincerely, Leonidas Fegaras = Abstract = MRQL is a query processing and optimization system for large-scale, distributed data analysis, built on top of Apache Hadoop and Hama. = Proposal = MRQL (pronounced ''miracle'') is a query processing and optimization system for large-scale, distributed data analysis. MRQL (the MapReduce Query Language) is an SQL-like query language for large-scale data analysis on a cluster of computers. The MRQL query processing system can evaluate MRQL queries in two modes: in MapReduce mode on top of Apache Hadoop or in Bulk Synchronous Parallel (BSP) mode on top of Apache Hama. The MRQL query language is powerful enough to express most common data analysis tasks over many forms of raw ''in-situ'' data, such as XML and JSON documents, binary files, and CSV documents. MRQL is more powerful than other current high-level MapReduce languages, such as Hive and PigLatin, since it can operate on more complex data and supports more powerful query constructs, thus eliminating the need for using explicit MapReduce code. With MRQL, users will be able to express complex data analysis tasks, such as PageRank, k-means clustering, matrix factorization, etc, using SQL-like queries exclusively, while the MRQL query processing system will be able to compile these queries to efficient Java code. = Background = The initial code was developed at the University of Texas of Arlington (UTA) by a research team, led by Leonidas Fegaras. The software was first released in May 2011. The original goal of this project was to build a query processing system that translates SQL-like data analysis queries to efficient workflows of MapReduce jobs. A design goal was to use HDFS as the physical storage layer, without any indexing, data partitioning, or data normalization, and to use Hadoop (without extensions) as the run-time engine. The motivation behind this work was to build a platform to test new ideas on query processing and optimization techniques applicable to the MapReduce framework. A year ago, MRQL was extended to run on Hama. The motivation for this extension was that Hadoop MapReduce jobs were required to read their input and write their output on HDFS. This simplifies reliability and fault tolerance but it imposes a high overhead to complex MapReduce workflows and graph algorithms, such as PageRank, which require repetitive jobs. In addition, Hadoop does not preserve data in memory across consecutive MapReduce jobs. This restriction requires to read data at every step, even when the data is constant. BSP, on the other hand, does not suffer from this restriction, and, under certain circumstances, allows complex repetitive algorithms to run entirely in the collective memory of a cluster. Thus, the goal was to be able to run the same MRQL queries in both modes, MapReduce and BSP, without modifying the queries: If there are enough resources available, and low latency and speed are more important than resilience, queries may run in BSP mode; otherwise, the same queries may run in MapReduce mode. BSP evaluation was found to be a good choice when fault tolerance is not critical, data (both input and intermediate) can fit in the cluster memory, and data processing requires complex/repetitive steps. The research results of this ongoing work have already been published in conferences (WebDB'11, EDBT'12, and DataCloud'12) and the authors have already received positive feedback from researchers in academia and industry who were attending these conferences. = Rationale = * MRQL will be the first general-purpose, SQL-like query language for data analysis based on BSP. Currently, many programmers prefer to code their MapReduce applications in a higher-level query language, rather than an algorithmic language. For
Re: [VOTE] Graduate CloudStack from Incubator
+1 (binding) I've been keeping a bit of an eye on that community and FWIW I think they are in a reasonable shape. Thanks, Roman. On Thu, Mar 14, 2013 at 9:47 AM, Chip Childers chip.child...@sungard.com wrote: Apache CloudStack entered the Incubator in April of 2012. We have made significant progress with the project since moving over to Apache. We have 31 committers and 13 PPMC members listed on our status page at [1], not including the 8 mentors that helped guide our community through incubation. 16 of the committers and 7 of the PPMC members were added after the podling was formed. One mentor joined the project after the podling started. 3 of the initial committers that were not in the initial PPMC have now joined the PPMC. 7 of our mentors will be remaining with the project as it transitions into a TLP. We have verified that Apache CloudStack is a suitable name [2], and the CloudStack marks are being donated from Citrix to the ASF. We completed two releases (Apache CloudStack 4.0.0-incubating and Apache CloudStack 4.0.1-incubating) and are currently preparing for two more (4.0.2 and 4.1.0). Our community has created a set of bylaws for the project [3]. The community of Apache CloudStack is active, healthy, and growing and has demonstrated the ability to self-govern using accepted Apache practices. After holding a discussion [4][5], the Apache CloudStack community subsequently voted overwhelmingly to graduate [6], collecting 55 +1 votes (including 4 from IPMC members), and no +0 or -1 votes. IPMC members voting +1 in the project-level thread are: * Mohammad Nour El-Din (IPMC/mentor) [7] * Noah Slater (IPMC/mentor) [8] * Alex Karasulu (IPMC/mentor) [9] * Brett Porter (IPMC/mentor) [10] Please cast your votes: [ ] +1 Graduate Apache CloudStack from Apache Incubator [ ] +0 Indifferent to graduation status of Apache CloudStack [ ] -1 Reject graduation of Apache CloudStack from Apache Incubator because... -chip [1] http://incubator.apache.org/projects/cloudstack.html [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23 [3] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html [4] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E [5] http://markmail.org/message/3nluchj5q5waguws [6] http://markmail.org/message/ntf777ctbhdytijp [7] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E [8] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E [9] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E [10] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E Proposed Resolution: X. Establish the Apache CloudStack 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 providing and supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache CloudStack Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache CloudStack Project be and hereby is responsible for the creation and maintenance of software related to providing and supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms. RESOLVED, that the office of Vice President, Apache CloudStack 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 CloudStack Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache CloudStack 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 CloudStack Project: * Joe Brockmeier j...@apache.org * Will Chan willc...@apache.org * Chip Childers chipchild...@apache.org * Mohammad Nour El-Din mn...@apache.org * Sebastien Goasguen seb...@apache.org * Matt Richard Hogstrom hogst...@apache.org * Wido den Hollander wid...@apache.org * Alex Huang ahu...@apache.org * Jim Jagielski j...@apache.org * Alex Karasulu akaras...@apache.org * John Kinsella j...@apache.org * Kevin Kluge kl...@apache.org * Olivier Lamy ol...@apache.org * David Nalley ke4...@apache.org *
Re: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
On Thu, Mar 14, 2013 at 4:48 PM, Dave Fisher dave2w...@comcast.net wrote: Are the five binding votes from IPMC members? It is not 5. For the record, there were 4 binding IPMC votes in favor. Mohammed Nour El-Din Alex Karasulu Tommaso Teofili Chris Mattmann Also, should proposals with only 1 valid Mentor be acceptable? In addition to Alex Karasulu, Mohammed Nour El-Din had volunteered, but seems to have been left off the version of the proposal which was VOTEd on. So unless Mohammed has withdrawn, MRQL has 2 Mentors. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
Maybe 3 including myself? or If we need to recruit one more Mentor and re-open the vote with properly updated proposal, Please let us know. I apologize that I made a mistake here. I was confused with this comment[1]. 1. http://markmail.org/message/k6s56f5wlxgqhq3k On Fri, Mar 15, 2013 at 10:06 AM, Marvin Humphrey mar...@rectangular.com wrote: On Thu, Mar 14, 2013 at 4:48 PM, Dave Fisher dave2w...@comcast.net wrote: Are the five binding votes from IPMC members? It is not 5. For the record, there were 4 binding IPMC votes in favor. Mohammed Nour El-Din Alex Karasulu Tommaso Teofili Chris Mattmann Also, should proposals with only 1 valid Mentor be acceptable? In addition to Alex Karasulu, Mohammed Nour El-Din had volunteered, but seems to have been left off the version of the proposal which was VOTEd on. So unless Mohammed has withdrawn, MRQL has 2 Mentors. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Ivory name
Thanks for bringing this to our attention. Will evaluate possible options. Regards Srikanth Sundarrajan On Fri, Mar 15, 2013 at 6:17 AM, Dmitriy Ryaboy dvrya...@gmail.com wrote: Folks, there is already a project in the general hadoop space called Ivory, and it shows up as the top result for ivory hadoop on Google. http://lintool.github.com/Ivory/ A Hadoop toolkit for web-scale information retrieval research (Disclaimer: I don't work on this project, but I do work with one of the primary authors, Jimmy Lin). -- _ The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. The firm is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.
Re: [PROPOSAL] Ivory - Hadoop data management and processing platform
Thanks. Yes, Git seems an attractive option for version control. Regards Srikanth Sundarrajan On Thu, Mar 14, 2013 at 6:26 AM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: +1, this will be a great addition to the Hadoop eco-system! The proposal looks fine overall. I quickly searched around for the name ivory, it looks to be a safe one, but someone needs to do due diligence? And I think you can chose to have git as the version control if you feel like it. Thanks, +Vinod Kumar Vavilapalli On Mar 13, 2013, at 10:00 AM, Srikanth Sundarrajan wrote: = Ivory Proposal = == Abstract == Ivory is a data processing and management solution for Hadoop designed for data motion, coordination of data pipelines, lifecycle management, and data discovery. Ivory enables end consumers to quickly onboard their data and its associated processing and management tasks on Hadoop clusters. == Proposal == Ivory will enable easy data management via declarative mechanism for Hadoop. Users of Ivory platform simply define infrastructure endpoints, data sets and processing rules declaratively. These configurations are expressed in such a way that the dependencies between these entities are explicitly described. This information about inter-dependencies between various entities allows Ivory to orchestrate and manage various data management functions. The key use cases that Ivory addresses are: * Data Motion * Process orchestration and scheduling * Policy-based Lifecycle Management * Data Discovery * Operability/Usability With these features it is possible for users to onboard their data sets with a comprehensive and holistic understanding of how, when and where their data is managed across its lifecycle. Complex functions such as retrying failures, identifying possible SLA breaches or automated handling of input data changes are now simple directives. All the administrative functions and user level functions are available via RESTful APIs. CLI is simply a wrapper over the RESTful APIs. == Background == Hadoop and its ecosystem of products have made storing and processing massive amounts of data commonplace. This has enabled numerous organizations to gain valuable insights that they never could have achieved in the past. While it is easy to leverage Hadoop for crunching large volumes of data, organizing data, managing life cycle of data and processing data is fairly involved. This is solved adequately well in a classic data platform involving data warehouses and standard ETL (extract-transform-load) tools, but remains largely unsolved today. In addition to data processing complexities, Hadoop presents new sets of challenges and opportunities relating to management of data. Data Management on Hadoop encompasses data motion, process orchestration, lifecycle management, data discovery, etc. among other concerns that are beyond ETL. Ivory is a new data processing and management platform for Hadoop that solves this problem and creates additional opportunities by building on existing components within the Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop DistCp etc.) without reinventing the wheel. Ivory has been in production at InMobi, going on its second year and has been managing hundreds of feeds and processes. Ivory is being developed by engineers employed with InMobi, Hortonworks and Yahoo!. This platform addition will increase the adoption of Apache Hadoop by driving data management tractable for end users. We are therefore proposing to make Ivory an Apache open source project. == Rationale == The Ivory project aims to improve the usability of Apache Hadoop. As a result Apache Hadoop will grow its community of users by increasing the places Hadoop can be utilized and the use cases it will solve. By developing Ivory in Apache we hope to gather a diverse community of contributors, helping to ensure that Ivory is deployable for a broad range of scenarios. Members of the Hadoop development community will be able to influence Ivory’s roadmap, and contribute to it. We believe having Ivory as part of the Apache Hadoop ecosystem will be a great benefit to all of Hadoop's users. == Current Status == Ivory is widely deployed in production within InMobi and moving on to its second year. A version with a valuable set of features is developed by the list of initial committers and is hosted on github. === Meritocracy === Our intent with this incubator proposal is to start building a diverse developer community around Ivory following the Apache meritocracy model. We have wanted to make the project open source and encourage contributors from multiple organizations from the start. We plan to provide plenty of support to new developers and to quickly recruit those who make solid contributions to committer status.
Re: [VOTE] Apache Ambari (incubating) 1.2.1 Release Candidate RC1.
+1 for the RC. On Wed, Mar 13, 2013 at 11:37 PM, Mahadev Konar maha...@apache.org wrote: Thanks to feedback from general@incubator we have updated the release artifacts with the following fixes: 1. Fixed NOTICE.txt 2. Fixed KEYS file. 3. Removed pyc files in my svn tree (unfortunately ran mvn test before building last time). 4. mvn apache-rat:check passes. The exclude files are files that cannot have Apache Headers since it breaks the run time. 5. Website has been updated (http://incubator.apache.org/ambari/ to fix all the issues mentioned earlier - thanks to Yusaku). 6. Release artifacts now use md5 and sha1. The staging Staging site is: http://people.apache.org/~mahadev/ambari-1.2.1-incubating-rc1/ with user docs at: http://incubator.apache.org/ambari/1.2.1/installing-hadoop-using-ambari/content/index.html and dev docs at: https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development SVN source tag: https://svn.apache.org/repos/asf/incubator/ambari/tags/release-1.2.1-rc1 PGP release keys (signed using 8EE2F25C) http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x0DFF492D8EE2F25C One can look into the issues fixed in this release at https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%20%221.2.1%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) thanks mahadev - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
On Mar 14, 2013, at 9:25 PM, Edward J. Yoon edwardy...@apache.org wrote: Maybe 3 including myself? Hi Edward, As you have previously pointed out Champion and Mentors are required to be IPMC members [1], [2]. So sorry you cannot be counted as a mentor/champion for MRQL. Since you have asked to be added to IPMC [3], I assume you realize you are not part of IPMC. Casting a binding vote on EasyAnt graduation [3] is not right. Please avoid creating such confusions. Suresh [1] - http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor [2] - http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Champion [3] - http://markmail.org/message/ldoyqm3o5eifyzrl [4] - http://markmail.org/message/dxqqa2cf6cpvoeyp or If we need to recruit one more Mentor and re-open the vote with properly updated proposal, Please let us know. I apologize that I made a mistake here. I was confused with this comment[1]. 1. http://markmail.org/message/k6s56f5wlxgqhq3k On Fri, Mar 15, 2013 at 10:06 AM, Marvin Humphrey mar...@rectangular.com wrote: On Thu, Mar 14, 2013 at 4:48 PM, Dave Fisher dave2w...@comcast.net wrote: Are the five binding votes from IPMC members? It is not 5. For the record, there were 4 binding IPMC votes in favor. Mohammed Nour El-Din Alex Karasulu Tommaso Teofili Chris Mattmann Also, should proposals with only 1 valid Mentor be acceptable? In addition to Alex Karasulu, Mohammed Nour El-Din had volunteered, but seems to have been left off the version of the proposal which was VOTEd on. So unless Mohammed has withdrawn, MRQL has 2 Mentors. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - 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: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
OKay I see. As you have previously pointed out Champion and Mentors are required to be IPMC members [1], [2]. So sorry you cannot be counted as a mentor/champion for MRQL. Regarding Champion, Am I not a Officer of ASF? - A candidate project shall be sponsored by an Officer or Member of the Foundation. On Fri, Mar 15, 2013 at 1:29 PM, Suresh Marru sma...@apache.org wrote: On Mar 14, 2013, at 9:25 PM, Edward J. Yoon edwardy...@apache.org wrote: Maybe 3 including myself? Hi Edward, As you have previously pointed out Champion and Mentors are required to be IPMC members [1], [2]. So sorry you cannot be counted as a mentor/champion for MRQL. Since you have asked to be added to IPMC [3], I assume you realize you are not part of IPMC. Casting a binding vote on EasyAnt graduation [3] is not right. Please avoid creating such confusions. Suresh [1] - http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor [2] - http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Champion [3] - http://markmail.org/message/ldoyqm3o5eifyzrl [4] - http://markmail.org/message/dxqqa2cf6cpvoeyp or If we need to recruit one more Mentor and re-open the vote with properly updated proposal, Please let us know. I apologize that I made a mistake here. I was confused with this comment[1]. 1. http://markmail.org/message/k6s56f5wlxgqhq3k On Fri, Mar 15, 2013 at 10:06 AM, Marvin Humphrey mar...@rectangular.com wrote: On Thu, Mar 14, 2013 at 4:48 PM, Dave Fisher dave2w...@comcast.net wrote: Are the five binding votes from IPMC members? It is not 5. For the record, there were 4 binding IPMC votes in favor. Mohammed Nour El-Din Alex Karasulu Tommaso Teofili Chris Mattmann Also, should proposals with only 1 valid Mentor be acceptable? In addition to Alex Karasulu, Mohammed Nour El-Din had volunteered, but seems to have been left off the version of the proposal which was VOTEd on. So unless Mohammed has withdrawn, MRQL has 2 Mentors. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - 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 -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Joining IPMC member
The reason of opening here is that I see mails like Request to join IPMC[1]. Moreover I already sent a mail to private@ at Feb 27. 1. http://mail-archives.apache.org/mod_mbox/incubator-general/201202.mbox/%3c87945f79-c905-4cdf-af5b-d7a9b54f3...@gmail.com%3E On Fri, Mar 15, 2013 at 1:25 AM, Suresh Marru sma...@apache.org wrote: On Mar 14, 2013, at 3:26 AM, Edward J. Yoon edwardy...@apache.org wrote: understand why virtually all ASF projects adhere to that convention now? P.S., It's been 6 years since I uploaded my first patch on HBase. I still don't know many things but I'm continuously learning from you guys ;-) Hi Edward, I do not think any one is questioning your credibility as a committer, or pmc member. I think Marvin hit it right and straight forward way. At ASF one of the few things (and primarily the only thing) like adding to a PMC is handled on private lists. Given that you have been contributing since 6 years you are certainly expected to know it. It is not healthy to side track the issue with your contributions or citing emotional reasons. Suresh On Thu, Mar 14, 2013 at 4:07 PM, Edward J. Yoon edwardy...@apache.org wrote: Yes, I think I'm not familiar with handling issues like personnel, and somewhat emotional person. However, I want to helping people who want to contribute to ASF or collaborate with ASF projects in the future. On Thu, Mar 14, 2013 at 3:46 PM, Marvin Humphrey mar...@rectangular.com wrote: Edward, are you not familiar with our custom of handling personnel matters on private lists? It has not always been that way, but do you understand why virtually all ASF projects adhere to that convention now? Marvin Humphrey On Wed, Mar 13, 2013 at 11:15 PM, Edward J. Yoon edwardy...@apache.org wrote: Hi, I just noticed that Mentor must be members of the Incubator PMC[1]. Regarding MRQL podling, I'm not only Champion but also want to be a Mentor for MRQL project. Please add me to IPMC. 1. http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor -- Best Regards, Edward J. Yoon @eddieyoon - 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 -- Best Regards, Edward J. Yoon @eddieyoon -- Best Regards, Edward J. Yoon @eddieyoon - 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 -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
