So it sound like what we want to do is "fork"
apache/apache-website-template into the master branch of
apache/incubator-livy-website then also move the gh-pages branch out of
apache/incubator-livy into apache/incubator-livy-website as well. Unless
there's objection/misunderstanding Luciano, Jerry and I agree on that path
forward.
After these steps happen I will open PRs to update the template with Livy
data (I already have this mostly ready) and, if we want to, can also open a
PR to clean up the old site branch so it doesn't include all the old livy
code, just the old website code.
Alex Bozarth
Software Engineer
Spark Technology Center
E-mail: [email protected]
GitHub: github.com/ajbozarth
505 Howard
Street
San Francisco, CA
94105
United
States
From: Saisai Shao <[email protected]>
To: [email protected]
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, this is much easier for maintaining
and updating compared to directly editing on html files. We can move on the
progress unless someone strongly oppose this way.
Thanks
Jerry
On Fri, Jul 14, 2017 at 10:23 AM, Alex Bozarth <[email protected]> wrote:
> Just an update so there no duplicate work. I forked the template Luciano
> mentioned yesterday and have been slowly updating it and filling it out
> with some of the current content. If/Once we decide to use template I
> should have a solid initial PR ready that will update it for Livy.
>
>
> *Alex Bozarth*
> Software Engineer
> Spark Technology Center
> ------------------------------
> *E-mail:* *[email protected]* <[email protected]>
> *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/13/2017 02:27:50
> PM---The issue with that though is by using the template we pla]"Alex
> Bozarth" ---07/13/2017 02:27:50 PM---The issue with that though is by
using
> the template we plan to not use the current site code, so imp
>
> From: "Alex Bozarth" <[email protected]>
> To: [email protected]
> 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 replace
it
> doesn't make sense to me. Though if it's not against the Apache
guidelines
> we could always leave the gh-pages branch in the main repo for prior
credit
> and start from the template in the website repo. I'm not sure what the
> apache guidelines are for branches, we do have a few junk branches in the
> repo currently.
>
> *Alex Bozarth*
> Software Engineer
> Spark Technology Center
> ------------------------------
> *E-mail:* *[email protected]* <[email protected]>
> *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
>
>
> 505 Howard Street
> San Francisco, CA 94105
> United States
>
>
>
> Saisai Shao ---07/13/2017 02:20:04 PM---Maybe we can apply the original
> changes to the master branch and then do the changes based on it to
>
> From: Saisai Shao <[email protected]>
> To: [email protected]
> Date: 07/13/2017 02:20 PM
> Subject: Re: Another approach for Livy Website
> ------------------------------
>
>
>
> Maybe we can apply the original changes to the master branch and then do
> the changes based on it to just keep the history.
>
> On Thu, Jul 13, 2017 at 2:12 PM, Alex Bozarth <[email protected]>
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:* *[email protected]* <[email protected]>
> > *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 <[email protected]>
> > To: [email protected]
> > 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 <[email protected]>
> > 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 <[email protected]>
> > > 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 <
> [email protected]
> > >
> > > > 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/>
> > >
> >
> >
> >
> >
>
>
>
>
>
>
