from:"Jarek Jarcec Cecho"

Re: [VOTE] Accept Spot into the Apache Incubator

2016-09-20 Thread Jarek Jarcec Cecho

ality is divided into different repositories, with each
> repository containing the relevant developer documentation:
> 
> * oni-ingest
> * oni-ml
> * oni-oa
> * oni-setup
> * oni-nfdump
> * oni-lda-c
> 
> An Installation Guide is published in the project wiki:
> * https://github.com/Open-Network-Insight/open-network-insight/wiki
> The Spot (currently Open Network Insight) website is managed via a
> Wordpress instance hosted by Bluehost:
> * http://open-network-insight.org/
> A Docker-based demo is available via Docker Hub:
> * https://hub.docker.com/r/opennetworkinsight/oni-demo/
> 
> == Initial Source ==
> 
> The Spot codebase is currently hosted on GitHub and will be
> transitioned to the ASF repositories during incubation. Spot and its
> submodules are currently licensed under several different licenses.
> 
> No trademarks or domain names for Spot have been registered to date,
> and it will be up to the ASF’s discretion to do so. The project’s
> current website at open-network-insight.org will be redirected to
> spot.incubator.apache.org during incubation.
> 
> Some portions of the code are imported from other open source projects
> under the Apache 2.0, BSD, or MIT licenses.
> 
> == External Dependencies ==
> 
> The full set of dependencies and licenses are:
> * Jupyter: BSD
> * D3js: BSD
> * Nfdump: BSD
> * Wireshark: GNU General Public License version 2
> * Apache Hadoop: Apache License 2.0
> * Apache Spark: Apache License 2.0
> * JQuery: MIT
> * ReactJS: BSD
> * Bootstrap: MIT
> 
> Issues related to GPL dependencies will be resolved during incubation.
> 
> == Cryptography ==
> 
> Spot does not currently include any cryptography-related code.
> 
> == Required Resources ==
> 
> === Developer and user mailing lists ===
> 
> * priv...@spot.incubator.apache.org (PMC)
> * comm...@spot.incubator.apache.org (git push emails)
> * iss...@spot.incubator.apache.org (JIRA issue feed)
> * d...@spot.incubator.apache.org (code reviews plus dev discussion)
> * u...@spot.incubator.apache.org (user questions)
> 
> === Repository ===
> 
> * git://git.apache.org/spot
> 
> === Issue Tracker ===
> 
> We would like to import our current JIRA project into the ASF JIRA,
> such that our historical commit messages and code comments continue to
> reference the appropriate bug numbers.
> 
> == Initial Committers ==
> 
> * Grant Babb
> * Ricardo Barona
> * Cesar Berho
> * Jarek Jarcec Cecho
> * Michael Czerny
> * Nick Gamb
> * Sai Ganji
> * Gabriela Lima Garza
> * Victor Gonzalez
> * Mark Grover
> * Morris Hicks
> * Ritu Kama
> * Austin Leahy
> * Ashrith Mekala
> * Diego Ortiz
> * Sudharshan Rao PakalaSai
> * Srinivasa Reddy
> * Alan Ross
> * Everardo Lopez Sandoval
> * Nathan Segerlind
> * Vartika Singh
> * Nathanael Smith
> * Carlos Villavicencio
> 
> == Affiliations ==
> 
> * Grant Babb: Jask
> * Ricardo Barona : Intel
> * Cesar Berho: Intel
> * Jarek Jarcec Cecho: StreamSets
> * Michael Czerny: Cybraics
> * Nick Gamb: Centrify
> * Sai Ganji: Cloudwick
> * Gabriela Lima Garza: Intel
> * Victor Gonzalez: Intel
> * Mark Grover: Cloudera
> * Morris Hicks: Cloudera
> * Ritu Kama: Intel
> * Austin Leahy: eBay
> * Ashrith Mekala: Cloudwick
> * Diego Ortiz: Intel
> * Sudharshan Rao PakalaSai: Cloudwick
> * Srinivasa Reddy: Cloudera
> * Alan Ross: Intel
> * Everardo Lopez Sandoval: Intel
> * Nathan Segerlind: Intel
> * Vartika Singh: Cloudera
> * Nathanael Smith: Intel
> * Carlos Villavicencio: Intel
> 
> == Sponsors ==
> 
> === Champion ===
> 
> * Doug Cutting - Cloudera
> 
> === Nominated Mentors ===
> 
> * Brock Noland - ASF Member, phData
> * Jarek Jarcec Cecho - ASF Member, StreamSets
> * Andrei Savu - Cloudera
> * Uma Maheswara Rao G - Intel
> 
> === Sponsoring Entity ===
> 
> The Apache Incubator.
> 
> -
> 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 Gearpump into the Apache Incubator

2016-03-02 Thread Jarek Jarcec Cecho

e to migrate to the Apache
> foundation. The Gearpump source code is licensed under Apache License
> Version 2.0 and will be kept that way. All contributions on the project
> will be licensed directly to the Apache foundation through signed
> Individual Contributor License Agreements or Corporate Contributor License
> Agreements.
> 
> === External Dependencies ===
> All of Gearpump dependencies are distributed under Apache compatible
> licenses.
> 
> Gearpump leverages Akka which has Apache 2.0 licensing for current and
> planned versions
> http://doc.akka.io/docs/akka/2.3.12/project/licenses.html#Licenses_for_Dependency_Libraries
> 
> === Cryptography ===
> Gearpump does not include or utilize cryptographic code.
> 
> === Required Resources ===
> We request that following resources be created for the project to use
> 
>  Mailing lists 
> 
> gearpump-priv...@incubator.apache.org (with moderated subscriptions)
> gearpump-dev
> gearpump-user
> gearpump-commits
> 
>  Git repository 
> Git is the preferred source control system: git://git.apache.org/gearpump
> 
>  Documentation 
> https://gearpump.incubator.apache.org/docs/
> 
>  JIRA instance 
> JIRA Gearpump (GEARPUMP)
> https://issues.apache.org/jira/browse/gearpump
> 
> === Initial Committers ===
> * Xiang Zhong 
> 
> * Tianlun Zhang 
> 
> * Qian Xu 
> 
> * Huafeng Wang 
> 
> * Kam Kasravi 
> 
> * Weihua Jiang 
> 
> * Tomasz Targonski 
> 
> * Karol Brejna 
> 
> * Gang Wang 
> 
> * Mark Chmarny 
> 
> * Xinglang Wang 
> 
> * Lan Wang 
> 
> * Jianzhong Chen 
> 
> * Xuefu Zhang 
> 
> * Rui Li 
> 
> === Affiliations ===
> * Xiang Zhong –  Intel
> 
> * Tianlun Zhang –  Intel
> 
> * Qian Xu –  Intel
> 
> * Huafeng Wang –  Intel
> 
> * Kam Kasravi –  Intel
> 
> * Weihua Jiang –  Intel
> 
> * Tomasz Targonski – Intel
> 
> * Karol Brejna – Intel
> 
> * Mark Chmarny – Intel
> 
> * Gang Wang – Intel
> 
> * Mark Chmarny  – Intel
> 
> * Xinglang Wang  – Ebay
> 
> * Lan Wang – Huawei
> 
> * Jianzhong Chen – Cloudera
> 
> * Xuefu Zhang – Cloudera
> 
> * Rui Li  – Intel
> 
> === Sponsors ===
> 
>  Champion 
> Andrew Purtell 
> 
>  Nominated Mentors 
> * Andrew Purtell 
> 
> * Jarek Jarcec Cecho 
> 
> * Todd Lipcon 
> 
> * Xuefu Zhang 
> 
> * Reynold Xin 
> 
>  Sponsoring Entity 
> Apache Incubator PMC
> 
> 


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

Re: [VOTE] Graduate Sentry

2016-02-25 Thread Jarek Jarcec Cecho

[ X ] +1 Graduate Sentry from the Incubator

Jarcec

> On Feb 25, 2016, at 7:53 AM, Ralph Goers <ralph.go...@dslextreme.com> wrote:
> 
> +1 (binding)
> 
> Ralph
> 
>> On Feb 24, 2016, at 12:20 PM, Sravya Tirukkovalur <sra...@apache.org> 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 <a...@apache.org>
>> 
>>  * Anne Yu <ann...@apache.org>
>> 
>>  * Arun Suresh <asur...@apache.org>
>> 
>>  * Brock Noland <br...@apache.org>
>> 
>>  * Chaoyu Tang <ct...@apache.org>
>> 
>>  * Colin Ma <co...@apache.org>
>> 
>>  * Daisy Zhou <da...@apache.org>
>> 
>>  * Dapeng Sun <s...@apache.org>
>> 
>>  * David Nalley <ke4...@apache.org>
>> 
>>  * Erick Tryzelaar <eri...@apache.org>
>> 
>>  * Gregory Chanan <gcha...@apache.org>
>> 
>>  * Guoquan Shen <gqs...@apache.org>
>> 
>>  * Hadi Nahari <h...@apache.org>
>> 
>>  * Hao Hao <ha...@apache.org>
>> 
>>  * Jarek Jarcec Cecho <jar...@apache.org>
>> 
>>  * Johnny Zhang <dreamb...@apache.org>
>> 
>>  * Karthik Ramachandran <kramachand...@apache.org>
>> 
>>  * Mark Grover <m...@apache.org>
>> 
>>  * Milo Polte <m...@apache.org>
>> 
>>  * Lenni Kuff <lsk...@apache.org>
>> 
>>  * Patrick Daly <d...@apache.org>
>> 
>>  * Patrick Hunt <ph...@apache.org>
>> 
>>  * Prasad Mujumdar <pras...@apache.org>
>> 
>>  * Raghu Mani <raghu_m...@apache.org>
>> 
>>  * Sean Mackrory <mackror...@apache.org>
>> 
>>  * Shreepadma Venugopalan <shreepa...@apache.org>
>> 
>>  * Sravya Tirukkovalur <sra...@apache.org>
>> 
>>  * Tuong Truong <tuongtru...@apache.org>
>> 
>>  * Vamsee Yarlagadda <vam...@apache.org>
>> 
>>  * Xiaomeng Huang <

