Re: [RESULT] Re: [VOTE] Livy to enter Apache Incubator

2017-06-05 Thread Bikas Saha
Hi,

I am sorry I was off email when all of this happened. Would like to add my post 
result +1 to join everyone in supporting this effort!

Thanks!
Bikas


From: Sean Busbey 
Sent: Monday, June 5, 2017 10:34:45 AM
To: general@incubator.apache.org
Subject: [RESULT] Re: [VOTE] Livy to enter Apache Incubator

With 7 binding +1 votes (and 14 non-binding +1 votes), this vote passes.

Thanks for everyone who took the time to vote!

I'll coordinate with the mentors to start the initial paperwork today. (And 
we'd be thrilled for the 4th mentor JB!)

binding:
Larry McCay
Jean-Baptiste Onofré
Luciano Resende
Andrew Purtell
Brock Noland
Raphael Bircher
Hitesh Shah

non-binding:
Sean Busbey
Ismaël Mejía
Marcelo Vanzin
Neelesh Salian
Phillip Rhodes
Kostas Sakellis
Jeff Zhang
Saisai Shao
tim shea
Pierre Smits
Arpit Agarwal
Madhawa Kasun Gunasekara
Bruno Mahé
Felix Cheung

-busbey

On 2017-05-31 08:03 (-0500), "Sean Busbey" wrote:
> Hi folks!
>
> I'm calling a vote to accept "Livy" into the Apache Incubator.
>
> The full proposal is available below, and is also available in the wiki:
>
> https://wiki.apache.org/incubator/LivyProposal
>
> For additional context, please see the discussion thread:
>
> https://s.apache.org/incubator-livy-proposal-thread
>
> Please cast your vote:
>
> [ ]  1, bring Livy into Incubator
> [ ] -1, do not bring Livy into Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding.
>
> I start with my vote:
>  1
>


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



Re: [VOTE] Release Livy 0.4.0-incubating based on Livy 0.4.0 RC2

2017-08-24 Thread Bikas Saha
+1 (binding)


Built from source and ran some local tests manually. Spot checked a few random 
files for license and attribution.


Bikas



From: Marcelo Vanzin 
Sent: Wednesday, August 23, 2017 9:04:46 AM
To: general@incubator.apache.org
Cc: d...@livy.incubator.apache.org
Subject: Re: [VOTE] Release Livy 0.4.0-incubating based on Livy 0.4.0 RC2

Just echoing my +1 from the Livy list.

On Tue, Aug 22, 2017 at 12:33 AM, Jerry Shao  wrote:
> Hello Incubator PMC’ers,
>
> The Apache Livy community has decided to release Apache Livy
> 0.4.0-incubating based on 0.4.0-incubating Release Candidate 2. We now
> kindly request the Incubator PMC members to review and vote on this incubator
> release.
>
> Livy is web service that exposes a REST interface for managing long running
> Apache Spark contexts in your cluster. With Livy, new applications can be
> built on top of Apache Spark that require fine grained interaction with
> many Spark contexts.
>
> Artifacts are available at
> https://dist.apache.org/repos/dist/dev/incubator/livy/, public keys are
> available at https://dist.apache.org/repos/dist/dev/incubator/livy/KEYS.
>
> livy-0.4.0-incubating-src.zip <
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.4.0-incubating/livy-0.4.0-incubating-src-RC2.zip
>> is a source release. Along with it, for convenience, please find the
> binary release as livy-0.4.0-incubating-bin-RC2.zip <
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.4.0-incubating/livy-0.4.0-incubating-bin-RC2.zip
>>.
>
>
> Git tag:
> *https://github.com/apache/incubator-livy/releases/tag/v0.4.0-incubating-rc2
> *
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> Members please be sure to indicate "(Binding)" with your vote which will
> help in tallying the vote(s).
>
> * Here is my +1 (non-binding) *
>
> Cheers,
> Jerry



--
Marcelo


Add to wiki contributor group

