Re: [VOTE] Graduate CloudStack from Incubator
What Niall said. +1 and congrats. Danese On Mar 15, 2013, at 7:08 PM, Niall Pemberton wrote: > Thanks for laying out all the evidence for graduation - this was a > good vote email. > > +1 from me. > > Niall > > On Thu, Mar 14, 2013 at 4: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 >> * Will Chan >> * Chip Childers >> * Mohammad Nour El-Din >> * Sebastien Goasguen >> * Matt Richard Hogstrom >> * Wido den Hollander >> * Alex Huang >> * Jim Jagielski >> * Alex Karasulu >> * John Kinsella >>
Re: [PROPOSAL] Ivory - Hadoop data management and processing platform
Well the question is whether its is ok for incubation to have name that could have conflict until it is time to graduate to become the TLP. As Jakob has mentioned part of incubation is to check for the name and looks like it will fail later. It would be better to propose new name I suppose. - Henry On Fri, Mar 15, 2013 at 11:09 AM, Seetharam Venkatesh < venkat...@innerzeal.com> wrote: > Hi Henry, > > Is there a concern with the current name? The closest is a tool for > Information Retrieval. Not sure if there is an overlap. We will also bring > this up with the champion and mentors to see if this needs to be vet with > trademarks folks as well. > > Your suggestions are welcome. > > Thanks! > > > On Fri, Mar 15, 2013 at 10:18 AM, Henry Saputra >wrote: > > > HI Srikanth, > > > > So does the Ivory name stay or once the podling near graduation it will > try > > to find another name? > > > > - Henry > > > > > > On Fri, Mar 15, 2013 at 12:34 AM, Srikanth Sundarrajan < > > srikanth.sundarra...@inmobi.com> wrote: > > > > > Made few edits to the proposal ( > > > http://wiki.apache.org/incubator/IvoryProposal) as per the feedback > > > received so far. > > > > > > Regards > > > Srikanth Sundarrajan > > > > > > = 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 > > > declarative configurations are expressed in such a way that the > > > dependencies between these configured 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 and > > > Hortonworks. 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 scenario
Re: [PROPOSAL] Ivory - Hadoop data management and processing platform
+1 =) On Fri, Mar 15, 2013 at 5:22 PM, Joe Schaefer wrote: > Can we pretty-please do this *before* resources > are requested, just to save us poor infra saps > the trouble of renaming everything? > > > > > > > > > From: Jakob Homan > >To: general@incubator.apache.org > >Sent: Friday, March 15, 2013 8:18 PM > >Subject: Re: [PROPOSAL] Ivory - Hadoop data management and processing > platform > > > >As part of Incubation a suitable name search will be done to verify the > >name's appropriate. I imagine Ivory would fail this test based on the > >prior project, so this Ivory would need to find a new name. > Alternatively, > >before the vote, the Ivory folks can find another name. This has happened > >before (Howl -> HCatalog), so it's not a huge reason to be concerned. > > > > > >On Fri, Mar 15, 2013 at 5:15 PM, Dmitriy Ryaboy > wrote: > > > >> It would be awfully nice of you not to stomp on another hadoop ecosystem > >> project's google-fu when your project becomes very successful and > admired > >> across the hadoopverse :) > >> > >> Ivory isn't a fly-by-night project someone threw up on github -- it's > >> generated over a dozen peer-reviewed papers, and has many watchers and > dev > >> forks. > >> > >> I don't have a vote here, but I'd say that yes, this will lead to > confusion > >> when people look for hadoop ivory. > >> > >> D > >> > >> > >> On Fri, Mar 15, 2013 at 11:09 AM, Seetharam Venkatesh < > >> venkat...@innerzeal.com> wrote: > >> > >> > Hi Henry, > >> > > >> > Is there a concern with the current name? The closest is a tool for > >> > Information Retrieval. Not sure if there is an overlap. We will also > >> bring > >> > this up with the champion and mentors to see if this needs to be vet > with > >> > trademarks folks as well. > >> > > >> > Your suggestions are welcome. > >> > > >> > Thanks! > >> > > >> > > >> > On Fri, Mar 15, 2013 at 10:18 AM, Henry Saputra < > henry.sapu...@gmail.com > >> > >wrote: > >> > > >> > > HI Srikanth, > >> > > > >> > > So does the Ivory name stay or once the podling near graduation it > will > >> > try > >> > > to find another name? > >> > > > >> > > - Henry > >> > > > >> > > > >> > > On Fri, Mar 15, 2013 at 12:34 AM, Srikanth Sundarrajan < > >> > > srikanth.sundarra...@inmobi.com> wrote: > >> > > > >> > > > Made few edits to the proposal ( > >> > > > http://wiki.apache.org/incubator/IvoryProposal) as per the > feedback > >> > > > received so far. > >> > > > > >> > > > Regards > >> > > > Srikanth Sundarrajan > >> > > > > >> > > > = 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 > >> > > > declarative configurations are expressed in such a way that the > >> > > > dependencies between these configured 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 > >> > > >
Re: [PROPOSAL] Ivory - Hadoop data management and processing platform
+1 Niall On Wed, Mar 13, 2013 at 5:00 PM, 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
Re: [PROPOSAL] Ivory - Hadoop data management and processing platform
Can we pretty-please do this *before* resources are requested, just to save us poor infra saps the trouble of renaming everything? > > From: Jakob Homan >To: general@incubator.apache.org >Sent: Friday, March 15, 2013 8:18 PM >Subject: Re: [PROPOSAL] Ivory - Hadoop data management and processing platform > >As part of Incubation a suitable name search will be done to verify the >name's appropriate. I imagine Ivory would fail this test based on the >prior project, so this Ivory would need to find a new name. Alternatively, >before the vote, the Ivory folks can find another name. This has happened >before (Howl -> HCatalog), so it's not a huge reason to be concerned. > > >On Fri, Mar 15, 2013 at 5:15 PM, Dmitriy Ryaboy wrote: > >> It would be awfully nice of you not to stomp on another hadoop ecosystem >> project's google-fu when your project becomes very successful and admired >> across the hadoopverse :) >> >> Ivory isn't a fly-by-night project someone threw up on github -- it's >> generated over a dozen peer-reviewed papers, and has many watchers and dev >> forks. >> >> I don't have a vote here, but I'd say that yes, this will lead to confusion >> when people look for hadoop ivory. >> >> D >> >> >> On Fri, Mar 15, 2013 at 11:09 AM, Seetharam Venkatesh < >> venkat...@innerzeal.com> wrote: >> >> > Hi Henry, >> > >> > Is there a concern with the current name? The closest is a tool for >> > Information Retrieval. Not sure if there is an overlap. We will also >> bring >> > this up with the champion and mentors to see if this needs to be vet with >> > trademarks folks as well. >> > >> > Your suggestions are welcome. >> > >> > Thanks! >> > >> > >> > On Fri, Mar 15, 2013 at 10:18 AM, Henry Saputra > > >wrote: >> > >> > > HI Srikanth, >> > > >> > > So does the Ivory name stay or once the podling near graduation it will >> > try >> > > to find another name? >> > > >> > > - Henry >> > > >> > > >> > > On Fri, Mar 15, 2013 at 12:34 AM, Srikanth Sundarrajan < >> > > srikanth.sundarra...@inmobi.com> wrote: >> > > >> > > > Made few edits to the proposal ( >> > > > http://wiki.apache.org/incubator/IvoryProposal) as per the feedback >> > > > received so far. >> > > > >> > > > Regards >> > > > Srikanth Sundarrajan >> > > > >> > > > = 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 >> > > > declarative configurations are expressed in such a way that the >> > > > dependencies between these configured 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 manage
Re: [PROPOSAL] Ivory - Hadoop data management and processing platform
As part of Incubation a suitable name search will be done to verify the name's appropriate. I imagine Ivory would fail this test based on the prior project, so this Ivory would need to find a new name. Alternatively, before the vote, the Ivory folks can find another name. This has happened before (Howl -> HCatalog), so it's not a huge reason to be concerned. On Fri, Mar 15, 2013 at 5:15 PM, Dmitriy Ryaboy wrote: > It would be awfully nice of you not to stomp on another hadoop ecosystem > project's google-fu when your project becomes very successful and admired > across the hadoopverse :) > > Ivory isn't a fly-by-night project someone threw up on github -- it's > generated over a dozen peer-reviewed papers, and has many watchers and dev > forks. > > I don't have a vote here, but I'd say that yes, this will lead to confusion > when people look for hadoop ivory. > > D > > > On Fri, Mar 15, 2013 at 11:09 AM, Seetharam Venkatesh < > venkat...@innerzeal.com> wrote: > > > Hi Henry, > > > > Is there a concern with the current name? The closest is a tool for > > Information Retrieval. Not sure if there is an overlap. We will also > bring > > this up with the champion and mentors to see if this needs to be vet with > > trademarks folks as well. > > > > Your suggestions are welcome. > > > > Thanks! > > > > > > On Fri, Mar 15, 2013 at 10:18 AM, Henry Saputra > >wrote: > > > > > HI Srikanth, > > > > > > So does the Ivory name stay or once the podling near graduation it will > > try > > > to find another name? > > > > > > - Henry > > > > > > > > > On Fri, Mar 15, 2013 at 12:34 AM, Srikanth Sundarrajan < > > > srikanth.sundarra...@inmobi.com> wrote: > > > > > > > Made few edits to the proposal ( > > > > http://wiki.apache.org/incubator/IvoryProposal) as per the feedback > > > > received so far. > > > > > > > > Regards > > > > Srikanth Sundarrajan > > > > > > > > = 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 > > > > declarative configurations are expressed in such a way that the > > > > dependencies between these configured 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 ha
Re: [PROPOSAL] Ivory - Hadoop data management and processing platform
It would be awfully nice of you not to stomp on another hadoop ecosystem project's google-fu when your project becomes very successful and admired across the hadoopverse :) Ivory isn't a fly-by-night project someone threw up on github -- it's generated over a dozen peer-reviewed papers, and has many watchers and dev forks. I don't have a vote here, but I'd say that yes, this will lead to confusion when people look for hadoop ivory. D On Fri, Mar 15, 2013 at 11:09 AM, Seetharam Venkatesh < venkat...@innerzeal.com> wrote: > Hi Henry, > > Is there a concern with the current name? The closest is a tool for > Information Retrieval. Not sure if there is an overlap. We will also bring > this up with the champion and mentors to see if this needs to be vet with > trademarks folks as well. > > Your suggestions are welcome. > > Thanks! > > > On Fri, Mar 15, 2013 at 10:18 AM, Henry Saputra >wrote: > > > HI Srikanth, > > > > So does the Ivory name stay or once the podling near graduation it will > try > > to find another name? > > > > - Henry > > > > > > On Fri, Mar 15, 2013 at 12:34 AM, Srikanth Sundarrajan < > > srikanth.sundarra...@inmobi.com> wrote: > > > > > Made few edits to the proposal ( > > > http://wiki.apache.org/incubator/IvoryProposal) as per the feedback > > > received so far. > > > > > > Regards > > > Srikanth Sundarrajan > > > > > > = 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 > > > declarative configurations are expressed in such a way that the > > > dependencies between these configured 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 and > > > Hortonworks. 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 w
Re: [VOTE] Graduate CloudStack from Incubator
Thanks for laying out all the evidence for graduation - this was a good vote email. +1 from me. Niall On Thu, Mar 14, 2013 at 4: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 > * Will Chan > * Chip Childers > * Mohammad Nour El-Din > * Sebastien Goasguen > * Matt Richard Hogstrom > * Wido den Hollander > * Alex Huang > * Jim Jagielski > * Alex Karasulu > * John Kinsella > * Kevin Kluge > * Olivier Lamy > * David Nalley > * Brett Porter > * Noah Slater > * Marcus Sorensen > * Edison Su > * Hugo Trippaers > * Chiradeep Vittal > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Chip Childers be appointed
Re: [DISCUSS] Graduation of Apache Onami
On Thu, Mar 14, 2013 at 8:23 PM, Christian Grobmeier wrote: > 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. My first thought was "Is this too quick?" - but looking are the origins and whos involved - then I think its OK. The only thing I would say is that the committers voted in during graduation are still very new - so I guess there will still be some mentoring after graduation. Niall > Cheers > Christian > > On Sun, Mar 10, 2013 at 12:04 PM, Christian Grobmeier > 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 > - 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 Fri, Mar 15, 2013 at 1:28 PM, Alex Karasulu wrote: > On Fri, Mar 15, 2013 at 3:01 PM, ant elder wrote: > >> On Fri, Mar 15, 2013 at 12:16 PM, Alex Karasulu > >wrote: >> >> > On Fri, Mar 15, 2013 at 10:21 AM, Edward J. Yoon > > >wrote: >> > >> > > > could you please close the "Create MRQL" tasks in the Infra Jira >> until >> > > > the situation has been cleared up. Whenever this all has been sorted >> > > > out you can reopen the issues. >> > > >> > > Sure. >> > > >> > > Since this might not be fixed soon, proposal can be changed >> > > (especially corporation volunteers). And, thank you for your >> > > suggestion, but I'm already in initial committers list. >> > > >> > > To IPMC, I would request you to focus more on reviewing Proposal in >> > > the future. The opportunity of MRQL should not be faded by my mistake. >> > > >> > > >> > Bravo! There was no malice in the vote, just a simple mistake. If need >> be I >> > or Mo can take on the Champion role. >> > >> > Are there others from the IPMC that would be interested in mentoring >> MRQL? >> > >> > -- >> > Best Regards, >> > -- Alex >> > >> >> The champion role is really just to help the proposal through any >> discussion prior to being accepted as a poddling so thats been done and it >> makes little difference now. > > > True. I'm totally down with your reasoning. > > But don't you think it might be a formality we need to comply with, even if > it does not make sense at this stage? > > Mohammed had volunteered to be a mentor so >> lets continue as that and I'll add myself as mentor too just to help if >> anymore is needed. So that gives plenty of mentors, we don't need more >> voting for that as the Incubator PMC can update mentors as it sees fit. So >> lets just continue on with that and the poddling accepted. >> >> > Based on your presence as a mentor along with Mo and myself I see this > poddling as accepted as well. If there's pressure to fill the Champion role > it can be handled on demand. > > Ted, Dave is this situation now more acceptable and does it alleviate your > concerns? If not we want to know why and take steps to rectify the > situation accordingly. I personally really appreciate your diligence on > this matter. As a mentor I should have caught the problems you sited but > because of the Champion's ex-VP role (Hama?) I thought he was a member of > both the ASF and the IPMC. I should have checked. I know its late - but I'm +1 to accepting MRQL Niall > -- > Thanks, > -- Alex - 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 Fri, Mar 15, 2013 at 4:01 PM, Suresh Marru wrote: > I fully agree. I had a chance also to look at the proposal closely, so will > +1 if the > vote is re-opened, but I see no need for it. Its in the hands of competent > mentors > and the podling is ready to get on board. +1 to that! 'Keep calm and carry on' as they say. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Graduation of EasyAnt into Ant
More than 72 hours has passed. I count 5 binding +1, 1 non binding +1. The vote passes. Thank you all. Nicolas Le 12 mars 2013 à 16:06, Nicolas Lalevée a écrit : > Hi, > > The EasyAnt community would like to graduate as an subproject of Ant. > > The Ant PMC has just accepted: > http://mail-archives.apache.org/mod_mbox/ant-dev/201303.mbox/%3CBD5DB6B8-13BC-421F-800C-CE6CB21D7BF4%40hibnet.org%3E > > The goal is to make EasyAnt a subproject of Ant, just like Ivy and IvyDE are. > - EasyAnt code will be brought into Ant's svn tree. > - EasyAnt committers will become Ant committers but not part of the PMC (on 5 > committers, 3 > are already Ant ones, and 2 are part of Ant's PMC) > - The Ant PMC will be responsible for the code, the community, the next > releases of EasyAnt. > > Easyant has been incubating since 31/01/2011. > A release has been done the 27/02/2013. > > Some usefull links: > - the EasyAnt project incubator page: > http://incubator.apache.org/projects/easyant.html > - the archive of the mailing lists > http://mail-archives.apache.org/mod_mbox/incubator-easyant-commits/ > http://mail-archives.apache.org/mod_mbox/incubator-easyant-dev/ > - the release > http://www.apache.org/dist/incubator/easyant > > Please cast your votes over the graduation of Easyant as a subproject of Ant. > > cheers, > Nicolas > - > 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
On Mar 15, 2013, at 6:25 PM, ant elder wrote: > On Fri, Mar 15, 2013 at 1:28 PM, Alex Karasulu wrote: > >> On Fri, Mar 15, 2013 at 3:01 PM, ant elder wrote: >> >>> On Fri, Mar 15, 2013 at 12:16 PM, Alex Karasulu >>> wrote: >>> On Fri, Mar 15, 2013 at 10:21 AM, Edward J. Yoon < >> edwardy...@apache.org > wrote: >> could you please close the "Create MRQL" tasks in the Infra Jira >>> until >> the situation has been cleared up. Whenever this all has been >> sorted >> out you can reopen the issues. > > Sure. > > Since this might not be fixed soon, proposal can be changed > (especially corporation volunteers). And, thank you for your > suggestion, but I'm already in initial committers list. > > To IPMC, I would request you to focus more on reviewing Proposal in > the future. The opportunity of MRQL should not be faded by my >> mistake. > > Bravo! There was no malice in the vote, just a simple mistake. If need >>> be I or Mo can take on the Champion role. Are there others from the IPMC that would be interested in mentoring >>> MRQL? -- Best Regards, -- Alex >>> >>> The champion role is really just to help the proposal through any >>> discussion prior to being accepted as a poddling so thats been done and >> it >>> makes little difference now. >> >> >> True. I'm totally down with your reasoning. >> >> But don't you think it might be a formality we need to comply with, even if >> it does not make sense at this stage? >> >> > There has been a vote, which passed with enough binding votes, no one has > -1'd, and no one has retracted their vote. Lets wait till Monday and if the > majority vote still passes just carry on with the additional mentors. I > hope no one does -1, theres several experienced mentors now so nothing > really to be gained from forcing some new vote. > > ...ant I fully agree. I had a chance also to look at the proposal closely, so will +1 if the vote is re-opened, but I see no need for it. Its in the hands of competent mentors and the podling is ready to get on board. Suresh - 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 Fri, Mar 15, 2013 at 1:28 PM, Alex Karasulu wrote: > On Fri, Mar 15, 2013 at 3:01 PM, ant elder wrote: > > > On Fri, Mar 15, 2013 at 12:16 PM, Alex Karasulu > >wrote: > > > > > On Fri, Mar 15, 2013 at 10:21 AM, Edward J. Yoon < > edwardy...@apache.org > > > >wrote: > > > > > > > > could you please close the "Create MRQL" tasks in the Infra Jira > > until > > > > > the situation has been cleared up. Whenever this all has been > sorted > > > > > out you can reopen the issues. > > > > > > > > Sure. > > > > > > > > Since this might not be fixed soon, proposal can be changed > > > > (especially corporation volunteers). And, thank you for your > > > > suggestion, but I'm already in initial committers list. > > > > > > > > To IPMC, I would request you to focus more on reviewing Proposal in > > > > the future. The opportunity of MRQL should not be faded by my > mistake. > > > > > > > > > > > Bravo! There was no malice in the vote, just a simple mistake. If need > > be I > > > or Mo can take on the Champion role. > > > > > > Are there others from the IPMC that would be interested in mentoring > > MRQL? > > > > > > -- > > > Best Regards, > > > -- Alex > > > > > > > The champion role is really just to help the proposal through any > > discussion prior to being accepted as a poddling so thats been done and > it > > makes little difference now. > > > True. I'm totally down with your reasoning. > > But don't you think it might be a formality we need to comply with, even if > it does not make sense at this stage? > > There has been a vote, which passed with enough binding votes, no one has -1'd, and no one has retracted their vote. Lets wait till Monday and if the majority vote still passes just carry on with the additional mentors. I hope no one does -1, theres several experienced mentors now so nothing really to be gained from forcing some new vote. ...ant
Re: Looking for a volunteer to finalize the March report
Nice report Matt, it looks very good summary. Thanks for volunteering to pull this together and shepherding a good number of podlings. Suresh On Mar 15, 2013, at 4:24 PM, Matt Franklin wrote: > Last call for comments on the report. I will commit it to SVN later > this evening. > > On Thu, Mar 14, 2013 at 9:24 AM, Matt Franklin > 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 >> 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 >>> wrote: Thanks! On Mon, Mar 11, 2013 at 7:28 AM, Matt Franklin wrote: > 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 >>> 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 > - 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
Last call for comments on the report. I will commit it to SVN later this evening. On Thu, Mar 14, 2013 at 9:24 AM, Matt Franklin 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 > 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 >> wrote: >>> Thanks! >>> >>> >>> On Mon, Mar 11, 2013 at 7:28 AM, Matt Franklin >>> wrote: >>> 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 >>> > >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
On Thu, Mar 14, 2013 at 12:35 PM, Christian Grobmeier wrote: > On Thu, Mar 14, 2013 at 5:29 PM, Matt Franklin > wrote: >> On Thu, Mar 14, 2013 at 12:24 PM, Christian Grobmeier >> 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. Thanks Christian. I saw your feedback and it looks good. I usually send it to the dev list of the podling and CC the general@ list as well. > > Cheers > >> >>> >>> On Thu, Mar 14, 2013 at 2:24 PM, Matt Franklin >>> 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 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 > wrote: >> Thanks! >> >> >> On Mon, Mar 11, 2013 at 7:28 AM, Matt Franklin >> wrote: >> >>> 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 >>> > >> >>> > >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 > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Ivory - Hadoop data management and processing platform
On Fri, Mar 15, 2013 at 11:09 AM, Seetharam Venkatesh wrote: > Hi Henry, > > Is there a concern with the current name? The closest is a tool for > Information Retrieval. Not sure if there is an overlap. We will also bring > this up with the champion and mentors to see if this needs to be vet with > trademarks folks as well. I think there's a *bit* of a concern (nothing blocking, mind you!). The way I see it one of the major points of going through the incubation is to bootstrap your community. Not only community of developers, but users as well. In my experience there's no greater enemy to the community building endeavor than confusion. And given that the first thing I see on google for Hadoop Ivory is this: http://lintool.github.com/Ivory/ I'd say it is confusing. Just my 2c. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Ivory - Hadoop data management and processing platform
Hi Henry, Is there a concern with the current name? The closest is a tool for Information Retrieval. Not sure if there is an overlap. We will also bring this up with the champion and mentors to see if this needs to be vet with trademarks folks as well. Your suggestions are welcome. Thanks! On Fri, Mar 15, 2013 at 10:18 AM, Henry Saputra wrote: > HI Srikanth, > > So does the Ivory name stay or once the podling near graduation it will try > to find another name? > > - Henry > > > On Fri, Mar 15, 2013 at 12:34 AM, Srikanth Sundarrajan < > srikanth.sundarra...@inmobi.com> wrote: > > > Made few edits to the proposal ( > > http://wiki.apache.org/incubator/IvoryProposal) as per the feedback > > received so far. > > > > Regards > > Srikanth Sundarrajan > > > > = 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 > > declarative configurations are expressed in such a way that the > > dependencies between these configured 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 and > > Hortonworks. 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
Re: [PROPOSAL] Ivory - Hadoop data management and processing platform
HI Srikanth, So does the Ivory name stay or once the podling near graduation it will try to find another name? - Henry On Fri, Mar 15, 2013 at 12:34 AM, Srikanth Sundarrajan < srikanth.sundarra...@inmobi.com> wrote: > Made few edits to the proposal ( > http://wiki.apache.org/incubator/IvoryProposal) as per the feedback > received so far. > > Regards > Srikanth Sundarrajan > > = 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 > declarative configurations are expressed in such a way that the > dependencies between these configured 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 and > Hortonworks. 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 a
Re: [VOTE] Apache Ambari (incubating) 1.2.1 Release Candidate RC1.
+1 (binding) Arun On Mar 13, 2013, at 11:37 PM, Mahadev Konar 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=vindex&search=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 > -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/
Re: [VOTE] Graduate CloudStack from Incubator
+1! On Mar 14, 2013, at 12: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 > * Will Chan > * Chip Childers > * Mohammad Nour El-Din > * Sebastien Goasguen > * Matt Richard Hogstrom > * Wido den Hollander > * Alex Huang > * Jim Jagielski > * Alex Karasulu > * John Kinsella > * Kevin Kluge > * Olivier Lamy > * David Nalley > * Brett Porter > * Noah Slater > * Marcus Sorensen > * Edison Su > * Hugo Trippaers > * Chiradeep Vittal > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Chip Childers be appointed to the > office of Vice President, Apache CloudStack, to serve in accordanc
Re: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
On Mar 15, 2013, at 7:05 AM, Matt Franklin wrote: > On Fri, Mar 15, 2013 at 9:28 AM, Alex Karasulu wrote: >> On Fri, Mar 15, 2013 at 3:01 PM, ant elder wrote: >> >>> On Fri, Mar 15, 2013 at 12:16 PM, Alex Karasulu >>> wrote: >>> On Fri, Mar 15, 2013 at 10:21 AM, Edward J. Yoon wrote: >> could you please close the "Create MRQL" tasks in the Infra Jira >>> until >> the situation has been cleared up. Whenever this all has been sorted >> out you can reopen the issues. > > Sure. > > Since this might not be fixed soon, proposal can be changed > (especially corporation volunteers). And, thank you for your > suggestion, but I'm already in initial committers list. > > To IPMC, I would request you to focus more on reviewing Proposal in > the future. The opportunity of MRQL should not be faded by my mistake. > > Bravo! There was no malice in the vote, just a simple mistake. If need >>> be I or Mo can take on the Champion role. Are there others from the IPMC that would be interested in mentoring >>> MRQL? -- Best Regards, -- Alex >>> >>> The champion role is really just to help the proposal through any >>> discussion prior to being accepted as a poddling so thats been done and it >>> makes little difference now. >> >> >> True. I'm totally down with your reasoning. >> >> But don't you think it might be a formality we need to comply with, even if >> it does not make sense at this stage? >> >> Mohammed had volunteered to be a mentor so >>> lets continue as that and I'll add myself as mentor too just to help if >>> anymore is needed. So that gives plenty of mentors, we don't need more >>> voting for that as the Incubator PMC can update mentors as it sees fit. So >>> lets just continue on with that and the poddling accepted. >>> >>> >> Based on your presence as a mentor along with Mo and myself I see this >> poddling as accepted as well. If there's pressure to fill the Champion role >> it can be handled on demand. > > Keep in mind that the role of champion was expanded slightly [1]. I > think it is important to ensure that MRQL has a champion listed. I > agree that the matter should be resolved once the champion and > additional mentors are listed. > > [1]: > http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Champion > >> >> Ted, Dave is this situation now more acceptable and does it alleviate your >> concerns? In a word, yes. Adding an appropriate champion and enough mentors solves my concerns. Regards, Dave >> If not we want to know why and take steps to rectify the >> situation accordingly. I personally really appreciate your diligence on >> this matter. As a mentor I should have caught the problems you sited but >> because of the Champion's ex-VP role (Hama?) I thought he was a member of >> both the ASF and the IPMC. I should have checked. >> >> -- >> Thanks, >> -- Alex > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of EasyAnt into Ant
+ 1 (binding) Suresh On Mar 12, 2013, at 11:06 AM, Nicolas Lalevée wrote: > Hi, > > The EasyAnt community would like to graduate as an subproject of Ant. > > The Ant PMC has just accepted: > http://mail-archives.apache.org/mod_mbox/ant-dev/201303.mbox/%3CBD5DB6B8-13BC-421F-800C-CE6CB21D7BF4%40hibnet.org%3E > > The goal is to make EasyAnt a subproject of Ant, just like Ivy and IvyDE are. > - EasyAnt code will be brought into Ant's svn tree. > - EasyAnt committers will become Ant committers but not part of the PMC (on 5 > committers, 3 > are already Ant ones, and 2 are part of Ant's PMC) > - The Ant PMC will be responsible for the code, the community, the next > releases of EasyAnt. > > Easyant has been incubating since 31/01/2011. > A release has been done the 27/02/2013. > > Some usefull links: > - the EasyAnt project incubator page: > http://incubator.apache.org/projects/easyant.html > - the archive of the mailing lists > http://mail-archives.apache.org/mod_mbox/incubator-easyant-commits/ > http://mail-archives.apache.org/mod_mbox/incubator-easyant-dev/ > - the release > http://www.apache.org/dist/incubator/easyant > > Please cast your votes over the graduation of Easyant as a subproject of Ant. > > cheers, > Nicolas > - > 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
On Mar 15, 2013, at 4:07 AM, Suresh Marru wrote: > As you might know, generally speaking for PMC's merit is not transferable. > But IPMC has one exception any member of the foundation can simply ask to be > added (it still goes through the normal workflow of board acknowledgement and > such, but without a formal IPMC voting). If the requester is not a member, > IPMC also has to discuss and vote based on contributions, interest to help > out just like any other PMC. Such requests to join should go to the private > list. See [1] "Mentors MUST be on the IPMC. Any prospective Mentors who are > not yet on the IPMC should ask to be added (by election). Email the > application topriv...@incubator.apache.org. This process may take a few days." I'd like to put a finer point on this since any foundation member can simply ask to be added. VPs of PMCs are not automatically foundation members. Though many VPs of PMCs also happen to be foundation members, they were voted in by the foundation membership after a foundation member nomination. Regards, Alan
Re: [VOTE] Graduation of EasyAnt into Ant
+1 binding Regards, Alan On Mar 12, 2013, at 8:06 AM, Nicolas Lalevée wrote: > Hi, > > The EasyAnt community would like to graduate as an subproject of Ant. > > The Ant PMC has just accepted: > http://mail-archives.apache.org/mod_mbox/ant-dev/201303.mbox/%3CBD5DB6B8-13BC-421F-800C-CE6CB21D7BF4%40hibnet.org%3E > > The goal is to make EasyAnt a subproject of Ant, just like Ivy and IvyDE are. > - EasyAnt code will be brought into Ant's svn tree. > - EasyAnt committers will become Ant committers but not part of the PMC (on 5 > committers, 3 > are already Ant ones, and 2 are part of Ant's PMC) > - The Ant PMC will be responsible for the code, the community, the next > releases of EasyAnt. > > Easyant has been incubating since 31/01/2011. > A release has been done the 27/02/2013. > > Some usefull links: > - the EasyAnt project incubator page: > http://incubator.apache.org/projects/easyant.html > - the archive of the mailing lists > http://mail-archives.apache.org/mod_mbox/incubator-easyant-commits/ > http://mail-archives.apache.org/mod_mbox/incubator-easyant-dev/ > - the release > http://www.apache.org/dist/incubator/easyant > > Please cast your votes over the graduation of Easyant as a subproject of Ant. > > cheers, > Nicolas > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of EasyAnt into Ant
Edward, You are not a member of the IPMC and so your vote is not binding. Regards, Alan On Mar 13, 2013, at 5:30 PM, edward yoon wrote: > +1 (binding) > > On 3/14/2013 12:30 AM, Matt Franklin wrote: >> +1 (binding) >> >> On Tue, Mar 12, 2013 at 11:06 AM, Nicolas Lalevée >> wrote: >>> Hi, >>> >>> The EasyAnt community would like to graduate as an subproject of Ant. >>> >>> The Ant PMC has just accepted: >>> http://mail-archives.apache.org/mod_mbox/ant-dev/201303.mbox/%3CBD5DB6B8-13BC-421F-800C-CE6CB21D7BF4%40hibnet.org%3E >>> >>> The goal is to make EasyAnt a subproject of Ant, just like Ivy and IvyDE >>> are. >>> - EasyAnt code will be brought into Ant's svn tree. >>> - EasyAnt committers will become Ant committers but not part of the PMC (on >>> 5 committers, 3 >>> are already Ant ones, and 2 are part of Ant's PMC) >>> - The Ant PMC will be responsible for the code, the community, the next >>> releases of EasyAnt. >>> >>> Easyant has been incubating since 31/01/2011. >>> A release has been done the 27/02/2013. >>> >>> Some usefull links: >>> - the EasyAnt project incubator page: >>> http://incubator.apache.org/projects/easyant.html >>> - the archive of the mailing lists >>> http://mail-archives.apache.org/mod_mbox/incubator-easyant-commits/ >>> http://mail-archives.apache.org/mod_mbox/incubator-easyant-dev/ >>> - the release >>> http://www.apache.org/dist/incubator/easyant >>> >>> Please cast your votes over the graduation of Easyant as a subproject of >>> Ant. >>> >>> cheers, >>> Nicolas >>> - >>> 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 > - 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 binding Regards, Alan On Mar 14, 2013, at 9:47 AM, 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 > * Will Chan > * Chip Childers > * Mohammad Nour El-Din > * Sebastien Goasguen > * Matt Richard Hogstrom > * Wido den Hollander > * Alex Huang > * Jim Jagielski > * Alex Karasulu > * John Kinsella > * Kevin Kluge > * Olivier Lamy > * David Nalley > * Brett Porter > * Noah Slater > * Marcus Sorensen > * Edison Su > * Hugo Trippaers > * Chiradeep Vittal > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Chip Childers be appointed to the > office of Vice President, Apache CloudStack
Re: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
On Fri, Mar 15, 2013 at 9:28 AM, Alex Karasulu wrote: > On Fri, Mar 15, 2013 at 3:01 PM, ant elder wrote: > >> On Fri, Mar 15, 2013 at 12:16 PM, Alex Karasulu > >wrote: >> >> > On Fri, Mar 15, 2013 at 10:21 AM, Edward J. Yoon > > >wrote: >> > >> > > > could you please close the "Create MRQL" tasks in the Infra Jira >> until >> > > > the situation has been cleared up. Whenever this all has been sorted >> > > > out you can reopen the issues. >> > > >> > > Sure. >> > > >> > > Since this might not be fixed soon, proposal can be changed >> > > (especially corporation volunteers). And, thank you for your >> > > suggestion, but I'm already in initial committers list. >> > > >> > > To IPMC, I would request you to focus more on reviewing Proposal in >> > > the future. The opportunity of MRQL should not be faded by my mistake. >> > > >> > > >> > Bravo! There was no malice in the vote, just a simple mistake. If need >> be I >> > or Mo can take on the Champion role. >> > >> > Are there others from the IPMC that would be interested in mentoring >> MRQL? >> > >> > -- >> > Best Regards, >> > -- Alex >> > >> >> The champion role is really just to help the proposal through any >> discussion prior to being accepted as a poddling so thats been done and it >> makes little difference now. > > > True. I'm totally down with your reasoning. > > But don't you think it might be a formality we need to comply with, even if > it does not make sense at this stage? > > Mohammed had volunteered to be a mentor so >> lets continue as that and I'll add myself as mentor too just to help if >> anymore is needed. So that gives plenty of mentors, we don't need more >> voting for that as the Incubator PMC can update mentors as it sees fit. So >> lets just continue on with that and the poddling accepted. >> >> > Based on your presence as a mentor along with Mo and myself I see this > poddling as accepted as well. If there's pressure to fill the Champion role > it can be handled on demand. Keep in mind that the role of champion was expanded slightly [1]. I think it is important to ensure that MRQL has a champion listed. I agree that the matter should be resolved once the champion and additional mentors are listed. [1]: http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Champion > > Ted, Dave is this situation now more acceptable and does it alleviate your > concerns? If not we want to know why and take steps to rectify the > situation accordingly. I personally really appreciate your diligence on > this matter. As a mentor I should have caught the problems you sited but > because of the Champion's ex-VP role (Hama?) I thought he was a member of > both the ASF and the IPMC. I should have checked. > > -- > Thanks, > -- Alex - 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 Fri, Mar 15, 2013 at 3:01 PM, ant elder wrote: > On Fri, Mar 15, 2013 at 12:16 PM, Alex Karasulu >wrote: > > > On Fri, Mar 15, 2013 at 10:21 AM, Edward J. Yoon > >wrote: > > > > > > could you please close the "Create MRQL" tasks in the Infra Jira > until > > > > the situation has been cleared up. Whenever this all has been sorted > > > > out you can reopen the issues. > > > > > > Sure. > > > > > > Since this might not be fixed soon, proposal can be changed > > > (especially corporation volunteers). And, thank you for your > > > suggestion, but I'm already in initial committers list. > > > > > > To IPMC, I would request you to focus more on reviewing Proposal in > > > the future. The opportunity of MRQL should not be faded by my mistake. > > > > > > > > Bravo! There was no malice in the vote, just a simple mistake. If need > be I > > or Mo can take on the Champion role. > > > > Are there others from the IPMC that would be interested in mentoring > MRQL? > > > > -- > > Best Regards, > > -- Alex > > > > The champion role is really just to help the proposal through any > discussion prior to being accepted as a poddling so thats been done and it > makes little difference now. True. I'm totally down with your reasoning. But don't you think it might be a formality we need to comply with, even if it does not make sense at this stage? Mohammed had volunteered to be a mentor so > lets continue as that and I'll add myself as mentor too just to help if > anymore is needed. So that gives plenty of mentors, we don't need more > voting for that as the Incubator PMC can update mentors as it sees fit. So > lets just continue on with that and the poddling accepted. > > Based on your presence as a mentor along with Mo and myself I see this poddling as accepted as well. If there's pressure to fill the Champion role it can be handled on demand. Ted, Dave is this situation now more acceptable and does it alleviate your concerns? If not we want to know why and take steps to rectify the situation accordingly. I personally really appreciate your diligence on this matter. As a mentor I should have caught the problems you sited but because of the Champion's ex-VP role (Hama?) I thought he was a member of both the ASF and the IPMC. I should have checked. -- Thanks, -- Alex
Re: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
On Fri, Mar 15, 2013 at 12:16 PM, Alex Karasulu wrote: > On Fri, Mar 15, 2013 at 10:21 AM, Edward J. Yoon >wrote: > > > > could you please close the "Create MRQL" tasks in the Infra Jira until > > > the situation has been cleared up. Whenever this all has been sorted > > > out you can reopen the issues. > > > > Sure. > > > > Since this might not be fixed soon, proposal can be changed > > (especially corporation volunteers). And, thank you for your > > suggestion, but I'm already in initial committers list. > > > > To IPMC, I would request you to focus more on reviewing Proposal in > > the future. The opportunity of MRQL should not be faded by my mistake. > > > > > Bravo! There was no malice in the vote, just a simple mistake. If need be I > or Mo can take on the Champion role. > > Are there others from the IPMC that would be interested in mentoring MRQL? > > -- > Best Regards, > -- Alex > The champion role is really just to help the proposal through any discussion prior to being accepted as a poddling so thats been done and it makes little difference now. Mohammed had volunteered to be a mentor so lets continue as that and I'll add myself as mentor too just to help if anymore is needed. So that gives plenty of mentors, we don't need more voting for that as the Incubator PMC can update mentors as it sees fit. So lets just continue on with that and the poddling accepted. ...ant
Re: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
On Fri, Mar 15, 2013 at 10:21 AM, Edward J. Yoon wrote: > > could you please close the "Create MRQL" tasks in the Infra Jira until > > the situation has been cleared up. Whenever this all has been sorted > > out you can reopen the issues. > > Sure. > > Since this might not be fixed soon, proposal can be changed > (especially corporation volunteers). And, thank you for your > suggestion, but I'm already in initial committers list. > > To IPMC, I would request you to focus more on reviewing Proposal in > the future. The opportunity of MRQL should not be faded by my mistake. > > Bravo! There was no malice in the vote, just a simple mistake. If need be I or Mo can take on the Champion role. Are there others from the IPMC that would be interested in mentoring MRQL? -- Best Regards, -- Alex
Re: Joining IPMC member
Hi Edward, As you might know, generally speaking for PMC's merit is not transferable. But IPMC has one exception any member of the foundation can simply ask to be added (it still goes through the normal workflow of board acknowledgement and such, but without a formal IPMC voting). If the requester is not a member, IPMC also has to discuss and vote based on contributions, interest to help out just like any other PMC. Such requests to join should go to the private list. See [1] "Mentors MUST be on the IPMC. Any prospective Mentors who are not yet on the IPMC should ask to be added (by election). Email the application to priv...@incubator.apache.org. This process may take a few days." I can see the source of your confusion both for asking on the general list and also interpreting an officer can be a champion. Its a misunderstanding, no worries. Your enthusiasm to help MRQL is certainly appreciated and once we have a IPMC member volunteer to champion the podling, everything should be back on track. I do not think MRQL will be hampered, just a delay. Its parked on the runway waiting to take off soon. Meanwhile sit back relax and have fun hacking. Suresh [1] - http://incubator.apache.org/guides/mentor.html On Mar 15, 2013, at 12:51 AM, Edward J. Yoon wrote: > 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 wrote: >> On Mar 14, 2013, at 3:26 AM, Edward J. Yoon 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 >>> 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 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 > 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 > - To unsubscribe, e-mail
Re: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
Hi On Fri, Mar 15, 2013 at 2:06 AM, Marvin Humphrey wrote: > On Thu, Mar 14, 2013 at 4:48 PM, Dave Fisher > 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. > No I didn't > > Marvin Humphrey > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Thanks - Mohammad Nour "Life is like riding a bicycle. To keep your balance you must keep moving" - Albert Einstein
Re: [VOTE] Graduate CloudStack from Incubator
+1 non-binding -- Andrei Savu On Fri, Mar 15, 2013 at 8:15 AM, Ioan Eugen Stan wrote: > +1 non-binding > -- > Ioan Eugen Stan > > - > 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 Fri, Mar 15, 2013 at 9:21 AM, Edward J. Yoon wrote: >> could you please close the "Create MRQL" tasks in the Infra Jira until >> the situation has been cleared up. Whenever this all has been sorted >> out you can reopen the issues. > > Sure. > > Since this might not be fixed soon, proposal can be changed > (especially corporation volunteers). And, thank you for your > suggestion, but I'm already in initial committers list. > > To IPMC, I would request you to focus more on reviewing Proposal in > the future. The opportunity of MRQL should not be faded by my mistake. +1 I can tell you this issue is already discussed. I am pretty sure there will be soon an outcome. Thanks for your patience! Cheers Christian > On Fri, Mar 15, 2013 at 4:13 PM, Christian Grobmeier > wrote: >> Hi Eddie, >> >> On Fri, Mar 15, 2013 at 8:02 AM, Ted Dunning wrote: >>> No. This doesn't work. That sentence is followed by another: >>> >>> Where the Champion is not a Member of the Foundation (i.e. is an Officer only), the Champion shall be a member of the PMC of the Sponsor. >>> >>> >>> The Sponsor here is the Incubator. The PMC of the Sponsor is the IPMC. >>> You aren't an IPMC member. Therefore, since you are not a Member and you >>> aren't a member of the PMC of the Sponsor, you can't be the champion. >> >> could you please close the "Create MRQL" tasks in the Infra Jira until >> the situation has been cleared up. Whenever this all has been sorted >> out you can reopen the issues. >> >> On another note: >> >> There were now multiple issues with this podling. Can I make a >> suggestion? What, if you would not join as a Mentor/Champion but as an >> initial committer. As you said yourself you do not know all the rules >> but you are willing to learn. Joining this podling would be a great >> chance to learn all the rules, which are mandatory to know when you >> want to mentor a podling. >> >> If that is ok, I furthermore suggest you write to general@ that you >> are going to add your name to the initial committers list. I guess >> nobody will object. >> >> Then there is a need for a champion; please ask on general@ in another >> mail for somebody who has the interest. >> >> When it comes to mentors, most people say a podling should start with >> 3. There are a few podlings with 2 mentors. I guess it could work out. >> >> Whenever you have the champion, please ask him to create a new >> acceptance vote for MRQL. I guess this one would be ok since Alex and >> Mo already +1, but I also feel it would be a good idea to make it >> proper. >> >> My 2 cents - other IPMC members might see things different. >> >> Cheers >> Christian >> >> >> >>> On Thu, Mar 14, 2013 at 9:43 PM, Edward J. Yoon >>> wrote: >>> > 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." >> >> >> >> -- >> 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 >> > > > > -- > 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 > -- 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: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
> could you please close the "Create MRQL" tasks in the Infra Jira until > the situation has been cleared up. Whenever this all has been sorted > out you can reopen the issues. Sure. Since this might not be fixed soon, proposal can be changed (especially corporation volunteers). And, thank you for your suggestion, but I'm already in initial committers list. To IPMC, I would request you to focus more on reviewing Proposal in the future. The opportunity of MRQL should not be faded by my mistake. On Fri, Mar 15, 2013 at 4:13 PM, Christian Grobmeier wrote: > Hi Eddie, > > On Fri, Mar 15, 2013 at 8:02 AM, Ted Dunning wrote: >> No. This doesn't work. That sentence is followed by another: >> >> Where the Champion is not a Member of the Foundation (i.e. is an Officer >>> only), the Champion shall be a member of the PMC of the Sponsor. >> >> >> The Sponsor here is the Incubator. The PMC of the Sponsor is the IPMC. >> You aren't an IPMC member. Therefore, since you are not a Member and you >> aren't a member of the PMC of the Sponsor, you can't be the champion. > > could you please close the "Create MRQL" tasks in the Infra Jira until > the situation has been cleared up. Whenever this all has been sorted > out you can reopen the issues. > > On another note: > > There were now multiple issues with this podling. Can I make a > suggestion? What, if you would not join as a Mentor/Champion but as an > initial committer. As you said yourself you do not know all the rules > but you are willing to learn. Joining this podling would be a great > chance to learn all the rules, which are mandatory to know when you > want to mentor a podling. > > If that is ok, I furthermore suggest you write to general@ that you > are going to add your name to the initial committers list. I guess > nobody will object. > > Then there is a need for a champion; please ask on general@ in another > mail for somebody who has the interest. > > When it comes to mentors, most people say a podling should start with > 3. There are a few podlings with 2 mentors. I guess it could work out. > > Whenever you have the champion, please ask him to create a new > acceptance vote for MRQL. I guess this one would be ok since Alex and > Mo already +1, but I also feel it would be a good idea to make it > proper. > > My 2 cents - other IPMC members might see things different. > > Cheers > Christian > > > >> On Thu, Mar 14, 2013 at 9:43 PM, Edward J. Yoon wrote: >> >>> > 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." > > > > -- > 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 > -- 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: [PROPOSAL] Ivory - Hadoop data management and processing platform
Made few edits to the proposal ( http://wiki.apache.org/incubator/IvoryProposal) as per the feedback received so far. Regards Srikanth Sundarrajan = 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 declarative configurations are expressed in such a way that the dependencies between these configured 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 and Hortonworks. 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 Sunderrajan, Shwetha G S, and Shaik Idris, two Hortonworks employees – Sanjay Radia and Venkatesh Seetharam. In addition, Rohini Palaniswamy and Thiruvel Thirumoolan, were also involved in the initial design discussions. Srikanth, Shwetha and Shaik are the original developers. All the eng
Re: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
Hi Eddie, On Fri, Mar 15, 2013 at 8:02 AM, Ted Dunning wrote: > No. This doesn't work. That sentence is followed by another: > > Where the Champion is not a Member of the Foundation (i.e. is an Officer >> only), the Champion shall be a member of the PMC of the Sponsor. > > > The Sponsor here is the Incubator. The PMC of the Sponsor is the IPMC. > You aren't an IPMC member. Therefore, since you are not a Member and you > aren't a member of the PMC of the Sponsor, you can't be the champion. could you please close the "Create MRQL" tasks in the Infra Jira until the situation has been cleared up. Whenever this all has been sorted out you can reopen the issues. On another note: There were now multiple issues with this podling. Can I make a suggestion? What, if you would not join as a Mentor/Champion but as an initial committer. As you said yourself you do not know all the rules but you are willing to learn. Joining this podling would be a great chance to learn all the rules, which are mandatory to know when you want to mentor a podling. If that is ok, I furthermore suggest you write to general@ that you are going to add your name to the initial committers list. I guess nobody will object. Then there is a need for a champion; please ask on general@ in another mail for somebody who has the interest. When it comes to mentors, most people say a podling should start with 3. There are a few podlings with 2 mentors. I guess it could work out. Whenever you have the champion, please ask him to create a new acceptance vote for MRQL. I guess this one would be ok since Alex and Mo already +1, but I also feel it would be a good idea to make it proper. My 2 cents - other IPMC members might see things different. Cheers Christian > On Thu, Mar 14, 2013 at 9:43 PM, Edward J. Yoon wrote: > >> > 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." -- 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: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator
No. This doesn't work. That sentence is followed by another: Where the Champion is not a Member of the Foundation (i.e. is an Officer > only), the Champion shall be a member of the PMC of the Sponsor. The Sponsor here is the Incubator. The PMC of the Sponsor is the IPMC. You aren't an IPMC member. Therefore, since you are not a Member and you aren't a member of the PMC of the Sponsor, you can't be the champion. On Thu, Mar 14, 2013 at 9:43 PM, Edward J. Yoon wrote: > > 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."
