Re: Possible missing mentor(s)

[Luciano Resende]

On Sat, Oct 20, 2018 at 4:50 PM Justin Mclean  wrote:
>
> Hi,
>
> We have discussed missing mentors on the incubator general list, identified 
> those who may be missing and over a couple of months tried to contact your 
> mentor in several ways but have got no reply so they have been removed from 
> the roster.
>
> If this is error, and your mentor is actually active, please contact me and 
> I'll add them back to the roster.
>
> The IPMC will also do what it can to find extra mentors for those podling 
> that need them.
>
> Thanks,
> Justin
> (V.P. Incubator)

Just FYI, I am around...

Also, note that sometimes these messages get lost on the Gmail
threading feature when it's copied into multiple podlings with the
same subject line.


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE]: Support Livy client for script submitting Solution

[Luciano Resende]

Please see:
http://incubator.apache.org/guides/ip_clearance.html

You should at a minimum file a CLA, you might also need an SGA which
is explained in "Establishing Provenance" section of the document.

On Mon, Jun 24, 2019 at 2:40 AM Jassy Wang  wrote:
>
> Hello, would you please tell me what should I do to donate this project to
> Apache/Livy?
>
> Luciano Resende  于2019年6月14日周五 下午12:34写道：
>
> > Then, as this was not developed in the open, you might need to follow an
> > extra process to donate the code to Apache/Livy. I will take a look at the
> > process and report back in couple days.
> >
> > On Fri, Jun 14, 2019 at 03:36 Jassy Wang  wrote:
> >
> > > yes, and we have already used in our production environment.
> > >
> > > Luciano Resende  于2019年6月14日周五 上午5:28写道：
> > >
> > > > Is the code already implemented ?
> > > >
> > > > On Thu, Jun 13, 2019 at 00:31 Jassy Wang 
> > > wrote:
> > > >
> > > > > Yes, we will provide code after voting completed.
> > > > >
> > > > > Marco Gaido  于2019年6月12日周三 下午7:54写道：
> > > > >
> > > > > > Yes, nothing is going to be merged to trunk. I think this is just
> > the
> > > > > vote
> > > > > > on the design doc.
> > > > > >
> > > > > > Il giorno mer 12 giu 2019 alle ore 13:38 Kevin Risden <
> > > > > kris...@apache.org>
> > > > > > ha scritto:
> > > > > >
> > > > > > > Maybe I missed something, but is LIVY-596 just the design doc?
> > Not
> > > > sure
> > > > > > > what is getting merged into trunk? I checked open PR/issues on
> > the
> > > > > Github
> > > > > > > project and LIVY-596 and only found the design doc linked.
> > > > > > >
> > > > > > > I like the idea of a Livy client and how it could "replace" spark
> > > > > client
> > > > > > in
> > > > > > > a lot of cases. I had a similar idea about 2 years ago but never
> > > > > pursued
> > > > > > > it.
> > > > > > >
> > > > > > > Kevin Risden
> > > > > > >
> > > > > > >
> > > > > > > On Wed, Jun 12, 2019 at 6:10 AM Marco Gaido <
> > > marcogaid...@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Thanks for starting the vote. The feature looks very
> > interesting
> > > as
> > > > > it
> > > > > > > may
> > > > > > > > spreard livy's adoption IMHO, so I am +1.
> > > > > > > > Thanks.
> > > > > > > >
> > > > > > > > Il giorno mer 12 giu 2019 alle ore 10:46 Yang Jiandan <
> > > > > > > > succeedin2...@gmail.com> ha scritto:
> > > > > > > >
> > > > > > > > > Thanks Jassy Wang for starting the discussion.
> > > > > > > > > This feature is very useful.
> > > > > > > > > I'm +1 for this feature.
> > > > > > > > >
> > > > > > > > > Jassy Wang  于2019年6月12日周三 下午4:31写道：
> > > > > > > > >
> > > > > > > > > > Hi All,
> > > > > > > > > >
> > > > > > > > > >Given the positive response to the design doc [1], here
> > is
> > > > the
> > > > > > > > > > formal vote thread to merge LIVY-596 in to trunk.
> > > > > > > > > >
> > > > > > > > > >Summary of code changes:
> > > > > > > > > >1. Add support of submitting by script for Livy server
> > > > > > > > > >2. Code changes for this branch are done in livy-client
> > > > > project,
> > > > > > > and
> > > > > > > > > > there is no impact to current livy
> > > > > > > > > >3. Add Parameter Support for specify session
> > > > > > > > > >
> > > > > > > > > >We are willing to accept more new ideas and communicate
> > > > about
> > > > > > this
> > > > > > > > > > feature, and this is our design doc:
> > > > > > > > > >
> > > > > > > > > >The vote will run for 7 days(including 5 weekdays),
> > ending
> > > > Sat
> > > > > > > June
> > > > > > > > > > 19th. I will start this
> > > > > > > > > > vote with my +1.
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > Zhefeng Wang
> > > > > > > > > >
> > > > > > > > > > Reference
> > > > > > > > > > [1]
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > https://docs.google.com/document/d/1Sc-EHLBhLhmqVn7kQqUexxZ1vwEomb8lW-Vvlpj2Gmc/edit?usp=sharing
> > > > > > > > > > [2] https://issues.apache.org/jira/browse/LIVY-596
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > --
> > > > Sent from my Mobile device
> > > >
> > >
> > --
> > Sent from my Mobile device
> >



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE]: Support Livy client for script submitting Solution

[Luciano Resende]

Then, as this was not developed in the open, you might need to follow an
extra process to donate the code to Apache/Livy. I will take a look at the
process and report back in couple days.

On Fri, Jun 14, 2019 at 03:36 Jassy Wang  wrote:

> yes, and we have already used in our production environment.
>
> Luciano Resende  于2019年6月14日周五 上午5:28写道：
>
> > Is the code already implemented ?
> >
> > On Thu, Jun 13, 2019 at 00:31 Jassy Wang 
> wrote:
> >
> > > Yes, we will provide code after voting completed.
> > >
> > > Marco Gaido  于2019年6月12日周三 下午7:54写道：
> > >
> > > > Yes, nothing is going to be merged to trunk. I think this is just the
> > > vote
> > > > on the design doc.
> > > >
> > > > Il giorno mer 12 giu 2019 alle ore 13:38 Kevin Risden <
> > > kris...@apache.org>
> > > > ha scritto:
> > > >
> > > > > Maybe I missed something, but is LIVY-596 just the design doc? Not
> > sure
> > > > > what is getting merged into trunk? I checked open PR/issues on the
> > > Github
> > > > > project and LIVY-596 and only found the design doc linked.
> > > > >
> > > > > I like the idea of a Livy client and how it could "replace" spark
> > > client
> > > > in
> > > > > a lot of cases. I had a similar idea about 2 years ago but never
> > > pursued
> > > > > it.
> > > > >
> > > > > Kevin Risden
> > > > >
> > > > >
> > > > > On Wed, Jun 12, 2019 at 6:10 AM Marco Gaido <
> marcogaid...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Thanks for starting the vote. The feature looks very interesting
> as
> > > it
> > > > > may
> > > > > > spreard livy's adoption IMHO, so I am +1.
> > > > > > Thanks.
> > > > > >
> > > > > > Il giorno mer 12 giu 2019 alle ore 10:46 Yang Jiandan <
> > > > > > succeedin2...@gmail.com> ha scritto:
> > > > > >
> > > > > > > Thanks Jassy Wang for starting the discussion.
> > > > > > > This feature is very useful.
> > > > > > > I'm +1 for this feature.
> > > > > > >
> > > > > > > Jassy Wang  于2019年6月12日周三 下午4:31写道：
> > > > > > >
> > > > > > > > Hi All,
> > > > > > > >
> > > > > > > >Given the positive response to the design doc [1], here is
> > the
> > > > > > > > formal vote thread to merge LIVY-596 in to trunk.
> > > > > > > >
> > > > > > > >Summary of code changes:
> > > > > > > >1. Add support of submitting by script for Livy server
> > > > > > > >2. Code changes for this branch are done in livy-client
> > > project,
> > > > > and
> > > > > > > > there is no impact to current livy
> > > > > > > >3. Add Parameter Support for specify session
> > > > > > > >
> > > > > > > >We are willing to accept more new ideas and communicate
> > about
> > > > this
> > > > > > > > feature, and this is our design doc:
> > > > > > > >
> > > > > > > >The vote will run for 7 days(including 5 weekdays), ending
> > Sat
> > > > > June
> > > > > > > > 19th. I will start this
> > > > > > > > vote with my +1.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Zhefeng Wang
> > > > > > > >
> > > > > > > > Reference
> > > > > > > > [1]
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://docs.google.com/document/d/1Sc-EHLBhLhmqVn7kQqUexxZ1vwEomb8lW-Vvlpj2Gmc/edit?usp=sharing
> > > > > > > > [2] https://issues.apache.org/jira/browse/LIVY-596
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > --
> > Sent from my Mobile device
> >
>
-- 
Sent from my Mobile device

Re: [VOTE]: Support Livy client for script submitting Solution

[Luciano Resende]

Is the code already implemented ?

On Thu, Jun 13, 2019 at 00:31 Jassy Wang  wrote:

