Re: [VOTE] Apache Ambari 1.2.5-incubating RC1

[Devaraj Das]

+1 (binding)

On Mon, Sep 9, 2013 at 1:29 PM, Arun C Murthy  wrote:
> +1 (binding)
>
> Missed ambari-dev@ in prev. response.
>
> Arun
>
> On Sep 4, 2013, at 10:39 AM, Sumit Mohanty  wrote:
>
>> Hi all,
>>
>> ambari-1.2.5-incubating-rc0 release candidate is now available.
>>
>> Here's a summary of what's new in Ambari 1.2.5:
>> * Added support to setup Ganglia and Nagios HTTPS
>> * Added support to run Ambari Server as non-root account.
>> * Added ability to manage Kerberos Secure Cluster.
>> * Added support to setup Ambari Server HTTPS.
>> * Enabled Ambari Server configuration property encryption.
>> * Added support to configure Ambari Server-Agent Two-Way SSL Communication.
>> * Added ability to customize Dashboard Widgets.
>> * Improved Host Checks during Install Wizard
>>
>> I have successfully deployed a 3-node cluster on RHEL 6.3 using the
>> instructions available at:
>> http://incubator.apache.org/ambari/1.2.5/installing-hadoop-using-ambari/cont
>> ent/index.html
>>
>> Git source tag:
>> https://git-wip-us.apache.org/repos/asf/incubator-ambari/repo?p=incubator-am
>> bari.git;a=log;h=refs/tags/release-1.2.5-rc0
>>
>> Staging site:
>> http://people.apache.org/~smohanty/ambari-release-1.2.5-rc0/
>>
>> PGP release keys (signed using 791FDAB0)
>> http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0xECFC8276791FDAB0
>>
>> One can look into the issues fixed in this release at:
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fi
>> xVersion%20%3D%20%221.2.5%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20
>> priority%20DESC
>>
>> Vote will be open for 72 hours.
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>> Here's my vote to start: +1 (binding)
>>
>> Sumit
>>
>>
>>
>> --
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity to
>> which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender immediately
>> and delete it from your system. Thank You.
>
> --
> Arun C. Murthy
> Hortonworks Inc.
> http://hortonworks.com/
>
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

-
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

[Devaraj Das]

dation.
>>
>> == External Dependencies ==
>>
>> To the best of our knowledge, all of Storm dependencies (except
>> 0MQ/JMQ) are distributed under Apache compatible licenses. Upon
>> acceptance to the incubator, we would begin a thorough analysis of all
>> transitive dependencies to verify this fact and introduce license
>> checking into the build and release process (for instance integrating
>> Apache Rat).
>>
>> Storm has used 0MQ and JMQ as the default mechanism for internal
>> messaging layer, and 0MQ/JMQ is licensed under GNU Lesser General
>> Public License. Recently, we have made Storm messaging layer
>> pluggable, and plan to use Netty (which is licensed under Apache
>> License v2) as our default messaging plugin (while keep 0MQ as an
>> optional plugin).
>>
>> == Cryptography ==
>>
>> We do not expect Storm to be a controlled export item due to the use
>> of encryption.
>> Storm enable encryptions via 2 plugins:
>>* SASL authentication plugins … Currently, we have provide “no-op”
>> authentication and digest authentication. In near future, we will
>> introduce Kerberos authentication.
>>* Tuple payload serialization plugins … Storm provides plugins for
>> plain-object serialization and blowfish encryption.
>>
>> == Required Resources ==
>>
>> === Mailing lists ===
>>
>>  * storm-user
>>  * storm-dev
>>  * storm-commits
>>  * storm-private (with moderated subscriptions)
>>
>> === Subversion Directory ===
>>
>> Git is the preferred source control system: git://git.apache.org/storm
>>
>>
>> === Issue Tracking ===
>>
>> JIRA Storm (STORM)
>>
>> == Initial Committers ==
>>
>>* Nathan Marz 
>>* James Xu 
>>* Jason Jackson 
>>* Andy Feng 
>>* Flip Kromer  
>>* David Lao 
>>* P. Taylor Goetz 
>>
>> == Affiliations ==
>>
>>* Nathan Marz - Nathan’s Startup
>>* James Xu - Alibaba
>>* Jason Jackson - Twitter
>>* Andy Feng - Yahoo!
>>* Flip Kromer - Infochimps
>>* David Lao - Microsoft
>>* P. Taylor Goetz - Health Market Science
>>
>> == Sponsors ==
>>
>>
>> === Champion ===
>>
>>* Doug Cutting  
>>
>> === Nominated Mentors ===
>>
>>   * Ted Dunning 
>>   * Arvind Prabhakar 
>>   * Devaraj Das 
>>   * Matt Franklin 
>>   * Benjamin Hindman 
>>
>> === Sponsoring Entity ===
>>
>>  The Apache Incubator
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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

Re: [VOTE] Apache Ambari 1.4.1-incubating RC1

[Devaraj Das]

+1. Downloaded, built and ran tests.


On Thu, Oct 17, 2013 at 1:38 PM, Siddharth Wagle wrote:

> Hi all,
>
> ambari-1.4.1-incubating-rc0 release candidate is now available.
>
> Here's a summary of what's new in Ambari 1.4.1:
>
> * Ability to deploy and manage the Hadoop 2.0 stack using Ambari
> * Ability to enable Namenode HA
> * Added support for enabling Kerberos based security for Hadoop 2.0
> services
> * Support for Ambari to work with SSL enabled Hadoop daemons
> * Support for Ambari to work with web authentication enabled for Hadoop
> daemons
> * Added support for JDK 7
>
>
> Git source tag:
>
> https://git-wip-us.apache.org/repos/asf/incubator-ambari/repo?p=incubator-ambari.git;a=log;h=refs/tags/release-1.4.1-rc0
>
> Staging site:
> http://people.apache.org/~swagle/ambari-release-1.4.1-rc0/
>
> PGP release keys (signed using F0708AB4)
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2317E1CEF0708AB4
>
> One can look into the issues fixed in this release at:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%20%221.4.1%22%20AND%20status%20in%20%28Resolved%2C%20Closed%29
>
> Instructions to build Ambari-1.4.1:
>
> https://cwiki.apache.org/confluence/display/AMBARI/Instructions+to+install+Ambari-1.4.1+bits
>
> Vote will be open for 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [VOTE] Graduate Ambari from Apache Incubator

[Devaraj Das]

+1 (binding) for graduation


On Fri, Nov 15, 2013 at 9:12 AM, Yusaku Sako  wrote:

> This is a call for vote to graduate Ambari from Apache Incubator.
>
> The Apache Ambari project has been incubating since August 2011.
> We have made significant progress with the project during the two years
> of Incubation, adding 27 committers for a total of 36 committers [1], and
> producing 8 releases following ASF policies and guidelines.
> The Apache Ambari community has voted to graduate Ambari as a TLP [2].
> The community vote results can be found at [3].
> The discussion thread for the board resolution can be found at [4].
>
> Please cast your votes:
>
> [  ] +1 Graduate Ambari from Incubator
> [  ] +0 Indifferent to graduation status of Ambari
> [  ] -1 Reject graduation of Ambari from Incubator
>
> This vote will remain open for at least 72 hours from now.
> Please find the proposed board resolution below.
>
> [1] http://people.apache.org/committers-by-project.html#ambari
> [2] http://markmail.org/thread/cp5ajf2uvfl3oj66
> [3] http://markmail.org/message/l6zss4rgfcs3gvpm
> [4] http://markmail.org/thread/36dplr3pwzmazwmg
>
> Regards,
> Yusaku Sako
>
> ###
>
> X. Establish the Apache Ambari 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 Hadoop cluster management.
>
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "Apache Ambari Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
>
>   RESOLVED, that the Apache Ambari Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to Hadoop cluster management;
>   and be it further
>
>   RESOLVED, that the office of "Vice President, Apache Ambari" 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 Ambari Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache Ambari 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 Ambari Project:
>
> * Babiichuk Andriy (ababiichuk)
> * Arun Murthy (acmurthy)
> * Aleksandr Kovalenko (akovalenko)
> * Antonenko Aleksandr Igorevich (alexantonenko)
> * Andrii Tkach (atkach)
> * Bernd Fondermann (berndf)
> * Billie Rinaldi (billie)
> * Christopher Douglas (cdouglas)
> * Chad Roberts (croberts)
> * Devaraj Das (ddas)
> * Dmitry Lysnichenko (dmitriusan)
> * Dmytro Sen (dsen)
> * Eric Yang (eyang)
> * Hitesh Shah (hitesh)
> * Jagane Sundar (jagane)
> * Jaimin Jetly (jaimin)
> * Jitendra Pandey (jitendra)
> * John Speidel (jspeidel)
> * Kan Zhang (kzhang)
> * Mahadev Konar (mahadev)
> * Papirkovskyy Myroslav (mpapirkovskyy)
> * Nate Cole (ncole)
> * Oleksandr Diachenko (odiachenko)
> * Owen O’Malley (omalley)
> * Oleg Nechiporenko (onechiporenko)
> * Ramya Sunil (ramya)
> * Varun Kapoor (reznor)
> * Sumit Mohanty (smohanty)
> * Srimanth Gunturi (srimanth)
> * Siddharth Wagle (swagle)
> * Thomas Beerbower (tbeerbower)
> * Suhas (vgogate)
> * Vikram Dixit K (vikram)
> * Vinod Kumar Vavilapalli (vinodkv)
> * Xi Wang (xiwang)
> * Yusaku Sako (yusaku)
>
>
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Yusaku Sako
>   be appointed to the office of Vice President, Apache Ambari, 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 Ambari 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 Ambari Project; and be it further
>
>   RESO

Re: [VOTE] Release Apache Knox-0.3.1-incubating RC3

[Devaraj Das]

+1 on the RC. Downloaded, built and ran unit tests.


On Mon, Nov 25, 2013 at 8:00 PM, larry mccay  wrote:

> Hello All -
>
> Just to follow up on this thread, we will have these NOTICES file issues
> corrected in the next release and assume that this VOTE will continue in
> the absence of a -1 vote.
>
> Thank you again, for the insight here.
>
> --larry
>
>
> On Sat, Nov 23, 2013 at 10:40 AM, larry mccay 
> wrote:
>
> > Hi Sebb -
> >
> > Thank you for your review and insight!
> >
> > We will make these changes immediately and insure that they are correct
> > going forward.
> >
> > Do these issues require a new release candidate - or would that only be
> > indicated by a -1?
> >
> > thanks,
> >
> > --larry
> >
> >
> > On Sat, Nov 23, 2013 at 10:23 AM, sebb  wrote:
> >
> >> On 20 November 2013 16:09, larry mccay  wrote:
> >> > Hello All,
> >> >
> >> > This is a call for a vote on Apache Knox Gateway 0.3.1 incubating.
> >> >
> >> > A vote was held on developer mailing list and it passed with 3 +1's,
> >> and 0
> >> > -1's or +0's and now
> >> > requires a vote on general@incubator.apache.org.
> >> >
> >> > The [VOTE] thread can be found at:
> >> >
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-knox-dev/201311.mbox/%3CCACRbFyjgLrCSahhtWWHK-%3DaeQFM4Oegbe3fQjs-RV2-TAnhdxA%40mail.gmail.com%3E
> >> >
> >> > The release candidate is a zip archive of the sources in:
> >> > https://git-wip-us.apache.org/repos/asf/incubator-knox.git
> >> > Branch v0.3.1 (git checkout -b v0.3.1)
> >> >
> >> > Tag:
> >> >
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-knox.git;a=tag;h=5a907022dbc2b0a8534de47fe7b8c871c4f075f9
> >>
> >> The NOTICE file is wrong; the first 6 lines should be removed (i.e.
> >> lines with == and following blank line)
> >>
> >> Also, the text should be:
> >>
> >> "This product includes software developed at"
> >> not
> >> "This product includes software developed by"
> >>
> >> > Source archive zip file and signature are available from:
> >> >
> >>
> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.1/knox-incubating-0.3.1-src.zip
> >> >
> >>
> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.1/knox-incubating-0.3.1-src.zip.asc
> >> >
> >> > Checksums of the source archive:
> >> >   SHA1:   04bb11360f57c0431c30cfb181e3199868fe6053
> >> >
> >> > The KEYS file can be found at:
> >> >
> >> >
> >>
> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.1/KEYS
> >>
> >> The KEYS file should really be at the top level of the release area,
> i.e.
> >>
> >> https://dist.apache.org/repos/dist/release/incubator/knox/KEYS
> >>
> >> > The release changes file can be found at:
> >> >
> >> >
> >>
> https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.1/CHANGES
> >> >
> >> > The release has been signed with key (587C089B):
> >> >
> >> http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x82F9C371587C089B
> >> >
> >> > Vote will be open for 72 hours.
> >> >
> >> > thanks,
> >> >
> >> > --larry
> >> >
> >> > Larry McCay
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
> >
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [VOTE] Phoenix for incubator project

