RE: [VOTE] Release Apache Lens 2.0.1-beta-incubating

[Srikanth Sundarrajan]

Hi Justin,
   I am assuming you are attempting to compile with "mvn compile".  I am 
guessing the build is failing since the server module is depending on test-jars 
meant to be built in lens-server-api module during test-compile, and the same 
isn't available. Can you please try with "mvn clean compile test-compile" or 
"mvn package" or anything that includes the test-compile phase.

Regards
Srikanth Sundarrajan

> Subject: Re: [VOTE] Release Apache Lens 2.0.1-beta-incubating
> From: jus...@classsoftware.com
> Date: Sat, 28 Feb 2015 11:33:35 +1100
> To: general@incubator.apache.org
> 
> Hi,
> 
> +0 for now (due to compilation issues). If resolved would vote +1
> 
> For the source release:
> - signatures and hashes correct
> - disclaimer exists
> - incubating in release name
> - LICENSE good
> - NOTICE has minor issue (see below)
> - No unexpected binary files (but did notice two power point files - perhaps 
> a more OS format could be used? As these are simple images why not just png?)
> - All source code has headers
> - Can't compile from source
> 
> Minor issues
> - No need to mention any of the JS libraries in NOTICE as they are MIT 
> licensed [1]
> - It may be the that two power point files have embedded fonts as they 
> contain "Copyright 2007 Apple Inc., all rights reserved"?
> 
> Currently I'm unable to get the source package to compile (on OSX using Java 
> 1.7).
> 
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Lens Checkstyle Rules . SUCCESS [  0.862 s]
> [INFO] Lens .. SUCCESS [  0.029 s]
> [INFO] Lens API .. SUCCESS [  0.518 s]
> [INFO] Lens API for server and extensions  SUCCESS [  1.246 s]
> [INFO] Lens Cube . SUCCESS [  0.236 s]
> [INFO] Lens DB storage ... SUCCESS [  0.140 s]
> [INFO] Lens Query Library  SUCCESS [  0.127 s]
> [INFO] Lens Hive Driver .. SUCCESS [  0.657 s]
> [INFO] Lens Driver for JDBC .. SUCCESS [  0.157 s]
> [INFO] Lens Server ... FAILURE [ 11.472 s]
> [INFO] Lens client ... SKIPPED
> [INFO] Lens CLI .. SKIPPED
> [INFO] Lens Examples . SKIPPED
> [INFO] Lens Distribution . SKIPPED
> [INFO] Lens ML Lib ... SKIPPED
> [INFO] Lens Regression ... SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 16.060 s
> [INFO] Finished at: 2015-02-28T10:48:24+10:00
> [INFO] Final Memory: 24M/58M
> [INFO] 
> 
> [ERROR] Failed to execute goal on project lens-server: Could not resolve 
> dependencies for project 
> org.apache.lens:lens-server:war:2.0.1-beta-incubating: Could not find 
> artifact org.apache.lens:lens-driver-hive:jar:tests:2.0.1-beta-incubating in 
> inmobi.repo (https://github.com/InMobi/mvn-repo/raw/master/releases) -> [Help 
> 1]
> 
> Why does it appear that the Apache lens artefacts are publicly deployed here 
> [2], are these pre Apache incubator versions of the software?
> 
> For the binary distribution (again all minor issues).
> -  I'm concerned by the inclusion of  LICENSE-GPLv3 and LICENSE-LGPL file. I 
> assume these are there because of dual licensing. They should probably be 
> removed.
> - NOTICE contain several items that shouldn't be there (anything MIT licensed 
> for instance)
> - NOTICE may be missing required notice from included NOTICE file (I didn't 
> check in detail, but would be surprised if it was empty with all those jars)
> - LICENSE is missing licences for opalliance-1.0.jar and xz-1.0.jar (public 
> domain). Unless stated the assumption would be that they are Apache 
> licensed/copyright Apache.
> 
> Thanks,
> Justin
> 
> 1. http://www.apache.org/dev/licensing-howto.html#permissive-deps
> 2. https://github.com/InMobi/mvn-repo/tree/master/releases/org/apache/lens
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
  

Re: Larger than normal non-reporting podlings

[Srikanth Sundarrajan]

I will put up the report shortly for Falcon.

Sent from my iPhone

> On 06-Dec-2014, at 7:44 am, "John D. Ament"  wrote:
> 
> All,
> 
> There's a pretty large list of podlings not reporting this period.
> Mentors, any idea why?
> 
> Argus
> Drill
> Falcon
> Kalumet
> log4cxx2
> NPanday
> Ripple

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

RE: [VOTE] Graduation of Apache Falcon from the Incubator

[Srikanth Sundarrajan]

Hi Brane,
   No, He just didn't get to it before the vote was closed. As I had stated in 
my earlier response, he has already expressed his views on graduation in the 
earlier discuss thread that preceded the vote. Adding it here for reference.

http://mail-archives.apache.org/mod_mbox/incubator-falcon-dev/201410.mbox/%3CCAFfn_Rru5Q%3Dps3EMEneUsqUyuy7p5quyp35YHdkbE4o-p%2BpmJw%40mail.gmail.com%3E

Regards
Srikanth Sundarrajan

> Date: Wed, 5 Nov 2014 16:27:53 +0100
> From: br...@apache.org
> To: general@incubator.apache.org
> Subject: Re: [VOTE] Graduation of Apache Falcon from the Incubator
> 
> On 05.11.2014 16:05, Srikanth Sundarrajan wrote:
> > Hi Jan,
> > Venkatesh Seetharam is extremely active on the project, but couldn't 
> > vote on this thread,
> 
> Why not? Are you guys by any chance treating project committers and PPMC
> members differently?
> 
> -- Brane
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
  

RE: [VOTE] Graduation of Apache Falcon from the Incubator

[Srikanth Sundarrajan]

Hi Jan,
Venkatesh Seetharam is extremely active on the project, but couldn't vote 
on this thread, while the others have contributed heavily to the project 
earlier, but haven't been active in very recent times. The vote result was 
announced after nearly 4 days of voting as enough votes have been cast, I am 
sure all the PPMC members and more developers would have voted had it run for 
longer. 

Venkatesh Seetharam did express his views on the topic on the discuss thread on 
the dev-mailing list that preceded the vote.

Regards
Srikanth Sundarrajan

> Date: Wed, 5 Nov 2014 15:56:51 +0100
> Subject: Re: [VOTE] Graduation of Apache Falcon from the Incubator
> From: j...@apache.org
> To: general@incubator.apache.org
> 
> On 5 November 2014 15:46, Srikanth Sundarrajan  wrote:
> 
> > Hi Jan,
> > Venkatesh Seetharam, Sanjay Radia and Rishu Mehrothra, all PPMC members
> > haven't cast their votes. Chris Douglas & Arun Murthy are mentors on the
> > project and have voted +1 and are counted against the binding list.
> >
> so you have 3 PPMC members, who dont cast a vote on one of the most
> important votes for the the project,  sounds a bit strange to me, sounds
> like inactivity.
> 
> 
> > Overall affiliations:
> > InMobi: 8
> > Hortonworks: 5
> > Talend: 1
> >
> thanks for a speedy and detailed response. I did expect more spread in the
> community, has there over time been tried to recruit people from outside
> these companies ?
> 
> rgds
> jan i.
> 
> >
> > Regards
> > Srikanth Sundarrajan
> >
> > > Date: Wed, 5 Nov 2014 15:36:29 +0100
> > > Subject: Re: [VOTE] Graduation of Apache Falcon from the Incubator
> > > From: j...@apache.org
> > > To: general@incubator.apache.org
> > >
> > > Two questions:
> > >
> > > You list 13 binding +1 votes, no 0/-1, but the PMC list contains 14
> > people.
> > > Was there a person that did not vote ?
> > >
> > > More than half of the new committers are from hortonworks, can you
> > specify
> > > how the total affilation look like (not needed by name, just how many
> > from
> > > each company).
> > >
> > > thanks in advance for your answers.
> > > rgds
> > > jan i
> > >
> > >
> > > On 5 November 2014 15:05, Srikanth Sundarrajan 
> > wrote:
> > >
> > > > Hi Daniel,
> > > > Since incubation the following members were voted in as commiters.
> > > > •2014-08-28: Ruslan Ostafiychuk added as a committer
> > > > •2014-08-25: Raghav Kumar Gautam added as a committer
> > > > •2014-07-04: Jean-Baptiste Onofre added as a committer
> > > > •2014-03-06: Suhas Vasu added as a committer
> > > > •2014-03-06: Arpit Gupta added as a committer
> > > > Affiliations of these members:
> > > >
> > > > Ruslan Ostafiychuk: Hortonworks
> > > > Raghav Kumar Gautam: Hortonworks
> > > > Jean-Baptiste Onofre: Talend
> > > > Suhas Vasu: InMobi
> > > > Arpit Gupta: Hortonworks
> > > >
> > > > Regards
> > > > Srikanth Sundarrajan
> > > >
> > > > > Date: Wed, 5 Nov 2014 15:01:03 +0100
> > > > > From: humbed...@apache.org
> > > > > To: general@incubator.apache.org
> > > > > Subject: Re: [VOTE] Graduation of Apache Falcon from the Incubator
> > > > >
> > > > > JIRA tickets, releases etc is all very fascinating, but what about
> > the
> > > > > community growth?
> > > > > Do you have any statistics on that, and more specifically, the
> > diversity
> > > > > of the project?
> > > > >
> > > > > I don't mean to be a grump, but Apache is about community over code,
> > so
> > > > > you should really present that the community has grown and is ready
> > for
> > > > > graduation rather than that you have resolved X number of issues :)
> > > > >
> > > > > With regards,
> > > > > Daniel.
> > > > >
> > > > > On 2014-11-05 14:54, Jean-Baptiste Onofré wrote:
> > > > > > By the way, please find:
> > > > > >
> > > > > > - an update about Falcon activity resulting to the discussion for
> > the
> > > > > > graduation:
> > > > > >
> > > > > >
> > > >
> > http://mail-archives

RE: [VOTE] Graduation of Apache Falcon from the Incubator

[Srikanth Sundarrajan]