Re: [VOTE] Graduate Sentry from the Incubator

2016-02-17 Thread Jarek Jarcec Cecho

+1

Binding.

Jarcec

> On Feb 16, 2016, at 2:07 PM, Sravya Tirukkovalur  wrote:
> 
> Justin,
> 
> Yes, for the release 1.5.0 - voting was restarted on the general
> list[1]. We later on did releases 1.5.1 (to fix some issues in 1.5.0)
> and 1.6.0.
> 
> [1]: 
> http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCAE%3DhR00RGz5N7PYV33iG%2BC%2B3Ye%3DaNSCDCg8_85RE9wBR8rW%3DBQ%40mail.gmail.com%3E
> 
> Thanks,
> 
> On Tue, Feb 16, 2016 at 1:49 PM, Justin Mclean  
> wrote:
>> Hi,
>> 
>> There was I recall some issue withApache Sentry incubating releases [1]. Was 
>> this resolved?
>> 
>> Thanks,
>> Justin
>> 
>> 1. http://markmail.org/message/75bxp6txgzwpxt77
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> 
> 
> -- 
> Sravya Tirukkovalur
> 
> -
> 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 Impala into the Apache Incubator

2015-11-25 Thread Jarek Jarcec Cecho

[X] +1, accept Impala into the Incubator

(Binding)

Jarcec

> On Nov 24, 2015, at 1:03 PM, Henry Robinson  wrote:
> 
> Hi -
> 
> The [DISCUSS] thread has been quiet for a few days, so I think there's been
> sufficient opportunity for discussion around our proposal to bring Impala
> to the ASF Incubator.
> 
> I'd like to call a VOTE on that proposal, which is on the wiki at
> https://wiki.apache.org/incubator/ImpalaProposal, and which I've pasted
> below.
> 
> During the discussion period, the proposal has been amended to add Brock
> Noland as a new mentor, to add one missed committer from the list and to
> correct some issues with the dependency list.
> 
> Please cast your votes as follows:
> 
> [] +1, accept Impala into the Incubator
> [] +/-0, non-counted vote to express a disposition
> [] -1, do not accept Impala into the Incubator (please give your reason(s))
> 
> As with the concurrent Kudu vote, I propose leaving the vote open for a
> full seven days (to close at Tuesday, December 1st at noon PST), due to the
> upcoming US holiday.
> 
> Thanks,
> Henry
> 
> 
> 
> = Abstract =
> Impala is a high-performance C++ and Java SQL query engine for data stored
> in Apache Hadoop-based clusters.
> 
> = Proposal =
> 
> We propose to contribute the Impala codebase and associated artifacts (e.g.
> documentation, web-site content etc.) to the Apache Software Foundation
> with the intent of forming a productive, meritocratic and open community
> around Impala’s continued development, according to the ‘Apache Way’.
> 
> Cloudera owns several trademarks regarding Impala, and proposes to transfer
> ownership of those trademarks in full to the ASF.
> 
> = Background =
> Engineers at Cloudera developed Impala and released it as an
> Apache-licensed open-source project in Fall 2012. Impala was written as a
> brand-new, modern C++ SQL engine targeted from the start for data stored in
> Apache Hadoop clusters.
> 
> Impala’s most important benefit to users is high-performance, making it
> extremely appropriate for common enterprise analytic and business
> intelligence workloads. This is achieved by a number of software
> techniques, including: native support for data stored in HDFS and related
> filesystems, just-in-time compilation and optimization of individual query
> plans, high-performance C++ codebase and massively-parallel distributed
> architecture. In benchmarks, Impala is routinely amongst the very highest
> performing SQL query engines.
> 
> = Rationale =
> 
> Despite the exciting innovation in the so-called ‘big-data’ space, SQL
> remains by far the most common interface for interacting with data in both
> traditional warehouses and modern ‘big-data’ clusters. There is clearly a
> need, as evidenced by the eager adoption of Impala and other SQL engines in
> enterprise contexts, for a query engine that offers the familiar SQL
> interface, but that has been specifically designed to operate in massive,
> distributed clusters rather than in traditional, fixed-hardware,
> warehouse-specific deployments. Impala is one such query engine.
> 
> We believe that the ASF is the right venue to foster an open-source
> community around Impala’s development. We expect that Impala will benefit
> from more productive collaboration with related Apache projects, and under
> the auspices of the ASF will attract talented contributors who will push
> Impala’s development forward at pace.
> 
> We believe that the timing is right for Impala’s development to move
> wholesale to the ASF: Impala is well-established, has been Apache-licensed
> open-source for more than three years, and the core project is relatively
> stable. We are excited to see where an ASF-based community can take Impala
> from this strong starting point.
> 
> = Initial Goals =
> Our initial goals are as follows:
> 
> * Establish ASF-compatible engineering practices and workflows
> * Refactor and publish existing internal build scripts and test
> infrastructure, in order to make them usable by any community member.
> * Transfer source code, documentation and associated artifacts to the ASF.
> * Grow the user and developer communities
> 
> = Current Status =
> 
> Impala is developed as an Apache-licensed open-source project. The source
> code is available at http://github.com/cloudera/Impala, and developer
> documentation is at https://github.com/cloudera/Impala/wiki. The majority
> of commits to the project have come from Cloudera-employed developers, but
> we have accepted some contributions from individuals from other
> organizations.
> 
> All code reviews are done via a public instance of the Gerrit review tool
> at http://gerrit.cloudera.org:8080/, and discussed on a public mailing
> list. All patches must be reviewed before they are accepted into the
> codebase, via a voting mechanism that is similar to that used on Apache
> projects such as Hadoop and HBase.
> 
> Before a patch is committed, it must pass a suite of pre-commit tests.
>

Re: [VOTE] Accept Kudu into the Apache Incubator

2015-11-24 Thread Jarek Jarcec Cecho

ation comments.
> * Many design documents are stored within the source code repository as
> text files next to the code being documented.
> 
> == Source and Intellectual Property Submission Plan ==
> 
> The Kudu codebase and web site is currently hosted on GitHub and will be
> transitioned to the ASF repositories during incubation. Kudu is already
> licensed under the Apache 2.0 license.
> 
> 
> 
> Some portions of the code are imported from other open source projects
> under the Apache 2.0, BSD, or MIT licenses, with copyrights held by authors
> other than the initial committers. These copyright notices are maintained
> in those files as well as a top-level NOTICE.txt file. We believe this to
> be permissible under the license terms and ASF policies, and confirmed via
> a recent thread on general@incubator.apache.org .
> 
> 
> 
> The “Kudu” name is not a registered trademark, though before the initial
> release of the project, we performed a trademark search and Cloudera’s
> legal counsel deemed it acceptable in the context of a data storage engine.
> There exists an unrelated open source project by the same name related to
> deployments on Microsoft’s Azure cloud service. We have been in contact
> with legal counsel from Microsoft and have obtained their approval for the
> use of the Kudu name.
> 
> 
> 
> Cloudera currently owns several domain names related to Kudu (getkudu.io,
> kududb.io, et al) which will be transferred to the ASF and redirected to
> the official page during incubation.
> 
> 
> 
> Portions of Kudu are protected by pending or published patents owned by
> Cloudera. Given the protections already granted by the Apache License, we
> do not anticipate any explicit licensing or transfer of this intellectual
> property.
> 
> == External Dependencies ==
> 
> The full set of dependencies and licenses are listed in
> https://github.com/cloudera/kudu/blob/master/LICENSE.txt
> 
> and summarized here:
> 
> * '''Twitter Bootstrap''': Apache 2.0
> * '''d3''': BSD 3-clause
> * '''epoch JS library''': MIT
> * '''lz4''': BSD 2-clause
> * '''gflags''': BSD 3-clause
> * '''glog''': BSD 3-clause
> * '''gperftools''': BSD 3-clause
> * '''libev''': BSD 2-clause
> * '''squeasel''':MIT license
> * '''protobuf''': BSD 3-clause
> * '''rapidjson''': MIT
> * '''snappy''': BSD 3-clause
> * '''trace-viewer''': BSD 3-clause
> * '''zlib''': zlib license
> * '''llvm''': University of Illinois/NCSA Open Source (BSD-alike)
> * '''bitshuffle''': MIT
> * '''boost''': Boost license
> * '''curl''': MIT
> * '''libunwind''': MIT
> * '''nvml''': BSD 3-clause
> * '''cyrus-sasl''': Cyrus SASL license (BSD-alike)
> * '''openssl''': OpenSSL License (BSD-alike)
> 
> * '''Guava''': Apache 2.0
> * '''StumbleUpon Async''': BSD
> * '''Apache Hadoop''': Apache 2.0
> * '''Apache log4j''': Apache 2.0
> * '''Netty''': Apache 2.0
> * '''slf4j''': MIT
> * '''Apache Commons''': Apache 2.0
> * '''murmur''': Apache 2.0
> 
> 
> '''Build/test-only dependencies''':
> 
> * '''CMake''': BSD 3-clause
> * '''gcovr''': BSD 3-clause
> * '''gmock''': BSD 3-clause
> * '''Apache Maven''': Apache 2.0
> * '''JUnit''': EPL
> * '''Mockito''': MIT
> 
> == Cryptography ==
> 
> Kudu does not currently include any cryptography-related code.
> 
> == Required Resources ==
> 
> === Mailing lists ===
> 
> * priv...@kudu.incubator.apache.org (PMC)
> * comm...@kudu.incubator.apache.org (git push emails)
> * iss...@kudu.incubator.apache.org (JIRA issue feed)
> * d...@kudu.incubator.apache.org (Gerrit code reviews plus dev discussion)
> * u...@kudu.incubator.apache.org (User questions)
> 
> 
> === Repository ===
> 
> * git://git.apache.org/kudu
> 
> === Gerrit ===
> 
> We hope to continue using Gerrit for our code review and commit workflow.
> The Kudu team has already been in contact with Jake Farrell to start
> discussions on how Gerrit can fit into the ASF. We know that several other
> ASF projects and 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 Kudu, 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).
> 
> == Issue Tracking ==
> 
> We would like to import our current JIRA project into the ASF JIRA, such
> that our historical commit messages and code comments continue to reference
> the appropriate bug numbers.
> 
> == Initial Committers ==
> 
> * Adar Dembo a...@cloude