[Devaraj Das]

t; Mailing list
> >
> > We will migrate the existing Phoenix mailing lists as follows:
> >
> > phoenix-hbase-u...@googlegroups.com -->
> us...@phoenix.incubator.apache.org
> >
> > phoenix-hbase-...@googlegroups.com --> d...@phoenix.incubator.apache.org
> >
> > priv...@phoenix.incubator.apache.org for IPMC members
> >
> > comm...@phoenix.incubator.apache.org
> >
> > The latter is to be consistent with the new PIAO naming scheme for
> > podlings.
> >
> > Source control
> >
> > The Phoenix team would like to use Git for source control, due to our
> > current use of Git. We request a writeable Git repo for Phoenix, and
> > mirroring to be set up to Github through INFRA.
> >
> > Issue Tracking
> >
> > Phoenix currently uses the github issue tracking system associated with
> its
> > github repo:
> >
> >
> https://github.com/forcedotcom/phoenix/issues?direction=desc&sort=updated&state=open
> > .
> > We will migrate to the Apache JIRA:
> > http://issues.apache.org/jira/browse/PHOENIX
> >
> > Other Resources
> >
> > Jenkins/Hudson for builds and test running.
> > Wiki for documentation purposes
> > Blog to improve project dissemination
> >
> > Initial Committers
> >
> > James Taylor 
> >
> > Mujtaba Chohan 
> >
> > Jesse Yates 
> >
> > Eli Levine 
> >
> > Simon Toens 
> >
> > Maryann Xue 
> >
> > Anoop Sam John 
> >
> > Ramkrishna S Vasudevan 
> >
> > Jeffrey Zhong 
> >
> > Nick Dimiduk 
> >
> > Affiliations
> >
> > The initial committers are from three organizations: Salesforce.com,
> Intel,
> > and Hortonworks.
> >
> > James Taylor (Salesforce.com)
> > Mujtaba Chohan (Salesforce.com)
> > Jesse Yates (Salesforce.com)
> > Eli Levine (Salesforce.com)
> > Simon Toens (Salesforce.com)
> > Maryann Xue (Intel)
> > Anoop Sam John (Intel)
> > Ramkrishna S Vasudevan (Intel)
> > Jeffrey Zhong (Hortonworks)
> > Nick Dimiduk (Hortonworks)
> >
> > Sponsors
> >
> > Champion
> >
> > Michael Stack
> >
> > Nominated Mentors
> >
> > Michael Stack
> > Lars Hofhansl
> > Andrew Purtell
> > Devaraj Das
> > Enis Soztutar
> > Steven Noels
> >
> > Sponsoring Entity
> >
> > The Apache Incubator
> >
>
>
>
> --
> // Jonathan Hsieh (shay)
> // Software Engineer, Cloudera
> // j...@cloudera.com
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: Hoya Proposal

[Devaraj Das]

Andreas, to me, Twill is a library, a convenience library, that one
can use to write Yarn apps. Hoya aims to provide a general framework
using which one can take existing apps (HBase/Accumulo to start with),
and make them run well in a Yarn cluster, without intruding at all
into the App internals. The goal is to have minimal, ideally zero
changes, in the App itself. The only glue between the App and Hoya is
a Hoya interface that the App needs to implement for it to be
deployable/manageable by Hoya.

Although, one could argue that Hoya can be written using Twill
libraries (which is something we should pursue as part of
long/medium-term collaboration between the two projects), but I'd
argue that the goals of the two projects are different - Twill would
continue to make Yarn app developers' lives easier, while Hoya is a
tool that could deploy distributed-frameworks easily in a Yarn
cluster, and be able to later do basic management (as is talked about
in the github docs). Things like dynamic configuration patching for
the applications like HBase to easily run in a Yarn cluster, security
issues, failure handling and defining a model for reacting to
failures, being able to store some state about applications to
facilitate better application restart behavior in a Yarn cluster, etc.
would be in the purview of Hoya. Management frameworks could use Hoya
as a tool as well to talk to Yarn and do application
start/stop/shrink/expand an instance of an application (e.g. HBase)
cluster.

On Thu, Jan 16, 2014 at 4:38 PM, Andreas Neumann  wrote:
> I do see a lot of value in all the features of Hoya, and I am not trying to
> discredit it. Yet I do think that most of these features are actually
> already in Twill or would be great additions to Twill, and sooner or later
> will be implemented in Twill, implying even greater overlap.
>
> I am not sure whether I follow the distinction between porting an existing
> app and developing a new app, if both require similar abstractions... And
> after all, porting an existing application is one way to start developing a
> Yarn application.
>
> Anyway, I just wanted to point out the overlap and offer collaboration. If
> the community thinks that the two projects are different beasts, that's
> fine with me.
>
>
> On Wed, Jan 15, 2014 at 10:40 AM, Josh Elser  wrote:
>
>> I wanted to weigh in on some of Steve's thoughts, I'm actually really
>> excited about being able to leverage Hoya inside of Accumulo itself.
>>
>> We presently have a few system tests that rely on manual set up, which can
>> be frustrating to deal with on a beefy boxes (running multiple Accumulo
>> procs on a single host). Hoya drastically reduces the amount of effort it
>> takes to run these distributed tests in a 'closer to real' environment.
>> On Jan 15, 2014 8:36 AM, "Steve Loughran"  wrote:
>>
>> > On 15 January 2014 02:13, Andreas Neumann  wrote:
>> >
>> > > I see. So is Hoya limited to HBase and Accumulo? Or is it open for any
>> > > other type of existing application? If so, won't it have some common
>> > > abstraction that is shared by all of them? That is where I see the
>> > > similarity with Twill.
>> > >
>> > >
>> > it started off as pure hbase, but now has the notion of a provider which
>> > has a client-side and server side
>> >
>> > client side
>> >  -helps set up the template JSON file to describe the cluster (e.g. adds
>> > default values),
>> >  -patches the configuration directory supplied at creation time with
>> > whatever options it wants (e.g links up fs.default.name & ZK settings in
>> > hbase-site.xml)
>> >  -does preflight validation of cluster options
>> >  -can also add its own .tar.gz to the resources of the AM (or any other
>> > resources)
>> >
>> > server side
>> >  -runs in the AM and sets up everything needed to run instances of a role
>> > (e.g. HBase master, Accumulo GC, ..)
>> >  -can run code in the AM to help set things up (e.g. Accumulo provider
>> > service runs bin/accumulo init if needed)
>> >  -TODO: liveness monitoring
>> >
>> > the requirements of an app to be deployable are
>> >
>> >
>> https://github.com/hortonworks/hoya/blob/master/src/site/markdown/app_needs.md
>> >
>> >
>> >
>> > > Whereas, if it is a separate effort for each existing application, say
>> > > HBase, then what is the end goal for Hoya when it comes out of
>> > incubation?
>> > > To merge it back into HBase proper?
>> > >
>> > >
>> > Now that it supports >1 application, it can't go into HBase. The
>> individual
>> > provider services can (their implementation classes are worked out via
>> the
>> > configuration.XML).
>> >
>> > But as we use the accumulo and HBase apps for testing, its really good to
>> > have them both in the hoya project right now -a project that builds
>> > downstream of both and needs
>> > to be given the Hadoop filesystem paths to .tar.gz files of each app.
>> >
>> > There's nothing to stop 3rd party apps joining in, indeed, one thing I'd
>> > like someone to do is actually have Hoya d

[ANNOUNCE] Suresh Srinivas joins the IPMC

[Devaraj Das]

Hi all,

Incubator PMC has voted to offer membership to Suresh Srinivas, who
has accepted to joined the ranks.

Suresh is a seasoned member of Hadoop PMC with deep technical skills,
and looking forward to mentoring projects in the Apache Incubator.

Welcome Suresh and thanks for your contributions.

Devaraj Das.

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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

Re: [VOTE] Release of Apache Phoenix 3.0.0 incubating RC1

[Devaraj Das]

+1. Downloaded the source, built the package and ran unit tests.

On Tue, Mar 25, 2014 at 9:39 AM, James Taylor  wrote:
> Hi everyone,
> This is a call for a vote on Apache Phoenix 3.0.0 incubating RC1. Phoenix
> is a SQL query engine for Apache HBase, a NoSQL data store. It is accessed
> as a JDBC driver and enables querying and managing HBase tables using SQL. 
> This
> is the next major release of Phoenix compatible with the 0.94 branch of
> Apache HBase and will be our second release in the incubator. The release
> includes both a source-only release and a convenience binary release.
>
> New features include:
> - Equi-joins through broadcast hash join
> - Shared tables over same physical HBase table
> - Read-only and updatable views
> - Multi-tenancy
> - JDBC ARRAY type
> - Sequence creation and usage
>
> The dev list thread for the passing vote (10 +1s with 3 IPMC votes) can be
> found at:
> http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201403.mbox/%3CCAAF1Jdg4x1Fo6xtX%3DEzWiGrQsxLkgGUJTAm7Dcb-M8NTR9MJgw%40mail.gmail.com%3E
>
> The source tarball, including signatures, digests, etc can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-3.0.0-incubating-rc1/src/
>
> The binary artifacts can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-3.0.0-incubating-rc1/bin/
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/mujtaba.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/dev/incubator/phoenix/KEYS
>
> The tag to be voted upon:
> https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=tag;h=refs/tags/v3.0.0-incubating-rc1
>
> For information about the contents of this release see:
> https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=log;h=refs/tags/v3.0.0-incubating-rc1
>
> Release notes
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12326145&styleName=Text&projectId=12315120&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C34a706e780c7e8f198c9ca903e80572b560599b6%7Clin
>
> Vote will be open for at least 72 hours. Please vote:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks,
> James

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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

Re: [VOTE] Release Apache Tez-0.4.0-incubating RC1

[Devaraj Das]

+1 (binding). Downloaded and ran unit tests.

On Wed, Apr 2, 2014 at 6:11 AM, Alan Gates  wrote:
> +1.  Checked the signature and checksums, looked over the LICENSE, NOTICE, 
> DISCLAIMER, and README files, built it.
>
> Alan.
>
> On Apr 1, 2014, at 11:42 PM, Siddharth Seth  wrote:
>
>> I have created a tez-0.4.0-incubating release candidate (rc1).
>>
>> This includes license and notice files missing from rc0 release artifacts
>> (the javadoc artifact has these files under resources/META-INF instead of
>> directly under META-INF)
>>
>> GIT source tag:
>> https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez.git;a=log;h=refs/tags/release-0.4.0-incubating-rc1
>> (git commit 145c730c8d1cea863185b2a3354b19f2ab21addd)
>>
>> Staging site:
>> https://dist.apache.org/repos/dist/dev/incubator/tez/0.4.0-incubating-rc1
>> (svn revision 4929)
>>
>> Nexus Staging URL:
>> *https://repository.apache.org/content/repositories/orgapachetez-1005/
>> *
>>
>> PGP release keys:
>> http://pgp.mit.edu/pks/lookup?op=get&search=0x477E02D33DD51430
>> KEYS file available at
>> https://dist.apache.org/repos/dist/release/incubator/tez/KEYS
>>
>> List of issues fixed in the release:
>> https://issues.apache.org/jira/browse/TEZ/fixforversion/12326283/
>> Also available in CHANGES.txt within the release tarball.
>>
>> Vote will be open for at least 72 hours ( until the required number of IPMC
>> votes are obtained
>> ).
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>> For folks not familiar with vetting a release, please refer to
>> http://incubator.apache.org/guides/releasemanagement.html#check-list
>>
>> Thanks
>> - Sid
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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

