Re: [VOTE] Resolution to graduate Apache Impala to TLP

[Tom White]

+1

Tom

On Thu, Nov 9, 2017 at 4:25 AM, Jim Apple  wrote:
> The graduation of Impala to a TLP has been discussed[0] on dev@impala,
> voted on[1] on dev@impala, and discussed[2] on general@incubator. All
> threads were open 72 hours or more, and all seem to have quiesced.
>
> This is a call for a VOTE to graduate Impala to a TLP. The draft resolution
> is below. Please select from:
>
> [ ] +1: Graduate Impala to a TLP
> [ ] +-0: Neither graduate nor do not graduate Impala to a TLP
> [ ] -1: Do NOT graduate Impala to a TLP, because ...
>
> 
>
> [0]: <
> https://lists.apache.org/thread.html/2f5db4788aff9b0557354b9106c0328a29c1f90c1a74a228163949d2@%3Cdev.impala.apache.org%3E
>>
>
> [1]: <
> https://lists.apache.org/thread.html/a5a7c6895b3e019347d6e4e4cf49d67d094d31b8f2c7b4d59200f3e4@%3Cdev.impala.apache.org%3E
>>
>
> [2]: <
> https://lists.apache.org/thread.html/6b8598408f76a472532923c5a7fc510470b21671677ba3486568c57e@%3Cgeneral.incubator.apache.org%3E
>>
>
> 
>
> Establish the Apache Impala Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a high-performance distributed SQL engine.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Impala Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Impala Project be and hereby is responsible
> for the creation and maintenance of software related to a
> high-performance distributed SQL engine; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Impala" 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 Impala
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Impala
> 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 Impala Project:
>
> * Alex Behm 
> * Bharath Vissapragada 
> * Brock Noland 
> * Carl Steinbach 
> * Casey Ching 
> * Daniel Hecht 
> * Dimitris Tsirogiannis 
> * Henry Robinson 
> * Ishaan Joshi 
> * Jim Apple 
> * John Russell 
> * Juan Yu 
> * Lars Volker 
> * Lenni Kuff 
> * Marcel Kornacker 
> * Martin Grund 
> * Matthew Jacobs 
> * Michael Brown 
> * Michael Ho 
> * Sailesh Mukil 
> * Skye Wanderman-Milne 
> * Taras Bobrovytsky 
> * Tim Armstrong 
> * Todd Lipcon 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Apple be appointed to
> the office of Vice President, Apache Impala, 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 Impala PMC be and hereby is tasked
> with the creation of a set of bylaws intended to encourage open
> development and increased participation in the Apache Impala Project;
> and be it further
>
> RESOLVED, that the Apache Impala Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Impala
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Impala podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Spot into the Apache Incubator

[Tom White]

+1

Tom