> Yes, we will provide code after voting completed.
>
> Marco Gaido  于2019年6月12日周三 下午7:54写道：
>
> > Yes, nothing is going to be merged to trunk. I think this is just the
> vote
> > on the design doc.
> >
> > Il giorno mer 12 giu 2019 alle ore 13:38 Kevin Risden <
> kris...@apache.org>
> > ha scritto:
> >
> > > Maybe I missed something, but is LIVY-596 just the design doc? Not sure
> > > what is getting merged into trunk? I checked open PR/issues on the
> Github
> > > project and LIVY-596 and only found the design doc linked.
> > >
> > > I like the idea of a Livy client and how it could "replace" spark
> client
> > in
> > > a lot of cases. I had a similar idea about 2 years ago but never
> pursued
> > > it.
> > >
> > > Kevin Risden
> > >
> > >
> > > On Wed, Jun 12, 2019 at 6:10 AM Marco Gaido 
> > > wrote:
> > >
> > > > Thanks for starting the vote. The feature looks very interesting as
> it
> > > may
> > > > spreard livy's adoption IMHO, so I am +1.
> > > > Thanks.
> > > >
> > > > Il giorno mer 12 giu 2019 alle ore 10:46 Yang Jiandan <
> > > > succeedin2...@gmail.com> ha scritto:
> > > >
> > > > > Thanks Jassy Wang for starting the discussion.
> > > > > This feature is very useful.
> > > > > I'm +1 for this feature.
> > > > >
> > > > > Jassy Wang  于2019年6月12日周三 下午4:31写道：
> > > > >
> > > > > > Hi All,
> > > > > >
> > > > > >Given the positive response to the design doc [1], here is the
> > > > > > formal vote thread to merge LIVY-596 in to trunk.
> > > > > >
> > > > > >Summary of code changes:
> > > > > >1. Add support of submitting by script for Livy server
> > > > > >2. Code changes for this branch are done in livy-client
> project,
> > > and
> > > > > > there is no impact to current livy
> > > > > >3. Add Parameter Support for specify session
> > > > > >
> > > > > >We are willing to accept more new ideas and communicate about
> > this
> > > > > > feature, and this is our design doc:
> > > > > >
> > > > > >The vote will run for 7 days(including 5 weekdays), ending Sat
> > > June
> > > > > > 19th. I will start this
> > > > > > vote with my +1.
> > > > > >
> > > > > > Regards,
> > > > > > Zhefeng Wang
> > > > > >
> > > > > > Reference
> > > > > > [1]
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://docs.google.com/document/d/1Sc-EHLBhLhmqVn7kQqUexxZ1vwEomb8lW-Vvlpj2Gmc/edit?usp=sharing
> > > > > > [2] https://issues.apache.org/jira/browse/LIVY-596
> > > > > >
> > > > >
> > > >
> > >
> >
>
-- 
Sent from my Mobile device

Re: Podling Report Reminder - April 2019

[Luciano Resende]

On Sun, Apr 7, 2019 at 3:48 PM Justin Mclean  wrote:
>
> Hi,
>
> Thanks for submitting your report here [1]. However, it's very light on 
> detail and several questions have not been answered, if you could fix that 
> hat would be appreciated. If you're not sure what to put into the report 
> please ask your mentors.
>
> Thanks,
> Justin
>
> 1. https://wiki.apache.org/incubator/April2019

Thanks for checking Justin, I believe that more details have been
added to the report and I have just signed it off.

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Release Livy 0.6.0 based on RC1

[Luciano Resende]

On Mon, Mar 18, 2019 at 4:03 PM Marcelo Vanzin
 wrote:
>
> On Mon, Mar 18, 2019 at 2:23 PM Luciano Resende  wrote:
> > Also, there are lots of version mismatching between the included jars
> > and the third-party license file
>
> Could you be a little more explicit about this one? I don't even see a
> 3rd party license file. What exactly is the expectation here?
>
> --
> Marcelo

When you extract the binary distro, there is a THIRD-PARTY file which
lists the external dependencies and their licenses.

I tried to validate some and noticed a few mismatches on the version:

