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 javadoc
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:
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
3.0), it requires multiple files update 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
+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>
> w
+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.
>
+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:
+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 wr
+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 >
+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. I
+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 cont
+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 sit
+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
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 import
+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 there
> 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 as
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
hadoop.apache.org
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
powerful
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 f
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:
Thi
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 ./asf-site directory
2. Add
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
> 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
> directory
> 3. Generate web pa
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
> 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.
--
e is migrated we can submit new patches (hopefully against a git branch)
in the normal way and further improve the site.
From: Owen O'Malley
Sent: Monday, March 13, 2017 6:15 PM
To: Marton Elek
Cc: common-dev@hadoop.apache.org
Subject: Re: HADO
.4). So the current method is not so
> nice, but much more bug-safe.
>
> I prefer to keep the current/content in this step (if possible) and if the
> site is migrated we can submit new patches (hopefully against a git branch)
> in the normal way and further improve the site.
>
&g
: 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 num
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.
29 matches
Mail list logo