Re: [VOTE] Release Sentry incubating version 1.6.0 (rc0)

2015-09-16 Thread Jarek Jarcec Cecho

+1

* Signature and checksums fits
* Verified top level files (LICENSE, DISCLAMER, …)
* Project compiles
* Apache Rat is happy with licenses

Jarcec

> On Sep 15, 2015, at 11:27 PM, Sun, Dapeng  wrote:
> 
> Hi IPMC,
> 
> 
> 
> This is the incubator release of Apache Sentry, version 1.6.0-incubating.
> 
> 
> 
> A vote on releasing this package has already passed in Apache Sentry. We ask 
> for your help to vote on this incubator release.
> 
> PPMC[1] including +1 votes from our PPMC (Sravya Tirukkovalur, Lenni Kuff, 
> Prasad Mujumdar).
> 
> 
> 
> The list of fixed issues, added features and improvements can be found here:
> 
> http://s.apache.org/w5
> 
> Source files : 
> https://dist.apache.org/repos/dist/dev/incubator/sentry/1.6.0-incubating-rc0/
> 
> Tag to be voted on (release-1.6.0-rc0/SHA: 
> 3c122b76483531db5f0de82cd80d9ce5967f6e00):
> 
> https://git-wip-us.apache.org/repos/asf?p=incubator-sentry.git;a=commit;h=3c122b76483531db5f0de82cd80d9ce5967f6e00
> 
> Sentry's KEYS containing the PGP key we used to sign the release:
> 
> http://www.apache.org/dist/incubator/sentry/KEYS
> 
> 
> 
> Note that this is a source only release and we are voting on the source:
> 
> tag=release-1.6.0-rc0, SHA=3c122b76483531db5f0de82cd80d9ce5967f6e00
> 
> 
> 
> Vote will be open for 72 hours.
> 
> 
> 
> [ ] +1 approve
> 
> [ ] +0 no opinion
> 
> [ ] -1 disapprove (and reason why)
> 
> 
> 
> Thanks
> 
> Sentry 1.6.0 Release Manager (Dapeng Sun)
> 
> 
> 
> [1] 
> -http://mail-archives.apache.org/mod_mbox/sentry-dev/201509.mbox/%3CB957EE1AFDEBFD4B934BCF11804A23DC032933E5%40shsmsx102.ccr.corp.intel.com%3E


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

Re: [VOTE] Release Sentry incubating version 1.5.1 (rc0)

2015-07-13 Thread Jarek Jarcec Cecho

+1 binding

* Signature and checksums are correct
* Name correctly contains “-incubating” suffix
* Verified top level files (LICENSE, DISCLAIMER, NOTICE)
* I was not able to compile the archive with maven 3.0.5, I was getting
dependency issues with some pentaho library. The issue goes away with newer
maven version (3.2.5) - it might be worth document for others.
* I was not able to compile the archive with JDK8u25, I was getting “can’t
access TBase” error. JDK7 worked well though. It also might be worth
documenting :)
* Verified that product complies with maven 3.2.5 and JDK7. I did not tested on
cluster though.

Jarcec

-- Forwarded message --
From: Shen, Guoquan guoquan.s...@intel.com
Date: Thu, Jul 9, 2015 at 6:07 PM
Subject: [VOTE] Release Sentry incubating version 1.5.1 (rc0)
To: general@incubator.apache.org general@incubator.apache.org

Hello IPMC,
We have passed the PPMC vote for Sentry incubator release 1.5.1(rc0) with 3
+1 votes from
Lenni Kuff, Prasad Mujumdar and Sravya Tirukkovalur. We ask for your help to
vote
on this incubator release.

This is the incubator release of Apache Sentry, version 1.5.1-incubating.
It fixes the following issues: http://s.apache.org/hVw
Source files :
https://dist.apache.org/repos/dist/dev/incubator/sentry/1.5.1-incubating/
Tag to be voted on
(release-1.5.1/SHA:d9ee8ade724d7ecc7433517bfb769da2cd002b0b):https://git-wip-us.apache.org/repos/asf?p=incubator-sentry.git;a=commit;h=d9ee8ade724d7ecc7433517bfb769da2cd002b0b

Sentry's KEYS containing the PGP key we used to sign the release:
http://www.apache.org/dist/incubator/sentry/KEYS

Note that this is a source only release and we are voting on the source:
tag=release-1.5.1, SHA=d9ee8ade724d7ecc7433517bfb769da2cd002b0b

Vote will be opened for 72 hours.

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

Thank you for your prompt votes.

Respectfully,

Sentry 1.5.1 Release Manager (Guoquan Shen)

--
Sravya Tirukkovalur

-
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

2014-05-18 Thread Jarek Jarcec Cecho

 [ X ] +1 Accept Parquet into the Incubator

(non-binding)

Jarcec

