19/2017 08:11:12
>> PM---One pub-sub is configured, every time we commit to a "con]Luciano
>> Resende ---07/19/2017 08:11:12 PM---One pub-sub is configured, every time
>> we commit to a "content" branch, the website gets updated.
>>
>> From: Luciano Resende
h 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.
>
> O
nch, the website gets updated.
>
> From: Luciano Resende
> To: dev@livy.incubator.apache.org
> Date: 07/19/2017 08:11 PM
> Subject: Re: Another approach for Livy Website
> --
>
>
>
> One pub-sub is configured, every time we commit to a "cont
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
: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, 20
United
States
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
e, 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
> --
>
>
>
>
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 pat
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@li
7 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://gith
y]"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:
United
States
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 be
ink the way Luciano and you
mentioned
> (using template and put old code into another branch) is g
>
> From: Saisai Shao
> To: dev@livy.incubator.apache.org
> Date: 07/14/2017 10:35 AM
> Subject: Re: Another approach for Livy Website
> --
>
>
&
; (using template and put old code into another branch) is g
>
> From: Saisai Shao
> To: dev@livy.incubator.apache.org
> Date: 07/14/2017 10:35 AM
> Subject: Re: Another approach for Livy Website
> --
>
>
>
> I think the way Luciano and
United
States
From: Saisai Shao
To: dev@livy.incubator.apache.org
Date: 07/14/2017 10:35 AM
Subject:Re: Another approach for Livy Website
I think the way Luciano and you mentioned (using template and put old code
into another branch) is good for me, thi
ue with that though is by using
> the template we plan to not use the current site code, so imp
>
> From: "Alex Bozarth"
> To: dev@livy.incubator.apache.org
> Date: 07/13/2017 02:27 PM
> Subject: Re: Another approach for Livy Website
> --
&
From: "Alex Bozarth"
To: dev@livy.incubator.apache.org
Date: 07/13/2017 02:27 PM
Subject: Re: Another approach for Livy Website
The issue with that though is by using the template we plan to not use the
current site code, so importing it to only completely delete and
[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
sai 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
>
>
United
States
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:
&g
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 a
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 thr
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 s
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
24 matches
Mail list logo