On Tue, Sep 20, 2016 at 7:15 PM, Doug Cutting  wrote:
> Following the discussion thread, I would like to call a vote on
> accepting Spot into the Apache Incubator.
>
> [] +1 Accept Spot into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Spot into the Apache Incubator because ...
>
> This vote will run for the usual 72 hours.
>
> The proposal is attached, but you can also access it on the wiki:
>https://wiki.apache.org/incubator/SpotProposal
>
> Thanks,
>
> Doug
>
> = SpotProposal =
>
> == Abstract ==
>
> Spot is an open source platform for network telemetry (packet, flow,
> and proxy at the moment) built on an open data model and Apache
> Hadoop.
>
> == Proposal ==
>
> Spot (formerly Open Network Insight, or ONI) is an open source
> solution for network telemetry (packet, flow, and proxy at the moment)
> built on an open data model and Apache Hadoop. It provides ingestion
> and transformation of binary data, scalable machine learning, and
> interactive visualization for identifying threats in network flows and
> DNS packets.
>
> Spot has a pluggable architecture that can accommodate multiple open
> data models. Although cybersecurity/network-intrusion analysis is the
> initial use case for Spot, we are actively encouraging the
> contribution of new models that will enable other adjacent
> applications, such as fraud detection or IT-operational analytics such
> as performance and health monitoring. Because these models are open,
> users maintain control of their own data.
>
> More information on Spot can be found at the existing project website
> at http://open-network-insight.org/.
>
> == Background ==
>
> It almost goes without saying that cybersecurity is an acute and
> paramount concern globally, for organizations of all types and
> sizes. Fortunately, thanks to the availability of massively scalable
> (in the PBs) data infrastructure, security professionals can now make
> authentically data-driven decisions about how they protect their
> assets. For example, records of network traffic, captured as network
> flows, are often stored and analyzed for use in network management,
> and this same information can provide valuable insights into network
> vulnerabilities.
>
> Cybersecurity is just one example, however: There are other examples
> of adjacent use cases, such as user fraud detection or IT-operations
> analytics, that would benefit from the combination of Spot
> functionality and PB-scale data sets for analysis.
>
> == Rationale ==
>
> Although cybersecurity is its initial use case/data model, Spot is
> intended to more generally tackle the dual challenges of facilitating
> the development of big data-driven analytic solutions, while helping
> vendors avoid having to create one/off infrastructure for each use
> case. Spot will eliminate issues related to vendor data models that
> create silos between solutions, and that make it difficult for users
> to consume these innovations from multiple vendors. In summary, Spot
> will accelerate the development of new massively scalable analytic
> applications that give users more flexibility, and more choices.
>
> As an initial effort, we are now seeking to build an ecosystem of
> developers, data scientists, and security professionals to make Spot
> the open, community-driven, cybersecurity platform standard it needs
> to become. By bringing Spot to Apache, we hope to galvanize these
> groups to cooperate in this highly matrixed effort, and to build a
> global, and diverse, Spot community.
>
> == 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 build and testing workflows in the context
> of the ASF Incremental development and releases per Apache guidelines
>
> == Current Status ==
>
> === Releases ===
>
> Spot has undergone one public release (1.0). This initial release was
> not performed in the typical ASF fashion; we will adopt the ASF source
> release process upon joining the incubator.
>
> === Source ===
>
> Spot’s source, including core platform and associated submodules, is
> currently hosted in several GitHub repositories under the indicated
> licenses:
>
>  * Core (Apache License 2.0)
>  * Oni-ingest (Apache License 2.0)
>  * Oni-ml (Apache License 2.0
>  * Oni-oa (BSD & MIT)
>  * Oni-setup (Apache License 2.0)
>  * Oni-nfdump (BSD)
>  * Oni-lda-c (GNU General Public License version 2)
>
> The repositories will be transitioned to Apache’s git hosting during
> incubation.  Issues related to GPL code will be resolved during
> incubation.
>
>
> === Issue Tracking ===
>
> Spot’s bug and feature tracking is hosted on Github at:
>
>  * https://github.com/Open-Network-Insight/open-network-insight/issues
>
> Issue tracking will be transitioned to Apache’s JIRA instance during 
> incubation.
>
> === Code review ===
>
> Spot maintainers currently use “LGTM” (Looks Good to 

Re: [VOTE] Graduate Sentry

[Tom White]

+1 (binding)

Tom

On Wed, Feb 24, 2016 at 7:20 PM, Sravya Tirukkovalur  wrote:
> Hi all,
>
> Following the positive discussion[1] and vote[2] in the Sentry
> community and a discussion[3] on the incubator list to graduate
> Sentry, I am calling a VOTE to graduate the project from the Incubator
> to a TLP. Please vote on the resolution pasted below.
>
> [ ] +1 Graduate Sentry from the Incubator
> [ ] +0 Don't care
> [ ] -1 Don't graduate Sentry from the Incubator (please specify reason)
>
> This vote will be open for at least 72 hours.
>
> References:
>
> [1] https://s.apache.org/dev_discuss
> [2] https://s.apache.org/dev_vote_result
> [3] https://s.apache.org/general_discuss
> Other:
> https://s.apache.org/general_notify
> https://cwiki.apache.org/confluence/display/SENTRY/Sentry+maturity+assessment
>
> Resolution to create a TLP from graduating Incubator podling:
>
> ==
>
>
> X. Establish the Apache Sentry Project
>
>   WHEREAS, the Board of Directors deems it to be in the best
>   interests of the Foundation and consistent with the
>   Foundation's purpose to establish a Project Management
>   Committee charged with the creation and maintenance of
>   open-source software, for distribution at no charge to
>   the public, related to Fine grained authorization to data and
> metadata in Hadoop.
>
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "Apache Sentry Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
>
>   RESOLVED, that the Apache Sentry Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to Fine grained authorization to data and metadata in Hadoop;
>   and be it further
>
>   RESOLVED, that the office of "Vice President, Apache Sentry" 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 Sentry Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache Sentry 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 Sentry Project:
>
> * Ali Rizvi 
>
>* Anne Yu 
>
>* Arun Suresh 
>
>* Brock Noland 
>
>* Chaoyu Tang 
>
>* Colin Ma 
>
>* Daisy Zhou 
>
>* Dapeng Sun 
>
>* David Nalley 
>
>* Erick Tryzelaar 
>
>* Gregory Chanan 
>
>* Guoquan Shen 
>
>* Hadi Nahari 
>
>* Hao Hao 
>
>* Jarek Jarcec Cecho 
>
>* Johnny Zhang 
>
>* Karthik Ramachandran 
>
>* Mark Grover 
>
>* Milo Polte 
>
>* Lenni Kuff 
>
>* Patrick Daly 
>
>* Patrick Hunt 
>
>* Prasad Mujumdar 
>
>* Raghu Mani 
>
>* Sean Mackrory 
>
>* Shreepadma Venugopalan 
>
>* Sravya Tirukkovalur 
>
>* Tuong Truong 
>
>* Vamsee Yarlagadda 
>
>* Xiaomeng Huang 
>
>* Xuefu Zhang 
>
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sravya Tirukkovalur
>   be appointed to the office of Vice President, Apache Sentry, 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 Sentry PMC be and hereby is
>   tasked with the creation of a set of bylaws intended to
>   encourage open development and increased participation in the
>   Apache Sentry Project; and be it further
>
>   RESOLVED, that the Apache Sentry Project be and hereby
>   is tasked with the migration and rationalization of the Apache
>   Incubator Sentry podling; and be it further
>
>   RESOLVED, that all responsibilities pertaining to the Apache
>   Incubator Sentry podling encumbered upon the Apache Incubator
>   Project are hereafter discharged.
>
> ==

Re: [VOTE] Accept Beam into the Apache Incubator

[Tom White]

Platform/DataflowJavaSDK),
> on Stack Overflow
> (http://stackoverflow.com/questions/tagged/google-cloud-dataflow) and has
> had contributions from a number of organizations and indivuduals.
>
> Everyday, Cloud Dataflow is actively used by a number of organizations and
> institutions for batch and stream processing of data. We believe acceptance
> will allow us to consolidate existing Dataflow-related work, grow the
> Dataflow community, and deepen connections between Dataflow and other open
> source projects.
>
> === Core Developers ===
>
> The core developers for Dataflow and the Dataflow runners are:
>
>  * Frances Perry
>  * Tyler Akidau
>  * Davor Bonaci
>  * Luke Cwik
>  * Ben Chambers
>  * Kenn Knowles
>  * Dan Halperin
>  * Daniel Mills
>  * Mark Shields
>  * Craig Chambers
>  * Maximilian Michels
>  * Tom White
>  * Josh Wills
>  * Robert Bradshaw
>
> === Alignment ===
>
> The Beam SDK can be used to create Beam pipelines which can be executed on
> Apache Spark or Apache Flink. Beam is also related to other Apache projects,
> such as Apache Crunch. We plan on expanding functionality for Beam runners,
> support for additional domain specific languages, and increased portability
> so Beam is a powerful abstraction layer for data processing.
>
> == Known Risks ==
>
> === Orphaned Products ===
>
> The Dataflow SDK is presently used by several organizations, from small
> startups to Fortune 100 companies, to construct production pipelines which
> are executed in Google Cloud Dataflow. Google has a long-term commitment to
> advance the Dataflow SDK; moreover, Dataflow is seeing increasing interest,
> development, and adoption from organizations outside of Google.
>
> === Inexperience with Open Source ===
>
> Google believes strongly in open source and the exchange of information to
> advance new ideas and work. Examples of this commitment are active OSS
> projects such as Chromium (https://www.chromium.org) and Kubernetes
> (http://kubernetes.io/). With Dataflow, we have tried to be increasingly
> open and forward-looking; we have published a paper in the VLDB conference
> describing the Dataflow model
> (http://www.vldb.org/pvldb/vol8/p1792-Akidau.pdf) and were quick to release
> the Dataflow SDK as open source software with the launch of Cloud Dataflow.
> Our submission to the Apache Software Foundation is a logical extension of
> our commitment to open source software.
>
> === Homogeneous Developers ===
>
> The majority of committers in this proposal belong to Google due to the fact
> that Dataflow has emerged from several internal Google projects. This
> proposal also includes committers outside of Google who are actively
> involved with other Apache projects, such as Hadoop, Flink, and Spark.  We
> expect our entry into incubation will allow us to expand the number of
> individuals and organizations participating in Dataflow development.
> Additionally, separation of the Dataflow SDK from Google Cloud Dataflow
> allows us to focus on the open source SDK and model and do what is best for
> this project.
>
> === Reliance on Salaried Developers ===
>
> The Dataflow SDK and Dataflow runners have been developed primarily by
> salaried developers supporting the Google Cloud Dataflow project. While the
> Dataflow SDK and Cloud Dataflow have been developed by different teams (and
> this proposal would reinforce that separation) we expect our initial set of
> developers will still primarily be salaried. Contribution has not been
> exclusively from salaried developers, however. For example, the contrib
> directory of the Dataflow SDK
> (https://github.com/GoogleCloudPlatform/DataflowJavaSDK/tree/master/contrib)
> contains items from free-time contributors. Moreover, seperate projects,
> such as ScalaFlow (https://github.com/darkjh/scalaflow) have been created
> around the Dataflow model and SDK. We expect our reliance on salaried
> developers will decrease over time during incubation.
>
> === Relationship with other Apache products ===
>
> Dataflow directly interoperates with or utilizes several existing Apache
> projects.
>
>  * Build
>   * Apache Maven
>  * Data I/O, Libraries
>   * Apache Avro
>   * Apache Commons
>  * Dataflow runners
>   * Apache Flink
>   * Apache Spark
>
> Beam when used in batch mode shares similarities with Apache Crunch;
> however, Beam is focused on a model, SDK, and abstraction layer beyond Spark
> and Hadoop (MapReduce.) One key goal of Beam is to provide an intermediate
> abstraction layer which can easily be implemented and utilized across
> several different processing frameworks.
>
> === An excessive fascination with the Apache brand ===
>
> With this pr

Impala commit policy

[Tom White]

The vote to accept Impala into the incubator has passed
(http://s.apache.org/u6r), however there are still some concerns about
CTR/RTC. My main takeaways from the CTR/RTC thread are that it's not a
binary choice, and that it's entirely reasonable that different
communities have different commit policies at the ASF.

I think Julian Hyde's suggestion that the Impala podling start with no
explicit commit policy is a good one. Incubation should be used as a
time to work out what works best for a project. The initial Impala
community should discuss the commit policy as they go through the
process of setting up ASF infra and start growing the podling. In
particular this will include how Gerrit can be used as a tool to
facilitate reviews, and how that fits with ASF culture, which is
something that other projects are looking at too.

Cheers,
Tom

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Impala into the Apache Incubator

[Tom White]

 wiki (https://github.com/cloudera/Impala/wiki)
>
> Impala’s auto-generated API documentation (
> http://impala.io/doc/html/index.html)
>
> = Initial Source =
> Impala’s initial source contribution will come from
> http://github.com/cloudera/Impala/.
>
> = External Dependencies =
>
> Impala depends upon a number of third-party libraries, which we list below.
> We intend to compile a LICENSE.txt file in the very short term (see
> https://issues.cloudera.org/browse/IMPALA-2670).
>
>  * Google gflags (BSD)
>  * Google glog (BSD)
>  * Apache Thrift (Apache Software License v2.0)
>  * Apache Commons (Apache Software License v2.0)
>  * Apache Hadoop (Apache Software License v2.0)
>  * Apache HBase (Apache Software License v2.0)
>  * Apache Hive (Apache Software License v2.0)
>  * Boost (Boost Software License)
>  * OpenLdap (OpenLDAP Software License)
>  * rapidjson (MIT)
>  * Google RE2 (BSD-style)
>  * lz4 (BSD)
>  * snappy (BSD)
>  * cyrus-sasl (CMU License)
>  * Apache Avro (Apache Software License v2.0)
>  * Cloudera squeasel (Apache Software License v2.0)
>  * Apache htrace (Incubating) (Apache Software License v2.0)
>  * Apache Sentry (Incubating) (Apache Software License v2.0)
>  * Apache Shiro (Apache Software License v2.0)
>  * Twitter Bootstrap (Apache Software License v2.0)
>  * d3 (BSD)
>  * LLVM (BSD-like)
>
> Build and test dependencies:
>
>  * ant (Apache Software License v2.0)
>  * Apache Maven (Apache Software License v2.0)
>  * cmake (BSD)
>  * clang (BSD)
>  * Google gtest (Apache Software License v2.0)
>
> = Required Resources =
>
> We request that following resources be created for the project to use:
>
> == Mailing lists ==
>
>  * priv...@impala.incubator.apache.org (moderated subscriptions)
>  * comm...@impala.incubator.apache.org
>  * d...@impala.incubator.apache.org
>  * iss...@impala.incubator.apache.org
>  * u...@impala.incubator.apache.org
>
> == Git repository ==
> https://git.apache.org/impala.git
>
> == JIRA instance ==
> JIRA project IMPALA (IMPALA or IMP)
>
> == Other Resources ==
> We hope to continue using Gerrit for our code review and commit workflow.
> We are involved with discussions that the Kudu team at Cloudera have been
> having with Jake Farrell to start discussions on how Gerrit can fit into
> the ASF. We know that several other ASF projects or podlings are also
> interested in Gerrit.
>
> If the Infrastructure team does not have the bandwidth to support gerrit,
> we will continue to support our own instance of gerrit for Impala, and make
> the necessary integrations such that commits are properly authenticated and
> maintain sufficient provenance to uphold the ASF standards (e.g. via the
> solution adopted by the AsterixDB podling).
>
> = Initial Committers =
>
>  * Tim Armstrong
>  * Alex Behm
>  * Taras Bobrovytsky
>  * Casey Ching
>  * Martin Grund
>  * Daniel Hecht
>  * Michael Ho
>  * Matthew Jacobs
>  * Ishaan Joshi
>  * Lenni Kuff
>  * Marcel Kornacker
>  * Sailesh Mukil
>  * Henry Robinson
>  * John Russell
>  * Dimitris Tsirogiannis
>  * Skye Wanderman-Milne
>  * Juan Yu
>
> == Affiliations ==
> All: Cloudera Inc.
>
> = Sponsors =
>
> == Champion ==
> Tom White
>
> == Nominated Mentors ==
>  * Tom White (Cloudera)
>  * Todd Lipcon (Cloudera)
>  * Carl Steinbach (LinkedIn)
>  * Brock Noland (StreamSets)
>
>
> = Sponsoring Entity =
> We ask that the Incubator PMC sponsor this proposal.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Kudu into the Apache Incubator

[Tom White]

+1 (binding)

Tom

On Tue, Nov 24, 2015 at 7:32 PM, Todd Lipcon  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 per Apache guidelines
>
> == Current Status ==
>
>  Releases 
>
> Kudu has undergone one public release, tagged here
> https://github.com/cloudera/kudu/tree/kudu0.5.0-release
>
> This initial release was not performed in the typical ASF fashion -- no
> source tarball was released, but rather only convenience binaries made
> 

Re: [VOTE] Graduate Apache Parquet from the Incubator

[Tom White]

+1

Tom

On Mon, Apr 13, 2015 at 4:46 PM, Jake Farrell jfarr...@apache.org wrote:
 This thread is to start a vote on the graduation resolution Apache Parquet
 has approved on the dev list with 14 positive votes (11 PPMC (4 from IPMC
 members), 3 community)

 Status page: http://incubator.apache.org/projects/parquet.html
 Graduation discussion: http://s.apache.org/8qU
 Graduation resolution: http://s.apache.org/w7

 Apache Parquet has been apart of the Incubator since May 2014 and in that
 time has

 * Had successful IPMC approved releases
 * Expanded the PPMC with new members
 * Worked and submitted fixes in other Apache projects to improve Parquet
 support
 * A successful community vote to graduate with 14 positive votes

 I would like to get the voting started with my own +1

 Please vote

 [ ] +1 Graduate Apache Parquet as a TLP
 [ ] +0
 [ ] -1 Don't graduate Apache Parquet as a TLP because…

 Voting will end in 72 hours, i.e. 12:00 UTC on 2015-04-16
 http://www.timeanddate.com/countdown/to?iso=20150416T12

 -Jake



 === Board Resolution ==

 Establish the Apache Parquet Project

 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the
 Foundation's purpose to establish a Project Management
 Committee charged with the creation and maintenance of
 open-source software, for distribution at no charge to the
 public, related to a columnar storage format for Hadoop.

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the Apache Parquet Project,
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further

 RESOLVED, that the Apache Parquet Project be and hereby is
 responsible for the creation and maintenance of software
 related to a columnar storage format for Hadoop; and be it further

 RESOLVED, that the office of Vice President, Apache Parquet 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 Parquet Project, and to have primary responsibility
 for management of the projects within the scope of
 responsibility of the Apache Parquet 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 Parquet Project:

* Chris Aniszczyk caniszc...@apache.org
* Ryan Blue b...@apache.org
* Jonathan Coveney jcove...@apache.org
* Tianshuo Deng tians...@apache.org
* Jake Farrell jfarr...@apache.org
* Marcel Kornacker mar...@apache.org
* Mickael Lacour mlac...@apache.org
* Julien Le Dem jul...@apache.org
* Alex Levenson alexleven...@apache.org
* Nong Li n...@apache.org
* Todd Lipcon t...@apache.org
* Chris Mattmann mattm...@apache.org
* Aniket Mokashi aniket...@apache.org
* Lukas Nalezenec lu...@apache.org
* Brock Noland br...@apache.org
* Wesley Graham Peck wesleyp...@apache.org
* Remy Pecqueur rpecqu...@apache.org
* Dmitriy Ryaboy dvrya...@apache.org
* Roman Shaposhnik r...@apache.org
* Daniel Weeks dwe...@apache.org
* Tom White tomwh...@apache.org

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Julien Le Dem
 be appointed to the office of Vice President, Apache Parquet, 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 Parquet PMC be and hereby is
 tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache Parquet Project; and be it further

 RESOLVED, that the Apache Parquet Project be and hereby
 is tasked with the migration and rationalization of the Apache
 Incubator Parquet podling; and be it further

 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator Parquet podling encumbered upon the Apache Incubator
 Project are hereafter discharged.

-
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

[Tom White]

 https://github.com/Parquet/parquet-mr/graphs/contributors) from a diverse
 group of companies.
 Several of the core contributors to the project are deeply familiar with
 OSS and Apache specifically: Julien Le Dem was until recently the PMC Chair
 for Apache Pig, and Dmitriy Ryaboy, Aniket Mokashi, and Jonathan Coveney
 are also Apache Pig committers with contributions to several other Apache
 projects. Todd Lipcon and Tom White are committers to Apache Hadoop and
 multiple other related projects. Brock Noland is a Hive committer.

 === Homogenous Developers ===

 The initial committers come from a number of companies and countries.
 Parquet has an active community of developers, and we are committed to
 recruiting additional committers based on their contributions to the
 project. The java library component alone has contributions from 31
 individual github accounts, 14 of which contributed over 1000 lines of code.

 === Reliance on Salaried Developers ===

 It is expected that Parquet development will occur on both salaried time
 and on volunteer time, after hours. The majority of initial committers are
 paid by their employers 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. As
 evidence of this statement, we present the GitHub punchcard (see
 https://github.com/Parquet/parquet-mr/graphs/punch-card) showing that a lot
 of activity happens on weekends. We are committed to recruiting additional
 committers including non-salaried developers.

 === Relationships with Other Apache Products ===

 As mentioned in the Alignment section, Parquet is closely related to
 Hadoop. It provides an API that allowed it to be easily integrated with
 many other apache projects: Pig, Hive, Avro, Thrift, Spark, Drill, Crunch,
 Tajo. Some of the features it provides are similar to the ORC file format
 which is part of the Hive project. However Parquet focused on being
 framework agnostic and language independent and has been really successful
 to that end. On top of the Apache projects mentioned above, Parquet is also
 integrated with other open source projects, including Protocol Buffers,
 Cloudera Impala or Scrooge. We look forward to continue collaborating with
 those communities, as well as other Apache communities.

 === An Excessive Fascination with the Apache Brand ===

 Parquet is an already healthy and well known open source project. This
 proposal is not for the purpose of generating publicity. Rather, the
 primary benefits to joining Apache are those outlined in the Rationale
 section.

 == Documentation ==

 Documentation is currently located as README markdown files:

  * https://github.com/Parquet/parquet-format
  * https://github.com/Parquet/parquet-mr

 == Source and Intellectual Property Submission Plan ==

 The Parquet codebase is currently hosted on Github:
 https://github.com/Parquet.

 These are the codebases that we would migrate to the Apache foundation.

 == External Dependencies ==


  * Junit: EPL
  * Apache Commons: ALv2
  * Apache Thrift: ALv2
  * Apache Maven: ALv2
  * Apache Avro: ALv2
  * Apache Hadoop: ALv2
  * Google Guava: ALv2
  * Google Protobuf: New BSD License

 == Cryptography ==

 We do not expect Parquet to be a controlled export item due to the use of
 encryption.

 == Required Resources ==

 === Mailing lists ===

  * priv...@parquet.incubator.apache.org
  * comm...@parquet.incubator.apache.org
  * d...@parquet.incubator.apache.org

 == Subversion Directory ==

 Git is the preferred source control system:

  * git://git.apache.org/parquet-format
  * git://git.apache.org/parquet-mr

 == Issue Tracking ==

 We'd like to keep using the Git review and issue tracking tools.
 Controlling Pull requests closing through git commit messages in
 git.apache.org

 == Initial Committers ==

  * Aniket Mokashi aniket...@gmail.com
  * Brock Noland br...@apache.org
  * Chris Aniszczyk caniszc...@gmail.com
  * Dmitriy Ryaboy dvrya...@apache.org
  * Jake Farrell jfarr...@apache.org
  * Jonathan Coveney jcove...@gmail.com
  * Julien Le Dem jul...@apache.org
  * Lukas Nalezenec lukas.naleze...@gmail.com
  * Marcel Kornacker mar...@cloudera.com
  * Mickael Lacour
  * Nong Li n...@cloudera.com
  * Remy Pecqueur
  * Ryan Blue b...@cloudera.com
  * Tianshuo Deng dengtians...@gmail.com
  * Tom White tomwh...@apache.org
  * Wesley Peck

 == Affiliations ==

  * Aniket Mokashi - Twitter
  * Brock Noland - Cloudera
  * Chris Aniszczyk - Twitter
  * Dmitriy Ryaboy - Twitter
  * Jake Farrell
  * Jonathan Coveney - Twitter
  * Julien Le Dem - Twitter
  * Lukas Nalezenec
  * Marcel Kornacker - Cloudera
  * Mickael Lacour - Criteo
  * Nong Li - Cloudera
  * Remy Pecqueur - Criteo
  * Ryan Blue - Cloudera
  * Tianshuo Deng - Twitter
  * Tom White - Cloudera
  * Wesley Peck - ARRIS, Inc.

 == Sponsors ==

 === Champion ===

  * Todd Lipcon

 === Nominated Mentors ===

  * Tom

Re: [VOTE] Release of Apache Twill 0.1.0-incubating [rc1]

[Tom White]

+1

I noticed a couple of things to fix for the next release (not blockers):
* Missing license header in twill-0.1.0-incubating/checkstyle.xml
* There's a file called DEPENDENCIES which looks like it is
auto-generated, and is not in the tagged source, but is in the source
archive.

Cheers,
Tom

On Sat, Feb 1, 2014 at 12:42 AM, Terence Yim cht...@gmail.com wrote:
 Hi all,

 This is to call for a vote for release of Apache Twill
 v0.1.0-incubating. This will be the first incubator release for Apache
 Twill.

 Vote on twill-dev:
 http://s.apache.org/Rsy

 Result on vote on twill-dev:
 http://s.apache.org/KMR

 The tag to be voted upon is v0.1.0-incubating:
 https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=tag;h=refs/tags/v0.1.0-incubating

 The source tarball, including signatures, digests, etc can be found at:
 https://dist.apache.org/repos/dist/dev/incubator/twill/0.1.0-incubating-rc1/src

 The binary artifacts can be found at:
 https://dist.apache.org/repos/dist/dev/incubator/twill/0.1.0-incubating-rc1/bin

 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://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=log;h=refs/tags/v0.1.0-incubating

 Please vote on releasing this package as Apache Twill 0.1.0-incubating

 The vote will be open for 72 hours.

 [ ] +1 Release this package as Apache Twill 0.1.0-incubating
 [ ] -1 Do not release this package because ...

 Thanks,
 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 Twill for Incubation

[Tom White]

 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.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Storm into the Incubator

[Tom White]

+1

Tom

On Thu, Sep 12, 2013 at 8:19 PM, Doug Cutting cutt...@apache.org wrote:
 Discussion about the Storm proposal has subsided, issues raised now
 seemingly resolved.

 I'd like to call a vote to accept Storm as a new Incubator podling.

 The proposal is included below and is also at:

   https://wiki.apache.org/incubator/StormProposal

 Let's keep the vote open for four working days, until 18 September.

 [ ] +1 Accept Storm into the Incubator
 [ ] +0 Don't care.
 [ ] -1 Don't accept Storm because...

 Doug


 = Storm Proposal =

 == Abstract ==

 Storm is a distributed, fault-tolerant, and high-performance realtime
 computation system that provides strong guarantees on the processing
 of data.

 == Proposal ==

 Storm is a distributed real-time computation system. Similar to how
 Hadoop provides a set of general primitives for doing batch
 processing, Storm provides a set of general primitives for doing
 real-time computation. Its use cases span stream processing,
 distributed RPC, continuous computation, and more. Storm has become a
 preferred technology for near-realtime big-data processing by many
 organizations worldwide (see a partial list at
 https://github.com/nathanmarz/storm/wiki/Powered-By). As an open
 source project, Storm’s developer community has grown rapidly to 46
 members.

 == Background ==

 The past decade has seen a revolution in data processing. MapReduce,
 Hadoop, and related technologies have made it possible to store and
 process data at scales previously unthinkable. Unfortunately, these
 data processing technologies are not realtime systems, nor are they
 meant to be. The lack of a Hadoop of realtime has become the biggest
 hole in the data processing ecosystem. Storm fills that hole.

 Storm was initially developed and deployed at BackType in 2011. After
 7 months of development BackType was acquired by Twitter in July 2011.
 Storm was open sourced in September 2011.

 Storm has been under continuous development on its Github repository
 since being open-sourced. It has undergone four major releases (0.5,
 0.6, 0.7, 0.8) and many minor ones.


 == Rationale ==

 Storm is a general platform for low-latency big-data processing. It is
 complementary to the existing Apache projects, such as Hadoop. Many
 applications are actually exploring using both Hadoop and Storm for
 big-data processing. Bringing Storm into Apache is very beneficial to
 both Apache community and Storm community.

 The rapid growth of Storm community is empowered by open source. We
 believe the Apache foundation is a great fit as the long-term home for
 Storm, as it provides an established process for community-driven
 development and decision making by consensus. This is exactly the
 model we want for future Storm 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 ==

 Storm has undergone four major releases (0.5, 0.6, 0.7, 0.8) and many
 minor ones. Storm 0.9 is about to be released. Storm is being used in
 production by over 50 organizations. Storm codebase is currently
 hosted at github.com, 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 ===

 The need for a low-latency big-data processing platform in the open
 source is tremendous. Storm is currently being used by at least 50
 organizations worldwide (see
 https://github.com/nathanmarz/storm/wiki/Powered-By), and is the most
 starred Java project on Github. By bringing Storm into Apache, we
 believe that the community will grow even bigger.

 === Core Developers ===

 Storm was started by Nathan Marz at BackType, and now has developers
 from Yahoo!, Microsoft, Alibaba, Infochimps, and many other companies.

 === Alignment ===

 In the big-data processing ecosystem, Storm is a very popular
 low-latency platform, while Hadoop is the primary platform for batch
 processing. We believe that it will help the further growth of
 big-data community by having Hadoop and Storm aligned within Apache
 foundation. The alignment is also beneficial to other Apache
 communities (such as Zookeeper, Thrift, Mesos). We could include
 additional sub-projects, Storm-on-YARN and Storm-on-Mesos, in the near
 future.

 == Known Risks ==

 === Orphaned Products ===

 The risk of the Storm project being abandoned is minimal. There are at
 least 50 organizations (Twitter, Yahoo!, Microsoft, Groupon, Baidu,
 Alibaba, Alipay, Taobao, PARC, RocketFuel etc) are highly 

Re: [VOTE]: Accept Sentry in Apache Incubator

[Tom White]

 Hadoop ecosystem, such as HDFS file permissions, by providing finer
 grained access control to data and metadata. It supersedes the access
 control capabilities of some other projects such as Apache Hive by
 providing stronger guarantees against malicious access.  Currently, Sentry
 integrates with Apache Hive, however we are planning to provide support for
 other components such as Apache Pig.

 While projects such as Apache Knox aim to provide perimeter security, the
 goal of Sentry is to implement a fine-grained role-based access control
 policy. Thus Sentry complements Apache Knox.

 == Known Risks ==

 === Orphaned Products ===

 Sentry is already deployed in production at a few well established
 companies and they are actively sharing feature requests. The risks of it
 being orphaned is negligible.

 === Inexperience with Open Source ===

 All committers of  the Sentry project are intimately familiar with the
 Apache model for open-source development and are experienced with working
 with various Apache open -source communities.

 === Homogeneous Developers ===

 The initial set of committers includes developers from several
 organizations - Cloudera, Oracle, Lab41, Nvidia and Wibidata.  We expect
 that once approved for incubation, the project will further attract new
 contributors.

 === Reliance on Salaried Developers ===

 It is expected that Sentry will be developed on both salaried and volunteer
 time, although all of the initial developers will work on it mainly on
 salaried time.

 === Relationships with Other Apache Products ===

 Sentry depends on other Apache Projects: Apache Hadoop, Apache Log4J,
 Apache Hive, Apache Shiro, multiple Apache Commons components. Build is
 orchestrated by Apache Maven. Sentry complements Apache Knox.

 === An Excessive Fascination with the Apache Brand ===

 We would like Sentry to become an Apache project to further foster a
 healthy community of users and developers around it. Since Sentry solves an
 important problem faced by Apache Hadoop users and interacts with other
 components of the Apache Hadoop ecosystem, we believe that Apache is the
 right home for Sentry.

 == Documentation ==

   * Cloudera provides documentation specific to its distribution of Sentry
 at:
 http://www.cloudera.com/content/cloudera-content/cloudera-docs/Sentry/Sentry.pdf
   * Sentry jira at Cloudera: https://issues.cloudera.org/browse/access

 == Initial Source ==

 https://github.com/cloudera/access

 == Source and Intellectual Property Submission Plan ==

 All of Sentry’s code is under Apache 2 license already.

 == External Dependencies ==

 All dependencies have licenses compatible with ASL. Dependencies that are
 not directly using ASL are,

   * Junit - Eclipse Public License

 == Cryptography ==

 Sentry currently doesn’t directly use any cryptographic libraries. However,
 Sentry uses Apache Shiro, which provides support for cryptography features
 such as hash, cipher etc.

 == Required Resources ==

 === Mailing Lists ===

   * priv...@sentry.incubator.apache.org for private PMC discussions (with
 moderated subscriptions)
   * secur...@sentry.incubator.apache.org for private security related
 discussions
   * d...@sentry.incubator.apache.org
   * comm...@sentry.incubator.apache.org

 === Source code repository ===

 Git repository running at http://git-wip-us.apache.org/.

 === Issue Tracking ===

 JIRA Sentry (SENTRY)

 === Other Resources ===

 The existing code already has unit and integration tests so we would like a
 Jenkins CI instance that would run the tests on reference environment. We
 would also like to use Jenkins to run tests for every newly submitted patch
 (so called pre-commit hook), however this can be added after project
 creation.

 == Initial Committers ==

   * Ali Rizvi (ali.rizvi at oracle.com)
   * Arvind Prabhakar (arvind at apache.org)
   * Brock Noland  (brock at apache.org)
   * Chaoyu Tang (ctang at cloudera.com)
   * Daisy Zhou (daisy at wibidata.com)
   * David Nalley (ke4qqq at apache.org)
   * Erick Tryzelaar(etryzelaar at iqt.org)
   * Greg Chanan (gchanan at apache.org)
   * Hadi Nahari (hnahari at nvidia.com)
   * Jarek Jarcec Cecho (jarcec at apache.org)
   * Johnny Zhang (xiaoyuz at cloudera.com)
   * Karthik Ramachandran (kramachandran at iqt.org)
   * Mark Grover (mgrover at cloudera.com)
   * Milo Polte (milo at wibidata.com)
   * Lenni Kuff  (lskuff at cloudera.com)
   * Patrick Daly (daly at cloudera.com)
   * Patrick Hunt (phunt at apache.org)
   * Prasad Mujumdar (prasadm at apache.org)
   * Raghu Mani (raghu.mani at oracle.com)
   * Sean Mackrory (sean at cloudera.com)
   * Shreepadma Venugopalan (shreepadma at cloudera.com)
   * Sravya Tirukkovalur (sravya at cloudera.com)
   * Tom White (tomwhite at apache.org)
   * Xuefu Zhang (xuefu at apache.org)

 == Affiliations ==

   * Ali Rizvi (Oracle)
   * Arvind Prabhakar (Cloudera)
   * Brock Noland  (Cloudera)
   * Chaoyu Tang (Cloudera)
   * Daisy Zhou (Wibidata)
   * David

Re: [VOTE] Release Apache Provisionr version 0.4.0-incubating, RC0

[Tom White]

+1 verified signature and checksum, ran RAT, checked LICENSE, NOTICE
and DISCLAIMER, built from source.

Tom

On Thu, Jun 27, 2013 at 1:33 AM, Andrei Savu as...@apache.org wrote:
 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!

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)

[Tom White]

+1 (verified checksum and signature, checked LICENSE, NOTICE, DISCLAIMER).

Tom

On Tue, Jun 11, 2013 at 1:05 AM, Benjamin Mahler
benjamin.mah...@gmail.com wrote:
 Please vote on releasing the following candidate as Apache Mesos
 (incubating) version 0.12.0. This will be the fourth incubator release for
 Mesos in Apache.

 The candidate for Mesos 0.12.0-incubating release is available at:
 http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz

 The tag to be voted on is 0.12.0-rc1:
 https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=57d7b9719dce662881b162eba10b5765a807d53c

 The MD5 checksum of the tarball can be found at:
 http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz.md5

 The signature of the tarball can be found at:
 http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz.asc

 PGP key used to sign the release:
 http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD0BEBB95D141A5B6

 Please vote on releasing this package as Apache Mesos 0.12.0-incubating!

 The vote is open until Thursday, June 13th at 00:00 UTC and passes if
 a majority
 of at least 3 +1 IPMC votes are cast.

 [ ] +1 Release this package as Apache Mesos 0.12.0-incubating
 [ ] -1 Do not release this package because ...

 To learn more about Apache Mesos, please see
 http://incubator.apache.org/mesos.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduation of Apache Mesos

[Tom White]

+1

Tom

On Wed, Jun 12, 2013 at 9:03 PM, Mattmann, Chris A (398J)
chris.a.mattm...@jpl.nasa.gov wrote:
 Hi All,

 The Apache Mesos community is ready to graduate. They have added
 committers and PPMC members while in the Incubator; have made a
 few releases; are discussing their issues on list and in the Apache
 way, and are inclusive and representative of Apache's goals as a
 Foundation.

 I'm extremely happy to put them up for Incubator graduation.
 We've VOTEd as a community to move forward with this:

 DISCUSS thread here: http://s.apache.org/XAu
 VOTE thread here: http://s.apache.org/K8C
 VOTE RESULT: Message-ID: cdde1f13.d6ea1%chris.a.mattm...@jpl.nasa.gov

 Project Incubator status page here:
 http://incubator.apache.org/projects/mesos.html

 Board resolution pasted at bottom of email.

 Existing tallies from the community VOTE:

 +1
 Chris Mattmann*
 Vinod Kone
 Benjamin Hindman
 Benjamin Mahler
 Yan Xiu
 Deepal Jayasinghe
 Brenden Matthews
 Matei Zaharia
 Ant Elder*
 Konstantin Boudnik

 * - indicates IPMC

 Please VOTE to graduate Apache Mesos from the Incubator. Though
 only Incubator PMC member VOTEs are binding, all are welcome to
 voice your opinion. I'll leave the VOTE open for at least 72 hours,
 and hopefully can get enough VOTEs in time to close it by Saturday
 or Sunday in time for the board meeting on 6/19.

 [ ] +1 Graduate Apache Mesos from the Incubator.
 [ ] +0 Don't care.
 [ ] -1 Don't graduate Apache Mesos from the Incubator because..

 Thanks everyone!

 Cheers,
 Chris


 ---board resolution
 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the
 Foundation's purpose to establish a Project Management
 Committee charged with the creation and maintenance of
 open-source software, for distribution at no charge to the
 public, related to efficient cluster management, resource
 isolation and sharing across distributed applications.

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the Apache Mesos Project, be
 and hereby is established pursuant to Bylaws of the Foundation;
 and be it further

 RESOLVED, that the Apache Mesos Project be and hereby is
 responsible for the creation and maintenance of software
 related to efficient cluster management, resource isolation
 and sharing across distributed applications; and be it further
 RESOLVED, that the office of Vice President, Apache Mesos 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 Mesos Project, and to have primary responsibility for
 management of the projects within the scope of responsibility
 of the Apache Mesos 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 Mesos Project:

  * Ali Ghodsi a...@apache.org
 * Andy Konwinski and...@apache.org
 * Benjamin Hindhman b...@apache.org
 * Benjamin Mahler bmah...@apache.org
 * Brian McCalister bri...@apache.org
 * Ian Holsman i...@apache.org
 * Matei Alexandru Zahari ma...@apache.org
 * Chris Mattmann mattm...@apache.org
 * Tom White tomwh...@apache.org
 * Vinod Kone vinodk...@apache.org
 * Brenden Matthews bren...@apache.org
 * Thomas Marshall tmarsh...@apache.org
 * Charles Reiss wog...@apache.org


 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Benjamin Hindman be
 appointed to the office of Vice President, Apache Mesos, 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 Apache Mesos Project be and hereby is
 tasked with the migration and rationalization of the Apache
 Incubator Mesos podling; and be it further

 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator Mesos podling encumbered upon the Apache Incubator
 Project are hereafter discharged.


 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++





 -
 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

Re: [VOTE] Accept jclouds into the Apache Incubator

[Tom White]

 as a build tool with the jclouds API.

 jclouds includes support for the Apache CloudStack API and is used as a
 compatibility test tool for its EC2 interface. jclouds can also be used to
 test Apache Deltacloud EC2 portability.

 === An Excessive Fascination with the Apache Brand ===

 jclouds recognizes the fortitude of the Apache brand, but the motivation
 for becoming an Apache project is to strengthen and expand the jclouds
 community and its user base. While the jclouds community has seen steady
 growth over the past several years, association with the ASF is expected to
 expedite this pattern of growth. Development is expected to continue on
 jclouds under the Apache license whether or not it is supported by the ASF.

 == Documentation ==

 The [[http://www.jclouds.org/|jclouds]] project documentation is publicly
 available at the following sites:

   * http://jclouds.org: installation guide, user guides, development
 resources, news, resources to get started
   * https://github.com/jclouds/jclouds: current source, source code
 issues log
   * https://github.com/jclouds/jclouds.github.com: static content for
 jclouds.org, documentation issues log
   * https://twitter.com/jclouds: jclouds on Twitter
   * https://groups.google.com/forum/?fromgroups#!forum/jclouds-dev: the
 jclouds development forum on Google Groups
   * https://groups.google.com/forum/?fromgroups#!forum/jclouds: the
 jclouds community forum on Google Groups

 == Initial Source ==

 The initial source is located on GitHub in the following repositories:

  * git://github.com/jclouds/jclouds.git
  * git://github.com/jclouds/jclouds-labs.git
  * git://github.com/jclouds/jclouds.github.com.git
  * git://github.com/jclouds/jclouds-chef.git
  * git://github.com/jclouds/jclouds-cli.git
  * git://github.com/jclouds/jclouds-karaf.git
  * git://github.com/jclouds/jclouds-examples.git

 == Source and Intellectual Property Submission Plan ==

 jclouds's initial source is licensed under the Apache License, Version
 2.0. https://github.com/jclouds/jclouds/blob/master/resources/LICENSE.txt

 == External Dependencies ==

 This is a listing of Maven coordinates for all of the external
 dependencies jclouds uses. All of the dependencies are in Sonatype and
 their licenses should be accessible.

  * aopalliance:aopalliance:jar:1.0:compile
  * com.google.code.gson:gson:jar:2.2.2:compile
  * com.google.guava:guava:jar:14.0.1:compile
  * com.google.inject.extensions:guice-assistedinject:jar:3.0:compile
  * com.google.inject:guice:jar:3.0:compile
  * javax.annotation:jsr250-api:jar:1.0:compile
  * javax.inject:javax.inject:jar:1:compile
  * javax.ws.rs:jsr311-api:jar:1.1.1:compile
  * org.99soft.guice:rocoto:jar:6.2:compile

 == Cryptography ==

 jclouds contains no cryptographic algorithms, but it does provide the
 ability for people to plug in various cryptographic libraries.

 == Required Resources ==

 === Mailing lists ===

  * jclouds-dev: for development discussions
  * jclouds-user: for community discussions
  * jclouds-private: for PPMC discussions
  * jclouds-commits: for code changes

 === Apache git repository ===

 The jclouds team is experienced in git and requests the following
 allocation on the Apache git server:

 git://git.apache.org/incubator-jclouds.git

 === Issue Tracking ===

 jclouds currently uses GitHub for issue tracking. The intent is to request
 an allocation for Jira upon acceptance into the Incubator. Proposed project
 name: jclouds

 == Initial Committers ==

  * Ignasi Barrera, ignasi dot barrera at gmail dot com
  * Andrew Bayer, abayer at apache dot org
  * Ioannis Canellos, iocanel at gmail dot com
  * Adrian Cole, adrianc at netflix dot com
  * Andrew Gaul, gaul at maginatics dot com
  * Andrew Phillips, aphillips at qrmedia dot com
  * Matt Stephenson, mattstep at mattstep dot net
  * Everett Toews, everett dot toews at rackspace dot com
  * Becca Wood, silkysun at silkysun dot net

 == Affiliations ==

  * Ignasi Barrera, Abiquo
  * Andrew Bayer, Cloudera
  * Ioannis Canellos, Red Hat
  * Adrian Cole, Netflix
  * Andrew Gaul, Maginatics
  * Matt Stephenson, Google
  * Everett Toews, Rackspace

 == Sponsors ==
 === Champion ===

  * Brian McCallister, Apache Software Foundation

 === Mentors ===

  * Brian McCallister, Apache Software Foundation
  * Tom White, Apache Software Foundation
  * Henning Schmiedehausen, Apache Software Foundation
  * David Nalley, Apache Software Foundation
  * Jean-Baptiste Onofré, Apache Software Foundation
  * Mohammad Nour El-Din, Apache Software Foundation
  * Olivier Lamy, Apache Software Foundation
  * Tomaz Muraus, Apache Software Foundation
  * Suresh Marru, Apache Software Foundation
  * Carlos Sanchez, Apache Software Foundation

 === Sponsoring Entity ===

 The jclouds contributors and community request sponsorship from the
 Incubator.

Re: [VOTE] Accept Provisionr into the Apache Incubator

[Tom White]

, 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 sharing ideas and
 best practices for running cloud services. The ASF does a great job at
 building communities, which is why we want to build Provisionr at Apache.

 == Documentation ==

  * https://github.com/axemblr/axemblr-provisionr/wiki
  *
 https://github.com/axemblr/axemblr-provisionr/wiki/Axemblr-Provisionr-in-5-Minutes
  *
 https://github.com/axemblr/axemblr-provisionr/wiki/Starting-an-HDFS-cluster-on-EC2-with-Provisionr-and-Rundeck
  *
 http://www.slideshare.net/savu.andrei/creating-pools-of-virtual-machines-apachecon-na-2013

 == Initial Source ==

 Available on GitHub: https://github.com/axemblr/axemblr-provisionr

 == Source and Intellectual Property Submission Plan ==

 We are going to prepare a software grant as needed. The source code is
 already available under the Apache 2.0 license.

 == External Dependencies ==

 The existing external dependencies all have Apache compatible licenses:
 Activiti (Apache 2.0), AWS SDK (Apache 2.0), jclouds (Apache 2.0), Google
 Guava (Apache 2.0).

 == Cryptography ==

 Provisionr uses standard APIs and tools for SSH and SSL.

 == Required Resources ==

 === Mailing lists ===

  * provisionr-private
  * provisionr-dev

 === Version Control ===

 Git repository

 === Issue Tracking ===

 JIRA Provisionr (PROVISIONR)

 === Other Resources ===

 The existing code already has unit and integration tests so we would like a
 Jenkins instance to run them whenever a new patch is submitted. This can be
 added after project creation.

 == Initial Committers ==

  * Andrei Savu - asavu at apache dot org
  * Ioan Eugen Stan - ieugen at apache dot org
  * Alex Ciminian - alex.ciminian at gmail dot org
  * Amandeep Khurana - amansk at gmail dot com
  * Roman Shaposhnik - rvs at apache dot org
  * Eric Sammer - esammer at apache dot org

 == Sponsors ==

 === Champion ===

 Tom White - tomwhite at apache dot org

 === Nominated Mentors ===

  * Roman Shaposhnik - rvs at apache dot org
  * Tom White - tomwhite at apache dot org
  * Mohammad Nour - mnour at apache dot org

 === Sponsoring ===

 Incubator PMC

-
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

[Tom White]

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. Provisionr shares no code with Whirr, but it would be natural
for Whirr to use Provisionr for reliable cloud provisioning. Indeed,
as the proposal states, This project started as a re-write of the
core of Apache Whirr, so Provisionr is a sort of Next Generation
Whirr. More importantly, in terms of community, Andrei is on the Whirr
PMC and I think that the communities would have considerable overlap.
It's worth deciding now, since there is an ongoing discussion about
whether existing projects are suitable homes for newly graduated
projects [1].

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.

Thanks,
Tom

[1] 
http://mail-archives.apache.org/mod_mbox/incubator-general/201302.mbox/%3ccabd8fluoxt71foldya60faebd4ys1-ovxapkkrufjn9hndd...@mail.gmail.com%3E

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Crunch 0.5.0 (incubating) RC0

[Tom White]

+1 checked signatures and checksums, RAT report is clean, license and
notice look good, builds from source.

Tom

On Sat, Feb 16, 2013 at 1:08 AM, Josh Wills jwi...@apache.org wrote:
 Hello,

 This is a call for a vote on releasing the following candidate as Apache
 Crunch 0.5.0 (incubating). This is our third release at Apache, and it
 fixes the following issues:

 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313526version=12323476

 The vote will be open for at least 72 hours. We received 1 IPMC member vote
 from Patrick Hunt on the vote thread on crunch-dev, and will need two more
 IPMC votes in order to make the release.

 Release artifacts:
 http://people.apache.org/~jwills/crunch-0.5.0-incubating-RC0/

 Maven staging repo:
 https://repository.apache.org/content/repositories/orgapachecrunch-228/

 The tag to be voted upon:
 https://git-wip-us.apache.org/repos/asf?p=incubator-crunch
 .git;a=tag;h=e60ace8424109dc941b13262d43dab659ffaca8a

 Crunch's KEYS file:
 http://www.apache.org/dist/incubator/crunch/KEYS

 Thanks,
 Josh

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Apache Knox Hadoop Gateway Project into the Incubator

[Tom White]

 org

 Subversion Directory

 https://svn.apache.org/repos/asf/incubator/knox

 Issue Tracking

 JIRA Knox (KNOX)

 Initial Committers

 Kevin Minder (kevin DOT minder AT hortonworks DOT com)

 Larry McCay (lmccay AT hortonworks DOT com)

 John Speidel (jspeidel AT hortonworks DOT com)
 Tom Beerbower (tbeerbower AT hortonworks DOT com)
 Sumit Mohanty (smohanty AT hortonworks DOT com)
 Venkatesh Seetharam (venkatesh AT hortonworks DOT com)

 Affiliations

 Kevin Minder (Hortonworks)

 Larry McCay (Hortonworks)

 John Speidel (Hortonworks)
 Tom Beerbower (Hortonworks)
 Sumit Mohanty (Hortonworks)
 Venkatesh Seetharm (Hortonworks)
 Owen O'Malley (Hortonworks)
 Mahadev Konar (Hortonworks)
 Alan Gates (Hortonworks)
 Devaraj Das (Hortwonrks)
 Chris Douglas (Microsoft)
 Chris Mattmann (NASA)
 Tom White (Cloudera)

 Sponsors

 Champion

 Devaraj Das (ddas AT apache DOT org)

 Nominated Mentors

 Owen O’Malley (omalley AT apache DOT org)
 Mahadev Konar (mahadev AT apache DOT org)
 Alan Gates (gates AT apache DOT org)
 Devaraj Das (ddas AT apache DOT org)
 Chris Douglas (cdouglas AT apache DOT org)
 Chris Mattmann (chris DOT a DOT mattmann AT jpl DOT nasa DOT gov)
 Tom White (tom DOT e DOT white AT gmail DOT com)

 Sponsoring Entity

 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: [PROPOSAL] Knox Hadoop Gateway Project

[Tom White]

This looks like an interesting and useful project. I'd like to volunteer as
a mentor on it.

Thanks,
Tom
On 11 Feb 2013 14:56, Kevin Minder kevin.min...@hortonworks.com wrote:

 Knox Gateway Proposal

 == Abstract ==

 Knox Gateway is a system that provides a single point of secure access for
 Apache Hadoop clusters.

 == Proposal ==

 The Knox Gateway (“Gateway” or “Knox”) is a system that provides a single
 point of authentication and access for Apache Hadoop services in a cluster.
 The goal is to simplify Hadoop security for both users (i.e. who access the
 cluster data and execute jobs) and operators (i.e. who control access and
 manage the cluster). The Gateway runs as a server (or cluster of servers)
 that serve one or more Hadoop clusters.

 Provide perimeter security to make Hadoop security setup easier
 Support authentication and token verification security scenarios
 Deliver users a single cluster end-point that aggregates capabilities for
 data and jobs
 Enable integration with enterprise and cloud identity management
 environments

 == Background ==

 An Apache Hadoop cluster is presented to consumers as a loose collection
 of independent services. This makes it difficult for users to interact with
 Hadoop since each service maintains it’s own method of access and security.
 As well, for operators, configuration and administration of a secure Hadoop
 cluster is a complex and many Hadoop clusters are insecure as a result.

 == Rationale ==

 Organizations that are struggling with Hadoop cluster security result in
 a) running Hadoop without security or b) slowing adoption of Hadoop. The
 Gateway aims to provide perimeter security that integrates more easily into
 existing organizations’ security infrastructure. Doing so will simplify
 security for these organizations and benefit all Hadoop stakeholders (i.e.
 users and operators). Additionally, making a dedicated perimeter security
 project part of the Apache Hadoop ecosystem will prevent fragmentation in
 this area and further increase the value of Hadoop as a data platform.

 == Current Status ==

 Prototype available, developed by the list of initial committers.

 === Meritocracy ===

 We desire to build a diverse developer community around Gateway following
 the Apache Way. We want to make the project open source and will encourage
 contributors from multiple organizations following the Apache meritocracy
 model.

 === Community ===

 We hope to extend the user and developer base in the future and build a
 solid open source community around Gateway. Apache Hadoop has a large
 ecosystem of open source projects, each with a strong community of
 contributors. All project communities in this ecosystem have an opportunity
 to participate in the advancement of the Gateway project because
 ultimately, Gateway will enable the security capabilities of their project
 to be more enterprise friendly.

 === Core Developers ===

 Gateway is currently being developed by several engineers from Hortonworks
 - Kevin Minder, Larry McCay, John Speidel, Tom Beerbower and Sumit Mohanty.
 All the engineers have deep expertise in middleware, security  identity
 systems and are quite familiar with the Hadoop ecosystem.

 === Alignment ===

 The ASF is a natural host for Gateway given that it is already the home of
 Hadoop, Hive, Pig, HBase, Oozie and other emerging big data software
 projects. Gateway is designed to solve the security challenges familiar to
 the Hadoop ecosystem family of projects.

 == Known Risks ==

 === Orphaned products  Reliance on Salaried Developers ===

 The core developers plan to work full time on the project. We believe that
 this project will be of general interest to many Hadoop users and will
 attract a diverse set of contributors. We intend to demonstrate this by
 having contributors from several organizations recognized as committers by
 the time Knox graduates from incubation.

 === Inexperience with Open Source ===

 All of the core developers are active users and followers of open source.
 As well, Hortonworks has a strong heritage of success with contributions to
 Apache Hadoop Projects.

 === Homogeneous Developers ===

 The current core developers are from Hortonworks, however, we hope to
 establish a developer community that includes contributors from several
 corporations.

 === Reliance on Salaried Developers ===

 Currently, the developers are paid to do work on Gateway. However, once
 the project has a community built around it, we expect to get committers
 and developers from outside the current core developers.

 === Relationships with Other Apache Products ===

 Gateway is going to be used by the users and operators of Hadoop, and the
 Hadoop ecosystem in general.

 === A Excessive Fascination with the Apache Brand ===

 Our interest in developing Gateway in Apache project is to follow an
 established development model, as well since many of the Hadoop ecosystem
 projects also are part of Apache, Gateway will 

Re: [VOTE][PROPOSAL] Hadoop Development Tools

[Tom White]

+1

Cheers,
Tom

On Tue, Nov 6, 2012 at 7:57 AM, Adam Berry ambe...@yahoo-inc.com wrote:
 Hello,

 This proposal has been open for discussion for a a few weeks, so now 
 submitting for a vote for this project to be accepted into the incubator.

 Cheers,
 Adam Berry

 = HDT (Hadoop Development Tools) =

 == Abstract ==
 Tools to support developing applications that use Apache Hadoop from within 
 Eclipse.

 == Proposal ==
 Hadoop Development Tools are a set of extensions to Eclipse providing support 
 for creating, launching and debugging distributed applications, as well as 
 interacting with HDFS filesystems. This work will build on the existing Map 
 Reduce Tools present in the Apache Hadoop project.

 == Background ==
 Map Reduce Tools have existed as part of contrib for Apache Hadoop. 
 Unfortunately they are source tied to a single version of Hadoop, and 
 development has stalled, with little movement past the Hadoop 0.20 line.

 == Rationale ==
 Support for newer versions of Hadoop from within Eclipse is regularly raised 
 on the Hadoop mailing lists, so there is a clear need to drive these tools 
 forward. Development tools generally are worked on separate from the target 
 tools/platform, separating the tools out will allow for supporting multiple 
 versions, so a developer could work with a heterogeneous environment.

 == Initial Goals ==
  * Give the tools project a home of its own.
  * Port current MapReduce tools feature set to all current release lines of 
 Hadoop in a single Eclipse install.
  * Documentation and tutorials for all features.
  * Publish Eclipse update site, and join Eclipse marketplace listing.
  * Establish release cycle that combines support for Hadoop and Eclipse 
 release cycles.
  * Look to build support for YARN, MRUnit and possibly other Hadoop-related 
 projects.

 == Current Status ==
 The source for the current MapReduceTools lives in the contrib section of the 
 Hadoop source. In its current implementation it is tied to the version of 
 Hadoop against which it is compiled. The layout and API that it was developed 
 with means that it can only be used with the 0.20 or 1.0 Hadoop releases, the 
 new layout and YARN api introduced with the 0.23 and 2.0 lines are not 
 supported.


 === Meritocracy ===
 Several people and companies have already expressed an interest in 
 contributing to this project, and we hope to attract additional interest 
 during the proposal discussion. We plan to invest and support a meritocracy 
 that attracts, invites, and supports newcomers to build a vibrant and  
 diverse community.

 === Community ===
 The target community is developers who are working developing Map/Reduce 
 applications against Hadoop. Given the success of Hadoop the target group is 
 likely to be quite large. Separation from the Hadoop community would make it 
 easier to support multiple versions of hadoop, as well as merging the release 
 cycles of Hadoop and Eclipse to provide predictable iteration and improvement 
 in the toolset.

 === Core Developers ===
 The initial list of developers includes people experienced with Hadoop and 
 developing against the Eclipse platform.
  * Adam Berry (amberry at yahoo-inc dot com)
  * Jeffrey Zemerick (jeffrrey at mtnfog dot com)
  * Evert Lammerts (Evert dot Lammerts at sara dot nl)
  * Simone Gianni (simoneg at apache dot org)

 === Alignment ===
 Hadoop Development Tools aligns with both Hadoop and Eclipse. Hadoop as the 
 platform for the development target, and Eclipse as the IDE platform used as 
 the base for the tools.

 == Known Risks ==

 === Orphaned Products ===

 === Inexperience with Open Source ===
 The committers have experience with Apache and Eclipse open source 
 development.

 === Reliance on Salaried Developers ===
 Hadoop Development Tools will be developed with a mix of salaried and 
 volunteer time.

 === Relationships with Other Apache Projects ===
 Hadoop Development Tools is closely related to Apache Hadoop.

 === An Excessive Fascination with the Apache Brand ===
 Given the success of Hadoop and associated projects, Apache is the natural 
 place for the Hadoop Development Tools. Chris Mattman suggested the Apache 
 Incubator as appropriate on the Hadoop general mailing list following the 
 success that MRUnit had taking the path from Hadoop contrib to an Apache top 
 level project.

 == Documentation ==
 Documentation for the current tools can be found at 
 http://wiki.apache.org/hadoop/EclipsePlugIn

 == Initial Source ==
 http://svn.apache.org/repos/asf/hadoop/common/trunk/hadoop-mapreduce-project/src/contrib/eclipse-plugin/

 ==  Source and Intellectual Property Submission Plan ==
 The source, and any suggested initial patches, are already hosted either in 
 Apache’s Subversion or JIRA.

 ==  External Dependencies ==
 Eclipse Platform
 Eclipse Java Development Tools

 ==  Cryptography ==
 Hadoop Development Tools likely does not fall into this area.

 ==  Required Resources ==
 === Mailing lists ===

Re: [VOTE] Graduate Bigtop podling from Apache Incubator

[Tom White]

+1

Tom

On Wed, Sep 12, 2012 at 5:08 PM, Roman Shaposhnik r...@apache.org wrote:
 This is a call for vote to graduate Bigtop podling from Apache Incubator

 The Apache Bigtop project entered incubator in June of 2011. Since then we
 have grown the community in users and contributors, and we've made
 significant improvements to the project. Following the Apache guidelines we
 have made four releases, we are preparing a 5th major and 6th maintenance
 releases, and we've added two new committers. The current set of committers
 and PPMC members are from different organizations and have demonstrated
 interest in growing the community further. We have learned the basis to manage
 the different aspects of an Apache project. The community of Bigtop is active,
 healthy and growing and has demonstrated the ability to self-govern using
 accepted Apache practices. Bigtop community has voted to proceed with
 graduation [1] and the result can be found at [2].

 Please cast your votes:

 [  ] +1 Graduate Bigtop podling from Apache Incubator
 [  ] +0 Indifferent to the graduation status of Bigtop podling
 [  ] -1 Reject graduation of Bigtop podling from Apache Incubator

 This vote will remain open for at least 72 hours from now (till 15 Sep
 2012, NOON PST). Please find the proposed board resolution below.

 [1] http://s.apache.org/SGm
 [2] http://s.apache.org/LOA

 Thanks,
 Roman Shaposhnik

 X. Establish the Apache Bigtop Project

WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software related to a system for integration,
packaging, deployment and validation of a big data management
software distribution based on Apache Hadoop
for distribution at no charge to the public.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache Bigtop Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache Bigtop Project be and hereby is
responsible for the creation and maintenance of software
related to a system for
open-source software related to a system for integration,
packaging, deployment and validation of a big data management
software distribution based on Apache Hadoop; and be it further

RESOLVED, that the office of Vice President, Apache Bigtop 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 Bigtop Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Bigtop 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 Bigtop Project:

 * Alan Gatesga...@apache.org
 * Patrick Hunt  ph...@apache.org
 * Steve Loughranste...@apache.org
 * Tom White tomwh...@apache.org

 * Alejandro Abdelnurt...@apache.org
 * Andrew Bayer  aba...@apache.org
 * Konstantin Boudnikc...@apache.org
 * Stephen Chu   s...@apache.org
 * Bruno Mahébm...@apache.org
 * Peter Linnell plinn...@apache.org
 * James Pagejamesp...@apache.org
 * Patrick Taylor Ramsey p...@apache.org
 * Roman Shaposhnik  r...@apache.org
 * Michael Stack st...@apache.org
 * Andrei Savu   as...@apache.org
 * Edward J. Yoonedwardy...@apache.org

 * Andre Arcilla arci...@apache.org
 * Eli Collins   e...@apache.org
 * Travis Crawford   traviscrawf...@apache.org
 * John Sichij...@apache.org
 * Owen O'Malley omal...@apache.org

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Roman Shaposhnik
be appointed to the office of Vice President, Apache Bigtop,
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 Bigtop PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Bigtop Project; and be it further

RESOLVED, that the Apache Bigtop Project

Re: [VOTE] Apache Crunch (incubating) 0.3.0 Release Candidate 1

[Tom White]

+1

Verified signature and checksums. Ran a RAT report. Checked for binary
and SCM files. Read LICENSE, NOTICE, DISCLAIMER files - all look
correct. Built from source successfully.

Cheers,
Tom

On Tue, Sep 11, 2012 at 1:58 PM, Josh Wills jwi...@apache.org wrote:
 Hello everyone,

 This is a call for a vote on releasing the following candidate as Apache
 Crunch 0.3.0 (incubating). This will be our first release. A vote was held
 on the developer mailing list and passed with 4 +1s:

 http://markmail.org/thread/yvtvog5lrj3a7gep

 +1s:
 phunt (IPMC)
 jwills (binding)
 greid (binding)
 mafr (binding)

 We need two additional IPMC votes.

 The release fixes the issues listed here:

 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313526version=12322446

 Please download, test, and vote by September 14th at 6AM Pacific Time.

 Source files:
 http://people.apache.org/~jwills/crunch-0.3.0-incubating-RC1/

 Maven staging repo:
 https://repository.apache.org/content/repositories/orgapachecrunch-040/

 The tag to be voted upon:
 https://git-wip-us.apache.org/repos/asf?p=incubator-crunch.git;a=tag;h=4666bd889f9b641d7c0157bc4401a1b985fedc89

 Crunch's KEYS file:
 http://www.apache.org/dist/incubator/crunch/KEYS

 The vote will be open for 72 hours.

 [ ] +1  approve
 [ ] +0  no opinion
 [ ] -1  disapprove (and reason why)

 Thank you,
 Josh

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Blur into the Apache Incubator

[Tom White]

+1

Tom

On Fri, Jul 20, 2012 at 12:42 PM, Aaron McCurry amccu...@gmail.com wrote:
 I would like to call a vote for accepting Blur for incubation in the
 Apache Incubator. The full proposal is available below.

 Please cast your vote:

 [ ] +1, bring Blur into Incubator
 [ ] +0, I don't care either way,
 [ ] -1, do not bring Blur into Incubator, because...

 This vote will be open for 72 hours and only votes from the Incubator
 PMC are binding.

 Thank you for your consideration!

 Aaron

 http://wiki.apache.org/incubator/BlurProposal

 = Blur Proposal =

 == Abstract ==
 Blur is a search platform capable of searching massive amounts of data
 in a cloud computing environment. Blur leverages several existing
 Apache projects, including Apache Lucene, Apache Hadoop, Apache
 !ZooKeeper and Apache Thrift.  Both bulk and near real time (NRT)
 updates are possible with Blur.  Bulk updates are accomplished using
 Hadoop Map/Reduce and NRT are performed through direct Thrift calls.

 == Proposal ==
 Blur is an open source search platform capable of querying massive
 amounts of data at incredible speeds. Rather than using the flat,
 document-like data model used by most search solutions, Blur allows
 you to build rich data models and search them in a semi-relational
 manner similar to joins while querying a relational database. Using
 Blur, you can get precise search results against terabytes of data at
 Google-like speeds.  Blur leverages multiple open source projects
 including Hadoop, Lucene, Thrift and !ZooKeeper to create an
 environment where structured data can be transformed into an index
 that runs on a Hadoop cluster.  Blur uses the power of Map/Reduce for
 bulk indexing into Blur.  Server failures are handled automatically by
 using !ZooKeeper for cluster state and HDFS for index storage.

 == Background ==
 Blur was created by Aaron !McCurry in 2010. Blur was developed to
 solve the challenges in dealing with searching huge quantities of data
 that the traditional RDBMS solutions could not cope with while still
 providing JOIN-like capabilities to query the data.  Several other
 open source projects have implemented aspects of this design including
 elasticsearch, Katta and Apache Solr.

 == Rationale ==
 There is a need for a distributed search capability within the Hadoop
 ecosystem. Currently, there are no other search solutions that
 natively leverage HDFS and the failover features of Hadoop in the same
 manner as the Blur project. The communities we expect to be most
 interested in such a project are government, health care, and other
 industries where scalability is a concern. We have made much progress
 in developing this project over the past 2 years and believe both the
 project and the interested communities would benefit from this work
 being openly available and having open development.  In future
 versions of Blur the API will more closely follow the API’s provided
 in Lucene so that systems that already use Lucene can more easily
 scale with Blur. Blur can be viewed as a query execution engine that
 Lucene based solutions can utilize when scale becomes an issue.

 == Initial Goals ==
 The initial goals of the project are:
  * To migrate the Blur codebase, issue tracking and wiki from
 github.com and integrate the project with the ASF infrastructure.
  * Add new committers to the project and grow the community in The Apache 
 Way.

 == Current Status ==

 === Meritocracy ===
 Blur was initially developed by Aaron !McCurry in June 2010.  Since
 then Blur has continued to evolve with the support of a small
 development team at Near Infinity.  As a part of the Apache Software
 Foundation, the Apache Blur team intends to strongly encourage the
 community to help with and contribute to the project.  Apache Blur
 will actively seek potential committers and help them become familiar
 with the codebase.

 === Community ===
 A small community has developed around Blur and several project teams
 are currently using Blur for their big data search capability. The
 source code is currently available on GitHub and there is a dedicated
 website (blur.io) that provides an overview of the project. Blur has
 been shared with several members of the Apache community and has been
 presented at the Bay Area HUG (see
 http://www.meetup.com/hadoop/events/20109471/).

 === Core Developers ===
 The current developers are employed by Near Infinity Corporation, but
 we anticipate interest developing among other companies.

 === Alignment ===
 Blur is built on top of a number of Apache projects; Hadoop, Lucene,
 !ZooKeeper, and Thrift. It builds with Maven.  During the course of
 Blur development, a couple of patches have been committed back to the
 Lucene project, including LUCENE-2205 and LUCENE-2215.  Due to the
 strong relationship with the before mentioned Apache projects, the
 incubator is a good match for Blur.

 == Known Risks ==

 === Orphaned Products ===
 There is only a small risk of being orphaned. The 

Re: [VOTE] Release Oozie 3.2.0-incubating (candidate 1)

[Tom White]

+1 I checked the signature and checksums, inspected the source tag,
ran a RAT report, checked the disclaimer, notice and license files.

Tom

On Fri, Jun 1, 2012 at 6:35 PM, Alejandro Abdelnur t...@cloudera.com wrote:
 Dear Incubator PMCs,

 Oozie Incubator community has voted on the Oozie 3.2.0-incubating release.

 The tally of the votes is:

 Results: 8 +1 votes, 0 -1 votes

  developers/users: 3 +1 (mona, jeremy, roman)
  committers: 4 +1 (harsh, virag, angelo, tucu)
  mentors: 1 +1 (alan)

 Below you'll find the email sent to the Oozie developer alias with the VOTE
 request. There you'll find the details of the release and where to download
 the release artifact.

 Vote closes on Monday JUN/04 17:00 PST.

 Thanks

 Alejandro

 -- Forwarded message --
 From: Alejandro Abdelnur t...@cloudera.com
 Date: Tue, May 29, 2012 at 3:23 PM
 Subject: [VOTE] Release Oozie 3.2.0-incubating (candidate 1)
 To: oozie-...@incubator.apache.org


 Dear Oozie community,

 The release candidate 1 for for Oozie 3.2.0-incubating is available.

 Changes from candidate 0:

 * removes native files and adds instructions on how to test Pipe
 * consolidate rat report
 * minor fix in the demo example


 Some of the new features are:

 * Hive action
 * Sqoop action
 * Shell action
 * Tool to create/upgrade database schema
 * Kerberos SPNEGO authentication
 * Proxy User capabilities for Oozie users
 * Job ACLs support
 * Improved Job information over HTTP REST API
 * Improved Workflow validation
 * Sharelib directories per action
 * EL functions for Workflow and Coordinator applications

 In addition it includes several improvements for performance and
 stability and several bug fixes.

 Keys used to sign the release are available at
 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.

 Please download, test, and try it out:

   http://people.apache.org/~tucu/oozie-3.2.0-incubating-candidate-1

 The release, md5 signature, gpg signature, and rat report can all be
 found at the above URL.

 Vote closes on Friday JUN/01 15:30 PST.

 Thanks

 --
 Alejandro

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Flume Graduation (was Re: June reports in two weeks)

[Tom White]

According to Clutch [1] the project has added 8 committers since it
entered incubation. Regarding diversity, committers from over four
organizations are actively involved in Flume development, which is
pretty healthy. There does seem to be a need to have more diversity at
the PPMC level, however, so that's something that could be worked on.

Tom

[1] http://incubator.apache.org/clutch.html

On Thu, May 24, 2012 at 2:06 PM, Dave Fisher dave2w...@comcast.net wrote:

 On May 24, 2012, at 11:49 AM, Ralph Goers wrote:


 On May 24, 2012, at 10:40 AM, Arvind Prabhakar wrote:

 Hi,

 On Thu, May 24, 2012 at 12:19 AM, Ralph Goers 
 ralph.go...@dslextreme.comwrote:

 The ONLY issue I see for Flume to graduate is diversity.  No one will
 convince me that the current makeup constitutes diversity of any kind.

 Perhaps I shouldn't have brought up the mailing list issues as that was
 only meant in the spirit of trying to offer some advice on how more
 diversity could be achieved.  Flume is really the only community I
 participate in that contains Cloudera employees so I do find myself
 wondering if the way the project is run is because that is the way all
 projects with a large number of Cloudera employees are run.  That might
 make all of those participants comfortable but might create a barrier to
 others.


 Here are the committers who have been active in the past three months:

 * Brock Noland (Cloudera)
 * Hari Shreedharan  (Cloudera)
 * Jarek Jarcec Cecho (AVG Technologies)
 * Juhani Connolly   (CyberAgent)
 * Mike Percy (Cloudera)
 * Mingjie Lai (Trend Micro)
 * Prasad Mujumdar (Cloudera)
 * Will McQueen (Cloudera)
 * Arvind Prabhakar (Cloudera)

 There are four companies represented in this list: AVG Technologies,
 Cloudera, CyberAgent and Trend Micro. Compared to other projects that have
 successfully graduated from Incubator in the past, this meets the diversity
 requirements very well.

 I was mistaken and the list above is indeed correct.  For some reason I 
 thought a couple of them had become Cloudera employees.

 However, none of those three are currently on the PPMC.  When you look at 
 the PPMC list you should also include a few more Cloudera people who do 
 participate in release votes and PPMC issues. Most, if not all, of the 
 non-Cloudera PMC members don't.

 I started reading some of the Flume website and I think that when you go to 
 the main Wiki page:

 https://cwiki.apache.org/confluence/display/FLUME/Index

 When you click on the Flume Cookbook the resource is at cloudera.org.

 http://archive.cloudera.com/cdh/3/flume/Cookbook/

 This page lists flume-...@cloudera.org and is a file with a revision dated 
 May 7, 2012.

 You can make you own conclusions, but it looks like podling resources need to 
 be migrated to the ASF.

 Regards,
 Dave







 In any case - I'm not insisting that the way the project is run needs to
 change. I'm simply saying I cannot support graduation with the current
 makeup of the committers and PMC. I don't have a hard and fast ratio -
 gaining 10 new unaffiliated committers who don't do much isn't nearly as
 good as 2 or 3 who are very active.  Ultimately the project needs to figure
 out how to solve this.


 Stating that some committers who don't do much isn't nearly as good as 2
 or 3 who are very active is an unfair characterization. This is more
 unfair for those who are part of the project but have not been active
 lately due to whatever reasons, but have played a foundational role in
 getting the project to a point where it is today. I think they are as
 important as any other committer who may be very active at the moment.
 Merit once earned, never expires [1].

 [1] http://www.apache.org/dev/committers.html#committer-set-term

 I think you misunderstood my point or I didn't state it very well.  
 Diversity isn't achieved simply by having bodies.  IOW I am not suggesting 
 offering commit rights to people who haven't earned it just to meet some 
 ratio.  However, I am not suggesting the project has ever even considered 
 doing that.

 Ralph



 -
 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] Graduate Apache MRUnit from Incubator

[Tom White]

+1 to graduate MRUnit.

Cheers,
Tom

On Thu, May 3, 2012 at 7:31 PM, Jim Donofrio donofrio...@gmail.com wrote:
 We havent heard anything +1 or -1 from any IPMC members besides our mentors.
 Any thoughts on this vote?

 We released 0.9.0-incubating on Tuesday so we have completed 4 releases and
 added 4 new commiters since the beginning of incubation

 To resummarize the current vote is below:


 7 +1's
 0 0's
 0 -1's

 IPMC +1
 Patrick Hunt
 Chris Mattmann

 PPMC +1
 Brock Noland
 Dave Beech
 Jim Donofrio
 Jarek Jarcec Cecho

 Others +1
 Joey Echeverria

 On 04/28/2012 12:11 PM, Mattmann, Chris A (388J) wrote:

 Hi Jim,

 Yep, we need more VOTEs than 2 (3 I believe, but it would be nice to have
 a bit more -- though not required). There's been a lot of traffic on
 general@incbuator
 lately so folks are probably just busy.

 I would wait until tonight or tomorrow and poll for some more VOTEs on the
 VOTE thread.

 Once we get the required VOTEs, you can close the VOTE, and I can add the
 resolution to
 the board agenda.

 Cheers,
 Chris

 On Apr 28, 2012, at 6:35 AM, Jim Donofrio wrote:

 How many IPMC votes are required for graduation?

 We got 2 IPMC votes so far from mentors but havent gotten any on the
 general@ list. Since the vote has been open for more than 72 hours, does
 this mean we cant graduate yet?


 On 04/23/2012 11:56 PM, Jim Donofrio wrote:

 We havent heard anything on the DISCUSS thread since posting it over 72
 hours ago so I am starting a VOTE thread following Chris Mattmann's
 recommendation. I will leave the vote open for 72 hours.

 The current vote is below copying from the community vote [2] that
 passed:

 7 +1's
 0 0's
 0 -1's

 IPMC +1
 Patrick Hunt
 Chris Mattmann

 PPMC +1
 Brock Noland
 Dave Beech
 Jim Donofrio
 Jarek Jarcec Cecho

 Others +1
 Joey Echeverria


 In the last MRUnit incubator report [1] the 3 blockers were:
 * Grow the community size and diversity
 * Make another incubating release
 * Construct an MRUnit website to replace the existing stub

 We have since:
 * Added 2 new committers/PPMC members
 * 0.9.0-incubating will get released soon, pending one more IPMC +1
 * We have a new website

  From the beginning of incubation we have:
 * Added 4 new committers/PPMC members
 * Done 4 releases once 0.9.0-incubating is released soon, pending one
 more IPMC +1
 * Created a real website

 [1]:

 http://incubator.apache.org/mrunit/ppmc/incubator_reports.html#march-2012
 [2]:

 http://mail-archives.apache.org/mod_mbox/incubator-mrunit-dev/201204.mbox/%3C4F91FED1.2010609%40gmail.com%3E


 X. Establish the Apache MRUnit Project

 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the
 Foundation's purpose to establish a Project Management
 Committee charged with the creation and maintenance of
 open-source software related to unit testing Apache Hadoop map
 reduce jobs for distribution at no charge to the public.

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the Apache MRUnit Project,
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further

 RESOLVED, that the Apache MRUnit Project be and hereby is
 responsible for the creation and maintenance of software
 related to unit testing Apache Hadoop map reduce jobs;
 and be it further

 RESOLVED, that the office of Vice President, Apache MRUnit 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 MRUnit Project, and to have primary responsibility
 for management of the projects within the scope of
 responsibility of the Apache MRUnit 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 MRUnit Project:

 * Brock Noland br...@apache.org
 * Patrick Hunt ph...@apache.org
 * Nigel Daley ni...@apache.org
 * Eric Sammer esam...@apache.org
 * Aaron Kimball kimba...@apache.org
 * Konstantin Boudnik c...@apache.org
 * Garrett Wu g...@apache.org
 * Jim Donofrio jdonof...@apache.org
 * Jarek Jarcec Cecho jar...@apache.org
 * Dave Beech dbe...@apache.org

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Brock Noland
 be appointed to the office of Vice President, Apache MRUnit, 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 MRUnit PMC be and hereby is
 tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache MRUnit Project; and be it further

 RESOLVED, that the Apache MRUnit Project be and hereby
 is tasked with the migration and rationalization of the Apache
 Incubator MRUnit podling; and be it further

 RESOLVED, that all 

Re: [VOTE] Release Apache Mesos 0.9.0-incubating (RC5)

[Tom White]

+1 checked checksums and signatures; license, notice, disclaimer and
svn tag all look correct.

Tom

On Thu, Apr 19, 2012 at 12:53 PM, Benjamin Hindman b...@berkeley.edu wrote:
 Please vote on releasing the following candidate as Apache Mesos
 (incubating) version 0.9.0. This will be the first incubator release for
 Mesos in Apache, but the sixth release candidate.

 Changes since RC4:
  * Updated NOTICE to include project name and copyright date as well as to
 include third-party licences.
  * Changed one of our third-party components to be included as an archive
 of it's source rather than a binary bundle (Python egg).
  * Added DISCLAIMER.

 The candidate for Mesos 0.9.0-incubating release is available at:

 http://people.apache.org/~benh/mesos-0.9.0-incubating-RC5/mesos-0.9.0-incubating.tar.gz

 The tag to be voted on:

 https://svn.apache.org/repos/asf/incubator/mesos/tags/release-0.9.0-incubating-RC5

 The MD5 checksum of the tarball can be found at:

 http://people.apache.org/~benh/mesos-0.9.0-incubating-RC5/mesos-0.9.0-incubating.tar.gz.md5

 The signature of the tarball can be found at:

 http://people.apache.org/~benh/mesos-0.9.0-incubating-RC5/mesos-0.9.0-incubating.tar.gz.asc

 Mesos' KEYS file, containing the PGP keys used to sign the release:
  http://svn.apache.org/repos/asf/incubator/mesos/dist/KEYS

 Please vote on releasing this package as Apache Mesos 0.9.0-incubating!

 The vote is open until Monday, April 23rd at 8 pm (a bit more than 72 hours
 since it's over the weekend) and passes if a majority of at least 3 +1 IPMC
 votes are cast.

 [ ] +1 Release this package as Apache Mesos 0.9.0-incubating
 [ ] -1 Do not release this package because ...

 To learn more about Apache Mesos, please see
 http://incubator.apache.org/mesos.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release MRUnit version 0.9.0-incubating-rc2

[Tom White]

+1 checked checksums, signatures, license/notice/disclaimer, svn tag.

Tom

On Wed, Apr 18, 2012 at 1:22 PM, Brock Noland br...@cloudera.com wrote:
 This is an incubator release for Apache MRUnit, version 0.9.0-incubating.

 It fixes the following issues:
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311292version=12316360

 *** Please download, test and vote by [3 working days after sending].

 Note that we are voting upon the source (tag), binaries are provided
 for convenience.

 Source and binary files:
 http://people.apache.org/~brock/mrunit-0.9.0-incubating-candidate-2/

 Maven staging repo:
 https://repository.apache.org/content/repositories/orgapachemrunit-070/

 The tag to be voted upon:
 http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/

 MRUnit's KEYS file containing PGP keys we use to sign the release:
 http://svn.apache.org/repos/asf/incubator/mrunit/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


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release MRUnit version 0.8.1-incubating

[Tom White]

+1

Verified checksums and signature, ran unit tests, checked license and
notice. I also successfully ran MRUnit tests against Hadoop 1.0 and
0.23 code.

Tom

On Fri, Feb 17, 2012 at 12:22 PM, Brock Noland br...@cloudera.com wrote:
 This is an incubator release for Apache MRUnit, version 0.8.1-incubating.

 It fixes the following issues:
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311292version=12319881

 *** Please download, test and vote by [3 working days after sending].

 Note that we are voting upon the source (tag), binaries are provided
 for convenience.

 Source and binary files:
 http://people.apache.org/~brock/mrunit-0.8.1-incubating-candidate-1/

 Maven staging repo:
 https://repository.apache.org/content/repositories/orgapachemrunit-022/

 The tag to be voted upon:
 http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.8.1-incubating/

 MRUnit's KEYS file containing PGP keys we use to sign the release:
 http://svn.apache.org/repos/asf/incubator/mrunit/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


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Sqoop version 1.4.1-incubating

[Tom White]

+1 Unpacked and ran the unit tests successfully. Checksums and
signature are good. RAT passes. LICENSE, NOTICE and DISCLAIMER look
ok.

Tom

On Fri, Feb 10, 2012 at 11:27 AM, Jarek Jarcec Cecho jar...@apache.org wrote:
 This is the second incubator release for Apache Sqoop, version 
 1.4.1-incubating.

 We already have one IPMC vote on dev list (Oliver Lamy) and we're looking for 
 additional two.

 *** Please cast your vote by 2012-02-14 ***

 Dev list vote thread:
 http://markmail.org/message/alpqeqwliq4xbbcc

 The list of fixed issues:
 http://svn.apache.org/repos/asf/incubator/sqoop/branches/branch-1.4.1/CHANGES.txt

 The tarball (*.tar.gz), signature (*.asc), checksum (*.md5),
 and test result (log/*.ant_test.log):
 http://people.apache.org/~jarcec/sqoop-1.4.1-incubating-rc3/

 The tag to be voted upon:
 http://svn.apache.org/repos/asf/incubator/sqoop/tags/release-1.4.1-rc3

 The KEYS file:
 http://www.apache.org/dist/incubator/sqoop/KEYS

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Sqoop version 1.4.0-incubating (with release candidate rc1)

[Tom White]

+1

Checked signatures/md5, ran RAT, tag looks good.

Cheers,
Tom

On Sun, Nov 20, 2011 at 11:40 PM, Bilung Lee b...@apache.org wrote:
 This will be the first incubator release for Apache Sqoop, version
 1.4.0-incubating.

 We got two IPMC votes from our dev list and are looking for a third.
  Thanks!

 *** Please cast the vote by November 23, 2011 ***

 Dev list vote result:
 http://markmail.org/message/jehsoo2vi6xboovu

 The list of fixed issues:
 http://svn.apache.org/repos/asf/incubator/sqoop/branches/branch-1.4.0/CHANGES.txt

 The tarball (*.tar.gz), signature (*.asc), checksum (*.md5), license audit
 result (log/*.ant_releaseaudit.log), and test result (log/*.ant_test.log):
 http://people.apache.org/~blee/sqoop-1.4.0-incubating-rc1/

 The tag to be voted upon:
 http://svn.apache.org/repos/asf/incubator/sqoop/tags/release-1.4.0-rc1

 The KEYS file:
 http://www.apache.org/dist/incubator/sqoop/KEYS


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release MRUnit version 0.5.0-incubating

[Tom White]

+1

Signatures and checksums look good. I could successfully build from
source. RAT ran cleanly.

Cheers,
Tom

On Fri, Nov 4, 2011 at 1:19 PM, Brock Noland br...@cloudera.com wrote:
 This is the first incubator release for Apache MRUnit, version
 0.5.0-incubating.

 It fixes the following issues:
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311292version=12316328

 *** Please download, test and vote by [3 working days after sending].

 Note that we are voting upon the source (tag), binaries are provided
 for convenience.

 Source and binary files:
 http://people.apache.org/~brock/mrunit-0.5.0-incubating-candidate-0

 Maven staging repo:
 https://repository.apache.org/content/repositories/orgapachemrunit-149/

 The tag to be voted upon:
 http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.5.0-incubating/

 MRUnit's KEYS file containing PGP keys we use to sign the release:
 http://svn.apache.org/repos/asf/incubator/mrunit/dist/KEYS

 -
 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 for Bigtop version 0.2.0-incubating RC2

[Tom White]

+1

I verified checksums and signature. NOTICE, LICENSE, and DISCLAIMER
files look good. I ran RAT and the files without licenses seem to be
test data.

Tom

On Fri, Nov 4, 2011 at 2:00 PM, Roman Shaposhnik r...@cloudera.com wrote:
 This takes care of Patrick's RAT concerns. From now on you can run RAT by:
  $ mvn -Prelease install
 at the top level of a project. This is THE only change between RC1 and RC2
 and given how cosmetic it is I'd like to think that all the existing
 +1 votes don't
 need to be recast. Please let me know if that's not the case.

 =
 This is the second incubator release for Apache Bigtop, version
 0.2.0-incubating.

 It fixes the following issues:
  https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317591projectId=12311420

 *** Please download, test, and vote by Saturday, November 5

 Note that we are voting on the source (tag): release-0.2.0-incubating-RC2

 Source tarball, checksums, signature:
    http://people.apache.org/~rvs/bigtop-0.2.0-incubating-RC2/

 The tag to be voted on:
   
 https://svn.apache.org/repos/asf/incubator/bigtop/tags/release-0.2.0-incubating-RC2/

 Bigtop's KEYS file, containing the PGP keys used to sign the release:
   http://svn.apache.org/repos/asf/incubator/bigtop/dist/KEYS

 Note that the Incubator PMC needs to vote on the release after a successful
 PPMC vote before any release can be made official.

 Thanks!

 -
 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 for Bigtop version 0.1.0-incubating RC2

[Tom White]

+1

I verified signatures and checksums, and ran RAT.

Cheers,
Tom

On Mon, Aug 22, 2011 at 11:07 AM, Andrew Bayer andrew.ba...@gmail.com wrote:
 This is the first incubator release for Apache Bigtop, version
 0.1.0-incubating.

 It fixes the following issues:
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317549styleName=HtmlprojectId=12311420

 *** Please download, test, and vote by Thursday, August 24 (3 working days
 from now)

 Note that we are voting on the source (tag).

 Source tarball, checksums, signature:
 http://people.apache.org/~abayer/bigtop-0.1.0-incubating-candidate-2/http://people.apache.org/~abayer/bigtop-0.1.0-incubating-candidate-0/

 The tag to be voted on:
 http://svn.apache.org/repos/asf/incubator/bigtop/tags/release-0.1.0-incubating-RC2
 (svn rev. 1160352)

 Bigtop's KEYS file, containing the PGP keys used to sign the release:
 http://svn.apache.org/repos/asf/incubator/bigtop/dist/KEYS

 Note that the Incubator PMC needs to vote on the release after a successful
 PPMC vote before any release can be made official.

 Thanks!

 A.


-
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

[Tom White]

+1

I checked signatures and checksums, ran RAT, and started a cluster.

Cheers,
Tom

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

Re: [VOTE][RESULT] Graduation of the Whirr Podling

[Tom White]

On Tue, Aug 9, 2011 at 12:44 AM, Robert Burrell Donkin
robertburrelldon...@gmail.com wrote:
 On Tue, Aug 9, 2011 at 8:28 AM, Tom White tomwh...@apache.org wrote:
 The vote passes, with 4 binding +1 votes (plus an additional two IPMC
 votes from the Whirr dev thread [1]), 1 non-binding +1 vote, no 0
 votes, and no -1 votes.

 The binding +1 votes:
 Chris A. Mattmann
 Mohammad Nour El-Din
 Doug Cutting
 Stefan Seelmann

 (Just for the record) I tried to cast another binding +1 vote using
 the boxes [1] (but on reflection I made it easy to miss by cluttering
 the VOTE thread with noise)

Sorry I missed that in the tally. Thanks for voting.

Cheers,
Tom


 Congratulations on graduation

 Robert

 http://mail-archives.apache.org/mod_mbox/incubator-general/201108.mbox/%3CCAKTa1mjReAgUj7Sqx2NJjCL3C49g0FTKWE4w4NzcPky+=go...@mail.gmail.com%3E

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Graduation of the Whirr Podling

[Tom White]

Hi everyone,

The Whirr podling joined the incubator in May 2010. Since then it has
made 5 releases following Apache guidelines, added 4 new committers,
and added 3 new PPMC members. The community is healthy and growing,
and we've shown an ability to self-govern using accepted Apache
practices.

The Whirr podling has now voted to graduate:

Vote: 
http://mail-archives.apache.org/mod_mbox/incubator-whirr-dev/201107.mbox/%3ccabqr8u_+mk8w_z-4vu-+9mwg+c+r4c1kmuhxa1drmulujnu...@mail.gmail.com%3E
Result: 
http://mail-archives.apache.org/mod_mbox/incubator-whirr-dev/201107.mbox/%3ccabqr8u8nttkqxjerp-txnn4jljrvqyrsrqxuesjiyq2td53...@mail.gmail.com%3E

The vote received 7 PPMC approvals, of which 3 were also IPMC members
(Patrick Hunt, Doug Cutting, and myself).

I would like to ask the IPMC to approve the graduation.

[  ] +1 - I approve of the Whirr graduation
[  ] +0 - I have no opinion
[  ] -1 - There's an issue with graduation at this time, which is

Voting will be open for 72 hours. Please find the proposed board
resolution below.

Thanks
Tom

## Resolution to create a TLP from graduating Incubator podling

X. Establish the Apache Whirr Project

   WHEREAS, the Board of Directors deems it to be in the best
   interests of the Foundation and consistent with the
   Foundation's purpose to establish a Project Management
   Committee charged with the creation and maintenance of
   open-source software related to running services on cloud
   infrastructure for distribution at no charge to the public.

   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the Apache Whirr Project,
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache Whirr Project be and hereby is
   responsible for the creation and maintenance of software
   related to running services on cloud infrastructure;
   and be it further

   RESOLVED, that the office of Vice President, Apache Whirr 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 Whirr Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache Whirr 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 Whirr Project:

 * Adrian Cole  adrianc...@apache.org
 * Lars George  larsgeo...@apache.org
 * Patrick Hunt ph...@apache.org
 * Tibor Kiss   ti...@apache.org
 * Johan Oskarsson  jo...@apache.org
 * Andrew Purtell   apurt...@apache.org
 * Andrei Savu  as...@apache.org
 * Tom Whitetomwh...@apache.org

   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tom White
   be appointed to the office of Vice President, Apache Whirr, 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 Whirr PMC be and hereby is
   tasked with the creation of a set of bylaws intended to
   encourage open development and increased participation in the
   Apache Whirr Project; and be it further

   RESOLVED, that the Apache Whirr Project be and hereby
   is tasked with the migration and rationalization of the Apache
   Incubator Whirr podling; and be it further

   RESOLVED, that all responsibilities pertaining to the Apache
   Incubator Whirr podling encumbered upon the Apache Incubator
   Project are hereafter discharged.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Oozie to join the Incubator

[Tom White]

+1

Tom

On Wed, Jun 29, 2011 at 8:10 PM, Mohammad Islam misla...@yahoo.com wrote:
 Hi All,

 The discussion about Oozie proposal is settling down. Therefore I would like 
 to
 initiate a vote to accept Oozie as an Apache Incubator project.

 The latest proposal is pasted at the end and it could be found in the wiki as
 well:

 http://wiki.apache.org/incubator/OozieProposal


 The related discussion thread is at:
 http://www.mail-archive.com/general@incubator.apache.org/msg29633.html


 Please cast your votes:

 [  ] +1 Accept Oozie for incubation
 [  ] +0 Indifferent to Oozie incubation
 [  ] -1 Reject Oozie for incubation

 This vote will close 72 hours  from now.

 Regards,
 Mohammad


 Abstract
 Oozie is a server-based workflow scheduling and coordination system to manage
 data processing jobs for Apache HadoopTM.

 Proposal
 Oozie is an  extensible, scalable and reliable system to define, manage,
 schedule,  and execute complex Hadoop workloads via web services. More
 specifically, this includes:

        * XML-based declarative framework to specify a job or a complex 
 workflow of
 dependent jobs.

        * Support different types of job such as Hadoop Map-Reduce, Pipe, 
 Streaming,
 Pig, Hive and custom java applications.

        * Workflow scheduling based on frequency and/or data availability.
        * Monitoring capability, automatic retry and failure handing of jobs.
        * Extensible and pluggable architecture to allow arbitrary grid 
 programming
 paradigms.

        * Authentication, authorization, and capacity-aware load throttling to 
 allow
 multi-tenant software as a service.

 Background
 Most data  processing applications require multiple jobs to achieve their 
 goals,
 with inherent dependencies among the jobs. A dependency could be  sequential,
 where one job can only start after another job has finished.  Or it could be
 conditional, where the execution of a job depends on the  return value or 
 status
 of another job. In other cases, parallel  execution of multiple jobs may be
 permitted – or desired – to exploit  the massive pool of compute nodes 
 provided
 by Hadoop.

 These  job dependencies are often expressed as a Directed Acyclic Graph, also
 called a workflow. A node in the workflow is typically a job (a  computation 
 on
 the grid) or another type of action such as an eMail  notification. 
 Computations
 can be expressed in map/reduce, Pig, Hive or  any other programming paradigm
 available on the grid. Edges of the graph  represent transitions from one node
 to the next, as the execution of a  workflow proceeds.

 Describing  a workflow in a declarative way has the advantage of decoupling 
 job
 dependencies and execution control from application logic. Furthermore,  the
 workflow is modularized into jobs that can be reused within the same  workflow
 or across different workflows. Execution of the workflow is  then driven by a
 runtime system without understanding the application  logic of the jobs. This
 runtime system specializes in reliable and  predictable execution: It can 
 retry
 actions that have failed or invoke a  cleanup action after termination of the
 workflow; it can monitor  progress, success, or failure of a workflow, and 
 send
 appropriate alerts  to an administrator. The application developer is relieved
 from  implementing these generic procedures.

 Furthermore,  some applications or workflows need to run in periodic intervals
 or  when dependent data is available. For example, a workflow could be  
 executed
 every day as soon as output data from the previous 24 instances  of another,
 hourly workflow is available. The workflow coordinator  provides such 
 scheduling
 features, along with prioritization, load  balancing and throttling to 
 optimize
 utilization of resources in the  cluster. This makes it easier to maintain,
 control, and coordinate  complex data applications.

 Nearly  three years ago, a team of Yahoo! developers addressed these critical
 requirements for Hadoop-based data processing systems by developing a  new
 workflow management and scheduling system called Oozie. While it was  
 initially
 developed as a Yahoo!-internal project, it was designed and  implemented with
 the intention of open-sourcing. Oozie was released as a GitHub project in 
 early
 2010. Oozie is used in production within Yahoo and  since it has been
 open-sourced it has been gaining adoption with  external developers

 Rationale
 Commonly,  applications that run on Hadoop require multiple Hadoop jobs in 
 order
 to  obtain the desired results. Furthermore, these Hadoop jobs are commonly  a
 combination of Java map-reduce jobs, Streaming map-reduce jobs, Pipes
 map-reduce jobs, Pig jobs, Hive jobs, HDFS operations, Java programs  and 
 shell
 scripts.

 Because  of this, developers find themselves writing ad-hoc glue programs to
 combine these Hadoop jobs. These ad-hoc programs are difficult to  schedule,
 manage, monitor and recover.

 Workflow  

[VOTE][RESULT] Accept Bigtop for incubation

[Tom White]

The 72 hour voting period has elapsed, and the vote has passed, with
19 +1 votes (12 binding), no -1 votes, and no 0 votes.

Binding votes (IPMC members):

Chris A. Mattmann
Leif Hedstrom
Patrick Hunt
Ralph Goers
Michael McCandless
Robert Burrell Donkin
Nigel Daley
Tom White
Mohammad Nour El-Din
Ian Holsman
Alan Gates
Doug Cutting

Non-binding votes:

Ashish
Eli Collins
Arvind Prabhakar
Eric Sammer
Paul Zimdars
Edward J. Yoon
Eric Charles

Thanks to everyone who voted.

Cheers,
Tom

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Bigtop for incubation

[Tom White]

+1

Tom

On Fri, Jun 17, 2011 at 10:15 AM, Tom White tomwh...@apache.org wrote:
 As there are no active discussions on the proposal thread, I would
 like to initiate a vote to accept Bigtop as an Apache Incubator
 project.

 The proposal is available at

 http://wiki.apache.org/incubator/BigtopProposal?action=recallrev=13

 I've also put a copy of the proposal at the end of this email.

 The discussion thread is available at

 http://mail-archives.apache.org/mod_mbox/incubator-general/201106.mbox/%3cbanlktimriyvs5g5maklqvinauz9h6s5...@mail.gmail.com%3E

 Please cast your votes:

 [  ] +1 Accept Bigtop for incubation
 [  ] +0 Indifferent to Bigtop incubation
 [  ] -1 Reject Bigtop for incubation

 This vote will close 72 hours from now.

 Thanks,
 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, Hama
 and Sqoop.

 From a packaging and deployment perspective, the current
 loosely-coupled nature of the project has limitations:
  1. Insufficient building against trunk versions of dependent projects
 (in the style of Apache Gump).
  1. Insufficient testing against the trunk versions of dependent projects.
  1. No consistent packaging for the Linux servers which provide the
 main Hadoop datacenter platform.
  1. No functional testing against multi-machine clusters as part of
 the regular automated build process. This is due to a lack of a
 physical or virtual Hadoop cluster for testing, and not enough test
 suites designed to run against a live cluster with known datasets.

 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 and Konstantin Boudnik designed and implemented
 the system testing framework.

 Many of the committers to the Bigtop project have contributed towards

[VOTE] Accept Bigtop for incubation

[Tom White]

As there are no active discussions on the proposal thread, I would
like to initiate a vote to accept Bigtop as an Apache Incubator
project.

The proposal is available at

http://wiki.apache.org/incubator/BigtopProposal?action=recallrev=13

I've also put a copy of the proposal at the end of this email.

The discussion thread is available at

http://mail-archives.apache.org/mod_mbox/incubator-general/201106.mbox/%3cbanlktimriyvs5g5maklqvinauz9h6s5...@mail.gmail.com%3E

Please cast your votes:

[  ] +1 Accept Bigtop for incubation
[  ] +0 Indifferent to Bigtop incubation
[  ] -1 Reject Bigtop for incubation

This vote will close 72 hours from now.

Thanks,
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, Hama
and Sqoop.

From a packaging and deployment perspective, the current
loosely-coupled nature of the project has limitations:
 1. Insufficient building against trunk versions of dependent projects
(in the style of Apache Gump).
 1. Insufficient testing against the trunk versions of dependent projects.
 1. No consistent packaging for the Linux servers which provide the
main Hadoop datacenter platform.
 1. No functional testing against multi-machine clusters as part of
the regular automated build process. This is due to a lack of a
physical or virtual Hadoop cluster for testing, and not enough test
suites designed to run against a live cluster with known datasets.

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 and Konstantin Boudnik 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, Konstantin
Boudnik, Eli Collins, Alan Gates, Patrick Hunt, Steve Loughran, Owen
O'Malley, John Sichi, Michael Stack, Tom White

Re: [PROPOSAL] Bigtop for the Apache Incubator

[Tom White]

Owen,

Thanks for offering to help out.

Cheers,
Tom

On Thu, Jun 16, 2011 at 7:13 AM, Owen O'Malley omal...@apache.org wrote:
 On Mon, Jun 13, 2011 at 9:26 PM, 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.


 I'd like to join as a committer and mentor.

 -- Owen


-
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

[Tom White]

Alan Gates has volunteered to be a committer and mentor, so I added
him to the proposal. (For some reason his email to this list didn't
come through.)

Thanks Alan!

Tom

On Mon, Jun 13, 2011 at 9:26 PM, 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 will complement these projects (Hadoop,
 Pig, Hive, HBase, etc...) by providing an environment for contributors
 interested in building more complex data processing pipelines to work
 together integrating more than a single project into a well tested
 whole.

 = Known Risks =

 == Orphaned Products

Re: [PROPOSAL] Bigtop for the Apache Incubator

[Tom White]

Edward, Andrei - thanks for volunteering to help out as initial
committers. Please add your names to the proposal on the wiki.

Cheers,
Tom

On Wed, Jun 15, 2011 at 6:15 AM, Andrei Savu as...@apache.org wrote:
 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

Re: [PROPOSAL] Bigtop for the Apache Incubator

[Tom White]

Steve,

Thanks for signing up.

Bigtop should not maintain branches or patchsets on top of upstream
projects. Any bugs or compatibility problems that are found will need
to be resolved in the upstream projects and then released in those
projects. This makes things harder for Bigtop, but, like you, I hope
having committers from the upstream projects involved in Bigtop will
give projects further impetus to make releases in a timely manner.

Cheers,
Tom

On Tue, Jun 14, 2011 at 4:51 AM, Steve Loughran ste...@apache.org wrote:
 I've added more on the limitations of the current process (not synchronised
 releases, not enough automated testing on multiple-host clusters), and on a
 risk of the project: the upstream projects need to care about and work on
 more synchronized releases.

 Cloudera managed to address that problem by patching their forks of the
 apache projects, then push back the patches by way of JIRA patches. Bigtop
 should not get into the game of having its own branches of any of the ASF
 projects, instead it should focus on getting its changes into trunk of the
 various projects SVN trees, and on having near-synchronized releases of the
 various projects

 That requires
  -engagement from the committer teams to get patches in. Having committers
 from the relevant projects in the BigTop project would address this.
  -support from the PMCs to do releases on a regular schedule. That's hard,
 but something like a six-monthly schedule for the big projects with the up
 and coming projects releasing in a proper factor of that timescale (3, 2, 1
 month), could help.

 -
 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

[PROPOSAL] Bigtop for the Apache Incubator

[Tom White]

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 will complement these projects (Hadoop,
Pig, Hive, HBase, etc...) by providing an environment for contributors
interested in building more complex data processing pipelines to work
together integrating more than a single project into a well tested
whole.

= Known Risks =

== Orphaned Products ==

The contributors are leading vendors of Hadoop-based technologies and
have a long standing in the Hadoop community. There is minimal risk of
this work becoming non-strategic and the contributors are confident
that a larger community will form within the project in a relatively
short space of time.

== Inexperience with Open Source

Re: [VOTE] Flume to join the Incubator.

[Tom White]

.  Furthermore, Flume provides a more general model for
 handling data and enables integration with projects such as Apache Hive,
 data stores such as Apache HBase, Apache Cassandra and Voldemort, and
 several Apache Lucene-related projects.

 == An Excessive Fascination with the Apache Brand ==

 We would like Flume to become an Apache project to further foster a healthy
 community of contributors and consumers around the project.  Since Flume
 directly interacts with many Apache Hadoop-related projects by solves an
 important problem of many Hadoop users, residing in the Apache Software
 Foundation will increase interaction with the larger community.

 = Documentation =

  * All Flume documentation (User Guide, Developer Guide, Cookbook, and
 Windows Guide) is maintained within Flume sources and can be built directly.
  * Cloudera provides documentation specific to its distribution of Flume at:
 http://archive.cloudera.com/cdh/3/flume/
  * Flume wiki at GitHub: https://github.com/cloudera/flume/wiki
  * Flume jira at Cloudera: https://issues.cloudera.org/browse/flume

 = Initial Source =

  * https://github.com/cloudera/flume/tree/

 == Source and Intellectual Property Submission Plan ==

  * The initial source is already licensed under the Apache License, Version
 2.0. https://github.com/cloudera/flume/blob/master/LICENSE

 == External Dependencies ==

 The required external dependencies are all Apache License or compatible
 licenses. Following components with non-Apache licenses are enumerated:

  * org.arabidopsis.ahocorasick : BSD-style

 Non-Apache build tools that are used by Flume are as follows:

  * AsciiDoc: GNU GPLv2
  * FindBugs: GNU LGPL
  * Cobertura: GNU GPLv2
  * PMD : BSD-style

 == Cryptography ==

 Flume uses standard APIs and tools for SSH and SSL communication where
 necessary.

 = Required  Resources =

 == Mailing lists ==

  * flume-private (with moderated subscriptions)
  * flume-dev
  * flume-commits
  * flume-user

 == Subversion Directory ==

 https://svn.apache.org/repos/asf/incubator/flume

 == Issue Tracking ==

 JIRA Flume (FLUME)

 == Other Resources ==

 The existing code already has unit and integration tests so we would like a
 Jenkins instance to run them whenever a new patch is submitted. This can be
 added after project creation.

 = Initial Committers =

  * Andrew Bayer (abayer at cloudera dot com)
  * Jonathan Hsieh (jon at cloudera dot com)
  * Patrick Hunt (phunt at cloudera dot com)
  * Aaron Kimball (akimball83 at gmail dot com)
  * Bruce Mitchener (bruce.mitchener at gmail dot com)
  * Arvind Prabhakar (arvind at cloudera dot com)
  * Ahmed Radwan (ahmed at cloudera dot com)
  * Henry Robinson (henry at cloudera dot com)
  * Eric Sammer (esammer at cloudera dot com)
  * Derek Deeter (ddeeterctrb at gmail dot com)

 = Affiliations =

  * Andrew Bayer, Cloudera
  * Jonathan Hsieh, Cloudera
  * Patrick Hunt, Cloudera
  * Aaron Kimball, Odiago
  * Bruce Mitchener, Independent
  * Arvind Prabhakar, Cloudera
  * Ahmed Radwan, Cloudera
  * Henry Robinson, Cloudera
  * Eric Sammer, Cloudera
  * Derek Deeter, Intuit


 = Sponsors =

 == Champion ==

  * Nigel Daley

 == Nominated Mentors ==

  * Tom White
  * Nigel Daley
  * Ralph Goers
  * Patrick Hunt

 == Sponsoring Entity ==

  * Apache Incubator PMC


 --
 // Jonathan Hsieh (shay)
 // Software Engineer, Cloudera
 // j...@cloudera.com


-
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.5.0-incubating (candidate 1)

[Tom White]

This vote has now passed with 3 binding +1s (2 from the dev list
vote), no +0's, and no -1's.

The binding votes were:

Stefan Seelmann, +1
Doug Cutting, +1 (on dev vote thread)
Tom White, +1 (on dev vote thread)

The non-binding votes (including those from the dev list vote) were as follows:

Andrei Savu, +1
Patrick Hunt, +0
Lars George, +1
Adrian Cole, +1
Johan Oskarsson, +1
Tibor Kiss, +1

I'll push the artifacts out.

Thanks to everyone who voted!

Cheers,
Tom

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Whirr version 0.5.0-incubating (candidate 1)

[Tom White]

Please vote on the following release candidate for Apache Whirr,
version 0.5.0-incubating. We already received two binding IPMC +1
votes for the PPMC release vote on whirr-dev.

PPMC release vote thread:
http://mail-archives.apache.org/mod_mbox/incubator-whirr-dev/201105.mbox/%3cbanlktimd_d7ar611s46w6_bh6anuy78...@mail.gmail.com%3E

It fixes the following issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12316248styleName=HtmlprojectId=1230

Note that we are voting upon the source (tag), binaries are provided
for convenience.

Source and binary files:
http://people.apache.org/~tomwhite/whirr-0.5.0-incubating-candidate-1

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachewhirr-012

The tag to be voted upon:
http://svn.apache.org/repos/asf/incubator/whirr/tags/release-0.5.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,
Tom

-
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

[Tom White]

On Fri, Mar 18, 2011 at 6:28 PM, sebb seb...@gmail.com wrote:
 On 18 March 2011 22:02, Tom White tom.e.wh...@gmail.com wrote:
 On Fri, Mar 18, 2011 at 10:30 AM, 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.

 Right, we definitely need to fix this, per
 http://incubator.apache.org/guides/releasemanagement.html#best-practice-license.


 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.

 Both products are present (jsr250-api-1.0.jar and jersey-core-1.4.jar)

 Sorry, it was not clear - I was referring to the source tarball, which
 does not contain any 3rd party libraries.

 and these are the only ones that contain required attributions (as far
 as I can tell). So I believe the NOTICE file is correct.

 It may be for the binary release, but if it is decided to release
 source only, it is not correct.

Whirr can't be used without these libraries, so it seems relevant to
include references to them in NOTICE. Or are you suggesting a
different NOTICE file for each distribution?

I've made all the other changes that you and Stefan suggested for the
next release candidate.

Thanks,
Tom



 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.

 It looks like the old LICENSE files in lib were mistakenly not removed
 when the JAR versions were updated (e.g. guava-r06-LICENSE.txt -
 guava-r08-LICENSE.txt) or removed since the last release. I agree this
 is confusing and they should be removed.

 Thanks for taking the time to check the release candidate.

 Cheers,
 Tom


 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

Re: [VOTE] Release Whirr version 0.4.0-incubating

[Tom White]

On Fri, Mar 18, 2011 at 10:30 AM, 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.

Right, we definitely need to fix this, per
http://incubator.apache.org/guides/releasemanagement.html#best-practice-license.


 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.

Both products are present (jsr250-api-1.0.jar and jersey-core-1.4.jar)
and these are the only ones that contain required attributions (as far
as I can tell). So I believe the NOTICE file is correct.


 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.

It looks like the old LICENSE files in lib were mistakenly not removed
when the JAR versions were updated (e.g. guava-r06-LICENSE.txt -
guava-r08-LICENSE.txt) or removed since the last release. I agree this
is confusing and they should be removed.

Thanks for taking the time to check the release candidate.

Cheers,
Tom


 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

Re: [VOTE] Release Whirr version 0.3.0-incubating

[Tom White]

With 3 +1's (binding votes from Doug Cutting and Tom White were made
on the whirr-dev vote thread) and no -1's the vote passes. I'll roll
out the release.

Thanks,
Tom

On Thu, Jan 27, 2011 at 1:04 PM, Steve Loughran ste...@apache.org wrote:
 On 26/01/2011 05:30, Tom White wrote:

 This is the third incubator release for Apache Whirr, version
 0.3.0-incubating. We already received one binding IPMC +1 vote for the
 PPMC release vote on whirr-dev, so are looking for two more.

 The vote is open for 72 hours.


 +1

 Ship it! Steve

 -
 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.3.0-incubating

[Tom White]

This is the third incubator release for Apache Whirr, version
0.3.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/201101.mbox/%3caanlktikdg83pbi+71pj0zcxs7pe_rs4musfavcwnx...@mail.gmail.com%3E

The issues fixed for 0.3.0-incubating
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315487styleName=HtmlprojectId=1230

Source and binary files:
http://people.apache.org/~tomwhite/whirr-0.3.0-incubating-candidate-0

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachewhirr-065

The tag to be voted upon:
http://svn.apache.org/repos/asf/incubator/whirr/tags/release-0.3.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,
Tom

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Mesos Project

[Tom White]

Thanks David. I think we can run a separate vote thread once this
proposal thread has run its course. Other recent proposal threads seem
to have general votes of support on them. As you say, this phase is a
time to respond to any questions that are raised, attract more
mentors, and so on.

Cheers,
Tom

On Wed, Dec 15, 2010 at 4:12 PM, David Crossley cross...@apache.org wrote:
 David Crossley wrote:
 The Proposal phase is for discussing the proposal,
 encouraging people, attracting mentors, ensuring that
 the proposal is ready.

 Then the Vote phase is for voting.

 Dunno what to do now that it has started :-)
 They gather steam, and we don't want to re-do it.

 Perhaps add Vote to the subject line and declare
 the end time, then tally everything at the end.

 -David

 -
 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 Gora into the Apache Incubator

[Tom White]

://code.google.com/p/guava-libraries/ -
 Apache License 2.0

 Required Resources
 Mailing Lists
 * gora-private (with moderated subscriptions)
 * gora-dev
 * gora-commits
 Subversion Directory
 * http://svn.apache.org/repos/asf/incubator/gora

 Issue Tracking
 * JIRA (GORA)
 Other Resources
 We need a wiki at http://wiki.apache.org. Currently, we have a wiki at
 Github, Since there is not a lot of pages there, we can manually move the
 pages to the wiki at wiki.apache.org.

 Initial Committers
 *    Name         email                  Affiliation   Timezone
 *    Enis Söztutar      enis [at] apache.org         Konneka             +3
 *    Doğacan Güney      dogacan [at] apache.org      Konneka             +3
 *    Sertan Alkan       sertanalkan [at] gmail.com   Konneka             +3
 *    Julien Nioche      jnioche [at] apache.org      DigitalPebble
 http://wiki.apache.org/incubator/DigitalPebble        +1
 *    Andrzej Bialecki   ab [at] apache.org           Sigram
 *    Andrew Hart        ahart [at] apache.org        NASA JPL            -8
 *    Dave Woollard      woollard [at] apache.org     NASA JPL            -8
 *    Henry Saputra      hsaputra [at] apache.org     Yahoo!              -8

  Affiliations
  All of the parties are affiliated with companies and organizations that are
  familiar with the development of open source . Most of the original Gora
  development was sponsored by ant.com, however we expect that the amount of
  volunteer work will increase, and more developers will come on board.

  Sponsors
  Champion
  * Chris Mattmann (mattmann AT apache DOT org)
  Nominated Mentors
  * Chris Mattmann (mattmann AT apache DOT org)
  * Andrzej Bialecki (ab AT apache DOT org )
  * Tom White (tomwhite AT apache DOT org)
  Sponsoring Entity
  Apache Incubator. Successful graduation can result in either being a TLP,
 or a subproject of  Hadoop, since most of the community is projected to
 overlap.

 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.mattm...@jpl.nasa.gov
 WWW:   http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++




-
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.1.0-incubating

[Tom White]

With 3 binding +1 IPMC votes (Ant Elder, Doug Cutting, and Tom White)
and no 0 or -1 votes, the vote passes. I'll proceed with the final
steps of the release.

Thanks to everyone who helped with the release!

Tom

BTW I've opened https://issues.apache.org/jira/browse/WHIRR-91 to
address the improvements that Ant raised for the next release.

On Tue, Sep 14, 2010 at 11:19 AM, Tom White tomwh...@apache.org wrote:
 This is the first incubator release for Apache Whirr, version
 0.1.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/201009.mbox/%3caanlktinio1np6d+gbnm4w6jjcg-6koe7x8begkuxr...@mail.gmail.com%3e

 The issues fixed for 0.1.0-incubating
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315111styleName=HtmlprojectId=1230

 Source and binary files:
 http://people.apache.org/~tomwhite/whirr-releases/

 Maven staging repo:
 https://repository.apache.org/content/repositories/orgapachewhirr-009

 The tag to be voted upon:
 http://svn.apache.org/repos/asf/incubator/whirr/tags/release-0.1.0-incubating

 The vote is open for 72 hours.

 [ ] +1
 [ ] +0
 [ ] -1

 Thanks,
 Tom


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Gora to enter Incubator

[Tom White]

I posted a little earlier volunteering to be a mentor, but it looks
like it may be in the moderation queue. Anyway, +1 to the proposal,
and happy to help out if you still need a mentor.

Cheers,
Tom

On Tue, Sep 14, 2010 at 2:44 PM, Mattmann, Chris A (388J)
chris.a.mattm...@jpl.nasa.gov wrote:
 Hi Folks,

 FYI, if any mentors out there have free cycles and are interested, we are 
 looking for 1 more mentor to fulfill the Incubator mentor requirements.

 Thanks,
 Chris



 On 9/13/10 6:10 AM, Enis Soztutar enis.soz.nu...@gmail.com wrote:

 Hi all,

 We would like to announce the Proposal for Gora, an ORM for Colum Stores,
 for the Apache Incubation. We believe that Gora can find a nice home at
 Apache.

 Wiki of the proposal can be found at
 http://wiki.apache.org/incubator/GoraProposal

 The proposal is as below.


 = Gora Proposal for Apache Incubation =

 == Abstract ==
 Gora is an ORM framework for column stores such as Apache HBase and Apache
 Cassandra with a specific focus on Hadoop.

 == Proposal ==
 Although there are various excellent ORM frameworks for relational
 databases, data modeling in NoSQL data stores differ profoundly from their
 relational cousins. Moreover, data-model agnostic frameworks such as JDO are
 not sufficient for use cases, where one needs to use the full power of the
 data models in column stores. Gora fills this gap by giving the user an
 easy-to-use ORM framework with data store specific mappings and built in
 Apache Hadoop support.

 The overall goal for Gora is to become the standard data representation and
 persistence framework for big data. The roadmap of Gora can be grouped as
 follows.

  * Data Persistence : Persisting objects to Column stores such as HBase,
 Cassandra, Hypertable; key-value stores such as Voldermort, Redis, etc; SQL
 databases, such as MySQL, HSQLDB, flat files in local file system of Hadoop
 HDFS.
  * Data Access : An easy to use Java-friendly common API for accessing the
 data regardless of its location.
  * Indexing : Persisting objects to Lucene and Solr indexes,
 accessing/querying the data with Gora API.
  * Analysis : Accesing the data and making analysis through adapters for
 Apache Pig, Apache Hive and Cascading
  * MapReduce support : Out-of-the-box and extensive MapReduce (Apache
 Hadoop) support for data in the data store.

 == Background ==
 ORM stands for Object Relation Mapping. It is a technology which abstacts
 the persistency layer
 (mostly Relational Databases) so that plain domain level objects can be
 used, without the cumbersome effort to save/load the data to and from the
 database. Gora differs from current solutions in that:
  * Gora is specially focussed at NoSQL data stores, but also has limited
 support for SQL databases
  * The main use case for Gora is to access/analyze big data using Hadoop.
  * Gora uses Avro for bean definition, not byte code enhancement or
 annotations
  * Object-to-data store mappings are backend specific, so that full data
 model can be utilized.
  * Gora is simple since it ignores complex SQL mappings
  * Gora will support persistence, indexing and anaysis of data, using Pig,
 Lucene, Hive, etc

 == Rationale ==
 ORM frameworks are nothing new. But with the explosion of data generated in
 Terabytes and even Petabytes, NoSQL data stores are gaining ever-increasing
 popularity. Coupled with limited support to already-proven Apache Hadoop
 support in current ORM frameworks, there was a need for a new project.

 Gora is currently hosted at Github. However, Gora has ties to ASF in many
 ways. As detailed in the proposal section, Gora will be a high level client
 for many Apache projects and subprojects including Hadoop(common, hdfs, and
 mapreduce), HBase, Cassandra, Avro, Lucene, Solr, Pig, and Hive. Gora
 already uses Hadoop, HBase, Cassandra and Avro. Moreover, Gora started its
 life inside Apache Nutch project, and now Nutch trunk uses Gora as a
 library. Even more, the initial set of committers are all ASF members.
 Therefore, we think that Apache will be an excellent home for Gora.

 == Initial Goals ==
 Initial goals for Gora can be summarized as:
  * Iron out the remaining issues with HBase, Cassandra and SQL support.
  * Make the first release before the end of the year.
  * Improve documentation
  * Support for Cascading

 == Current Status ==
 === Meritocracy ===
 Current commit rights belong to the initial list of committers four of who
 are also ASF members. All the developers have extensive experience with
 Apache projects. We honor the meritocracy policy of ASF foundation.

 === Community ===
 Gora’s community mostly overlap with that of Nutch, Hadoop, HBase, Avro and
 Cassandra. We
 have a small community for now (5 initial committers, 18 people tracking the
 project at Github), but have been piggybacking the Nutch community for a
 while. If Gora is accepted to Apache Incubator, we expect more traction.
 Moreover, with the increasing popularity of NoSQL databases, we expect more
 

Re: [PROPOSAL] Gora to enter Incubator

[Tom White]

+1 Sounds very interesting. I'd be happy to help out as a mentor.

Cheers,
Tom

On Mon, Sep 13, 2010 at 6:10 AM, Enis Soztutar enis.soz.nu...@gmail.com wrote:
 Hi all,

 We would like to announce the Proposal for Gora, an ORM for Colum Stores,
 for the Apache Incubation. We believe that Gora can find a nice home at
 Apache.

 Wiki of the proposal can be found at
 http://wiki.apache.org/incubator/GoraProposal

 The proposal is as below.


 = Gora Proposal for Apache Incubation =

 == Abstract ==
 Gora is an ORM framework for column stores such as Apache HBase and Apache
 Cassandra with a specific focus on Hadoop.

 == Proposal ==
 Although there are various excellent ORM frameworks for relational
 databases, data modeling in NoSQL data stores differ profoundly from their
 relational cousins. Moreover, data-model agnostic frameworks such as JDO are
 not sufficient for use cases, where one needs to use the full power of the
 data models in column stores. Gora fills this gap by giving the user an
 easy-to-use ORM framework with data store specific mappings and built in
 Apache Hadoop support.

 The overall goal for Gora is to become the standard data representation and
 persistence framework for big data. The roadmap of Gora can be grouped as
 follows.

  * Data Persistence : Persisting objects to Column stores such as HBase,
 Cassandra, Hypertable; key-value stores such as Voldermort, Redis, etc; SQL
 databases, such as MySQL, HSQLDB, flat files in local file system of Hadoop
 HDFS.
  * Data Access : An easy to use Java-friendly common API for accessing the
 data regardless of its location.
  * Indexing : Persisting objects to Lucene and Solr indexes,
 accessing/querying the data with Gora API.
  * Analysis : Accesing the data and making analysis through adapters for
 Apache Pig, Apache Hive and Cascading
  * MapReduce support : Out-of-the-box and extensive MapReduce (Apache
 Hadoop) support for data in the data store.

 == Background ==
 ORM stands for Object Relation Mapping. It is a technology which abstacts
 the persistency layer
 (mostly Relational Databases) so that plain domain level objects can be
 used, without the cumbersome effort to save/load the data to and from the
 database. Gora differs from current solutions in that:
  * Gora is specially focussed at NoSQL data stores, but also has limited
 support for SQL databases
  * The main use case for Gora is to access/analyze big data using Hadoop.
  * Gora uses Avro for bean definition, not byte code enhancement or
 annotations
  * Object-to-data store mappings are backend specific, so that full data
 model can be utilized.
  * Gora is simple since it ignores complex SQL mappings
  * Gora will support persistence, indexing and anaysis of data, using Pig,
 Lucene, Hive, etc

 == Rationale ==
 ORM frameworks are nothing new. But with the explosion of data generated in
 Terabytes and even Petabytes, NoSQL data stores are gaining ever-increasing
 popularity. Coupled with limited support to already-proven Apache Hadoop
 support in current ORM frameworks, there was a need for a new project.

 Gora is currently hosted at Github. However, Gora has ties to ASF in many
 ways. As detailed in the proposal section, Gora will be a high level client
 for many Apache projects and subprojects including Hadoop(common, hdfs, and
 mapreduce), HBase, Cassandra, Avro, Lucene, Solr, Pig, and Hive. Gora
 already uses Hadoop, HBase, Cassandra and Avro. Moreover, Gora started its
 life inside Apache Nutch project, and now Nutch trunk uses Gora as a
 library. Even more, the initial set of committers are all ASF members.
 Therefore, we think that Apache will be an excellent home for Gora.

 == Initial Goals ==
 Initial goals for Gora can be summarized as:
  * Iron out the remaining issues with HBase, Cassandra and SQL support.
  * Make the first release before the end of the year.
  * Improve documentation
  * Support for Cascading

 == Current Status ==
 === Meritocracy ===
 Current commit rights belong to the initial list of committers four of who
 are also ASF members. All the developers have extensive experience with
 Apache projects. We honor the meritocracy policy of ASF foundation.

 === Community ===
 Gora’s community mostly overlap with that of Nutch, Hadoop, HBase, Avro and
 Cassandra. We
 have a small community for now (5 initial committers, 18 people tracking the
 project at Github), but have been piggybacking the Nutch community for a
 while. If Gora is accepted to Apache Incubator, we expect more traction.
 Moreover, with the increasing popularity of NoSQL databases, we expect more
 users.

 === Core Developers ===
 Gora was started by the initial code base inside Apache Nutch by Doğacan
 Güney. Then Enis Söztutar has refactored and re-architected the project out
 of Nutch. Later Julien Nioche, Andrzej Bialecki and Doğacan has ported Nutch
 to use the newly formed project. Later, Sertan Alkan has joined. Doğacan and
 Julien are Nutch PMC members, Andrzej is the 

Re: Restored missing Bluesky/Clerezza parts of this month's report

[Tom White]

On Mon, May 17, 2010 at 1:35 PM, Bertrand Delacretaz
bdelacre...@apache.org wrote:
 Hi Noel,

 FYI I just fixed the report (although it said closed) at
 http://wiki.apache.org/incubator/May2010 - the beginning of Clerezza
 report had been mistakenly deleted in revision 19.

 Looks like there are other inconsistencies in the wiki report, Amber,
 Hise and Whirr are missing but according to
 http://wiki.apache.org/incubator/ReportingSchedule they should be
 there.

I read the page to mean that the first report for Amber and Whirr
would be June, then July, August, before falling into a quarterly
schedule. Please say if I've got this wrong, so we can put together a
report for Whirr.

Cheers
Tom


 -Bertrand

 -
 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 Whirr for Incubation

[Tom White]

The vote passes with 11 +1s (6 binding), zero 0s and zero -1s.

The next step is to create the podling and infrastructure.

Thanks,
Tom

On Mon, May 10, 2010 at 6:50 AM, Donald Woods dwo...@apache.org wrote:
 [X] +1 Accept Whirr for incubation


 -Donald


 On 5/5/10 2:06 PM, Tom White wrote:
 We've added three mentors since starting the proposal thread, so I
 would like to start the vote to accept Whirr into the Apache
 Incubator.

 The proposal is included below and is also at:
 http://wiki.apache.org/incubator/WhirrProposal

 Please cast your votes:

 [ ] +1 Accept Whirr for incubation
 [ ] +0 Don't care
 [ ] -1 Reject for the following reason:

 Thanks,

 Tom

 = Whirr, a library of cloud services =

 == Abstract ==
 Whirr will be a set of libraries for running cloud services.

 == Proposal ==
 Whirr will provide code for running a variety of software services on
 cloud infrastructure. It will provide bindings in several languages
 (e.g. Python and Java) for popular cloud providers to make it easy to
 start and stop services like Hadoop clusters. The project will not be
 limited to a particular set of services, rather it will be expected
 that a range of services are developed, as determined by the project
 contributors. Possible services include Hadoop, HBase, !ZooKeeper,
 Cassandra.

 == Background ==
 The ability to run services on cloud providers is very useful,
 particularly for proofs of concept, testing, and also ad hoc
 production work. Bringing up clusters in the cloud is non-trivial,
 since careful choreography is required. (Designing an interface that
 is convenient as well as secure is also a challenge in a cloud
 context.)  Making services that runs on a variety of cloud providers
 is harder, even with the availability of libraries like libcloud and
 jclouds, since each platform's quirks and extra features must be
 considered (and either worked around, or possibly taken advantage of,
 as appropriate) . Whirr will facilitate sharing of best practices,
 both for a particular service (such as Hadoop configuration on a
 particular provider), and for common cloud operations (such as
 installation of dependencies across cloud providers). It will provide
 a space to share good configurations and will encode service-specific
 knowledge.

 == Rationale ==
 There are already scripts in the Hadoop project that allow users to
 run Hadoop clusters on Amazon EC2 and other cloud providers. While
 users have found these scripts useful, their current home as a Hadoop
 Common contrib project has the following limitations:
  * Tying the scripts' release cycle to Hadoop's means that it is
 difficult to distribute updates to the scripts which are changing fast
 (new features and bugfixes).
  * The scripts support multiple versions of Hadoop, so it makes more
 sense to distribute them separately from Hadoop itself.
  * They are general: people want to contribute code for non-Hadoop
 services like Cassandra (for example:
 http://github.com/johanoskarsson/cassandra-ec2).
  * Having a uniform approach to running services in the cloud, hosted
 in one project, makes launching sets of complementary services easier
 for the user. Today, the scripts and libraries hosted within each
 project (e.g. in Hadoop, HBase, Cassandra) have slightly different
 conventions and semantics, and are likely to diverge over time.
 Building a community around cloud infrastructure services will help
 enforce a common approach to running services in the cloud.

 == Initial Goals ==
  * Provide a new home for the existing Hadoop cloud scripts.
  * Add more services (e.g. HBase)
  * Develop Java libraries for Hadoop clusters
  * Add new cloud providers by taking advantage of libcloud and jclouds.
  * (Future) Run on own hardware, so users can take advantage of the
 same interface to control services running locally or in the cloud.

 == Current Status ==
 === Meritocracy ===
 The Hadoop scripts were originally created by Tom White, and have had
 a substantial number of contributions from members of the Hadoop
 community. By becoming its own project, significant contributors to
 Whirr would become committers, and allow the project to grow.

 === 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. For example, this project would provide a
 home to facilitate collaboration between the groups of Hadoop and
 HBase developers who are building cloud services.

 === Core developers ===
 Tom White wrote most of the original code and is familiar with open
 source and Apache-style development, being a Hadoop committer and an
 ASF member. There have been a number of contributors who have provided
 patches to these scripts over time. Andrew Purtell who created the
 HBase cloud scripts is a HBase committer. Johan Oskarsson (Hadoop and
 Cassandra

Re: [VOTE] Accept Whirr for Incubation

[Tom White]

The vote passes with 11 +1s (6 binding), zero 0s and zero -1s.

The next step is to create the podling and infrastructure.

Thanks,
Tom

On Mon, May 10, 2010 at 6:50 AM, Donald Woods dwo...@apache.org wrote:
 [X] +1 Accept Whirr for incubation


 -Donald


 On 5/5/10 2:06 PM, Tom White wrote:
 We've added three mentors since starting the proposal thread, so I
 would like to start the vote to accept Whirr into the Apache
 Incubator.

 The proposal is included below and is also at:
 http://wiki.apache.org/incubator/WhirrProposal

 Please cast your votes:

 [ ] +1 Accept Whirr for incubation
 [ ] +0 Don't care
 [ ] -1 Reject for the following reason:

 Thanks,

 Tom

 = Whirr, a library of cloud services =

 == Abstract ==
 Whirr will be a set of libraries for running cloud services.

 == Proposal ==
 Whirr will provide code for running a variety of software services on
 cloud infrastructure. It will provide bindings in several languages
 (e.g. Python and Java) for popular cloud providers to make it easy to
 start and stop services like Hadoop clusters. The project will not be
 limited to a particular set of services, rather it will be expected
 that a range of services are developed, as determined by the project
 contributors. Possible services include Hadoop, HBase, !ZooKeeper,
 Cassandra.

 == Background ==
 The ability to run services on cloud providers is very useful,
 particularly for proofs of concept, testing, and also ad hoc
 production work. Bringing up clusters in the cloud is non-trivial,
 since careful choreography is required. (Designing an interface that
 is convenient as well as secure is also a challenge in a cloud
 context.)  Making services that runs on a variety of cloud providers
 is harder, even with the availability of libraries like libcloud and
 jclouds, since each platform's quirks and extra features must be
 considered (and either worked around, or possibly taken advantage of,
 as appropriate) . Whirr will facilitate sharing of best practices,
 both for a particular service (such as Hadoop configuration on a
 particular provider), and for common cloud operations (such as
 installation of dependencies across cloud providers). It will provide
 a space to share good configurations and will encode service-specific
 knowledge.

 == Rationale ==
 There are already scripts in the Hadoop project that allow users to
 run Hadoop clusters on Amazon EC2 and other cloud providers. While
 users have found these scripts useful, their current home as a Hadoop
 Common contrib project has the following limitations:
  * Tying the scripts' release cycle to Hadoop's means that it is
 difficult to distribute updates to the scripts which are changing fast
 (new features and bugfixes).
  * The scripts support multiple versions of Hadoop, so it makes more
 sense to distribute them separately from Hadoop itself.
  * They are general: people want to contribute code for non-Hadoop
 services like Cassandra (for example:
 http://github.com/johanoskarsson/cassandra-ec2).
  * Having a uniform approach to running services in the cloud, hosted
 in one project, makes launching sets of complementary services easier
 for the user. Today, the scripts and libraries hosted within each
 project (e.g. in Hadoop, HBase, Cassandra) have slightly different
 conventions and semantics, and are likely to diverge over time.
 Building a community around cloud infrastructure services will help
 enforce a common approach to running services in the cloud.

 == Initial Goals ==
  * Provide a new home for the existing Hadoop cloud scripts.
  * Add more services (e.g. HBase)
  * Develop Java libraries for Hadoop clusters
  * Add new cloud providers by taking advantage of libcloud and jclouds.
  * (Future) Run on own hardware, so users can take advantage of the
 same interface to control services running locally or in the cloud.

 == Current Status ==
 === Meritocracy ===
 The Hadoop scripts were originally created by Tom White, and have had
 a substantial number of contributions from members of the Hadoop
 community. By becoming its own project, significant contributors to
 Whirr would become committers, and allow the project to grow.

 === 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. For example, this project would provide a
 home to facilitate collaboration between the groups of Hadoop and
 HBase developers who are building cloud services.

 === Core developers ===
 Tom White wrote most of the original code and is familiar with open
 source and Apache-style development, being a Hadoop committer and an
 ASF member. There have been a number of contributors who have provided
 patches to these scripts over time. Andrew Purtell who created the
 HBase cloud scripts is a HBase committer. Johan Oskarsson (Hadoop and
 Cassandra

[VOTE] Accept Whirr for Incubation

[Tom White]

We've added three mentors since starting the proposal thread, so I
would like to start the vote to accept Whirr into the Apache
Incubator.

The proposal is included below and is also at:
http://wiki.apache.org/incubator/WhirrProposal

Please cast your votes:

[ ] +1 Accept Whirr for incubation
[ ] +0 Don't care
[ ] -1 Reject for the following reason:

Thanks,

Tom

= Whirr, a library of cloud services =

== Abstract ==
Whirr will be a set of libraries for running cloud services.

== Proposal ==
Whirr will provide code for running a variety of software services on
cloud infrastructure. It will provide bindings in several languages
(e.g. Python and Java) for popular cloud providers to make it easy to
start and stop services like Hadoop clusters. The project will not be
limited to a particular set of services, rather it will be expected
that a range of services are developed, as determined by the project
contributors. Possible services include Hadoop, HBase, !ZooKeeper,
Cassandra.

== Background ==
The ability to run services on cloud providers is very useful,
particularly for proofs of concept, testing, and also ad hoc
production work. Bringing up clusters in the cloud is non-trivial,
since careful choreography is required. (Designing an interface that
is convenient as well as secure is also a challenge in a cloud
context.)  Making services that runs on a variety of cloud providers
is harder, even with the availability of libraries like libcloud and
jclouds, since each platform's quirks and extra features must be
considered (and either worked around, or possibly taken advantage of,
as appropriate) . Whirr will facilitate sharing of best practices,
both for a particular service (such as Hadoop configuration on a
particular provider), and for common cloud operations (such as
installation of dependencies across cloud providers). It will provide
a space to share good configurations and will encode service-specific
knowledge.

== Rationale ==
There are already scripts in the Hadoop project that allow users to
run Hadoop clusters on Amazon EC2 and other cloud providers. While
users have found these scripts useful, their current home as a Hadoop
Common contrib project has the following limitations:
 * Tying the scripts' release cycle to Hadoop's means that it is
difficult to distribute updates to the scripts which are changing fast
(new features and bugfixes).
 * The scripts support multiple versions of Hadoop, so it makes more
sense to distribute them separately from Hadoop itself.
 * They are general: people want to contribute code for non-Hadoop
services like Cassandra (for example:
http://github.com/johanoskarsson/cassandra-ec2).
 * Having a uniform approach to running services in the cloud, hosted
in one project, makes launching sets of complementary services easier
for the user. Today, the scripts and libraries hosted within each
project (e.g. in Hadoop, HBase, Cassandra) have slightly different
conventions and semantics, and are likely to diverge over time.
Building a community around cloud infrastructure services will help
enforce a common approach to running services in the cloud.

== Initial Goals ==
 * Provide a new home for the existing Hadoop cloud scripts.
 * Add more services (e.g. HBase)
 * Develop Java libraries for Hadoop clusters
 * Add new cloud providers by taking advantage of libcloud and jclouds.
 * (Future) Run on own hardware, so users can take advantage of the
same interface to control services running locally or in the cloud.

== Current Status ==
=== Meritocracy ===
The Hadoop scripts were originally created by Tom White, and have had
a substantial number of contributions from members of the Hadoop
community. By becoming its own project, significant contributors to
Whirr would become committers, and allow the project to grow.

=== 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. For example, this project would provide a
home to facilitate collaboration between the groups of Hadoop and
HBase developers who are building cloud services.

=== Core developers ===
Tom White wrote most of the original code and is familiar with open
source and Apache-style development, being a Hadoop committer and an
ASF member. There have been a number of contributors who have provided
patches to these scripts over time. Andrew Purtell who created the
HBase cloud scripts is a HBase committer. Johan Oskarsson (Hadoop and
Cassandra committer) ported the scripts to Cassandra.

=== Alignment ===
Whirr complements libcloud, currently in the Incubator. Libcloud
provides multi-cloud provider support, while Whirr will provide
multi-service support in the cloud. Whirr will build cloud components
for several Apache projects, such as Hadoop, HBase, !ZooKeeper,
Cassandra, and hopefully more.

== Known Risks ==
=== Orphaned

Re: [PROPOSAL] Whirr Project

[Tom White]

Patrick,

That sounds great - thanks for volunteering. I've added you to the
initial committer list on the proposal page at
http://wiki.apache.org/incubator/WhirrProposal.

Steve Loughran has volunteered to be a mentor; I've added his name too.

I would like to send a vote on this proposal to the Incubator PMC in
the next few days, so if anyone else would like to mentor (and we'd
love to have more mentors), please sign up soon.

Thanks,
Tom

On Wed, Apr 28, 2010 at 11:13 PM, Patrick Hunt ph...@apache.org wrote:
 Tom, I'd be happy to be a committer (or contributor) for Whirr. I'm very
 interested to see ZooKeeper supported. Also very interested in
 non-production uses (such as testing).

 Regards,

 Patrick


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Whirr Project

[Tom White]

Thanks for the advice, Niclas. I've sent a mail to the PMC private list.

Cheers,
Tom

On Thu, Apr 22, 2010 at 5:25 PM, Niclas Hedhman nic...@hedhman.org wrote:
 On Fri, Apr 23, 2010 at 7:58 AM, Tom White tomwh...@apache.org wrote:
 You do know any ASF member can sign up to be an incubator mentor, right? If
 I count correctly you have two on your list :)

 I didn't know that. I've added myself as a mentor.

 Just send a mail to PMC private list that you wish to be added to the
 PMC and subscribe to the private list. Then you are set to go.


 Cheers
 --
 Niclas Hedhman, Software Developer
 http://www.qi4j.org - New Energy for Java

 I  live here; http://tinyurl.com/2qq9er
 I  work here; http://tinyurl.com/2ymelc
 I relax here; http://tinyurl.com/2cgsug

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Whirr Project

[Tom White]

On Thu, Apr 22, 2010 at 3:46 PM, Leo Simons m...@leosimons.com wrote:

 ...and pasted inline below (as is customary). The proposal looks fine to me.
 Like you mention your initial group of committers is a bit small which is a
 risk but hey, cloud is hot, go build community :)

That's the plan.

 You do know any ASF member can sign up to be an incubator mentor, right? If
 I count correctly you have two on your list :)

I didn't know that. I've added myself as a mentor.

@Doug - thanks for volunteering to be a mentor - I've added you to the
wiki page too.

Cheers,
Tom

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Whirr Project

[Tom White]

Hi Chris,

Thanks for your interest in the proposal. Using Whirr in other
projects, like OODT, is definitely a use case I'm interested in. Also
Solr would make a good service to include in Whirr.

Cheers,
Tom

On Thu, Apr 15, 2010 at 10:28 PM, Mattmann, Chris A (388J)
chris.a.mattm...@jpl.nasa.gov wrote:
 Hi Tom,

 This sounds interesting. It would be interesting to look at e.g., how we 
 could take some of the OODT [1] configurations and use Whirr as a front-end 
 to run them in the cloud. I also know the folks in Solr are using Zookeeper, 
 so they may benefit from this project as well.

 I don't have a huge amount of time since I'm overcommitted at work, and with 
 2 podlings I'm participating in (OODT and SIS), but my +1 to move forward 
 with this as it seems useful. I will try and monitor the lists and if I get 
 the time to help out at some point, I'll bug you on list ^_^

 Cheers,
 Chris

 [1] http://incubator.apache.org/projects/oodt.html


 On 4/15/10 2:42 PM, Tom White tomwh...@apache.org wrote:

 I would like to propose Whirr as an incubator proposal.

 Whirr will be a set of libraries for running cloud services, such as
 Hadoop or Cassandra. The initial code (for Hadoop) is hosted as a
 Hadoop contrib module, but I believe it would flourish as its own
 project with its own community.

 The proposal is on the incubator wiki at
 http://wiki.apache.org/incubator/WhirrProposal.

 We look forward to hearing feedback and questions on the proposal.
 Also, we don't have any mentors yet, so please sign up if you are
 interested in helping out.

 Thanks,
 Tom

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org




 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.mattm...@jpl.nasa.gov
 WWW:   http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[PROPOSAL] Whirr Project

[Tom White]

I would like to propose Whirr as an incubator proposal.

Whirr will be a set of libraries for running cloud services, such as
Hadoop or Cassandra. The initial code (for Hadoop) is hosted as a
Hadoop contrib module, but I believe it would flourish as its own
project with its own community.

The proposal is on the incubator wiki at
http://wiki.apache.org/incubator/WhirrProposal.

We look forward to hearing feedback and questions on the proposal.
Also, we don't have any mentors yet, so please sign up if you are
interested in helping out.

Thanks,
Tom

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org