On Sun, May 18, 2014 at 02:15:15PM -0700, Chris Aniszczyk wrote:
 Based on the results of the discussion thread:
 http://mail-archives.apache.org/mod_mbox/incubator-general/201405.mbox/%3CCAJg1wMRGhLu4P7LeVQB%2B5K0C-fr-pw2448uj%3D6-3zHag4F1EbA%40mail.gmail.com%3E
 
 I would like to call a vote on accepting Parquet into the incubator.
 https://wiki.apache.org/incubator/ParquetProposal
 
 [ ] +1 Accept Parquet into the Incubator
 [ ] +0 Indifferent to the acceptance of Parquet
 [ ] -1 Do not accept Parquet because ...
 
 The vote will be open until Thursday May 22nd 18:00 UTC.
 
 = Parquet Proposal =
 
 == Abstract ==
 Parquet is a columnar storage format for Hadoop.
 
 == Proposal ==
 
 We created Parquet to make the advantages of compressed, efficient columnar
 data representation available to any project in the Hadoop ecosystem,
 regardless of the choice of data processing framework, data model, or
 programming language.
 
 == Background ==
 
 Parquet is built from the ground up with complex nested data structures in
 mind, and uses the repetition/definition level approach to encoding such
 data structures, as popularized by Google Dremel (
 https://blog.twitter.com/2013/dremel-made-simple-with-parquet). We believe
 this approach is superior to simple flattening of nested name spaces.
 
 Parquet is built to support very efficient compression and encoding
 schemes. Parquet allows compression schemes to be specified on a per-column
 level, and is future-proofed to allow adding more encodings as they are
 invented and implemented. We separate the concepts of encoding and
 compression, allowing parquet consumers to implement operators that work
 directly on encoded data without paying decompression and decoding penalty
 when possible.
 
 == Rationale ==
 
 Parquet is built to be used by anyone. We believe that an efficient,
 well-implemented columnar storage substrate should be useful to all
 frameworks without the cost of extensive and difficult to set up
 dependencies.
 
 Furthermore, the rapid growth of Parquet community is empowered by open
 source. We believe the Apache foundation is a great fit as the long-term
 home for Parquet, as it provides an established process for
 community-driven development and decision making by consensus. This is
 exactly the model we want for future Parquet development.
 
 == Initial Goals ==
 
  * Move the existing codebase to Apache
  * Integrate with the Apache development process
  * Ensure all dependencies are compliant with Apache License version 2.0
  * Incremental development and releases per Apache guidelines
 
 == Current Status ==
 
 Parquet has undergone 2 major releases:
 https://github.com/Parquet/parquet-format/releases of the core format and
 22 releases: https://github.com/Parquet/parquet-mr/releases of the
 supporting set of Java libraries.
 
 The Parquet source is currently hosted at GitHub, which will seed the
 Apache git repository.
 
 === Meritocracy ===
 
 We plan to invest in supporting a meritocracy. We will discuss the
 requirements in an open forum. Several companies have already expressed
 interest in this project, and we intend to invite additional developers to
 participate. We will encourage and monitor community participation so that
 privileges can be extended to those that contribute.
 
 === Community ===
 
 There is a large need for an advanced columnar storage format for Hadoop.
 Parquet is being used in production by many organizations (see
 https://github.com/Parquet/parquet-mr/blob/master/PoweredBy.md)
 
  * Cloudera: https://twitter.com/HenryR/statuses/324222874011451392
  * Criteo: https://twitter.com/julsimon/statuses/312114074911666177
  * Salesforce: https://twitter.com/TwitterOSS/statuses/392734610116726784
  * Stripe: https://twitter.com/avibryant/statuses/391339949250715648
  * Twitter: https://twitter.com/J_/statuses/315844725611581441
 
 By bringing Parquet into Apache, we believe that the community will grow
 even bigger.
 
 === Core Developers ===
 
 Parquet was initially developed as a collaboration between Twitter,
 Cloudera and Criteo.
 
 See
 https://blog.twitter.com/2013/announcing-parquet-10-columnar-storage-for-hadoop
 
 === Alignment ===
 
 We believe that having Parquet at Apache will help further the growth of
 the big-data community, as it will encourage cooperation within the greater
 ecosystem of projects spawned by Apache Hadoop. The alignment is also
 beneficial to other Apache communities (such as Hadoop, Hive, Avro).
 
 == Known Risks ==
 
 === Orphaned Products ===
 
 The risk of the Parquet project being abandoned is minimal. There are many
 organizations using Parquet in production, including Twitter, Cloudera,
 Stripe, and Salesforce (
 http://blog.cloudera.com/blog/2013/10/parquet-at-salesforce-com/).
 
 === Inexperience with Open Source ===
 
 Parquet has existed as a healthy open source for one year. During that
 time, we have

Re: Change of IPMC Chair

2014-02-03 Thread Jarek Jarcec Cecho

Congratulations Roman!

Jarcec

On Mon, Feb 03, 2014 at 06:11:42PM -0800, Henry Saputra wrote:
 Congrats Roman!
 
 On Monday, February 3, 2014, Marvin Humphrey mar...@rectangular.com wrote:
 
  Greetings,
 
  Congratulations to Roman Shaposhnik!  The Incubator PMC has voted to
  recommend
  Roman as our next Chair in a resolution to the Board next week.
 
  My wholehearted thanks go out to everyone who has contributed to a podling
  or
  otherwise worked to advance the Incubator during my tenure as Chair.  I
  look
  forward to supporting Roman and to continued collaboration with you all,
  both
  here in the Incubator and elsewhere.
 
  Marvin Humphrey
 
  -
  To unsubscribe, e-mail: 
  general-unsubscr...@incubator.apache.orgjavascript:;
  For additional commands, e-mail: 
  general-h...@incubator.apache.orgjavascript:;
 
 


signature.asc
Description: Digital signature

Re: [VOTE] Accept DataFu into the Incubator

2013-12-31 Thread Jarek Jarcec Cecho

 has released Hourglass as a sub-project of
 DataFu. Sam contributed much of the original code and continues to
 contribute to the project. Will has been contributing to DataFu since it
 was first open sourced. Evion has been contributing for the past year.
 Mathieu leads the open source Gephi project. Jakob has been actively
 involved with the ASF as a full-time Hadoop committer and PMC member.
 
 Homogeneous Developers
 
 The current core developers are all from LinkedIn. DataFu has also received
 contributions from other corporations such as Cloudera. Two of these
 developers are among the Initial Committers listed below. We hope to
 establish a developer community that includes contributors from several
 other corporations and we are actively encouraging new contributors via
 presentations and blog posts.
 
 Reliance on Salaried Developers
 
 The current core developers are salaried employees of LinkedIn, however
 they are not paid specifically to work on DataFu. Contributions to DataFu
 arise from the developers solving problems they encounter in their various
 projects. The purpose of DataFu is to share these solutions so that others
 may benefit and build a community of developers striving to solve common
 problems together. Furthermore, once the project has a community built
 around it, we expect to get committers, developers and contributions from
 outside the current core developers.
 
 Relationships with Other Apache Products
 
 DataFu is deeply integrated with Apache products. It began as a library of
 user-defined functions for Apache Pig. It has grown to also include Hadoop
 jobs for incremental data processing and in the future will include code
 for other higher level languages built on top of Apache Hadoop.
 
 An Excessive Obsession with the Apache Brand
 
 While we respect the reputation of the Apache brand and have no doubts that
 it will attract contributors and users, our interest is primarily to give
 DataFu a solid home as an open source project following an established
 development model.
 
 Documentation
 
 Information on DataFu can be found at:
 
 https://github.com/LinkedIn/DataFu/blob/master/README.md
 
 Initial Source
 
 The initial source is available at:
 
 https://github.com/LinkedIn/DataFu
 
 Source and Intellectual Property Submission Plan
 
 The DataFu library source code, available on GitHub.
 
 External Dependencies
 
 The initial source has the following external dependencies that are either
 included in the final DataFu library or required in order to use it:
 
 fastutil (Apache 2.0)
 joda-time (Apache 2.0)
 commons-math (Apache 2.0)
 guava (Apache 2.0)
 stream (Apache 2.0)
 jsr-305 (BSD)
 log4j (Apache 2.0)
 json (The JSON License)
 avro (Apache 2.0)
 
 In addition, the following external libraries are used either in building,
 developing, or testing the project:
 
 pig (Apache 2.0)
 hadoop (Apache 2.0)
 jline (BSD)
 antlr (BSD)
 commons-io (Apache 2.0)
 testng (Apache 2.0)
 maven (Apache 2.0)
 jsr-311 (CDDL-1.0)
 slf4j (MIT)
 eclipse (Eclipse Public License 1.0)
 autojar (GPLv2)
 jarjar (Apache 2.0)
 
 Cryptography
 
 DataFu has user-defined functions that use MD5 and SHA provided by Java’s
 java.security.MessageDigest.
 
 Required Resources
 
 Mailing Lists
 
 DataFu-private for private PMC discussions (with moderated subscriptions)
 DataFu-dev DataFu-commits
 
 Subversion Directory
 
 Git is the preferred source control system: git://git.apache.org/DataFu
 
 Issue Tracking
 
 JIRA DataFu (DataFu)
 
 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
 
 Matthew Hayes
 William Vaughan
 Evion Kim
 Sam Shah
 Xiangrui Meng
 Christopher Lloyd
 Mathieu Bastian
 Mitul Tiwari
 Josh Wills
 Jarek Jarcec Cecho
 
 Affiliations
 
 Matthew Hayes (LinkedIn)
 
 William Vaughan (LinkedIn)
 
 Evion Kim (LinkedIn)
 
 Sam Shah (LinkedIn)
 
 Xiangrui Meng (LinkedIn)
 
 Christopher Lloyd (LinkedIn)
 
 Mathieu Bastian (LinkedIn)
 
 Mitul Tiwari (LinkedIn)
 Josh Wills (Cloudera)
 Jarek Jarcec Cecho (Cloudera)
 
 Sponsors
 
 Champion
 
 Jakob Homan (Apache Member)
 
 Nominated Mentors
 
 Ashutosh Chauhan hashutosh at apache dot org
 
 Roman Shaposhnik rvs at apache dot org
 
 Ted Dunning tdunning at apache dot org
 
 Sponsoring Entity
 
 We are requesting the Incubator to sponsor this project.


signature.asc
Description: Digital signature

Re: [PROPOSAL] Ivory - Hadoop data management and processing platform

2013-03-13 Thread Jarek Jarcec Cecho

Hi Srikanth,
I've read the proposal and documentation available on Github and the project 
seems very interesting to me. I'm currently mainly focusing on Apache Sqoop [1] 
and I can see a lot of opportunities for integration. I'll be more than happy 
to help with Ivory going forward. In case that you're open to the idea of open 
enrolment, I'll be more than happy to sign up as initial contributor.

Jarcec

P.S. - I found few nits in the docs so I've created github pull request to fix 
them.

Links:
1: http://sqoop.apache.org/

On Wed, Mar 13, 2013 at 10:30:01PM +0530, Srikanth Sundarrajan wrote:
 = Ivory Proposal =
 
 == Abstract ==
 Ivory is a data processing and management solution for Hadoop designed for
 data motion, coordination of data pipelines, lifecycle management, and
 data discovery. Ivory enables end consumers to quickly onboard their data
 and its associated processing and management tasks on Hadoop clusters.
 
 == Proposal ==
 Ivory will enable easy data management via declarative mechanism for
 Hadoop. Users of Ivory platform simply define infrastructure endpoints,
 data sets and processing rules declaratively. These configurations
 are expressed in such a way that the dependencies between
 these entities are explicitly described. This information about
 inter-dependencies between various entities allows Ivory to orchestrate and
 manage various data management functions.
 
 The key use cases that Ivory addresses are:
  * Data Motion
  * Process orchestration and scheduling
  * Policy-based Lifecycle Management
  * Data Discovery
  * Operability/Usability
 
 With these features it is possible for users to onboard their data sets
 with
 a comprehensive and holistic understanding of how, when and where their
 data
 is managed across its lifecycle. Complex functions such as retrying
 failures,
 identifying possible SLA breaches or automated handling of input data
 changes
 are now simple directives. All the administrative functions and user level
 functions are available via RESTful APIs. CLI is simply a wrapper over the
 RESTful APIs.
 
 == Background ==
 Hadoop and its ecosystem of products have made storing and processing
 massive
 amounts of data commonplace. This has enabled numerous organizations to
 gain
 valuable insights that they never could have achieved in the past. While it
 is easy to leverage Hadoop for crunching large volumes of data, organizing
 data, managing life cycle of data and processing data is fairly involved.
 This is solved adequately well in a classic data platform involving data
 warehouses and standard ETL (extract-transform-load) tools, but remains
 largely
 unsolved today. In addition to data processing complexities, Hadoop
 presents
 new sets of challenges and opportunities relating to management of data.
 
 Data Management on Hadoop encompasses data motion, process orchestration,
 lifecycle management, data discovery, etc. among other concerns that are
 beyond
 ETL. Ivory is a new data processing and management platform for Hadoop that
 solves this problem and creates additional opportunities by building on
 existing
 components within the Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop
 DistCp
 etc.) without reinventing the wheel. Ivory has been in production at
 InMobi,
 going on its second year and has been managing hundreds of feeds and
 processes.
 
 Ivory is being developed by engineers employed with InMobi, Hortonworks and
 Yahoo!. This platform addition will increase the adoption of Apache Hadoop
 by
 driving data management tractable for end users. We are therefore proposing
 to
 make Ivory an Apache open source project.
 
 == Rationale ==
 The Ivory project aims to improve the usability of Apache Hadoop. As a
 result
 Apache Hadoop will grow its community of users by increasing the places
 Hadoop
 can be utilized and the use cases it will solve. By developing Ivory in
 Apache
 we hope to gather a diverse community of contributors, helping to ensure
 that
 Ivory is deployable for a broad range of scenarios. Members of the Hadoop
 development community will be able to influence Ivory’s roadmap, and
 contribute
 to it. We believe having Ivory as part of the Apache Hadoop ecosystem will
 be
 a great benefit to all of Hadoop's users.
 
 == Current Status ==
 Ivory is widely deployed in production within InMobi and moving on to its
 second year. A version with a valuable set of features is developed by the
 list of initial committers and is hosted on github.
 
 === Meritocracy ===
 Our intent with this incubator proposal is to start building a diverse
 developer
 community around Ivory following the Apache meritocracy model. We have
 wanted to
 make the project open source and encourage contributors from multiple
 organizations from the start. We plan to provide plenty of support to new
 developers and to quickly recruit those who make solid contributions to
 committer status.
 
 === Community ===
 We are happy to report that the initial team already

Re: [DISCUSS] Apache Mayhem proposal

2012-11-01 Thread Jarek Jarcec Cecho

I've been participating in three different projects that were moving from SVN 
to git (flume, sqoop, mrunit) and we did not experienced any issues with that 
process.

Jarcec

On Thu, Nov 01, 2012 at 12:09:43PM -0700, Craig L Russell wrote:
 
 On Nov 1, 2012, at 11:59 AM, Christian Grobmeier wrote:
 
 Hello,
 
 I would prefer GIT, even when I am not a GIT guru. The reason is
 simple:
 there is no way to save history when moving from git to svn. At
 least two
 or three incubating projects had to fight with that recently
 (Wave, Cordova
 i think). Somebody from the Apache committers started an effort to
 make a
 migration tool but its not finished to my knowledge.
 
 That said, I welcome the opportunity to work with git in a big
 team. And I
 would not like to loose history.
 
 Not sure about the entry criteria for the GIT experiment right
 now, but I
 think it should be pretty stable - lets ask infra?
 
 From what I've seen, the entry criteria are a team that wants to use
 git, and most important:
 
 volunteers from the team to work actively with infra to manage the
 git repository.
 
 Craig
 
 Cheers
 Christian
 
 
 On Thu, Nov 1, 2012 at 1:04 PM, Simone Tripodi
 simonetrip...@apache.orgwrote:
 
 Hi Mohammad,
 
 what about having SVN+Git mirror? I personally just need a SCM, don't
 have a strong preference, so recommendations are more than welcome!
 What do you suggest?
 
 Many thanks in advance, all the best!
 -Simo
 
 http://people.apache.org/~simonetripodi/
 http://simonetripodi.livejournal.com/
 http://twitter.com/simonetripodi
 http://www.99soft.org/
 
 
 On Thu, Nov 1, 2012 at 11:11 AM, Mohammad Nour El-Din
 nour.moham...@gmail.com wrote:
 Hi
 
  I noticed that the code is hosted on github but u r asking
 for an svn
 rep
 while we can have a git repo, or u don't want to continue
 using git ?
 
 Sent from my Samsung Galaxy S3
 Apologies for any typos
 On Nov 1, 2012 11:59 AM, Mohammad Nour El-Din nour.moham...@gmail.com
 
 wrote:
 
 Hi Simone
 
   I like the idea pretty much and I would like to be a
 mentor of this
 project. But I can't edit the wiki page at the moment would u
 please add
 me
 :)
 Thanks for bringing the project to ASF
 
 Sent from my Samsung Galaxy S3
 Apologies for any typos
 
 On Nov 1, 2012 10:30 AM, Eric Charles e...@apache.org wrote:
 
 I was waiting this since a long time, especially since
 guiceyfruit is
 not officially update to guice3.
 
 It's great time to do this, as more well-known 3rd parties provide
 their own extensions [1]. With such a good code base coming
 from 99soft
 foundation, we will be good on track.
 
 Big +1 and thx again,
 
 Eric
 
 [1]
 
 http://techblog.netflix.com/2012/10/governator-lifecycle-and-dependency.html
 
 
 On 31/10/2012 22:16, Christian Grobmeier wrote:
 
 I like that proposal (you have guessed it as I signed up
 to mentor).
 Guice is something cool as I found out recently. And I
 really like
 the
 logging component in there (surprise)
 
 
 On Wed, Oct 31, 2012 at 8:55 PM, Donald Whytock
 dwhyt...@gmail.com
 wrote:
 
 Just giving a post-hurricane nudge.
 
 On Tue, Oct 30, 2012 at 11:49 AM, Simone Tripodi
 simonetrip...@apache.org wrote:
 
 Hi all guys,
 
 I prepared a new proposal[1] for the incubator, concerning the
 creation of a new community focused on all aspects
 of Google Guice
 extensions, starting from a rather than small
 codebase that I and
 other friends - already ASF committers/members - would like to
 donate
 to the ASF.
 
 We still need at least one mentor, is there any
 volunteer available
 on
 joining to provide help on bringing that new community up?
 
 Many thanks in advance, all the best!!!
 -Simo
 
 [1] http://wiki.apache.org/incubator/MayhemProposal
 
 http://people.apache.org/~simonetripodi/
 http://simonetripodi.livejournal.com/
 http://twitter.com/simonetripodi
 http://www.99soft.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
 
 
 
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
 
 
 -- 
 http://www.grobmeier.de
 https://www.timeandbill.de
 
 Craig L Russell
 Architect, Oracle
 http://db.apache.org/jdo
 408 276-5638 mailto:craig.russ...@oracle.com
 P.S. A good JDO? O, Gasp!
 
 
 -
 To unsubscribe, e-mail:

Re: [DISCUSS] Apache Mayhem proposal

2012-11-01 Thread Jarek Jarcec Cecho

As was written - the repository was moved in direction SVN - GIT using git-svn 
including entire history, all branches and tags. Without any issues. 

We've luckily did not have to do the other way around (GIT - SVN), so I do 
have no experience there.

Jarcec

On Thu, Nov 01, 2012 at 11:11:15PM +0100, Christian Grobmeier wrote:
 Yes, I was mistyping of course.
 
 
 On Thu, Nov 1, 2012 at 8:57 PM, Joe Schaefer joe_schae...@yahoo.com wrote:
 
  No no no.  It's migrating from git to svn that
  we don't know how to do, going the other way
  is largely trivial with git-svn.
 
 
 
 
 
  
   From: Christian Grobmeier grobme...@gmail.com
  To: general@incubator.apache.org general@incubator.apache.org
  Sent: Thursday, November 1, 2012 3:48 PM
  Subject: Re: [DISCUSS] Apache Mayhem proposal
  
  Cool.
  
  Personally I have not the competence to do anything with git except using
  it (referencing to Craigs mail).
  Now... how did you do the history transition from svn to git?
  
  Cheers
  
  
  On Thu, Nov 1, 2012 at 8:24 PM, Jarek Jarcec Cecho jar...@apache.org
  wrote:
  
   I've been participating in three different projects that were moving
  from
   SVN to git (flume, sqoop, mrunit) and we did not experienced any issues
   with that process.
  
   Jarcec
  
   On Thu, Nov 01, 2012 at 12:09:43PM -0700, Craig L Russell wrote:
   
On Nov 1, 2012, at 11:59 AM, Christian Grobmeier wrote:
   
Hello,

I would prefer GIT, even when I am not a GIT guru. The reason is
simple:
there is no way to save history when moving from git to svn. At
least two
or three incubating projects had to fight with that recently
(Wave, Cordova
i think). Somebody from the Apache committers started an effort to
make a
migration tool but its not finished to my knowledge.

That said, I welcome the opportunity to work with git in a big
team. And I
would not like to loose history.

Not sure about the entry criteria for the GIT experiment right
now, but I
think it should be pretty stable - lets ask infra?
   
From what I've seen, the entry criteria are a team that wants to use
git, and most important:
   
volunteers from the team to work actively with infra to manage the
git repository.
   
Craig

Cheers
Christian


On Thu, Nov 1, 2012 at 1:04 PM, Simone Tripodi
simonetrip...@apache.orgwrote:

Hi Mohammad,

what about having SVN+Git mirror? I personally just need a SCM,
  don't
have a strong preference, so recommendations are more than welcome!
What do you suggest?

Many thanks in advance, all the best!
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/


On Thu, Nov 1, 2012 at 11:11 AM, Mohammad Nour El-Din
nour.moham...@gmail.com wrote:
Hi

 I noticed that the code is hosted on github but u r asking
for an svn
rep
while we can have a git repo, or u don't want to continue
using git ?

Sent from my Samsung Galaxy S3
Apologies for any typos
On Nov 1, 2012 11:59 AM, Mohammad Nour El-Din 
   nour.moham...@gmail.com

wrote:

Hi Simone

  I like the idea pretty much and I would like to be a
mentor of this
project. But I can't edit the wiki page at the moment would u
please add
me
:)
Thanks for bringing the project to ASF