Re: [VOTE] Release of Apache Phoenix 3.0.0 incubating RC3

[Devaraj Das]

+1 (binding).

On Wed, Apr 2, 2014 at 10:27 PM, lars hofhansl  wrote:
> +1 (binding)
>
> - promoting my +1 from the Phoenix dev list.
>
> -- Lars
>
>
>
> 
>  From: James Taylor 
> To: general@incubator.apache.org
> Sent: Monday, March 31, 2014 10:40 PM
> Subject: [VOTE] Release of Apache Phoenix 3.0.0 incubating RC3
>
>
> Hi everyone,
> This is a call for a vote on Apache Phoenix 3.0.0 incubating RC3. Phoenix
> is a SQL query engine for Apache HBase, a NoSQL data store. It is accessed
> as a JDBC driver and enables querying and managing HBase tables using SQL. 
> This
> is the next major release of Phoenix compatible with the 0.94 branch of
> Apache HBase and will be our second release in the incubator. The release
> includes both a source-only release and a convenience binary release.
>
> New features include:
> - Equi-joins through broadcast hash join
> - Shared tables over same physical HBase table
> - Read-only and updatable views
> - Multi-tenancy
> - JDBC ARRAY type
> - Sequence creation and usage
>
> The dev list thread for the passing vote (8 +1s with 2 IPMC votes) can be
> found at:
> http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201404.mbox/%3CCAAF1JdiaQHkaT7FeMW9R343j4mbZLOr0Qxn2ZeP9EoXVv4%3DGZQ%40mail.gmail.com%3E
>
> The source tarball, including signatures, digests, etc can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-3.0.0-incubating-rc3/src/
>
> The binary artifacts can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-3.0.0-incubating-rc3/bin/
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/mujtaba.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/incubator/phoenix/KEYS
>
> The hash and tag to be voted on:
> https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=commit;h=363e71bfd7cf6576657dddb484c6a48de9b8de61
> https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=tag;h=refs/tags/v3.0.0-incubating-rc3
>
> For information about the contents of this release see:
> https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=log;h=refs/tags/v3.0.0-incubating-rc3
>
> Vote will be open for at least 72 hours. Please vote:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks,
> The Apache Phoenix Team

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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

Re: [RESULT][VOTE] Release of Apache Phoenix 4.0.0 incubating RC3

[Devaraj Das]

+1

On Thu, Apr 3, 2014 at 4:06 PM, Enis Söztutar  wrote:
> +1
>
> On Thursday, April 3, 2014, Steven Noels  wrote:
>
>> On Wed, Apr 2, 2014, at 08:53 AM, Stack wrote:
>> > +1
>> >
>> > (Promoting my phoenix dev list +1 here)
>>
>> +1
>>
>> (ditto)
>>
>> Keep up the great work.
>>
>> Steven.
>>
>> -
>> To unsubscribe, e-mail: 
>> general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: 
>> general-h...@incubator.apache.org
>>
>>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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

Re: [VOTE] Accept Slider into the incubator

[Devaraj Das]

+1 (binding)

On Thu, Apr 17, 2014 at 6:01 AM, Steve Loughran  wrote:
> I'd like to call a vote on accepting Slider into the incubator
>
>
> https://wiki.apache.org/incubator/SliderProposal
>
> [ ] +1 Accept Slider into the Incubator
> [ ] +0 Indifferent to the acceptance of Slider
> [ ] -1 Do not accept Slider because ...
>
>
> The vote will be open until Thursday April 24 13:00 UTC
>
> -Steve
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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

Re: [VOTE] Graduation of Apache Phoenix from the Incubator

[Devaraj Das]

+1

On Wed, Apr 30, 2014 at 10:44 PM, James Taylor  wrote:
> Hi everyone,
>
> The Apache Phoenix podling has has discussed and voted to graduate from the
> incubator with 22 +1 votes, 5 of which were IPMC vote [1]. We've made three
> releases, increased our contributor and committer list [2], and have an
> active, thriving community.
>
> Please VOTE below on the graduation of Apache Phoenix from the
> Incubator. The graduation resolution is pasted below.
>
> The VOTE will be open for at least 72 hours:
>
> [ ] +1 Graduate Apache Phoenix from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Phoenix from the Incubator because
>
> [1]
> http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201405.mbox/%3CCAAF1JdgX_0nc7hgSrx9v1wJGKG0C3LBjO2ceZpGYsW1Z%3DsSaYw%40mail.gmail.com%3E
> [2] https://incubator.apache.org/projects/phoenix.html
>
>
> X. Establish the Apache Phoenix 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 SQL database for NoSQL data stores
>such as Apache HBase.
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>Committee (PMC), to be known as the "Apache Phoenix Project",
>be and hereby is established pursuant to Bylaws of the
>Foundation; and be it further
>
>RESOLVED, that the Apache Phoenix Project be and hereby is
>responsible for the creation and maintenance of software
>related to a SQL database for NoSQL data stores such as Apache
>HBase; and be it further
>
>RESOLVED, that the office of "Vice President, Apache Phoenix" 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 Phoenix Project, and to have primary responsibility
>for management of the projects within the scope of
>responsibility of the Apache Phoenix 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 Phoenix Project:
>
>  * Andrew Purtell
>  * Anoop Sam John
>  * Devaraj Das   
>  * Eli Levine
>  * Enis Soztutar 
>  * Gabriel Reid  
>  * James R. Taylor   
>  * Jeffrey Zhong 
>  * Jesse Yates   
>  * Lars Hofhansl 
>  * Maryann Xue   
>  * Michael Stack 
>  * Mujtaba Chohan
>  * Nick Dimiduk  
>  * Ramkrishna Vasudevan  
>  * Simon Toens   
>  * Steven Noels  
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that James R. Taylor
>be appointed to the office of Vice President, Apache Phoenix, 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 Phoenix 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 Phoenix Project; and be it further
>
>RESOLVED, that the Apache Phoenix Project be and hereby
>is tasked with the migration and rationalization of the Apache
>Incubator Phoenix podling; and be it further
>
>RESOLVED, that all responsibilities pertaining to the Apache
>Incubator Phoenix podling encumbered upon the Apache Incubator
>Project are hereafter discharged.

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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

Re: [VOTE] Graduate Apache Tez from Apache Incubator to TLP

[Devaraj Das]

+1 (binding)

On Mon, Jun 30, 2014 at 9:16 PM, Hitesh Shah  wrote:
> Hello folks
>
> Tez entered incubation in February, 2013. Since then, we have made progress 
> towards graduation[1]. The Tez community recently voted positively towards 
> graduation[2] with 27 +1s.
> Of the 27, there were 5 IPMC votes from our mentors:
> - Alan Gates
> - Arun C. Murthy
> - Chris Mattman
> - Chris Douglas
> - Jakob Homan
>
> Now, I would like to ask the IPMC to vote for the graduation of Apache Tez.
>
> Please VOTE to indicate if Apache Tez is ready to graduate as a Top Level 
> Project. The board resolution is included below.
>
> [ ] +1 Graduate Apache Tez as a TLP
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Tez as a TLP because…
>
> The vote will remain open for 72 hours.
>
> thanks
> — Hitesh Shah ( on behalf of Tez PPMC )
>
> [1] 
> http://mail-archives.apache.org/mod_mbox/incubator-tez-dev/201406.mbox/%3ccfc4fef8.16337a%25chris.a.mattm...@jpl.nasa.gov%3E
> [2] 
> http://mail-archives.apache.org/mod_mbox/incubator-tez-dev/201406.mbox/%3ccaoapips7pjs_6hinkwk0uv0hnnrydqcg639dpf9vojeuto9...@mail.gmail.com%3E
>
> Board Resolution:
> --
> X. Establish the Apache Tez 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 fast and flexible large-scale data analysis
> on clusters.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Tez Project", be
> and hereby is established pursuant to Bylaws of the Foundation;
> and be it further
>
> RESOLVED, that the Apache Tez 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 Tez" 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 Tez Project, and to have primary responsibility for
> management of the projects within the scope of responsibility
> of the Apache Tez 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 Tez Project:
>
>  * Alan Gates 
>  * Arun C. Murthy 
>  * Ashutosh Chauhan 
>  * Bill Graham 
>  * Bikas Saha 
>  * Chris Douglas 
>  * Chris Mattmann 
>  * Daryn Sharp 
>  * Devaraj Das 
>  * Gopal Vijayaraghavan 
>  * Gunther Hagleitner 
>  * Hitesh Shah 
>  * Jitendra Pandey 
>  * Jason Lowe 
>  * Jakob Homan 
>  * Julien Le Dem 
>  * Kevin Wilfong 
>  * Mike Liddell 
>  * Mohammad Kamrul Islam 
>  * Namit Jain 
>  * Nathan Roberts 
>  * Owen O’Malley 
>  * Rajesh Balamohan 
>  * Robert Evans 
>  * Rohini Palaniswamy 
>  * Siddharth Seth 
>  * Tassapol Athiapinya 
>  * Thomas Graves 
>  * Tom White 
>  * Vikram Dixit 
>  * Vinod Kumar Vavilapalli 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hitesh Shah be
> appointed to the office of Vice President, Apache Tez, 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 Tez Project be and hereby is
> tasked with the migration and rationalization of the Apache
> Incubator Tez podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Tez 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
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notifi

Re: [VOTE] Release Apache Samza 0.7.0-incubating RC0

[Devaraj Das]

+1 (binding). Downloaded the source and ran unit tests. Looked good.

On Sat, Jun 28, 2014 at 5:02 PM, Jakob Homan  wrote:
> This is vote for Samza's 0.7.0 release.  The PPMC vote passed 6x+1 6
> (Martin, Jakob, Yan, Sriram, Zhijie, Garry):
> http://bit.ly/samza070releasevote
>
> The release candidate can be downloaded from here:
> http://people.apache.org/~martinkl/samza-0.7.0-rc0/
>
> The release candidate is signed with pgp key ED78F8F5352D8EDF, which is
> included in the repository's KEYS file:
> https://git-wip-us.apache.org/repos/asf?p=incubator-samza.git;a=blob_plain;f=KEYS;h=7c59d68a82a6b6172334725962583b2fa8071242;hb=HEAD
> and can also be found on keyservers:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xED78F8F5352D8EDF
>
> The git tag is release-0.7.0-rc0 and signed with the same pgp key:
> https://git-wip-us.apache.org/repos/asf?p=incubator-samza.git;a=tag;h=refs/tags/release-0.7.0-rc0
>
> 155 issues were resolved for this release:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20fixVersion%20%3D%200.7.0%20AND%20status%20in%20(Resolved%2C%20Closed)
>
> Here's my +1 (binding)

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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

Re: [VOTE] Argus as a new incubator project

[Devaraj Das]

+1