2017-09-06 Thread Bikas Saha
Hi,

Please add account - BikasSaha - to the incubator wiki contributor group.

Thanks
Bikas



RE: [VOTE] Release Apache Tez-0.2.0-incubating RC0

2013-12-04 Thread Bikas Saha
+1

-Original Message-
From: Jason Lowe [mailto:jl...@yahoo-inc.com]
Sent: Monday, December 02, 2013 12:56 PM
To: d...@tez.incubator.apache.org; general@incubator.apache.org
Subject: Re: [VOTE] Release Apache Tez-0.2.0-incubating RC0

+1

- verified digests and signatures
- built from source
- ran a few example jobs on a single-node cluster

Jason

On 11/25/2013 06:33 PM, Hitesh Shah wrote:
> Hello folks,
>
> I have created a tez-0.2.0-incubating release candidate (rc0). This is
the first release for Tez. Therefore, please do not be gentle.
>
> GIT source tag:
> https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator
> -tez.git;a=log;h=refs/tags/release-0.2.0-rc0
> Staging site:
> http://people.apache.org/~hitesh/tez-release-rc/tez-0.2.0-incubating-r
> c0/ Nexus Staging URL:
> https://repository.apache.org/content/repositories/orgapachetez-002/
>
> PGP release keys:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA9510905F0B000F0
> KEYS file also available at
> https://dist.apache.org/repos/dist/release/incubator/tez/KEYS
>
> One can look into the issues fixed in this release at:
> https://issues.apache.org/jira/browse/TEZ/fixforversion/12324349
>
> Vote will be open for 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> thanks
> -- Hitesh

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

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



RE: [VOTE] Release Apache Tez-0.3.0-incubating RC0

2014-02-24 Thread Bikas Saha
+1.



-Original Message-
From: Hitesh Shah [mailto:hit...@apache.org]
Sent: Sunday, February 23, 2014 11:31 AM
To: d...@tez.incubator.apache.org; general@incubator.apache.org
Subject: [VOTE] Release Apache Tez-0.3.0-incubating RC0

Hello folks,

I have created a tez-0.3.0-incubating release candidate (rc0). This is the
second release for Tez.

GIT source tag:
https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez
.git;a=log;h=refs/tags/release-0.3.0-incubating-rc0
Staging site:
https://dist.apache.org/repos/dist/dev/incubator/tez/0.3.0-incubating-rc0/
Nexus Staging URL:
https://repository.apache.org/content/repositories/orgapachetez-1002

PGP release keys:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA9510905F0B000F0
KEYS file also available at
https://dist.apache.org/repos/dist/release/incubator/tez/KEYS

One can look into the issues fixed in this release at:
https://issues.apache.org/jira/browse/TEZ/fixforversion/12325655 or look
at the CHANGES.txt in the release tarball.

Vote will be open for at least 72 hours ( until the required number of
IPMC votes are obtained ).

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

For folks not familiar with vetting a release, please refer to
http://incubator.apache.org/guides/releasemanagement.html#check-list

thanks
-- Hitesh

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

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



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

2014-04-05 Thread Bikas Saha
+1

Built from source. Ran tests.

-Original Message-
From: Tsuyoshi OZAWA [mailto:ozawa.tsuyo...@gmail.com]
Sent: Friday, April 04, 2014 1:51 AM
To: d...@tez.incubator.apache.org
Cc: general@incubator.apache.org
Subject: Re: [VOTE] Release Apache Tez-0.4.0-incubating RC1

+1 (non-binding)

Built form source and ran tests.