Sent from my Samsung Galaxy S3
Apologies for any typos

On Nov 1, 2012 10:30 AM, Eric Charles e...@apache.org wrote:

I was waiting this since a long time, especially since
guiceyfruit is
not officially update to guice3.

It's great time to do this, as more well-known 3rd parties
  provide
their own extensions [1]. With such a good code base coming
from 99soft
foundation, we will be good on track.

Big +1 and thx again,

Eric

[1]


  
  http://techblog.netflix.com/2012/10/governator-lifecycle-and-dependency.html


On 31/10/2012 22:16, Christian Grobmeier wrote:

I like that proposal (you have guessed it as I signed up
to mentor).
Guice is something cool as I found out recently. And I
really like
the
logging component in there (surprise)


On Wed, Oct 31, 2012 at 8:55 PM, Donald Whytock
dwhyt...@gmail.com
wrote:

Just giving a post-hurricane nudge.

On Tue, Oct 30, 2012 at 11:49 AM, Simone Tripodi
simonetrip...@apache.org wrote:

Hi all guys,

I prepared a new proposal[1] for the incubator, concerning the
creation of a new community focused on all aspects
of Google Guice
extensions, starting from a rather than small
codebase that I and
other friends - already ASF committers/members - would like to
donate
to the ASF

Re: [DISCUSS] Apache Mayhem proposal

