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 <ajboz...@us.ibm.com> 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* <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 <sai.sai.s...@gmail.com> > 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 <ajboz...@us.ibm.com> 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* <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" <ajboz...@us.ibm.com> > > 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* <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 <luckbr1...@gmail.com> > > To: dev@livy.incubator.apache.org > > Date: 07/17/2017 01:07 PM > > Subject: Re: Another approach for Livy Website > > ------------------------------ > > > > > > > > Great Alex, > > > > Once you have the fork ok, please ask us to do a quick review and > probably > > the best way to merge is to push a mirror of your fork to livy website > > repository. I can help with that when you are ready. > > > > On Mon, Jul 17, 2017 at 12:41 PM, Alex Bozarth <ajboz...@us.ibm.com> > > wrote: > > > > > 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:* *ajboz...@us.ibm.com* <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/14/2017 10:35:27 > > > AM---I think the way Luciano and you mentioned (using template > and]Saisai > > > Shao ---07/14/2017 10:35:27 AM---I think the way Luciano and you > > mentioned > > > (using template and put old code into another branch) is g > > > > > > From: Saisai Shao <sai.sai.s...@gmail.com> > > > 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, 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 <ajboz...@us.ibm.com> > > > 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:* *ajboz...@us.ibm.com* <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 "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" <ajboz...@us.ibm.com> > > > > 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 > > 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:* *ajboz...@us.ibm.com* <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 > > > > > > > > > > > > > > > > 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 <sai.sai.s...@gmail.com> > > > > To: dev@livy.incubator.apache.org > > > > 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 <ajboz...@us.ibm.com> > > > 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* <ajboz...@us.ibm.com> > > > > > *GitHub: **github.com/ajbozarth* <*https://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 <sai.sai.s...@gmail.com> > > > > > 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 < > > luckbr1...@gmail.com > > > > > > > > > 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 < > > sai.sai.s...@gmail.com > > > > > > > > > > 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* > > <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://twitter.com/lresende1975>> > > > > > > > > > > > > *http://lresende.blogspot.com/* < > > *http://lresende.blogspot.com/* <http://lresende.blogspot.com/>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Luciano Resende > > > > > > *http://twitter.com/lresende1975* < > > *http://twitter.com/lresende1975* <http://twitter.com/lresende1975>> > > > > > > *http://lresende.blogspot.com/* <*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/