On Wed, Apr 2, 2014 at 6:42 AM, Siddharth Seth  wrote:
> I have created a tez-0.4.0-incubating release candidate (rc1).
>
> This includes license and notice files missing from rc0 release
> artifacts (the javadoc artifact has these files under
> resources/META-INF instead of directly under META-INF)
>
> GIT source tag:
> https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator
> -tez.git;a=log;h=refs/tags/release-0.4.0-incubating-rc1
> (git commit 145c730c8d1cea863185b2a3354b19f2ab21addd)
>
> Staging site:
> https://dist.apache.org/repos/dist/dev/incubator/tez/0.4.0-incubating-
> rc1
> (svn revision 4929)
>
> Nexus Staging URL:
> *https://repository.apache.org/content/repositories/orgapachetez-1005/
>  >*
>
> PGP release keys:
> http://pgp.mit.edu/pks/lookup?op=get&search=0x477E02D33DD51430
> KEYS file available at
> https://dist.apache.org/repos/dist/release/incubator/tez/KEYS
>
> List of issues fixed in the release:
> https://issues.apache.org/jira/browse/TEZ/fixforversion/12326283/
> Also available in CHANGES.txt within the release tarball.
>
> Vote will be open for at least 72 hours ( until the required number of
> IPMC votes are obtained ).
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> For folks not familiar with vetting a release, please refer to
> http://incubator.apache.org/guides/releasemanagement.html#check-list
>
> Thanks
> - Sid



--
- Tsuyoshi

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

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



RE: Tez graduation [Was: Request for mentor assessment]

2014-06-23 Thread Bikas Saha
Community building is an organic process that grows on its own accord.
Members can only make efforts to evangelize the project and support the
initial users of the project by answering questions and helping them out.
We have tried do our part as the initial members of the community and we
think that we have been reasonably successful towards our goals - given
the complex technical nature of the project itself.

The beginnings of community building come from being open. When the
project was still new it was important that people understand the
motivations for the project and the core technical architecture of the
code that seeded the project. In order to do that we published a series of
deep technical blogs that describe the project and its technical
architecture. http://goo.gl/sQ1QZb. There was considerable favorable
reception about the quality of this series and brought a lot of mindshare
to the project.

Next we have spoken at a number of forums about Apache Tez. Here are the
presentations that come to mind.
1) Hadoop Summit San Jose 2013
2) Hadoop Summit Amsterdam 2014
3) Beijing Big Data Technology Conference 2013
4) Bay Area Hadoop User Group 2014
5) Los Angeles Hadoop User Group 2013
6) Big Data Camp LA 2014
7) Seattle Scalability Meetup 2014
8) New York Hadoop User Group 2014
9) Hadoop Summit San Jose 2014
10) QConf San Francisco Conference 2013
11) Discovery 2020 Workshop at LBNL Berkeley
12) Big Data Gurus Meetup 2014
13) Silicon Valley Hands On Programming Meetup 2014
14) Presentation at MapR HQ on Apache Tez

The community outreach events have been spread over time and geography and
should represent substantial effort towards community building. Here is an
example of the presentations we have made. http://goo.gl/BL67o7. More than
10 out of 48 slides are specifically there to motivate people to try out
and dig deeper with Apache Tez because the main aim of these presentations
is community outreach.

The email lists are a bit of a chicken and egg situation. Initial
questions are around simpler things like installation etc. But as people
start getting deeper they start asking more technical questions and then
start contributing to the project itself. Off-late there have been much
more interesting questions around scheduling and control plane events and
it reflects increasing usage and interest in the project.

We should also look at the response times for emails on those lists.
Almost all emails get answered within 1 day and most within 1 hour. We are
a small community with strong motivation to increase our community of
users and developers by addressing their roadblocks as soon as we can.

Aside from dev mailing lists, the other measure of interaction is on the
Apache Tez jira itself. Out of the 1200 jiras opened under the Apache Tez
project about 200 have been created by non-committer community members.

Another take on community building is how other community projects are
interacting with Apache Tez. We have strong adoption from Apache Pig and
Apache Hive. The Apache Pig effort has been an excellent example of cross
company collaboration done under the Apache umbrella with members from
Yahoo, LinkedIn, Netflix and Hortonworks. Apache Flink is a new incubator
project that is experimenting with integrating with Tez and shows a
positive outcome of the community outreach efforts. Adoption creates the
greatest support for project sustainability because the adopters have
interest in making sure that the project stays alive and continues to meet
their needs.
As an example of the interest shown by Apache Hive and Apache Pig in Tez
there have been multiple public talks by members of those communities
about how they have integrated with success with Apache Tez.
1) Bay Area Hadoop User Group 2014 (both Hive and Pig)
2) Hadoop Summit San Jose 2014 (both Hive and Pig)