On Mon, Jul 21, 2014 at 6:37 PM, P. Taylor Goetz  wrote:
> I think the added diversity among mentors will help with some of the concerns 
> raised. I also imagine the podling would need to build a more diverse 
> committer/PPMC membership prior to graduation.
>
> +1 (non-binding)
>
> -Taylor
>
>> On Jul 21, 2014, at 12:03 PM, "Owen O'Malley"  wrote:
>>
>> Following the discussion earlier, I'm calling a vote to accept Argus as a
>> new Incubator project.
>>
>> The proposal draft is available at:
>> https://wiki.apache.org/incubator/ArgusProposal, and is also included
>> below.
>>
>> Vote is open for 72h and closes at 24 July 2014 at 10am PST.
>>
>> [ ] +1 accept Argus in the Incubator
>> [ ] +/-0
>> [ ] -1 because...
>>
>> I'm +1.
>>
>> .. Owen
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

-
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

[Devaraj Das]

Hi folks,
Happy to see such a hugely positive response on the proposal. I'll put
up a vote tomorrow.

Now, on the mentors, I think we have enough at this point and we have
also addressed the diversity concern. I had got the confirmation from
Chris Douglas and Chris Mattmann yesterday afternoon that they would
participate as mentors in the project. On the nominations for getting
involved in the project, you are welcome to come in as contributors.
Individuals in the initial list of committers all have a view point
that the committers list be kept as such and the standard practice
(based on contributions, after the project is accepted for incubation)
for accepting new committers be followed here.

Thanks
Devaraj.

On Mon, Feb 11, 2013 at 8:07 AM, Kevin Minder
 wrote:
> Hi Bertrand,
> Currently all of the mentors are affiliated with Hortonworks as well.  We
> can reach out to a number of other people and organizations that are
> interested in the project to diversify if this is an important consideration
> at this stage.
>
> One other question I have is about creating a wiki to host the proposal.  I
> don't seem to have privs to create http://wiki.apache.org/incubator/knox.
> Would that be the correct place to evolve the proposal?  If so, how do I go
> about creating in?
> Kevin.
>
>
> On 2/11/13 10:10 AM, Bertrand Delacretaz wrote:
>>
>> On Mon, Feb 11, 2013 at 3:55 PM, Kevin Minder
>>  wrote:
>> ...
>>>
>>> === 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)
>>
>> ...
>>
>> Considering all initial committers are from hortonworks, I'd like to
>> see affiliations for mentors as well - or at least indicate which
>> mentors are *not* affiliated with hortonworks.
>>
>> -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
>


On Mon, Feb 11, 2013 at 8:07 AM, Kevin Minder
 wrote:
> Hi Bertrand,
> Currently all of the mentors are affiliated with Hortonworks as well.  We
> can reach out to a number of other people and organizations that are
> interested in the project to diversify if this is an important consideration
> at this stage.
>
> One other question I have is about creating a wiki to host the proposal.  I
> don't seem to have privs to create http://wiki.apache.org/incubator/knox.
> Would that be the correct place to evolve the proposal?  If so, how do I go
> about creating in?
> Kevin.
>
>
> On 2/11/13 10:10 AM, Bertrand Delacretaz wrote:
>>
>> On Mon, Feb 11, 2013 at 3:55 PM, Kevin Minder
>>  wrote:
>> ...
>>>
>>> === 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)
>>
>> ...
>>
>> Considering all initial committers are from hortonworks, I'd like to
>> see affiliations for mentors as well - or at least indicate which
>> mentors are *not* affiliated with hortonworks.
>>
>> -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
>


On Mon, Feb 11, 2013 at 8:07 AM, Kevin Minder
 wrote:
> Hi Bertrand,
> Currently all of the mentors are affiliated with Hortonworks as well.  We
> can reach out to a number of other people and organizations that are
> interested in the project to diversify if this is an important consideration
> at this stage.
>
> One other question I have is about creating a wiki to host the proposal.  I
> don't seem to have privs to create http://wiki.apache.org/incubator/knox.
> Would that be the correct place to evolve the proposal?  If so, how do I go
> about creating in?
> Kevin.
>
>
> On 2/11/13 10:10 AM, Bertra

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

[Devaraj Das]

 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

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

[Devaraj Das]

Oops. Sorry. Will re-initiate the vote.

On Thu, Feb 14, 2013 at 8:25 PM, Mattmann, Chris A (388J)
 wrote:
> s/Apache Open Climate Workbench/Apache Knox Hadoop Gateway/ :)
>
> May want to resend the [VOTE] thread.
>
> On 2/14/13 5:26 PM, "Devaraj Das"  wrote:
>
>>Hi Folks,
>>
>>Thanks for participating in the discussion. I'd like to call a VOTE
>>for acceptance of Apache Knox Hadoop Gateway Project into the
>>Incubator. The vote will close on Feb 21 at 6:00 p.m.
>>
>>[ ]  +1 Accept Apache Open Climate Workbench into the Incubator
>>[ ]  +0 Don't care.
>>[ ]  -1 Don't accept Apache Open Climate Workbench into the Incubator
>>because...
>>
>>Full proposal is pasted at the bottom of this email, and the
>>corresponding wiki is http://wiki.apache.org/incubator/knox. Only
>>VOTEs from Incubator PMC members are binding.
>>
>>Here's my +1 (binding).
>>
>>Thanks,
>>Devaraj.
>>
>>p.s. In the last day, Tom White has been added as a mentor, and
>>Venkatesh Seetharam has been added in the list of initial committers.
>>
>>
>>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.
>>
>>The goal of the project is to provide coverage for all existing Hadoop
>>ecosystem projects. In addition, the project will be extensible to
>>allow for new and/or proprietary Hadoop components without requiring
>>changes to the gateway source code. The gateway is expected to run in
>>a DMZ environment where it will provide controlled access to these
>>Hadoop services. In this way Hadoop clusters can be protected by a
>>firewall and only limited access provided through the firewall for the
>>gateway. The authentication components of the gateway will be modular
>>and extensible such that it can be integrated with existing security
>>infrastructure.
>>
>>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 ul

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

[Devaraj Das]

 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

Re: [VOTE] Accept Tez into Incubator

[Devaraj Das]

+1 (binding).

On Tue, Feb 19, 2013 at 8:26 PM, Arun C Murthy  wrote:
> Hi Folks,
>
> Thanks for participating in the discussion. I'd like to call a VOTE for 
> acceptance of Apache Tez into the Incubator. I'll let the vote run till into 
> this weekend (Sun 2/24 6pm PST).
>
> [ ]  +1 Accept Apache Tez into the Incubator
> [ ]  +0 Don't care.
> [ ]  -1 Don't accept Apache Tez into the Incubator because...
>
> Full proposal is pasted at the bottom of this email, and the corresponding 
> wiki is http://wiki.apache.org/incubator/TezProposal.
>
> Only VOTEs from Incubator PMC members are binding, but all are welcome to 
> express their thoughts.
>
> Here's my +1 (binding).
>
> thanks,
> Arun
>
> PS: From the initial discussion, the only changes are that I've added one new 
> mentor and 2 new committers. All the new additions come from the non-major 
> employer while we continue to strive to further diversify during the 
> incubation. Thanks.
>
> 
>
> = Tez =
>
> == Abstract ==
> Tez is an effort to develop a generic application framework which can be used
> to process arbitrarily complex data-processing tasks and also a re-usable set
> of data-processing primitives which can be used by other projects.
>
> == Proposal ==
> Tez is a proposal to develop a generic application which can be used to
> process complex data-processing task DAGs and runs natively on Apache Hadoop
> YARN. YARN is a generic resource-management system on which currently
> applications like MapReduce already exist. MapReduce is a specific, and
> constrained, DAG - which is not optimal for several frameworks like Apache 
> Hive
> and Apache Pig. Furthermore, we propose to develop a re-usable set of
> libraries of data-processing primitives such as sorting, merging,
> data-shuffling, intermediate data management etc. which are necessary for Tez
> which we envision can be used directly by other projects.
>
> == Background ==
> Apache Hadoop MapReduce has emerged as the assembly-language on which other
> frameworks like Apache Pig and Apache Hive have been built. However, it has
> been well accepted that MapReduce produces very constrained task DAGs for each
> job which results in Apache Pig and Apache Hive requiring multiple MapReduce
> jobs for several queries. By providing a more expressive DAG of tasks for a
> job, Tez attempts to provide significantly enhanced data-processing
> capabilities for projects like Apache Pig, Apache Hive, Cascading etc.
>
> == Rationale ==
> There is an important gap that Tez fulfills in the Apache Hadoop ecosystem of
> allowing for more expressive task DAGs for data-processing applications such
> as Apache Pig, Apache Hive, Cascading etc.
>
> With emergence of Apache Hadoop YARN, there is a strong need for a
> common DAG application which can then be shared by Apache Pig, Apache Hive,
> Cascading etc.
>
> == Initial Goals ==
> The initial goals for this project are to specify the detailed requirements
> and architecture, and then develop the initial implementation including the
> DAG ApplicationMaster to run natively inside Apache Hadoop YARN.
>
> == Current Status ==
> Significant work has been completed to identify the initial requirements and
> define the overall system architecture. There is a patch available in the
> internal Hortonworks git repository which can act as the initial seed.
>
> === 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 generic DAG application for data processing in the open source 
> is
> tremendous, so there is a potential for a very large community. We believe
> that Tez's extensible architecture will further encourage community 
> participation.
> Also, related Apache projects (eg, Pig, Hive) have very large and active
> communities, and we expect that over time Tez will also attract a large 
> community.
>
> === Core Developers ===
> The developers on the initial committers list include people very experienced
> in the Apache Hadoop ecosystem:
>
>  * Alan Gates 
>  * Arun C Murthy 
>  * Ashutosh Chauhan 
>  * Bikas Saha 
>  * Chris Douglas 
>  * Daryn Sharp 
>  * Devaraj Das 
>  * Gopal Vijayaraghavan 
>  * Gunther Hagleitner 
>  * Hitesh Shah 
>  * Jason Lowe 
>  * Jean Xu 
>  * Jitendra Pandey 
>  * Julien Le Dem 
>  * Kevin Wilfong 
>  *

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

[Devaraj Das]

Hi folks,
With 10 binding +1 votes, this vote has passed.  Thanks to everyone who
voted.
Devaraj.
 +1 (binding)

On Feb 15, 2013, at 11:22 AM, Devaraj Das wrote:

> Hi Folks,
>
> Thanks for participating in the discussion. I'd like to call a VOTE
> for acceptance of Apache Knox Hadoop Gateway Project into the
> Incubator. The vote will close on Feb 22 at 6:00 p.m.
>
> [ ]  +1 Accept Apache Knox Hadoop Gateway Project into the Incubator
> [ ]  +0 Don't care.
> [ ]  -1 Don't accept Apache Knox Hadoop Gateway Project into the
> Incubator because...
>
> Full proposal is pasted at the bottom of this email, and the
> corresponding wiki is http://wiki.apache.org/incubator/knox. Only
> VOTEs from Incubator PMC members are binding.
>
> Here's my +1 (binding).
>
> Thanks,
> Devaraj.
>
> -
>
> 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.
>
> The goal of the project is to provide coverage for all existing Hadoop
> ecosystem projects. In addition, the project will be extensible to
> allow for new and/or proprietary Hadoop components without requiring
> changes to the gateway source code. The gateway is expected to run in
> a DMZ environment where it will provide controlled access to these
> Hadoop services. In this way Hadoop clusters can be protected by a
> firewall and only limited access provided through the firewall for the
> gateway. The authentication components of the gateway will be modular
> and extensible such that it can be integrated with existing security
> infrastructure.
>
> 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, 

Write access on wiki

[Devaraj Das]

Could I please get write access on the wiki content under
http://wiki.apache.org/incubator/. My username is DevarajDas.

Thanks
Devaraj

Re: [VOTE] Accept Falcon into the Apache Incubator (was originally named Ivory)

[Devaraj Das]