Hi Jan, 
Venkatesh Seetharam, Sanjay Radia and Rishu Mehrothra, all PPMC members haven't 
cast their votes. Chris Douglas & Arun Murthy are mentors on the project and 
have voted +1 and are counted against the binding list.

Overall affiliations:
InMobi: 8
Hortonworks: 5
Talend: 1

Regards
Srikanth Sundarrajan

> Date: Wed, 5 Nov 2014 15:36:29 +0100
> Subject: Re: [VOTE] Graduation of Apache Falcon from the Incubator
> From: j...@apache.org
> To: general@incubator.apache.org
> 
> Two questions:
> 
> You list 13 binding +1 votes, no 0/-1, but the PMC list contains 14 people.
> Was there a person that did not vote ?
> 
> More than half of the new committers are from hortonworks, can you specify
> how the total affilation look like (not needed by name, just how many from
> each company).
> 
> thanks in advance for your answers.
> rgds
> jan i
> 
> 
> On 5 November 2014 15:05, Srikanth Sundarrajan  wrote:
> 
> > Hi Daniel,
> > Since incubation the following members were voted in as commiters.
> > •2014-08-28: Ruslan Ostafiychuk added as a committer
> > •2014-08-25: Raghav Kumar Gautam added as a committer
> > •2014-07-04: Jean-Baptiste Onofre added as a committer
> > •2014-03-06: Suhas Vasu added as a committer
> > •2014-03-06: Arpit Gupta added as a committer
> > Affiliations of these members:
> >
> > Ruslan Ostafiychuk: Hortonworks
> > Raghav Kumar Gautam: Hortonworks
> > Jean-Baptiste Onofre: Talend
> > Suhas Vasu: InMobi
> > Arpit Gupta: Hortonworks
> >
> > Regards
> > Srikanth Sundarrajan
> >
> > > Date: Wed, 5 Nov 2014 15:01:03 +0100
> > > From: humbed...@apache.org
> > > To: general@incubator.apache.org
> > > Subject: Re: [VOTE] Graduation of Apache Falcon from the Incubator
> > >
> > > JIRA tickets, releases etc is all very fascinating, but what about the
> > > community growth?
> > > Do you have any statistics on that, and more specifically, the diversity
> > > of the project?
> > >
> > > I don't mean to be a grump, but Apache is about community over code, so
> > > you should really present that the community has grown and is ready for
> > > graduation rather than that you have resolved X number of issues :)
> > >
> > > With regards,
> > > Daniel.
> > >
> > > On 2014-11-05 14:54, Jean-Baptiste Onofré wrote:
> > > > By the way, please find:
> > > >
> > > > - an update about Falcon activity resulting to the discussion for the
> > > > graduation:
> > > >
> > > >
> > http://mail-archives.apache.org/mod_mbox/incubator-falcon-dev/201410.mbox/%3CBLU179-W92113438D987BB591B3BF4A4AD0%40phx.gbl%3E
> > > >
> > > >
> > > > - the graduation vote result on the Falcon mailing list:
> > > >
> > > >
> > http://mail-archives.apache.org/mod_mbox/incubator-falcon-dev/201411.mbox/%3cblu179-w397f9246e19603e9a06835a4...@phx.gbl%3E
> > > >
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > On 11/05/2014 02:48 PM, Jean-Baptiste Onofré wrote:
> > > >> Hi all,
> > > >>
> > > >> We wrapped up the vote on the Apache Falcon dev list in which the
> > > >> community expressed its desire to graduate to a top-level project.
> > > >>
> > > >> The vote has passed with:
> > > >> 13 binding +1 votes
> > > >> 8 non-binding +1 votes
> > > >> no 0 or -1 vote
> > > >>
> > > >> This is the Incubator vote to decide if Apache Falcon should graduate
> > > >> from the Incubator. Please see the resolution later in this e-mail.
> > > >> This vote is open for at least 72 hours.
> > > >>
> > > >> [ ] +1 Graduate Apache Falcon from the Incubator.
> > > >> [ ] +0 Don't care.
> > > >> [ ] -1 Don't graduate Apache Falcon from the Incubator because ...
> > > >>
> > > >> Thanks,
> > > >> Regards
> > > >> JB
> > > >>
> > > >>  resolution
> > > >> WHEREAS, the Board of Directors deems it to be in the best interests
> > of
> > > >> the Foundation and consistent with the Foundation's purpose to
> > establish
> > > >> a Project Management Committee charged with the creation and
> > maintenance
> > > >> of open-source software, for

RE: [VOTE] Graduation of Apache Falcon from the Incubator

[Srikanth Sundarrajan]

Hi Daniel,
Since incubation the following members were voted in as commiters.
•2014-08-28: Ruslan Ostafiychuk added as a committer
•2014-08-25: Raghav Kumar Gautam added as a committer
•2014-07-04: Jean-Baptiste Onofre added as a committer
•2014-03-06: Suhas Vasu added as a committer
•2014-03-06: Arpit Gupta added as a committer
Affiliations of these members:

Ruslan Ostafiychuk: Hortonworks
Raghav Kumar Gautam: Hortonworks
Jean-Baptiste Onofre: Talend
Suhas Vasu: InMobi
Arpit Gupta: Hortonworks

Regards
Srikanth Sundarrajan

> Date: Wed, 5 Nov 2014 15:01:03 +0100
> From: humbed...@apache.org
> To: general@incubator.apache.org
> Subject: Re: [VOTE] Graduation of Apache Falcon from the Incubator
> 
> JIRA tickets, releases etc is all very fascinating, but what about the 
> community growth?
> Do you have any statistics on that, and more specifically, the diversity 
> of the project?
> 
> I don't mean to be a grump, but Apache is about community over code, so 
> you should really present that the community has grown and is ready for 
> graduation rather than that you have resolved X number of issues :)
> 
> With regards,
> Daniel.
> 
> On 2014-11-05 14:54, Jean-Baptiste Onofré wrote:
> > By the way, please find:
> >
> > - an update about Falcon activity resulting to the discussion for the 
> > graduation:
> >
> > http://mail-archives.apache.org/mod_mbox/incubator-falcon-dev/201410.mbox/%3CBLU179-W92113438D987BB591B3BF4A4AD0%40phx.gbl%3E
> >  
> >
> >
> > - the graduation vote result on the Falcon mailing list:
> >
> > http://mail-archives.apache.org/mod_mbox/incubator-falcon-dev/201411.mbox/%3cblu179-w397f9246e19603e9a06835a4...@phx.gbl%3E
> >  
> >
> >
> > Regards
> > JB
> >
> > On 11/05/2014 02:48 PM, Jean-Baptiste Onofré wrote:
> >> Hi all,
> >>
> >> We wrapped up the vote on the Apache Falcon dev list in which the
> >> community expressed its desire to graduate to a top-level project.
> >>
> >> The vote has passed with:
> >> 13 binding +1 votes
> >> 8 non-binding +1 votes
> >> no 0 or -1 vote
> >>
> >> This is the Incubator vote to decide if Apache Falcon should graduate
> >> from the Incubator. Please see the resolution later in this e-mail.
> >> This vote is open for at least 72 hours.
> >>
> >> [ ] +1 Graduate Apache Falcon from the Incubator.
> >> [ ] +0 Don't care.
> >> [ ] -1 Don't graduate Apache Falcon from the Incubator because ...
> >>
> >> Thanks,
> >> Regards
> >> JB
> >>
> >>  resolution
> >> WHEREAS, the Board of Directors deems it to be in the best interests of
> >> the Foundation and consistent with the Foundation's purpose to establish
> >> a Project Management Committee charged with the creation and maintenance
> >> of open-source software, for distribution at no charge to the public,
> >> related to Big Data management platform covering data pipelines, data
> >> motion, data lifecycle management, data discovery & governance
> >>
> >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >> (PMC), to be known as the "Apache Falcon Project", be and hereby is
> >> established pursuant to Bylaws of the Foundation; and be it further
> >>
> >> RESOLVED, that the Apache Falcon Project be and hereby is responsible
> >> for the creation and maintenance of software related to interactive
> >> analysis of large-scale datasets; and be it further RESOLVED, that the
> >> office of "Vice President, Apache Falcon" 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 Falcon Project, and to have primary
> >> responsibility for management of the projects within the scope of
> >> responsibility of the Apache Falcon 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 Falcon Project:
> >>
> >> * Srikanth Sundarrajan 
> >> * Venkatesh Seetharam 
> >> * Shwetha GS 
> >> * Shaik Idris 
> >> * Sanjay Radia 
> >> * Sharad Agarwal 
> >> * Amareshwari SR 
> >> * Samarth Gupta 
> >> * Rishu Mehrothra 
> >> * Arpit Gupta 
> >> * Suhas Vasu 
> >> * Jean-Baptiste Onofré 
> >> * Ruslan Ostafiychuk 
> >> * Raghav Kumar

RE: [VOTE] Accept Lens into the Apache Incubator (earlier called Grill)

[Srikanth Sundarrajan]

+1 (non-binding)

Srikanth Sundarrajan

> Date: Mon, 6 Oct 2014 17:21:41 +0530
> Subject: [VOTE] Accept Lens into the Apache Incubator (earlier called Grill)
> From: sha...@apache.org
> To: general@incubator.apache.org
> 
> Following the discussion earlier in the thread
> https://www.mail-archive.com/general@incubator.apache.org/msg45208.html
> I would like to call a Vote for accepting Lens as a new incubator project.
> 
> The proposal is available at:
> https://wiki.apache.org/incubator/LensProposal
> 
> Vote is open till Oct 09, 2014 4 PM PST.
> 
>  [ ] +1 accept Lens in the Incubator
>  [ ] +/-0
>  [ ] -1 because...
> 
> Only Votes from Incubator PMC members are binding, but all are welcome to
> express their thoughts.
> I am +1 (non-binding).
> 
> Thanks
> Sharad
  

[ANNOUNCE] Apache Falcon 0.5-incubating released

[Srikanth Sundarrajan]

The Apache Falcon team is happy to announce the release of Apache Falcon - 
version 0.5-incubating.

Apache Falcon is a data processing and management solution for Hadoop designed 
for data motion, coordination of data pipelines, lifecycle management, and data 
discovery. Falcon enables end consumers to quickly onboard their data and its 
associated processing and management tasks on Hadoop clusters.  See 
http://falcon.incubator.apache.org/ for more details.
 