Over the last few months we have been receiving active contributions in
quality and volume that enabled us to add a number of new committers.
Since their contributions were fairly obvious because of their
interactions with existing committers on the jiras, there wasn't much
discussion on the vote thread itself.

Finally, our 0.5 release is targeting community adoption and user adoption
by considerably simplifying the API for the project because we have
received feedback of that area being the specially challenging for
newcomers.

I hope these examples will help allay any doubts about the efforts and
success at building out the community around Apache Tez.

Thanks
Bikas


-Original Message-
From: Mattmann, Chris A (3980) [mailto:chris.a.mattm...@jpl.nasa.gov]
Sent: Monday, June 23, 2014 1:46 PM
To: general@incubator.apache.org
Cc: d...@tez.incubator.apache.org
Subject: Re: Tez graduation [Was: Request for mentor assessment]

Thanks Ted, appreciate it and we will make sure to address your comments
and sincerely appreciate the time you took to type your replies and do
your research. It will no doubt help the community and thank you again

RE: Tez graduation [Was: Request for mentor assessment]

2014-06-23 Thread Bikas Saha
I think we are on the same page here about working hard to build the
community. We need to work hard to make the community grow. I was merely
saying that how that effort converts into adoption is not something that can
be predicted. I hope that clarifies. Always looking for guidance to make the
most out of our efforts at community building and ways we can improve.

I hope the information provided in this thread helps display that we are
working hard and committed to building a vibrant Apache Tez community.

Thanks
Bikas

-Original Message-
From: Ted Dunning [mailto:ted.dunn...@gmail.com]
Sent: Monday, June 23, 2014 2:41 PM
To: general@incubator.apache.org
Cc: d...@tez.incubator.apache.org
Subject: Re: Tez graduation [Was: Request for mentor assessment]

On Mon, Jun 23, 2014 at 2:23 PM, Bikas Saha  wrote:

> Community building is an organic process that grows on its own accord.
>

Really, I was going to run away for a bit, but my feeling is that this
statement is amazingly naive about how communities are built.

Community doesn't just happen.  Community doesn't just grow of its own
accord.  Community grows when people make serious, explicit actions to help
it grow, to bring in newcomers, to publish plans in many places *before*
code is written.

Building community is hard work that you have to intend to do.  If you don't
do the work, it won't just happen any more than code writes itself.

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

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



RE: [VOTE] Release Apache Tez-0.4.1-incubating RC0

2014-06-27 Thread Bikas Saha
+1. This will help users doing personal builds of Hive 0.13 and Tez. There
has been some ask about that on the mailing lists.

Bikas

-Original Message-
From: Siddharth Seth [mailto:ss...@apache.org]
Sent: Thursday, June 26, 2014 1:53 PM
To: d...@tez.incubator.apache.org; general@incubator.apache.org
Subject: [VOTE] Release Apache Tez-0.4.1-incubating RC0

I have created a tez-0.4.1-incubating release candidate (rc0).
This is bug fix release created from branch-0.4, and does not change APIs
from the 0.4.0 release.

GIT source tag:
https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez.git;a=log;h=refs/tags/release-0.4.1-incubating-rc0

Staging site:
https://dist.apache.org/repos/dist/dev/incubator/tez/tez-0.4.1-incubating-src-rc0/

Nexus Staging URL:
https://repository.apache.org/content/repositories/orgapachetez-1006/

PGP release keys:
http://pgp.mit.edu/pks/lookup?op=get&search=0x477E02D33DD51430
KEYS file available at
https://dist.apache.org/repos/dist/release/incubator/tez/KEYS