b repository at:
> > https://github.com/sriksun/Falcon
> >
> > == Source and Intellectual Property Submission Plan ==
> > The complete Falcon code is under Apache Software License 2.
> >
> > == External Dependencies ==
> > The dependencies all have Apache compatible licenses. These include
> > BSD, MIT licensed dependencies.
> >
> > == Cryptography ==
> > None
> >
> > == Required Resources ==
> >
> > === Mailing lists ===
> >
> >  * falcon-dev AT incubator DOT apache DOT org
> >  * falcon-commits AT incubator DOT apache DOT org
> >  * falcon-user AT incubator apache DOT org
> >  * falcon-private AT incubator DOT apache DOT org
> >
> > === Subversion Directory ===
> > Git is the preferred source control system: git://git.apache.org/falcon
> >
> > === Issue Tracking ===
> > JIRA FALCON
> >
> > == Initial Committers ==
> >  * Srikanth Sundarrajan (Srikanth.Sundarrajan AT inmobi DOT com)
> >  * Shwetha GS (shwetha.gs AT inmobi DOT com)
> >  * Shaik Idris (shaik.idris AT inmobi DOT com)
> >  * Venkatesh Seetharam (Venkatesh AT apache DOT org)
> >  * Sanjay Radia (sanjay AT apache DOT org)
> >  * Sharad Agarwal (sharad AT apache DOT org)
> >  * Amareshwari SR (amareshwari AT apache DOT org)
> >  * Samarth Gupta (samarth.gupta AT inmobi DOT com)
> >  * Rishu Mehrothra (rishu.mehrothra AT inmobi DOT com)
> >
> > == Affiliations ==
> >  * Srikanth Sundarrajan (InMobi)
> >  * Shwetha GS (InMobi)
> >  * Shaik Idris (InMobi)
> >  * Venkatesh Seetharam (Hortonworks Inc.)
> >  * Sanjay Radia (Hortonworks Inc.)
> >  * Sharad Agarwal (InMobi)
> >  * Amareshwari SR (InMobi)
> >  * Samarth Gupta (InMobi)
> >  * Rishu Mehrothra (InMobi)
> >
> > == Sponsors ==
> >
> > === Champion ===
> >  * Arun C Murthy (acmurthy at apache dot org)
> >
> > === Nominated Mentors ===
> >  * Alan Gates (gates AT apache DOT org)
> >  * Chris Douglas (cdouglas AT apache DOT org)
> >  * Devaraj  Das (ddas AT apache DOT org)
> >  * Owen O’Malley (omalley AT apache DOT org)
> >
> > === Sponsoring Entity ===
> > Incubator PMC
> >
> > --
> > _
> > The information contained in this communication is intended solely for
> the
> > use of the individual or entity to whom it is addressed and others
> > authorized to receive it. It may contain confidential or legally
> privileged
> > information. If you are not the intended recipient you are hereby
> notified
> > that any disclosure, copying, distribution or taking any action in
> reliance
> > on the contents of this information is strictly prohibited and may be
> > unlawful. If you have received this communication in error, please notify
> > us immediately by responding to this email and then delete it from your
> > system. The firm is neither liable for the proper and complete
> transmission
> > of the information contained in this communication nor for any delay in
> its
> > receipt.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache Ambari 1.2.2-incubating RC1

[Devaraj Das]

+1 (binding). Downloaded source, buil package, and, ran unit tests
successfully.


On Mon, Apr 8, 2013 at 11:58 AM, Yusaku Sako  wrote:

> Hi all,
>
> I have created the ambari-1.2.2-incubating-rc1 release candidate.
>
> I have run the rat tool and successfully deployed a 5-node cluster on RHEL
> 6.3 using the instructions available at:
>
> http://incubator.apache.org/ambari/1.2.2/installing-hadoop-using-ambari/content/index.html
>
> Critical fixes made since ambari-1.2.2-rc0 are:
> https://issues.apache.org/jira/browse/AMBARI-1748: JDK option on the UI
> when used is not passed onto the global parameters
> https://issues.apache.org/jira/browse/AMBARI-1794: Add Host install retry
> shuts down all services in the cluster
> https://issues.apache.org/jira/browse/AMBARI-1795: Add Hosts - retrying
> install shows all progress bars in red and causes the wizard to get stuck
> on the progress page
> https://issues.apache.org/jira/browse/AMBARI-1815; After modifying custom
> configs, properties are shown as blank, leading to corrupt core-site.xml
> upon save
>
> SVN source tag:
> https://svn.apache.org/repos/asf/incubator/ambari/tags/release-1.2.2-rc1
>
> Staging site:
> http://people.apache.org/~yusaku/ambari-1.2.2-incubating-rc1
>
> PGP release keys (signed using 3ABE18B3)
> http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x4C3AA2723ABE18B3
>
> One can look into the issues fixed in this release at:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%20%221.2.2%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC
>
> Vote will be open for 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
>
> Here's my vote to start: +1 (binding)
>
> Yusaku
>

Re: [VOTE] Release of Apache Falcon (incubating) v0.3

[Devaraj Das]

+1 (binding)

On Wed, Aug 14, 2013 at 8:39 AM, Arun C Murthy  wrote:
> +1 (binding)
>
> Arun
>
> On Aug 11, 2013, at 11:39 PM, Srikanth Sundarrajan  
> wrote:
>
>> Hello,
>> This is a call for a vote on Apache Falcon 0.3 incubating. This is our first 
>> release.
>>
>> A vote was held on developer mailing list and it
>> passed with 7 +1's.
>>
>> VOTE: 
>> http://mail-archives.apache.org/mod_mbox/falcon-dev/201308.mbox/%3CBLU167-W17AB8E710B264BF39C06C0A45E0%40phx.gbl%3E
>> RESULT: 
>> http://mail-archives.apache.org/mod_mbox/incubator-falcon-dev/201308.mbox/
>>
>> Source tar ball is available at
>> http://people.apache.org/~sriksun/falcon-release/0.3-rc4
>>
>> The release has been signed through key(D2498DC9):
>> http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x90814E84D2498DC9
>>
>> Source corresponding to this release can be found at
>> https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=tag;h=refs/tags/v0.3-rc4
>>
>> Checksums:
>> MD5(falcon-0.3-incubating-sources.tar.gz)= 92bedce87ce2f3959156f9c050638ada
>> SHA1(falcon-0.3-incubating-sources.tar.gz)= 
>> 0acfb200c2bfa60142a163a43f5deeab23ee149c
>>
>> List of issues closed in this release is available at 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314429&version=12324423
>>
>> Vote will be open for 72 hours and close at 15/Aug/2013 12PM IST.
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>> Thanks & Regards
>> Srikanth Sundarrajan
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
> --
> Arun C. Murthy
> Hortonworks Inc.
> http://hortonworks.com/
>
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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

[VOTE] Accept HMS as an incubator project

[Devaraj Das]

of support to new 
developers and to quickly recruit those who make solid contributions to 
committer status.

Community

We are happy to report that multiple organizations are already represented by 
initial team. We hope to extend the user and developer base further in the 
future and build a solid open source community around HMS.

Core Developers

HMS is currently being developed by four engineers from Hortonworks - Eric 
Yang, Owen O’Malley, Vitthal (a.k.a Suhas) Gogate and Devaraj Das. In addition, 
a Yahoo! employee, Jagane Sundar, and an IBM employee, Kan Zhang, are also 
involved. Eric, Jagane and Kan are the original developers. All the engineers 
have deep expertise in Hadoop and are quite familiar with the Hadoop Ecosystem.

Alignment

The ASF is a natural host for HMS given that it is already the home of Hadoop, 
Pig, HBase, Cassandra, and other emerging cloud software projects. HMS has been 
designed to solve the deployment, management and configuration problems of the 
Hadoop ecosystem family of products. HMS fills the gap that Hadoop ecosystem 
has been lacking in the areas of configuration, deployment and manageability.

Known Risks

Orphaned products & Reliance on Salaried Developers

The core developers plan to work full time on the project. There is very little 
risk of HMS getting orphaned. HMS is in use by companies we work for so the 
companies have an interest in its continued vitality.

Inexperience with Open Source

All of the core developers are active users and followers of open source. Eric 
Yang is a committer on Apache Chukwa. Owen O’Malley is the lead of the Apache 
Hadoop project. Devaraj Das is an Apache Hadoop committer and Apache Hadoop PMC 
member. Vitthal (Suhas) Gogate has contributed extensively to the Hadoop Vaidya 
project (part of Apache Hadoop). Jagane Sundar has been contributing, in terms 
of ideas, to the Hadoop project. Kan Zhang is a Hadoop Committer.

Homogeneous Developers

The current core developers are from Hortonworks, IBM, and, Yahoo!. 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 HMS. 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

HMS is going to be used by the users of Hadoop and the Hadoop ecosystem in 
general.

A Excessive Fascination 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 HMS a 
solid home as an open source project following an established development 
model. We have also given reasons in the Rationale and Alignment sections.

Documentation

There is documentation in Hortonworks’s internal repositories.

Initial Source

The source is currently in Hortonworks’s internal repositories.

Source and Intellectual Property Submission Plan

The complete HMS code is under Apache Software License 2.

External Dependencies

The dependencies all have Apache compatible licenses. These include BSD, MIT 
licensed dependencies.

Cryptography

None

Required Resources

Mailing lists

• hms-dev AT incubator DOT apache DOT org
• hms-commits AT incubator DOT apache DOT org
• hms-user AT hms incubator apache DOT org
• hms-private AT incubator DOT apache DOT org
Subversion Directory

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

Issue Tracking

JIRA HMS

Initial Committers

    • Devaraj Das (ddas AT apache DOT org)
• Vitthal Suhas Gogate (gogate AT apache DOT org)
• Owen O'Malley (omalley AT apache DOT org)
• Jagane Sunder (jagane AT sundar DOT org)
• Eric Yang (eyang AT apache DOT org)
• Kan Zhang (kzhang AT apache DOT org)
Affiliations

• Devaraj Das (Hortonworks)
• Vitthal Suhas Gogate (Hortonworks)
• Owen O'Malley (Hortonworks)
• Jagane Sunder (Yahoo)
• Eric Yang (Hortonworks)
• Kan Zhang (IBM)
• Chris Douglas (Yahoo)
• Arun C Murthy (Hortonworks)
Sponsors

Champion

• Owen O'Malley
Nominated Mentors

• Owen O'Malley
• Arun C Murthy
• Chris Douglas
Sponsoring Entity

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

[VOTE][RESULT] Accept HMS as an incubator project

[Devaraj Das]

With ten binding +1 votes, one non-binding +1, and no -1s, this vote passes. 
Thanks to everyone who voted. 

We will proceed on to the next set of steps for having HMS in the Apache 
Incubator.

Devaraj.