jars/jackson-jaxrs-1.9.13.jar
* JAX-RS provider for JSON content type
(org.codehaus.jackson:jackson-jaxrs:1.8.3 -
http://jackson.codehaus.org)

Also, I just noticed the following (L)GPL dependencies. Are these new
? Were it introduced since the previous release? Or are these
dual-licensed?


  GNU General Public Library:

* Streaming API for XML (javax.xml.stream:stax-api:1.0-2 - no url defined)

  GNU Lesser General Public License (LGPL), Version 2.1:

* JAX-RS provider for JSON content type
(org.codehaus.jackson:jackson-jaxrs:1.8.3 -
http://jackson.codehaus.org)
* Xml Compatibility extensions for Jackson
(org.codehaus.jackson:jackson-xc:1.8.3 - http://jackson.codehaus.org)

  GPL:

* JTransforms (com.github.rwl:jtransforms:2.4.0 -
http://sourceforge.net/projects/jtransforms/)

  GPL2 w/ CPE:

* JAXB API bundle for GlassFish V3 (javax.xml.bind:jaxb-api:2.2.2
- https://jaxb.dev.java.net/)
* JAXB RI (com.sun.xml.bind:jaxb-impl:2.2.3-1 - http://jaxb.java.net/)
* javax.ws.rs-api (javax.ws.rs:javax.ws.rs-api:2.0.1 -
http://jax-rs-spec.java.net)
* jersey-client (com.sun.jersey:jersey-client:1.9 -
https://jersey.java.net/jersey-client/)
* jersey-core (com.sun.jersey:jersey-core:1.9 -
https://jersey.java.net/jersey-core/)
* jersey-guice (com.sun.jersey.contribs:jersey-guice:1.9 -
https://jersey.java.net/jersey-contribs/jersey-guice/)
* jersey-json (com.sun.jersey:jersey-json:1.9 -
https://jersey.java.net/jersey-json/)
* jersey-server (com.sun.jersey:jersey-server:1.9 -
https://jersey.java.net/jersey-server/)

  GPLv2+CE:

* JavaMail API (compat) (javax.mail:mail:1.4.7 -
http://kenai.com/projects/javamail/mail)

  LGPL:

* JTransforms (com.github.rwl:jtransforms:2.4.0 -
http://sourceforge.net/projects/jtransforms/)

  LGPL 2.1:

* Javassist (org.javassist:javassist:3.18.1-GA - http://www.javassist.org/)





-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Release Livy 0.6.0 based on RC1

[Luciano Resende]

On Mon, Mar 18, 2019 at 14:29 Marcelo Vanzin 
wrote:

> On Mon, Mar 18, 2019 at 2:23 PM Luciano Resende 
> wrote:
> > There has been a lot of discussion around this, but at the moment it's
> > not acceptable to have binary jars in a source release.
>
> Can you clarify this?
>
> There are two ways to interpret that:
>
> - no jars files in the source archive. There is an empty test jar file
> in the source archive, don't think that counts.
>
> - releasing binaries at all. I saw a bunch of discussion around that
> and my understanding is that a lot of people are actually very pro
> having "convenience binaries".
>
> Anyway, whatever the IPMC says. If we'll only have a zip file of the
> sources, preparing the release will be much simpler, but also much
> less useful (no maven artifacts, for example).
>
> --
> Marcelo


The issue is the test jar on the source distro. I tried for  over a month
on this while I was releasing Toree and gave up. You could use the Spark
utility that builds a jar from scratch for you or download a jar from a
maven repo.


> --
Sent from my Mobile device

Re: [VOTE] Release Livy 0.6.0 based on RC1

[Luciano Resende]

-1

There has been a lot of discussion around this, but at the moment it's
not acceptable to have binary jars in a source release.
Also, there are lots of version mismatching between the included jars
and the third-party license file

Minor:
Extract folder should prefix apache in the name (e.g. apache-livy-xxx
instead of livy-xxx)

On Mon, Mar 18, 2019 at 2:02 PM Marcelo Vanzin
 wrote:
>
> This vote is for releasing Livy 0.6.0 based on RC1.
>
> The vote will be open at least 72 hours until Thursday March 21st, 21:00 UTC 
> and
> will pass with a minimum of 3 +1 binding votes and a majority of positive 
> votes.
>
> [+1] This release is ready to send to the Incubator PMC for approval
>
> [-1] This release is not ready because...
>
> This vote is held according to Apache Incubator release policy:
> https://incubator.apache.org/policy/incubation.html#releases
>
> The RC is based on tag v0.6.0-incubating-rc1:
> https://github.com/apache/incubator-livy/commit/b8861bbc3ad9aa0b7069fe1d7ae4a390bd422cb3
>
> The release files can be found here:
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc1/
>
> The staged maven artifacts can be found here:
> https://repository.apache.org/content/repositories/orgapachelivy-1006
>
> The list of resolved JIRAs in this release can be found here:
> https://issues.apache.org/jira/projects/LIVY/versions/12342736
>
> --
> Marcelo



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Move source repo to gitbox

[Luciano Resende]

+1

On Thu, Jan 3, 2019 at 15:57 Marcelo Vanzin 
wrote:

> Creating a formal vote for this. I don't think we have a choice but
> they seem to request a vote anyway. This will be lazy consensus, I
> plan to create an infra ticket for the migration on Monday if the vote
> passes.
>
> Starting with my +1.
>
>
> --
> Marcelo
>
-- 
Sent from my Mobile device

Re: GitHub emails on dev

[Luciano Resende]

Ok, so I checked and livy already have a reviews@ list, we just need
to make sure infra setup github notifications to that list, please
create a jira to handle that.
On Mon, Oct 8, 2018 at 9:42 PM Jean-Baptiste Onofré  wrote:
>
> +1
>
> and the lists can be created using the selfserve.
>
> Regards
> JB
>
> On 09/10/2018 03:02, Luciano Resende wrote:
> > You guys should create a list and have these forwarded to the new list.
> > Some projects use notifications@
> >
> > On Mon, Oct 8, 2018 at 17:46 Alex Bozarth  wrote:
> >
> >> I opened https://issues.apache.org/jira/browse/INFRA-17121 for INFRA to
> >> take a look into it.
> >>
> >>
> >> *Alex Bozarth*
> >> Software Engineer
> >> Center for Open-Source Data & AI Technologies
> >> --
> >> *E-mail:* *ajboz...@us.ibm.com* 
> >> *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
> >>
> >>
> >> 505 Howard Street
> >> <https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g>
> >> San Francisco, CA 94105
> >> <https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g>
> >> United States
> >> <https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g>
> >>
> >>
> >>
> >> [image: Inactive hide details for Marcelo Vanzin ---10/08/2018 04:23:04
> >> PM---Maybe infra did something to re-enable it. We asked them t]Marcelo
> >> Vanzin ---10/08/2018 04:23:04 PM---Maybe infra did something to re-enable
> >> it. We asked them to disable it way back (INFRA-14973). Maybe
> >>
> >> From: Marcelo Vanzin 
> >> To: dev@livy.incubator.apache.org
> >> Date: 10/08/2018 04:23 PM
> >> Subject: Re: GitHub emails on dev
> >> --
> >>
> >>
> >>
> >>
> >> Maybe infra did something to re-enable it. We asked them to disable it
> >> way back (INFRA-14973). Maybe reopen that ticket or file a new one.
> >> On Mon, Oct 8, 2018 at 4:19 PM Alex Bozarth  wrote:
> >>>
> >>>
> >>>
> >>> Is there a reason we've begun getting GitHub PR emails on the dev list?
> >> The
> >>> regular glut of emails for every comment on every PR probably shouldn't
> >> be
> >>> CC'd to dev@
> >>>
> >>>
> >>>  Alex Bozarth
> >>>  Software Engineer
> >>>  Center for Open-Source Data & AI Technologies
> >>>
> >>>
> >>>
> >>>
> >>>  E-mail: ajboz...@us.ibm.com
> >>>  GitHub: github.com/ajbozarth
> >>>505
> >> Howard Street
> >> <https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g>
> >>>  San
> >> Francisco, CA 94105
> >> <https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g>
> >>>
> >>> United
> >> States
> >> <https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >> --
> >> Marcelo
> >>
> >>
> >>
> >>
> >> --
> > Sent from my Mobile device
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: GitHub emails on dev

[Luciano Resende]

I will create the list in the morning and then we can ask infra to switch
the configured mailing list.

On Mon, Oct 8, 2018 at 18:05 Alex Bozarth  wrote:

> That's a good idea, how would we go about doing that? Ask infra or can a
> mentor do it? And what kind of approval would we need?
>
>
> *Alex Bozarth*
> Software Engineer
> Center for Open-Source Data & AI Technologies
> --
> *E-mail:* *ajboz...@us.ibm.com* 
> *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
>
>
> 505 Howard Street
> <https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g>
> San Francisco, CA 94105
> <https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g>
> United States
> <https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g>
>
>
>
> [image: Inactive hide details for Luciano Resende ---10/08/2018 06:02:30
> PM---You guys should create a list and have these forwarded to]Luciano
> Resende ---10/08/2018 06:02:30 PM---You guys should create a list and have
> these forwarded to the new list. Some projects use notificati
>
> From: Luciano Resende 
> To: dev@livy.incubator.apache.org
> Date: 10/08/2018 06:02 PM
> Subject: Re: GitHub emails on dev
> --
>
>
>
> You guys should create a list and have these forwarded to the new list.
> Some projects use notifications@
>
> On Mon, Oct 8, 2018 at 17:46 Alex Bozarth  wrote:
>
> > I opened https://issues.apache.org/jira/browse/INFRA-17121 for INFRA to
> > take a look into it.
> >
> >
> > *Alex Bozarth*
> > Software Engineer
> > Center for Open-Source Data & AI Technologies
> > --
> > *E-mail:* *ajboz...@us.ibm.com* 
> > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
> >
> >
> > 505 Howard Street
> <https://maps.google.com/?q=505+Howard+Street&entry=gmail&source=g>
> > <
> https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g
> >
> > San Francisco, CA 94105
> > <
> https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g
> >
> > United States
> > <
> https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g
> >
> >
> >
> >
> > [image: Inactive hide details for Marcelo Vanzin ---10/08/2018 04:23:04
> > PM---Maybe infra did something to re-enable it. We asked them t]Marcelo
> > Vanzin ---10/08/2018 04:23:04 PM---Maybe infra did something to re-enable
> > it. We asked them to disable it way back (INFRA-14973). Maybe
> >
> > From: Marcelo Vanzin 
> > To: dev@livy.incubator.apache.org
> > Date: 10/08/2018 04:23 PM
> > Subject: Re: GitHub emails on dev
> > --
> >
> >
> >
> >
> > Maybe infra did something to re-enable it. We asked them to disable it
> > way back (INFRA-14973). Maybe reopen that ticket or file a new one.
> > On Mon, Oct 8, 2018 at 4:19 PM Alex Bozarth  wrote:
> > >
> > >
> > >
> > > Is there a reason we've begun getting GitHub PR emails on the dev list?
> > The
> > > regular glut of emails for every comment on every PR probably shouldn't
> > be
> > > CC'd to dev@
> > >
> > >
> > >  Alex Bozarth
> > >  Software Engineer
> > >  Center for Open-Source Data & AI Technologies
> > >
> > >
> > >
> > >
> > >  E-mail: ajboz...@us.ibm.com
> > >  GitHub: github.com/ajbozarth
> > >505
> > Howard Street
> <https://maps.google.com/?q=505+Howard+Street&entry=gmail&source=g>
> > <
> https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g
> >
> > >  San
> > Francisco, CA 94105
> > <
> https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g
> >
> > >
>  United
> > States
> > <
> https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g
> >
>
>
> > >
> > >
> > >
> > >
> > >
> >
> >
> > --
> > Marcelo
> >
> >
> >
> >
> > --
> Sent from my Mobile device
>
>
>
> --
Sent from my Mobile device

Re: GitHub emails on dev

[Luciano Resende]

You guys should create a list and have these forwarded to the new list.
Some projects use notifications@

On Mon, Oct 8, 2018 at 17:46 Alex Bozarth  wrote:

> I opened https://issues.apache.org/jira/browse/INFRA-17121 for INFRA to
> take a look into it.
>
>
> *Alex Bozarth*
> Software Engineer
> Center for Open-Source Data & AI Technologies
> --
> *E-mail:* *ajboz...@us.ibm.com* 
> *GitHub: **github.com/ajbozarth* 
>
>
> 505 Howard Street
> 
> San Francisco, CA 94105
> 
> United States
> 
>
>
>
> [image: Inactive hide details for Marcelo Vanzin ---10/08/2018 04:23:04
> PM---Maybe infra did something to re-enable it. We asked them t]Marcelo
> Vanzin ---10/08/2018 04:23:04 PM---Maybe infra did something to re-enable
> it. We asked them to disable it way back (INFRA-14973). Maybe
>
> From: Marcelo Vanzin 
> To: dev@livy.incubator.apache.org
> Date: 10/08/2018 04:23 PM
> Subject: Re: GitHub emails on dev
> --
>
>
>
>
> Maybe infra did something to re-enable it. We asked them to disable it
> way back (INFRA-14973). Maybe reopen that ticket or file a new one.
> On Mon, Oct 8, 2018 at 4:19 PM Alex Bozarth  wrote:
> >
> >
> >
> > Is there a reason we've begun getting GitHub PR emails on the dev list?
> The
> > regular glut of emails for every comment on every PR probably shouldn't
> be
> > CC'd to dev@
> >
> >
> >  Alex Bozarth
> >  Software Engineer
> >  Center for Open-Source Data & AI Technologies
> >
> >
> >
> >
> >  E-mail: ajboz...@us.ibm.com
> >  GitHub: github.com/ajbozarth
> >505
> Howard Street
> 
> >  San
> Francisco, CA 94105
> 
> >
> > United
> States
> 
> >
> >
> >
> >
> >
>
>
> --
> Marcelo
>
>
>
>
> --
Sent from my Mobile device

Re: Missing board report

[Luciano Resende]

Livy team, the report is not optional... Could someone please help draft a
report... it should take a few minutes and we can help posting if you don’t
have access.

Thanks

On Tue, Oct 2, 2018 at 16:54 Justin Mclean  wrote:

> HI,
>
> Just a reminder that the report is due today and I don't see any
> discussion on it. It helps me finish the IPMC report on time if you get
> your report in on time.
>
> Thanks,
> Justin
>
-- 
Sent from my Mobile device

Re: Podling Report Reminder - February 2018

[Luciano Resende]

Thanks, signed off on the report.

On Mon, Feb 5, 2018 at 3:56 PM, Alex Bozarth  wrote:

> I've updated the report if a mentor could take a look and sign off (or
> give feedback).
>
>
> *Alex Bozarth*
> Software Engineer
> Spark Technology Center
> --
> *E-mail:* *ajboz...@us.ibm.com* 
> *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
>
>
> 505 Howard Street
> <https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g>
> San Francisco, CA 94105
> <https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g>
> United States
> <https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States&entry=gmail&source=g>
>
>
>
> [image: Inactive hide details for johndament---02/05/2018 03:39:37
> PM---Dear podling, This email was sent by an automated system on 
> beh]johndament---02/05/2018
> 03:39:37 PM---Dear podling, This email was sent by an automated system on
> behalf of the Apache
>
> From: johndam...@apache.org
> To: dev@livy.incubator.apache.org
> Date: 02/05/2018 03:39 PM
> Subject: Podling Report Reminder - February 2018
> --
>
>
>
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 21 February 2018, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, February 07).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
>the project or necessarily of its field
> *   A list of the three most important issues to address in the move
>towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.
> apache.org_incubator_February2018&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=S1_
> S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo&m=9w4xtXyRYOT11wkHHK2PmZpGws3TV-
> cfS06hWIz5_Ts&s=bk0pXyivBbYVNYwGkWrBcayuHCm00XM3YMlLps3E8yI&e=
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>
>
>
>
>


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Release Apache Livy 0.5.0-incubating (RC2)

[Luciano Resende]

+1 (binding)

On Mon, Jan 29, 2018 at 8:56 PM Alex Bozarth  wrote:

>
>
> The Apache Livy community has voted on and approved a proposal to release
> Apache Livy 0.5.0-incubating (RC2). We would like to request that the
> Incubator PMC members review and vote on this incubator release candidate.
>
> Apache Livy (incubating) 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.
>
>
> The livy dev voting thread can be found here:
> https://www.mail-archive.com/dev@livy.incubator.apache.org/msg00297.html
>
> And the results here:
> https://www.mail-archive.com/dev@livy.incubator.apache.org/msg00308.html
>
> Git tag: v0.5.0-incubating-rc2
> https://github.com/apache/incubator-livy/tree/v0.5.0-incubating-rc2
>
> All distribution packages, including signatures, digests, etc. can be found
> at:
> https://dist.apache.org/repos/dist/dev/incubator/livy/
>
> Staging artifacts can be found at:
> https://repository.apache.org/content/repositories/orgapachelivy-1005/
>
>
> The vote is open for at least 72 hours and passes if a majority of at least
> 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Livy 0.5.0-incubating
>
> [ ] -1 Do not release this package because ...
>
>
> Thank you on behalf of the Apache Livy community,
>
>  Alex Bozarth
>  Software Engineer
>  Spark Technology Center
>
>
>
>
>  E-mail: ajboz...@us.ibm.com
>  GitHub: github.com/ajbozarth
>505
> Howard Street
>  San
> Francisco, CA 94105
>
>  United States
>
>
>
>
>
> --
Sent from my Mobile device

Re: How to get the test logs from travis

[Luciano Resende]

Take a look at what Zeppelin does, they kind cat a lot of the logs and
related files which then get appended to the build results.

https://github.com/apache/zeppelin/blob/master/.travis.yml

On Wed, Sep 20, 2017 at 8:22 PM, Saisai Shao  wrote:

> Hi Team,
>
> Currently it is quite painful to figure out the cause of failure on travis
> test. Do you know how to get test logs from travis, is there a way
> supported by travis to either upload environment to some places, or log on
> to travis to dig the files.
>
> Previously we uploaded logs to azure when test is failed, I'm not sure it
> is still worked, shall we figure out a stable way to address this issue?
>
> Thanks
> Jerry
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Commit permission

[Luciano Resende]

Based on the Livy project proposal, I just added the following as PPMC
members (couldn't find Alex Man):


   -

   Marcelo Vanzin (van...@cloudera.com)
   -

   Jeff Zhang (zjf...@gmail.com)
   -

   Saisai Shao (ss...@hortonworks.com)
   -

   Kostas Sakellis (kos...@cloudera.com)


On Tue, Sep 5, 2017 at 9:59 AM, Marcelo Vanzin  wrote:

> I looked at Whimsy but couldn't find the list of committers...
> https://whimsy4.apache.org/roster/ppmc/livy
>
> I this is just a matter of opening an INFRA ticket to add you, I can
> do it. But I'm not really super familiar with the process.
>
> On Mon, Sep 4, 2017 at 8:15 PM, Jeff Zhang  wrote:
> > Can anyone help to check whether I have commit permission, I am trying to
> > commit PR 43, but fails due to permission issue.   My apache mail is :
> > zjf...@apache.org
> >
> >
> > Writing objects: 100% (12/12), 870 bytes | 0 bytes/s, done.
> >
> > Total 12 (delta 4), reused 0 (delta 0)
> >
> > remote: You are not authorized to edit this repository.
> >
> > remote:
> >
> > To https://git-wip-us.apache.org/repos/asf/incubator-livy.git
> >
> >  ! [remote rejected] PR_TOOL_MERGE_PR_43_MASTER -> master (pre-receive
> hook
> > declined)
> >
> > error: failed to push some refs to '
> > https://git-wip-us.apache.org/repos/asf/incubator-livy.git'
> >
> > Restoring head pointer to master
> >
> > git checkout master
>
>
>
> --
> Marcelo
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Update ASF GitHub Bot Settings?

[Luciano Resende]

Please file an INFRA jira describing you want to change the GitHub workflow.

On Mon, Aug 28, 2017 at 11:22 AM, Alex Bozarth  wrote:

>
>
> Is there a way to edit the default ASF GitHub Bot settings? I think it's
> great that it auto-comments on our JIRAs with links to new PRs, but it's
> also auto-commenting on the JIRAs for every single comment on those PRs,
> which clutters up both the JIRA and the Activity Stream (which is how I
> personally keep up on the Livy JIRAs.
>
>
>  Alex Bozarth
>  Software Engineer
>  Spark Technology Center
>
>
>
>
>  E-mail: ajboz...@us.ibm.com
>  GitHub: github.com/ajbozarth
>505
> Howard Street
>      San
> Francisco, CA 94105
>
>  United States
>
>
>
>
>
>


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: The process of Livy 0.4.0-incubating release

[Luciano Resende]

On Sun, Aug 27, 2017 at 11:53 PM, Saisai Shao 
wrote:

> Hi mentors,
>
> Would you please guide us on how to release the Livy 0.4.0-incubating,
> including artifact publish.
>

The artifacts move from :
https://dist.apache.org/repos/dist/dev/incubator/livy/

to
https://dist.apache.org/repos/dist/release/incubator/livy/


>
> Also regarding push artifacts to repo, are we inclining to change to Maven
> central repo, or we still use Cloudera repo, any suggestion?
>
>
You should have a maven staging repository at repository.apache.org, after
a release is approved, that repository should just be released.


> Besides, for Python package release, do we need to publish this python
> client package to PIP or we don't need to do this now, any comment?
>
>
+0, I would say do what you have been doing in the past


> Thanks for your help and suggestion.
>
> Best regards,
> Saisai (Jerry)
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Help to verify Apache Livy 0.4.0-incubating release

[Luciano Resende]

This is minor and can be handled in the next release or if we make another
RC.

On Tue, Aug 22, 2017 at 3:35 PM, Alex Bozarth  wrote:

> Nice catch, it must not be a big issue though because it's been that way
> since the original Livy 0.2.0 release.
>
> @jerry do you think we should update this with a minor and open a rc3 or
> just fix it in the next release?
>
> *Alex Bozarth*
> Software Engineer
> Spark Technology Center
> --
> *E-mail:* *ajboz...@us.ibm.com* 
> *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
>
>
> 505 Howard Street
> San Francisco, CA 94105
> United States
>
>
>
> [image: Inactive hide details for Meisam Fathi ---08/22/2017 10:00:19
> AM---The version of org.apache.httpcomponents:httpclient is diffe]Meisam
> Fathi ---08/22/2017 10:00:19 AM---The version of 
> org.apache.httpcomponents:httpclient
> is different in /pom.xml from the version in /cl
>
> From: Meisam Fathi 
> To: dev@livy.incubator.apache.org
> Date: 08/22/2017 10:00 AM
> Subject: Re: Help to verify Apache Livy 0.4.0-incubating release
> --
>
>
>
> The version of org.apache.httpcomponents:httpclient is different in
> /pom.xml from the version in /client-http/pom.xml
>
> /pom.xml --->  ${httpclient.version} ---> 4.5.2
> /client-http/pom.xml --->  4.5.1
>
> Is this intended?
>
> Thanks,
> Meisam
>
> On Thu, Aug 17, 2017 at 12:34 AM, Saisai Shao 
>
> > Hi all,
> >
> >
> > We're under progress to make a first Apache release of Livy
> >
> > (0.4.0-incubating), we really hope you could verify the RC2[1] release
> >
> > (binary and source) locally and return us the feedbacks.
> >
> [1]https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__dist.apache.org_repos_dist_dev_incubator_livy_0&d=
> DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-
> cx37DPYDyo&m=Kb-p_IVOP_NdMjLDuaQ3n9M8JuXyOyZoJMW1js8FH1c&s=
> LgN1J8mfdzW3GoDhuYQeFGOVag4Ncz_WBKBTcVau970&e= .
> >
>
>
>
>


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: To release a first Apache version Livy

[Luciano Resende]

I think the question is more, what the users expect as Livy is a server
app, IMHO most users are expecting a binary release that they can just
start/run. But the community can decide, and maybe do a first source
release and subsequent binary release.

On Tue, Aug 15, 2017 at 3:16 AM, Saisai Shao  wrote:

> Hi All,
>
> I just created a new tag RC2 which includes new commits to generate
> third-party dependencies license through maven plugin. Would you please
> help to check and verify this RC2 (
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.4.0-incubating/),
> thanks!
>
> PS. I only upload the source release, not binary release.
>
> Question: are we inclined to release a source release or binary release for
> the first Apache version? Binary release requires more works but easy for
> user to use, what is your preference?
>
> Best regards
>
> On Tue, Aug 8, 2017 at 11:56 AM, Luciano Resende 
> wrote:
>
> > The top level distribution (e.g. tar.gz should have a proper LICENSE and
> > NOTES) and it should reflect the included dependencies LICENSE and NOTES.
> >
> > On Mon, Aug 7, 2017 at 7:31 PM, Saisai Shao 
> > wrote:
> >
> > > Hi Luciano, should we include all the third jar license in a file in
> > binary
> > > release? I already add this as DEPENDENCIES file in each Livy jars
> > > META-INF, is it enough?
> > >
> > > On Tue, Aug 8, 2017 at 10:02 AM, Luciano Resende  >
> > > wrote:
> > >
> > > > There is also a simpler script for creating a release at bahir, it
> was
> > > > inspired by the Spark one.
> > > >
> > > > https://github.com/apache/bahir/blob/master/dev/release-build.sh
> > > >
> > > > On Mon, Aug 7, 2017 at 6:14 PM, Saisai Shao 
> > > > wrote:
> > > >
> > > > > Thanks Marcelo for your comments. I checked create_release.sh in
> > > Spark, I
> > > > > think I will adopt this after this first release, for this first
> > > release
> > > > I
> > > > > would like to do each step in person.
> > > > >
> > > > > On Tue, Aug 8, 2017 at 8:34 AM, Marcelo Vanzin <
> van...@cloudera.com>
> > > > > wrote:
> > > > >
> > > > > > Spark has a "create_release.sh" script, I wonder if that can be
> > > reused
> > > > > > / adapted for Livy to make this easier in the future.
> > > > > >
> > > > > > I tracked all the dependencies' licenses for the incubation
> > proposal,
> > > > > > if that helps; although I didn't have the actual text of the
> > licenses
> > > > > > there.
> > > > > >
> > > > > > On Mon, Aug 7, 2017 at 5:29 PM, Luciano Resende <
> > > luckbr1...@gmail.com>
> > > > > > wrote:
> > > > > > > Just took a quick look at it, and here are some comments:
> > > > > > >
> > > > > > > Apache release requires source releases as described below
> > > > > > > http://www.apache.org/legal/release-policy.html#source-
> packages
> > > > > > >
> > > > > > > Binary releases can also be provided as a convenience for
> users:
> > > > > > > http://www.apache.org/legal/release-policy.html#compiled-
> > packages
> > > > > > >
> > > > > > >
> > > > > > > Also, for the binary artifact, I would list each included jar
> and
> > > > it's
> > > > > > > license type in the license file (see below as an example)
> > > > > > > http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/
> > > > > > trunk/distribution/all/src/main/release/bin/LICENSE
> > > > > > >
> > > > > > > But note that, the source release artifact, which should not
> > > include
> > > > > any
> > > > > > > dependency jars, should have the LICENSE file similar to what
> is
> > in
> > > > the
> > > > > > > root of git today.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Aug 7, 2017 at 2:16 AM, Saisai Shao <
> > > sai.sai.s...@gmail.com>
> > > > > > wrote:
> > > > > > >
> > > > &

Re: To release a first Apache version Livy

[Luciano Resende]

The top level distribution (e.g. tar.gz should have a proper LICENSE and
NOTES) and it should reflect the included dependencies LICENSE and NOTES.

On Mon, Aug 7, 2017 at 7:31 PM, Saisai Shao  wrote:

> Hi Luciano, should we include all the third jar license in a file in binary
> release? I already add this as DEPENDENCIES file in each Livy jars
> META-INF, is it enough?
>
> On Tue, Aug 8, 2017 at 10:02 AM, Luciano Resende 
> wrote:
>
> > There is also a simpler script for creating a release at bahir, it was
> > inspired by the Spark one.
> >
> > https://github.com/apache/bahir/blob/master/dev/release-build.sh
> >
> > On Mon, Aug 7, 2017 at 6:14 PM, Saisai Shao 
> > wrote:
> >
> > > Thanks Marcelo for your comments. I checked create_release.sh in
> Spark, I
> > > think I will adopt this after this first release, for this first
> release
> > I
> > > would like to do each step in person.
> > >
> > > On Tue, Aug 8, 2017 at 8:34 AM, Marcelo Vanzin 
> > > wrote:
> > >
> > > > Spark has a "create_release.sh" script, I wonder if that can be
> reused
> > > > / adapted for Livy to make this easier in the future.
> > > >
> > > > I tracked all the dependencies' licenses for the incubation proposal,
> > > > if that helps; although I didn't have the actual text of the licenses
> > > > there.
> > > >
> > > > On Mon, Aug 7, 2017 at 5:29 PM, Luciano Resende <
> luckbr1...@gmail.com>
> > > > wrote:
> > > > > Just took a quick look at it, and here are some comments:
> > > > >
> > > > > Apache release requires source releases as described below
> > > > > http://www.apache.org/legal/release-policy.html#source-packages
> > > > >
> > > > > Binary releases can also be provided as a convenience for users:
> > > > > http://www.apache.org/legal/release-policy.html#compiled-packages
> > > > >
> > > > >
> > > > > Also, for the binary artifact, I would list each included jar and
> > it's
> > > > > license type in the license file (see below as an example)
> > > > > http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/
> > > > trunk/distribution/all/src/main/release/bin/LICENSE
> > > > >
> > > > > But note that, the source release artifact, which should not
> include
> > > any
> > > > > dependency jars, should have the LICENSE file similar to what is in
> > the
> > > > > root of git today.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Mon, Aug 7, 2017 at 2:16 AM, Saisai Shao <
> sai.sai.s...@gmail.com>
> > > > wrote:
> > > > >
> > > > >> Hi Team,
> > > > >>
> > > > >> Today I cut a RC1 release based on branch-0.4, here is the link (
> > > > >> https://github.com/apache/incubator-livy/releases/tag/
> > > > >> v0.4.0-incubating-rc1
> > > > >> and https://dist.apache.org/repos/dist/dev/incubator/livy/),
> would
> > > you
> > > > >> please help to test and verify. Thanks a lot and appreciate your
> > help.
> > > > >>
> > > > >> Best regards,
> > > > >> Saisai
> > > > >>
> > > > >> On Sat, Aug 5, 2017 at 10:44 AM, Alex Bozarth <
> ajboz...@us.ibm.com>
> > > > wrote:
> > > > >>
> > > > >> > Last comment on the INFRA JIRA seemed to indicate that they hit
> a
> > > snag
> > > > >> > with the import over a week ago and he never got back to us
> after.
> > > He
> > > > >> told
> > > > >> > us to keep using the Cloudera JIRA until he successfully
> > completed a
> > > > test
> > > > >> > import then we could re-export for him.
> > > > >> >
> > > > >> >
> > > > >> > *Alex Bozarth*
> > > > >> > Software Engineer
> > > > >> > Spark Technology Center
> > > > >> > --
> > > > >> > *E-mail:* *ajboz...@us.ibm.com* 
> > > > >> > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
> > > > >> >
> > > > >&g

Re: To release a first Apache version Livy

[Luciano Resende]

There is also a simpler script for creating a release at bahir, it was
inspired by the Spark one.

https://github.com/apache/bahir/blob/master/dev/release-build.sh

On Mon, Aug 7, 2017 at 6:14 PM, Saisai Shao  wrote:

> Thanks Marcelo for your comments. I checked create_release.sh in Spark, I
> think I will adopt this after this first release, for this first release I
> would like to do each step in person.
>
> On Tue, Aug 8, 2017 at 8:34 AM, Marcelo Vanzin 
> wrote:
>
> > Spark has a "create_release.sh" script, I wonder if that can be reused
> > / adapted for Livy to make this easier in the future.
> >
> > I tracked all the dependencies' licenses for the incubation proposal,
> > if that helps; although I didn't have the actual text of the licenses
> > there.
> >
> > On Mon, Aug 7, 2017 at 5:29 PM, Luciano Resende 
> > wrote:
> > > Just took a quick look at it, and here are some comments:
> > >
> > > Apache release requires source releases as described below
> > > http://www.apache.org/legal/release-policy.html#source-packages
> > >
> > > Binary releases can also be provided as a convenience for users:
> > > http://www.apache.org/legal/release-policy.html#compiled-packages
> > >
> > >
> > > Also, for the binary artifact, I would list each included jar and it's
> > > license type in the license file (see below as an example)
> > > http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/
> > trunk/distribution/all/src/main/release/bin/LICENSE
> > >
> > > But note that, the source release artifact, which should not include
> any
> > > dependency jars, should have the LICENSE file similar to what is in the
> > > root of git today.
> > >
> > >
> > >
> > >
> > >
> > > On Mon, Aug 7, 2017 at 2:16 AM, Saisai Shao 
> > wrote:
> > >
> > >> Hi Team,
> > >>
> > >> Today I cut a RC1 release based on branch-0.4, here is the link (
> > >> https://github.com/apache/incubator-livy/releases/tag/
> > >> v0.4.0-incubating-rc1
> > >> and https://dist.apache.org/repos/dist/dev/incubator/livy/), would
> you
> > >> please help to test and verify. Thanks a lot and appreciate your help.
> > >>
> > >> Best regards,
> > >> Saisai
> > >>
> > >> On Sat, Aug 5, 2017 at 10:44 AM, Alex Bozarth 
> > wrote:
> > >>
> > >> > Last comment on the INFRA JIRA seemed to indicate that they hit a
> snag
> > >> > with the import over a week ago and he never got back to us after.
> He
> > >> told
> > >> > us to keep using the Cloudera JIRA until he successfully completed a
> > test
> > >> > import then we could re-export for him.
> > >> >
> > >> >
> > >> > *Alex Bozarth*
> > >> > Software Engineer
> > >> > Spark Technology Center
> > >> > --
> > >> > *E-mail:* *ajboz...@us.ibm.com* 
> > >> > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
> > >> >
> > >> >
> > >> > 505 Howard Street
> > >> > San Francisco, CA 94105
> > >> > United States
> > >> >
> > >> >
> > >> >
> > >> > [image: Inactive hide details for Bikas Saha ---08/04/2017 07:22:50
> > >> > PM---Hi, Most of those jiras looked like bug fixes to me. Hence I
> > t]Bikas
> > >> > Saha ---08/04/2017 07:22:50 PM---Hi, Most of those jiras looked like
> > bug
> > >> > fixes to me. Hence I thought 0.4 could be a bug fix release.
> > >> >
> > >> > From: Bikas Saha 
> > >> > To: "dev@livy.incubator.apache.org" 
> > >> > Date: 08/04/2017 07:22 PM
> > >> > Subject: Re: To release a first Apache version Livy
> > >> > --
> > >> >
> > >> >
> > >> >
> > >> > Hi,
> > >> >
> > >> >
> > >> > Most of those jiras looked like bug fixes to me. Hence I thought 0.4
> > >> could
> > >> > be a bug fix release. But I am ok releasing the current state so
> users
> > >> can
> > >> > gets an Apache release to transition to.
> > >> >
> > >> >
> > >> > Given that its 

Re: To release a first Apache version Livy

[Luciano Resende]

> > > >
> > > >
> > > >
> > > > Hi Alex, can you please list the JIRAs for UI related works you want
> to
> > > > merge in 0.4 release?
> > > >
> > > > Thanks
> > > >
> > > > On Sat, Jul 29, 2017 at 7:59 AM, Alex Bozarth 
> > > wrote:
> > > >
> > > > > After some tweaking and opening of PRs today, I'll change my vote
> to
> > a
> > > +1
> > > > > with the inclusion of my currently open PRs.
> > > > >
> > > > >
> > > > > *Alex Bozarth*
> > > > > Software Engineer
> > > > > Spark Technology Center
> > > > > --
> > > > > *E-mail:* *ajboz...@us.ibm.com* 
> > > > > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
> > > > >
> > > > >
> > > > > 505 Howard Street
> > > > > San Francisco, CA 94105
> > > > > United States
> > > > >
> > > > >
> > > > >
> > > > > [image: Inactive hide details for "Alex Bozarth" ---07/28/2017
> > 01:01:16
> > > > > PM---I'm a +0 on this, I think we should get in a release
> soon,]"Alex
> > > > > Bozarth" ---07/28/2017 01:01:16 PM---I'm a +0 on this, I think we
> > > should
> > > > > get in a release soon, but I'm not sure if we should wait until
> > > > >
> > > > > From: "Alex Bozarth" 
> > > > > To: dev@livy.incubator.apache.org
> > > > > Date: 07/28/2017 01:01 PM
> > > > > Subject: Re: To release a first Apache version Livy
> > > > > --
> > > > >
> > > > >
> > > > >
> > > > > I'm a +0 on this, I think we should get in a release soon, but I'm
> > not
> > > > > sure if we should wait until the Web UI and Documentation are
> > finished
> > > > > (tracking in *LIVY-87* <https://issues.cloudera.org/browse/LIVY-87
> >
> > > and
> > > > > *LIVY-384* <https://issues.cloudera.org/browse/LIVY-384>). If
> others
> > > are
> > > > > fine releasing with these feature partially complete then I'll be
> > okay
> > > as
> > > > > well.
> > > > >
> > > > > *Alex Bozarth*
> > > > > Software Engineer
> > > > > Spark Technology Center
> > > > > --
> > > > > *E-mail:* *ajboz...@us.ibm.com* 
> > > > > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
> > > > >
> > > > >
> > > > > 505 Howard Street
> > > > > San Francisco, CA 94105
> > > > > United States
> > > > >
> > > > >
> > > > >
> > > > > Jeff Zhang ---07/28/2017 01:12:24 AM---+1 for making the first
> apache
> > > > > release. Saisai Shao 于2017年7月28日周五
> 下午3:42写道：
> > > > >
> > > > > From: Jeff Zhang 
> > > > > To: dev@livy.incubator.apache.org
> > > > > Date: 07/28/2017 01:12 AM
> > > > > Subject: Re: To release a first Apache version Livy
> > > > > --
> > > > >
> > > > >
> > > > >
> > > > > +1 for making the first apache release.
> > > > >
> > > > >
> > > > > Saisai Shao 于2017年7月28日周五 下午3:42写道：
> > > > >
> > > > > > Hi Team,
> > > > > >
> > > > > > We have already done most of the migration works to Apache, I
> think
> > > it
> > > > > > would be better to have a first Apache release based on the
> current
> > > > code.
> > > > > > What do you think?
> > > > > >
> > > > > > Thanks
> > > > > > Saisai
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: New Livy Logo Discussion and Input

[Luciano Resende]

On Mon, Aug 7, 2017 at 2:55 PM, Marcelo Vanzin  wrote:

> I don't really have opinions about the current logo, but you'd probably get
> more feedback if you suggested a new logo instead of asking whether it
> should be changed.
>

+1

If you have the time and resource, I would say go for it and provide some
proposals.

I would suggest trying to design something that help users associate the
logo to what the project does.



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: To release a first Apache version Livy

[Luciano Resende]

 not sure if we should wait until
> >> >
> >> > From: "Alex Bozarth" 
> >> > To: dev@livy.incubator.apache.org
> >> > Date: 07/28/2017 01:01 PM
> >> > Subject: Re: To release a first Apache version Livy
> >> > --
> >> >
> >> >
> >> >
> >> > I'm a +0 on this, I think we should get in a release soon, but I'm not
> >> > sure if we should wait until the Web UI and Documentation are finished
> >> > (tracking in *LIVY-87* <https://issues.cloudera.org/browse/LIVY-87>
> and
> >> > *LIVY-384* <https://issues.cloudera.org/browse/LIVY-384>). If others
> >> are
> >> > fine releasing with these feature partially complete then I'll be okay
> >> as
> >> > well.
> >> >
> >> > *Alex Bozarth*
> >> > Software Engineer
> >> > Spark Technology Center
> >> > --
> >> > *E-mail:* *ajboz...@us.ibm.com* 
> >> > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
> >> >
> >> >
> >> > 505 Howard Street
> >> > San Francisco, CA 94105
> >> > United States
> >> >
> >> >
> >> >
> >> > Jeff Zhang ---07/28/2017 01:12:24 AM---+1 for making the first apache
> >> > release. Saisai Shao 于2017年7月28日周五 下午3:42写道：
> >> >
> >> > From: Jeff Zhang 
> >> > To: dev@livy.incubator.apache.org
> >> > Date: 07/28/2017 01:12 AM
> >> > Subject: Re: To release a first Apache version Livy
> >> > --
> >> >
> >> >
> >> >
> >> > +1 for making the first apache release.
> >> >
> >> >
> >> > Saisai Shao 于2017年7月28日周五 下午3:42写道：
> >> >
> >> > > Hi Team,
> >> > >
> >> > > We have already done most of the migration works to Apache, I think
> it
> >> > > would be better to have a first Apache release based on the current
> >> code.
> >> > > What do you think?
> >> > >
> >> > > Thanks
> >> > > Saisai
> >> > >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >>
> >>
> >
>
>
>
>


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Livy website is now live

[Luciano Resende]

I believe the most important thing is to have the incubator disclaimer on
the pages, and that is available on the bottom of the page.

The Incubator website guidelines don't say anything about explicitly
calling it incubator on the title.
https://incubator.apache.org/guides/sites.html

But I am ok with both ways.


On Thu, Jul 20, 2017 at 1:44 PM, Alex Bozarth  wrote:

> Dang, can't believe I messed that one up, I'll submit a fix
>
>
> *Alex Bozarth*
> Software Engineer
> Spark Technology Center
> --
> *E-mail:* *ajboz...@us.ibm.com* 
> *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
>
>
> 505 Howard Street
> San Francisco, CA 94105
> United States
>
>
>
> [image: Inactive hide details for Marcelo Vanzin ---07/20/2017 01:39:48
> PM---Sweet! Shouldn't the page say "incubating" though?]Marcelo Vanzin
> ---07/20/2017 01:39:48 PM---Sweet! Shouldn't the page say "incubating"
> though?
>
> From: Marcelo Vanzin 
> To: dev@livy.incubator.apache.org
> Date: 07/20/2017 01:39 PM
> Subject: Re: Livy website is now live
> --
>
>
>
> Sweet!
>
> Shouldn't the page say "incubating" though?
>
> e.g. http://impala.incubator.apache.org/
>
>
> On Thu, Jul 20, 2017 at 1:33 PM, Luciano Resende 
> wrote:
> > We are live now:
> >
> > http://livy.incubator.apache.org/
> >
> >
> > --
> > Luciano Resende
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
>
>
>
> --
> Marcelo
>
>
>
>
>


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Livy website is now live

[Luciano Resende]

We are live now:

http://livy.incubator.apache.org/


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Livy Slack and the move to Apache

[Luciano Resende]

+1 for using the project mailing lists.

On Wed, Jul 19, 2017 at 7:21 PM, Alex Bozarth  wrote:

>
>
> With our move to Apache I looked into and discussed with Luciano how we
> should handle the Livy Slack that we link to on the README and came to the
> following answer:
>
> I petition we officially abandon the Livy Dev Slack channel and
> leave
> final messages pointing users to use the email lists.
>
> I'm not sure this is something we should vote on, but I strongly believe a
> solid decision should be made. There is no precedence for Apache projects
> to have Slack channels (since the email lists should be used) and very few
> even have unofficial Slack channels. If everyone agrees, I plan to remove
> the link to the Slack channel in my upcoming README updates PR and we
> should leave official statements pointing to the email list on the Slack.
>
>
>  Alex Bozarth
>  Software Engineer
>  Spark Technology Center
>
>
>
>
>  E-mail: ajboz...@us.ibm.com
>  GitHub: github.com/ajbozarth
>505
> Howard Street
>          San
> Francisco, CA 94105
>
>  United States
>
>
>
>
>
>


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Commit style best practices, was Re: incubator-livy-website git commit: Fix bug in merge_livy_pr.py because incubator-livy-website repo has no branch it's name started with "branch-"

[Luciano Resende]

Could we try to follow some best practices on PR title, commit message, etc?

Some info from: http://bahir.apache.org/contributing/#Creating+a+Pull+
Request

- Open a pull request against the master branch

   - The PR title should be of the form [LIVY-] Title, where LIVY-
   is the relevant JIRA number and Title may be the JIRA’s title or a more
   specific title describing the PR itself.
   - If the pull request is still a work in progress, and so is not ready
   to be merged, but needs to be pushed to Github to facilitate review, then
   add [WIP] after the component.
   - For website work, a JIRA is not required

- Follow The 7 rules for a great commit message
<http://chris.beams.io/posts/git-commit/>

   - Separate subject from body with a blank line
   - Limit the subject line to 50 characters
   - Capitalize the subject line
   - Do not end the subject line with a period
   - Use the imperative mood in the subject line
   - Wrap the body at 72 characters
   - Use the body to explain what and why vs. how

Below is an example of a good commit message

[LIVY-001] Performance enhancements for decision tree

Generate Matrix with random values through local memory
if there is sufficient memory.



Thoughts ?

On Thu, Jul 20, 2017 at 1:03 PM,  wrote:

> Repository: incubator-livy-website
> Updated Branches:
>   refs/heads/master 27348bab6 -> 572b37b1e
>
>
> Fix bug in merge_livy_pr.py because incubator-livy-website repo has no
> branch it's name started with "branch-"
>
>
> Project: http://git-wip-us.apache.org/repos/asf/incubator-livy-websit
> e/repo
> Commit: http://git-wip-us.apache.org/repos/asf/incubator-livy-websit
> e/commit/572b37b1
> Tree: http://git-wip-us.apache.org/repos/asf/incubator-livy-websit
> e/tree/572b37b1
> Diff: http://git-wip-us.apache.org/repos/asf/incubator-livy-websit
> e/diff/572b37b1
>
> Branch: refs/heads/master
> Commit: 572b37b1efc2a2947272790261b6ba023ec53b74
> Parents: 27348ba
> Author: jerryshao 
> Authored: Thu Jul 20 13:02:23 2017 -0700
> Committer: jerryshao 
> Committed: Thu Jul 20 13:03:22 2017 -0700
>
> --
>  merge_livy_pr.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/incubator-livy-websit
> e/blob/572b37b1/merge_livy_pr.py
> --
> diff --git a/merge_livy_pr.py b/merge_livy_pr.py
> index b527a29..7296aef 100755
> --- a/merge_livy_pr.py
> +++ b/merge_livy_pr.py
> @@ -359,7 +359,7 @@ def main():
>  original_head = get_current_ref()
>
>  branches = get_json("%s/branches" % GITHUB_API_BASE)
> -branch_names = filter(lambda x: x.startswith("branch-"), [x['name']
> for x in branches])
> +branch_names = [x['name'] for x in branches]
>  # Assumes branch names can be sorted lexicographically
>  latest_branch = sorted(branch_names, reverse=True)[0]
>
>
>


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Another approach for Livy Website

[Luciano Resende]

One pub-sub is configured, every time we commit to a "content" branch, the
website gets updated.

On Wed, Jul 19, 2017 at 8:08 PM, Alex Bozarth  wrote:

> Thanks, will there be a straight forward process to it for future updates
> or will we have to open a INFRA JIRA each time?
>
>
> *Alex Bozarth*
> Software Engineer
> Spark Technology Center
> --
> *E-mail:* *ajboz...@us.ibm.com* 
> *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
>
>
> 505 Howard Street
> San Francisco, CA 94105
> United States
>
>
>
> [image: Inactive hide details for Luciano Resende ---07/19/2017 08:02:27
> PM---Yes, let me create a INFRA JIRA to publish it. On Wed, Ju]Luciano
> Resende ---07/19/2017 08:02:27 PM---Yes, let me create a INFRA JIRA to
> publish it. On Wed, Jul 19, 2017 at 7:59 PM, Alex Bozarth 
> From: Luciano Resende 
> To: dev@livy.incubator.apache.org
> Date: 07/19/2017 08:02 PM
> Subject: Re: Another approach for Livy Website
> --
>
>
>
> Yes, let me create a INFRA JIRA to publish it.
>
> On Wed, Jul 19, 2017 at 7:59 PM, Alex Bozarth  wrote:
>
> > Thanks Luciano, are there any steps we still need to take for the website
> > to actually start showing up at livy.incubating.apache.org? It currently
> > throws a 404 and livy.apache.org, which should also work, doesn't even
> > exist.
> >
> >
> > *Alex Bozarth*
> > Software Engineer
> > Spark Technology Center
> > --
> > *E-mail:* *ajboz...@us.ibm.com* 
> > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
> >
> >
> > 505 Howard Street
> > San Francisco, CA 94105
> > United States
> >
> >
> >
> > [image: Inactive hide details for Luciano Resende ---07/19/2017 06:56:52
> > PM---After my little mistake, a pushing from different local r]Luciano
> > Resende ---07/19/2017 06:56:52 PM---After my little mistake, a pushing
> from
> > different local repositry, things are fixed and it should be
> >
> > From: Luciano Resende 
> > To: dev@livy.incubator.apache.org
> > Date: 07/19/2017 06:56 PM
> > Subject: Re: Another approach for Livy Website
> > --
>
> >
> >
> >
> > After my little mistake, a pushing from different local repositry, things
> > are fixed and it should be ready now:
> >
> >
> https://github.com/apache/incubator-livy-website
>
> >
> > Thanks, Alex and others for the patience getting this ready.
> >
> >
> > On Wed, Jul 19, 2017 at 5:20 PM, Alex Bozarth 
> wrote:
> >
> > > Thanks Jerry,
> > >
> > > @Luciano if the code looks good to you can you do copy? I'll follow up
> by
> > > opening a few PRs to move the Docs out of the README into the website
> > once
> > > you've finished the copy.
> > >
> > >
> > > *Alex Bozarth*
> > > Software Engineer
> > > Spark Technology Center
> > > --
> > > *E-mail:* *ajboz...@us.ibm.com* 
> > > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
> > >
> > >
> > > 505 Howard Street
> > > San Francisco, CA 94105
> > > United States
> > >
> > >
> > >
> > > [image: Inactive hide details for Saisai Shao ---07/19/2017 05:17:12
> > > PM---Hi Alex, if think the changes are pretty ready, you can
> creat]Saisai
> > > Shao ---07/19/2017 05:17:12 PM---Hi Alex, if think the changes are
> pretty
> > > ready, you can create a PR to incubator-livy-website.
> > >
> > > From: Saisai Shao 
> > > To: dev@livy.incubator.apache.org
> > > Date: 07/19/2017 05:17 PM
> > > Subject: Re: Another approach for Livy Website
> > > --
> >
> > >
> > >
> > >
> > > Hi Alex, if think the changes are pretty ready, you can create a PR  to
> > > incubator-livy-website.
> > >
> > > Thanks
> > > Jerry
> > >
> > > On Mon, Jul 17, 2017 at 6:12 PM, Alex Bozarth 
> > wrote:
> > >
> > > > I have a personal GitHub repo all ready to go:
> > > >
> > https://github.com/ajbozarth/incubator-livy-website
> >
> > > >
> > > > The master branch is a fork of apache/apache-website-template plus my
> > > > Livy update commit.
> > > > The repo also includes an old-site branch with a copy of the gh-page

Re: Another approach for Livy Website

[Luciano Resende]

Yes, let me create a INFRA JIRA to publish it.

On Wed, Jul 19, 2017 at 7:59 PM, Alex Bozarth  wrote:

> Thanks Luciano, are there any steps we still need to take for the website
> to actually start showing up at livy.incubating.apache.org? It currently
> throws a 404 and livy.apache.org, which should also work, doesn't even
> exist.
>
>
> *Alex Bozarth*
> Software Engineer
> Spark Technology Center
> --
> *E-mail:* *ajboz...@us.ibm.com* 
> *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
>
>
> 505 Howard Street
> San Francisco, CA 94105
> United States
>
>
>
> [image: Inactive hide details for Luciano Resende ---07/19/2017 06:56:52
> PM---After my little mistake, a pushing from different local r]Luciano
> Resende ---07/19/2017 06:56:52 PM---After my little mistake, a pushing from
> different local repositry, things are fixed and it should be
>
> From: Luciano Resende 
> To: dev@livy.incubator.apache.org
> Date: 07/19/2017 06:56 PM
> Subject: Re: Another approach for Livy Website
> --
>
>
>
> After my little mistake, a pushing from different local repositry, things
> are fixed and it should be ready now:
>
> https://github.com/apache/incubator-livy-website
>
> Thanks, Alex and others for the patience getting this ready.
>
>
> On Wed, Jul 19, 2017 at 5:20 PM, Alex Bozarth  wrote:
>
> > Thanks Jerry,
> >
> > @Luciano if the code looks good to you can you do copy? I'll follow up by
> > opening a few PRs to move the Docs out of the README into the website
> once
> > you've finished the copy.
> >
> >
> > *Alex Bozarth*
> > Software Engineer
> > Spark Technology Center
> > --
> > *E-mail:* *ajboz...@us.ibm.com* 
> > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
> >
> >
> > 505 Howard Street
> > San Francisco, CA 94105
> > United States
> >
> >
> >
> > [image: Inactive hide details for Saisai Shao ---07/19/2017 05:17:12
> > PM---Hi Alex, if think the changes are pretty ready, you can creat]Saisai
> > Shao ---07/19/2017 05:17:12 PM---Hi Alex, if think the changes are pretty
> > ready, you can create a PR to incubator-livy-website.
> >
> > From: Saisai Shao 
> > To: dev@livy.incubator.apache.org
> > Date: 07/19/2017 05:17 PM
> > Subject: Re: Another approach for Livy Website
> > --
>
> >
> >
> >
> > Hi Alex, if think the changes are pretty ready, you can create a PR  to
> > incubator-livy-website.
> >
> > Thanks
> > Jerry
> >
> > On Mon, Jul 17, 2017 at 6:12 PM, Alex Bozarth 
> wrote:
> >
> > > I have a personal GitHub repo all ready to go:
> > >
> https://github.com/ajbozarth/incubator-livy-website
>
> > >
> > > The master branch is a fork of apache/apache-website-template plus my
> > > Livy update commit.
> > > The repo also includes an old-site branch with a copy of the gh-pages
> > > branch from apache/incubator-livy plus a clean up commit leaving only
> the
> > > website code.
> > >
> > > @Luciano: I added you as a contributor to my repo so you can do
> whatever
> > > you need to copy it to apache/incubator-livy-website
> > >
> > > @Everyone please look through my updates commit. There's still more to
> > > add, but I believe for a first push and initial website it's good.
> > >
> > > Things I addressed:
> > > - Updating the template for the Livy project (instead of the default
> > > template values)
> > > - Added the content from livy.io and the GitHub wiki page
> > > - Various html/css tweaking for my personal sanity
> > >
> > > Some future things to address that I didn't tackle in my initial
> commit:
> > > - Adding the API Docs and Examples from the README
> > > - Fine tuning of the Website content for professionalism and accuracy,
> I
> > > did my best here but we should continue to clean up the site more
> > > - New Livy logo. Our Current Logo is not that great moving forward and
> I
> > > personally believe we should replace it. On this front I'm working to
> > pitch
> > > a new logo here on the dev list soon.
> > >
> > >
> > > *Alex Bozarth*
> > > Software Engineer
> > > Spark Technology Center
> > > --
> > > *E-mail:* *ajboz...@us.ibm.com* 
> > > *GitHub: *

Re: Apologies

[Luciano Resende]

All seems to be resolved now:

https://github.com/apache/incubator-livy-website

On Wed, Jul 19, 2017 at 6:38 PM, Luciano Resende 
wrote:

> I did a little mistake while pushing the website, will fix it soon.
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Another approach for Livy Website

[Luciano Resende]

After my little mistake, a pushing from different local repositry, things
are fixed and it should be ready now:

https://github.com/apache/incubator-livy-website

Thanks, Alex and others for the patience getting this ready.


On Wed, Jul 19, 2017 at 5:20 PM, Alex Bozarth  wrote:

> Thanks Jerry,
>
> @Luciano if the code looks good to you can you do copy? I'll follow up by
> opening a few PRs to move the Docs out of the README into the website once
> you've finished the copy.
>
>
> *Alex Bozarth*
> Software Engineer
> Spark Technology Center
> --
> *E-mail:* *ajboz...@us.ibm.com* 
> *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
>
>
> 505 Howard Street
> San Francisco, CA 94105
> United States
>
>
>
> [image: Inactive hide details for Saisai Shao ---07/19/2017 05:17:12
> PM---Hi Alex, if think the changes are pretty ready, you can creat]Saisai
> Shao ---07/19/2017 05:17:12 PM---Hi Alex, if think the changes are pretty
> ready, you can create a PR to incubator-livy-website.
>
> From: Saisai Shao 
> To: dev@livy.incubator.apache.org
> Date: 07/19/2017 05:17 PM
> Subject: Re: Another approach for Livy Website
> --
>
>
>
> Hi Alex, if think the changes are pretty ready, you can create a PR  to
> incubator-livy-website.
>
> Thanks
> Jerry
>
> On Mon, Jul 17, 2017 at 6:12 PM, Alex Bozarth  wrote:
>
> > I have a personal GitHub repo all ready to go:
> > https://github.com/ajbozarth/incubator-livy-website
> >
> > The master branch is a fork of apache/apache-website-template plus my
> > Livy update commit.
> > The repo also includes an old-site branch with a copy of the gh-pages
> > branch from apache/incubator-livy plus a clean up commit leaving only the
> > website code.
> >
> > @Luciano: I added you as a contributor to my repo so you can do whatever
> > you need to copy it to apache/incubator-livy-website
> >
> > @Everyone please look through my updates commit. There's still more to
> > add, but I believe for a first push and initial website it's good.
> >
> > Things I addressed:
> > - Updating the template for the Livy project (instead of the default
> > template values)
> > - Added the content from livy.io and the GitHub wiki page
> > - Various html/css tweaking for my personal sanity
> >
> > Some future things to address that I didn't tackle in my initial commit:
> > - Adding the API Docs and Examples from the README
> > - Fine tuning of the Website content for professionalism and accuracy, I
> > did my best here but we should continue to clean up the site more
> > - New Livy logo. Our Current Logo is not that great moving forward and I
> > personally believe we should replace it. On this front I'm working to
> pitch
> > a new logo here on the dev list soon.
> >
> >
> > *Alex Bozarth*
> > Software Engineer
> > Spark Technology Center
> > --
> > *E-mail:* *ajboz...@us.ibm.com* 
> > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
> >
> >
> > 505 Howard Street
> > San Francisco, CA 94105
> > United States
> >
> >
> >
> > [image: Inactive hide details for "Alex Bozarth" ---07/17/2017 01:13:44
> > PM---If that's the best way then I'll set up a fork with all my]"Alex
> > Bozarth" ---07/17/2017 01:13:44 PM---If that's the best way then I'll set
> > up a fork with all my previous suggestions and once my initial
> >
> > From: "Alex Bozarth" 
> > To: dev@livy.incubator.apache.org
> > Date: 07/17/2017 01:13 PM
> > Subject: Re: Another approach for Livy Website
> > --
> >
> >
> >
> > If that's the best way then I'll set up a fork with all my previous
> > suggestions and once my initial Livy website code is ready I'll post a
> link
> > here for review.
> >
> > *Alex Bozarth*
> > Software Engineer
> > Spark Technology Center
> > --
> > *E-mail:* *ajboz...@us.ibm.com* 
> > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
> >
> >
> > 505 Howard Street
> > San Francisco, CA 94105
> > United States
> >
> >
> >
> > Luciano Resende ---07/17/2017 01:07:08 PM---Great Alex, Once you have the
> > fork ok, please ask us to do a quick review and probably
> >
> > From: Luciano Resende 
> > To: dev@livy.incubator.apache.org
>

Apologies

[Luciano Resende]

I did a little mistake while pushing the website, will fix it soon.

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Another approach for Livy Website

[Luciano Resende]

 the history.
> >
> > On Thu, Jul 13, 2017 at 2:12 PM, Alex Bozarth 
> wrote:
> >
> > > I don't have a problem with it but given commits to branches aren't
> given
> > > credit in the master branch I'd say if we went with the template we
> > should
> > > just start from scratch and forget the history.
> > >
> > > On the note of starting from scratch, I support the idea and am willing
> > to
> > > personally take on the task of filling out the template with our
> current
> > > content. I've already written down a list of current content from the
> > > website, wiki, and README that makes sense to put in the webpage and
> was
> > > planning on putting in a JIRA once the JIRA migrated but I can share it
> > > here if desired.
> > >
> > >
> > > *Alex Bozarth*
> > > Software Engineer
> > > Spark Technology Center
> > > --
> > > *E-mail:* *ajboz...@us.ibm.com* 
> > > *GitHub: **github.com/ajbozarth* <*https://github.com/ajbozarth*
> > <https://github.com/ajbozarth>>
> > >
> > >
> > > 505 Howard Street
> > > San Francisco, CA 94105
> > > United States
> > >
> > >
> > >
> > > [image: Inactive hide details for Saisai Shao ---07/13/2017 01:57:11
> > > PM---It's fine for me. Not sure if other guys have additional
> conc]Saisai
> > > Shao ---07/13/2017 01:57:11 PM---It's fine for me. Not sure if other
> guys
> > > have additional concern. On Thu, Jul 13, 2017 at 1:52 PM, L
> > >
> > > From: Saisai Shao 
> > > To: dev@livy.incubator.apache.org
> > > Date: 07/13/2017 01:57 PM
> > > Subject: Re: Another approach for Livy Website
> > > --
> >
> > >
> > >
> > >
> > > It's fine for me. Not sure if other guys have additional concern.
> > >
> > > On Thu, Jul 13, 2017 at 1:52 PM, Luciano Resende  >
> > > wrote:
> > >
> > > > I think we could fork the template repository, and try to push the
> > > current
> > > > Livy website as a branch (e.g. original_website) ? That should
> resolve
> > > the
> > > > current concerns about history/credits.
> > > >
> > > > On Thu, Jul 13, 2017 at 1:45 PM, Saisai Shao  >
> > > > wrote:
> > > >
> > > > > I think this is great. Looking from the previous thread our major
> > > concern
> > > > > is to keep the contribution history/credits, will this break the
> > > > > history/credits? If not I think this probably be better.
> > > > >
> > > > > On Thu, Jul 13, 2017 at 1:33 PM, Luciano Resende <
> > luckbr1...@gmail.com
> > > >
> > > > > wrote:
> > > > >
> > > > > > While looking at the current website, it seems that there are
> only
> > > > three
> > > > > > pages based on pure HTML content.
> > > > > >
> > > > > > Should we look into actually creating a new website from scratch,
> > > based
> > > > > on
> > > > > > Jekkyl, similar to what a few of the other projects are using
> (e.g.
> > > > > Spark,
> > > > > > Bahir, SystemML, etc).
> > > > > >
> > > > > > If we choose this approach, there is already a template
> available (
> > > > > >
> > *https://github.com/apache/apache-website-template*
> > <https://github.com/apache/apache-website-template>) that follows most
> >
> > > > of
> > > > > > the
> > > > > > Apache Policy and has most of the structure for pages like
> > download,
> > > > > > community, etc. and we will only need to change model and update
> > > > content
> > > > > > but in the long run will make it easier for the community to
> > > contribute
> > > > > and
> > > > > > extend the website much simpler.
> > > > > >
> > > > > > Thoughts ?
> > > > > >
> > > > > > --
> > > > > > Luciano Resende
> > > > > >
> > *http://twitter.com/lresende1975* <http://twitter.com/lresende1975>
> >
> > > > > > *http://lresende.blogspot.com/* <http://lresende.blogspot.com/>
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Luciano Resende
> > > > *http://twitter.com/lresende1975* <http://twitter.com/lresende1975>
> > > > *http://lresende.blogspot.com/* <http://lresende.blogspot.com/>
> > > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> >
>
>
>
>


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Another approach for Livy Website

[Luciano Resende]

I think we could fork the template repository, and try to push the current
Livy website as a branch (e.g. original_website) ? That should resolve the
current concerns about history/credits.

On Thu, Jul 13, 2017 at 1:45 PM, Saisai Shao  wrote:

> I think this is great. Looking from the previous thread our major concern
> is to keep the contribution history/credits, will this break the
> history/credits? If not I think this probably be better.
>
> On Thu, Jul 13, 2017 at 1:33 PM, Luciano Resende 
> wrote:
>
> > While looking at the current website, it seems that there are only three
> > pages based on pure HTML content.
> >
> > Should we look into actually creating a new website from scratch, based
> on
> > Jekkyl, similar to what a few of the other projects are using (e.g.
> Spark,
> > Bahir, SystemML, etc).
> >
> > If we choose this approach, there is already a template available (
> > https://github.com/apache/apache-website-template) that follows most of
> > the
> > Apache Policy and has most of the structure for pages like download,
> > community, etc. and we will only need to change model and update content
> > but in the long run will make it easier for the community to contribute
> and
> > extend the website much simpler.
> >
> > Thoughts ?
> >
> > --
> > Luciano Resende
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
> >
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Another approach for Livy Website

[Luciano Resende]

While looking at the current website, it seems that there are only three
pages based on pure HTML content.

Should we look into actually creating a new website from scratch, based on
Jekkyl, similar to what a few of the other projects are using (e.g. Spark,
Bahir, SystemML, etc).

If we choose this approach, there is already a template available (
https://github.com/apache/apache-website-template) that follows most of the
Apache Policy and has most of the structure for pages like download,
community, etc. and we will only need to change model and update content
but in the long run will make it easier for the community to contribute and
extend the website much simpler.

Thoughts ?

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Feedback needed: Inital website import with move to apache git

[Luciano Resende]

Please take a quick look at the attempt to import only the website history
(looks like Jon's commit failed to import):

https://github.com/lresende/incubator-livy-website-temp

If this looks ok, I can push to Apache website master

On Wed, Jul 12, 2017 at 12:02 PM, Alex Bozarth  wrote:

> Thanks Marcelo, that's a great alternative. Since the website does only
> consist of 15 total additive commits that strategy would work. Since I'm
> not a committer I'm not sure how simple that process is for an apache git
> repo. @Luciano, is this something possible?
>
>
> *Alex Bozarth*
> Software Engineer
> Spark Technology Center
> --
> *E-mail:* *ajboz...@us.ibm.com* 
> *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
>
>
> 505 Howard Street
> San Francisco, CA 94105
> United States
>
>
>
> [image: Inactive hide details for Marcelo Vanzin ---07/12/2017 11:54:11
> AM---On Wed, Jul 12, 2017 at 11:44 AM, Alex Bozarth  Vanzin ---07/12/2017 11:54:11 AM---On Wed, Jul 12, 2017 at 11:44 AM, Alex
> Bozarth  wrote: > The actual website cod
>
> From: Marcelo Vanzin 
> To: dev@livy.incubator.apache.org
> Date: 07/12/2017 11:54 AM
> Subject: Re: Feedback needed: Inital website import with move to apache
> git
> --
>
>
>
> On Wed, Jul 12, 2017 at 11:44 AM, Alex Bozarth 
> wrote:
> > The actual website code was written by @jkestelyn
> > through 13 commits on top of the branch of livy (plus an initial commit
> by
> > Kostas Sakellis and a later bug fix by Jon Alter).
>
> If that's the case, it should be possible to use "git format-patch" to
> create separate patch files for each of those commits, then use "git
> am" to apply those patches to the other repo, right?
>
> There might be some manual work to make things work (e.g. if the
> commits touch files that exist in the livy repo, instead of being
> purely additive), but it shouldn't be hard.
>
> Another option is to add the livy repo as a remote in your local clone
> of the web site's repo, and use "git cherry-pick", and resolve
> conflicts. Given it's not that many patches, it shouldn't be that hard
> either.
>
> --
> Marcelo
>
>
>
>
>


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Livy Incubator setup progress

[Luciano Resende]

We have started making some progress on the infrstructure setup for Livy as
an Apache Incubator project. The mailling lists and source git repository
is already available, and we are in the process of migrating previous JIRA
issues and the website.

Available mailing lists :

u...@livy.incubator.apache.org
dev@livy.incubator.apache.org
iss...@livy.incubator.apache.org
revi...@livy.incubator.apache.org
comm...@livy.incubator.apache.org

To subscribe, add -subscribe to the list you want to subscribe (e.g.
dev-subscr...@livy.incubator.apache.org

Git repository

https://github.com/apache/incubator-livy
https://github.com/apache/incubator-livy-website


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/