Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-09-07 Thread Elek, Marton
Thanks all the positive feedback. I just uploaded the new site to the new repository: https://gitbox.apache.org/repos/asf/hadoop-site.git (asf-site branch) It contains: 1. Same content, new layout. (source files of the site) 2. The rendered content under /content together with all the

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-09-04 Thread Arpit Agarwal
Requested a new git repo for the site: https://gitbox.apache.org/repos/asf/hadoop-site.git On 9/4/18, 1:33 PM, "Mingliang Liu" wrote: It might be late but I'm +1 on the new site and transition proposal. Thanks Marton. On Fri, Aug 31, 2018 at 1:07 AM Elek, Marton wrote:

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-09-04 Thread Mingliang Liu
It might be late but I'm +1 on the new site and transition proposal. Thanks Marton. On Fri, Aug 31, 2018 at 1:07 AM Elek, Marton wrote: > Bumping this thread at last time. > > I have the following proposal: > > 1. I will request a new git repository hadoop-site.git and import the > new site to

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-09-02 Thread Rohith Sharma K S
during a new > release. > >> And if something would be missed, there could be displayed multiple > "2.7" > >> menu item (one for 2.7.3 and for 2.7.4). So the current method is not so > >> nice, but much more bug-safe. > >> > >> I prefe

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-09-02 Thread Sunil G
+1. Looks really good. - Sunil On Mon, Sep 3, 2018 at 10:51 AM Vinayakumar B wrote: > +1, New site looks great. > > Just one nit in README > '--refresh' flag for hugo server no longer available. > > -Vinay > > On Mon, 3 Sep 2018, 10:21 am Shashikant Banerjee, < > sbaner...@hortonworks.com> >

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-09-02 Thread Vinayakumar B
+1, New site looks great. Just one nit in README '--refresh' flag for hugo server no longer available. -Vinay On Mon, 3 Sep 2018, 10:21 am Shashikant Banerjee, wrote: > +1 > > Thanks > Shashi > > On 9/3/18, 9:23 AM, "Mukul Kumar Singh" wrote: > > +1, Thanks for working on this Marton. >

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-09-02 Thread Shashikant Banerjee
+1 Thanks Shashi On 9/3/18, 9:23 AM, "Mukul Kumar Singh" wrote: +1, Thanks for working on this Marton. -Mukul On 03/09/18, 9:02 AM, "John Zhuge" wrote: +1 Like the new site. On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang wrote:

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-09-02 Thread Mukul Kumar Singh
+1, Thanks for working on this Marton. -Mukul On 03/09/18, 9:02 AM, "John Zhuge" wrote: +1 Like the new site. On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang wrote: > That's really nice, +1. > > -- > Weiwei > > On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-09-02 Thread John Zhuge
+1 Like the new site. On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang wrote: > That's really nice, +1. > > -- > Weiwei > > On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan wrote: > > > +1, thanks for working on this, Marton! > > > > Best, > > Wangda > > > > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-08-31 Thread Wangda Tan
+1, thanks for working on this, Marton! Best, Wangda On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal wrote: > +1 > > Thanks for initiating this Marton. > > > On 8/31/18, 1:07 AM, "Elek, Marton" wrote: > > Bumping this thread at last time. > > I have the following proposal: > > 1.

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-08-31 Thread Arpit Agarwal
+1 Thanks for initiating this Marton. On 8/31/18, 1:07 AM, "Elek, Marton" wrote: Bumping this thread at last time. I have the following proposal: 1. I will request a new git repository hadoop-site.git and import the new site to there (which has exactly the same

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-08-31 Thread Brahma Reddy Battula
+1 It’s better to new version link in old version. Brahma Reddy Battula On Fri, Aug 31, 2018 at 9:59 PM, Sangjin Lee wrote: > +1. Thanks for the work, Marton! > > On Fri, Aug 31, 2018 at 8:37 AM Vinod Kumar Vavilapalli < > vino...@apache.org> > wrote: > > > Is there no way to host the new

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-08-31 Thread Sangjin Lee
+1. Thanks for the work, Marton! On Fri, Aug 31, 2018 at 8:37 AM Vinod Kumar Vavilapalli wrote: > Is there no way to host the new site and the old site concurrently? And > link back & forth? > > +Vinod > > > > On Aug 31, 2018, at 1:07 AM, Elek, Marton wrote: > > > > Bumping this thread at last

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-08-31 Thread Vinod Kumar Vavilapalli
Is there no way to host the new site and the old site concurrently? And link back & forth? +Vinod > On Aug 31, 2018, at 1:07 AM, Elek, Marton wrote: > > Bumping this thread at last time. > > I have the following proposal: > > 1. I will request a new git repository hadoop-site.git and

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-08-31 Thread larry mccay
+1 from me On Fri, Aug 31, 2018, 5:30 AM Steve Loughran wrote: > > > > On 31 Aug 2018, at 09:07, Elek, Marton wrote: > > > > Bumping this thread at last time. > > > > I have the following proposal: > > > > 1. I will request a new git repository hadoop-site.git and import the > new site to

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-08-31 Thread Steve Loughran
> On 31 Aug 2018, at 09:07, Elek, Marton wrote: > > Bumping this thread at last time. > > I have the following proposal: > > 1. I will request a new git repository hadoop-site.git and import the new > site to there (which has exactly the same content as the existing site). > > 2. I will

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-08-31 Thread Elek, Marton
Bumping this thread at last time. I have the following proposal: 1. I will request a new git repository hadoop-site.git and import the new site to there (which has exactly the same content as the existing site). 2. I will ask infra to use the new repository as the source of

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-06-21 Thread Elek, Marton
Thank you very much to bump up this thread. About [2]: (Just for the clarification) the content of the proposed website is exactly the same as the old one. About [1]. I believe that the "mvn site" is perfect for the documentation but for website creation there are more simple and

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-06-20 Thread Vinod Kumar Vavilapalli
Got pinged about this offline. Thanks for keeping at it, Marton! I think there are two road-blocks here (1) Is the mechanism using which the website is built good enough - mvn-site / hugo etc? (2) Is the new website good enough? For (1), I just think we need more committer attention and get

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-02-16 Thread Elek, Marton
Hi, I would like to bump this thread up. TLDR; There is a proposed version of a new hadoop site which is available from here: https://elek.github.io/hadoop-site-proposal/ and https://issues.apache.org/jira/browse/HADOOP-14163 Please let me know what you think about it. Longer version:

Re: HADOOP-14163 proposal for new hadoop.apache.org

2017-08-16 Thread Akira Ajisaka
Thanks a lot! First I will work on the 1. and 2. in HADOOP-14163. On 2017/08/09 5:03, Allen Wittenauer wrote: On Aug 8, 2017, at 12:36 AM, Akira Ajisaka wrote: Now I'm okay with not creating another repo. I'm thinking the following procedures may work: 1. Create

Re: HADOOP-14163 proposal for new hadoop.apache.org

2017-08-08 Thread Allen Wittenauer
Something else to consider. The main hadoop repo has precommit support. I could easily see a quick and dirty maven pom.xml and dockerfile put in place to build the website against “patches” uploaded to JIRA or github. - To

Re: HADOOP-14163 proposal for new hadoop.apache.org

2017-08-08 Thread Allen Wittenauer
> On Aug 8, 2017, at 12:36 AM, Akira Ajisaka wrote: > > Now I'm okay with not creating another repo. > I'm thinking the following procedures may work: > > 1. Create ./asf-site directory > 2. Add the content of https://github.com/elek/hadoop-site-proposal to the >

Re: HADOOP-14163 proposal for new hadoop.apache.org

2017-08-08 Thread Akira Ajisaka
Thanks Allen for the comment. Yes, it can be done without creating another git repo. In the near future, I'd like to enable CI job to push the site to asf-site branch automatically when the site source is changed. If we have a separate repository for web site, Pro: CI job can detect the change

Re: HADOOP-14163 proposal for new hadoop.apache.org

2017-08-07 Thread Allen Wittenauer
> On Aug 7, 2017, at 3:53 AM, Akira Ajisaka wrote: > > > I'll ask INFRA to create a git repository if there are no objections. There's no need to create a git repo. They just need to know to pull the website from the asf-site branch.

Re: HADOOP-14163 proposal for new hadoop.apache.org

2017-08-07 Thread Akira Ajisaka
ed we can submit new patches (hopefully against a git branch) in the normal way and further improve the site. From: Owen O'Malley <omal...@apache.org> Sent: Monday, March 13, 2017 6:15 PM To: Marton Elek Cc: common-dev@hadoop.apache.org Subject: Re:

Re: HADOOP-14163 proposal for new hadoop.apache.org

2017-03-24 Thread Andrew Wang
___________________ > From: Owen O'Malley <omal...@apache.org> > Sent: Monday, March 13, 2017 6:15 PM > To: Marton Elek > Cc: common-dev@hadoop.apache.org > Subject: Re: HADOOP-14163 proposal for new hadoop.apache.org > > Thanks for addressing

Re: HADOOP-14163 proposal for new hadoop.apache.org

2017-03-24 Thread Marton Elek
Monday, March 13, 2017 6:15 PM To: Marton Elek Cc: common-dev@hadoop.apache.org Subject: Re: HADOOP-14163 proposal for new hadoop.apache.org Thanks for addressing this. Getting rid of Hadoop's use of forrest is a good thing. In terms of content, the documentation links should be sorted by number with

Re: HADOOP-14163 proposal for new hadoop.apache.org

2017-03-13 Thread Owen O'Malley
Thanks for addressing this. Getting rid of Hadoop's use of forrest is a good thing. In terms of content, the documentation links should be sorted by number with only the latest from each minor release line (eg. 3.0, 2.7, 2.6). The download page points to the mirrors for checksums and signatures.