We thank everyone who made this release possible.

Thanks
Srikanth Sundarrajan (on behalf of Apache Falcon Team)
  

[RESULT] [VOTE] Release of Apache Falcon 0.5-incubating - RC6

[Srikanth Sundarrajan]

Thanks for taking time to review and vote on this release.  The vote passes 
with three binding +1's and
no -1's.

The binding votes were from:
Justin McLean 
Jean-Baptiste Onofre
Chris Douglas

We'll now move the artifacts to Apache mirrors.

Thanks
Srikanth Sundarrajan

> From: srik...@hotmail.com
> To: general@incubator.apache.org
> Subject: [VOTE] Release of Apache Falcon 0.5-incubating - RC6
> Date: Mon, 15 Sep 2014 19:50:25 +0530
> 
> Have generated a new release candidate for Apache Falcon 0.5 post feedback 
> from IPMC (Refer: 
> http://mail-archives.apache.org/mod_mbox/incubator-general/201409.mbox/%3CBLU179-W4635CB0EDA7F8C86C013E9A4CB0%40phx.gbl%3E).
> 
> A vote was held among the developers for the previous release candidate (RC5) 
> and the release has been accepted. Details of the vote and the result can be 
> found at http://s.apache.org/falcon-0.5-rc5-dev-vote and 
> http://s.apache.org/falcon-0.5-rc5-dev-vote-result respectively. 
> 
> Specific changes made in RC6 compared to RC5 is 
> https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=commitdiff;h=876ff83b9002052b96e967ebd4d2f881ed27b338
> 
> The source tar ball can be downloaded from 
> http://people.apache.org/~sriksun/0.5-incubating-rc6, along with signature 
> and checksum files.
> 
> MD5(apache-falcon-0.5-incubating-sources.tar.gz)= 
> 6e0e4c32fa3e8950ffac5bc363f1676f
> SHA1(apache-falcon-0.5-incubating-sources.tar.gz)= 
> be878ac54571cf2e17a5fca30e3a07f4d1951848
> 
> Git tag for the release is 
> https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=tag;h=refs/tags/release-0.5-rc6
>  (hash: 876ff83b9002052b96e967ebd4d2f881ed27b338)
> 
> More than 140 JIRAs have been closed as part of this release and the release 
> notes can be accessed from http://s.apache.org/falcon-0.5-release-notes and 
> the change logs are available at http://s.apache.org/falcon-0.5-change-log
> 
> The release has been signed through key(D2498DC9):
> http://s.apache.org/pgp-sriksun
> 
> Keys to verify the signature of the release artifact are available at:
> http://www.apache.org/dist/incubator/falcon/KEYS
> 
> Please vote on the release. The vote will close no sooner than Sep 19, 2014 
> 09:00 UTC
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
> 
> Thanks
> Srikanth Sundarrajan 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
  

[VOTE] Release of Apache Falcon 0.5-incubating - RC6

[Srikanth Sundarrajan]

Have generated a new release candidate for Apache Falcon 0.5 post feedback from 
IPMC (Refer: 
http://mail-archives.apache.org/mod_mbox/incubator-general/201409.mbox/%3CBLU179-W4635CB0EDA7F8C86C013E9A4CB0%40phx.gbl%3E).

A vote was held among the developers for the previous release candidate (RC5) 
and the release has been accepted. Details of the vote and the result can be 
found at http://s.apache.org/falcon-0.5-rc5-dev-vote and 
http://s.apache.org/falcon-0.5-rc5-dev-vote-result respectively. 

Specific changes made in RC6 compared to RC5 is 
https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=commitdiff;h=876ff83b9002052b96e967ebd4d2f881ed27b338

The source tar ball can be downloaded from 
http://people.apache.org/~sriksun/0.5-incubating-rc6, along with signature and 
checksum files.

MD5(apache-falcon-0.5-incubating-sources.tar.gz)= 
6e0e4c32fa3e8950ffac5bc363f1676f
SHA1(apache-falcon-0.5-incubating-sources.tar.gz)= 
be878ac54571cf2e17a5fca30e3a07f4d1951848

Git tag for the release is 
https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=tag;h=refs/tags/release-0.5-rc6
 (hash: 876ff83b9002052b96e967ebd4d2f881ed27b338)

More than 140 JIRAs have been closed as part of this release and the release 
notes can be accessed from http://s.apache.org/falcon-0.5-release-notes and the 
change logs are available at http://s.apache.org/falcon-0.5-change-log

The release has been signed through key(D2498DC9):
http://s.apache.org/pgp-sriksun

Keys to verify the signature of the release artifact are available at:
http://www.apache.org/dist/incubator/falcon/KEYS

Please vote on the release. The vote will close no sooner than Sep 19, 2014 
09:00 UTC

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

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

[CANCEL] [VOTE] Release of Apache Falcon 0.5-incubating - RC5

[Srikanth Sundarrajan]

Cancelling this vote as there are some license related errors in the release 
tar ball. Will initiate a new vote with the fixes.

@Justin, one of the dependent components (Apache Oozie 4.0) requires java 1.6 
and hence the dependency on Java 1.6.

Thanks
Srikanth Sundarrajan


> Date: Sun, 14 Sep 2014 14:48:44 -0700
> Subject: Re: [VOTE] Release of Apache Falcon 0.5-incubating - RC5
> From: cdoug...@apache.org
> To: general@incubator.apache.org
>
> On Sun, Sep 14, 2014 at 1:59 PM, Justin Mclean  
> wrote:
>> Sorry but it's -1 (binding) from me. Everything is good except that the 
>> jQuery has had an Apache license header added to it. (in 
>> ./html5-ui/js/jquery-1.11.0.min.js) If other incubator members think this 
>> isn't a blocker I'll change my vote.
>>
>> jQuery is MIT licensed [1] so should be treated the same as the other 
>> bundled MIT bits and put in LICENSE. (If the license could be changed to 
>> Apache then this would needed to have been mentioned in NOTICE.)
>
> Unfortunately, I think this is a fair catch.
>
> Srikanth, we do *not* need another vote of the PPMC on the 0.5 release
> if the only change is deleting this header and adding the jquery
> license with the others. This should be a quick fix. Could you roll a
> new RC with only this change, and start a new vote thread on
> general@incubator? -C
>
>> Here's what I checked:
>> - File name contain incubating
>> - DISCLAIMER exists
>> - LICENSE and NOTICE good (older version of bootstrap is handled correctly, 
>> if newer version is used than LICENSE would need to change)
>> - All source files contain Apache header
>> - No unexpected binary files in release
>> - Can compile from source
>>
>> Minor issues you may want to fix for the next release.
>> - License has:
>> This product bundles dust-helpers 1.2.0, which is available under a
>> MIT license. For details, see docs/license/dust-LICENSE.txt
>>
>> Which should be this:
>> This product bundles dust-helpers 1.2.0, which is available under a
>> MIT license. For details, see docs/license/dust-helpers-LICENSE.txt
>>
>> - A RELEASE_NOTES listing changes from previous version/list of bugs fixed 
>> would be helpful.
>> - To compile you need to set MVN_CMD, add this to installation instructions.
>> - Looks like a packaging issue in the process directory with a directory 
>> named "${system.lib.location}"
>>
>> Would also be nice if at all possible if you could compile with Java 1.7 
>> rather than 1.6 as 1.6 has been EOLed
>>
>> Thanks,
>> Justin
>>
>> 1. https://jquery.org/license/
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
  
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release of Apache Falcon 0.5-incubating - RC5

[Srikanth Sundarrajan]

Thanks for taking the time to review. Will cancel this and spin a new one with 
suggested corrections.

Sent from my iPhone

> On 15-Sep-2014, at 3:31 am, "Roman Shaposhnik"  wrote:
> 
>> On Sun, Sep 14, 2014 at 2:47 PM, Marvin Humphrey  
>> wrote:
>>> On Sun, Sep 14, 2014 at 1:59 PM, Justin Mclean  
>>> wrote:
>>> 
>>> Sorry but it's -1 (binding) from me.  Everything is good except that the
>>> jQuery has had an Apache license header added to it.  (in
>>> ./html5-ui/js/jquery-1.11.0.min.js) If other incubator members think this
>>> isn't a blocker I'll change my vote.
>> 
>> I concur with your reasoning, Justin.  This is not just a licensing
>> documentation bug, it's a licensing error.
> 
> Fully agree.
> 
> Thanks,
> Roman.
> 
> -
> 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 of Apache Falcon 0.5-incubating - RC5

[Srikanth Sundarrajan]

Hello,
    We have reworked the release for Falcon 0.5 post feedback on LICENSE and 
NOTICE from IPMC. Special thanks to Sebb, Justin Mclean and Chris Douglas for 
helping us with this. 
 
A vote was held among the developers for this release candidate and the release 
has been accepted. Details of the vote and the result can be found at 
http://s.apache.org/falcon-0.5-rc5-dev-vote and 
http://s.apache.org/falcon-0.5-rc5-dev-vote-result respectively.
 
The source tar ball can be downloaded from 
http://people.apache.org/~sriksun/0.5-incubating-rc5, along with signature and 
checksum files.
 
SHA1 checksum : 986d50b97710e252c1b6027dda9354b1c4127869
MD5 checksum: 33e6d2e4cea237be470020bb69a350f7
 
Git tag for the release is 
https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=tag;h=refs/tags/release-0.5-rc5,
 tag's hash 5a9b96a74014718a3683c71875f2a020519eb587

More than 140 JIRAs have been closed as part of this release and the release 
notes can be accessed from http://s.apache.org/falcon-0.5-release-notes and the 
change logs are available at http://s.apache.org/falcon-0.5-change-log
 
The release has been signed through key(D2498DC9):
http://s.apache.org/pgp-sriksun
 
Keys to verify the signature of the release artifact are available at:
http://www.apache.org/dist/incubator/falcon/KEYS
 
Please vote on the release. The vote will close no sooner than Sep 18, 2014 
17:00 UTC
 
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
 
PS: Earlier "call for vote" message sent on the mailing list had incorrectly 
specified an expiry time on the same and the same has been reworded. Also added 
the hash of the git tag.

Regards
Srikanth Sundarrajan 

> From: srik...@hotmail.com
> To: general@incubator.apache.org
> Subject: [VOTE] Release of Apache Falcon 0.5-incubating - RC5
> Date: Sun, 14 Sep 2014 13:11:09 +0530
>
> Hello,
> We have reworked the release for Falcon 0.5 post feedback on LICENSE and 
> NOTICE from IPMC. Special thanks to Sebb, Justin Mclean and Chris Douglas for 
> helping us with this.
>
> A vote was held among the developers for this release candidate and the 
> release has been accepted. Details of the vote and the result can be found at 
> http://s.apache.org/falcon-0.5-rc5-dev-vote and 
> http://s.apache.org/falcon-0.5-rc5-dev-vote-result respectively.
>
> The source tar ball can be downloaded from 
> http://people.apache.org/~sriksun/0.5-incubating-rc5, along with signature 
> and checksum files.
>
> SHA1 checksum : 986d50b97710e252c1b6027dda9354b1c4127869
> MD5 checksum: 33e6d2e4cea237be470020bb69a350f7
>
> Git tag for the release is 
> https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=tag;h=refs/tags/release-0.5-rc5
>
> More than 140 JIRAs have been closed as part of this release and the release 
> notes can be accessed from http://s.apache.org/falcon-0.5-release-notes and 
> the change logs are available at http://s.apache.org/falcon-0.5-change-log
>
> The release has been signed through key(D2498DC9):
> http://s.apache.org/pgp-sriksun
>
> Keys to verify the signature of the release artifact are available at:
> http://www.apache.org/dist/incubator/falcon/KEYS
>
> Please vote on the release. Vote will expire on Sep 18, 2014 10:00AM IST.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Regards
> Srikanth Sundarrajan
>
  
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: [VOTE] Release of Apache Falcon 0.5-incubating - RC5

[Srikanth Sundarrajan]

Thanks for the suggestions, I will send a revised vote on the same thread, with 
the revised wordings.

Srikanth Sundarrajan


> Date: Sun, 14 Sep 2014 14:06:59 +0100
> Subject: Re: [VOTE] Release of Apache Falcon 0.5-incubating - RC5
> From: seb...@gmail.com
> To: general@incubator.apache.org
>
> On 14 September 2014 13:45, John D. Ament  wrote:
>> Srikanth
>>
>> Just replace expiry with closes ( or until enough votes have been cast )
>> should be enough.
>
> A common incantation is
>
> "The vote will close no sooner than 72 hours from now, i.e. after "
>
> Please use GMT/UTC for the time as people are likely to know their GMT
> offset but will not know every local time - e.g. I've no idea offhand
> what IST means nor what its offset is.
>
>> On Sep 14, 2014 8:33 AM, "Srikanth Sundarrajan"  wrote:
>>
>>> Git hash tag for the release is 5a9b96a74014718a3683c71875f2a020519eb587
>>>
>>>
>>> https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=commit;h=5a9b96a74014718a3683c71875f2a020519eb587
>>>
>>> @Sebb, Thanks for pointing out the gap relating to vote expiry. What is
>>> the recommendation on this, I hope we can continue on the vote and keep it
>>> open as long as it is required to complete review of the release and
>>> related discussions if needed.
>>>
>>> Thanks
>>> Srikanth Sundarrajan
>>>
>>> ----
>>>> Date: Sun, 14 Sep 2014 12:39:42 +0100
>>>> Subject: Re: [VOTE] Release of Apache Falcon 0.5-incubating - RC5
>>>> From: seb...@gmail.com
>>>> To: general@incubator.apache.org
>>>>
>>>> On 14 September 2014 08:41, Srikanth Sundarrajan 
>>> wrote:
>>>>> Hello,
>>>>> We have reworked the release for Falcon 0.5 post feedback on LICENSE
>>> and NOTICE from IPMC. Special thanks to Sebb, Justin Mclean and Chris
>>> Douglas for helping us with this.
>>>>>
>>>>> A vote was held among the developers for this release candidate and the
>>> release has been accepted. Details of the vote and the result can be found
>>> at http://s.apache.org/falcon-0.5-rc5-dev-vote and
>>
>> http://s.apache.org/falcon-0.5-rc5-dev-vote-result respectively.
>>>>>
>>>>> The source tar ball can be downloaded from
>>> http://people.apache.org/~sriksun/0.5-incubating-rc5, along with
>>> signature and checksum files.
>>>>>
>>>>> SHA1 checksum : 986d50b97710e252c1b6027dda9354b1c4127869
>>>>> MD5 checksum: 33e6d2e4cea237be470020bb69a350f7
>>>>
>>>>> Git tag for the release is
>>> https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=tag;h=refs/tags/release-0.5-rc5
>>>>
>>>> Git tags are not immutable - what is the hash for the tag?
>>>>
>>>>> More than 140 JIRAs have been closed as part of this release and the
>>> release notes can be accessed from
>>> http://s.apache.org/falcon-0.5-release-notes and the change logs are
>>> available at http://s.apache.org/falcon-0.5-change-log
>>>>>
>>>>> The release has been signed through key(D2498DC9):
>>>>> http://s.apache.org/pgp-sriksun
>>>>>
>>>>> Keys to verify the signature of the release artifact are available at:
>>>>> http://www.apache.org/dist/incubator/falcon/KEYS
>>>>
>>>> (BTW, the old release 0.3 should have been deleted by now; also 0.4
>>>> should be removed from the dist/ directory shortly after 0.5 is
>>>> released. It is important to keep the release directory tidy [1])
>>>>
>>>> [1] http://www.apache.org/dev/release.html#when-to-archive
>>>>
>>>>>
>>>>> Please vote on the release. Vote will expire on Sep 18, 2014 10:00AM
>>> IST.
>>>>
>>>> Votes don't expire.
>>>> They have a minimum time to closure of 72 hours.
>>>>
>>>>>
>>>>> [ ] +1 approve
>>>>> [ ] +0 no opinion
>>>>> [ ] -1 disapprove (and reason why)
>>>>>
>>>>> Regards
>>>>> Srikanth Sundarrajan
>>>>>
>>>>> -
>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>>>
>>>>
>>>> -
>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>>
>>>
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
  
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: [VOTE] Release of Apache Falcon 0.5-incubating - RC5

[Srikanth Sundarrajan]

Git hash tag for the release is 5a9b96a74014718a3683c71875f2a020519eb587

https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=commit;h=5a9b96a74014718a3683c71875f2a020519eb587

@Sebb, Thanks for pointing out the gap relating to vote expiry. What is the 
recommendation on this, I hope we can continue on the vote and keep it open as 
long as it is required to complete review of the release and related 
discussions if needed.

Thanks
Srikanth Sundarrajan


> Date: Sun, 14 Sep 2014 12:39:42 +0100
> Subject: Re: [VOTE] Release of Apache Falcon 0.5-incubating - RC5
> From: seb...@gmail.com
> To: general@incubator.apache.org
>
> On 14 September 2014 08:41, Srikanth Sundarrajan  wrote:
>> Hello,
>> We have reworked the release for Falcon 0.5 post feedback on LICENSE and 
>> NOTICE from IPMC. Special thanks to Sebb, Justin Mclean and Chris Douglas 
>> for helping us with this.
>>
>> A vote was held among the developers for this release candidate and the 
>> release has been accepted. Details of the vote and the result can be found 
>> at http://s.apache.org/falcon-0.5-rc5-dev-vote and 
>> http://s.apache.org/falcon-0.5-rc5-dev-vote-result respectively.
>>
>> The source tar ball can be downloaded from 
>> http://people.apache.org/~sriksun/0.5-incubating-rc5, along with signature 
>> and checksum files.
>>
>> SHA1 checksum : 986d50b97710e252c1b6027dda9354b1c4127869
>> MD5 checksum: 33e6d2e4cea237be470020bb69a350f7
>
>> Git tag for the release is 
>> https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=tag;h=refs/tags/release-0.5-rc5
>
> Git tags are not immutable - what is the hash for the tag?
>
>> More than 140 JIRAs have been closed as part of this release and the release 
>> notes can be accessed from http://s.apache.org/falcon-0.5-release-notes and 
>> the change logs are available at http://s.apache.org/falcon-0.5-change-log
>>
>> The release has been signed through key(D2498DC9):
>> http://s.apache.org/pgp-sriksun
>>
>> Keys to verify the signature of the release artifact are available at:
>> http://www.apache.org/dist/incubator/falcon/KEYS
>
> (BTW, the old release 0.3 should have been deleted by now; also 0.4
> should be removed from the dist/ directory shortly after 0.5 is
> released. It is important to keep the release directory tidy [1])
>
> [1] http://www.apache.org/dev/release.html#when-to-archive
>
>>
>> Please vote on the release. Vote will expire on Sep 18, 2014 10:00AM IST.
>
> Votes don't expire.
> They have a minimum time to closure of 72 hours.
>
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>> Regards
>> Srikanth Sundarrajan
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
  
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release of Apache Falcon 0.5-incubating - RC5

[Srikanth Sundarrajan]

Hello,
    We have reworked the release for Falcon 0.5 post feedback on LICENSE and 
NOTICE from IPMC. Special thanks to Sebb, Justin Mclean and Chris Douglas for 
helping us with this. 

A vote was held among the developers for this release candidate and the release 
has been accepted. Details of the vote and the result can be found at 
http://s.apache.org/falcon-0.5-rc5-dev-vote and 
http://s.apache.org/falcon-0.5-rc5-dev-vote-result respectively.

The source tar ball can be downloaded from 
http://people.apache.org/~sriksun/0.5-incubating-rc5, along with signature and 
checksum files.

SHA1 checksum : 986d50b97710e252c1b6027dda9354b1c4127869
MD5 checksum: 33e6d2e4cea237be470020bb69a350f7

Git tag for the release is 
https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=tag;h=refs/tags/release-0.5-rc5

More than 140 JIRAs have been closed as part of this release and the release 
notes can be accessed from http://s.apache.org/falcon-0.5-release-notes and the 
change logs are available at http://s.apache.org/falcon-0.5-change-log

The release has been signed through key(D2498DC9):
http://s.apache.org/pgp-sriksun

Keys to verify the signature of the release artifact are available at:
http://www.apache.org/dist/incubator/falcon/KEYS

Please vote on the release. Vote will expire on Sep 18, 2014 10:00AM IST.

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

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

RE: help needed

[Srikanth Sundarrajan]

Hi Subhasis,
   You might want to checkout https://incubator.apache.org/guides/proposal.html

Regards
Srikanth Sundarrajan

-
> From: subhasis.go...@gmail.com
> Date: Sat, 22 Mar 2014 09:42:44 +0530
> Subject: help needed
> To: general@incubator.apache.org
>
> Hello,
> I had a query - basically sometime back I had submitted one project idea
> to this forum. I'm totally new to this process. I had gone through the docs
> but didn't quite get the it very clearly.
> I'm yet to receive any feedback or suggestion from you. I'm not sure, the
> idea could be very simple or flimsy - but still I would look for your
> valuable suggestions. That would help me a lot in future.
> I'm sharing the outline of my idea again -
> https://drive.google.com/file/d/0B9Q1BwMfX5KcOWZaZk5TZmxodjg/edit?usp=sharing
> Github Repo: https://github.com/subhasisgorai/HQuery/tree/master/MyMSWork
>
> I thank you in anticipation ..
> - Subhasis Gorai
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[ANNOUNCE] Apache Falcon 0.3-incubating released

[Srikanth Sundarrajan]

Hello,

The Apache Falcon team is pleased to announce the release of version 
0.3-incubating from the Apache Incubator. Falcon is a data processing and 
management solution for Hadoop designed for data motion, coordination of data 
pipelines, lifecycle management, and data discovery. Falcon enables end 
consumers to quickly onboard their data and its associated processing and 
management tasks on Hadoop clusters.

Link to release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314429&version=12324423

The most recent source release can be obtained from an Apache Mirror:
http://www.apache.org/dyn/closer.cgi/incubator/falcon

For general information on Apache Falcon, please visit the project website:
http://falcon.incubator.apache.org

Disclaimer:
Apache Falcon is an effort undergoing incubation at the Apache Software 
Foundation (ASF), sponsored by the Apache Incubator PMC.

Incubation is required of all newly accepted projects until a further review 
indicates that the infrastructure, communications, and decision making process 
have stabilized in a manner consistent with other successful ASF projects.

While incubation status is not necessarily a reflection of the completeness or 
stability of the code, it does indicate that the project has yet to be fully 
endorsed by the ASF.

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

[ANNOUNCE] Apache Falcon 0.3-incubating released

[Srikanth Sundarrajan]

Hello,

The Apache Falcon team is pleased to announce the release of version 
0.3-incubating from the Apache Incubator. Falcon is a data processing and 
management solution for Hadoop designed for data motion, coordination of data 
pipelines, lifecycle management, and data discovery. Falcon enables end 
consumers to quickly onboard their data and its associated processing and 
management tasks on Hadoop clusters.

Link to release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314429&version=12324423

The most recent source release can be obtained from an Apache Mirror:
http://www.apache.org/dyn/closer.cgi/incubator/falcon

For general information on Apache Falcon, please visit the project website:
http://falcon.incubator.apache.org

Disclaimer:
Apache Falcon is an effort undergoing incubation at the Apache Software 
Foundation (ASF), sponsored by the Apache Incubator PMC.

Incubation is required of all newly accepted projects until a further review 
indicates that the infrastructure, communications, and decision making process 
have stabilized in a manner consistent with other successful ASF projects.

While incubation status is not necessarily a reflection of the completeness or 
stability of the code, it does indicate that the project has yet to be fully 
endorsed by the ASF.

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

RE: Review of binary tar ball for Apache Falcon (incubating) 0.3 RC4

[Srikanth Sundarrajan]

Thanks. This is fairly useful. Will rework and put up a new tar ball 
accommodating these comments.

Regards
Srikanth Sundarrajan


> Date: Tue, 20 Aug 2013 11:45:28 +0100
> Subject: Re: Review of binary tar ball for Apache Falcon (incubating) 0.3 RC4
> From: seb...@gmail.com
> To: general@incubator.apache.org
>
> On 20 August 2013 06:19, Srikanth Sundarrajan  wrote:
>> Hello,
>> We had recently called for a vote on Apache Falcon 0.3 RC4 (source tar ball) 
>> and the result has been announced (http://s.apache.org/wLO). We intend to 
>> also make a binary tar ball available for user convenience. We would really 
>> appreciate if someone on this mailing list could take a few minutes to 
>> review it for compliance.
>>
>> The tar ball and signatures are available at 
>> http://people.apache.org/~sriksun/falcon-release/0.3-rc4-bin/
>
> The NOTICE file starts with:
> =
> == NOTICE file corresponding to the section 4 d of ==
> == the Apache License, Version 2.0, ==
> == in this case for the Apache Falcon distribution. ==
> =
>
> This is wrong; it should be removed.
> The first two lines should be:
>
> Apache Falcon (incubating)
> Copyright 2011-2013 The Apache Software Foundation
>
> i.e. no blank lines between them.
>
> The rest of the NOTICE file is for *required* notices.
> And they must only be required notices for software that is actually included.
>
> It's not obvious that *any* of the attributions are actually required.
> Remember that the NOTICE file must only contain required attributions; see:
>
> http://www.apache.org/dev/licensing-howto.html#mod-notice
>
> ==
>
> It's quite difficult to find the licences for the individual jars in 
> LICENSE.txt
> For example, at first I thought there was no license for
> activation-1.1.jar, but then I discovered that this is covered by the
> "javax" section.
> It would be a lot easier to follow (and manage as dependencies
> changed) if the jar names were itemised in the LICENSE.txt file, along
> with pointers to their licenses.
> It's not necessary for the licenses to be included in LICENSE.txt,
> they can be in separate files so long as LICENSE.txt references them
> clearly.
>
> I could not find a license reference for:
> annotations-1.3.2.jar
> aopalliance-1.0.jar
>
> and several others don't appear to have licenses.
>
> ==
>
> The binary file is much larger than it need be; several jars are
> included twice in the top level jar in different directories.
> And there are two different versions of some of the jars.
> Furthermore, just about all the jars are also included in the falcon.war file.
> That does not have any identical duplicates, because the jars are all
> in a single directory.
> However it does have two versions of servlet-api and stax-api, as well as
> commons-logging-1.1.jar/commons-logging-api-1.1.jar
> commons-beanutils-1.8.3.jar
> commons-beanutils-core-1.8.0.jar
>
> That seems unnecessary; each jar could be included once and copied
> into any required additional locations as part of the installation.
> Mixing jar versions in the same directory is also likely to result in
> some classpath problems.
>
>> Regards
>> Srikanth Sundarrajan
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Review of binary tar ball for Apache Falcon (incubating) 0.3 RC4

[Srikanth Sundarrajan]

Hello,
We had recently called for a vote on Apache Falcon 0.3 RC4 (source tar ball) 
and the result has been announced  (http://s.apache.org/wLO). We intend to also 
make a binary tar ball available for user convenience. We would really 
appreciate if someone on this mailing list could take a few minutes to review 
it for compliance.

The tar ball and signatures are available at 
http://people.apache.org/~sriksun/falcon-release/0.3-rc4-bin/

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

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

[Srikanth Sundarrajan]

Hello,
Thanks for voting on the Falcon 0.3 Release.

We have 9 +1 votes with 4 binding IPMC votes.

(binding)
=
Arun Murthy
Alan Gates
Chris Douglas
Devaraj Das

(non-binding)
=
Ashish Paliwal
Venkat Ranganathan
Srikanth Sundarrajan
Venkatesh Seetharam
Luciano Resende

PS: While Devaraj Das, Arun Murthy & Luciano Resende voted on the thread in 
general@incubator, others have voted on the original thread in dev@falcon 
(http://s.apache.org/ywq)

Will now work on pushing the release to dist. 

Thanks
Srikanth Sundarrajan


> From: srik...@hotmail.com
> To: general@incubator.apache.org
> Subject: [VOTE] Release of Apache Falcon (incubating) v0.3
> Date: Sun, 11 Aug 2013 23:39:42 -0700
>
> 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

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

[Srikanth Sundarrajan]

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

RE: [VOTE] Accept Samza into the Incubator

[Srikanth Sundarrajan]

+1 (non-binding)


> From: jgho...@gmail.com
> Date: Fri, 26 Jul 2013 12:52:49 -0700
> Subject: [VOTE] Accept Samza into the Incubator
> To: general@incubator.apache.org
>
> Incubator-
>
> Following the discussion earlier this week, I'm calling a vote to accept
> Samza as a new Incubator project.
>
> The proposal draft is available at:
> https://wiki.apache.org/incubator/SamzaProposal,
> and is also included below. It is identical as what was proposed in the
> discussion except for removing the user list, per Marvin's suggestion.
>
> Vote is open for at least 96h and closes at the earliest on 30 July 13:00
> PDT. I'm letting the vote run an extra day as we're bookending the weekend
> and I want to give everybody a reasonable workweek margin.
>
> [ ] +1 accept Samza in the Incubator
> [ ] +/-0
> [ ] -1 because...
>
> Here's my binding +1
>
> -Jakob  
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: Access to wiki.apache.org/incubator

[Srikanth Sundarrajan]

Thanks much. I have access to edit the page.
RegardsSrikanth Sundarrajan

> From: grobme...@gmail.com
> Date: Tue, 9 Apr 2013 10:50:39 +0200
> Subject: Re: Access to wiki.apache.org/incubator
> To: general@incubator.apache.org
> 
> Should work now, have fun
> 
> On Tue, Apr 9, 2013 at 10:48 AM, Srikanth Sundarrajan
>  wrote:
> > Wiki login: SrikanthSundarrajan
> > ThanksSrikanth Sundarrajan
> >
> >> From: grobme...@gmail.com
> >> Date: Tue, 9 Apr 2013 10:31:25 +0200
> >> Subject: Re: Access to wiki.apache.org/incubator
> >> To: general@incubator.apache.org
> >>
> >> What is your Wiki-Name?
> >>
> >> On Tue, Apr 9, 2013 at 9:27 AM, Srikanth Sundarrajan
> >>  wrote:
> >> > Hi,Need access to wiki.apache.org/incubator to put up the quarterly 
> >> > board report for the Falcon podling. Can someone help?
> >> > RegardsSrikanth Sundarrajan
> >>
> >>
> >>
> >> --
> >> http://www.grobmeier.de
> >> https://www.timeandbill.de
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >
> 
> 
> 
> --
> http://www.grobmeier.de
> https://www.timeandbill.deSh
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
  

RE: Access to wiki.apache.org/incubator

[Srikanth Sundarrajan]

Wiki login: SrikanthSundarrajan
ThanksSrikanth Sundarrajan

> From: grobme...@gmail.com
> Date: Tue, 9 Apr 2013 10:31:25 +0200
> Subject: Re: Access to wiki.apache.org/incubator
> To: general@incubator.apache.org
> 
> What is your Wiki-Name?
> 
> On Tue, Apr 9, 2013 at 9:27 AM, Srikanth Sundarrajan
>  wrote:
> > Hi,Need access to wiki.apache.org/incubator to put up the quarterly 
> > board report for the Falcon podling. Can someone help?
> > RegardsSrikanth Sundarrajan
> 
> 
> 
> -- 
> http://www.grobmeier.de
> https://www.timeandbill.de
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
  

Access to wiki.apache.org/incubator

[Srikanth Sundarrajan]

Hi,Need access to wiki.apache.org/incubator to put up the quarterly board 
report for the Falcon podling. Can someone help?
RegardsSrikanth Sundarrajan   

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

[Srikanth Sundarrajan]

Adding RESULT to the subject.

> Date: Tue, 26 Mar 2013 21:42:37 +0530
> Subject: Re: [VOTE] Accept Falcon into the Apache Incubator (was originally 
> named Ivory)
> From: srikanth.sundarra...@inmobi.com
> To: general@incubator.apache.org
> 
> Hi,
> This vote has PASSED with 8 binding +1s and 5 non-binding +1s.
> 
> Binding +1 VOTES:
> ===
> Arun Murthy
> Chris Douglas
> Alan Gates
> Niall Pemberton
> Devaraj Das
> Leif Hedstrom
> Owen O Malley
> Alan Cabrera
> 
> Non-binding +1 VOTES
> ==
> Sharad Agarwal
> Vinod Kumar Vavilapalli
> Shwetha GS
> Idris Ali
> Samarth Gupta
> 
> Thanks to all who voted and participated in the discussions.
> 
> Srikanth Sundarrajan
> 
> On Thu, Mar 21, 2013 at 10:24 AM, Srikanth Sundarrajan <
> srikanth.sundarra...@inmobi.com> wrote:
> 
> > Hi,
> >
> > Thanks for participating in the proposal discussion on Falcon (formerly 
> > Ivory). I'd like to call a VOTE for acceptance of Apache
> > Falcon into the Incubator. I'll let the vote run till (Tue 3/26 6pm IST).
> >
> > [ ]  +1 Accept Apache Falcon into the Incubator
> > [ ]  +0 Don't care.
> > [ ]  -1 Don't accept Apache Falcon into the Incubator because...
> >
> > Full proposal is pasted at the bottom of this email, and the corresponding 
> > wiki is http://wiki.apache.org/incubator/FalconProposal.
> >
> >
> > Only VOTEs from Incubator PMC members are binding, but all are welcome to 
> > express their thoughts.
> >
> > Thanks,
> > Srikanth Sundarrajan
> > = Falcon Proposal =
> >
> > == Abstract ==
> > Falcon is a data processing and management solution for Hadoop designed for 
> > data motion, coordination of data pipelines, lifecycle management, and data 
> > discovery. Falcon enables end consumers to quickly onboard their data and 
> > its associated processing and management tasks on Hadoop clusters.
> >
> > == Proposal ==
> > Falcon will enable easy data management via declarative mechanism for 
> > Hadoop. Users of Falcon platform simply define infrastructure endpoints, 
> > data sets and processing rules declaratively. These declarative 
> > configurations are expressed in such a way that the dependencies between 
> > these configured entities are explicitly described. This information about 
> > inter-dependencies between various entities allows Falcon to orchestrate 
> > and manage various data management functions.
> >
> > The key use cases that Falcon addresses are:
> >  * Data Motion
> >  * Process orchestration and scheduling
> >  * Policy-based Lifecycle Management
> >  * Data Discovery
> >  * Operability/Usability
> >
> > With these features it is possible for users to onboard their data sets 
> > with a comprehensive and holistic understanding of how, when and where 
> > their data is managed across its lifecycle. Complex functions such as 
> > retrying failures, identifying possible SLA breaches or automated handling 
> > of input data changes are now simple directives. All the administrative 
> > functions and user level functions are available via RESTful APIs. CLI is 
> > simply a wrapper over the RESTful APIs.
> >
> > == Background ==
> > Hadoop and its ecosystem of products have made storing and processing 
> > massive amounts of data commonplace. This has enabled numerous 
> > organizations to gain valuable insights that they never could have achieved 
> > in the past. While it is easy to leverage Hadoop for crunching large 
> > volumes of data, organizing data, managing life cycle of data and 
> > processing data is fairly involved. This is solved adequately well in a 
> > classic data platform involving data warehouses and standard ETL 
> > (extract-transform-load) tools, but remains largely unsolved today. In 
> > addition to data processing complexities, Hadoop presents new sets of 
> > challenges and opportunities relating to management of data.
> >
> > Data Management on Hadoop encompasses data motion, process orchestration, 
> > lifecycle management, data discovery, etc. among other concerns that are 
> > beyond ETL. Falcon is a new data processing and management platform for 
> > Hadoop that solves this problem and creates additional opportunities by 
> > building on existing components within the Hadoop ecosystem (ex. Apache 
> > Oozie, Apache Hadoop DistCp etc.) without reinventing the wheel. Falcon has 
> > been in production at InMobi, going on its second year and has been 
> > managing hundreds of fee

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

[Srikanth Sundarrajan]

Hi,
This vote has PASSED with 8 binding +1s and 5 non-binding +1s.

Binding +1 VOTES:
===
Arun Murthy
Chris Douglas
Alan Gates
Niall Pemberton
Devaraj Das
Leif Hedstrom
Owen O Malley
Alan Cabrera

Non-binding +1 VOTES
==
Sharad Agarwal
Vinod Kumar Vavilapalli
Shwetha GS
Idris Ali
Samarth Gupta

Thanks to all who voted and participated in the discussions.

Srikanth Sundarrajan

On Thu, Mar 21, 2013 at 10:24 AM, Srikanth Sundarrajan <
srikanth.sundarra...@inmobi.com> wrote:

> Hi,
>
> Thanks for participating in the proposal discussion on Falcon (formerly 
> Ivory). I'd like to call a VOTE for acceptance of Apache
> Falcon into the Incubator. I'll let the vote run till (Tue 3/26 6pm IST).
>
> [ ]  +1 Accept Apache Falcon into the Incubator
> [ ]  +0 Don't care.
> [ ]  -1 Don't accept Apache Falcon into the Incubator because...
>
> Full proposal is pasted at the bottom of this email, and the corresponding 
> wiki is http://wiki.apache.org/incubator/FalconProposal.
>
>
> Only VOTEs from Incubator PMC members are binding, but all are welcome to 
> express their thoughts.
>
> Thanks,
> Srikanth Sundarrajan
> = Falcon Proposal =
>
> == Abstract ==
> Falcon is a data processing and management solution for Hadoop designed for 
> data motion, coordination of data pipelines, lifecycle management, and data 
> discovery. Falcon enables end consumers to quickly onboard their data and its 
> associated processing and management tasks on Hadoop clusters.
>
> == Proposal ==
> Falcon will enable easy data management via declarative mechanism for Hadoop. 
> Users of Falcon platform simply define infrastructure endpoints, data sets 
> and processing rules declaratively. These declarative configurations are 
> expressed in such a way that the dependencies between these configured 
> entities are explicitly described. This information about inter-dependencies 
> between various entities allows Falcon to orchestrate and manage various data 
> management functions.
>
> The key use cases that Falcon addresses are:
>  * Data Motion
>  * Process orchestration and scheduling
>  * Policy-based Lifecycle Management
>  * Data Discovery
>  * Operability/Usability
>
> With these features it is possible for users to onboard their data sets with 
> a comprehensive and holistic understanding of how, when and where their data 
> is managed across its lifecycle. Complex functions such as retrying failures, 
> identifying possible SLA breaches or automated handling of input data changes 
> are now simple directives. All the administrative functions and user level 
> functions are available via RESTful APIs. CLI is simply a wrapper over the 
> RESTful APIs.
>
> == Background ==
> Hadoop and its ecosystem of products have made storing and processing massive 
> amounts of data commonplace. This has enabled numerous organizations to gain 
> valuable insights that they never could have achieved in the past. While it 
> is easy to leverage Hadoop for crunching large volumes of data, organizing 
> data, managing life cycle of data and processing data is fairly involved. 
> This is solved adequately well in a classic data platform involving data 
> warehouses and standard ETL (extract-transform-load) tools, but remains 
> largely unsolved today. In addition to data processing complexities, Hadoop 
> presents new sets of challenges and opportunities relating to management of 
> data.
>
> Data Management on Hadoop encompasses data motion, process orchestration, 
> lifecycle management, data discovery, etc. among other concerns that are 
> beyond ETL. Falcon is a new data processing and management platform for 
> Hadoop that solves this problem and creates additional opportunities by 
> building on existing components within the Hadoop ecosystem (ex. Apache 
> Oozie, Apache Hadoop DistCp etc.) without reinventing the wheel. Falcon has 
> been in production at InMobi, going on its second year and has been managing 
> hundreds of feeds and processes.
>
> Falcon is being developed by engineers employed with InMobi and Hortonworks. 
> This platform addition will increase the adoption of Apache Hadoop by driving 
> data management tractable for end users. We are therefore proposing to make 
> Falcon an Apache open source project.
>
> == Rationale ==
> The Falcon project aims to improve the usability of Apache Hadoop. As a 
> result Apache Hadoop will grow its community of users by increasing the 
> places Hadoop can be utilized and the use cases it will solve. By developing 
> Falcon in Apache we hope to gather a diverse community of contributors, 
> helping to ensure that Falcon is deployable for a broad range of scenarios. 
> Members of the Hadoop dev

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

[Srikanth Sundarrajan]

Thanks Bertrand. Since the VOTE is already out, I will leave it so.
However, we will continue to watch out for any serious objections/concern
with the name "Falcon".

Regards
Srikanth Sundarrajan

On Thu, Mar 21, 2013 at 2:46 PM, Bertrand Delacretaz  wrote:

> On Thu, Mar 21, 2013 at 5:54 AM, Srikanth Sundarrajan
>  wrote:
> > ...Thanks for participating in the proposal discussion on Falcon
> > (formerly Ivory). I'd like to call a VOTE for acceptance of Apache
> > Falcon into the Incubator...
>
> I hate to slow down things, but considering that the name change to
> Falcon was only announced 4 hours ago, and there are some concerns
> about it in the discussion thread, I'd say the discussion hasn't
> sufficiently settled down to vote.
>
> We usually allow at least 24 hours for lazy consensus, doing that for
> this name change would be good IMO, especially as the discussion
> thread shows that Falcon is far from being a unique name.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
_
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.

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

[Srikanth Sundarrajan]

Hi Justin,
I am assuming it won't be an issue as Falcon used within the
Adobe/Apache Flex isn't related to Hadoop.

Regards
Srikanth Sundarrajan

On Thu, Mar 21, 2013 at 10:23 AM, Justin Mclean wrote:

> Hi,
>
> JFYI Falcon is already a name used by Adobe and Apache Flex. It's an AS
> compiler and an experimental AS to JS compiler (Falcon JS) - not sure if
> that is an issue or not.
>
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
_
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.

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

[Srikanth Sundarrajan]

Hi,

Thanks for participating in the proposal discussion on Falcon
(formerly Ivory). I'd like to call a VOTE for acceptance of Apache
Falcon into the Incubator. I'll let the vote run till (Tue 3/26 6pm IST).

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

Full proposal is pasted at the bottom of this email, and the
corresponding wiki is http://wiki.apache.org/incubator/FalconProposal.


Only VOTEs from Incubator PMC members are binding, but all are welcome
to express their thoughts.

Thanks,
Srikanth Sundarrajan
= Falcon Proposal =

== Abstract ==
Falcon is a data processing and management solution for Hadoop
designed for data motion, coordination of data pipelines, lifecycle
management, and data discovery. Falcon enables end consumers to
quickly onboard their data and its associated processing and
management tasks on Hadoop clusters.

== Proposal ==
Falcon will enable easy data management via declarative mechanism for
Hadoop. Users of Falcon platform simply define infrastructure
endpoints, data sets and processing rules declaratively. These
declarative configurations are expressed in such a way that the
dependencies between these configured entities are explicitly
described. This information about inter-dependencies between various
entities allows Falcon to orchestrate and manage various data
management functions.

The key use cases that Falcon addresses are:
 * Data Motion
 * Process orchestration and scheduling
 * Policy-based Lifecycle Management
 * Data Discovery
 * Operability/Usability

With these features it is possible for users to onboard their data
sets with a comprehensive and holistic understanding of how, when and
where their data is managed across its lifecycle. Complex functions
such as retrying failures, identifying possible SLA breaches or
automated handling of input data changes are now simple directives.
All the administrative functions and user level functions are
available via RESTful APIs. CLI is simply a wrapper over the RESTful
APIs.

== Background ==
Hadoop and its ecosystem of products have made storing and processing
massive amounts of data commonplace. This has enabled numerous
organizations to gain valuable insights that they never could have
achieved in the past. While it is easy to leverage Hadoop for
crunching large volumes of data, organizing data, managing life cycle
of data and processing data is fairly involved. This is solved
adequately well in a classic data platform involving data warehouses
and standard ETL (extract-transform-load) tools, but remains largely
unsolved today. In addition to data processing complexities, Hadoop
presents new sets of challenges and opportunities relating to
management of data.

Data Management on Hadoop encompasses data motion, process
orchestration, lifecycle management, data discovery, etc. among other
concerns that are beyond ETL. Falcon is a new data processing and
management platform for Hadoop that solves this problem and creates
additional opportunities by building on existing components within the
Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop DistCp etc.) without
reinventing the wheel. Falcon has been in production at InMobi, going
on its second year and has been managing hundreds of feeds and
processes.

Falcon is being developed by engineers employed with InMobi and
Hortonworks. This platform addition will increase the adoption of
Apache Hadoop by driving data management tractable for end users. We
are therefore proposing to make Falcon an Apache open source project.

== Rationale ==
The Falcon project aims to improve the usability of Apache Hadoop. As
a result Apache Hadoop will grow its community of users by increasing
the places Hadoop can be utilized and the use cases it will solve. By
developing Falcon in Apache we hope to gather a diverse community of
contributors, helping to ensure that Falcon is deployable for a broad
range of scenarios. Members of the Hadoop development community will
be able to influence Falcon’s roadmap, and contribute to it. We
believe having Falcon as part of the Apache Hadoop ecosystem will be a
great benefit to all of Hadoop's users.

== Current Status ==
Falcon is widely deployed in production within InMobi and moving on to
its second year. A version with a valuable set of features is
developed by the list of initial committers and is hosted on github.

=== Meritocracy ===
Our intent with this incubator proposal is to start building a diverse
developer community around Falcon following the Apache meritocracy
model. We have wanted to make the project open source and encourage
contributors from multiple organizations from the start. We plan to
provide plenty of support to new developers and to quickly recruit
those who make solid contributions to committer status.

=== Community ===
We are happy to report that the initial team already represents
multiple organizations. We ho

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

[Srikanth Sundarrajan]

esign discussions. Srikanth, Shwetha and Shaik are the
original developers. All the engineers have built two generations of
Data Management on Hadoop, having deep expertise in Hadoop and are
quite familiar with the Hadoop Ecosystem. Samarth Gupta & Rishu
Mehrothra, both from InMobi have build the QA automation for Falcon.

=== Alignment ===
The ASF is a natural host for Falcon given that it is already the home
of Hadoop, Pig, Knox, HCatalog, and other emerging “big data” software
projects. Falcon has been designed to solve the data management
challenges and opportunities of the Hadoop ecosystem family of
products. Falcon fills the gap that Hadoop ecosystem has been lacking
in the areas of data processing and data lifecycle management.

== 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 Falcon getting orphaned. Falcon 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. Srikanth Sundarrajan has been contributing patches to Apache
Hadoop and Apache Oozie, Shwetha GS has been contributing patches to
Apache Oozie.  Seetharam Venkatesh is a committer on Apache Knox.
Sharad Agarwal, Amareshwari SR (also a Apache Hive PMC member) and
Sanjay Radia are PMC members on Apache Hadoop.

=== Homogeneous Developers ===
The current core developers are from diverse set of organizations such
as InMobi and Hortonworks. We expect to quickly establish a developer
community that includes contributors from several corporations post
incubation.

=== Reliance on Salaried Developers ===
Currently, most developers are paid to do work on Falcon but few are
contributing in their spare time. However, once the project has a
community built around it post incubation, we expect to get committers
and developers from outside the current core developers.

=== Relationships with Other Apache Products ===
Falcon 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 Falcon 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 ==http://wiki.apache.org/incubator/FalconProposal

== Initial Source ==
The source is currently in github 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



On Sat, Mar 16, 2013 at 5:52 AM, Joe Schaefer wrote:

> Can we pretty-please do this *before* resources
> are requested, just to save us poor infra saps
> the trouble of renaming everything?
>
>
>
>
>
> >
> > From: Jakob Homan 
> >To: general@incubator.apache.org
> >Sent: Friday, March 15, 2013 8:18 PM
> >Subject: Re: [PROPOSAL] Ivory - Hadoop data management and processing
> platform
> >
> >As part of Incubation a suitable name search will be done to verify the

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

[Srikanth Sundarrajan]

Made few edits to the proposal (
http://wiki.apache.org/incubator/IvoryProposal) as per the feedback
received so far.

Regards
Srikanth Sundarrajan

= Ivory Proposal =

== Abstract ==
Ivory is a data processing and management solution for Hadoop designed
for data motion, coordination of data pipelines, lifecycle management,
and data discovery. Ivory enables end consumers to quickly onboard
their data and its associated processing and management tasks on
Hadoop clusters.

== Proposal ==
Ivory will enable easy data management via declarative mechanism for
Hadoop. Users of Ivory platform simply define infrastructure
endpoints, data sets and processing rules declaratively. These
declarative configurations are expressed in such a way that the
dependencies between these configured entities are explicitly
described. This information about inter-dependencies between various
entities allows Ivory to orchestrate and manage various data
management functions.

The key use cases that Ivory addresses are:
 * Data Motion
 * Process orchestration and scheduling
 * Policy-based Lifecycle Management
 * Data Discovery
 * Operability/Usability

With these features it is possible for users to onboard their data
sets with a comprehensive and holistic understanding of how, when and
where their data is managed across its lifecycle. Complex functions
such as retrying failures, identifying possible SLA breaches or
automated handling of input data changes are now simple directives.
All the administrative functions and user level functions are
available via RESTful APIs. CLI is simply a wrapper over the RESTful
APIs.

== Background ==
Hadoop and its ecosystem of products have made storing and processing
massive amounts of data commonplace. This has enabled numerous
organizations to gain valuable insights that they never could have
achieved in the past. While it is easy to leverage Hadoop for
crunching large volumes of data, organizing data, managing life cycle
of data and processing data is fairly involved. This is solved
adequately well in a classic data platform involving data warehouses
and standard ETL (extract-transform-load) tools, but remains largely
unsolved today. In addition to data processing complexities, Hadoop
presents new sets of challenges and opportunities relating to
management of data.

Data Management on Hadoop encompasses data motion, process
orchestration, lifecycle management, data discovery, etc. among other
concerns that are beyond ETL. Ivory is a new data processing and
management platform for Hadoop that solves this problem and creates
additional opportunities by building on existing components within the
Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop DistCp etc.) without
reinventing the wheel. Ivory has been in production at InMobi, going
on its second year and has been managing hundreds of feeds and
processes.

Ivory is being developed by engineers employed with InMobi and
Hortonworks. This platform addition will increase the adoption of
Apache Hadoop by driving data management tractable for end users. We
are therefore proposing to make Ivory an Apache open source project.

== Rationale ==
The Ivory project aims to improve the usability of Apache Hadoop. As a
result Apache Hadoop will grow its community of users by increasing
the places Hadoop can be utilized and the use cases it will solve. By
developing Ivory in Apache we hope to gather a diverse community of
contributors, helping to ensure that Ivory is deployable for a broad
range of scenarios. Members of the Hadoop development community will
be able to influence Ivory’s roadmap, and contribute to it. We believe
having Ivory as part of the Apache Hadoop ecosystem will be a great
benefit to all of Hadoop's users.

== Current Status ==
Ivory is widely deployed in production within InMobi and moving on to
its second year. A version with a valuable set of features is
developed by the list of initial committers and is hosted on github.

=== Meritocracy ===
Our intent with this incubator proposal is to start building a diverse
developer community around Ivory following the Apache meritocracy
model. We have wanted to make the project open source and encourage
contributors from multiple organizations from the start. We plan to
provide plenty of support to new developers and to quickly recruit
those who make solid contributions to committer status.

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

=== Core Developers ===
Ivory is currently being developed by three engineers from InMobi –
Srikanth Sunderrajan, Shwetha G S, and Shaik Idris, two Hortonworks
employees – Sanjay Radia and Venkatesh Seetharam. In addition, Rohini
Palaniswamy and Thiruvel Thirumoolan, were also involved in the
initial design discussions. Srikanth, Shwetha and Shaik are the
original developers. Al

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

[Srikanth Sundarrajan]

Thanks. Yes, Git seems an attractive option for version control.

Regards
Srikanth Sundarrajan

On Thu, Mar 14, 2013 at 6:26 AM, Vinod Kumar Vavilapalli <
vino...@hortonworks.com> wrote:

>
> +1, this will be a great addition to the Hadoop eco-system!
>
> The proposal looks fine overall. I quickly searched around for the name
> ivory, it looks to be a safe one, but someone needs to do due diligence?
>
> And I think you can chose to have git as the version control if you feel
> like it.
>
> Thanks,
> +Vinod Kumar Vavilapalli
>
> On Mar 13, 2013, at 10:00 AM, Srikanth Sundarrajan wrote:
>
> > = Ivory Proposal =
> >
> > == Abstract ==
> > Ivory is a data processing and management solution for Hadoop designed
> for
> > data motion, coordination of data pipelines, lifecycle management, and
> > data discovery. Ivory enables end consumers to quickly onboard their data
> > and its associated processing and management tasks on Hadoop clusters.
> >
> > == Proposal ==
> > Ivory will enable easy data management via declarative mechanism for
> > Hadoop. Users of Ivory platform simply define infrastructure endpoints,
> > data sets and processing rules declaratively. These configurations
> > are expressed in such a way that the dependencies between
> > these entities are explicitly described. This information about
> > inter-dependencies between various entities allows Ivory to orchestrate
> and
> > manage various data management functions.
> >
> > The key use cases that Ivory addresses are:
> > * Data Motion
> > * Process orchestration and scheduling
> > * Policy-based Lifecycle Management
> > * Data Discovery
> > * Operability/Usability
> >
> > With these features it is possible for users to onboard their data sets
> > with
> > a comprehensive and holistic understanding of how, when and where their
> > data
> > is managed across its lifecycle. Complex functions such as retrying
> > failures,
> > identifying possible SLA breaches or automated handling of input data
> > changes
> > are now simple directives. All the administrative functions and user
> level
> > functions are available via RESTful APIs. CLI is simply a wrapper over
> the
> > RESTful APIs.
> >
> > == Background ==
> > Hadoop and its ecosystem of products have made storing and processing
> > massive
> > amounts of data commonplace. This has enabled numerous organizations to
> > gain
> > valuable insights that they never could have achieved in the past. While
> it
> > is easy to leverage Hadoop for crunching large volumes of data,
> organizing
> > data, managing life cycle of data and processing data is fairly involved.
> > This is solved adequately well in a classic data platform involving data
> > warehouses and standard ETL (extract-transform-load) tools, but remains
> > largely
> > unsolved today. In addition to data processing complexities, Hadoop
> > presents
> > new sets of challenges and opportunities relating to management of data.
> >
> > Data Management on Hadoop encompasses data motion, process orchestration,
> > lifecycle management, data discovery, etc. among other concerns that are
> > beyond
> > ETL. Ivory is a new data processing and management platform for Hadoop
> that
> > solves this problem and creates additional opportunities by building on
> > existing
> > components within the Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop
> > DistCp
> > etc.) without reinventing the wheel. Ivory has been in production at
> > InMobi,
> > going on its second year and has been managing hundreds of feeds and
> > processes.
> >
> > Ivory is being developed by engineers employed with InMobi, Hortonworks
> and
> > Yahoo!. This platform addition will increase the adoption of Apache
> Hadoop
> > by
> > driving data management tractable for end users. We are therefore
> proposing
> > to
> > make Ivory an Apache open source project.
> >
> > == Rationale ==
> > The Ivory project aims to improve the usability of Apache Hadoop. As a
> > result
> > Apache Hadoop will grow its community of users by increasing the places
> > Hadoop
> > can be utilized and the use cases it will solve. By developing Ivory in
> > Apache
> > we hope to gather a diverse community of contributors, helping to ensure
> > that
> > Ivory is deployable for a broad range of scenarios. Members of the Hadoop
> > development community will be able to influence Ivory’s roadmap, and
> > contribute
> > to it. We believe havin

Re: Ivory name

[Srikanth Sundarrajan]

Thanks for bringing this to our attention. Will evaluate possible options.

Regards
Srikanth Sundarrajan

On Fri, Mar 15, 2013 at 6:17 AM, Dmitriy Ryaboy  wrote:

> Folks,  there is already a project in the general "hadoop" space called
> Ivory, and it shows up as the top result for "ivory hadoop" on Google.
>
> http://lintool.github.com/Ivory/
> "A Hadoop toolkit for web-scale information retrieval research"
>
> (Disclaimer: I don't work on this project, but I do work with one of the
> primary authors, Jimmy Lin).
>

-- 
_
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.

[PROPOSAL] Ivory - Hadoop data management and processing platform

[Srikanth Sundarrajan]

= Ivory Proposal =

== Abstract ==
Ivory is a data processing and management solution for Hadoop designed for
data motion, coordination of data pipelines, lifecycle management, and
data discovery. Ivory enables end consumers to quickly onboard their data
and its associated processing and management tasks on Hadoop clusters.

== Proposal ==
Ivory will enable easy data management via declarative mechanism for
Hadoop. Users of Ivory platform simply define infrastructure endpoints,
data sets and processing rules declaratively. These configurations
are expressed in such a way that the dependencies between
these entities are explicitly described. This information about
inter-dependencies between various entities allows Ivory to orchestrate and
manage various data management functions.

The key use cases that Ivory addresses are:
 * Data Motion
 * Process orchestration and scheduling
 * Policy-based Lifecycle Management
 * Data Discovery
 * Operability/Usability

With these features it is possible for users to onboard their data sets
with
a comprehensive and holistic understanding of how, when and where their
data
is managed across its lifecycle. Complex functions such as retrying
failures,
identifying possible SLA breaches or automated handling of input data
changes
are now simple directives. All the administrative functions and user level
functions are available via RESTful APIs. CLI is simply a wrapper over the
RESTful APIs.

== Background ==
Hadoop and its ecosystem of products have made storing and processing
massive
amounts of data commonplace. This has enabled numerous organizations to
gain
valuable insights that they never could have achieved in the past. While it
is easy to leverage Hadoop for crunching large volumes of data, organizing
data, managing life cycle of data and processing data is fairly involved.
This is solved adequately well in a classic data platform involving data
warehouses and standard ETL (extract-transform-load) tools, but remains
largely
unsolved today. In addition to data processing complexities, Hadoop
presents
new sets of challenges and opportunities relating to management of data.

Data Management on Hadoop encompasses data motion, process orchestration,
lifecycle management, data discovery, etc. among other concerns that are
beyond
ETL. Ivory is a new data processing and management platform for Hadoop that
solves this problem and creates additional opportunities by building on
existing
components within the Hadoop ecosystem (ex. Apache Oozie, Apache Hadoop
DistCp
etc.) without reinventing the wheel. Ivory has been in production at
InMobi,
going on its second year and has been managing hundreds of feeds and
processes.

Ivory is being developed by engineers employed with InMobi, Hortonworks and
Yahoo!. This platform addition will increase the adoption of Apache Hadoop
by
driving data management tractable for end users. We are therefore proposing
to
make Ivory an Apache open source project.

== Rationale ==
The Ivory project aims to improve the usability of Apache Hadoop. As a
result
Apache Hadoop will grow its community of users by increasing the places
Hadoop
can be utilized and the use cases it will solve. By developing Ivory in
Apache
we hope to gather a diverse community of contributors, helping to ensure
that
Ivory is deployable for a broad range of scenarios. Members of the Hadoop
development community will be able to influence Ivory’s roadmap, and
contribute
to it. We believe having Ivory as part of the Apache Hadoop ecosystem will
be
a great benefit to all of Hadoop's users.

== Current Status ==
Ivory is widely deployed in production within InMobi and moving on to its
second year. A version with a valuable set of features is developed by the
list of initial committers and is hosted on github.

=== Meritocracy ===
Our intent with this incubator proposal is to start building a diverse
developer
community around Ivory following the Apache meritocracy model. We have
wanted to
make the project open source and encourage contributors from multiple
organizations from the start. We plan to provide plenty of support to new
developers and to quickly recruit those who make solid contributions to
committer status.

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

=== Core Developers ===
Ivory is currently being developed by three engineers from InMobi –
Srikanth Sundarrajan, Shwetha G S, and Shaik Idris, two Hortonworks
employees –
Sanjay Radia and Venkatesh Seetharam. In addition, two Yahoo! employees,
Rohini Palaniswamy and Thiruvel Thirumoolan, are also involved. Srikanth,
Shwetha and Shaik are the original developers. All the engineers have built
two generations of Data Management on Hadoop, having deep expertise in
Hadoop
and are quite familiar with the Hadoop Ecosystem.

=== Alignment ===
The A