> 
> On Aug 25, 2011, at 1:57 PM, Devaraj Das wrote:
> 
>> Hello everyone,
>> This is a vote proposing that HMS be accepted as a project in the Apache 
>> Incubator. HMS is monitoring, administration and lifecycle management 
>> project for Apache Hadoop clusters. The latest proposal is pasted at the end 
>> and it could be found in the wiki as well - 
>> http://wiki.apache.org/incubator/HMSProposal
>> 
>> The related discussion thread is at:
>> 
>> http://www.mail-archive.com/general@incubator.apache.org/msg30354.html
>> 
>> Please cast your votes:
>> [  ] +1 Accept HMS for incubation
>> [  ] +0 Indifferent to HMS incubation
>> [  ] -1 Reject HMS for incubation (and why)
>> 
>> This vote will close 72 hours  from now.
>> 
>> Thanks,
>> Devaraj.
> 
>> --
>> 
>> HMS Proposal
>> 
>> Abstract
>> 
>> HMS is monitoring, administration and lifecycle management project for 
>> Apache Hadoop clusters.
>> 
>> Proposal
>> 
>> HMS will simplify the process of deployment, configuration, management and 
>> monitoring of the collection of Hadoop services and applications that 
>> compose a Hadoop cluster. The collection of services (Hadoop Stack) will 
>> include at least HDFS, MapReduce, HBase, Hive, HCatalog, Pig and Zookeeper. 
>> HMS will be easily configurable to add additional services and applications 
>> to the stack. Our plan is to support the Hadoop stack as a unit of 
>> deployment and configuration where only certain pre-tested versions of 
>> software components are supported to be part of Hadoop stack. Administrators 
>> can always enable/disable the individual software components from the Hadoop 
>> stack per their deployment needs.
>> 
>> The main use cases that HMS is trying to address are the following:
>> 
>>  • Hadoop stack deployment and upgrades
>>  • Hadoop services configuration & management
>> 
>>  • Administration of Hadoop services
>>  • Includes starting and stopping services
>>  • Hadoop system maintenance tasks, such as fsck, format, 
>> re-balance, and compaction
>>  • User access & quota management on Hadoop clusters
>> 
>>  • Easily check and be alerted to failures in Hadoop servers
>>  • Automated discovery of new machines that become available
>>  • Expanding and contracting Hadoop clusters
>>  • Automatic resynchronization to ‘desired’ state (of Hadoop stack) to 
>> handle faulty nodes
>>  • Handle node burn-ins (stress test nodes using Hadoop before deploying 
>> them for production use)
>>  • Simple monitoring and management UI
>>  • Dynamic configuration - Hadoop configuration deduced from machine 
>> attributes (e.g., RAM, CPU, Disk)
>>  • Operational HBase-based (inspired by OpenTSDB) monitoring for Hadoop 
>> clusters
>>  • Make it possible for administrators to deploy other Hadoop related 
>> services and client applications
>> HMS is targeted to administrators responsible for managing Hadoop clusters. 
>> HMS leverages existing data center management and monitoring infrastructure 
>> - Nagios, LDAP, Kerberos, etc. All HMS functionality and data will be 
>> accessible via RESTFUL APIs and command line tools to facilitate its 
>> integration with existing data center management suites.
>> 
>> For the bare metal provisioning, the cluster admins continue to use their 
>> existing infrastructure. Provisioning a machine from scratch is not in the 
>> scope of the current roadmap.
>> 
>> Background
>> 
>> Hadoop’s ecosystem includes many projects (HDFS, MapReduce, Pig, HBase, 
>> etc.). In many cases, users and operators typically want to deploy a 
>> combination of some projects as a stack. It takes a significant amount of 
>> time to get a properly configured Hadoop cluster up and running. HMS has 
>> been designed to solve that problem. HMS automates the whole process of 
>> deploying a stack.
>> 
>> HMS is being developed by developers employed with Yahoo!, Hortonworks and 
>> IBM. Such a tool would have a large number of users and increase the 
>> adoption of Apache Hadoop’s ecosystem. We are therefore proposing to make 
>> HMS Apache open source.
>> 
>> Rati

Re: [VOTE] Change the name of the HMS podling to Ambari.

[Devaraj Das]

On Aug 31, 2011, at 10:58 AM, Owen O'Malley wrote:

> When I was doing the initial trademark search for HMS, I found that
> there are a lot of projects (including software) named HMS. It also
> has the problem of being very bad to search for (42.7m hits on
> google).
> 
> Before I go through and create the infrastructure for Apache
> incubator, I wanted to discuss changing the name. Suhas did some
> searches and found that the name for the royal chair on top of
> elephants is "Ambari," which seems like a very nice name to me.
> 
> Toward that end, I'd like to propose changing the name from HMS to Ambari.
> 

+1

> -- Owen
> 
> -
> 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: Ambari Status

[Devaraj Das]

Yeah, am happy to be a mentor on Ambari. 

Devaraj
 
On May 10, 2012, at 8:19 AM, Owen O'Malley wrote:

> On Thu, May 10, 2012 at 4:55 AM, Franklin, Matthew B.
>  wrote:
> 
> Also, I noticed that ddas signed off on it as a mentor.  I don't see him 
> listed
>>> as an Apache member or IPMC member.
 
 He was added to the IPMC. The message from Noel was dated 6 Oct 2011.
>>> 
>>> Note: he is currently listed in committee-info.txt as a member of the IPMC.
>> 
>> Missed that yesterday.  Thanks for the clarification.  Can we update the 
>> podling status page to reflect his mentorship of Ambari?
> 
> That was my mistake in that I misremembered Devaraj as a mentor for
> Ambari and so I added him as approving it on the wiki. (He had +1'ed
> the report on the ambari-dev mailing list.) Given that Devaraj is on
> the IPMC and is following the dev lists already, I think it would make
> sense to add him as a mentor. If Chris Mattmann is willing to join as
> a mentor too, that would add a non-Hortonworks viewpoint that would be
> appreciated.
> 
> Thanks,
>   Owen
> 
> -
> 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 Drill into the Apache Incubator

[Devaraj Das]

+1 (binding)

On Aug 7, 2012, at 7:41 PM, Ted Dunning wrote:

> I would like to call a vote for accepting Drill for incubation in the
> Apache Incubator. The full proposal is available below.  Discussion
> over the last few days has been quite positive.
> 
> Please cast your vote:
> 
> [ ] +1, bring Drill into Incubator
> [ ] +0, I don't care either way,
> [ ] -1, do not bring Drill into Incubator, because...
> 
> This vote will be open for 72 hours and only votes from the Incubator
> PMC are binding.  The start of the vote is just before 3AM UTC on 8
> August so the closing time will be 3AM UTC on 11 August.
> 
> Thank you for your consideration!
> 
> Ted
> 
> http://wiki.apache.org/incubator/DrillProposal
> 
> = Drill =
> 
> == Abstract ==
> Drill is a distributed system for interactive analysis of large-scale
> datasets, inspired by
> [[http://research.google.com/pubs/pub36632.html|Google's Dremel]].
> 
> == Proposal ==
> Drill is a distributed system for interactive analysis of large-scale
> datasets. Drill is similar to Google's Dremel, with the additional
> flexibility needed to support a broader range of query languages, data
> formats and data sources. It is designed to efficiently process nested
> data. It is a design goal to scale to 10,000 servers or more and to be
> able to process petabyes of data and trillions of records in seconds.
> 
> == Background ==
> Many organizations have the need to run data-intensive applications,
> including batch processing, stream processing and interactive
> analysis. In recent years open source systems have emerged to address
> the need for scalable batch processing (Apache Hadoop) and stream
> processing (Storm, Apache S4). In 2010 Google published a paper called
> "Dremel: Interactive Analysis of Web-Scale Datasets," describing a
> scalable system used internally for interactive analysis of nested
> data. No open source project has successfully replicated the
> capabilities of Dremel.
> 
> == Rationale ==
> There is a strong need in the market for low-latency interactive
> analysis of large-scale datasets, including nested data (eg, JSON,
> Avro, Protocol Buffers). This need was identified by Google and
> addressed internally with a system called Dremel.
> 
> In recent years open source systems have emerged to address the need
> for scalable batch processing (Apache Hadoop) and stream processing
> (Storm, Apache S4). Apache Hadoop, originally inspired by Google's
> internal MapReduce system, is used by thousands of organizations
> processing large-scale datasets. Apache Hadoop is designed to achieve
> very high throughput, but is not designed to achieve the sub-second
> latency needed for interactive data analysis and exploration. Drill,
> inspired by Google's internal Dremel system, is intended to address
> this need.
> 
> It is worth noting that, as explained by Google in the original paper,
> Dremel complements MapReduce-based computing. Dremel is not intended
> as a replacement for MapReduce and is often used in conjunction with
> it to analyze outputs of MapReduce pipelines or rapidly prototype
> larger computations. Indeed, Dremel and MapReduce are both used by
> thousands of Google employees.
> 
> Like Dremel, Drill supports a nested data model with data encoded in a
> number of formats such as JSON, Avro or Protocol Buffers. In many
> organizations nested data is the standard, so supporting a nested data
> model eliminates the need to normalize the data. With that said, flat
> data formats, such as CSV files, are naturally supported as a special
> case of nested data.
> 
> The Drill architecture consists of four key components/layers:
> * Query languages: This layer is responsible for parsing the user's
> query and constructing an execution plan.  The initial goal is to
> support the SQL-like language used by Dremel and
> [[https://developers.google.com/bigquery/docs/query-reference|Google
> BigQuery]], which we call DrQL. However, Drill is designed to support
> other languages and programming models, such as the
> [[http://www.mongodb.org/display/DOCS/Mongo+Query+Language|Mongo Query
> Language]], [[http://www.cascading.org/|Cascading]] or
> [[https://github.com/tdunning/Plume|Plume]].
> * Low-latency distributed execution engine: This layer is responsible
> for executing the physical plan. It provides the scalability and fault
> tolerance needed to efficiently query petabytes of data on 10,000
> servers. Drill's execution engine is based on research in distributed
> execution engines (eg, Dremel, Dryad, Hyracks, CIEL, Stratosphere) and
> columnar storage, and can be extended with additional operators and
> connectors.
> * Nested data formats: This layer is responsible for supporting
> various data formats. The initial goal is to support the column-based
> format used by Dremel. Drill is designed to support schema-based
> formats such as Protocol Buffers/Dremel, Avro/AVRO-806/Trevni and CSV,
> and schema-less formats such as JSON, BSON or YAML. In ad

Re: [VOTE] Graduate Oozie podling from Apache Incubator

[Devaraj Das]

+1 (binding)

To Bertrand's suggestion on leaving Oozie mentor & ASF member in the PMC, I'll 
be happy to be on the PMC (as well, with Alan) if the community is interested.

On Aug 10, 2012, at 4:12 PM, Alejandro Abdelnur wrote:

> This is a call for vote to graduate Oozie podling from Apache Incubator.
> 
> Oozie entered the Incubator in July of 2011. Since then it has added
> two new committers and made two significant releases following the ASF
> policies and guidelines. The community of Oozie is active, healthy and
> growing and has demonstrated the ability to self-govern using accepted
> Apache practices. Oozie community has voted to proceed with graduation
> [1] and the result can be found at [2].
> 
> Please cast your votes:
> 
> [  ] +1 Graduate Oozie podling from Apache Incubator
> [  ] +0 Indifferent to the graduation status of Oozie podling
> [  ] -1 Reject graduation of Oozie podling from Apache Incubator
> 
> This vote will be open for at least 72 hours. Please find the proposed
> board resolution below.
> 
> [1] http://s.apache.org/WDb
> [2] http://s.apache.org/AB2
> 
> Regards,
> Alejandro Abdelnur
> 
> 
>X. Establish the Apache Oozie 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 managing
>   and scheduling workflows that run Apache Hadoop Map Reduce
>   jobs, Apache Pig jobs, Apache Hive jobs and Apache Sqoop 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 Oozie Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
> 
>   RESOLVED, that the Apache Oozie Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to a system for managing
>   and scheduling workflows that run Apache Hadoop Map Reduce
>   jobs, Apache Pig jobs, Apache Hive jobs and Apache Sqoop jobs;
>   and be it further
> 
>   RESOLVED, that the office of "Vice President, Apache Oozie" 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 Oozie Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache Oozie 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 Oozie Project:
> 
>* Alejandro Abdelnurt...@apache.org
>* Andreas Neumann   a...@apache.org
>* Angelo Huang  ange...@apache.org
>* Chao Wang broo...@apache.org
>* Harsh Chouraria   qwertyman...@apache.org
>* Mayank Bansal may...@apache.org
>* Mohammad Islamkam...@apache.org
>* Virag Kothari vi...@apache.org
> 
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Alejandro Abdelnur
>   be appointed to the office of Vice President, Apache Oozie,
>   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 Oozie 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 Oozie Project; and be it further
> 
>   RESOLVED, that the Apache Oozie Project be and hereby
>   is tasked with the migration and rationalization of the Apache
>   Incubator Oozie podling; and be it further
> 
>   RESOLVED, that all responsibilities pertaining to the Apache
>   Incubator Oozie 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
> 


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

Re: [VOTE] Release Apache Trafodion (incubating) 1.3.0-incubating

[Devaraj Das]

+1 (binding)




On Mon, Jan 4, 2016 at 2:41 PM -0800, "Roberta Marton" 
mailto:roberta.mar...@esgyn.com>> wrote:

Hello,



The Apache Trafodion community has voted on and approved its first release

– Apache Trafodion 1.3.0 –incubating (release candidate 5)



Vote request on dev list:

http://mail-archives.apache.org/mod_mbox/incubator-trafodion-dev/201512.mbox/ajax/%3C835f19bc6267f402358a71221c2b6afc%40mail.gmail.com%3E



Vote result on dev list:

http://mail-archives.apache.org/mod_mbox/incubator-trafodion-dev/201601.mbox/ajax/%3Cf41e5961dcf6f0d0d86ee766a6a93833%40mail.gmail.com%3E



The commit id is 6ae976fdc60a683e954d867dab6ff30c55146c8f which corresponds
to tag 1.3.0rc5:

https://git-wip-us.apache.org/repos/asf?p=incubator-trafodion.git;a=tag;h=5af956f989f1f32664bbec768e4f354516daa96b



The release artifacts can be downloaded from:

https://dist.apache.org/repos/dist/dev/incubator/trafodion/apache-trafodion-1.3.0-incubating



Instructions on how to build and run Apache Trafodion are described here:

http://trafodion.apache.org/download.html



The source tar file has been signed with pgp key A44C5A05 which is included
in the download location’s KEYS file:

https://dist.apache.org/repos/dist/dev/incubator/trafodion/KEYS



For changes included in the release, please see the release notes:

http://trafodion.apache.org/release-notes-1-3-0.html



The RAT tool was run on the source and the excluded are defined in the

RAT_README.txt file found in the top level source directory.



The following is a list of issues found during the podling review. It was
determined that these issues can be fixed in a subsequent release, Jira’s,
as noted, were created for each issue.



TRAFODION-1733: Incorrect information included in LICENSE file

  The Facebook copyright is already Apache and does not need to be in the
LICENSE file

  Asciidocs is included but not used

TRAFODION-1725: missing licenses for:

  MooTools Framework MIT licensed Copyright Valerio Proietti

  swscanf.cpp/swprintf.cpp BSD license copyright Chris Torek

  JQuery files - JQuery Foundation, Inc

TRAFODION-1734: Suggestions for licensing improvements:

  Should specify the type of license in the LICENSE file instead of
requiring a lookup in the corresponding license text.

  Should copy all license text to Apache Trafodion instead of specifying an
external link.  The external license could change.

TRAFODION-1735: There was a concern that changes made to some of the BSD
copyrighted files were more than minor so additional copyright information
may be required.





Pursuant to the Release section of the Incubation Policy and with the

endorsement of our mentors we would now like to request the permission  of

the Incubator PMC to publish the release.



The vote will be open for 72 hours.



[ ] +1 approve

[ ] +0 no opinion

[ ] -1 disapprove (and reason why)



   Regards,

Roberta Marton

Re: [VOTE] Release Apache Ranger 0.5.1 (incubating)

[Devaraj Das]

+1 (binding)

From: Madhan Neethiraj 
Sent: Thursday, January 14, 2016 1:46 PM
To: general@incubator.apache.org
Subject: [VOTE] Release Apache Ranger 0.5.1 (incubating)

Incubator PMC,

The Apache Ranger community has voted on and approved the proposal to release 
Apache Ranger 0.5.1 (incubating). The voting result is available at 
http://mail-archives.apache.org/mod_mbox/incubator-ranger-dev/201601.mbox/%3cab1cffbc-e050-4597-b46c-185d2d4d9...@apache.org%3e.

Prior releases of Apache Ranger (incubating) are:
  - Apache Ranger 0.5.0 Jul 2015
  - Apache Ranger 0.4.0 Nov 2014


Artifacts for this release are given below:
  - Git tag for the release: 
https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=shortlog;h=refs/tags/ranger-0.5.1-rc2
  - Sources for the release: 
http://people.apache.org/~madhan/ranger/ranger-0.5.1-rc2/apache-ranger-incubating-0.5.1.tar.gz
  - Source release verification:
- PGP Signature:   
http://people.apache.org/~madhan/ranger/ranger-0.5.1-rc2/apache-ranger-incubating-0.5.1.tar.gz.asc
- MD5/SHA  Hash:  
http://people.apache.org/~madhan/ranger/ranger-0.5.1-rc2/apache-ranger-incubating-0.5.1.tar.gz.mds
  - Keys to verify the signature of the release artifact are available at: 
https://people.apache.org/keys/group/ranger.asc


Please review and vote.


The vote will be open for at least 72 hours or until necessary number of votes 
is reached.
  [  ] +1  approve
  [  ] +0  no opinion
  [  ] -1  disapprove (and reason why)

Here is my +1 (non binding)

Thanks
Madhan



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



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

Re: [VOTE] Release Apache Atlas 0.7.1 (incubating) RC3

[Devaraj Das]

+1 (binding)

From: Madhan Neethiraj 
Sent: Monday, January 23, 2017 12:24 PM
To: general@incubator.apache.org
Cc: d...@atlas.incubator.apache.org
Subject: [VOTE] Release Apache Atlas 0.7.1 (incubating) RC3

Incubator PMC,

Apache Atlas community has voted on and approved the proposal to release Apache 
Atlas 0.7.1 (incubating).
  - vote result thread: 
https://lists.apache.org/thread.html/3615a9f16a49a1960e7a694b6693c8b27e4600b3003e973b755e0078@%3Cdev.atlas.apache.org%3E
  - vote thread: 
https://lists.apache.org/thread.html/e7c09d423895cd6c96d30034646b417d534369475065ad1918a55a3b@%3Cdev.atlas.apache.org%3E

Apache Atlas 0.7.1 (incubating) release candidate #3, artifacts given below, is 
now available for IPMC vote. Please review and vote.

The vote will be open for at least 72 hours or until necessary number of votes 
are reached.

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

Thanks,
Madhan


List of issues addressed in this release: 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20Atlas%20AND%20fixVersion%20%3D%200.7.1-incubating%20ORDER%20BY%20key%20DESC

Git tag for the release: 
https://github.com/apache/incubator-atlas/tree/release-0.7.1-rc3

Sources for the release: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.1-incubating-rc3/apache-atlas-0.7.1-incubating-sources.tar.gz

Source release verification:
  PGP Signature: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.1-incubating-rc3/apache-atlas-0.7.1-incubating-sources.tar.gz.asc
  MD5 Hash: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.1-incubating-rc3/apache-atlas-0.7.1-incubating-sources.tar.gz.mds
  Keys to verify the signature of the release artifacts are available at: 
https://dist.apache.org/repos/dist/dev/incubator/atlas/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 Falcon version 0.6-incubating

[Devaraj Das]

+1 (binding)

On Fri, Nov 28, 2014 at 11:11 PM, Seetharam Venkatesh
 wrote:
> Hello folks,
>
> This is a call for a vote on Apache Falcon 0.6 incubating release.
>
> A vote was held on developer mailing list and it passed with 10 +1's.
>
> Vote thread: http://s.apache.org/YwI
> Results thread: http://s.apache.org/8Pq
>
> The source tarball (*.tar.gz), signature (*.asc), checksum (*.md5, *.sha):
> http://people.apache.org/~venkatesh/falcon-0.6-incubating-rc1/source/
>
> The SHA1 checksum of the archive is 2060489fc68b273560e0ea783318fa3fad3b19cb
>
> The commit id (e2482b8b24ce27bd3caa9e7aa96be67e945eff57) to ve voted upon:
> https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=commit;h=e2482b8b24ce27bd3caa9e7aa96be67e945eff57
>
> The tag to be voted upon:
> https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=tag;h=refs/tags/release-0.6-rc1
>
> The list of fixed issues:
> https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=blob;f=CHANGES.txt;h=2b131c0e5c2dcb98ddd40f680ff688b0b018998c;hb=e2482b8b24ce27bd3caa9e7aa96be67e945eff57
>
> The release has been signed through key(42C7A5EA):
> http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x1B16738C42C7A5EA
>
> Keys to verify the signature of the release artifact are available at:
> http://www.apache.org/dist/incubator/falcon/KEYS
> PGP release keys:
> http://pgp.mit.edu/pks/lookup?op=vindex&search=0x1B16738C42C7A5EA
>
> Note that this is a source only release and we are voting on the source.
> Checksums:
>
> SHA1 (release-0.6-incubating-rc1 / SHA:
> 2060489fc68b273560e0ea783318fa3fad3b19cb)
> MD5 (apache-falcon-0.6-incubating-sources.tar.gz) =
> cccf15351e1de32e4738d6f067025819
>
> Vote will be open for 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> +1 from my side for the release.
>
> Thanks!
>
> --
> Regards,
> Venkatesh
>
> “Perfection (in design) is achieved not when there is nothing more to add,
> but rather when there is nothing more to take away.”
> - Antoine de Saint-Exupéry

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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

Re: [DISCUSS] Trafodion Incubation Proposal

[Devaraj Das]

Looks good. If you need more mentors on this, please count me in.

From: saint@gmail.com  on behalf of Stack 

Sent: Friday, May 08, 2015 2:59 PM
To: general@incubator.apache.org
Subject: [DISCUSS] Trafodion Incubation Proposal

I would like to start up a discussion on Trafodion joining the ASF as an
incubating project.

Trafodion is a webscale SQL-on-Hadoop solution that enables transactional
or operational workloads on Hadoop, .

The proposal is available on the wiki here:
https://wiki.apache.org/incubator/TrafodionProposal#preview

The proposal text is also attached to the end of this email.

Trafodion is a rich, storied SQL engine that has recently been ported to
run on HBase and Hadoop. I think it would make for a fine addition to the
Apache family of projects  It would be good to hear what others think.

Thank you in advance for giving the proposal a read.

Yours,
St.Ack


Trafodion Apache Incubator Proposal

Abstract

Trafodion is a webscale SQL-on-Hadoop solution enabling transactional or
operational workloads on Hadoop.

Proposal

Apache Trafodion builds on the scalability, elasticity, and flexibility of
Hadoop. Trafodion extends Hadoop to provide guaranteed transactional
integrity, enabling new kinds of big data applications to run on Hadoop. Key
features of Apache Trafodion include:

* Full-functioned ANSI SQL language support
* JDBC/ODBC connectivity for Linux/Windows clients
* Distributed ACID transaction protection across multiple statements,
tables and rows
* Performance improvements for OLTP workloads with compile-time and
run-time optimizations
* Support for large data sets using a parallel-aware query optimizer
* ANSI SQL security and data integrity constraints including referential
integrity

Hewlett-Packard Company submits this proposal to donate its Apache License,
Version 2.0 open source project known as Trafodion, its source code,
documentation, and web site content to the Apache Software Foundation in
order to build an open source community

Background

Trafodion is an open source project sponsored by HP, incubated at HP Labs
and HP-IT, to develop an enterprise-class SQL-on-Hadoop solution targeting
big data transactional or operational workloads. HP publically announced
the open source project and uploaded the source code to GitHub in June 2014.

The SQL compiler, optimizer and executor components of Trafodion have a
rich heritage. Under development since 1993, they were released as
commercial closed source software in various flavors such as HP NonStop
SQL/MX and HP Neoview. NonStop SQL/MX was designed for online transaction
processing on HP’s NonStop (formerly Tandem) fault-tolerant servers and is
known for its high availability, scalability, and performance. Hundreds of
companies and thousands of servers are running mission-critical
applications today on NonStop SQL/MX. In addition, much of these components
today are running internal to HP as the core of its Enterprise Data
Warehouse (EDW), managing over a PB of data.

Starting in 2013, the software was modified to run on HBase and a new
distributed transaction manager was written to run as an HBase co-processor.

Unlike most NOSQL and other SQL-on-Hadoop open source projects, Trafodion
provides comprehensive ANSI SQL language support including full-functioned
data definition (DDL), data manipulation (DML), transaction control (TCL)
and database utility support.

Trafodion provides comprehensive and standard SQL data manipulation support
including SELECT, INSERT, UPDATE, DELETE, and UPSERT/MERGE syntax with
language options including join variants, unions, where predicates,
aggregations (group by and having), sort ordering, sampling, correlated and
nested sub-queries, cursors, and many SQL functions.

Utilities are provided for updating table statistics used by the optimizer
for costing (i.e. selectivity/cardinality estimates) plan alternatives, for
displaying the chosen SQL execution plan, plan shaping, backup and
restoring the database, data loading and unloading, and a command line
utility for interfacing with the database engine.

Explicit control statements are provided to allow applications to define
transaction boundaries and to abort transactions when warranted, including
BEGIN WORK, COMMIT WORK, ROLLBACK WORK and SET TRANSACTION.

Trafodion supports ANSI’s grant/revoke semantics to define user and role
privileges in terms of managing and accessing the database objects.

Rationale

The name “Trafodion” (the Welsh word for transactions, pronounced
“Tra-vod-eee-on”) was chosen specifically to emphasize the differentiation
that Trafodion provides in closing a critical gap in the Hadoop ecosystem.
Trafodion builds on the scalability, elasticity, and flexibility of Hadoop.
Trafodion extends Hadoop to provide guaranteed transactional integrity,
enabling new kinds of big data applications to run on Hadoop.

Current Status

HP released the Trafodion code under the Apache License, Versi

Re: [VOTE] Release Apache Slider 0.80.0-incubating

[Devaraj Das]

+1 for the release

> On May 12, 2015, at 2:08 PM, Gour Saha  wrote:
> 
> Hello,
> 
> This is a call for a vote for releasing Apache Slider 0.80.0-incubating.
> 
> This is a source+binary release.
> 
> Summary of fixes: http://s.apache.org/539
> Release notes: http://s.apache.org/lUH
> Vote thread: http://s.apache.org/MNx
> Results: http://s.apache.org/oeK
> 
> Staged artifacts:
> https://repository.apache.org/content/repositories/orgapacheslider-1006/org/apache/slider
> 
> Git Source:
> https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;a=commit;h=d7e3449fa649dbb88388329724334f2d1aac2869
> SHA1: d7e3449fa649dbb88388329724334f2d1aac2869
> Tag: slider-0.80.0-incubating
> 
> PGP key:
> http://pgp.mit.edu/pks/lookup?op=vindex&search=gourks...@apache.org
> 
> Basic build/test instructions:
> http://slider.incubator.apache.org/developing/building.html
> 
> Please vote on releasing this package as Apache Slider 0.80.0-incubating.
> 
> This vote will be open for 72 hours.
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
> 
> Thank You,
> The Apache Slider Team
> 
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.

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

Re: [VOTE] Accept Trafodion into Apache Incubator

[Devaraj Das]

upon Apache HBase and extends it to support ACID
> transactions with HBase co-processors for distributed transaction
> management and recovery. Trafodion envisions future collaborations with the
> Apache HBase project on performance optimizations, such as in the areas of
> mixed workload support, High Availability, etc. It also provides
> transactional support and querying from native HBase tables as well.
> 
> Trafodion uses Apache Zookeeper to coordinate and manage the distribution
> of connection services across the cluster for load-balancing and high
> availability reconnection purposes in the event a Trafodion process should
> fail.
> 
> Trafodion also envisions working with the Apache Ambari project on enabling
> better Trafodion manageability. While Ambari focuses on system and
> component level performance metrics, Trafodion manageability will focus in
> a complimentary way on database workload monitoring and performance
> analytics with capabilities more geared towards database administrators.
> 
> There are alternative open source projects that are providing SQL-on-Hadoop
> capabilities, such as Apache Hive, Apache Drill, and Apache Phoenix. These
> are more focused on reporting and analytics across data structures
> supported on HDFS. In comparison to all of these technologies Trafodion
> provides a very complete implementation of ANSI SQL, one of the most
> sophisticated optimizers for such workloads, a completely parallel data
> flow architecture that does not materialize intermediate results unless
> necessary, full ACID transactional support, ANSI GRANT/REVOKE security, and
> other capabilities that would take decades to build in these products. On
> the other hand currently Trafodion is just focused on HBase and querying
> Hive, whereas Hive and Drill provide access to other data formats in HDFS.
> 
> An Excessive Fascination with the Apache Brand
> 
> We understand the reputation and value of the Apache brand, and no doubt
> believe that it will help us attract contributors and users. Our primary
> goal is to follow a proven, open source development and community building
> model that will make Trafodion successful and enable better collaboration
> with other Apache projects in the Hadoop ecosystem. We also understand the
> rules and guidelines about the use of the Apache brand and intend to follow
> them.
> 
> Documentation
> 
> Documentation and technical details on Trafodion can be found at:
> http://www.trafodion.org/
> 
> Initial Source
> 
> The source is available today in a public github repository:
> https://github.com/trafodion/trafodion.
> 
> Source and Intellectual Property Submission Plan
> 
> The source code has already been released under the Apache License, Version
> 2. The manuals have been released in Adobe PDF format. As part of the
> submission process, the source for the manuals will be converted from a
> proprietary DocBook XML format to AsciiDoc.
> 
> External Dependencies
> 
> Two dependencies do not have Apache compatible licenses and will be
> addressed as we enter incubation. One dependency is log4cpp, which is
> licensed under the LGPL. A compatible alternative might be Apache incubator
> project log4cxx. The other dependency is unixodbc, which is used as the
> ODBC driver manager. We will look into how Apache Hive manages being able
> to use this incompatible software and do similar. All other dependencies
> have Apache compatible licenses, including Apache 2.0, MIT/X11, MIT, and
> BSD.
> 
> Cryptography
> 
> Trafodion does not contain any cryptographic code. It does call
> cryptographic libraries: OpenSSL for C++ code and Java Cryptography
> Extension (JCE) for Java code.
> 
> Required Resources
> 
> Mailing Lists
> 
> priv...@trafodion.incubator.apache.org
> d...@trafodion.incubator.apache.org comm...@trafodion.incubator.apache.org
> 
> Git Repository
> 
> https://git-wip-us.apache.org/repos/afs/incubator-trafodion.git
> 
> Issue Tracking
> 
> JIRA: JIRA Trafodion (Trafodion)
> 
> 
> Initial Committers and Affiliation
> 
> Dave Birdsall, Hewlett-Packard Company, Dave.Birdsallhpcom
> Matt Brown, Hewlett-Packard Company, mattbrownhpcom
> Tharak Capirala, Hewlett-Packard Company, Tharak.Capiralahpcom
> Alice Chen, Hewlett-Packard Company, Alice.Chenhpcom
> John DeRoo, Hewlett-Packard Company, John.Deroohpcom
> Roberta Marton, Hewlett-Packard Company, Roberta.Martonhpcom
> Amanda Moran, Hewlett-Packard Company, Amanda.Kay.Moranhpcom
> Suresh Subbiah, Hewlett-Packard Company, Suresh.Subbiahhpcom
> Sandyha Sundaresan, Hewlett-Packard Company,
> Sandhya.Sundaresanhpcom
> 
> Sponsors
> 
> Champion
> 
> Michael Stack, Stackapacheorg
> 
> Nominated Mentors
> 
> Andrew Purtell apurtellapacheorg
> Devaraj Das, ddasapacheor
> Enis Söztutar, Enisapacheorg
> Lars Hofhansl, larshapacheorg
> Michael Stack, Stackapacheorg
> Roman Shaposhnik, rshaposhnikpivotalio
> 
> 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] Release Apache Ranger 0.5.0 (incubating)

[Devaraj Das]

+1 

From: Selvamohan Neethiraj 
Sent: Saturday, June 06, 2015 1:43 PM
To: general@incubator.apache.org
Subject: [VOTE] Release Apache Ranger 0.5.0 (incubating)

The Apache Ranger community has voted on and approved a proposal to release
Apache Ranger 0.5.0 (incubating) - Voting Thread Link
 .

This will be our second release since the project entered incubation in July
2014.

The ranger-0.5.0-rc3 release candidate is build from ranger-0.5 branch and
is available with the following artifacts up for a project vote:

Git tag for the release:
https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=shortlog;h=
refs/tags/ranger-0.5.0-rc3


Source release:
http://people.apache.org/~sneethir/ranger/ranger-0.5.0-rc3/ranger-0.5.0.tar.
gz


PGP Signature:
http://people.apache.org/~sneethir/ranger/ranger-0.5.0-rc3/ranger-0.5.0.tar.
gz.asc


MD5/SHA hash:

http://people.apache.org/~sneethir/ranger/ranger-0.5.0-rc3/ranger-0.5.0.tar.
gz.mds



Keys to verify the signature of the release artifact are available at:
https://people.apache.org/keys/group/ranger.asc

The vote will be open for at least 72 hours or until necessary number of
votes is reached.
 [   ] +1  approve
 [   ] +0  no opinion
 [   ] -1  disapprove (and reason why)

Here is my +1 (non binding)

Thanks
Selva-



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

Re: [VOTE] Accept Uniffle into the Apache Incubator

[Devaraj Das]

+1 (binding)

On Mon, May 30, 2022 at 9:12 PM Weiwei Yang  wrote:

> +1 (binding)
>
> On Mon, May 30, 2022 at 8:42 PM Ye Xianjin  wrote:
>
> > +1 (no-binding)
> >
> > Sent from my iPhone
> >
> > > On May 31, 2022, at 10:46 AM, Aloys Zhang 
> wrote:
> > >
> > > +1 （no-binding）
> > >
> > > XiaoYu  于2022年5月31日周二 10:12写道：
> > >
> > >> +1 (no-binding)
> > >>
> > >> Xun Liu  于2022年5月31日周二 10:07写道：
> > >>>
> > >>> +1 (binding) for me.
> > >>>
> > >>> Good luck!
> > >>>
> > >>> On Tue, May 31, 2022 at 10:04 AM Goson zhang 
> > >> wrote:
> > >>>
> >  +1 (no-binding)
> > 
> >  Good luck!!
> > 
> >  tison  于2022年5月31日周二 09:43写道：
> > 
> > > +1 (binding)
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > Jerry Shao  于2022年5月31日周二 09:37写道：
> > >
> > >> Hi all,
> > >>
> > >> Following up the [DISCUSS] thread on Uniffle[1] and Firestorm[2],
> I
> >  would
> > >> like to
> > >> call a VOTE to accept Uniffle into the Apache Incubator, please
> > >> check
> >  out
> > >> the Uniffle Proposal from the incubator wiki[3].
> > >>
> > >> Please cast your vote:
> > >>
> > >> [ ] +1, bring Uniffle into the Incubator
> > >> [ ] +0, I don't care either way
> > >> [ ] -1, do not bring Uniffle into the Incubator, because...
> > >>
> > >> The vote will open at least for 72 hours, and only votes from the
> > >> Incubator PMC are binding, but votes from everyone are welcome.
> > >>
> > >> [1]
> > >> https://lists.apache.org/thread/fyyhkjvhzl4hpzr52hd64csh5lt2wm6h
> > >> [2]
> > >> https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f
> > >> [3]
> > >
> > >> https://cwiki.apache.org/confluence/display/INCUBATOR/UniffleProposal
> > >>
> > >> Best regards,
> > >> Jerry
> > >>
> > >
> > 
> > >>
> > >> -
> > >> 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
> >
> >
>