2012-11-01 Thread Jarek Jarcec Cecho

I'm sorry, I probably miss understood the intention here.

Jarcec

On Thu, Nov 01, 2012 at 11:21:22PM +0100, Christian Grobmeier wrote:
 On Thu, Nov 1, 2012 at 11:17 PM, Jarek Jarcec Cecho jar...@apache.orgwrote:
 
  As was written - the repository was moved in direction SVN - GIT using
  git-svn including entire history, all branches and tags. Without any issues.
 
  We've luckily did not have to do the other way around (GIT - SVN), so I
  do have no experience there.
 
 
 Ah ok. Then this is not what I was looking for and what I wrote about the
 problems still stands. it seems these days nobody is interested in going
 from GIT to SVN.
 
 Cheers,
 Christian
 
 
  Jarcec
 
  On Thu, Nov 01, 2012 at 11:11:15PM +0100, Christian Grobmeier wrote:
   Yes, I was mistyping of course.
  
  
   On Thu, Nov 1, 2012 at 8:57 PM, Joe Schaefer joe_schae...@yahoo.com
  wrote:
  
No no no.  It's migrating from git to svn that
we don't know how to do, going the other way
is largely trivial with git-svn.
   
   
   
   
   

 From: Christian Grobmeier grobme...@gmail.com
To: general@incubator.apache.org general@incubator.apache.org
Sent: Thursday, November 1, 2012 3:48 PM
Subject: Re: [DISCUSS] Apache Mayhem proposal

Cool.

Personally I have not the competence to do anything with git except
  using
it (referencing to Craigs mail).
Now... how did you do the history transition from svn to git?

Cheers


On Thu, Nov 1, 2012 at 8:24 PM, Jarek Jarcec Cecho jar...@apache.org
wrote:

 I've been participating in three different projects that were moving
from
 SVN to git (flume, sqoop, mrunit) and we did not experienced any
  issues
 with that process.

 Jarcec

 On Thu, Nov 01, 2012 at 12:09:43PM -0700, Craig L Russell wrote:
 
  On Nov 1, 2012, at 11:59 AM, Christian Grobmeier wrote:
 
  Hello,
  
  I would prefer GIT, even when I am not a GIT guru. The reason is
  simple:
  there is no way to save history when moving from git to svn. At
  least two
  or three incubating projects had to fight with that recently
  (Wave, Cordova
  i think). Somebody from the Apache committers started an effort
  to
  make a
  migration tool but its not finished to my knowledge.
  
  That said, I welcome the opportunity to work with git in a big
  team. And I
  would not like to loose history.
  
  Not sure about the entry criteria for the GIT experiment right
  now, but I
  think it should be pretty stable - lets ask infra?
 
  From what I've seen, the entry criteria are a team that wants to
  use
  git, and most important:
 
  volunteers from the team to work actively with infra to manage the
  git repository.
 
  Craig
  
  Cheers
  Christian
  
  
  On Thu, Nov 1, 2012 at 1:04 PM, Simone Tripodi
  simonetrip...@apache.orgwrote:
  
  Hi Mohammad,
  
  what about having SVN+Git mirror? I personally just need a SCM,
don't
  have a strong preference, so recommendations are more than
  welcome!
  What do you suggest?
  
  Many thanks in advance, all the best!
  -Simo
  
  http://people.apache.org/~simonetripodi/
  http://simonetripodi.livejournal.com/
  http://twitter.com/simonetripodi
  http://www.99soft.org/
  
  
  On Thu, Nov 1, 2012 at 11:11 AM, Mohammad Nour El-Din
  nour.moham...@gmail.com wrote:
  Hi
  
   I noticed that the code is hosted on github but u r asking
  for an svn
  rep
  while we can have a git repo, or u don't want to continue
  using git ?
  
  Sent from my Samsung Galaxy S3
  Apologies for any typos
  On Nov 1, 2012 11:59 AM, Mohammad Nour El-Din 
 nour.moham...@gmail.com
  
  wrote:
  
  Hi Simone
  
I like the idea pretty much and I would like to be a
  mentor of this
  project. But I can't edit the wiki page at the moment would u
  please add
  me
  :)
  Thanks for bringing the project to ASF
  
  Sent from my Samsung Galaxy S3
  Apologies for any typos
  
  On Nov 1, 2012 10:30 AM, Eric Charles e...@apache.org
  wrote:
  
  I was waiting this since a long time, especially since
  guiceyfruit is
  not officially update to guice3.
  
  It's great time to do this, as more well-known 3rd parties
