Re: [VOTE] Recommend 'Apache Druid graduation to Top Level Project' resolution to the board
+1 (binding) Congrats! Great to see such an active community. -- Andrei Savu On Tue, Aug 13, 2019 at 12:03 AM Gian Merlino wrote: > The Apache Druid community has recently discussed our readiness for > graduation [1] and voted on it affirmatively [2, 3]. We've also assessed > ourselves against the maturity model [4] and collaborated on a resolution > for graduation including PMC membership and PMC chair. > > The community's achievements since entering the Incubator in early 2018 > include the following: > > - Accepted 1240 patches from 142 contributors > - Performed 5 releases with 4 different release managers > - Invited 10 new committers > - Some time later on, invited all 10 of those new committers to join the > PMC (those that have accepted are named in the resolution below) > - Migrated development to Apache's GitHub org: > https://github.com/apache/incubator-druid > - Migrated our web site to https://druid.apache.org/ > - Migrated developer conversations to the list at d...@druid.apache.org > > Now the Druid community is bringing the attached resolution up for a formal > IPMC VOTE. > > Please take a minute to vote on whether or not Apache Druid should graduate > to a Top Level Project by responding with one of the following: > > [ ] +1 Apache Druid should graduate > [ ] 0 No opinion > [ ] -1 Apache Druid should not graduate because... > > The VOTE is open for a minimum of 72 hours. > > [1] > > https://lists.apache.org/thread.html/68fcc3d2fc66c7f559e2c9dd02478d17f195565fecdb07ed53bc965e@%3Cdev.druid.apache.org%3E > [2] > > https://lists.apache.org/thread.html/10c615a7648db14a268759be91f4b1eff448960f5338e0d416c7373a@%3Cdev.druid.apache.org%3E > [3] > > https://lists.apache.org/thread.html/7517dd38fbeb28978b1188bed1d69e91445927d13d520a4c71ae9fcf@%3Cdev.druid.apache.org%3E > [4] https://gist.github.com/gianm/33ae4d61ebaa8b8714d9e2f51a11e7f7 > > -- > > Establish Apache Druid 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 analytical database > software, for distribution at no charge to the public. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > Committee (PMC), to be known as the "The Apache Druid Project", > be and hereby is established pursuant to Bylaws of the > Foundation; and be it further > > RESOLVED, that The Apache Druid Project be and hereby is > responsible for the creation and maintenance of an analytical > database software project; and be it further > > RESOLVED, that the office of "Vice President, Druid" 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 > Druid Project, and to have primary responsibility for > management of the projects within the scope of responsibility of > The Apache Druid 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 Druid Project: > > * Benedict Jin (asdf2...@apache.org) > * Charles Allen(cral...@apache.org) > * Clint Wylie (cwy...@apache.org) > * David Lim(david...@apache.org) > * Dylan Wylie (dylanwy...@apache.org) > * Eric Tschetter (ched...@apache.org) > * Fangjin Yang (f...@apache.org) > * Gian Merlino (g...@apache.org) > * Himanshu Gupta (himans...@apache.org) > * Jihoon Son (jihoon...@apache.org) > * Jonathan Wei (jon...@apache.org) > * Julian Hyde (jh...@apache.org) > * Kurt Young (k...@apache.org) > * Lijin Bin(binli...@apache.org) > * Maxime Beauchemin(maximebeauche...@apache.org) > * Niketh Sabbineni (nik...@apache.org) > * Nishant Bangarwa (nish...@apache.org) > * P. Taylor Goetz (ptgo...@apache.org) > * Parag Jain (pja...@apache.org) > * Roman Leventov (leven...@apache.org) > * Slim Bouguerra (bs...@apache.org) > * Surekha Saharan (sure...@apache.org) > * Xavier Léauté(x...@apache.org) > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gian Merlino > be and hereby is appointed to the office of Vice President, > Druid, to serve in accordance with and subject to the direction > of the Board of Directors and the Bylaws of the Foundation until > death, resignation, retirement, removal or disqualification, or > until a successor is appointed; and be it further > > RESOLVED, that the initial Apache Druid Project be and hereby > is tasked with the migration and rationalization of the Apache > Incubator Druid podling; and be it further > > RESOLVED, that all responsibility pertaining to the Apache > Incubator Druid podling encumbered upon the Apache Incubator > PMC are hereafter discharged. >
Re: [VOTE] Accept Impala into the Apache Incubator
+1 (binding) -- Andrei Savu On Sun, Nov 29, 2015 at 12:05 PM, Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > +1 (binding) > > Regards > JB > > > On 11/24/2015 10:03 PM, Henry Robinson wrote: > >> Hi - >> >> The [DISCUSS] thread has been quiet for a few days, so I think there's >> been >> sufficient opportunity for discussion around our proposal to bring Impala >> to the ASF Incubator. >> >> I'd like to call a VOTE on that proposal, which is on the wiki at >> https://wiki.apache.org/incubator/ImpalaProposal, and which I've pasted >> below. >> >> During the discussion period, the proposal has been amended to add Brock >> Noland as a new mentor, to add one missed committer from the list and to >> correct some issues with the dependency list. >> >> Please cast your votes as follows: >> >> [] +1, accept Impala into the Incubator >> [] +/-0, non-counted vote to express a disposition >> [] -1, do not accept Impala into the Incubator (please give your >> reason(s)) >> >> As with the concurrent Kudu vote, I propose leaving the vote open for a >> full seven days (to close at Tuesday, December 1st at noon PST), due to >> the >> upcoming US holiday. >> >> Thanks, >> Henry >> >> >> >> = Abstract = >> Impala is a high-performance C++ and Java SQL query engine for data stored >> in Apache Hadoop-based clusters. >> >> = Proposal = >> >> We propose to contribute the Impala codebase and associated artifacts >> (e.g. >> documentation, web-site content etc.) to the Apache Software Foundation >> with the intent of forming a productive, meritocratic and open community >> around Impala’s continued development, according to the ‘Apache Way’. >> >> Cloudera owns several trademarks regarding Impala, and proposes to >> transfer >> ownership of those trademarks in full to the ASF. >> >> = Background = >> Engineers at Cloudera developed Impala and released it as an >> Apache-licensed open-source project in Fall 2012. Impala was written as a >> brand-new, modern C++ SQL engine targeted from the start for data stored >> in >> Apache Hadoop clusters. >> >> Impala’s most important benefit to users is high-performance, making it >> extremely appropriate for common enterprise analytic and business >> intelligence workloads. This is achieved by a number of software >> techniques, including: native support for data stored in HDFS and related >> filesystems, just-in-time compilation and optimization of individual query >> plans, high-performance C++ codebase and massively-parallel distributed >> architecture. In benchmarks, Impala is routinely amongst the very highest >> performing SQL query engines. >> >> = Rationale = >> >> Despite the exciting innovation in the so-called ‘big-data’ space, SQL >> remains by far the most common interface for interacting with data in both >> traditional warehouses and modern ‘big-data’ clusters. There is clearly a >> need, as evidenced by the eager adoption of Impala and other SQL engines >> in >> enterprise contexts, for a query engine that offers the familiar SQL >> interface, but that has been specifically designed to operate in massive, >> distributed clusters rather than in traditional, fixed-hardware, >> warehouse-specific deployments. Impala is one such query engine. >> >> We believe that the ASF is the right venue to foster an open-source >> community around Impala’s development. We expect that Impala will benefit >> from more productive collaboration with related Apache projects, and under >> the auspices of the ASF will attract talented contributors who will push >> Impala’s development forward at pace. >> >> We believe that the timing is right for Impala’s development to move >> wholesale to the ASF: Impala is well-established, has been Apache-licensed >> open-source for more than three years, and the core project is relatively >> stable. We are excited to see where an ASF-based community can take Impala >> from this strong starting point. >> >> = Initial Goals = >> Our initial goals are as follows: >> >> * Establish ASF-compatible engineering practices and workflows >> * Refactor and publish existing internal build scripts and test >> infrastructure, in order to make them usable by any community member. >> * Transfer source code, documentation and associated artifacts to the >> ASF. >> * Grow the user and developer communities >> >> = Current Status = >> &g
Re: [VOTE] Accept Kudu into the Apache Incubator
+1 (binding) -- Andrei Savu On Tue, Nov 24, 2015 at 11:32 AM, Todd Lipcon <t...@apache.org> wrote: > Hi all, > > Discussion on the [DISCUSS] thread seems to have wound down, so I'd like to > call a VOTE on acceptance of Kudu into the ASF Incubator. The proposal is > pasted below and also available on the wiki at: > https://wiki.apache.org/incubator/KuduProposal > > The proposal is unchanged since the original version, except for the > addition of Carl Steinbach as a Mentor. > > Please cast your votes: > > [] +1, accept Kudu into the Incubator > [] +/-0, positive/negative non-counted expression of feelings > [] -1, do not accept Kudu into the incubator (please state reasoning) > > Given the US holiday this week, I imagine many folks are traveling or > otherwise offline. So, let's run the vote for a full week rather than the > traditional 72 hours. Unless the IPMC objects to the extended voting > period, the vote will close on Tues, Dec 1st at noon PST. > > Thanks > -Todd > - > > = Kudu Proposal = > > == Abstract == > > Kudu is a distributed columnar storage engine built for the Apache Hadoop > ecosystem. > > == Proposal == > > Kudu is an open source storage engine for structured data which supports > low-latency random access together with efficient analytical access > patterns. Kudu distributes data using horizontal partitioning and > replicates each partition using Raft consensus, providing low > mean-time-to-recovery and low tail latencies. Kudu is designed within the > context of the Apache Hadoop ecosystem and supports many integrations with > other data analytics projects both inside and outside of the Apache > Software Foundation. > > > > We propose to incubate Kudu as a project of the Apache Software Foundation. > > == Background == > > In recent years, explosive growth in the amount of data being generated and > captured by enterprises has resulted in the rapid adoption of open source > technology which is able to store massive data sets at scale and at low > cost. In particular, the Apache Hadoop ecosystem has become a focal point > for such “big data” workloads, because many traditional open source > database systems have lagged in offering a scalable alternative. > > > > Structured storage in the Hadoop ecosystem has typically been achieved in > two ways: for static data sets, data is typically stored on Apache HDFS > using binary data formats such as Apache Avro or Apache Parquet. However, > neither HDFS nor these formats has any provision for updating individual > records, or for efficient random access. Mutable data sets are typically > stored in semi-structured stores such as Apache HBase or Apache Cassandra. > These systems allow for low-latency record-level reads and writes, but lag > far behind the static file formats in terms of sequential read throughput > for applications such as SQL-based analytics or machine learning. > > > > Kudu is a new storage system designed and implemented from the ground up to > fill this gap between high-throughput sequential-access storage systems > such as HDFS and low-latency random-access systems such as HBase or > Cassandra. While these existing systems continue to hold advantages in some > situations, Kudu offers a “happy medium” alternative that can dramatically > simplify the architecture of many common workloads. In particular, Kudu > offers a simple API for row-level inserts, updates, and deletes, while > providing table scans at throughputs similar to Parquet, a commonly-used > columnar format for static data. > > > > More information on Kudu can be found at the existing open source project > website: http://getkudu.io and in particular in the Kudu white-paper PDF: > http://getkudu.io/kudu.pdf from which the above was excerpted. > > == Rationale == > > As described above, Kudu fills an important gap in the open source storage > ecosystem. After our initial open source project release in September 2015, > we have seen a great amount of interest across a diverse set of users and > companies. We believe that, as a storage system, it is critical to build an > equally diverse set of contributors in the development community. Our > experiences as committers and PMC members on other Apache projects have > taught us the value of diverse communities in ensuring both longevity and > high quality for such foundational systems. > > == Initial Goals == > > * Move the existing codebase, website, documentation, and mailing lists to > Apache-hosted infrastructure > * Work with the infrastructure team to implement and approve our code > review, build, and testing workflows in the context of the ASF > * Incremental development and releases
Re: [VOTE] Release Apache Twill-0.5.0-incubating
+1 checked the source archive and signatures On Thu, Feb 26, 2015 at 1:44 PM, Patrick Hunt ph...@apache.org wrote: +1. the sig/xsum validate. Rat ran clean and the files all look right to me. Patrick On Wed, Feb 25, 2015 at 5:36 PM, Henry Saputra henry.sapu...@gmail.com wrote: Signature file look good Checksum files looks good NOTICE file looks good LICENSE file look good DISCLAIMER file exist No third party executables Source code compiled +1 (binding) Congrats! On Tue, Feb 24, 2015 at 12:52 PM, Terence Yim cht...@apache.org wrote: Hi all, This is to call for a vote on releasing Apache Twill 0.5.0-incubating. This is the sixth release for Twill. Apache Twill is an abstraction over Apache Hadoop YARN that reduces the complexity of developing distributed applications. Vote on twill-dev: http://s.apache.org/lfz Result on vote on twill-dev: http://s.apache.org/YQY The source tarball, including signatures, digests, etc can be found at: https://dist.apache.org/repos/dist/dev/incubator/twill/0.5.0-incubating-rc1/src/ The tag to be voted upon is v0.5.0-incubating: https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=shortlog;h=refs/tags/v0.5.0-incubating The release hash is 01cbe903b37eb981b8fab0bde9d9ff0f7dc4fd5c https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=commit;h=01cbe903b37eb981b8fab0bde9d9ff0f7dc4fd5c The Nexus Staging URL: https://repository.apache.org/content/repositories/orgapachetwill-1016 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/chtyim.asc KEYS file available here: https://dist.apache.org/repos/dist/dev/incubator/twill/KEYS For information about the contents of this release see: https://dist.apache.org/repos/dist/dev/incubator/twill/0.5.0-incubating-rc1/CHANGES.txt Please vote on releasing this package as Apache Twill 0.5.0-incubating The vote will be open for 72 hours. [ ] +1 Release this package as Apache Twill 0.5.0-incubating [ ] +0 no opinion [ ] -1 Do not release this package because ... Thanks, Terence - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Twill-0.3.0-incubating [rc1]
+1 On Fri, Aug 15, 2014 at 6:52 PM, Terence Yim cht...@apache.org wrote: Hi all, This is to call for a vote for releasing twill-0.3.0-incubating. This is the third release for Twill. Vote on twill-dev: http://s.apache.org/aS1 Result on vote on twill-dev: http://s.apache.org/vTq The source tarball, including signatures, digests, etc can be found at: https://dist.apache.org/repos/dist/dev/incubator/twill/0.3.0-incubating-rc1/src The tag to be voted upon is v0.3.0-incubating: https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=shortlog;h=refs/tags/v0.3.0-incubating The release hash is a721588a19ae454243dcae9072d3bf03d8be97d6 https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=commit;h=a721588a19ae454243dcae9072d3bf03d8be97d6 The Nexus Staging URL: https://repository.apache.org/content/repositories/orgapachetwill-1002 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/chtyim.asc KEYS file available here: https://dist.apache.org/repos/dist/dev/incubator/twill/KEYS For information about the contents of this release see: https://dist.apache.org/repos/dist/dev/incubator/twill/0.3.0-incubating-rc1/CHANGES.txt Please vote on releasing this package as Apache Twill 0.3.0-incubating The vote will be open for 72 hours. [ ] +1 Release this package as Apache Twill 0.3.0-incubating [ ] +0 no opinion [ ] -1 Do not release this package because ... Thanks, The Apache Twill Team - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Parquet into the incubator
+1 (binding) -- Andrei Savu (from mobile) On May 18, 2014 3:15 PM, Chris Aniszczyk caniszc...@gmail.com wrote: Based on the results of the discussion thread: http://mail-archives.apache.org/mod_mbox/incubator-general/201405.mbox/%3CCAJg1wMRGhLu4P7LeVQB%2B5K0C-fr-pw2448uj%3D6-3zHag4F1EbA%40mail.gmail.com%3E I would like to call a vote on accepting Parquet into the incubator. https://wiki.apache.org/incubator/ParquetProposal [ ] +1 Accept Parquet into the Incubator [ ] +0 Indifferent to the acceptance of Parquet [ ] -1 Do not accept Parquet because ... The vote will be open until Thursday May 22nd 18:00 UTC. = Parquet Proposal = == Abstract == Parquet is a columnar storage format for Hadoop. == Proposal == We created Parquet to make the advantages of compressed, efficient columnar data representation available to any project in the Hadoop ecosystem, regardless of the choice of data processing framework, data model, or programming language. == Background == Parquet is built from the ground up with complex nested data structures in mind, and uses the repetition/definition level approach to encoding such data structures, as popularized by Google Dremel ( https://blog.twitter.com/2013/dremel-made-simple-with-parquet). We believe this approach is superior to simple flattening of nested name spaces. Parquet is built to support very efficient compression and encoding schemes. Parquet allows compression schemes to be specified on a per-column level, and is future-proofed to allow adding more encodings as they are invented and implemented. We separate the concepts of encoding and compression, allowing parquet consumers to implement operators that work directly on encoded data without paying decompression and decoding penalty when possible. == Rationale == Parquet is built to be used by anyone. We believe that an efficient, well-implemented columnar storage substrate should be useful to all frameworks without the cost of extensive and difficult to set up dependencies. Furthermore, the rapid growth of Parquet community is empowered by open source. We believe the Apache foundation is a great fit as the long-term home for Parquet, as it provides an established process for community-driven development and decision making by consensus. This is exactly the model we want for future Parquet development. == Initial Goals == * Move the existing codebase to Apache * Integrate with the Apache development process * Ensure all dependencies are compliant with Apache License version 2.0 * Incremental development and releases per Apache guidelines == Current Status == Parquet has undergone 2 major releases: https://github.com/Parquet/parquet-format/releases of the core format and 22 releases: https://github.com/Parquet/parquet-mr/releases of the supporting set of Java libraries. The Parquet source is currently hosted at GitHub, which will seed the Apache git repository. === Meritocracy === We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. === Community === There is a large need for an advanced columnar storage format for Hadoop. Parquet is being used in production by many organizations (see https://github.com/Parquet/parquet-mr/blob/master/PoweredBy.md) * Cloudera: https://twitter.com/HenryR/statuses/324222874011451392 * Criteo: https://twitter.com/julsimon/statuses/312114074911666177 * Salesforce: https://twitter.com/TwitterOSS/statuses/392734610116726784 * Stripe: https://twitter.com/avibryant/statuses/391339949250715648 * Twitter: https://twitter.com/J_/statuses/315844725611581441 By bringing Parquet into Apache, we believe that the community will grow even bigger. === Core Developers === Parquet was initially developed as a collaboration between Twitter, Cloudera and Criteo. See https://blog.twitter.com/2013/announcing-parquet-10-columnar-storage-for-hadoop === Alignment === We believe that having Parquet at Apache will help further the growth of the big-data community, as it will encourage cooperation within the greater ecosystem of projects spawned by Apache Hadoop. The alignment is also beneficial to other Apache communities (such as Hadoop, Hive, Avro). == Known Risks == === Orphaned Products === The risk of the Parquet project being abandoned is minimal. There are many organizations using Parquet in production, including Twitter, Cloudera, Stripe, and Salesforce ( http://blog.cloudera.com/blog/2013/10/parquet-at-salesforce-com/). === Inexperience with Open Source === Parquet has existed as a healthy open source for one year. During that time, we have curated an open-source community successfully, attracting
Re: [VOTE] Accept Brooklyn into the Incubator
+1 -- Andrei Savu On Mon, Apr 28, 2014 at 6:49 AM, Chip Childers chipchild...@apache.orgwrote: Based on the previous discussion of accepting Brooklyn into the Apache Incubator as a podling, I'd like to call a vote for this now. [ ] +1 Accept Brooklyn into the Incubator [ ] +/-0 Indifferent to the acceptance of Brooklyn [ ] -1 Do not accept Brooklyn because... The proposal can be found here: https://wiki.apache.org/incubator/BrooklynProposal (For the IPMC members, I believe we typically lock the proposal page making it read-only during the voting. I'm not sure how to do this, or if I'm remembering correctly. Can someone clarify? I'll watch that page to be sure there are no changes during the voting process.) -chip - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Brooklyn
On Wed, Apr 23, 2014 at 7:28 AM, Chip Childers chipchild...@apache.orgwrote: This is the discussion thread for this proposal. We would also like to solicit contributions from additional IPMC members willing to mentor the potential podling. Anyone interested? It's great to see Brooklyn joining the Apache Incubator! I'm happy to help as a mentor. -- Andrei
Re: [VOTE] Release Apache Twill-0.2.0-incubating [rc1]
+1 (binding) -- Andrei Savu On Mon, Apr 7, 2014 at 2:11 PM, aakash aakash email2aak...@gmail.comwrote: +1 Release this package as Apache Twill 0.2.0-incubating -Aakash On Mon, Apr 7, 2014 at 10:24 AM, Terence Yim cht...@gmail.com wrote: Hi all, This vote has been up for over 72 hrs, but only got +1 binding vote and no 0 or -1 vote. May I get some attention from the committee to take a look at this release? Thanks, Terence On Fri, Apr 4, 2014 at 9:15 AM, Terence Yim cht...@gmail.com wrote: On Fri, Apr 4, 2014 at 3:21 AM, sebb seb...@gmail.com wrote: On 3 April 2014 06:04, Terence Yim cht...@gmail.com wrote: Hi all, This is to call for a vote for releasing twill-0.2.0-incubating. This is the second release for Twill. Vote on twill-dev: http://s.apache.org/ZJP Result on vote on twill-dev: http://s.apache.org/ksD The source tarball, including signatures, digests, etc can be found at: https://dist.apache.org/repos/dist/dev/incubator/twill/0.2.0-incubating-rc1/src The tag to be voted upon is v0.2.0-incubating: https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=shortlog;h=refs/tags/v0.2.0-incubating Please also provide the hash for the record; tags are not immutable. The hash is ea2bcbe27f355c3189f0f2207032217b146d3f6d ( https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=commit;h=ea2bcbe27f355c3189f0f2207032217b146d3f6d ) The NOTICE file says: Copyright [2013-2014] The Apache Software Foundation that should really be Copyright 2013-2014 The Apache Software Foundation I don't think that's a blocker but please fix for the next release. The Nexus Staging URL: https://repository.apache.org/content/repositories/orgapachetwill-1001 The jars have NOTICE and LICENSE files under META-INF, which is good. However the names are missing the Apache, for example twill-core-0.2.0-incubating-sources.jar says Twill core library it should be Apache Twill core library SImilarly elsewhere. again please fix for the next release. Will fix in next release. Thanks for point them out. Terence Release artifacts are signed with the following key: https://people.apache.org/keys/committer/chtyim.asc KEYS file available here: https://dist.apache.org/repos/dist/dev/incubator/twill/KEYS For information about the contents of this release see: https://dist.apache.org/repos/dist/dev/incubator/twill/0.2.0-incubating-rc1/CHANGES.txt Please vote on releasing this package as Apache Twill 0.2.0-incubating The vote will be open for 72 hours. [ ] +1 Release this package as Apache Twill 0.2.0-incubating [ ] +0 no opinion [ ] -1 Do not release this package because ... Thanks, The Apache Twill Team - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept DataFu into the Incubator
+1 (binding) -- Andrei Savu On Tue, Dec 31, 2013 at 12:39 PM, Jakob Homan jgho...@gmail.com wrote: Incubator- Following the discussion earlier, I'm calling a vote to accept DataFu as a new Incubator project. The proposal draft is available at: https://wiki.apache.org/incubator/DataFuProposal, and is also included below. Vote is open for at least 96h and closes at the earliest on 4 Jan 13:00 PDT. I'm letting the vote run an extra day as we're in the holiday season. [ ] +1 accept DataFu in the Incubator [ ] +/-0 [ ] -1 because... Here's my binding +1. -Jakob --- Abstract DataFu makes it easier to solve data problems using Hadoop and higher level languages based on it. Proposal DataFu provides a collection of Hadoop MapReduce jobs and functions in higher level languages based on it to perform data analysis. It provides functions for common statistics tasks (e.g. quantiles, sampling), PageRank, stream sessionization, and set and bag operations. DataFu also provides Hadoop jobs for incremental data processing in MapReduce. Background DataFu began two years ago as set of UDFs developed internally at LinkedIn, coming from our desire to solve common problems with reusable components. Recognizing that the community could benefit from such a library, we added documentation, an extensive suite of unit tests, and open sourced the code. Since then there have been steady contributions to DataFu as we encountered common problems not yet solved by it. Others outside LinkedIn have contributed as well. More recently we recognized the challenges with efficient incremental processing of data in Hadoop and have contributed a set of Hadoop MapReduce jobs as a solution. DataFu began as a project at LinkedIn, but it has shown itself to be useful to other organizations and developers as well as they have faced similar problems. We would like to share DataFu with the ASF and begin developing a community of developers and users within Apache. Rationale There is a strong need for well tested libraries that help developers solve common data problems in Hadoop and higher level languages such as Pig, Hive, Crunch, Scalding, etc. Current Status Meritocracy Our intent with this incubator proposal is to start building a diverse developer community around DataFu following the Apache meritocracy model. Since DataFu was initially open sourced in 2011, it has received contributions from both within and outside LinkedIn. We plan to continue support for new contributors and work with those who contribute significantly to the project to make them committers. Community DataFu has been building a community of developers for two years. It began with contributors from LinkedIn and has received contributions from developers at Cloudera since very early on. It has been included included in Cloudera’s Hadoop Distribution and Apache Bigtop. We hope to extend our contributor base significantly and invite all those who are interested in solving large-scale data processing problems to participate. Core Developers DataFu has a strong base of developers at LinkedIn. Matthew Hayes initiated the project in 2011, and aside from continued contributions to DataFu has also contributed the sub-project Hourglass for incremental MapReduce processing. Separate from DataFu he has also open sourced the White Elephant project. Sam Shah contributed a significant portion of the original code and continues to contribute to the project. William Vaughan has been contributing regularly to DataFu for the past two years. Evion Kim has been contributing to DataFu for the past year. Xiangrui Meng recently contributed implementations of scalable sampling algorithms based on research from a paper he published. Chris Lloyd has provided some important bug fixes and unit tests. Mitul Tiwari has also contributed to DataFu. Mathieu Bastian has been developing MapReduce jobs that we hope to include in DataFu. In addition he also leads the open source Gephi project. Alignment The ASF is the natural choice to host the DataFu project as its goal of encouraging community-driven open-source projects fits with our vision for DataFu. Additionally, other projects DataFu integrates with, such as Apache Pig and Apache Hadoop, and in the future Apache Hive and Apache Crunch, are hosted by the ASF and we will benefit and provide benefit by close proximity to them. Known Risks Orphaned Products The core developers have been contributing to DataFu for the past two years. There is very little risk of DataFu being abandoned given its widespread use within LinkedIn. Inexperience with Open Source DataFu was started as an open source project in 2011 and has remained so for two years. Matt initiated the project, and additionally is the creator of the open source White Elephant project. He has also contributed patches to Apache Pig. Most recently he has released
Re: [RESULT][VOTE] Retire the Provisionr podling
I think we are done now. Thanks Tony! I will update the incubator report in a few days. -- Andrei Savu On Sun, Nov 24, 2013 at 11:43 PM, Andrei Savu as...@apache.org wrote: I've update the incubator project status page. All the remaining tasks are listed here: https://issues.apache.org/jira/browse/INFRA-7041 -- Andrei Savu On Fri, Nov 22, 2013 at 10:56 PM, Andrei Savu as...@apache.org wrote: The VOTE passed with 3 +1 binding votes from the following IPMC members: Roman Shaposhnik Tom White Bertrand Delacretaz I will take care of the retirement steps and reply to this email when done: http://incubator.apache.org/guides/retirement.html#steps-to-retirement Thanks, Andrei Savu
Re: [RESULT][VOTE] Retire the Provisionr podling
I've update the incubator project status page. All the remaining tasks are listed here: https://issues.apache.org/jira/browse/INFRA-7041 -- Andrei Savu On Fri, Nov 22, 2013 at 10:56 PM, Andrei Savu as...@apache.org wrote: The VOTE passed with 3 +1 binding votes from the following IPMC members: Roman Shaposhnik Tom White Bertrand Delacretaz I will take care of the retirement steps and reply to this email when done: http://incubator.apache.org/guides/retirement.html#steps-to-retirement Thanks, Andrei Savu
[RESULT][VOTE] Retire the Provisionr podling
The VOTE passed with 3 +1 binding votes from the following IPMC members: Roman Shaposhnik Tom White Bertrand Delacretaz I will take care of the retirement steps and reply to this email when done: http://incubator.apache.org/guides/retirement.html#steps-to-retirement Thanks, Andrei Savu
Re: [VOTE] Retire the Provisionr podling
On Tue, Nov 19, 2013 at 12:43 AM, David Crossley cross...@apache.orgwrote: So far we've got 2 votes from IPMC members (not counting my own): I don't understand why yours would not be counted. And that makes 3. I'm counting my vote as a PPMC member mainly because I've joined the IPMC recently and I'm the project founder. I'm biased. Either way we now have 3 IPMC votes: Bertrand Delacretaz, Roman Shaposhnik, Tom White. I will wait two more days, close the vote and start the procedure. Thanks all for voting!
[VOTE] Retire the Provisionr podling
Hi - We voted [1] to retire the Provisionr podling form the Apache Incubator. Following the retirement guide, it is now time for an IPMC vote to ratify the decision. [ ] +1 Retire the Provisionr podling [ ] +0 Neither here nor there [ ] -1 Do not retire the podling because ... This vote will remain open for at least the next 72 hours. So far we've got 2 votes from IPMC members (not counting my own): * Roman Shaposhnik * Tom White Thanks! [1] http://s.apache.org/xtG [2] http://incubator.apache.org/guides/retirement.html
Re: Shepherding November 2013
Something is fishy. I haven't received any Shepherd assignments ... email for November and I've done no reviews. It's not clear to me how my name got added as a reviewer for Tez. On Mon, Nov 11, 2013 at 3:04 PM, Marvin Humphrey mar...@rectangular.comwrote: Shepherd reviews extracted from https://wiki.apache.org/incubator/November2013: Ambari Roman Shaposhnik (rvs): Project should be pretty close to a well deserved graduation. Kudos to the community building effort! BatchEE Suresh Marru (smarru): The podling is waiting on website setup. The dev mailing list is not yet setup (or atleast not visible in archives), surprisingly the user and commit lists have archives, is something amiss? Blur Suresh Marru (smarru): * The podling seems to be very healthy and kudos to PPMC for pulling of their first release and getting ready for second. * A big kudos to couple of mentors for pro-actively engaging. * Blur website does not conform to the branding guidelines and should add the incubator logo and disclaimer prominently. Also, should include the ASF, security and thanks to sponsor links. Sirona Roman Shaposhnik (rvs): Given that it has been less then a month since project entered incubation I see that the most immediate needs of having a source code repo, JIRA and MLs have been met. Still it would be nice if the bootstrapping were to wrap up as quickly as possible. At this point, for example, there's no website and no wiki, etc. Those are the tools for helping the community growth and it would be very nice to see those coming online in a few weeks. Tez Andrei Savu (asavu): The project is moving very quickly, but needs to make a release soon. Podlings which did not receive shepherd reviews this cycle: Aurora DeviceMap Droids Hadoop Development Tools Knox Open Climate Workbench Ripple Sentry Storm - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherding November 2013
On Mon, Nov 11, 2013 at 7:50 PM, Marvin Humphrey mar...@rectangular.comwrote: The comment was added by Owen O'Malley. I've corrected the report. I'm glad we sorted that out. With regards to Shepherd assignments email, I didn't send one out this month, instead noting in the November 2013 report timeline that the assignments are on the report wiki page. Maybe that explains the low participation. :( Sorry for not helping this month - I've missed the note on the report timeline.
Re: [VOTE] Accept Twill for Incubation
in the External Dependencies section are Apache projects, and Twill will benefit by close proximity to them. = Known Risks = == Orphaned Products == There is very little risk of Twill being orphaned, as it is a key part of Continuuity’s products. The core Twill developers plan to continue to work on Twill, and Continuuity has funding in place to support their efforts going forward. Many other Big Data companies can benefit from Twill, and we have already received interest from various entities that would like to use and contribute to Twill. == Inexperience with Open Source == Several of the core developers have experience with open source development. Terence Yim, Andreas Neumann and Gary Helmling are currently Apache committers for Helix, Oozie and HBase respectively Homogeneous Developers The current core developers are all Continuuity employees. However, we intend to establish a developer community that includes independent and corporate contributors. We are encouraging new contributors via our mailing lists, public presentations, and personal contacts, and we will continue to do so. Various entities have already expressed interest in becoming involved with Twill. == Reliance on Salaried Developers == Currently, these developers are paid to work on Twill. Once the project has built a community, we expect to attract committers, developers and community other than the current core developers. However, because Continuuity products use Twill internally, the reliance on salaried developers is unlikely to change, at least in the near term. == Relationships with Other Apache Products == Twill is deeply integrated with Apache projects. Twill uses Apache YARN as its underlying resource management and task scheduling system and Apache Zookeeper for coordination. In addition, Twill uses Apache HDFS and Apache Kafka. A number of other Apache projects are Twill dependencies and are listed in the External Dependencies section. == An Excessive Fascination with the Apache Brand == While we respect the reputation of the Apache brand and have no doubt that it will attract contributors and users, our interest is primarily to give Twill a solid home as an open source project following an established development model. We have also given additional reasons in the Rationale and Alignment sections. = Documentation = The current documentation for Weave is at https://github.com/continuuity/weave. This will be adapted to the new name Twill. = Initial Source = The Weave codebase is currently hosted at https://github.com/continuuity/weave. Weave will be renamed to Twill to seed the Apache git repository. = External Dependencies = The dependencies all have Apache-compatible licenses: * avro (Apache 2.0) * hadoop (Apache 2.0) * gson (Apache 2.0) * guava-libraries (Apache 2.0) * hbase (Apache 2.0) * hdfs (Apache 2.0) * kafka (Apache 2.0) * netty (Apache 2.0) * snappy-java (Apache 2.0) * yarn (Apache 2.0) * zookeeper (Apache 2.0) * asm (BSD) * junit (EPL v1.0) * logback (EPL v1.0 ) * slf4j (MIT) = Cryptography = Twill will depend on secure Hadoop, which can optionally use Kerberos. = Required Resources = == Mailing Lists == * twill-private for private PMC discussions (with moderated subscriptions) * twill-dev for technical discussions among contributors * twill-commits for notification about commits == Subversion Directory == Git is the preferred source control system: git://git.apache.org/twill == Issue Tracking == JIRA Twill (TWILL) == Other Resources == The existing code already has unit tests, so we would like a Hudson instance to run them whenever a new patch is submitted. This can be added after project creation. = Initial Committers = * Terence Yim * Andreas Neumann * Gary Helmling * Poorna Chandra * Albert Shau = Affiliations = * Terence Yim (Continuuity) * Andreas Neumann (Continuuity) * Gary Helmling (Continuuity) * Poorna Chandra (Continuuity) * Albert Shau (Continuuity) = Sponsors = == Champion == Vinod K vinodkv at apache dot org (Apache Member) == Nominated Mentors == * Arun C Murthy acmurthy at apache dot org * Tom White tomwhite at apache dot org * Patrick Hunt phunt at apache dot org * Andrei Savu asavu at apache dot org == Sponsoring Entity == We are requesting that the Incubator sponsor this project.
Re: [PROPOSAL] Weave for Apache Incubator
IMO it's a good idea to keep this a separate project - the same way we have Curator for ZooKeeper. If you are looking for one more mentor I'm happy to help. -- Andrei Savu On Sun, Nov 3, 2013 at 11:21 PM, Roman Shaposhnik r...@apache.org wrote: Have you guys considered contributing this code directly to Hadoop? From what you are describing it sounds like a developer friendly library wrapped around YARN (along the lines of kitten: https://github.com/jwills/kitten). Thanks, Roman. On Tue, Oct 29, 2013 at 12:53 PM, Andreas Neumann a...@apache.org wrote: I would like to propose Weave, an abstraction over Apache Hadoop® YARN to reduce the complexity of developing distributed applications, as an Apache Incubator podling. The proposal is included in plain text. I would also like to put this on the wiki, but I appear to lack privileges to create pages. What do I need to do to get permission? -Andreas. Abstract Weave is an abstraction over Apache Hadoop® YARN that reduces the complexity of developing distributed applications, allowing developers to focus more on their business logic. Proposal Weave is a set of libraries that reduces the complexity of developing distributed applications. It exposes the distributed capabilities of Apache Hadoop® YARN via a simple and intuitive programming model similar to Java threads. Weave also has built-in capabilities required by many distributed applications, such as real-time application logs and metrics collection, application lifecycle management, and network service discovery. Background == Hadoop YARN is a generic cluster resource manager that supports any type of distributed application. However, YARN’s interfaces are too low level for rapid application development. It requires a great deal of boilerplate code even for a simple application, creating a high ramp up cost that can turn developers away. Weave is designed to improve this situation with a programming model that makes running distributed applications as easy as running Java threads. With the abstraction provided by Weave, applications can be executed in process threads during development and unit testing and then be deployed to a YARN cluster without any modifications. Weave also has built-in support for real-time application logs and metrics collection, delegation token renewal, application lifecycle management, and network service discovery. This greatly reduces the pain that developers face when developing, debugging, deploying and monitoring distributed applications. Weave is not a replacement for YARN, it’s a framework that operates on top of YARN. Rationale = Developers who write YARN applications typically find themselves implementing the same (or similar) boilerplate code over and over again for every application. It makes sense to distill this common code into a reusable set of libraries that is perpetually maintained and improved by a diverse community of developers. Weave’s simple thread-like programming model will enable many Java programmers to develop distributed applications. We believe that this simplicity will attract developers who would otherwise be discouraged by complexity, and many new use cases will emerge for the usage of YARN. Incubating Weave as an Apache project makes sense because Weave is a framework built on top of YARN, and Weave uses Apache Zookeeper, HDFS, Kafka, and other Apache software (see the External Dependencies section). Current Status == Weave was initially developed at Continuuity. The Weave codebase is currently hosted in a public repository at github.com, which will seed the Apache git repository. Meritocracy --- Our intent with this incubator proposal is to start building a diverse developer community around Weave following the Apache meritocracy model. Since Weave was initially developed in early 2013, we have had fast adoption and contributions within Continuuity. We are looking forward to new contributors. We wish to build a community based on Apache's meritocracy principles, working with those who contribute significantly to the project and welcoming them to be committers both during the incubation process and beyond. Community - Weave is currently being used internally at Continuuity and is at the core of our products. We hope to extend our contributor base significantly and we will invite all who are interested in simplifying the development of distributed applications to participate. Core Developers --- Weave is currently being developed by five engineers at Continuuity: Terence Yim, Andreas Neumann, Gary Helmling, Poorna Chandra and Albert Shau. Terence Yim is an Apache committer for Helix, Andreas is an Apache committer and PMC member for Oozie, and Gary
Re: [VOTE] Apache Sirona as an incubated project
+1 -- Andrei Savu (from mobile) On Oct 9, 2013 4:30 AM, Olivier Lamy ol...@apache.org wrote: Hi, Since discussion about the Sirona seems done, I'd like to call a vote for Sirona to become an incubated project. The proposal is pasted below, and also available at: https://wiki.apache.org/incubator/SironaProposal Let's keep this vote open for three business days. [ ] +1 Accept Sirona into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Sirona because... ## page was renamed from MonitoringProposal = Apache Sirona = == Abstract == Apache Sirona aims to provide a simple but extensible monitoring solution for Java applications. Apache Sirona provides two kind of components : * Apache Sirona Core to provide a base framework for monitoring/recording a Java application. * Default based plugins * Apache Sirona base reporting web application (provide a basic reporting on recorded figures). == Background == Currently, Apache Sirona source is hosted in Apache Commons Sandbox scm. The development has begun few years ago but goes to dormant statut. == Rationale == Currently users who need some monitoring need to use some non Open Source solutions or GPL solutions. The goal is to provide a solution based on the Apache License. == Initial Goals == Apache Sirona doesn't have any release currently. The initial goal of this project will be to build community in the spirit of the Apache Way, and to address new features and bug-fixes of the first releases. === Current Status === Intent of the proposal is to build a diverse community of developers around Sirona. Sirona started in the Apache Commons Sandbox, driven in the spirit of open source and we would like to continue in this spirit by, for example, encouraging contributors from a variety of organizations. === Community === Apache Sirona stakeholders desire to expand the user and developer base of Apache Sirona further in the future == Known Risks == === Orphaned Products === Sirona is a new product. So without community adoption the risks of it being orphaned exist. === Inexperience with Open Source === The code has been developed in Apache Commons Sandbox mostly by Romain Manni-Bucau and Olivier Lamy who intimately familiar with the Apache model for open-source development and is experienced with working with new contributors. === Homogeneous Developers === The initial set of committers is from a small set of organizations. However, we expect that once approved for incubation, the project will attract new contributors from diverse organizations and will thus grow organically. The participation of developers from several different organizations in the mailing list is a strong indication for this assertion. === Reliance on Salaried Developers === It is expected that Apache Sirona will be developed on salaried and volunteer time. === Relationships with Other Apache Products === Apache Sirona depends upon other Apache Projects: Velocity and various Apache Commons components and build systems like Maven. === A Fascination with the Apache Brand === The reason for joining Apache is to foster a healthy community of contributors and consumers around the project. This is facilitated by ASF and that is the primary reason we would like Apache Sirona to become an Apache project. == Documentation == Docs: http://commons.apache.org/sandbox/commons-monitoring/ == Initial Source == https://svn.apache.org/repos/asf/commons/sandbox/monitoring/trunk == Source and Intellectual Property Submission Plan == The initial source is already Apache 2.0 licensed. == External Dependencies == The required external dependencies are all Apache License or compatible licenses. Following components with non-Apache licenses are enumerated : == Cryptography == Apache Sirona does not depend upon any cryptography tools or libraries. == Required Resources == === Mailing lists === * sirona-private (with moderated subscriptions) * sirona-dev * sirona-commits * sirona-user == Subversion Directory == https://svn.apache.org/repos/asf/incubator/sirona == Issue Tracking == JIRA Sirona (key: SIRONA) == Other Resources == The existing code already has unit and integration tests so we would like to use Jenkins instance to run them whenever a new patch is submitted. This can be added after project creation. == Initial Committer == * Romain Manni-Bucau (rmannibu...@apache.org) * Jean-Louis Monteiro (jlmonte...@apache.org) * Fred Zhang (no ASF account) * Fabrice Bacchella (no ASF account) * Christian Grobmeier (grobme...@apache.org) == Affiliations == * Olivier Lamy, Ecetera * Fred Zhang, Ecetera == Sponsors == === Champion === * Olivier Lamy (ol...@apache.org) === Nominated Mentors === * Olivier Lamy (ol...@apache.org) * Henri Gomez (hgo...@apache.org) * Jean-Baptiste Onofré (jbono...@apache.org) * Tammo van Lessen (va...@apache.org
Re: [VOTE] Accept Aurora for Apache Incubation
+1 (binding) -- Andrei Savu • linkedin.com/in/sandrei On Thu, Sep 26, 2013 at 7:08 PM, Dave Lester d...@ischool.berkeley.eduwrote: Since discussion about the Aurora proposal has calmed and the team recently published a snapshot of the their source code on github ( https://github.com/twitter/aurora), I'd like to call a vote for Aurora to become an incubated project. The proposal is pasted below, and also available at: https://wiki.apache.org/incubator/AuroraProposal Let's keep this vote open for three business days, closing the voting on Tuesday 10/1. [ ] +1 Accept Aurora into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Aurora because... Dave = Abstract = Aurora is a service scheduler used to schedule jobs onto Apache Mesos. = Proposal = Aurora is a scheduler that provides all of the primitives necessary to quickly deploy and scale stateless and fault tolerant services in a datacenter. Aurora builds on top of Apache Mesos and provides common features that allow any site to run large scale production applications. While the project is currently used in production at Twitter, we wish to develop a community to increase contributions and see it thrive in the future. = Background = The initial development of Aurora was done at Twitter, and its codebase was recently open sourced. This proposal is for Aurora to join the Apache Incubator. = Rationale = While the Apache Mesos core focuses on distributing individual tasks across nodes in a cluster, typical services consist of dozens or hundreds of replicas of tasks. As a service scheduler, Aurora provides the abstraction of a job to bundle and manage these tasks. Aurora provides many key functionalities centered around a job, including: definition, the concept of an instance and the serverset, deployment and scheduling, health checking, and introspection. It also allows cross-cutting concerns to be handled like observability and log collection. = Current Status = == Meritocracy == By submitting this incubator proposal, we’re expressing our intent to build a diverse developer community around Aurora that will conduct itself according to The Apache Way and use meritocratic means of accepting contributions. Several members of the Aurora team overlap with Apache Mesos, which successfully graduated from the Incubator and has embraced a meritocratic model of governance; we plan to follow a similar path forward with Aurora and believe that a synergy between both projects will make this even easier. == Community == Aurora is currently being used internally at Twitter. By open sourcing the project, we hope to extend our contributor base significantly and create a vibrant community around the project. == Core Developers == Aurora is currently being developed by a team of seven engineers at Twitter. == Alignment == The ASF is a natural choice to host the Aurora project, given the goal of open sourcing the project and fostering a community to grow and support the software. Additionally, Aurora integrates with Apache Mesos, and Apache ZooKeeper for service discovery. We believe that inclusion within Apache will build stronger ties between these projects, and create further alignment between their goals and communities. = Known Risks = == Orphaned Products == The core developers plan to continue working full time on the project, and there is very little risk of Aurora being abandoned since it is running hundreds of services as part of Twitter’s infrastructure. Additionally, members of the Mesos community beyond Twitter have expressed interest in an advanced scheduler like Aurora (see “Interested Parties” section); we believe that need will drive some of the community involvement necessary for the project to incubate successfully. == Inexperience with Open Source == Initial Aurora committers have varying levels of experience using and contributing to Open Source projects, however by working with our mentors and the Apache community we believe we will be able to conduct ourselves in accordance with Apache Incubator guidelines. The close relationship between the Aurora team and Apache Mesos means there is an awareness of the incubation process and a willingness to embrace The Apache Way. == Homogenous Developers == The initial set of committers are from a single organization, however we expect that once approved for incubation the project will attract contributors from more organizations. We have already had conversations with other companies who have expressed an interest in Aurora. == Reliance on Salaried Developers == Initial Aurora committers are salaried developers at Twitter, however shortly after open sourcing the code we plan to diversify the project’s core committers and contributors. == Relationships with Other Apache Products == Initially, Aurora has been developed as a scheduler for Apache Mesos. Additionally, it relies on ZooKeeper
Re: [VOTE]: Release Apache Sentry 1.2.0 incubating (rc0)
+1 (binding) -- Andrei Savu On Sun, Sep 22, 2013 at 8:02 AM, Shreepadma Venugopalan shreepa...@apache.org wrote: This is the first incubator release of Apache Sentry, version 1.2.0-incubating. It fixes the following issues: http://s.apache.org/VlU Source files : http://people.apache.org/~shreepadma/sentry-1.2.0/ Tag to be voted on (rc0): https://git-wip-us.apache.org/repos/asf/incubator-sentry/repo?p=incubator-sentry.git;a=log;h=refs/tags/release-1.2.0-rc0 Sentry's KEYS containing the PGP key we used to sign the release: https://people.apache.org/keys/group/sentry.asc Note that this is a source only release and we are voting on the source (tag). A vote on releasing this package has already passed in Apache Sentry PPMC[1] including +1 votes from our IPMC mentors (Patrick Hunt and Arvind Prabhakar). Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Shreepadma [1] - http://markmail.org/search/?q=sentry%20vote%20release#query:sentry%20vote%20release+page:1+mid:sqrwevgsxakqatqk+state:results
Re: [VOTE] first release of Apache Blur (incubating)
+1 (binding) Nice work guys! -- Andrei Savu On Tue, Sep 24, 2013 at 3:50 AM, Aaron McCurry amccu...@gmail.com wrote: We've held a vote on blur-dev to release the first incubating release. The vote thread can be found here: http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201309.mbox/%3CCAB6tTr0cG%3D78nBuQHBqzKLyn4T8-4gHnmD8%2Bo8voP79qmVz2fw%40mail.gmail.com%3E The vote passed with 3 x +1 binding votes 3 x +1 non-binding votes A summary email can be found here: http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201309.mbox/%3CCAB6tTr39cN8nMQ7zmX6s9yjqk5iLS6NO4g_1_G6aiOMQu%2Bv_Hw%40mail.gmail.com%3E The source and binary release artifacts can be found together with signatures here: https://dist.apache.org/repos/dist/dev/incubator/blur/0.2.0-incubating/ Please vote on this release
Re: Shepherding September 2013
On Sun, Sep 15, 2013 at 7:34 AM, Marvin Humphrey mar...@rectangular.comwrote: Shepherd participation was light this month; a few stalwarts seem to have quietly fallen away. Thanks to them for their past efforts... If there are volunteers out there interested in shepherding, please speak up -- we have slots. (Sheperding can be as minimal as scanning the mailing list archives to ensure that a podling's Mentors have been engaged over the last quarter, or it can involve observations and opinions as per the style of most present shepherds.) I'm also available to help. I can review 1-2 projects per month. Regards, -- Andrei Savu
Re: [VOTE]: Release Apache Sentry 1.2.0 incubating (rc0)
On Thu, Sep 19, 2013 at 4:31 AM, Shreepadma Venugopalan shreepa...@apache.org wrote: Sentry's KEYS containing the PGP key we used to sign the release: https://people.apache.org/keys/group/sentry.asc Adding sebb's comment regarding KEYS file from the Spark vote thread. There is a longer thread on general@incubator explaining why this location is preferred. - The KEYS file should normally be under: http://www.apache.org/dist/incubator/sentry/ as this is where the release artifacts will be found if the vote succeeds. Also that location is automatically archived, It's important that the KEYS file contains all keys used to sign any releases, so keys should only be added to it, never removed (except possibly if the key has been compromised). So please add your key to the KEYS file at that location (creating it if necessary). - -- Andrei Savu
Re: [VOTE]: Release Apache Sentry 1.2.0 incubating (rc0)
I've been able to build and test the project using the instruction from README.md. It would be useful to have a basic website or some instructions on the wiki on how to deploy Sentry. I see that sentry-binding-hive still use org.apache.access as package name (HiveAuthzBindingSessionHook.java). Is this intended? Everything else looks good to me: GPG signature, hashes, DISCLAIMER NOTICE files, license headers. Are there any plans to provide binaries for convenience or to push the jar files to repository.apache.org / Maven Central? -- Andrei Savu On Thu, Sep 19, 2013 at 4:31 AM, Shreepadma Venugopalan shreepa...@apache.org wrote: This vote is being concurrently called on dev@sentry.incubator.apache.organd general@incubator.apache.org. This is the first incubator release of Apache Sentry, version 1.2.0-incubating. It fixes the following issues: goo.gl/Bx5D1x Source files : http://people.apache.org/~shreepadma/sentry-1.2.0/ Tag to be voted on (rc0): https://git-wip-us.apache.org/repos/asf/incubator-sentry/repo?p=incubator-sentry.git;a=log;h=refs/tags/release-1.2.0-rc0 Sentry's KEYS containing the PGP key we used to sign the release: https://people.apache.org/keys/group/sentry.asc Note that this is a source only release and we are voting on the source (tag). Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks. Shreepadma
Re: [ANNOUNCE] Andrei Savu joins the IPMC
Thanks! I'm looking forward to help as needed. Cheers, -- Andrei Savu / axemblr.com On Wed, Sep 11, 2013 at 5:24 AM, Chris Mattmann mattm...@apache.org wrote: Welcome, Andrei! -Original Message- From: Marvin Humphrey mar...@rectangular.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Tuesday, September 10, 2013 9:17 PM To: general@incubator.apache.org general@incubator.apache.org Subject: [ANNOUNCE] Andrei Savu joins the IPMC Greets, The Incubator PMC has VOTEd to add new member Andrei Savu. Welcome, Andrei! Marvin Humphrey, on behalf of the Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE]: Accept Sentry in Apache Incubator
+1 (non-binding) -- Andrei Savu On Mon, Aug 5, 2013 at 4:23 PM, Shreepadma Venugopalan shreepa...@cloudera.com wrote: Following the discussions last week, I'm calling a vote to accept Sentry as a new project in the Apache Incubator. The proposal draft is available at: https://wiki.apache.org/incubator/SentryProposal and is also pasted to the bottom of this email. It is identical to what was proposed except for a) addition of two new mentors, and b) removal of the user list for now, per Marvin's suggestion. The proposal thread is available at: http://goo.gl/bvvJPh [ ] +1 Accept Sentry in the Incubator [ ] +/-0 Don't care [ ] -1 Don't accept Sentry in the Incubator because... Thanks. Shreepadma = Sentry - A fine-grained Authorization System for the Hadoop ecosystem = == Abstract == Sentry is a highly modular system for providing fine grained role based authorization to both data and metadata stored on an Apache Hadoop cluster. Sentry can be used to enforce various access policy rules when accessing data stored on Hadoop Distributed File System through various Hadoop ecosystem components such as Apache Hive, Apache Pig or others. == Proposal == Traditionally, user access control in Apache Hadoop has been implemented using file based permissions on HDFS. Following the UNIX permissions model, HDFS offers all or nothing semantics allowing administrator to configure system to allow certain users or user groups read, write or perform both operations on files. This system does not enable more fine grained permissions that allow access policies for logical parts within one file. Furthermore, this model can't be used to restrict access to the rich set of objects in the metadata catalog that are stored outside HDFS. Sentry will provide true role-based fine-grained user access control for Apache Hadoop and its ecosystem components such as Hive, Pig or HBase. This includes providing fine- grained role based access to both data as well as the metadata, which provides a rich object based abstraction such as databases, tables or columns. == Background == Sentry was initially developed by Cloudera to allow users fine grained access to data as well as the metadata in Apache Hadoop. Sentry has been maintained as an open source project on Cloudera’s github. Sentry was previously called “Access”. All code in Sentry is open source and has been made publicly available under the Apache 2 license. During this time, Sentry has been formally released two times as versions 1.0.0 and 1.1.0. == Rationale == Currently, users don't have a way to achieve fine grained enforceable user access control to data stored in HDFS and their associated metadata. While users can use file based permissions to control access to specific directories and files, it is insufficient because access can't be restricted to file parts i.e., to specific lines or logical columns. In the absence of such support, users have to resort to duplicating data. Furthermore, file based permissions are insufficient to provide any form of access control to the metadata that provides an object abstraction such as databases, tables, columns or partitions over the data stored in HDFS. Current Sentry developers subscribe to the mission of ASF and are familiar with the open source development process. Several members are already committers and PMC members of various other Apache projects. == Initial Goals == Sentry is currently in its first major release with a considerable number of enhancement requests, tasks, and issues recorded towards its future development. The initial goal of this project will be to continue to build community in the spirit of the Apache Way, and to address the highly requested features and bug-fixes towards the next dot release. == Current Status == === Meritocracy === Intent of the proposal is to build a diverse community of developers around Sentry. Sentry started as a open source project on Github, driven in the spirit of open source and we would like to continue in this spirit by, for example, encouraging contributors from a variety of organizations. === Community === Sentry stakeholders desire to expand the user and developer base of Sentry further in the future. The current sets of developers in Sentry are committed to building a strong user base and open source community around the project. Development discussions within the current team have been on a public mailing [[ https://groups.google.com/a/cloudera.org/forum/#!forum/access-dev | list]]. === Core Developers === The core developers for the Sentry project are Brock Noland, Shreepadma Venugopalan, Prasad Mujumdar and Jarek Jarcec Cecho. Other contributors include Arvind Prabhakar and Xuefu Zhang. All engineers have deep expertise in Hadoop and various other ecosystem components. === Alignment === Sentry complements the access control feature of some projects in the Apache Hadoop
[RESULT][VOTE] Release Apache Provisionr version 0.4.0-incubating
The vote to release Apache Provisionr 0.4.0-incubating has passed with 3 IPMC +1s and 4 non-binding +1s IPMC Binding Votes: Tom White Joe Brockmeier Roman Shaposhnik Non-Binding Votes: Rahul Sharma Alex Ciminian Andrei Savu Ioan Eugen Stan Thanks all! -- Andrei Savu -- Forwarded message -- From: Andrei Savu as...@apache.org Date: Thu, Jun 27, 2013 at 11:33 AM Subject: [VOTE] Release Apache Provisionr version 0.4.0-incubating, RC0 To: general@incubator.apache.org Cc: dev d...@provisionr.incubator.apache.org This is the first release candidate for Apache Provisionr, version 0.4.0-incubating. The PPMC vote thread: http://mail-archives.apache.org/mod_mbox/incubator-provisionr-dev/201306.mbox/%3CCAHZL8y-PzC6AVavK-cs5d8Sv%2BV2bfq0REHPjAaWn1Fs-y3PSqQ%40mail.gmail.com%3E It fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314423version=12324250 *** Please download, test and vote by July 2, 2013. Note that we are voting upon the source (tag), binaries are provided for convenience. Source and binary files: http://people.apache.org/~asavu/provisionr-0.4.0-incubating-candidate-0/ Maven staging repo: https://repository.apache.org/content/repositories/orgapacheprovisionr-035/ The tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=incubator-provisionr.git;a=tag;h=62abf302b47460abff904e2e721606255561757d Provisionr's KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/provisionr/KEYS Check the following email to understand how this releases candidate was created and tested so far (we are still lacking documentation): http://mail-archives.apache.org/mod_mbox/incubator-provisionr-dev/201306.mbox/%3CCAHZL8y8dHL%3DU2kFVGySX2aNuF%3DRhNg9n4%2Bcpd1yktvacCZwbPA%40mail.gmail.com%3E [ ] +1 [ ] 0 [ ] -1 (explain why) Thanks!
Re: [VOTE] Release Apache Provisionr version 0.4.0-incubating, RC0
Thanks Roman! Good catch finding the missing .gitignore - I've create a JIRA issue: https://issues.apache.org/jira/browse/PROVISIONR-42 We can address the WOT thing next time we meet face to face. Cheers, -- Andrei Savu / axemblr.com On Mon, Jul 1, 2013 at 8:29 PM, Roman Shaposhnik r...@apache.org wrote: +1 (binding). That said, here's a couple of nits I *really* would like you guys to address for the next release: On Thu, Jun 27, 2013 at 1:33 AM, Andrei Savu as...@apache.org wrote: Source and binary files: http://people.apache.org/~asavu/provisionr-0.4.0-incubating-candidate-0/ The tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=incubator-provisionr.git;a=tag;h=62abf302b47460abff904e2e721606255561757d The tag and the published tarballs differ in one file: .gitignore Provisionr's KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/provisionr/KEYS It really would be quite nice if the key for release came with at least some level of WOT. Thanks, Roman.
Re: [VOTE] Release Apache Provisionr version 0.4.0-incubating, RC0
Thanks Joe for explaining the process! I will remember that for the next release. We now have 2 binding votes from the IPMC. Only one more is needed. Regards, -- Andrei Savu On Sat, Jun 29, 2013 at 12:13 AM, Joe Brockmeier j...@zonker.net wrote: On Thu, Jun 27, 2013, at 04:10 PM, Andrei Savu wrote: On Thu, Jun 27, 2013 at 7:59 PM, Dave Fisher dave2w...@comcast.net wrote: This link doesn't help determine who has voted from the PPMC nor does it provide a count of how many votes and by whom. Have you had any IPMC/binding votes? My bad. I was a bit lazy. We had 3 +1's from the PPMC and one +1 from Rahul Sharma (as contributor). No binding votes on the project mailing list. Generally, it's best practice to: 1) Supply a list of binding votes from your PPMC in the summary email to this list, like so: http://markmail.org/thread/wu4lpcdk6uk6lben 2) Supply a link to your [RESULT][VOTE] message that summarizes the vote, at the tail end of the VOTE thread. See, for example: http://markmail.org/message/dg6mquboi65t2nho Having to go through the list + comb through the names match them with PPMC is time-consuming. I looked it over, built it, etc. Looks good to me. +1 (binding) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache Provisionr version 0.4.0-incubating, RC0
This is the first release candidate for Apache Provisionr, version 0.4.0-incubating. The PPMC vote thread: http://mail-archives.apache.org/mod_mbox/incubator-provisionr-dev/201306.mbox/%3CCAHZL8y-PzC6AVavK-cs5d8Sv%2BV2bfq0REHPjAaWn1Fs-y3PSqQ%40mail.gmail.com%3E It fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314423version=12324250 *** Please download, test and vote by July 2, 2013. Note that we are voting upon the source (tag), binaries are provided for convenience. Source and binary files: http://people.apache.org/~asavu/provisionr-0.4.0-incubating-candidate-0/ Maven staging repo: https://repository.apache.org/content/repositories/orgapacheprovisionr-035/ The tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=incubator-provisionr.git;a=tag;h=62abf302b47460abff904e2e721606255561757d Provisionr's KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/provisionr/KEYS Check the following email to understand how this releases candidate was created and tested so far (we are still lacking documentation): http://mail-archives.apache.org/mod_mbox/incubator-provisionr-dev/201306.mbox/%3CCAHZL8y8dHL%3DU2kFVGySX2aNuF%3DRhNg9n4%2Bcpd1yktvacCZwbPA%40mail.gmail.com%3E [ ] +1 [ ] 0 [ ] -1 (explain why) Thanks!
Re: [VOTE] Release Apache Provisionr version 0.4.0-incubating, RC0
On Thu, Jun 27, 2013 at 7:59 PM, Dave Fisher dave2w...@comcast.net wrote: This link doesn't help determine who has voted from the PPMC nor does it provide a count of how many votes and by whom. Have you had any IPMC/binding votes? My bad. I was a bit lazy. We had 3 +1's from the PPMC and one +1 from Rahul Sharma (as contributor). No binding votes on the project mailing list. -- Andrei Savu
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (non-binding) -- Andrei Savu On Tue, Apr 23, 2013 at 9:40 AM, Tomaz Muraus to...@apache.org wrote: +1 (binding) On Apr 22, 2013 3:39 PM, Rebecca Wood silky...@gmail.com wrote: Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... The full proposal is pasted below, and the corresponding wiki is http://wiki.apache.org/incubator/jcloudsProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Becca Wood -- = jclouds Proposal for Apache Incubator = == Abstract == [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Proposal == [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions for cloud computing and cloud storage in the form of Java or Clojure libraries. By abstracting away vendor-specific details, jclouds supplies a solution for users to avoid lock-in to a specific cloud vendor. It also provisions hooks to make it easy to take advantage of specific features from those vendors. == Background == jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 plugin for Infinispan. He discovered that existing S3 libraries would not pass the concurrent test suite needed for write behind persistence. When it became clear that a new library was needed, jclouds formed as an independent project founded by Cole under the mentorship of Manik Surtani. The fledgling jclouds team soon encountered two portability issues: runtime portability with Google App Engine and compatibility with the similar cloud files service from Rackspace. The legacy of Google App Engine is still present within jclouds and is expressed by the 'driver' design which doesn't require threads. Supporting Rackspace started a legacy of cloud portability which would soon extend to provisioning. As jclouds supports newer and cutting edge cloud technologies, it is in a constant state of evolution. jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking between European Java User Groups accounts for the initial population of European developers and users within the community. The initial contributors to jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there were a number of other advisers as well. == Rationale == There are many providers that offer IaaS clouds, but few APIs that can bridge the gap between cloud providers. jclouds supplies an abstraction layer for both compute and storage resources that makes it easy to work with many different cloud APIs using a simple and singular API. jclouds provides this abstraction layer for the Java and Clojure communities. It is a unique niche within the cloud community. jclouds provides the write once, run anywhere concept when utilizing infrastructure cloud resources. == Initial Goals == * Build a more centralized community pulling together jclouds developers, jclouds integrators, and service providers who use jclouds. * Although jclouds has a fairly collaborative community, the committers wish to further bridge the gap between developers and community by encouraging more community involvement in development processes. * Break down from a monolithic release process into one that is more decentrilized. * Bring the jclouds core code base consisting of ComputeService and Blobstore into Apache. * jclouds will not move all existing provider code into Apache. The goal is to move the provider code for those clouds that have complete portability and are tried, tested, and true. This includes code for OpenStack, Amazon EC2, and Google Cloud. == Current Status == === Meritocracy === jclouds has an active community of contributors who are encouraged to become full-fledged jclouds committers. A jclouds committer understands the importance of seeking community feedback, actively listening to suggestions, and fostering relationships with community members who make contributions. The entirety of jclouds is built upon the relationships that have been built with community members. This camaraderie will continue to be promoted as jclouds is introduced into the Incubator and beyond. jclouds encourages involvement from its community members, and the issues are open and available to any developers who wish to contribute to the project. The jclouds team currently seeks help and asks for suggestions utilizing the jclouds and jclouds-dev Google groups and IRC on irc.freenode.net#jclouds
Re: Creating announce@ lists by default
I think we should see this as option and let the podling decide. In some cases it's useful but most of time it's enough if you filter the dev / user lists for messages that contain ANNOUNCE in the subject line. -- Andrei Savu / axemblr.com On Tue, Mar 26, 2013 at 7:50 PM, Noah Slater nsla...@apache.org wrote: Why would you want to subscribe to the announce list of every new incubator project? If you wanted to do that, you'd just subscribe to general@incubator.apache.org, or even annou...@apache.org. Please note, I am not suggesting we disband annou...@apache.org. We already have plenty of TLPs using annou...@tlp.apache.org lists, and they post to that as well as annou...@apache.org. All I am suggesting is that we suggest to incubating projects that they create an project specific announce@ list, so as to create a low-volume, high-signal news channel. It is my experience that such things are useful. On 26 March 2013 17:44, Luciano Resende luckbr1...@gmail.com wrote: On Tue, Mar 26, 2013 at 10:38 AM, Noah Slater nsla...@apache.org wrote: Yep. Obviously, I'm aware we have a foundation-wide announce list. :) It's not very helpful for people who are only interested in one or two projects, however. If I am using Hadoop, and only care about knowing about new Hadoop releases or security disclosures, I do not want to: a) subscribe to annou...@apache.org, and receive loads of completely irrelevant junk, or b) subscribe to u...@hadoop.apache.org, and receive even more irrelevant junk Having a high-signal, low-volume announcements list would be beneficial for most projects, IMO. And it seems like the sort of thing we should be encouraging right from the start. I think Hadoop would be the best example in ASF, if you really using Hadoop, you are probably using Haddop, HDFS, HBase, Oozie, and so on... the whole Hadoop Ecosystem projects... and imagine if you have to subscribe to all of those and to every new related incubator project that comes every month ? BTW, the traffic on this list is not really unmanageable and will definitely not make you consider that this new list is flooding your inbox. -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- NS
[jira] [Created] (PODLINGNAMESEARCH-29) Establish whether Apache Provisionr is a suitable name
Andrei Savu created PODLINGNAMESEARCH-29: Summary: Establish whether Apache Provisionr is a suitable name Key: PODLINGNAMESEARCH-29 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-29 Project: Podling Suitable Names Search Issue Type: Suitable Name Search Reporter: Andrei Savu Provisionr was formed by dropping the last e from provisioner - similar to Apache Buildr. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - 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 non-binding -- Andrei Savu On Fri, Mar 15, 2013 at 8:15 AM, Ioan Eugen Stan stan.ieu...@gmail.comwrote: +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: [PROPOSAL] Provisionr join the Apache Incubator
On Fri, Mar 8, 2013 at 2:20 AM, Andrew Bayer andrew.ba...@gmail.com wrote: A little belated, but I'd be interested in helping out as well. You are welcome! :) -- Andrei Savu
Re: [VOTE] Accept Provisionr into the Apache Incubator
Thanks to all who voted! With 18 +1s (10 binding) the vote passes. I'll start the work to get the podling started. Thanks, Andrei On Mon, Mar 4, 2013 at 9:31 PM, Henry Saputra henry.sapu...@gmail.comwrote: +1 non-binding Good luck On Sat, Mar 2, 2013 at 3:35 PM, Andrei Savu as...@apache.org wrote: Hi Guys, I'd like to call a VOTE for acceptance of Provisionr into the Apache Incubator. The vote will close on March 8. [] +1 Accept Provisionr into the Apache incubator [] +0 Don't care. [] -1 Don't accept Provisionr into the incubator because... Full proposal is pasted at the bottom on this email, and the corresponding wiki is http://wiki.apache.org/incubator/ProvisionrProposal Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Andrei Savu -- Provisionr Proposal == Abstract == Provisionr is an effort to develop a service that can be used to create and manage pools of virtual machines on multiple clouds. Our focus is on semi-automated workflows and cloud portability. == Proposal == Provisionr solves the problem of cloud portability by hiding completely the APIs and only focusing on building a cluster that matches the same set of assumptions on all clouds, assumptions like: running a specific operating system (e.g. Ubuntu 12.04 LTS), having the same set of pre-installed packages and binaries, sane dns settings (forward reverse ip resolution - as needed for Hadoop), ntp settings, networking settings, firewall, ssh admin access, vpn access etc. As a secondary goal Provisionr should also provide primitives for building automatic or semi-automatic workflows for configuring services, workflows that assume that all the machines share a common set of characteristics as described above. == Background == Creating clusters on cloud infrastructure is non-trivial because careful orchestration is required. To make it easy to deploy services we need to start from a foundation that matches a common set of assumptions on multiple providers. == Rationale == This project started as a re-write of the core of Apache Whirr but has a different target being more focused on semi-automated workflows and cloud portability. == Initial Goals == * Build a community * Provide an excellent user experience for semi-automatic workflows (e.g. using Rundeck) * Implement a REST service and a Web Console * Add support for more providers == Current Status == Provisionr had four releases on [[ https://github.com/axemblr/axemblr-provisionr/wiki|GitHub]] and it's used to deploy Hadoop clusters on-demand at Axemblr and infrastructure for testing / QA. === Meritocracy === We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. === Community === The community interested in cloud service infrastructure is currently spread across many smaller projects, and one of the main goals of this project is to build a vibrant community to share best practices and build common infrastructure. === Core developers === Core developers are very experienced in the Apache ecosystem. To achieve more diversity of developers, we will be eager to recruit developers from diverse companies. * Andrei Savu - asavu at apache dot org (Apache Whirr PMC) * Ioan Eugen Stan - ieugen at apache dot org (Apache James PMC) * Alex Ciminian - alex.ciminian at gmail dot org === Alignment === Provisionr complements Apache Whirr and later on it should provide a robust foundation for more advanced functionalities. == Known Risks == === Orphaned products === The contributors have significant open source experience and the project is being used as part of a commercial product, so the risk of being orphaned is relatively low. We plan to mitigate this risk by recruiting additional committers. === Inexperience with Open Source === Most of the initial committers have experience working on open source projects. Andrei Savu and Ioan Eugen Stan have experience as committers and PMC members on other Apache projects. === Homogenous Developers === We are committed to recruiting additional committers from other companies based on their contributions to the project. === Reliance on Salaried Developers === It is expected that Provisionr development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by their employer to contribute to this project. However, they are all passionate about the project, and we are confident
Re: [PROPOSAL] Provisionr join the Apache Incubator
I think the proposal is now ready for voting. I will go ahead and start a new thread. http://wiki.apache.org/incubator/ProvisionrProposal Thank you all! -- Andrei Savu On Fri, Mar 1, 2013 at 6:57 PM, Andrei Savu savu.and...@gmail.com wrote: On Fri, Mar 1, 2013 at 10:45 AM, Eric Sammer esam...@cloudera.com wrote: I'd love to be involved if you're actively looking for initial committers. I'm very familiar with OSGi, puppet, and the Hadoop ecosystem side of things. I'm (non-binding) +1 on accepting the project to the incubator. Thanks Eric and welcome to the team. -- Andrei Savu
[VOTE] Accept Provisionr into the Apache Incubator
Hi Guys, I'd like to call a VOTE for acceptance of Provisionr into the Apache Incubator. The vote will close on March 8. [] +1 Accept Provisionr into the Apache incubator [] +0 Don't care. [] -1 Don't accept Provisionr into the incubator because... Full proposal is pasted at the bottom on this email, and the corresponding wiki is http://wiki.apache.org/incubator/ProvisionrProposal Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Andrei Savu -- Provisionr Proposal == Abstract == Provisionr is an effort to develop a service that can be used to create and manage pools of virtual machines on multiple clouds. Our focus is on semi-automated workflows and cloud portability. == Proposal == Provisionr solves the problem of cloud portability by hiding completely the APIs and only focusing on building a cluster that matches the same set of assumptions on all clouds, assumptions like: running a specific operating system (e.g. Ubuntu 12.04 LTS), having the same set of pre-installed packages and binaries, sane dns settings (forward reverse ip resolution - as needed for Hadoop), ntp settings, networking settings, firewall, ssh admin access, vpn access etc. As a secondary goal Provisionr should also provide primitives for building automatic or semi-automatic workflows for configuring services, workflows that assume that all the machines share a common set of characteristics as described above. == Background == Creating clusters on cloud infrastructure is non-trivial because careful orchestration is required. To make it easy to deploy services we need to start from a foundation that matches a common set of assumptions on multiple providers. == Rationale == This project started as a re-write of the core of Apache Whirr but has a different target being more focused on semi-automated workflows and cloud portability. == Initial Goals == * Build a community * Provide an excellent user experience for semi-automatic workflows (e.g. using Rundeck) * Implement a REST service and a Web Console * Add support for more providers == Current Status == Provisionr had four releases on [[ https://github.com/axemblr/axemblr-provisionr/wiki|GitHub]] and it's used to deploy Hadoop clusters on-demand at Axemblr and infrastructure for testing / QA. === Meritocracy === We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. === Community === The community interested in cloud service infrastructure is currently spread across many smaller projects, and one of the main goals of this project is to build a vibrant community to share best practices and build common infrastructure. === Core developers === Core developers are very experienced in the Apache ecosystem. To achieve more diversity of developers, we will be eager to recruit developers from diverse companies. * Andrei Savu - asavu at apache dot org (Apache Whirr PMC) * Ioan Eugen Stan - ieugen at apache dot org (Apache James PMC) * Alex Ciminian - alex.ciminian at gmail dot org === Alignment === Provisionr complements Apache Whirr and later on it should provide a robust foundation for more advanced functionalities. == Known Risks == === Orphaned products === The contributors have significant open source experience and the project is being used as part of a commercial product, so the risk of being orphaned is relatively low. We plan to mitigate this risk by recruiting additional committers. === Inexperience with Open Source === Most of the initial committers have experience working on open source projects. Andrei Savu and Ioan Eugen Stan have experience as committers and PMC members on other Apache projects. === Homogenous Developers === We are committed to recruiting additional committers from other companies based on their contributions to the project. === Reliance on Salaried Developers === It is expected that Provisionr development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by their employer to contribute to this project. However, they are all passionate about the project, and we are confident that the project will continue even if no salaried developers contribute to the project. We are committed to recruiting additional committers including non-salaried developers. === Relationships with Other Apache Products === Provisionr is closely integrated with CloudStack, Karaf, CXF, BigTop in a numerous ways. We look forward to collaborating with those communities, as well as other Apache communities (like Apache Helix). === A Excessive Fascination with the Apache Brand === We think that Provisionr will benefit from the community
Re: [PROPOSAL] Provisionr join the Apache Incubator
On Fri, Mar 1, 2013 at 12:59 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: I would like to help and hence added myself as a mentor. Thanks for bringing the project to Apache. Thanks for joining! Your help is highly appreciated. -- Andrei Savu
Re: [PROPOSAL] Provisionr join the Apache Incubator
Thanks Steve! On Fri, Mar 1, 2013 at 3:43 AM, Steve Loughran steve.lough...@gmail.comwrote: One thing I would recommend for the curious is to get a demo of it from Andrei; I saw one over G+ and it looked very nice. Anyone should feel free to email me if they want a live demo. -- Andrei Savu
Re: [PROPOSAL] Provisionr join the Apache Incubator
On Fri, Mar 1, 2013 at 10:45 AM, Eric Sammer esam...@cloudera.com wrote: I'd love to be involved if you're actively looking for initial committers. I'm very familiar with OSGi, puppet, and the Hadoop ecosystem side of things. I'm (non-binding) +1 on accepting the project to the incubator. Thanks Eric and welcome to the team. -- Andrei Savu
Re: [PROPOSAL] Provisionr join the Apache Incubator
Anyone else interested to join? We are still looking for mentors / initial contributor. If you are working with OSGi, Karaf, Activiti, Cloud APIs or Puppet it would be great to have you on-board as a mentor or contributor. I am at ApacheCon in Portland - feel free to get in touch if you want to know more. -- Andrei Savu On Wed, Feb 27, 2013 at 10:56 AM, Andrei Savu savu.and...@gmail.com wrote: I think the following presentation does a better job at explaining the scope of Provisionr: http://www.slideshare.net/savu.andrei/creating-pools-of-virtual-machines-apachecon-na-2013 Regards, -- Andrei Savu On Wed, Feb 27, 2013 at 7:53 AM, Benson Margulies bimargul...@gmail.comwrote: On Wed, Feb 27, 2013 at 2:28 AM, Tom White tom.e.wh...@gmail.com wrote: On Tue, Feb 26, 2013 at 6:34 AM, Andrei Savu savu.and...@gmail.com wrote: Tom do you want to be a champion for this proposal? Yes, I'd be happy to. One thing I think is worth discussing more here is whether Provisionr should be a TLP on graduation, or whether it should be a module in Whirr. Well, that puts this proposal into a gray area. In case you haven't been reading all the traffic on this list, I'll give a quick summary here. Historically, the Foundation had 'subprojects', and the the incubator hosted podlings intended, eventually, to become subprojects of existing TLPs. We don't do that anymore. If Provisionr becomes part of Whir, it just becomes, well, part of Whir. That raises the question of what you need the incubator for if this is your goal. There's a pretty simple alternative. The existing Provisionr team works with Whir to do an IP grant of the code to the Foundation. The existing team submits ICLAs. Whir makes a branch or other distinctive tree in source control and grants the Provisionr team commit access _to that tree_. Over time, the Provisionr people earn full committer status by merit, and appropriate adjustments are made to the tree structure. Given the state of the conversation about policy on this subject, I think it would be reasonable to ask you all to talk to the Whir people about this, and see if you an all come to an agreement for something like this in parallel with a discussion here. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Provisionr join the Apache Incubator
Hi David - On Thu, Feb 28, 2013 at 11:19 AM, David Nalley da...@gnsa.us wrote: I am interested in this. I know one or two things about puppet and cloud APIs. Not sure how many cycles I can expend. It would be great to have you part of the team. Feel free to edit the wiki. CloudStack support is very important for me and I'm going to spend a fair amount of time on that over the next cloud of weeks / months. -- Andrei Savu
Re: [PROPOSAL] Provisionr join the Apache Incubator
Thanks Tom! On Wed, Feb 27, 2013 at 2:28 AM, Tom White tom.e.wh...@gmail.com wrote: BTW Andrei, please put the proposal on the Incubator wiki so others can edit it, and so it's easy to find in the future. I have updated the proposal and posted it on the Incubator wiki: http://wiki.apache.org/incubator/ProvisionrProposal -- Andrei Savu
Re: [PROPOSAL] Provisionr join the Apache Incubator
Hi Benson - Thanks for your feedback! It's too early to decide if there is an overlap between communities. Provisionr solves a different problem being focused on semi-automated workflows (e.g. with Rundeck) and cloud portability while Whirr is more focused on deploying services from the Hadoop stack. I had this conversation before with Tom. -- Andrei Savu On Wed, Feb 27, 2013 at 7:53 AM, Benson Margulies bimargul...@gmail.comwrote: On Wed, Feb 27, 2013 at 2:28 AM, Tom White tom.e.wh...@gmail.com wrote: On Tue, Feb 26, 2013 at 6:34 AM, Andrei Savu savu.and...@gmail.com wrote: Tom do you want to be a champion for this proposal? Yes, I'd be happy to. One thing I think is worth discussing more here is whether Provisionr should be a TLP on graduation, or whether it should be a module in Whirr. Well, that puts this proposal into a gray area. In case you haven't been reading all the traffic on this list, I'll give a quick summary here. Historically, the Foundation had 'subprojects', and the the incubator hosted podlings intended, eventually, to become subprojects of existing TLPs. We don't do that anymore. If Provisionr becomes part of Whir, it just becomes, well, part of Whir. That raises the question of what you need the incubator for if this is your goal. There's a pretty simple alternative. The existing Provisionr team works with Whir to do an IP grant of the code to the Foundation. The existing team submits ICLAs. Whir makes a branch or other distinctive tree in source control and grants the Provisionr team commit access _to that tree_. Over time, the Provisionr people earn full committer status by merit, and appropriate adjustments are made to the tree structure. Given the state of the conversation about policy on this subject, I think it would be reasonable to ask you all to talk to the Whir people about this, and see if you an all come to an agreement for something like this in parallel with a discussion here. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Provisionr join the Apache Incubator
I think the following presentation does a better job at explaining the scope of Provisionr: http://www.slideshare.net/savu.andrei/creating-pools-of-virtual-machines-apachecon-na-2013 Regards, -- Andrei Savu On Wed, Feb 27, 2013 at 7:53 AM, Benson Margulies bimargul...@gmail.comwrote: On Wed, Feb 27, 2013 at 2:28 AM, Tom White tom.e.wh...@gmail.com wrote: On Tue, Feb 26, 2013 at 6:34 AM, Andrei Savu savu.and...@gmail.com wrote: Tom do you want to be a champion for this proposal? Yes, I'd be happy to. One thing I think is worth discussing more here is whether Provisionr should be a TLP on graduation, or whether it should be a module in Whirr. Well, that puts this proposal into a gray area. In case you haven't been reading all the traffic on this list, I'll give a quick summary here. Historically, the Foundation had 'subprojects', and the the incubator hosted podlings intended, eventually, to become subprojects of existing TLPs. We don't do that anymore. If Provisionr becomes part of Whir, it just becomes, well, part of Whir. That raises the question of what you need the incubator for if this is your goal. There's a pretty simple alternative. The existing Provisionr team works with Whir to do an IP grant of the code to the Foundation. The existing team submits ICLAs. Whir makes a branch or other distinctive tree in source control and grants the Provisionr team commit access _to that tree_. Over time, the Provisionr people earn full committer status by merit, and appropriate adjustments are made to the tree structure. Given the state of the conversation about policy on this subject, I think it would be reasonable to ask you all to talk to the Whir people about this, and see if you an all come to an agreement for something like this in parallel with a discussion here. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Curator for the Apache Incubator
+1 (non binding) I've used Curator in the past and I'm happy to see this project joining the foundation. -- Andrei Savu On Tue, Feb 26, 2013 at 1:14 AM, Jordan Zimmerman jor...@jordanzimmerman.com wrote: Hello, I would like to propose that Curator to be an Apache Incubator project. The proposal can be found here: http://wiki.apache.org/incubator/CuratorProposal I have included the contents of the proposal below. Sincerely, Jordan Zimmerman === = Curator - ZooKeeper client wrapper and rich ZooKeeper framework = == Abstract == Curator is a set of Java libraries that make using Apache ZooKeeper much easier. While ZooKeeper comes bundled with a Java client, using the client is non-trivial and error prone. == Proposal == Curator is a set of Java libraries that make using Apache ZooKeeper much easier. While ZooKeeper comes bundled with a Java client, using the client is non-trivial and error prone. It consists of three components that build on each other. Curator Client is a replacement for the bundled ZooKeeper class that takes care of some low-level housekeeping and provides some useful utilities. Curator Framework is a high-level API that greatly simplifies using ZooKeeper. It adds many features that build on ZooKeeper and handles the complexity of managing connections to the ZooKeeper cluster and retrying operations. Curator Recipes consists of implementations of some of the common ZooKeeper “recipes”. Additionally, Curator Test is included which includes utilities to help with unit testing ZooKeeper-based applications. == Background == Curator was initially developed by Netflix to make writing ZooKeeper-based applications easier and more reliable. Curator was open-sourced by Netflix on !GitHub as an Apache 2.0 licensed project in July 2011. During this time Curator has been formally released many times and has gained widespread adoption. == Rationale == New users of ZooKeeper are surprised to learn that a significant amount of connection management must be done manually. For example, when the ZooKeeper client connects to the ensemble it must negotiate a new session, etc. This takes some time. If you use a ZooKeeper client API before the connection process has completed, ZooKeeper will throw an exception. These types of exceptions are referred to as “recoverable” errors. Curator automatically handles connection management, greatly simplifying client code. Instead of directly using the ZooKeeper APIs you use Curator APIs that internally check for connection completion and wrap each ZooKeeper API in a retry loop. Curator uses a retry mechanism to handle recoverable errors and automatically retry operations. The method of retry is customizable. Curator comes bundled with several implementations (ExponentialBackoffRetry, etc.) or custom implementations can be written. The ZooKeeper documentation describes many possible uses for ZooKeeper calling each a “recipe”. While the distribution comes bundled with a few implementations of these recipes, most ZooKeeper users will need to manually implement one or more of the recipes. Implementing a ZooKeeper recipe is not trivial. Besides the connection handling issues, there are numerous edge cases that are not well documented that must be considered. For example, many recipes require that an ephemeral-sequential node be created. New users of ZooKeeper will not know that there is an edge case in ephemeral-sequential node creation that requires you to put a special “marker” in the node’s name so that you can search for the created node if an I/O failure occurs. This is but one of many edge cases that are not well documented but are handled by Curator. = Current Status = == Meritocracy == Curator was initially developed by Jordan Zimmerman in 2011 at Netflix. Developers external to Netflix provided feedback, suggested features and fixes and implemented extensions of Curator. Netflix's engineering team has since maintained the project and has been dedicated towards its improvement. Contributors to Curator include developers from multiple organizations around the world. Curator will be a meritocracy as it enters the Incubator and beyond. == Community == Curator is currently used by a number of organizations all over the world. Curator has an active and growing user and developer community with active participation in the [[http://groups.google.com/group/curator-users]] mailing list and at its !Github home: [[ https://github.com/Netflix/curator]]. Since open sourcing the project, there have been fifteen individuals from various organizations who have contributed code. == Core Developers == The core developers for Curator are: * Jordan Zimmerman * Jay Zarfoss Jordan has contributed towards Apache ZooKeeper and both Jordan and Jay are familiar with Apache principles and philosophy for community driven software development. == Alignment == Curator
Permission to edit wiki
Hi, Can someone grant me the permission to edit the Incubator wiki? My id is andreisavu. I want to move the proposal from GitHub before asking for a vote: https://github.com/axemblr/axemblr-provisionr/wiki/Provisionr-Proposal Thanks, -- Andrei Savu
[PROPOSAL] Provisionr join the Apache Incubator
Hi guys - I would like to propose Provisionr to the Apache Incubator: https://github.com/axemblr/axemblr-provisionr/wiki/Provisionr-Proposal Provisionr is a service that wants to solves the problem of cloud portability by hiding completely the APIs and only focusing on building a cluster that matches the same set of assumptions on all clouds, assumptions like: running a specific operating system (e.g. Ubuntu 12.04 LTS), having the same set of pre-installed packages and binaries, sane dns settings (forward reverse ip resolution - as needed for Hadoop), ntp settings, networking settings, firewall, ssh admin access, vpn access etc. I am looking forward to your feedback and suggestions. Thanks, -- Andrei Savu ## Abstract Provisionr is an effort to develop a service that can be used to create and manage pools of virtual machines on multiple clouds in an automatic or semi-automatic fashion. ## Proposal Provisionr solves the problem of cloud portability by hiding completely the APIs and only focusing on building a cluster that matches the same set of assumptions on all clouds, assumptions like: running a specific operating system (e.g. Ubuntu 12.04 LTS), having the same set of pre-installed packages and binaries, sane dns settings (forward reverse ip resolution - as needed for Hadoop), ntp settings, networking settings, firewall, ssh admin access, vpn access etc. As a secondary goal Provisionr should also provide primitives for building automatic or semi-automatic workflows for configuring services, workflows that assume that all the machines share a common set of characteristics as described above. ## Background Creating clusters on cloud infrastructure is non-trivial because careful orchestration is required. To make it easy to deploy services we need to start from a foundation that matches a common set of assumptions on multiple providers. ## Rationale This project started as a re-write of the core of Apache Whirr but has a different target being more focused on semi-automated workflows and cloud portability. ## Initial Goals * Build a community * Provide an excellent user experience for semi-automatic workflows (e.g. using Rundeck) * Implement a REST service and a Web Console * Add support for more providers ## Current Status Provisionr had four releases on GitHub and it's used to deploy Hadoop clusters on-demand at Axemblr and infrastructure for testing / QA. ### Meritocracy We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. ### Community The community interested in cloud service infrastructure is currently spread across many smaller projects, and one of the main goals of this project is to build a vibrant community to share best practices and build common infrastructure. ### Core developers Core developers are very experienced in the Apache ecosystem. To achieve more diversity of developers, we will be eager to recruit developers from diverse companies. * Andrei Savu - asavu at apache dot org (Apache Whirr PMC) * Ioan Eugen Stan - ieugen at apache dot org (Apache James PMC) * Alex Ciminian (not a committer) ### Alignment Provisionr complements Apache Whirr and later on it should provide a robust foundation for more advanced functionalities. ## Known Risks ### Orphaned products The contributors have significant open source experience and the project is being used as part of a commercial product, so the risk of being orphaned is relatively low. We plan to mitigate this risk by recruiting additional committers. ### Inexperience with Open Source Most of the initial committers have experience working on open source projects. Andrei Savu and Ioan Eugen Stan have experience as committers and PMC members on other Apache projects. ### Homogenous Developers We are committed to recruiting additional committers from other companies based on their contributions to the project. ### Reliance on Salaried Developers It is expected that Provisionr development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by their employer to contribute to this project. However, they are all passionate about the project, and we are confident that the project will continue even if no salaried developers contribute to the project. We are committed to recruiting additional committers including non-salaried developers. ### Relationships with Other Apache Products Provisionr is closely integrated with Karaf, CXF in a numerous ways. We look forward to collaborating with those communities, as well as other Apache communities. ### A Excessive Fascination with the Apache Brand We
Re: [PROPOSAL] Provisionr join the Apache Incubator
On Tue, Feb 26, 2013 at 5:26 AM, Greg Stein gst...@gmail.com wrote: A user list is not recommended for a new community. That only serves to divide a limited number of people. Your users should be involved on the dev@ list until the user influx becomes distracting. Good point. Thanks! It may be advisable to have a -commits list, but sending all commits to the -dev list is also workable. I would prefer to do only send JIRA updates on the dev- list with a Review-Then-Commit development process. Champions must be an Officer or a Member of the Foundation. Tom do you want to be a champion for this proposal? -- Andrei Savu
Re: [VOTE] Release Whirr version 0.6.0-incubating
+1 Checked signatures and started a HBase cluster. -- Andrei Savu / andreisavu.ro On Mon, Aug 22, 2011 at 10:37 PM, Andrei Savu savu.and...@gmail.com wrote: This is the first incubator release for Apache Whirr, version 0.6.0-incubating and the last release as an incubator project. It fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1230version=12316468 *** Please download, test and vote by August 26, 2011. Note that we are voting upon the source (tag), binaries are provided for convenience. Source and binary files: http://people.apache.org/~asavu/whirr-0.6.0-incubating-candidate-0 Maven staging repo: https://repository.apache.org/content/repositories/orgapachewhirr-058 The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/whirr/tags/release-0.6.0-incubating Whirr's KEYS file containing PGP keys we use to sign the release: http://svn.apache.org/repos/asf/incubator/whirr/dist/KEYS Note that the Incubator PMC needs to vote upon the release after a successful PPMC vote before any release can be made official. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE][RESULT] Release Whirr version 0.6.0-incubating (candidate 1)
This vote has now passed with 3 binding +1's, no +0's, and no -1's. The binding votes were from members of the new Whirr PMC: Patrick Hunt, +1 Tom White, +1 Andrei Savu, +1 The non-binding votes were as follows: Guillaume Alleon, +1 Edward J. Yoon, +1 I'll push the artifacts out. Thanks to everyone who voted! Cheers, Andrei - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Whirr version 0.6.0-incubating
On Wed, Aug 24, 2011 at 6:26 PM, Luciano Resende luckbr1...@gmail.com wrote: First incubator release for whirr (0.6.0-incubating) ? More like the first release for the 0.6 branch. Didn't Whirr just graduated ? http://markmail.org/message/ggjcxf6ndeaxn224 Yes but there are many things we have to do in order to prepare the infrastructure so that we can have a release as a top level project. We have been working on the current candidate for more than 2 and a half months and I don't it's a good idea to delay things even more. We've discussed about this and we've decided that this should be our last release as an incubator project. Now that the resolution was accepted by the board is no longer possible to have a last release as an incubator project? Thanks, Andrei - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Whirr version 0.6.0-incubating
This is the first incubator release for Apache Whirr, version 0.6.0-incubating and the last release as an incubator project. It fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1230version=12316468 *** Please download, test and vote by August 26, 2011. Note that we are voting upon the source (tag), binaries are provided for convenience. Source and binary files: http://people.apache.org/~asavu/whirr-0.6.0-incubating-candidate-0 Maven staging repo: https://repository.apache.org/content/repositories/orgapachewhirr-058 The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/whirr/tags/release-0.6.0-incubating Whirr's KEYS file containing PGP keys we use to sign the release: http://svn.apache.org/repos/asf/incubator/whirr/dist/KEYS Note that the Incubator PMC needs to vote upon the release after a successful PPMC vote before any release can be made official. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Bigtop for the Apache Incubator
I'm happy to see this project joining the Foundation. As an Apache
Whirr committer I feel a lot of pain when it comes to testing
compatibility for multiple services across multiple operating systems
(and multiple cloud providers).
I would love to join the Bigtop team as one of the initial committers
an do some of testing work we are already doing in Whirr.
PS: having ready to use .rpm and .deb packages sounds really great!
Cheers,
-- Andrei Savu / andreisavu.ro
On Tue, Jun 14, 2011 at 7:26 AM, Tom White tomwh...@apache.org wrote:
Hi,
I would like to propose Bigtop to be an Apache Incubator project.
Bigtop is a project for the development of packaging and tests of the
Hadoop ecosystem. The goal is to do testing at various levels
(packaging, platform, runtime, upgrade, etc...) developed by a
community with a focus on the system as a whole, rather than
individual projects.
Here's a link to the proposal on the wiki
http://wiki.apache.org/incubator/BigtopProposal
I've also included the initial contents below.
Cheers,
Tom
= Bigtop - Apache Hadoop Ecosystem Packaging and Test =
== Abstract ==
Bigtop - a project for the development of packaging and tests of the
Hadoop ecosystem.
== Proposal ==
The primary goal of Bigtop is to build a community around the
packaging and interoperability testing of Hadoop-related projects.
This includes testing at various levels (packaging, platform, runtime,
upgrade, etc...) developed by a community with a focus on the system
as a whole, rather than individual projects.
Build, packaging and integration test code that depends upon official
releases of the Apache Hadoop-related projects (HDFS, MapReduce,
HBase, Hive, Pig, ZooKeeper, etc...) will be developed and released by
this project. As bugs and other issues are found we expect these to be
fixed upstream.
== Background ==
The initial packaging and test code for Bigtop was developed by
Cloudera to package projects from the Apache Hadoop ecosystem and
provide a consistent, inter-operable framework.
== Rationale ==
Hadoop defines itself as:
{{{
The Apache Hadoop project develops open-source software for reliable,
scalable, distributed computing. Hadoop includes these subprojects:
* Hadoop Common: The common utilities that support the other Hadoop
subprojects.
* HDFS: A distributed file system that provides high throughput access
to application data.
* MapReduce: A software framework for distributed processing of large
data sets on compute clusters.
}}}
There are also several other Hadoop-related projects at Apache. Some
TLP examples include HBase, Hive, Mahout, ZooKeeper, and Pig. There
are also several new projects in the Incubator such as HCatalog and
Sqoop.
There is limited interoperability testing done the projects
themselves. The intent of this project is to build a community where
the projects are brought together, packaged, and tested for
interoperability.
Projects such as Apache Whirr (incubating), which deploy and use a
collection of Hadoop-related projects, would benefit from the
interoperability testing done by Bigtop, rather than picking and
testing project combinations themselves.
== Initial Goals ==
Much of the code for Bigtop has been released by Cloudera under the
Apache 2.0 license for over two years.
Some current goals include:
* create a set of packages for the Hadoop ecosystem, over a wide
range of platforms
* interoperability test these projects
* document project sets that are known to work well together
Bigtop’s release artifact would consist of a single tarball of
packaging and test code that, when built, would produce source and
binary Linux packages for the upstream projects.
= Current Status =
== Meritocracy ==
Bigtop was originally developed and released as an open source
packaging infrastructure, CDH, by Cloudera.
== Community ==
The community is primarily the original developers at Cloudera,
however a number of contributions to the packaging specifications have
been accepted from outside contributors. Growing a diverse community
is the main reason to bring Bigtop to the Apache Incubator.
== Core Developers ==
The core developers for Bigtop project are:
* Andrew Bayer has extensive expertise with build tools, specifically
Jenkins continuous integration and Maven.
* Peter Linnell has contributed to the RPM packaging.
* Bruno Mahé has overseen much of the development of the RPM and
Debian packaging system.
* Roman Shaposhnik designed and implemented the system testing framework.
Many of the committers to the Bigtop project have contributed towards
Hadoop or related Apache projects (Alejandro Abdelnur, Eli Collins,
Patrick Hunt, John Sichi, Michael Stack, Tom White) and are familiar
with Apache principals and philosophy for community driven software
development.
== Alignment ==
We expect projects in Bigtop to be drawn from Hadoop and related
projects at Apache. Bigtop
Re: [VOTE] Release Whirr version 0.4.0-incubating
Stefan, thanks for reviewing this release candidate. I've created a new issue to investigate if it's possible to add license headers to Confluence files: https://issues.apache.org/jira/browse/WHIRR-270 On Mon, Mar 28, 2011 at 5:56 PM, Stefan Bodewig bode...@apache.org wrote: On 2011-03-23, Andrei Savu wrote: Note that we are voting upon the source (tag), binaries are provided for convenience. Source and binary files: http://people.apache.org/~asavu/whirr-0.4.0-incubating-candidate-2 Maven staging repo: https://repository.apache.org/content/repositories/orgapachewhirr-028 The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/whirr/tags/release-0.4.0-incubating +1 Looks good to me. For your next release you may want to investigate whether you can add license headers to the confluence files in your source tree and the docs you generate from them. I'm neither familiar enough with Confluence nor the tools you use to create the documentation to know whether this is possible at all. Stefan - 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
[VOTE] Release Whirr version 0.4.0-incubating
This is the first incubator release for Apache Whirr, version 0.4.0-incubating. It fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1230version=12316065 *** Please download, test and vote by March, 28. Note that we are voting upon the source (tag), binaries are provided for convenience. Source and binary files: http://people.apache.org/~asavu/whirr-0.4.0-incubating-candidate-2 Maven staging repo: https://repository.apache.org/content/repositories/orgapachewhirr-028 The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/whirr/tags/release-0.4.0-incubating Whirr's KEYS file containing PGP keys we use to sign the release: http://svn.apache.org/repos/asf/incubator/whirr/dist/KEYS Note that the Incubator PMC needs to vote upon the release after a successful PPMC vote before any release can be made official. Cheers, Andrei - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Whirr version 0.4.0-incubating
+1 I've been able to run the integration tests on both cloud providers and I have started a ZooKeeper cluster. RC2 contains no code changes from RC1. -- Andrei Savu / andreisavu.ro On Wed, Mar 23, 2011 at 10:26 PM, Andrei Savu savu.and...@gmail.com wrote: This is the first incubator release for Apache Whirr, version 0.4.0-incubating. It fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1230version=12316065 *** Please download, test and vote by March, 28. Note that we are voting upon the source (tag), binaries are provided for convenience. Source and binary files: http://people.apache.org/~asavu/whirr-0.4.0-incubating-candidate-2 Maven staging repo: https://repository.apache.org/content/repositories/orgapachewhirr-028 The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/whirr/tags/release-0.4.0-incubating Whirr's KEYS file containing PGP keys we use to sign the release: http://svn.apache.org/repos/asf/incubator/whirr/dist/KEYS Note that the Incubator PMC needs to vote upon the release after a successful PPMC vote before any release can be made official. Cheers, Andrei - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Whirr version 0.4.0-incubating
Sebb, Stefan, thanks for noticing this issue. Is there a page on apache.org where I could read more about licensing issues? I'm not familiar with this topic. It would be great if you could check the current release candidate for more issue so that we can fix them in one batch. Thanks, Andrei On Fri, Mar 18, 2011 at 7:30 PM, sebb seb...@gmail.com wrote: On 18 March 2011 16:43, Stefan Bodewig bode...@apache.org wrote: On 2011-03-18, sebb wrote: But the main issue is that the binary distribution contains lots of 3rd party products which are not mentioned in either the NOTICE file or the LICENSE file. They likely are supposed to be in the - unfortunately empty - license files inside the lib directory. Whether it requires attribution or not, 3rd party product licenses must be recorded in the LICENSE file. The standard method is to include the text in the file, but it may be allowable to just include a pointer to the license elsewhere in the distribution. This pointer is missing, you are correct. I think these issues are sufficient to block the release. Of the binary convenience build. If the whirr project wanted to release the source tarball alone, the problems you have found wouldn't apply. The source tarball looks good to me. The NOTICE file includes attributions for two products that are not present. AIUI it's important that NOTICE only contains *required* attributions because the NOTICEs have to passed on to downstream users. The divider lines should be removed (not a blocker) and the year should be updated. Also, the lib directory is full of licence files for products that are not present. It's not necessary for everything in SVN to be in the source archive, though everything in the source archive must be in SVN (or be derivable directly from it) This is confusing. Stefan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Whirr version 0.4.0-incubating
This is the first incubator release for Apache Whirr, version 0.4.0-incubating. It fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1230version=12316065 *** Please download, test and vote by March, 22. Note that we are voting upon the source (tag), binaries are provided for convenience. Source and binary files: http://people.apache.org/~asavu/whirr-0.4.0-incubating-candidate-1 Maven staging repo: https://repository.apache.org/content/repositories/orgapachewhirr-017 The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/whirr/tags/release-0.4.0-incubating Whirr's KEYS file containing PGP keys we use to sign the release: http://svn.apache.org/repos/asf/incubator/whirr/dist/KEYS Note that the Incubator PMC needs to vote upon the release after a successful PPMC vote before any release can be made official. Cheers, Andrei - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Whirr version 0.4.0-incubating
Stefan, thanks for taking the time to review this release candidate. :) See bellow for my comments. On Tue, Mar 8, 2011 at 3:23 PM, Stefan Bodewig bode...@apache.org wrote: On 2011-03-07, Andrei Savu wrote: Source and binary files: http://people.apache.org/~asavu/whirr-0.4.0-incubating-candidate-0 The binary contains among other things the Bouncycastle provider so I think you have to do some extra work (see http://www.apache.org/dev/crypto.html) but I don't see Whirr mentioned on http://www.apache.org/licenses/exports/ and can't find any crypto notice inside the README. Tom will investigate and fix this one. RAT flags a few .sh, .css and .html files that are without any license header. We've already fixed this in trunk. I will backport the patch to the 0.4 branch. The binary distribution contains lots of jars that I can't easily match to the license files in the tarball. What is aws-ec2-1.0-beta-9.jar's license (likely jcloud's but how would I know)? They all belong to jclouds. We will add the missing license files to the repo. Whirr's KEYS file containing PGP keys we use to sign the release: http://svn.apache.org/repos/asf/incubator/whirr/dist/KEYS Note the file is different from http://www.apache.org/dist/incubator/whirr/KEYS which doesn't contain your key. Thanks for pointing this out. I will also update the release instructions on the wiki. Stefan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org We will restart the vote with a new release candidate soon. Cheers, Andrei - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Whirr version 0.4.0-incubating
This is the fourth incubator release for Apache Whirr, version 0.4.0-incubating. We already received one binding IPMC +1 vote for the PPMC release vote on whirr-dev, so are looking for two more. PPMC release vote thread: http://mail-archives.apache.org/mod_mbox/incubator-whirr-dev/201103.mbox/%3CAANLkTi=-9dEsd1WgAj7kS0aNU61xMFe0b=r=t2zof...@mail.gmail.com%3E The issues fixed for 0.3.0-incubating https://issues.apache.org/jira/secure/ReleaseNote.jspa?atl_token=6724a5b05e7a6de128c2b0e1f463d031d2c91e0aversion=12316065styleName=HtmlprojectId=1230Create=Create Source and binary files: http://people.apache.org/~asavu/whirr-0.4.0-incubating-candidate-0 Maven staging repo: https://repository.apache.org/content/repositories/orgapachewhirr-004 The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/whirr/tags/release-0.4.0-incubating Whirr's KEYS file containing PGP keys we use to sign the release: http://svn.apache.org/repos/asf/incubator/whirr/dist/KEYS The vote is open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, Andrei - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