List of issues fixed in the release:
*https://issues.apache.org/jira/browse/TEZ/fixforversion/12327143/
*
Also available in CHANGES.txt within the release tarball.

Vote will be open for at least 72 hours ( until the required number of IPMC
votes are obtained).

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

For folks not familiar with vetting a release, please refer to
http://incubator.apache.org/guides/releasemanagement.html#check-list

Thanks
- Sid

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

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



Re: [DISCUSS] Retire Livy podling

2022-10-14 Thread Bikas Saha
+1 to JB's comments. The project is open but the original set of folks who 
actually worked on the code seem to have moved on. So there is a bit of a 
struggle to keep the project code moving.

The mailing lists are also quiet, perhaps because the project is mature. So 
Livy could be in a unique situation where it is mature/stable while its still 
incubating. There are many users but not much development. Though it also 
appears from this thread that different users have created forks for feature 
development internally.

IIRC in the past someone from another company, that was actively using Livy, 
had also raised interest because of concerns about the project "getting 
shelved". But at that time nothing concrete happened. Perhaps getting these 
forks committed back to open would kick start the project.

There is the issue of the lack of active committers to actually review/commit 
the code. Any thoughts on solutions for that?

Bikas


From: larry mccay 
Sent: Friday, October 14, 2022 6:51 AM
To: general@incubator.apache.org 
Subject: Re: [DISCUSS] Retire Livy podling

I have a simplified proposal nearly ready to send. Since there weren't any
requirements for it provided here it is just declaring the intent and new
members from this thread and my employer.

If there is anything else you'd like to see in it just let me know.

On Fri, Oct 14, 2022, 9:46 AM Jean-Baptiste Onofré  wrote:

> There's no need to reestablished the podling as it's still running ;)
>
> I think we can just update the original proposal, reshape the PPMC and
> move forward.
>
> Thoughts ?
>
> Regards
> JB
>
> On Fri, Oct 14, 2022 at 9:55 AM Brahma Reddy Battula 
> wrote:
> >
> > Hi Justin,
> >
> > Any chance to re-establish podding or add some members to existing
> > community so that it can be active ,as we can see so many people are
> > interested to contribute to Livy podling?
> >
> >
> >
> > On Thu, 13 Oct 2022 at 10:02 PM, Justin Mclean  >
> > wrote:
> >
> > > Hi,
> > >
> > > Just a note, poddlings do not go to the attic, only top level projects
> do.
> > > Most often a podling in this state will continue to live on GitHub as
> long
> > > as there is a community to support it.
> > >
> > > Kind Regards,
> > > Justin
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: [VOTE] Release Apache Livy 0.7.0 (incubating) based on RC4

2020-02-01 Thread Bikas Saha
+1 based on the projects own voting thread in December.

Sorry missed this as its been busy at work after the holidays. Just catching up 
on ASF threads. Good catch on the potential icon issue. Maybe let us try to 
work out a solution for that for the next release. If the verbiage cannot be 
resolved then perhaps we could consider changing the dependency.

Thanks
Bikas


From: Justin Mclean 
Sent: Tuesday, January 21, 2020 2:59 PM
To: general@incubator.apache.org ; 
junping...@apache.org 
Subject: Re: [VOTE] Release Apache Livy 0.7.0 (incubating) based on RC4

Hi,

+1 binding

I checked:
- incubating in name
- signatures and hashes are fine
- DISCLAIMER exists
- LICENSE is missing a license
- NOTICE incorrect states "2018 and onwards” please fix
- No unexpected binary files
- All source files have ASF headers
- unable to compile from source bu assume it my setup (on OSX)

LICENSE is missing license for this font [1][2]

Thanks,
Justin

1.  ./docs/assets/themes/apache/bootstrap/fonts/glyphicons-halflings-regular.*
2. 
./server/src/main/resources/org/apache/livy/server/ui/static/fonts/glyphicons-halflings-regular.*




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