provide
  their own extensions [1]. With such a good code base coming
  from 99soft
  foundation, we will be good on track.
  
  Big +1 and thx again,
  
  Eric
  
  [1]
  
  

   
  http://techblog.netflix.com/2012/10/governator-lifecycle-and-dependency.html
  
  
  On 31/10/2012 22:16, Christian Grobmeier wrote:
  
  I like that proposal (you have

Re: [ANNOUNCE] Welcome Roman Shaposhnik to the Apache Incubator PMC

2012-10-19 Thread Jarek Jarcec Cecho

Wow,
congratulations Roman!

Jarcec

On Oct 19, 2012, at 11:09 AM, Christian Grobmeier grobme...@gmail.com wrote:

 Welcome!
 
 On Fri, Oct 19, 2012 at 7:47 PM, Mattmann, Chris A (388J)
 chris.a.mattm...@jpl.nasa.gov wrote:
 Hey Folks,
 
 The Apache Incubator PMC has VOTEd to add Roman Shaposhnik to our ranks.
 
 Welcome, Roman! Feel free to say a bit about yourself.
 
 Cheers,
 Chris
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
 
 
 -- 
 http://www.grobmeier.de
 https://www.timeandbill.de
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 


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

Re: ${podling}.incubator.apache.org

2012-10-12 Thread Jarek Jarcec Cecho

I also like the idea of moving podling name to domain name. However I'm pretty 
indifferent between $podling.incubator.a.o and $podling.a.o, so I'm +1 on both 
(just contributor opinion).

Jarcec

On Fri, Oct 12, 2012 at 07:24:10AM -0700, Luciano Resende wrote:
 On Friday, October 12, 2012, Jukka Zitting wrote:
 
  Hi,
 
  On Fri, Oct 12, 2012 at 10:31 AM, Daniel Shahaf 
  d...@daniel.shahaf.namejavascript:;
  wrote:
   Do people mind if web sites (and maybe mailing lists) of new podlings
   live at domains of the form ${podling}.incubator.apache.org?
 
  Not at all. I'd even be fine with ${podling}.apache.org especially if
  they've already completed the PODLINGNAMESEARCH process.
 
  See http://markmail.org/message/sbpw2ifnppzd4kal for an earlier
  discussion on this that so far didn't lead to much action.
 
 
 +1 for  ${podling}.apache.org
 
 
 
 
 -- 
 Luciano Resende
 http://people.apache.org/~lresende
 http://twitter.com/lresende1975
 http://lresende.blogspot.com/


signature.asc
Description: Digital signature

Re: [VOTE] Graduate Flume podling from Apache Incubator

2012-06-05 Thread Jarek Jarcec Cecho

 [ X ] +1 Graduate Flume podling from Apache Incubator

Jarcec

On Tue, Jun 05, 2012 at 01:17:57AM -0700, Arvind Prabhakar wrote:
 This is a call for vote to graduate Flume podling from Apache Incubator.
 
 Flume entered the Incubator in June of 2011. Since then it has added nine
 new committers and made two signifiant releases following the ASF policies
 and guidelines. The community of Flume is active, healthy and growing and
 has demonstrated the ability to self-govern using accepted
 Apache practices. Flume community has voted to proceed with graduation [1]
 and the result can be found at [2].
 
 Please cast your votes:
 
 [  ] +1 Graduate Flume podling from Apache Incubator
 [  ] +0 Indifferent to the graduation status of Flume podling
 [  ] -1 Reject graduation of Flume podling from Apache Incubator
 
 This vote will be open for 72 hours. Please find the proposed board
 resolution below.
 
 [1] http://s.apache.org/Ckq
 [2] http://s.apache.org/DBv
 
 Regards,
 Arvind Prabhakar
 
 
 X. Establish the Apache Flume 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 aggregating
large amounts of log data on Apache Hadoop's HDFS and
other scalable storage systems 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 Flume Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
 
RESOLVED, that the Apache Flume Project be and hereby is
responsible for the creation and maintenance of software
related to  a system for aggregating large amounts of log
data on Apache Hadoop's HDFS and other scalable storage
systems; and be it further
 
RESOLVED, that the office of Vice President, Apache Flume 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 Flume Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Flume 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 Flume Project:
 
  * Aaron Kimball  kimba...@apache.org
  * Andrew Bayer   aba...@apache.org
  * Ahmed Radwan   ah...@apache.org
  * Arvind Prabhakar   arv...@apache.org
  * Brock Noland   br...@apache.org
  * Bruce Mitchenerbru...@apache.org
  * Derek Deeter   ddee...@apache.org
  * Eric Sammeresam...@apache.org
  * Hari Shreedharan   hshreedha...@apache.org
  * Henry Robinson he...@apache.org
  * Jaroslav Cecho jar...@apache.org
  * Jonathan Hsieh jmhs...@apache.org
  * Juhani Connollyjuha...@apache.org
  * Mike Percy mpe...@apache.org
  * Mingjie Laim...@apache.org
  * Nick Verbeck   nerdyn...@apache.org
  * Patrick Hunt   ph...@apache.org
  * Prasad Mujumdarpras...@apache.org
  * Ralph Goersrgo...@apache.org
  * Will McQueen   w...@apache.org
 
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Arvind Prabhakar
be appointed to the office of Vice President, Apache Flume, 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 Flume 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 Flume Project; and be it further
 
RESOLVED, that the Apache Flume Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Flume podling; and be it further
 
RESOLVED, that all responsibilities pertaining to the Apache
Incubator Flume podling encumbered upon the Apache Incubator
Project are hereafter discharged.


signature.asc
Description: Digital signature

Re: [VOTE] Graduate Sqoop podling from Apache Incubator

2012-02-28 Thread Jarek Jarcec Cecho

Hi Alex and Alan,
we already moved entire logic to org.apache namespace. We're keeping classes in 
com.cloudera in place only for compatibility with tools that are based on sqoop 
(for example various connectors). However those classes do not contain any 
logic, they are just inheriting from org.apache namespace and do nothing. Let 
me show you what I mean on following example:

https://svn.apache.org/repos/asf/incubator/sqoop/trunk/src/java/com/cloudera/sqoop/manager/MySQLManager.java

All other files in com.cloudera namespace have similar structure. They are just 
skeleton code that is in place for compatibility without any logic (additional 
code).

Do we really need to remove entirely com.cloudera namespace or is this state 
acceptable for graduating?

Jarcec

On Tue, Feb 28, 2012 at 10:39:35AM +0200, Alex Karasulu wrote:
 On Mon, Feb 27, 2012 at 10:10 PM, Alan Gates ga...@hortonworks.com wrote:
 
  The source code in Sqoop still exists in both com.cloudera.sqoop and
  org.apache.sqoop packages and most of the code appears to include the
  com.cloudera packages and not the org.apache packages.  While in the
  incubator this seems fine.  Are we ok with this in a TLP?  I couldn't find
  any policy statements on it in the Apache pages.
 
 
 Good catch Alan. You are right we are not OK with this situation. It needs
 to be corrected then another vote can be taken.
 
 Thanks,
 Alex
 
 
 
  On Feb 24, 2012, at 1:34 PM, Arvind Prabhakar wrote:
 
   This is a call for vote to graduate Sqoop podling from Apache Incubator.
  
   Sqoop entered Incubator in June of 2011. Since then it has added three
   new committers from diverse organizations, added two new PPMC members,
   and made two releases following the ASF policies and guidelines. The
   community of Sqoop is active, healthy and growing and has demonstrated
   the ability to self-govern using accepted Apache practices. Sqoop
   community has voted to proceed with graduation [1] and the result can
   be found at [2].
  
   Please cast your votes:
  
   [  ] +1 Graduate Sqoop podling from Apache Incubator
   [  ] +0 Indifferent to the graduation status of Sqoop podling
   [  ] -1 Reject graduation of Sqoop podling from Apache Incubator
  
   This vote will be open for 72 hours. Please find the proposed board
   resolution below.
  
   [1] http://markmail.org/thread/xwhjtkik7pgrmypi
   [2] http://s.apache.org/sqoop
  
   Thanks,
   Arvind Prabhakar
  
   X. Establish the Apache Sqoop 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 efficiently transferring
 bulk data between Apache Hadoop and structured datastores
 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 Sqoop Project,
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further
  
 RESOLVED, that the Apache Sqoop Project be and hereby is
 responsible for the creation and maintenance of software
 related to efficiently transferring bulk data between Apache
 Hadoop and structured datastores; and be it further
  
 RESOLVED, that the office of Vice President, Apache Sqoop 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 Sqoop Project, and to have primary responsibility
 for management of the projects within the scope of
 responsibility of the Apache Sqoop 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 Sqoop Project:
  
   * Aaron Kimball kimba...@apache.org
   * Andrew Bayer  aba...@apache.org
   * Ahmed Radwan  ah...@apache.org
   * Arvind Prabhakar  arv...@apache.org
   * Bilung Leeb...@apache.org
   * Greg Cottman  gcott...@apache.org
   * Guy le Marguyle...@apache.org
   * Jaroslav Cechojar...@apache.org
   * Jonathan Hsiehjmhs...@apache.org
   * Olivier Lamy  ol...@apache.org
   * Paul Zimdars  pzimd...@apache.org
   * Roman Shaposhnik  r...@apache.org
  
 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Arvind Prabhakar
 be appointed to the office of Vice President, Apache Sqoop, to
 serve in accordance with and subject to the direction of the
 Board of Directors and the Bylaws of the Foundation until

'' Re: [VOTE] Graduate Sqoop podling from Apache Incubator

2012-02-24 Thread Jarek Jarcec Cecho

[ X ] +1 Graduate Sqoop podling from Apache Incubator (Non-binding)

Jarcec

On Fri, Feb 24, 2012 at 01:34:09PM -0800, Arvind Prabhakar wrote:
 This is a call for vote to graduate Sqoop podling from Apache Incubator.
 
 Sqoop entered Incubator in June of 2011. Since then it has added three
 new committers from diverse organizations, added two new PPMC members,
 and made two releases following the ASF policies and guidelines. The
 community of Sqoop is active, healthy and growing and has demonstrated
 the ability to self-govern using accepted Apache practices. Sqoop
 community has voted to proceed with graduation [1] and the result can
 be found at [2].
 
 Please cast your votes:
 
 [  ] +1 Graduate Sqoop podling from Apache Incubator
 [  ] +0 Indifferent to the graduation status of Sqoop podling
 [  ] -1 Reject graduation of Sqoop podling from Apache Incubator
 
 This vote will be open for 72 hours. Please find the proposed board
 resolution below.
 
 [1] http://markmail.org/thread/xwhjtkik7pgrmypi
 [2] http://s.apache.org/sqoop
 
 Thanks,
 Arvind Prabhakar
 
 X. Establish the Apache Sqoop 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 efficiently transferring
bulk data between Apache Hadoop and structured datastores
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 Sqoop Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
 
RESOLVED, that the Apache Sqoop Project be and hereby is
responsible for the creation and maintenance of software
related to efficiently transferring bulk data between Apache
Hadoop and structured datastores; and be it further
 
RESOLVED, that the office of Vice President, Apache Sqoop 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 Sqoop Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Sqoop 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 Sqoop Project:
 
  * Aaron Kimball kimba...@apache.org
  * Andrew Bayer  aba...@apache.org
  * Ahmed Radwan  ah...@apache.org
  * Arvind Prabhakar  arv...@apache.org
  * Bilung Leeb...@apache.org
  * Greg Cottman  gcott...@apache.org
  * Guy le Marguyle...@apache.org
  * Jaroslav Cechojar...@apache.org
  * Jonathan Hsiehjmhs...@apache.org
  * Olivier Lamy  ol...@apache.org
  * Paul Zimdars  pzimd...@apache.org
  * Roman Shaposhnik  r...@apache.org
 
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Arvind Prabhakar
be appointed to the office of Vice President, Apache Sqoop, 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 Sqoop 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 Sqoop Project; and be it further
 
RESOLVED, that the Apache Sqoop Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Sqoop podling; and be it further
 
RESOLVED, that all responsibilities pertaining to the Apache
Incubator Sqoop 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
 


signature.asc
Description: Digital signature

Re: [VOTE] Graduate Sqoop from Apache Incubator

2012-02-19 Thread Jarek Jarcec Cecho

+1

Jarcec

On Sun, Feb 19, 2012 at 01:00:57AM -0800, Arvind Prabhakar wrote:
 The Apache Sqoop project entered incubator in June of 2011. Since then we
 have added three new committers from diverse organizations and added two
 new PPMC members. The codebase of our product has steadily grown and we
 have made two releases following the ASF policies and guidelines. Thanks to
 the excellent mentorship we have received through this period, we have
 learnt to self-govern and grow our community using accepted Apache
 practices. Sqoop continues to attract interest from contributors and users
 from all across the world.
 
 Given these milestones, I strongly feel that Sqoop is ready to graduate
 from Incubator.
 
 The first step towards graduation is to vote as a community that Sqoop is
 ready to graduate. If the vote is successful, we will draft a board
 resolution proposal and call it to vote on the general Incubator list. The
 complete graduation process is described [1].
 
 Please cast your votes:
 
 [  ]  +1 Graduate Sqoop from Incubator
 [  ]  +0 Indifferent to graduation status of Sqoop
 [  ]  +1 Reject graduation of Sqoop from Incubator
 
 This vote will remain open for at least 72 hours from now.
 
 [1] http://incubator.apache.org/guides/graduation.html
 
 Thanks,
 Arvind Prabhakar


signature.asc
Description: Digital signature

Re: [VOTE] Graduate Sqoop from Apache

2012-02-19 Thread Jarek Jarcec Cecho

+1.

Jarcec

On Sun, Feb 19, 2012 at 09:22:01AM -0800, Arvind Prabhakar wrote:
 The Apache Sqoop project entered incubator in June of 2011. Since then we
 have added three new committers from diverse organizations and added two
 new PPMC members. The codebase of our product has steadily grown and we
 have made two releases following the ASF policies and guidelines. Thanks to
 the excellent mentorship we have received through this period, we have
 learnt to self-govern and grow our community using accepted Apache
 practices. Sqoop continues to attract interest from contributors and users
 from all across the world.
 
 Given these milestones, I strongly feel that Sqoop is ready to graduate
 from Incubator.
 
 The first step towards graduation is to vote as a community that Sqoop is
 ready to graduate. If the vote is successful, we will draft a board
 resolution proposal and call it to vote on the general Incubator list. The
 complete graduation process is described [1].
 
 Please cast your votes:
 
 [  ]  +1 Graduate Sqoop from Incubator
 [  ]  +0 Indifferent to graduation status of Sqoop
 [  ]  -1 Reject graduation of Sqoop from Incubator
 
 This vote will remain open for at least 72 hours from now.
 
 [1] http://incubator.apache.org/guides/graduation.html
 
 Thanks,
 Arvind Prabhakar


signature.asc
Description: Digital signature

Re: [VOTE] Release Sqoop version 1.4.1-incubating

2012-02-14 Thread Jarek Jarcec Cecho

I'm closing this vote. I'll sent results shortly. Thanks to everyone who 
participated!

Jarcec

On Mon, Feb 13, 2012 at 06:38:16PM +0100, Jarek Jarcec Cecho 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.
 
 I'm resending this email again without original RE: prefix in subject to 
 stress that this is new vote.
 
 Thanks,
 Jarcec
 
 *** 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




signature.asc
Description: Digital signature

[RESULT][VOTE] Release Sqoop version 1.4.1-incubating

2012-02-14 Thread Jarek Jarcec Cecho

The vote now passes with 3 +1 binding votes (including 1 from dev list vote):
Tom White
Patrick Hunt
Olivier Lamy (dev list vote)

Thanks for everyone who has reviewed and voted!

There was one note with slightly outdated year in one license that will be 
addressed in next release. I will continue with the release process.

Jarcec

On Tue, Feb 14, 2012 at 07:33:03PM +0100, Jarek Jarcec Cecho wrote:
 I'm closing this vote. I'll sent results shortly. Thanks to everyone who 
 participated!
 
 Jarcec
 
 On Mon, Feb 13, 2012 at 06:38:16PM +0100, Jarek Jarcec Cecho 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.
  
  I'm resending this email again without original RE: prefix in subject to 
  stress that this is new vote.
  
  Thanks,
  Jarcec
  
  *** 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
 
 




signature.asc
Description: Digital signature

Re: [RESULT][VOTE] Release Sqoop version 1.4.1-incubating

2012-02-14 Thread Jarek Jarcec Cecho

Hi Roman,
we're definitely open to embrace any Apache policy for naming files. Can you 
point me to some written docs?

We're currently appending -src postfix to stress out that it's only source 
artifact whereas other artifacts also contains binaries.

Jarcec

On Tue, Feb 14, 2012 at 02:27:35PM -0800, Roman Shaposhnik wrote:
 On Tue, Feb 14, 2012 at 10:38 AM, Jarek Jarcec Cecho jar...@apache.org 
 wrote:
  The vote now passes with 3 +1 binding votes (including 1 from dev list 
  vote):
  Tom White
  Patrick Hunt
  Olivier Lamy (dev list vote)
 
  Thanks for everyone who has reviewed and voted!
 
  There was one note with slightly outdated year in one license that will be 
  addressed in next release.
  I will continue with the release process.
 
 One small cosmetic nit: is there any chance to drop the -src postfix
 from the release tarball
 (and top level subdirectory)? Not a big deal, but inconsistent with
 all the other release tarballs
 from the Apache incubator.
 
 Thanks,
 Roman.
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 


signature.asc
Description: Digital signature

Re: [RESULT][VOTE] Release Sqoop version 1.4.1-incubating

2012-02-14 Thread Jarek Jarcec Cecho

Thank you very much for your comment Roman. I didn't know that we're causing 
you problems by using different naming convention than other hadoop related 
projects.

I've filled JIRA SQOOP-439 to make this change happen.

Jarcec

On Tue, Feb 14, 2012 at 11:42:20PM -0800, Roman Shaposhnik wrote:
 Hi!
 
 On Tue, Feb 14, 2012 at 11:31 PM, Jarek Jarcec Cecho jar...@apache.org 
 wrote:
  Hi Roman,
  we're definitely open to embrace any Apache policy for naming files. Can 
  you point me to some written docs?
 
 AFAIK, it would be fair to say that Apache, in general, is all
 about source releases. The binary artifacts are simply convenience
 artifacts and thus it makes sense that the default tarballs are
 source tarballs.
 
 I'm not sure I can quote chapter and verse, my experience comes from
 doing Apache Bigtop
 Project which is an integration point between at least a dozen
 different Apache projects.
 When I pulled your RC into Bigtop the other day it was the only
 project that I had to modify
 my scripts for. Everything else follows the most default naming convention.
 
 Hope this helps.
 
 Thanks,
 Roman.
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 


signature.asc
Description: Digital signature

[VOTE] Release Sqoop version 1.4.1-incubating

2012-02-13 Thread Jarek Jarcec Cecho

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.

I'm resending this email again without original RE: prefix in subject to 
stress that this is new vote.

Thanks,
Jarcec

*** 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


signature.asc
Description: Digital signature

Re: [VOTE] Release Sqoop version 1.4.1-incubating

2012-02-13 Thread Jarek Jarcec Cecho

Thank you for your feedback sir. If it's not an blocker, we will fix that in 
next release.

Jarcec

On Tue, Feb 14, 2012 at 12:41:00AM +, sebb wrote:
 On 10 February 2012 19:27, 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
 
 
 NOTICE file is slightly dated:
 
 Apache Sqoop
 Copyright 2011 The Apache Software Foundation
 
 
  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
 


signature.asc
Description: Digital signature

Re: [VOTE] Release Sqoop version 1.4.1-incubating

2012-02-12 Thread Jarek Jarcec Cecho

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


signature.asc
Description: Digital signature

[VOTE] Release Sqoop version 1.4.1-incubating

2012-02-10 Thread Jarek Jarcec Cecho

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


signature.asc
Description: Digital signature

Re: [VOTE] Accept Spot into the Apache Incubator

Re: [VOTE] Accept Gearpump into the Apache Incubator

Re: [VOTE] Graduate Sentry

Re: [VOTE] Graduate Sentry from the Incubator

Re: [VOTE] Accept Impala into the Apache Incubator

Re: [VOTE] Accept Kudu into the Apache Incubator

Re: [VOTE] Release Sentry incubating version 1.6.0 (rc0)

Re: [VOTE] Release Sentry incubating version 1.5.1 (rc0)

Re: [VOTE] Accept Parquet into the incubator

Re: Change of IPMC Chair

Re: [VOTE] Accept DataFu into the Incubator

Re: [PROPOSAL] Ivory - Hadoop data management and processing platform

Re: [DISCUSS] Apache Mayhem proposal

Re: [DISCUSS] Apache Mayhem proposal

Re: [DISCUSS] Apache Mayhem proposal

Re: [ANNOUNCE] Welcome Roman Shaposhnik to the Apache Incubator PMC

Re: ${podling}.incubator.apache.org

Re: [VOTE] Graduate Flume podling from Apache Incubator

Re: [VOTE] Graduate Sqoop podling from Apache Incubator

'' Re: [VOTE] Graduate Sqoop podling from Apache Incubator

Re: [VOTE] Graduate Sqoop from Apache Incubator

Re: [VOTE] Graduate Sqoop from Apache

Re: [VOTE] Release Sqoop version 1.4.1-incubating

[RESULT][VOTE] Release Sqoop version 1.4.1-incubating

Re: [RESULT][VOTE] Release Sqoop version 1.4.1-incubating

Re: [RESULT][VOTE] Release Sqoop version 1.4.1-incubating

[VOTE] Release Sqoop version 1.4.1-incubating

Re: [VOTE] Release Sqoop version 1.4.1-incubating

Re: [VOTE] Release Sqoop version 1.4.1-incubating

[VOTE] Release Sqoop version 1.4.1-incubating

30 matches

Site Navigation

Mail list logo

Footer information