You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by Marton Elek <me...@hortonworks.com> on 2017/03/13 14:28:48 UTC
HADOOP-14163 proposal for new hadoop.apache.org
Hi,
In the previous thread the current forrest based hadoop site is identified as one of the pain points of the release process.
I created a new version of the site with exactly the same content.
As it uses newer site generator (hugo), now:
1. It’s enough to create one new markdown file per release, and all the documentation/download links will be automatically added.
2. It requires only one single binary to render.
A preview version is temporary hosted at
http://hadoop.anzix.net/
to make it easier to review.
For more details, you can check my comments on the issue https://issues.apache.org/jira/browse/HADOOP-14163
I would be thankful to get any feedback/review.
Cheers,
Marton
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Rohith Sharma K S <ro...@apache.org>.
+1 looks good
On Mon, 7 Aug 2017 at 16:23, Akira Ajisaka <aa...@apache.org> wrote:
> Hi folks,
>
> I'd like to create a separate git repository for the web site (now managed
> in svn).
> For more details, please see the discussion in
> https://issues.apache.org/jira/browse/HADOOP-14163.
>
> I'll ask INFRA to create a git repository if there are no objections.
>
> Thanks Marton Elek for the continuous work.
>
> Regards,
> Akira
>
> On 2017/03/25 3:35, Andrew Wang wrote:
> > Thanks again for working on this Marton!
> >
> > Based on my read of the blog post you linked, we should have the git
> branch
> > ready before asking infra to switch it over.
> >
> > I can do a more detailed review on the JIRA once you rev, and can help
> with
> > the INFRA ticket once it's ready. We'll also have to update BUILDING.txt
> > and the wiki instructions as part of this.
> >
> > Best,
> > Andrew
> >
> > On Fri, Mar 24, 2017 at 3:06 AM, Marton Elek <me...@hortonworks.com>
> wrote:
> >
> >>
> >>
> >> Thank you all of the feedbacks, I fixed all of them (except one, see the
> >> comment below) and updated the http://hadoop.anzix.net preview site.
> >>
> >> So the next steps:
> >>
> >> 0. Let me know if you have any comment about the latest version
> >>
> >> 1. I wait for the 2.8.0 announcement, and migrate the new announcement
> as
> >> well. (wouldn't like to complicate the 2.8.0 with the site change)
> >>
> >> 2. I like the suggestion of Owen to move the site to a specific git
> >> branch. I wouldn't like to pending on it if it's too much time, but if
> any
> >> of the commiters could pick it up, I would wait for it.
> >>
> >> I tested it, and seems to be easy:
> >>
> >> git svn clone https://svn.apache.org/repos/asf/hadoop/common/site/main
> >> cd main
> >> git remote add elek git@github.com:elek/hadoop.git
> >> git push elek master:asf-site
> >>
> >> According to the blog entry, an INFRA issue should be opened (I guess
> by a
> >> commiter or maybe a pmc member):
> >>
> >> https://blogs.apache.org/infra/entry/git_based_websites_available
> >>
> >> 3. After that I can submit the new site as a regular patch against the
> >> asf-site branch.
> >>
> >> 4. If it's merged, I can update the release wiki pages
> >>
> >> Marton
> >>
> >> ps:
> >>
> >> The only suggested item which is not implemented is the short version
> >> names in the documentation menu (2.7 instead of 2.7.3).
> >>
> >> I think there are two forces: usability of the site and the simplicity
> of
> >> the site generation. Ideally a new release could be added to the site as
> >> easy as possible (that was one of the motivation of the migration).
> >>
> >> While a new tag could be added to the header of the markdown files (eg:
> >> versionLine: 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.
> >>
> >> 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.
> >>
> >>
> >> ________________________________________
> >> From: Owen O'Malley <om...@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 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. It
> >> should use the direct links, such as
> >>
> >> https://dist.apache.org/repos/dist/release/hadoop/common/
> >> hadoop-2.7.3/hadoop-2.7.3-src.tar.gz.asc
> >> https://dist.apache.org/repos/dist/release/hadoop/common/
> >> hadoop-2.7.3/hadoop-2.7.3-src.tar.gz.mds
> >>
> >> Speaking of which, Hadoop's dist directory is huge and should be heavily
> >> pruned. We should probably take it down to just hadoop-2.6.5,
> hadoop-2.7.3,
> >> and hadoop-3.0.0-alpha2.
> >>
> >> You might also want to move us to git-pubsub so that we can use a
> branch in
> >> our source code git repository to publish the html. Typically this uses
> the
> >> asf-site branch.
> >>
> >> .. Owen
> >>
> >> On Mon, Mar 13, 2017 at 7:28 AM, Marton Elek <me...@hortonworks.com>
> >> wrote:
> >>
> >>>
> >>> Hi,
> >>>
> >>> In the previous thread the current forrest based hadoop site is
> >> identified
> >>> as one of the pain points of the release process.
> >>>
> >>> I created a new version of the site with exactly the same content.
> >>>
> >>> As it uses newer site generator (hugo), now:
> >>>
> >>> 1. It’s enough to create one new markdown file per release, and all the
> >>> documentation/download links will be automatically added.
> >>> 2. It requires only one single binary to render.
> >>>
> >>>
> >>> A preview version is temporary hosted at
> >>>
> >>> http://hadoop.anzix.net/
> >>>
> >>> to make it easier to review.
> >>>
> >>>
> >>> For more details, you can check my comments on the issue
> >>> https://issues.apache.org/jira/browse/HADOOP-14163
> >>>
> >>> I would be thankful to get any feedback/review.
> >>>
> >>> Cheers,
> >>> Marton
> >>>
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Allen Wittenauer <aw...@effectivemachines.com>.
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 unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Arpit Agarwal <aa...@hortonworks.com>.
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" <li...@gmail.com> 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 <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
> >
> > 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 tools.
> >
> > Hugo has more simple compared to jekyll. Just one binary, without
> > dependencies, works everywhere (mac, linux, windows)
> >
> > Hugo has much more powerful compared to "mvn site". Easier to create/use
> > more modern layout/theme, and easier to handle the content (for example
> > new release announcements could be generated as part of the release
> > process)
> >
> > I think it's very low risk to try out a new approach for the site (and
> > easy to rollback in case of problems)
> >
> > Marton
> >
> > ps: I just updated the patch/preview site with the recent releases:
> >
> > ***************************
> > * http://hadoop.anzix.net *
> > ***************************
> >
> > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> >> 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
> >> feedback rapidly and get it in.
> >>
> >> For (2), how about we do it in a different way in the interest of
> >> progress?
> >> - We create a hadoop.apache.org/new-site/ where this new site goes.
> >> - We then modify the existing web-site to say that there is a new
> >> site/experience that folks can click on a link and navigate to
> >> - As this new website matures and gets feedback & fixes, we finally
> >> pull the plug at a later point of time when we think we are good to go.
> >>
> >> Thoughts?
> >>
> >> +Vinod
> >>
> >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> >>>
> >>> 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:
> >>>
> >>> This thread started long time ago to use a more modern hadoop site:
> >>>
> >>> Goals were:
> >>>
> >>> 1. To make it easier to manage it (the release entries could be
> >>> created by a script as part of the release process)
> >>> 2. To use a better look-and-feel
> >>> 3. Move it out from svn to git
> >>>
> >>> I proposed to:
> >>>
> >>> 1. Move the existing site to git and generate it with hugo (which is
> >>> a single, standalone binary)
> >>> 2. Move both the rendered and source branches to git.
> >>> 3. (Create a jenkins job to generate the site automatically)
> >>>
> >>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
> >>> the documentation which is generated by mvn-site (as before)
> >>>
> >>>
> >>> I got multiple valuable feedback and I improved the proposed site
> >>> according to the comments. Allen had some concerns about the used
> >>> technologies (hugo vs. mvn-site) and I answered all the questions why
> >>> I think mvn-site is the best for documentation and hugo is best for
> >>> generating site.
> >>>
> >>>
> >>> I would like to finish this effort/jira: I would like to start a
> >>> discussion about using this proposed version and approach as a new
> >>> site of Apache Hadoop. Please let me know what you think.
> >>>
> >>>
> >>> Thanks a lot,
> >>> Marton
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
--
Mingliang Liu
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Arpit Agarwal <aa...@hortonworks.com>.
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" <li...@gmail.com> 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 <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
> >
> > 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 tools.
> >
> > Hugo has more simple compared to jekyll. Just one binary, without
> > dependencies, works everywhere (mac, linux, windows)
> >
> > Hugo has much more powerful compared to "mvn site". Easier to create/use
> > more modern layout/theme, and easier to handle the content (for example
> > new release announcements could be generated as part of the release
> > process)
> >
> > I think it's very low risk to try out a new approach for the site (and
> > easy to rollback in case of problems)
> >
> > Marton
> >
> > ps: I just updated the patch/preview site with the recent releases:
> >
> > ***************************
> > * http://hadoop.anzix.net *
> > ***************************
> >
> > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> >> 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
> >> feedback rapidly and get it in.
> >>
> >> For (2), how about we do it in a different way in the interest of
> >> progress?
> >> - We create a hadoop.apache.org/new-site/ where this new site goes.
> >> - We then modify the existing web-site to say that there is a new
> >> site/experience that folks can click on a link and navigate to
> >> - As this new website matures and gets feedback & fixes, we finally
> >> pull the plug at a later point of time when we think we are good to go.
> >>
> >> Thoughts?
> >>
> >> +Vinod
> >>
> >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> >>>
> >>> 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:
> >>>
> >>> This thread started long time ago to use a more modern hadoop site:
> >>>
> >>> Goals were:
> >>>
> >>> 1. To make it easier to manage it (the release entries could be
> >>> created by a script as part of the release process)
> >>> 2. To use a better look-and-feel
> >>> 3. Move it out from svn to git
> >>>
> >>> I proposed to:
> >>>
> >>> 1. Move the existing site to git and generate it with hugo (which is
> >>> a single, standalone binary)
> >>> 2. Move both the rendered and source branches to git.
> >>> 3. (Create a jenkins job to generate the site automatically)
> >>>
> >>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
> >>> the documentation which is generated by mvn-site (as before)
> >>>
> >>>
> >>> I got multiple valuable feedback and I improved the proposed site
> >>> according to the comments. Allen had some concerns about the used
> >>> technologies (hugo vs. mvn-site) and I answered all the questions why
> >>> I think mvn-site is the best for documentation and hugo is best for
> >>> generating site.
> >>>
> >>>
> >>> I would like to finish this effort/jira: I would like to start a
> >>> discussion about using this proposed version and approach as a new
> >>> site of Apache Hadoop. Please let me know what you think.
> >>>
> >>>
> >>> Thanks a lot,
> >>> Marton
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
--
Mingliang Liu
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Arpit Agarwal <aa...@hortonworks.com>.
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" <li...@gmail.com> 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 <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
> >
> > 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 tools.
> >
> > Hugo has more simple compared to jekyll. Just one binary, without
> > dependencies, works everywhere (mac, linux, windows)
> >
> > Hugo has much more powerful compared to "mvn site". Easier to create/use
> > more modern layout/theme, and easier to handle the content (for example
> > new release announcements could be generated as part of the release
> > process)
> >
> > I think it's very low risk to try out a new approach for the site (and
> > easy to rollback in case of problems)
> >
> > Marton
> >
> > ps: I just updated the patch/preview site with the recent releases:
> >
> > ***************************
> > * http://hadoop.anzix.net *
> > ***************************
> >
> > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> >> 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
> >> feedback rapidly and get it in.
> >>
> >> For (2), how about we do it in a different way in the interest of
> >> progress?
> >> - We create a hadoop.apache.org/new-site/ where this new site goes.
> >> - We then modify the existing web-site to say that there is a new
> >> site/experience that folks can click on a link and navigate to
> >> - As this new website matures and gets feedback & fixes, we finally
> >> pull the plug at a later point of time when we think we are good to go.
> >>
> >> Thoughts?
> >>
> >> +Vinod
> >>
> >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> >>>
> >>> 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:
> >>>
> >>> This thread started long time ago to use a more modern hadoop site:
> >>>
> >>> Goals were:
> >>>
> >>> 1. To make it easier to manage it (the release entries could be
> >>> created by a script as part of the release process)
> >>> 2. To use a better look-and-feel
> >>> 3. Move it out from svn to git
> >>>
> >>> I proposed to:
> >>>
> >>> 1. Move the existing site to git and generate it with hugo (which is
> >>> a single, standalone binary)
> >>> 2. Move both the rendered and source branches to git.
> >>> 3. (Create a jenkins job to generate the site automatically)
> >>>
> >>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
> >>> the documentation which is generated by mvn-site (as before)
> >>>
> >>>
> >>> I got multiple valuable feedback and I improved the proposed site
> >>> according to the comments. Allen had some concerns about the used
> >>> technologies (hugo vs. mvn-site) and I answered all the questions why
> >>> I think mvn-site is the best for documentation and hugo is best for
> >>> generating site.
> >>>
> >>>
> >>> I would like to finish this effort/jira: I would like to start a
> >>> discussion about using this proposed version and approach as a new
> >>> site of Apache Hadoop. Please let me know what you think.
> >>>
> >>>
> >>> Thanks a lot,
> >>> Marton
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
--
Mingliang Liu
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Arpit Agarwal <aa...@hortonworks.com>.
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" <li...@gmail.com> 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 <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
> >
> > 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 tools.
> >
> > Hugo has more simple compared to jekyll. Just one binary, without
> > dependencies, works everywhere (mac, linux, windows)
> >
> > Hugo has much more powerful compared to "mvn site". Easier to create/use
> > more modern layout/theme, and easier to handle the content (for example
> > new release announcements could be generated as part of the release
> > process)
> >
> > I think it's very low risk to try out a new approach for the site (and
> > easy to rollback in case of problems)
> >
> > Marton
> >
> > ps: I just updated the patch/preview site with the recent releases:
> >
> > ***************************
> > * http://hadoop.anzix.net *
> > ***************************
> >
> > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> >> 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
> >> feedback rapidly and get it in.
> >>
> >> For (2), how about we do it in a different way in the interest of
> >> progress?
> >> - We create a hadoop.apache.org/new-site/ where this new site goes.
> >> - We then modify the existing web-site to say that there is a new
> >> site/experience that folks can click on a link and navigate to
> >> - As this new website matures and gets feedback & fixes, we finally
> >> pull the plug at a later point of time when we think we are good to go.
> >>
> >> Thoughts?
> >>
> >> +Vinod
> >>
> >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> >>>
> >>> 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:
> >>>
> >>> This thread started long time ago to use a more modern hadoop site:
> >>>
> >>> Goals were:
> >>>
> >>> 1. To make it easier to manage it (the release entries could be
> >>> created by a script as part of the release process)
> >>> 2. To use a better look-and-feel
> >>> 3. Move it out from svn to git
> >>>
> >>> I proposed to:
> >>>
> >>> 1. Move the existing site to git and generate it with hugo (which is
> >>> a single, standalone binary)
> >>> 2. Move both the rendered and source branches to git.
> >>> 3. (Create a jenkins job to generate the site automatically)
> >>>
> >>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
> >>> the documentation which is generated by mvn-site (as before)
> >>>
> >>>
> >>> I got multiple valuable feedback and I improved the proposed site
> >>> according to the comments. Allen had some concerns about the used
> >>> technologies (hugo vs. mvn-site) and I answered all the questions why
> >>> I think mvn-site is the best for documentation and hugo is best for
> >>> generating site.
> >>>
> >>>
> >>> I would like to finish this effort/jira: I would like to start a
> >>> discussion about using this proposed version and approach as a new
> >>> site of Apache Hadoop. Please let me know what you think.
> >>>
> >>>
> >>> Thanks a lot,
> >>> Marton
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
--
Mingliang Liu
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Mingliang Liu <li...@gmail.com>.
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 <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
> >
> > 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 tools.
> >
> > Hugo has more simple compared to jekyll. Just one binary, without
> > dependencies, works everywhere (mac, linux, windows)
> >
> > Hugo has much more powerful compared to "mvn site". Easier to create/use
> > more modern layout/theme, and easier to handle the content (for example
> > new release announcements could be generated as part of the release
> > process)
> >
> > I think it's very low risk to try out a new approach for the site (and
> > easy to rollback in case of problems)
> >
> > Marton
> >
> > ps: I just updated the patch/preview site with the recent releases:
> >
> > ***************************
> > * http://hadoop.anzix.net *
> > ***************************
> >
> > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> >> 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
> >> feedback rapidly and get it in.
> >>
> >> For (2), how about we do it in a different way in the interest of
> >> progress?
> >> - We create a hadoop.apache.org/new-site/ where this new site goes.
> >> - We then modify the existing web-site to say that there is a new
> >> site/experience that folks can click on a link and navigate to
> >> - As this new website matures and gets feedback & fixes, we finally
> >> pull the plug at a later point of time when we think we are good to go.
> >>
> >> Thoughts?
> >>
> >> +Vinod
> >>
> >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> >>>
> >>> 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:
> >>>
> >>> This thread started long time ago to use a more modern hadoop site:
> >>>
> >>> Goals were:
> >>>
> >>> 1. To make it easier to manage it (the release entries could be
> >>> created by a script as part of the release process)
> >>> 2. To use a better look-and-feel
> >>> 3. Move it out from svn to git
> >>>
> >>> I proposed to:
> >>>
> >>> 1. Move the existing site to git and generate it with hugo (which is
> >>> a single, standalone binary)
> >>> 2. Move both the rendered and source branches to git.
> >>> 3. (Create a jenkins job to generate the site automatically)
> >>>
> >>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
> >>> the documentation which is generated by mvn-site (as before)
> >>>
> >>>
> >>> I got multiple valuable feedback and I improved the proposed site
> >>> according to the comments. Allen had some concerns about the used
> >>> technologies (hugo vs. mvn-site) and I answered all the questions why
> >>> I think mvn-site is the best for documentation and hugo is best for
> >>> generating site.
> >>>
> >>>
> >>> I would like to finish this effort/jira: I would like to start a
> >>> discussion about using this proposed version and approach as a new
> >>> site of Apache Hadoop. Please let me know what you think.
> >>>
> >>>
> >>> Thanks a lot,
> >>> Marton
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
--
Mingliang Liu
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Mingliang Liu <li...@gmail.com>.
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 <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
> >
> > 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 tools.
> >
> > Hugo has more simple compared to jekyll. Just one binary, without
> > dependencies, works everywhere (mac, linux, windows)
> >
> > Hugo has much more powerful compared to "mvn site". Easier to create/use
> > more modern layout/theme, and easier to handle the content (for example
> > new release announcements could be generated as part of the release
> > process)
> >
> > I think it's very low risk to try out a new approach for the site (and
> > easy to rollback in case of problems)
> >
> > Marton
> >
> > ps: I just updated the patch/preview site with the recent releases:
> >
> > ***************************
> > * http://hadoop.anzix.net *
> > ***************************
> >
> > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> >> 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
> >> feedback rapidly and get it in.
> >>
> >> For (2), how about we do it in a different way in the interest of
> >> progress?
> >> - We create a hadoop.apache.org/new-site/ where this new site goes.
> >> - We then modify the existing web-site to say that there is a new
> >> site/experience that folks can click on a link and navigate to
> >> - As this new website matures and gets feedback & fixes, we finally
> >> pull the plug at a later point of time when we think we are good to go.
> >>
> >> Thoughts?
> >>
> >> +Vinod
> >>
> >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> >>>
> >>> 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:
> >>>
> >>> This thread started long time ago to use a more modern hadoop site:
> >>>
> >>> Goals were:
> >>>
> >>> 1. To make it easier to manage it (the release entries could be
> >>> created by a script as part of the release process)
> >>> 2. To use a better look-and-feel
> >>> 3. Move it out from svn to git
> >>>
> >>> I proposed to:
> >>>
> >>> 1. Move the existing site to git and generate it with hugo (which is
> >>> a single, standalone binary)
> >>> 2. Move both the rendered and source branches to git.
> >>> 3. (Create a jenkins job to generate the site automatically)
> >>>
> >>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
> >>> the documentation which is generated by mvn-site (as before)
> >>>
> >>>
> >>> I got multiple valuable feedback and I improved the proposed site
> >>> according to the comments. Allen had some concerns about the used
> >>> technologies (hugo vs. mvn-site) and I answered all the questions why
> >>> I think mvn-site is the best for documentation and hugo is best for
> >>> generating site.
> >>>
> >>>
> >>> I would like to finish this effort/jira: I would like to start a
> >>> discussion about using this proposed version and approach as a new
> >>> site of Apache Hadoop. Please let me know what you think.
> >>>
> >>>
> >>> Thanks a lot,
> >>> Marton
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
--
Mingliang Liu
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by "Elek, Marton" <el...@apache.org>.
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 javadocs
(289003 file)
3. The old site (as suggested by Vinod. I added a link back to the old
site). https://hadoop.apache.org/old
Infra has already changed the pubsub script. The new site is live.
Please let me know if you see any problem...
I will update the wiki pages / release instruction very soon.
Thanks,
Marton
ps:
Please give me write permission to the OLD wiki
(https://wiki.apache.org/hadoop/), if you can. My username is MartonElek
Thanks a lot.
On 08/31/2018 10: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 content as the existing
> site).
>
> 2. I will ask infra to use the new repository as the source of
> hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
>>
>> 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 tools.
>>
>> Hugo has more simple compared to jekyll. Just one binary, without
>> dependencies, works everywhere (mac, linux, windows)
>>
>> Hugo has much more powerful compared to "mvn site". Easier to
>> create/use more modern layout/theme, and easier to handle the content
>> (for example new release announcements could be generated as part of
>> the release process)
>>
>> I think it's very low risk to try out a new approach for the site (and
>> easy to rollback in case of problems)
>>
>> Marton
>>
>> ps: I just updated the patch/preview site with the recent releases:
>>
>> ***************************
>> * http://hadoop.anzix.net *
>> ***************************
>>
>> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
>>> 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
>>> feedback rapidly and get it in.
>>>
>>> For (2), how about we do it in a different way in the interest of
>>> progress?
>>> - We create a hadoop.apache.org/new-site/ where this new site goes.
>>> - We then modify the existing web-site to say that there is a new
>>> site/experience that folks can click on a link and navigate to
>>> - As this new website matures and gets feedback & fixes, we finally
>>> pull the plug at a later point of time when we think we are good to go.
>>>
>>> Thoughts?
>>>
>>> +Vinod
>>>
>>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>>>
>>>> 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:
>>>>
>>>> This thread started long time ago to use a more modern hadoop site:
>>>>
>>>> Goals were:
>>>>
>>>> 1. To make it easier to manage it (the release entries could be
>>>> created by a script as part of the release process)
>>>> 2. To use a better look-and-feel
>>>> 3. Move it out from svn to git
>>>>
>>>> I proposed to:
>>>>
>>>> 1. Move the existing site to git and generate it with hugo (which is
>>>> a single, standalone binary)
>>>> 2. Move both the rendered and source branches to git.
>>>> 3. (Create a jenkins job to generate the site automatically)
>>>>
>>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
>>>> the documentation which is generated by mvn-site (as before)
>>>>
>>>>
>>>> I got multiple valuable feedback and I improved the proposed site
>>>> according to the comments. Allen had some concerns about the used
>>>> technologies (hugo vs. mvn-site) and I answered all the questions
>>>> why I think mvn-site is the best for documentation and hugo is best
>>>> for generating site.
>>>>
>>>>
>>>> I would like to finish this effort/jira: I would like to start a
>>>> discussion about using this proposed version and approach as a new
>>>> site of Apache Hadoop. Please let me know what you think.
>>>>
>>>>
>>>> Thanks a lot,
>>>> Marton
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Sunil G <su...@apache.org>.
+1. Looks really good.
- Sunil
On Mon, Sep 3, 2018 at 10:51 AM Vinayakumar B <vi...@apache.org>
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, <
> sbanerjee@hortonworks.com>
> wrote:
>
> > +1
> >
> > Thanks
> > Shashi
> >
> > On 9/3/18, 9:23 AM, "Mukul Kumar Singh" <ms...@hortonworks.com> wrote:
> >
> > +1, Thanks for working on this Marton.
> >
> > -Mukul
> >
> > On 03/09/18, 9:02 AM, "John Zhuge" <jo...@gmail.com> wrote:
> >
> > +1 Like the new site.
> >
> > On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang <ab...@gmail.com>
> > wrote:
> >
> > > That's really nice, +1.
> > >
> > > --
> > > Weiwei
> > >
> > > On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wheeleast@gmail.com
> >
> > wrote:
> > >
> > > > +1, thanks for working on this, Marton!
> > > >
> > > > Best,
> > > > Wangda
> > > >
> > > > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <
> > aagarwal@hortonworks.com
> > > >
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > Thanks for initiating this Marton.
> > > > >
> > > > >
> > > > > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org>
> 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 ask infra to use the new repository as the
> > source of
> > > > > hadoop.apache.org
> > > > >
> > > > > 3. I will sync manually all of the changes in the next
> > two months
> > > > back
> > > > > to the svn site from the git (release announcements,
> new
> > > committers)
> > > > >
> > > > > IN CASE OF ANY PROBLEM we can switch back to the svn
> > without any
> > > > > problem.
> > > > >
> > > > > If no-one objects within three days, I'll assume lazy
> > consensus and
> > > > > start with this plan. Please comment if you have
> > objections.
> > > > >
> > > > > Again: it allows immediate fallback at any time as svn
> > repo will be
> > > > > kept
> > > > > as is (+ I will keep it up-to-date in the next 2
> months)
> > > > >
> > > > > Thanks,
> > > > > Marton
> > > > >
> > > > >
> > > > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > > > > >
> > > > > > 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 tools.
> > > > > >
> > > > > > Hugo has more simple compared to jekyll. Just one
> > binary, without
> > > > > > dependencies, works everywhere (mac, linux, windows)
> > > > > >
> > > > > > Hugo has much more powerful compared to "mvn site".
> > Easier to
> > > > > create/use
> > > > > > more modern layout/theme, and easier to handle the
> > content (for
> > > > > example
> > > > > > new release announcements could be generated as part
> > of the
> > > release
> > > > > > process)
> > > > > >
> > > > > > I think it's very low risk to try out a new approach
> > for the site
> > > > > (and
> > > > > > easy to rollback in case of problems)
> > > > > >
> > > > > > Marton
> > > > > >
> > > > > > ps: I just updated the patch/preview site with the
> > recent
> > > releases:
> > > > > >
> > > > > > ***************************
> > > > > > * http://hadoop.anzix.net *
> > > > > > ***************************
> > > > > >
> > > > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli
> wrote:
> > > > > >> 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
> > > > > >> feedback rapidly and get it in.
> > > > > >>
> > > > > >> For (2), how about we do it in a different way in
> the
> > interest
> > > of
> > > > > >> progress?
> > > > > >> - We create a hadoop.apache.org/new-site/ where
> > this new site
> > > > > goes.
> > > > > >> - We then modify the existing web-site to say that
> > there is a
> > > > new
> > > > > >> site/experience that folks can click on a link and
> > navigate to
> > > > > >> - As this new website matures and gets feedback &
> > fixes, we
> > > > > finally
> > > > > >> pull the plug at a later point of time when we think
> > we are good
> > > > to
> > > > > go.
> > > > > >>
> > > > > >> Thoughts?
> > > > > >>
> > > > > >> +Vinod
> > > > > >>
> > > > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <
> > elek@apache.org>
> > > > wrote:
> > > > > >>>
> > > > > >>> 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:
> > > > > >>>
> > > > > >>> This thread started long time ago to use a more
> > modern hadoop
> > > > site:
> > > > > >>>
> > > > > >>> Goals were:
> > > > > >>>
> > > > > >>> 1. To make it easier to manage it (the release
> > entries could be
> > > > > >>> created by a script as part of the release process)
> > > > > >>> 2. To use a better look-and-feel
> > > > > >>> 3. Move it out from svn to git
> > > > > >>>
> > > > > >>> I proposed to:
> > > > > >>>
> > > > > >>> 1. Move the existing site to git and generate it
> > with hugo
> > > (which
> > > > > is
> > > > > >>> a single, standalone binary)
> > > > > >>> 2. Move both the rendered and source branches to
> git.
> > > > > >>> 3. (Create a jenkins job to generate the site
> > automatically)
> > > > > >>>
> > > > > >>> NOTE: this is just about forrest based
> > hadoop.apache.org, NOT
> > > > > about
> > > > > >>> the documentation which is generated by mvn-site
> (as
> > before)
> > > > > >>>
> > > > > >>>
> > > > > >>> I got multiple valuable feedback and I improved the
> > proposed
> > > site
> > > > > >>> according to the comments. Allen had some concerns
> > about the
> > > used
> > > > > >>> technologies (hugo vs. mvn-site) and I answered all
> > the
> > > questions
> > > > > why
> > > > > >>> I think mvn-site is the best for documentation and
> > hugo is best
> > > > > for
> > > > > >>> generating site.
> > > > > >>>
> > > > > >>>
> > > > > >>> I would like to finish this effort/jira: I would
> > like to start
> > > a
> > > > > >>> discussion about using this proposed version and
> > approach as a
> > > > new
> > > > > >>> site of Apache Hadoop. Please let me know what you
> > think.
> > > > > >>>
> > > > > >>>
> > > > > >>> Thanks a lot,
> > > > > >>> Marton
> > > > > >>>
> > > > > >>>
> > > > >
> > ---------------------------------------------------------------------
> > > > > >>> To unsubscribe, e-mail:
> > > common-dev-unsubscribe@hadoop.apache.org
> > > > > >>> For additional commands, e-mail:
> > > > common-dev-help@hadoop.apache.org
> > > > > >>>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > >
> > ---------------------------------------------------------------------
> > > > > >> To unsubscribe, e-mail:
> > > common-dev-unsubscribe@hadoop.apache.org
> > > > > >> For additional commands, e-mail:
> > > > common-dev-help@hadoop.apache.org
> > > > > >>
> > > > > >
> > > > > >
> > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail:
> > hdfs-dev-unsubscribe@hadoop.apache.org
> > > > > > For additional commands, e-mail:
> > hdfs-dev-help@hadoop.apache.org
> > > > >
> > > > >
> > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> > hdfs-dev-unsubscribe@hadoop.apache.org
> > > > > For additional commands, e-mail:
> > hdfs-dev-help@hadoop.apache.org
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Weiwei Yang
> > >
> >
> >
> > --
> > John
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> >
> >
> >
> >
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Sunil G <su...@apache.org>.
+1. Looks really good.
- Sunil
On Mon, Sep 3, 2018 at 10:51 AM Vinayakumar B <vi...@apache.org>
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, <
> sbanerjee@hortonworks.com>
> wrote:
>
> > +1
> >
> > Thanks
> > Shashi
> >
> > On 9/3/18, 9:23 AM, "Mukul Kumar Singh" <ms...@hortonworks.com> wrote:
> >
> > +1, Thanks for working on this Marton.
> >
> > -Mukul
> >
> > On 03/09/18, 9:02 AM, "John Zhuge" <jo...@gmail.com> wrote:
> >
> > +1 Like the new site.
> >
> > On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang <ab...@gmail.com>
> > wrote:
> >
> > > That's really nice, +1.
> > >
> > > --
> > > Weiwei
> > >
> > > On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wheeleast@gmail.com
> >
> > wrote:
> > >
> > > > +1, thanks for working on this, Marton!
> > > >
> > > > Best,
> > > > Wangda
> > > >
> > > > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <
> > aagarwal@hortonworks.com
> > > >
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > Thanks for initiating this Marton.
> > > > >
> > > > >
> > > > > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org>
> 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 ask infra to use the new repository as the
> > source of
> > > > > hadoop.apache.org
> > > > >
> > > > > 3. I will sync manually all of the changes in the next
> > two months
> > > > back
> > > > > to the svn site from the git (release announcements,
> new
> > > committers)
> > > > >
> > > > > IN CASE OF ANY PROBLEM we can switch back to the svn
> > without any
> > > > > problem.
> > > > >
> > > > > If no-one objects within three days, I'll assume lazy
> > consensus and
> > > > > start with this plan. Please comment if you have
> > objections.
> > > > >
> > > > > Again: it allows immediate fallback at any time as svn
> > repo will be
> > > > > kept
> > > > > as is (+ I will keep it up-to-date in the next 2
> months)
> > > > >
> > > > > Thanks,
> > > > > Marton
> > > > >
> > > > >
> > > > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > > > > >
> > > > > > 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 tools.
> > > > > >
> > > > > > Hugo has more simple compared to jekyll. Just one
> > binary, without
> > > > > > dependencies, works everywhere (mac, linux, windows)
> > > > > >
> > > > > > Hugo has much more powerful compared to "mvn site".
> > Easier to
> > > > > create/use
> > > > > > more modern layout/theme, and easier to handle the
> > content (for
> > > > > example
> > > > > > new release announcements could be generated as part
> > of the
> > > release
> > > > > > process)
> > > > > >
> > > > > > I think it's very low risk to try out a new approach
> > for the site
> > > > > (and
> > > > > > easy to rollback in case of problems)
> > > > > >
> > > > > > Marton
> > > > > >
> > > > > > ps: I just updated the patch/preview site with the
> > recent
> > > releases:
> > > > > >
> > > > > > ***************************
> > > > > > * http://hadoop.anzix.net *
> > > > > > ***************************
> > > > > >
> > > > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli
> wrote:
> > > > > >> 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
> > > > > >> feedback rapidly and get it in.
> > > > > >>
> > > > > >> For (2), how about we do it in a different way in
> the
> > interest
> > > of
> > > > > >> progress?
> > > > > >> - We create a hadoop.apache.org/new-site/ where
> > this new site
> > > > > goes.
> > > > > >> - We then modify the existing web-site to say that
> > there is a
> > > > new
> > > > > >> site/experience that folks can click on a link and
> > navigate to
> > > > > >> - As this new website matures and gets feedback &
> > fixes, we
> > > > > finally
> > > > > >> pull the plug at a later point of time when we think
> > we are good
> > > > to
> > > > > go.
> > > > > >>
> > > > > >> Thoughts?
> > > > > >>
> > > > > >> +Vinod
> > > > > >>
> > > > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <
> > elek@apache.org>
> > > > wrote:
> > > > > >>>
> > > > > >>> 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:
> > > > > >>>
> > > > > >>> This thread started long time ago to use a more
> > modern hadoop
> > > > site:
> > > > > >>>
> > > > > >>> Goals were:
> > > > > >>>
> > > > > >>> 1. To make it easier to manage it (the release
> > entries could be
> > > > > >>> created by a script as part of the release process)
> > > > > >>> 2. To use a better look-and-feel
> > > > > >>> 3. Move it out from svn to git
> > > > > >>>
> > > > > >>> I proposed to:
> > > > > >>>
> > > > > >>> 1. Move the existing site to git and generate it
> > with hugo
> > > (which
> > > > > is
> > > > > >>> a single, standalone binary)
> > > > > >>> 2. Move both the rendered and source branches to
> git.
> > > > > >>> 3. (Create a jenkins job to generate the site
> > automatically)
> > > > > >>>
> > > > > >>> NOTE: this is just about forrest based
> > hadoop.apache.org, NOT
> > > > > about
> > > > > >>> the documentation which is generated by mvn-site
> (as
> > before)
> > > > > >>>
> > > > > >>>
> > > > > >>> I got multiple valuable feedback and I improved the
> > proposed
> > > site
> > > > > >>> according to the comments. Allen had some concerns
> > about the
> > > used
> > > > > >>> technologies (hugo vs. mvn-site) and I answered all
> > the
> > > questions
> > > > > why
> > > > > >>> I think mvn-site is the best for documentation and
> > hugo is best
> > > > > for
> > > > > >>> generating site.
> > > > > >>>
> > > > > >>>
> > > > > >>> I would like to finish this effort/jira: I would
> > like to start
> > > a
> > > > > >>> discussion about using this proposed version and
> > approach as a
> > > > new
> > > > > >>> site of Apache Hadoop. Please let me know what you
> > think.
> > > > > >>>
> > > > > >>>
> > > > > >>> Thanks a lot,
> > > > > >>> Marton
> > > > > >>>
> > > > > >>>
> > > > >
> > ---------------------------------------------------------------------
> > > > > >>> To unsubscribe, e-mail:
> > > common-dev-unsubscribe@hadoop.apache.org
> > > > > >>> For additional commands, e-mail:
> > > > common-dev-help@hadoop.apache.org
> > > > > >>>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > >
> > ---------------------------------------------------------------------
> > > > > >> To unsubscribe, e-mail:
> > > common-dev-unsubscribe@hadoop.apache.org
> > > > > >> For additional commands, e-mail:
> > > > common-dev-help@hadoop.apache.org
> > > > > >>
> > > > > >
> > > > > >
> > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail:
> > hdfs-dev-unsubscribe@hadoop.apache.org
> > > > > > For additional commands, e-mail:
> > hdfs-dev-help@hadoop.apache.org
> > > > >
> > > > >
> > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> > hdfs-dev-unsubscribe@hadoop.apache.org
> > > > > For additional commands, e-mail:
> > hdfs-dev-help@hadoop.apache.org
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Weiwei Yang
> > >
> >
> >
> > --
> > John
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> >
> >
> >
> >
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Sunil G <su...@apache.org>.
+1. Looks really good.
- Sunil
On Mon, Sep 3, 2018 at 10:51 AM Vinayakumar B <vi...@apache.org>
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, <
> sbanerjee@hortonworks.com>
> wrote:
>
> > +1
> >
> > Thanks
> > Shashi
> >
> > On 9/3/18, 9:23 AM, "Mukul Kumar Singh" <ms...@hortonworks.com> wrote:
> >
> > +1, Thanks for working on this Marton.
> >
> > -Mukul
> >
> > On 03/09/18, 9:02 AM, "John Zhuge" <jo...@gmail.com> wrote:
> >
> > +1 Like the new site.
> >
> > On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang <ab...@gmail.com>
> > wrote:
> >
> > > That's really nice, +1.
> > >
> > > --
> > > Weiwei
> > >
> > > On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wheeleast@gmail.com
> >
> > wrote:
> > >
> > > > +1, thanks for working on this, Marton!
> > > >
> > > > Best,
> > > > Wangda
> > > >
> > > > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <
> > aagarwal@hortonworks.com
> > > >
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > Thanks for initiating this Marton.
> > > > >
> > > > >
> > > > > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org>
> 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 ask infra to use the new repository as the
> > source of
> > > > > hadoop.apache.org
> > > > >
> > > > > 3. I will sync manually all of the changes in the next
> > two months
> > > > back
> > > > > to the svn site from the git (release announcements,
> new
> > > committers)
> > > > >
> > > > > IN CASE OF ANY PROBLEM we can switch back to the svn
> > without any
> > > > > problem.
> > > > >
> > > > > If no-one objects within three days, I'll assume lazy
> > consensus and
> > > > > start with this plan. Please comment if you have
> > objections.
> > > > >
> > > > > Again: it allows immediate fallback at any time as svn
> > repo will be
> > > > > kept
> > > > > as is (+ I will keep it up-to-date in the next 2
> months)
> > > > >
> > > > > Thanks,
> > > > > Marton
> > > > >
> > > > >
> > > > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > > > > >
> > > > > > 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 tools.
> > > > > >
> > > > > > Hugo has more simple compared to jekyll. Just one
> > binary, without
> > > > > > dependencies, works everywhere (mac, linux, windows)
> > > > > >
> > > > > > Hugo has much more powerful compared to "mvn site".
> > Easier to
> > > > > create/use
> > > > > > more modern layout/theme, and easier to handle the
> > content (for
> > > > > example
> > > > > > new release announcements could be generated as part
> > of the
> > > release
> > > > > > process)
> > > > > >
> > > > > > I think it's very low risk to try out a new approach
> > for the site
> > > > > (and
> > > > > > easy to rollback in case of problems)
> > > > > >
> > > > > > Marton
> > > > > >
> > > > > > ps: I just updated the patch/preview site with the
> > recent
> > > releases:
> > > > > >
> > > > > > ***************************
> > > > > > * http://hadoop.anzix.net *
> > > > > > ***************************
> > > > > >
> > > > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli
> wrote:
> > > > > >> 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
> > > > > >> feedback rapidly and get it in.
> > > > > >>
> > > > > >> For (2), how about we do it in a different way in
> the
> > interest
> > > of
> > > > > >> progress?
> > > > > >> - We create a hadoop.apache.org/new-site/ where
> > this new site
> > > > > goes.
> > > > > >> - We then modify the existing web-site to say that
> > there is a
> > > > new
> > > > > >> site/experience that folks can click on a link and
> > navigate to
> > > > > >> - As this new website matures and gets feedback &
> > fixes, we
> > > > > finally
> > > > > >> pull the plug at a later point of time when we think
> > we are good
> > > > to
> > > > > go.
> > > > > >>
> > > > > >> Thoughts?
> > > > > >>
> > > > > >> +Vinod
> > > > > >>
> > > > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <
> > elek@apache.org>
> > > > wrote:
> > > > > >>>
> > > > > >>> 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:
> > > > > >>>
> > > > > >>> This thread started long time ago to use a more
> > modern hadoop
> > > > site:
> > > > > >>>
> > > > > >>> Goals were:
> > > > > >>>
> > > > > >>> 1. To make it easier to manage it (the release
> > entries could be
> > > > > >>> created by a script as part of the release process)
> > > > > >>> 2. To use a better look-and-feel
> > > > > >>> 3. Move it out from svn to git
> > > > > >>>
> > > > > >>> I proposed to:
> > > > > >>>
> > > > > >>> 1. Move the existing site to git and generate it
> > with hugo
> > > (which
> > > > > is
> > > > > >>> a single, standalone binary)
> > > > > >>> 2. Move both the rendered and source branches to
> git.
> > > > > >>> 3. (Create a jenkins job to generate the site
> > automatically)
> > > > > >>>
> > > > > >>> NOTE: this is just about forrest based
> > hadoop.apache.org, NOT
> > > > > about
> > > > > >>> the documentation which is generated by mvn-site
> (as
> > before)
> > > > > >>>
> > > > > >>>
> > > > > >>> I got multiple valuable feedback and I improved the
> > proposed
> > > site
> > > > > >>> according to the comments. Allen had some concerns
> > about the
> > > used
> > > > > >>> technologies (hugo vs. mvn-site) and I answered all
> > the
> > > questions
> > > > > why
> > > > > >>> I think mvn-site is the best for documentation and
> > hugo is best
> > > > > for
> > > > > >>> generating site.
> > > > > >>>
> > > > > >>>
> > > > > >>> I would like to finish this effort/jira: I would
> > like to start
> > > a
> > > > > >>> discussion about using this proposed version and
> > approach as a
> > > > new
> > > > > >>> site of Apache Hadoop. Please let me know what you
> > think.
> > > > > >>>
> > > > > >>>
> > > > > >>> Thanks a lot,
> > > > > >>> Marton
> > > > > >>>
> > > > > >>>
> > > > >
> > ---------------------------------------------------------------------
> > > > > >>> To unsubscribe, e-mail:
> > > common-dev-unsubscribe@hadoop.apache.org
> > > > > >>> For additional commands, e-mail:
> > > > common-dev-help@hadoop.apache.org
> > > > > >>>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > >
> > ---------------------------------------------------------------------
> > > > > >> To unsubscribe, e-mail:
> > > common-dev-unsubscribe@hadoop.apache.org
> > > > > >> For additional commands, e-mail:
> > > > common-dev-help@hadoop.apache.org
> > > > > >>
> > > > > >
> > > > > >
> > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail:
> > hdfs-dev-unsubscribe@hadoop.apache.org
> > > > > > For additional commands, e-mail:
> > hdfs-dev-help@hadoop.apache.org
> > > > >
> > > > >
> > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> > hdfs-dev-unsubscribe@hadoop.apache.org
> > > > > For additional commands, e-mail:
> > hdfs-dev-help@hadoop.apache.org
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Weiwei Yang
> > >
> >
> >
> > --
> > John
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> >
> >
> >
> >
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Sunil G <su...@apache.org>.
+1. Looks really good.
- Sunil
On Mon, Sep 3, 2018 at 10:51 AM Vinayakumar B <vi...@apache.org>
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, <
> sbanerjee@hortonworks.com>
> wrote:
>
> > +1
> >
> > Thanks
> > Shashi
> >
> > On 9/3/18, 9:23 AM, "Mukul Kumar Singh" <ms...@hortonworks.com> wrote:
> >
> > +1, Thanks for working on this Marton.
> >
> > -Mukul
> >
> > On 03/09/18, 9:02 AM, "John Zhuge" <jo...@gmail.com> wrote:
> >
> > +1 Like the new site.
> >
> > On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang <ab...@gmail.com>
> > wrote:
> >
> > > That's really nice, +1.
> > >
> > > --
> > > Weiwei
> > >
> > > On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wheeleast@gmail.com
> >
> > wrote:
> > >
> > > > +1, thanks for working on this, Marton!
> > > >
> > > > Best,
> > > > Wangda
> > > >
> > > > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <
> > aagarwal@hortonworks.com
> > > >
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > Thanks for initiating this Marton.
> > > > >
> > > > >
> > > > > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org>
> 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 ask infra to use the new repository as the
> > source of
> > > > > hadoop.apache.org
> > > > >
> > > > > 3. I will sync manually all of the changes in the next
> > two months
> > > > back
> > > > > to the svn site from the git (release announcements,
> new
> > > committers)
> > > > >
> > > > > IN CASE OF ANY PROBLEM we can switch back to the svn
> > without any
> > > > > problem.
> > > > >
> > > > > If no-one objects within three days, I'll assume lazy
> > consensus and
> > > > > start with this plan. Please comment if you have
> > objections.
> > > > >
> > > > > Again: it allows immediate fallback at any time as svn
> > repo will be
> > > > > kept
> > > > > as is (+ I will keep it up-to-date in the next 2
> months)
> > > > >
> > > > > Thanks,
> > > > > Marton
> > > > >
> > > > >
> > > > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > > > > >
> > > > > > 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 tools.
> > > > > >
> > > > > > Hugo has more simple compared to jekyll. Just one
> > binary, without
> > > > > > dependencies, works everywhere (mac, linux, windows)
> > > > > >
> > > > > > Hugo has much more powerful compared to "mvn site".
> > Easier to
> > > > > create/use
> > > > > > more modern layout/theme, and easier to handle the
> > content (for
> > > > > example
> > > > > > new release announcements could be generated as part
> > of the
> > > release
> > > > > > process)
> > > > > >
> > > > > > I think it's very low risk to try out a new approach
> > for the site
> > > > > (and
> > > > > > easy to rollback in case of problems)
> > > > > >
> > > > > > Marton
> > > > > >
> > > > > > ps: I just updated the patch/preview site with the
> > recent
> > > releases:
> > > > > >
> > > > > > ***************************
> > > > > > * http://hadoop.anzix.net *
> > > > > > ***************************
> > > > > >
> > > > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli
> wrote:
> > > > > >> 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
> > > > > >> feedback rapidly and get it in.
> > > > > >>
> > > > > >> For (2), how about we do it in a different way in
> the
> > interest
> > > of
> > > > > >> progress?
> > > > > >> - We create a hadoop.apache.org/new-site/ where
> > this new site
> > > > > goes.
> > > > > >> - We then modify the existing web-site to say that
> > there is a
> > > > new
> > > > > >> site/experience that folks can click on a link and
> > navigate to
> > > > > >> - As this new website matures and gets feedback &
> > fixes, we
> > > > > finally
> > > > > >> pull the plug at a later point of time when we think
> > we are good
> > > > to
> > > > > go.
> > > > > >>
> > > > > >> Thoughts?
> > > > > >>
> > > > > >> +Vinod
> > > > > >>
> > > > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <
> > elek@apache.org>
> > > > wrote:
> > > > > >>>
> > > > > >>> 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:
> > > > > >>>
> > > > > >>> This thread started long time ago to use a more
> > modern hadoop
> > > > site:
> > > > > >>>
> > > > > >>> Goals were:
> > > > > >>>
> > > > > >>> 1. To make it easier to manage it (the release
> > entries could be
> > > > > >>> created by a script as part of the release process)
> > > > > >>> 2. To use a better look-and-feel
> > > > > >>> 3. Move it out from svn to git
> > > > > >>>
> > > > > >>> I proposed to:
> > > > > >>>
> > > > > >>> 1. Move the existing site to git and generate it
> > with hugo
> > > (which
> > > > > is
> > > > > >>> a single, standalone binary)
> > > > > >>> 2. Move both the rendered and source branches to
> git.
> > > > > >>> 3. (Create a jenkins job to generate the site
> > automatically)
> > > > > >>>
> > > > > >>> NOTE: this is just about forrest based
> > hadoop.apache.org, NOT
> > > > > about
> > > > > >>> the documentation which is generated by mvn-site
> (as
> > before)
> > > > > >>>
> > > > > >>>
> > > > > >>> I got multiple valuable feedback and I improved the
> > proposed
> > > site
> > > > > >>> according to the comments. Allen had some concerns
> > about the
> > > used
> > > > > >>> technologies (hugo vs. mvn-site) and I answered all
> > the
> > > questions
> > > > > why
> > > > > >>> I think mvn-site is the best for documentation and
> > hugo is best
> > > > > for
> > > > > >>> generating site.
> > > > > >>>
> > > > > >>>
> > > > > >>> I would like to finish this effort/jira: I would
> > like to start
> > > a
> > > > > >>> discussion about using this proposed version and
> > approach as a
> > > > new
> > > > > >>> site of Apache Hadoop. Please let me know what you
> > think.
> > > > > >>>
> > > > > >>>
> > > > > >>> Thanks a lot,
> > > > > >>> Marton
> > > > > >>>
> > > > > >>>
> > > > >
> > ---------------------------------------------------------------------
> > > > > >>> To unsubscribe, e-mail:
> > > common-dev-unsubscribe@hadoop.apache.org
> > > > > >>> For additional commands, e-mail:
> > > > common-dev-help@hadoop.apache.org
> > > > > >>>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > >
> > ---------------------------------------------------------------------
> > > > > >> To unsubscribe, e-mail:
> > > common-dev-unsubscribe@hadoop.apache.org
> > > > > >> For additional commands, e-mail:
> > > > common-dev-help@hadoop.apache.org
> > > > > >>
> > > > > >
> > > > > >
> > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail:
> > hdfs-dev-unsubscribe@hadoop.apache.org
> > > > > > For additional commands, e-mail:
> > hdfs-dev-help@hadoop.apache.org
> > > > >
> > > > >
> > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> > hdfs-dev-unsubscribe@hadoop.apache.org
> > > > > For additional commands, e-mail:
> > hdfs-dev-help@hadoop.apache.org
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Weiwei Yang
> > >
> >
> >
> > --
> > John
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> >
> >
> >
> >
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Vinayakumar B <vi...@apache.org>.
+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, <sb...@hortonworks.com>
wrote:
> +1
>
> Thanks
> Shashi
>
> On 9/3/18, 9:23 AM, "Mukul Kumar Singh" <ms...@hortonworks.com> wrote:
>
> +1, Thanks for working on this Marton.
>
> -Mukul
>
> On 03/09/18, 9:02 AM, "John Zhuge" <jo...@gmail.com> wrote:
>
> +1 Like the new site.
>
> On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang <ab...@gmail.com>
> wrote:
>
> > That's really nice, +1.
> >
> > --
> > Weiwei
> >
> > On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wh...@gmail.com>
> wrote:
> >
> > > +1, thanks for working on this, Marton!
> > >
> > > Best,
> > > Wangda
> > >
> > > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <
> aagarwal@hortonworks.com
> > >
> > > wrote:
> > >
> > > > +1
> > > >
> > > > Thanks for initiating this Marton.
> > > >
> > > >
> > > > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the
> source of
> > > > hadoop.apache.org
> > > >
> > > > 3. I will sync manually all of the changes in the next
> two months
> > > back
> > > > to the svn site from the git (release announcements, new
> > committers)
> > > >
> > > > IN CASE OF ANY PROBLEM we can switch back to the svn
> without any
> > > > problem.
> > > >
> > > > If no-one objects within three days, I'll assume lazy
> consensus and
> > > > start with this plan. Please comment if you have
> objections.
> > > >
> > > > Again: it allows immediate fallback at any time as svn
> repo will be
> > > > kept
> > > > as is (+ I will keep it up-to-date in the next 2 months)
> > > >
> > > > Thanks,
> > > > Marton
> > > >
> > > >
> > > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > > > >
> > > > > 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 tools.
> > > > >
> > > > > Hugo has more simple compared to jekyll. Just one
> binary, without
> > > > > dependencies, works everywhere (mac, linux, windows)
> > > > >
> > > > > Hugo has much more powerful compared to "mvn site".
> Easier to
> > > > create/use
> > > > > more modern layout/theme, and easier to handle the
> content (for
> > > > example
> > > > > new release announcements could be generated as part
> of the
> > release
> > > > > process)
> > > > >
> > > > > I think it's very low risk to try out a new approach
> for the site
> > > > (and
> > > > > easy to rollback in case of problems)
> > > > >
> > > > > Marton
> > > > >
> > > > > ps: I just updated the patch/preview site with the
> recent
> > releases:
> > > > >
> > > > > ***************************
> > > > > * http://hadoop.anzix.net *
> > > > > ***************************
> > > > >
> > > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > > > >> 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
> > > > >> feedback rapidly and get it in.
> > > > >>
> > > > >> For (2), how about we do it in a different way in the
> interest
> > of
> > > > >> progress?
> > > > >> - We create a hadoop.apache.org/new-site/ where
> this new site
> > > > goes.
> > > > >> - We then modify the existing web-site to say that
> there is a
> > > new
> > > > >> site/experience that folks can click on a link and
> navigate to
> > > > >> - As this new website matures and gets feedback &
> fixes, we
> > > > finally
> > > > >> pull the plug at a later point of time when we think
> we are good
> > > to
> > > > go.
> > > > >>
> > > > >> Thoughts?
> > > > >>
> > > > >> +Vinod
> > > > >>
> > > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <
> elek@apache.org>
> > > wrote:
> > > > >>>
> > > > >>> 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:
> > > > >>>
> > > > >>> This thread started long time ago to use a more
> modern hadoop
> > > site:
> > > > >>>
> > > > >>> Goals were:
> > > > >>>
> > > > >>> 1. To make it easier to manage it (the release
> entries could be
> > > > >>> created by a script as part of the release process)
> > > > >>> 2. To use a better look-and-feel
> > > > >>> 3. Move it out from svn to git
> > > > >>>
> > > > >>> I proposed to:
> > > > >>>
> > > > >>> 1. Move the existing site to git and generate it
> with hugo
> > (which
> > > > is
> > > > >>> a single, standalone binary)
> > > > >>> 2. Move both the rendered and source branches to git.
> > > > >>> 3. (Create a jenkins job to generate the site
> automatically)
> > > > >>>
> > > > >>> NOTE: this is just about forrest based
> hadoop.apache.org, NOT
> > > > about
> > > > >>> the documentation which is generated by mvn-site (as
> before)
> > > > >>>
> > > > >>>
> > > > >>> I got multiple valuable feedback and I improved the
> proposed
> > site
> > > > >>> according to the comments. Allen had some concerns
> about the
> > used
> > > > >>> technologies (hugo vs. mvn-site) and I answered all
> the
> > questions
> > > > why
> > > > >>> I think mvn-site is the best for documentation and
> hugo is best
> > > > for
> > > > >>> generating site.
> > > > >>>
> > > > >>>
> > > > >>> I would like to finish this effort/jira: I would
> like to start
> > a
> > > > >>> discussion about using this proposed version and
> approach as a
> > > new
> > > > >>> site of Apache Hadoop. Please let me know what you
> think.
> > > > >>>
> > > > >>>
> > > > >>> Thanks a lot,
> > > > >>> Marton
> > > > >>>
> > > > >>>
> > > >
> ---------------------------------------------------------------------
> > > > >>> To unsubscribe, e-mail:
> > common-dev-unsubscribe@hadoop.apache.org
> > > > >>> For additional commands, e-mail:
> > > common-dev-help@hadoop.apache.org
> > > > >>>
> > > > >>
> > > > >>
> > > > >>
> > > >
> ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail:
> > common-dev-unsubscribe@hadoop.apache.org
> > > > >> For additional commands, e-mail:
> > > common-dev-help@hadoop.apache.org
> > > > >>
> > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> hdfs-dev-unsubscribe@hadoop.apache.org
> > > > > For additional commands, e-mail:
> hdfs-dev-help@hadoop.apache.org
> > > >
> > > >
> >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> hdfs-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail:
> hdfs-dev-help@hadoop.apache.org
> > > >
> > > >
> > > >
> > > >
> > >
> >
> >
> > --
> > Weiwei Yang
> >
>
>
> --
> John
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
>
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Vinayakumar B <vi...@apache.org>.
+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, <sb...@hortonworks.com>
wrote:
> +1
>
> Thanks
> Shashi
>
> On 9/3/18, 9:23 AM, "Mukul Kumar Singh" <ms...@hortonworks.com> wrote:
>
> +1, Thanks for working on this Marton.
>
> -Mukul
>
> On 03/09/18, 9:02 AM, "John Zhuge" <jo...@gmail.com> wrote:
>
> +1 Like the new site.
>
> On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang <ab...@gmail.com>
> wrote:
>
> > That's really nice, +1.
> >
> > --
> > Weiwei
> >
> > On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wh...@gmail.com>
> wrote:
> >
> > > +1, thanks for working on this, Marton!
> > >
> > > Best,
> > > Wangda
> > >
> > > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <
> aagarwal@hortonworks.com
> > >
> > > wrote:
> > >
> > > > +1
> > > >
> > > > Thanks for initiating this Marton.
> > > >
> > > >
> > > > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the
> source of
> > > > hadoop.apache.org
> > > >
> > > > 3. I will sync manually all of the changes in the next
> two months
> > > back
> > > > to the svn site from the git (release announcements, new
> > committers)
> > > >
> > > > IN CASE OF ANY PROBLEM we can switch back to the svn
> without any
> > > > problem.
> > > >
> > > > If no-one objects within three days, I'll assume lazy
> consensus and
> > > > start with this plan. Please comment if you have
> objections.
> > > >
> > > > Again: it allows immediate fallback at any time as svn
> repo will be
> > > > kept
> > > > as is (+ I will keep it up-to-date in the next 2 months)
> > > >
> > > > Thanks,
> > > > Marton
> > > >
> > > >
> > > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > > > >
> > > > > 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 tools.
> > > > >
> > > > > Hugo has more simple compared to jekyll. Just one
> binary, without
> > > > > dependencies, works everywhere (mac, linux, windows)
> > > > >
> > > > > Hugo has much more powerful compared to "mvn site".
> Easier to
> > > > create/use
> > > > > more modern layout/theme, and easier to handle the
> content (for
> > > > example
> > > > > new release announcements could be generated as part
> of the
> > release
> > > > > process)
> > > > >
> > > > > I think it's very low risk to try out a new approach
> for the site
> > > > (and
> > > > > easy to rollback in case of problems)
> > > > >
> > > > > Marton
> > > > >
> > > > > ps: I just updated the patch/preview site with the
> recent
> > releases:
> > > > >
> > > > > ***************************
> > > > > * http://hadoop.anzix.net *
> > > > > ***************************
> > > > >
> > > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > > > >> 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
> > > > >> feedback rapidly and get it in.
> > > > >>
> > > > >> For (2), how about we do it in a different way in the
> interest
> > of
> > > > >> progress?
> > > > >> - We create a hadoop.apache.org/new-site/ where
> this new site
> > > > goes.
> > > > >> - We then modify the existing web-site to say that
> there is a
> > > new
> > > > >> site/experience that folks can click on a link and
> navigate to
> > > > >> - As this new website matures and gets feedback &
> fixes, we
> > > > finally
> > > > >> pull the plug at a later point of time when we think
> we are good
> > > to
> > > > go.
> > > > >>
> > > > >> Thoughts?
> > > > >>
> > > > >> +Vinod
> > > > >>
> > > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <
> elek@apache.org>
> > > wrote:
> > > > >>>
> > > > >>> 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:
> > > > >>>
> > > > >>> This thread started long time ago to use a more
> modern hadoop
> > > site:
> > > > >>>
> > > > >>> Goals were:
> > > > >>>
> > > > >>> 1. To make it easier to manage it (the release
> entries could be
> > > > >>> created by a script as part of the release process)
> > > > >>> 2. To use a better look-and-feel
> > > > >>> 3. Move it out from svn to git
> > > > >>>
> > > > >>> I proposed to:
> > > > >>>
> > > > >>> 1. Move the existing site to git and generate it
> with hugo
> > (which
> > > > is
> > > > >>> a single, standalone binary)
> > > > >>> 2. Move both the rendered and source branches to git.
> > > > >>> 3. (Create a jenkins job to generate the site
> automatically)
> > > > >>>
> > > > >>> NOTE: this is just about forrest based
> hadoop.apache.org, NOT
> > > > about
> > > > >>> the documentation which is generated by mvn-site (as
> before)
> > > > >>>
> > > > >>>
> > > > >>> I got multiple valuable feedback and I improved the
> proposed
> > site
> > > > >>> according to the comments. Allen had some concerns
> about the
> > used
> > > > >>> technologies (hugo vs. mvn-site) and I answered all
> the
> > questions
> > > > why
> > > > >>> I think mvn-site is the best for documentation and
> hugo is best
> > > > for
> > > > >>> generating site.
> > > > >>>
> > > > >>>
> > > > >>> I would like to finish this effort/jira: I would
> like to start
> > a
> > > > >>> discussion about using this proposed version and
> approach as a
> > > new
> > > > >>> site of Apache Hadoop. Please let me know what you
> think.
> > > > >>>
> > > > >>>
> > > > >>> Thanks a lot,
> > > > >>> Marton
> > > > >>>
> > > > >>>
> > > >
> ---------------------------------------------------------------------
> > > > >>> To unsubscribe, e-mail:
> > common-dev-unsubscribe@hadoop.apache.org
> > > > >>> For additional commands, e-mail:
> > > common-dev-help@hadoop.apache.org
> > > > >>>
> > > > >>
> > > > >>
> > > > >>
> > > >
> ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail:
> > common-dev-unsubscribe@hadoop.apache.org
> > > > >> For additional commands, e-mail:
> > > common-dev-help@hadoop.apache.org
> > > > >>
> > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> hdfs-dev-unsubscribe@hadoop.apache.org
> > > > > For additional commands, e-mail:
> hdfs-dev-help@hadoop.apache.org
> > > >
> > > >
> >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> hdfs-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail:
> hdfs-dev-help@hadoop.apache.org
> > > >
> > > >
> > > >
> > > >
> > >
> >
> >
> > --
> > Weiwei Yang
> >
>
>
> --
> John
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
>
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Vinayakumar B <vi...@apache.org>.
+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, <sb...@hortonworks.com>
wrote:
> +1
>
> Thanks
> Shashi
>
> On 9/3/18, 9:23 AM, "Mukul Kumar Singh" <ms...@hortonworks.com> wrote:
>
> +1, Thanks for working on this Marton.
>
> -Mukul
>
> On 03/09/18, 9:02 AM, "John Zhuge" <jo...@gmail.com> wrote:
>
> +1 Like the new site.
>
> On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang <ab...@gmail.com>
> wrote:
>
> > That's really nice, +1.
> >
> > --
> > Weiwei
> >
> > On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wh...@gmail.com>
> wrote:
> >
> > > +1, thanks for working on this, Marton!
> > >
> > > Best,
> > > Wangda
> > >
> > > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <
> aagarwal@hortonworks.com
> > >
> > > wrote:
> > >
> > > > +1
> > > >
> > > > Thanks for initiating this Marton.
> > > >
> > > >
> > > > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the
> source of
> > > > hadoop.apache.org
> > > >
> > > > 3. I will sync manually all of the changes in the next
> two months
> > > back
> > > > to the svn site from the git (release announcements, new
> > committers)
> > > >
> > > > IN CASE OF ANY PROBLEM we can switch back to the svn
> without any
> > > > problem.
> > > >
> > > > If no-one objects within three days, I'll assume lazy
> consensus and
> > > > start with this plan. Please comment if you have
> objections.
> > > >
> > > > Again: it allows immediate fallback at any time as svn
> repo will be
> > > > kept
> > > > as is (+ I will keep it up-to-date in the next 2 months)
> > > >
> > > > Thanks,
> > > > Marton
> > > >
> > > >
> > > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > > > >
> > > > > 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 tools.
> > > > >
> > > > > Hugo has more simple compared to jekyll. Just one
> binary, without
> > > > > dependencies, works everywhere (mac, linux, windows)
> > > > >
> > > > > Hugo has much more powerful compared to "mvn site".
> Easier to
> > > > create/use
> > > > > more modern layout/theme, and easier to handle the
> content (for
> > > > example
> > > > > new release announcements could be generated as part
> of the
> > release
> > > > > process)
> > > > >
> > > > > I think it's very low risk to try out a new approach
> for the site
> > > > (and
> > > > > easy to rollback in case of problems)
> > > > >
> > > > > Marton
> > > > >
> > > > > ps: I just updated the patch/preview site with the
> recent
> > releases:
> > > > >
> > > > > ***************************
> > > > > * http://hadoop.anzix.net *
> > > > > ***************************
> > > > >
> > > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > > > >> 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
> > > > >> feedback rapidly and get it in.
> > > > >>
> > > > >> For (2), how about we do it in a different way in the
> interest
> > of
> > > > >> progress?
> > > > >> - We create a hadoop.apache.org/new-site/ where
> this new site
> > > > goes.
> > > > >> - We then modify the existing web-site to say that
> there is a
> > > new
> > > > >> site/experience that folks can click on a link and
> navigate to
> > > > >> - As this new website matures and gets feedback &
> fixes, we
> > > > finally
> > > > >> pull the plug at a later point of time when we think
> we are good
> > > to
> > > > go.
> > > > >>
> > > > >> Thoughts?
> > > > >>
> > > > >> +Vinod
> > > > >>
> > > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <
> elek@apache.org>
> > > wrote:
> > > > >>>
> > > > >>> 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:
> > > > >>>
> > > > >>> This thread started long time ago to use a more
> modern hadoop
> > > site:
> > > > >>>
> > > > >>> Goals were:
> > > > >>>
> > > > >>> 1. To make it easier to manage it (the release
> entries could be
> > > > >>> created by a script as part of the release process)
> > > > >>> 2. To use a better look-and-feel
> > > > >>> 3. Move it out from svn to git
> > > > >>>
> > > > >>> I proposed to:
> > > > >>>
> > > > >>> 1. Move the existing site to git and generate it
> with hugo
> > (which
> > > > is
> > > > >>> a single, standalone binary)
> > > > >>> 2. Move both the rendered and source branches to git.
> > > > >>> 3. (Create a jenkins job to generate the site
> automatically)
> > > > >>>
> > > > >>> NOTE: this is just about forrest based
> hadoop.apache.org, NOT
> > > > about
> > > > >>> the documentation which is generated by mvn-site (as
> before)
> > > > >>>
> > > > >>>
> > > > >>> I got multiple valuable feedback and I improved the
> proposed
> > site
> > > > >>> according to the comments. Allen had some concerns
> about the
> > used
> > > > >>> technologies (hugo vs. mvn-site) and I answered all
> the
> > questions
> > > > why
> > > > >>> I think mvn-site is the best for documentation and
> hugo is best
> > > > for
> > > > >>> generating site.
> > > > >>>
> > > > >>>
> > > > >>> I would like to finish this effort/jira: I would
> like to start
> > a
> > > > >>> discussion about using this proposed version and
> approach as a
> > > new
> > > > >>> site of Apache Hadoop. Please let me know what you
> think.
> > > > >>>
> > > > >>>
> > > > >>> Thanks a lot,
> > > > >>> Marton
> > > > >>>
> > > > >>>
> > > >
> ---------------------------------------------------------------------
> > > > >>> To unsubscribe, e-mail:
> > common-dev-unsubscribe@hadoop.apache.org
> > > > >>> For additional commands, e-mail:
> > > common-dev-help@hadoop.apache.org
> > > > >>>
> > > > >>
> > > > >>
> > > > >>
> > > >
> ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail:
> > common-dev-unsubscribe@hadoop.apache.org
> > > > >> For additional commands, e-mail:
> > > common-dev-help@hadoop.apache.org
> > > > >>
> > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> hdfs-dev-unsubscribe@hadoop.apache.org
> > > > > For additional commands, e-mail:
> hdfs-dev-help@hadoop.apache.org
> > > >
> > > >
> >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> hdfs-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail:
> hdfs-dev-help@hadoop.apache.org
> > > >
> > > >
> > > >
> > > >
> > >
> >
> >
> > --
> > Weiwei Yang
> >
>
>
> --
> John
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
>
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Vinayakumar B <vi...@apache.org>.
+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, <sb...@hortonworks.com>
wrote:
> +1
>
> Thanks
> Shashi
>
> On 9/3/18, 9:23 AM, "Mukul Kumar Singh" <ms...@hortonworks.com> wrote:
>
> +1, Thanks for working on this Marton.
>
> -Mukul
>
> On 03/09/18, 9:02 AM, "John Zhuge" <jo...@gmail.com> wrote:
>
> +1 Like the new site.
>
> On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang <ab...@gmail.com>
> wrote:
>
> > That's really nice, +1.
> >
> > --
> > Weiwei
> >
> > On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wh...@gmail.com>
> wrote:
> >
> > > +1, thanks for working on this, Marton!
> > >
> > > Best,
> > > Wangda
> > >
> > > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <
> aagarwal@hortonworks.com
> > >
> > > wrote:
> > >
> > > > +1
> > > >
> > > > Thanks for initiating this Marton.
> > > >
> > > >
> > > > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the
> source of
> > > > hadoop.apache.org
> > > >
> > > > 3. I will sync manually all of the changes in the next
> two months
> > > back
> > > > to the svn site from the git (release announcements, new
> > committers)
> > > >
> > > > IN CASE OF ANY PROBLEM we can switch back to the svn
> without any
> > > > problem.
> > > >
> > > > If no-one objects within three days, I'll assume lazy
> consensus and
> > > > start with this plan. Please comment if you have
> objections.
> > > >
> > > > Again: it allows immediate fallback at any time as svn
> repo will be
> > > > kept
> > > > as is (+ I will keep it up-to-date in the next 2 months)
> > > >
> > > > Thanks,
> > > > Marton
> > > >
> > > >
> > > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > > > >
> > > > > 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 tools.
> > > > >
> > > > > Hugo has more simple compared to jekyll. Just one
> binary, without
> > > > > dependencies, works everywhere (mac, linux, windows)
> > > > >
> > > > > Hugo has much more powerful compared to "mvn site".
> Easier to
> > > > create/use
> > > > > more modern layout/theme, and easier to handle the
> content (for
> > > > example
> > > > > new release announcements could be generated as part
> of the
> > release
> > > > > process)
> > > > >
> > > > > I think it's very low risk to try out a new approach
> for the site
> > > > (and
> > > > > easy to rollback in case of problems)
> > > > >
> > > > > Marton
> > > > >
> > > > > ps: I just updated the patch/preview site with the
> recent
> > releases:
> > > > >
> > > > > ***************************
> > > > > * http://hadoop.anzix.net *
> > > > > ***************************
> > > > >
> > > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > > > >> 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
> > > > >> feedback rapidly and get it in.
> > > > >>
> > > > >> For (2), how about we do it in a different way in the
> interest
> > of
> > > > >> progress?
> > > > >> - We create a hadoop.apache.org/new-site/ where
> this new site
> > > > goes.
> > > > >> - We then modify the existing web-site to say that
> there is a
> > > new
> > > > >> site/experience that folks can click on a link and
> navigate to
> > > > >> - As this new website matures and gets feedback &
> fixes, we
> > > > finally
> > > > >> pull the plug at a later point of time when we think
> we are good
> > > to
> > > > go.
> > > > >>
> > > > >> Thoughts?
> > > > >>
> > > > >> +Vinod
> > > > >>
> > > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <
> elek@apache.org>
> > > wrote:
> > > > >>>
> > > > >>> 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:
> > > > >>>
> > > > >>> This thread started long time ago to use a more
> modern hadoop
> > > site:
> > > > >>>
> > > > >>> Goals were:
> > > > >>>
> > > > >>> 1. To make it easier to manage it (the release
> entries could be
> > > > >>> created by a script as part of the release process)
> > > > >>> 2. To use a better look-and-feel
> > > > >>> 3. Move it out from svn to git
> > > > >>>
> > > > >>> I proposed to:
> > > > >>>
> > > > >>> 1. Move the existing site to git and generate it
> with hugo
> > (which
> > > > is
> > > > >>> a single, standalone binary)
> > > > >>> 2. Move both the rendered and source branches to git.
> > > > >>> 3. (Create a jenkins job to generate the site
> automatically)
> > > > >>>
> > > > >>> NOTE: this is just about forrest based
> hadoop.apache.org, NOT
> > > > about
> > > > >>> the documentation which is generated by mvn-site (as
> before)
> > > > >>>
> > > > >>>
> > > > >>> I got multiple valuable feedback and I improved the
> proposed
> > site
> > > > >>> according to the comments. Allen had some concerns
> about the
> > used
> > > > >>> technologies (hugo vs. mvn-site) and I answered all
> the
> > questions
> > > > why
> > > > >>> I think mvn-site is the best for documentation and
> hugo is best
> > > > for
> > > > >>> generating site.
> > > > >>>
> > > > >>>
> > > > >>> I would like to finish this effort/jira: I would
> like to start
> > a
> > > > >>> discussion about using this proposed version and
> approach as a
> > > new
> > > > >>> site of Apache Hadoop. Please let me know what you
> think.
> > > > >>>
> > > > >>>
> > > > >>> Thanks a lot,
> > > > >>> Marton
> > > > >>>
> > > > >>>
> > > >
> ---------------------------------------------------------------------
> > > > >>> To unsubscribe, e-mail:
> > common-dev-unsubscribe@hadoop.apache.org
> > > > >>> For additional commands, e-mail:
> > > common-dev-help@hadoop.apache.org
> > > > >>>
> > > > >>
> > > > >>
> > > > >>
> > > >
> ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail:
> > common-dev-unsubscribe@hadoop.apache.org
> > > > >> For additional commands, e-mail:
> > > common-dev-help@hadoop.apache.org
> > > > >>
> > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> hdfs-dev-unsubscribe@hadoop.apache.org
> > > > > For additional commands, e-mail:
> hdfs-dev-help@hadoop.apache.org
> > > >
> > > >
> >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> hdfs-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail:
> hdfs-dev-help@hadoop.apache.org
> > > >
> > > >
> > > >
> > > >
> > >
> >
> >
> > --
> > Weiwei Yang
> >
>
>
> --
> John
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
>
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Shashikant Banerjee <sb...@hortonworks.com>.
+1
Thanks
Shashi
On 9/3/18, 9:23 AM, "Mukul Kumar Singh" <ms...@hortonworks.com> wrote:
+1, Thanks for working on this Marton.
-Mukul
On 03/09/18, 9:02 AM, "John Zhuge" <jo...@gmail.com> wrote:
+1 Like the new site.
On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang <ab...@gmail.com> wrote:
> That's really nice, +1.
>
> --
> Weiwei
>
> On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wh...@gmail.com> wrote:
>
> > +1, thanks for working on this, Marton!
> >
> > Best,
> > Wangda
> >
> > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <aagarwal@hortonworks.com
> >
> > wrote:
> >
> > > +1
> > >
> > > Thanks for initiating this Marton.
> > >
> > >
> > > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
> > > hadoop.apache.org
> > >
> > > 3. I will sync manually all of the changes in the next two months
> > back
> > > to the svn site from the git (release announcements, new
> committers)
> > >
> > > IN CASE OF ANY PROBLEM we can switch back to the svn without any
> > > problem.
> > >
> > > If no-one objects within three days, I'll assume lazy consensus and
> > > start with this plan. Please comment if you have objections.
> > >
> > > Again: it allows immediate fallback at any time as svn repo will be
> > > kept
> > > as is (+ I will keep it up-to-date in the next 2 months)
> > >
> > > Thanks,
> > > Marton
> > >
> > >
> > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > > >
> > > > 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 tools.
> > > >
> > > > Hugo has more simple compared to jekyll. Just one binary, without
> > > > dependencies, works everywhere (mac, linux, windows)
> > > >
> > > > Hugo has much more powerful compared to "mvn site". Easier to
> > > create/use
> > > > more modern layout/theme, and easier to handle the content (for
> > > example
> > > > new release announcements could be generated as part of the
> release
> > > > process)
> > > >
> > > > I think it's very low risk to try out a new approach for the site
> > > (and
> > > > easy to rollback in case of problems)
> > > >
> > > > Marton
> > > >
> > > > ps: I just updated the patch/preview site with the recent
> releases:
> > > >
> > > > ***************************
> > > > * http://hadoop.anzix.net *
> > > > ***************************
> > > >
> > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > > >> 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
> > > >> feedback rapidly and get it in.
> > > >>
> > > >> For (2), how about we do it in a different way in the interest
> of
> > > >> progress?
> > > >> - We create a hadoop.apache.org/new-site/ where this new site
> > > goes.
> > > >> - We then modify the existing web-site to say that there is a
> > new
> > > >> site/experience that folks can click on a link and navigate to
> > > >> - As this new website matures and gets feedback & fixes, we
> > > finally
> > > >> pull the plug at a later point of time when we think we are good
> > to
> > > go.
> > > >>
> > > >> Thoughts?
> > > >>
> > > >> +Vinod
> > > >>
> > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org>
> > wrote:
> > > >>>
> > > >>> 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:
> > > >>>
> > > >>> This thread started long time ago to use a more modern hadoop
> > site:
> > > >>>
> > > >>> Goals were:
> > > >>>
> > > >>> 1. To make it easier to manage it (the release entries could be
> > > >>> created by a script as part of the release process)
> > > >>> 2. To use a better look-and-feel
> > > >>> 3. Move it out from svn to git
> > > >>>
> > > >>> I proposed to:
> > > >>>
> > > >>> 1. Move the existing site to git and generate it with hugo
> (which
> > > is
> > > >>> a single, standalone binary)
> > > >>> 2. Move both the rendered and source branches to git.
> > > >>> 3. (Create a jenkins job to generate the site automatically)
> > > >>>
> > > >>> NOTE: this is just about forrest based hadoop.apache.org, NOT
> > > about
> > > >>> the documentation which is generated by mvn-site (as before)
> > > >>>
> > > >>>
> > > >>> I got multiple valuable feedback and I improved the proposed
> site
> > > >>> according to the comments. Allen had some concerns about the
> used
> > > >>> technologies (hugo vs. mvn-site) and I answered all the
> questions
> > > why
> > > >>> I think mvn-site is the best for documentation and hugo is best
> > > for
> > > >>> generating site.
> > > >>>
> > > >>>
> > > >>> I would like to finish this effort/jira: I would like to start
> a
> > > >>> discussion about using this proposed version and approach as a
> > new
> > > >>> site of Apache Hadoop. Please let me know what you think.
> > > >>>
> > > >>>
> > > >>> Thanks a lot,
> > > >>> Marton
> > > >>>
> > > >>>
> > > ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >>> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>>
> > > >>
> > > >>
> > > >>
> > > ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> > >
> > >
> >
>
>
> --
> Weiwei Yang
>
--
John
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Shashikant Banerjee <sb...@hortonworks.com>.
+1
Thanks
Shashi
On 9/3/18, 9:23 AM, "Mukul Kumar Singh" <ms...@hortonworks.com> wrote:
+1, Thanks for working on this Marton.
-Mukul
On 03/09/18, 9:02 AM, "John Zhuge" <jo...@gmail.com> wrote:
+1 Like the new site.
On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang <ab...@gmail.com> wrote:
> That's really nice, +1.
>
> --
> Weiwei
>
> On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wh...@gmail.com> wrote:
>
> > +1, thanks for working on this, Marton!
> >
> > Best,
> > Wangda
> >
> > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <aagarwal@hortonworks.com
> >
> > wrote:
> >
> > > +1
> > >
> > > Thanks for initiating this Marton.
> > >
> > >
> > > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
> > > hadoop.apache.org
> > >
> > > 3. I will sync manually all of the changes in the next two months
> > back
> > > to the svn site from the git (release announcements, new
> committers)
> > >
> > > IN CASE OF ANY PROBLEM we can switch back to the svn without any
> > > problem.
> > >
> > > If no-one objects within three days, I'll assume lazy consensus and
> > > start with this plan. Please comment if you have objections.
> > >
> > > Again: it allows immediate fallback at any time as svn repo will be
> > > kept
> > > as is (+ I will keep it up-to-date in the next 2 months)
> > >
> > > Thanks,
> > > Marton
> > >
> > >
> > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > > >
> > > > 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 tools.
> > > >
> > > > Hugo has more simple compared to jekyll. Just one binary, without
> > > > dependencies, works everywhere (mac, linux, windows)
> > > >
> > > > Hugo has much more powerful compared to "mvn site". Easier to
> > > create/use
> > > > more modern layout/theme, and easier to handle the content (for
> > > example
> > > > new release announcements could be generated as part of the
> release
> > > > process)
> > > >
> > > > I think it's very low risk to try out a new approach for the site
> > > (and
> > > > easy to rollback in case of problems)
> > > >
> > > > Marton
> > > >
> > > > ps: I just updated the patch/preview site with the recent
> releases:
> > > >
> > > > ***************************
> > > > * http://hadoop.anzix.net *
> > > > ***************************
> > > >
> > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > > >> 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
> > > >> feedback rapidly and get it in.
> > > >>
> > > >> For (2), how about we do it in a different way in the interest
> of
> > > >> progress?
> > > >> - We create a hadoop.apache.org/new-site/ where this new site
> > > goes.
> > > >> - We then modify the existing web-site to say that there is a
> > new
> > > >> site/experience that folks can click on a link and navigate to
> > > >> - As this new website matures and gets feedback & fixes, we
> > > finally
> > > >> pull the plug at a later point of time when we think we are good
> > to
> > > go.
> > > >>
> > > >> Thoughts?
> > > >>
> > > >> +Vinod
> > > >>
> > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org>
> > wrote:
> > > >>>
> > > >>> 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:
> > > >>>
> > > >>> This thread started long time ago to use a more modern hadoop
> > site:
> > > >>>
> > > >>> Goals were:
> > > >>>
> > > >>> 1. To make it easier to manage it (the release entries could be
> > > >>> created by a script as part of the release process)
> > > >>> 2. To use a better look-and-feel
> > > >>> 3. Move it out from svn to git
> > > >>>
> > > >>> I proposed to:
> > > >>>
> > > >>> 1. Move the existing site to git and generate it with hugo
> (which
> > > is
> > > >>> a single, standalone binary)
> > > >>> 2. Move both the rendered and source branches to git.
> > > >>> 3. (Create a jenkins job to generate the site automatically)
> > > >>>
> > > >>> NOTE: this is just about forrest based hadoop.apache.org, NOT
> > > about
> > > >>> the documentation which is generated by mvn-site (as before)
> > > >>>
> > > >>>
> > > >>> I got multiple valuable feedback and I improved the proposed
> site
> > > >>> according to the comments. Allen had some concerns about the
> used
> > > >>> technologies (hugo vs. mvn-site) and I answered all the
> questions
> > > why
> > > >>> I think mvn-site is the best for documentation and hugo is best
> > > for
> > > >>> generating site.
> > > >>>
> > > >>>
> > > >>> I would like to finish this effort/jira: I would like to start
> a
> > > >>> discussion about using this proposed version and approach as a
> > new
> > > >>> site of Apache Hadoop. Please let me know what you think.
> > > >>>
> > > >>>
> > > >>> Thanks a lot,
> > > >>> Marton
> > > >>>
> > > >>>
> > > ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >>> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>>
> > > >>
> > > >>
> > > >>
> > > ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> > >
> > >
> >
>
>
> --
> Weiwei Yang
>
--
John
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Mukul Kumar Singh <ms...@hortonworks.com>.
+1, Thanks for working on this Marton.
-Mukul
On 03/09/18, 9:02 AM, "John Zhuge" <jo...@gmail.com> wrote:
+1 Like the new site.
On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang <ab...@gmail.com> wrote:
> That's really nice, +1.
>
> --
> Weiwei
>
> On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wh...@gmail.com> wrote:
>
> > +1, thanks for working on this, Marton!
> >
> > Best,
> > Wangda
> >
> > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <aagarwal@hortonworks.com
> >
> > wrote:
> >
> > > +1
> > >
> > > Thanks for initiating this Marton.
> > >
> > >
> > > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
> > > hadoop.apache.org
> > >
> > > 3. I will sync manually all of the changes in the next two months
> > back
> > > to the svn site from the git (release announcements, new
> committers)
> > >
> > > IN CASE OF ANY PROBLEM we can switch back to the svn without any
> > > problem.
> > >
> > > If no-one objects within three days, I'll assume lazy consensus and
> > > start with this plan. Please comment if you have objections.
> > >
> > > Again: it allows immediate fallback at any time as svn repo will be
> > > kept
> > > as is (+ I will keep it up-to-date in the next 2 months)
> > >
> > > Thanks,
> > > Marton
> > >
> > >
> > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > > >
> > > > 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 tools.
> > > >
> > > > Hugo has more simple compared to jekyll. Just one binary, without
> > > > dependencies, works everywhere (mac, linux, windows)
> > > >
> > > > Hugo has much more powerful compared to "mvn site". Easier to
> > > create/use
> > > > more modern layout/theme, and easier to handle the content (for
> > > example
> > > > new release announcements could be generated as part of the
> release
> > > > process)
> > > >
> > > > I think it's very low risk to try out a new approach for the site
> > > (and
> > > > easy to rollback in case of problems)
> > > >
> > > > Marton
> > > >
> > > > ps: I just updated the patch/preview site with the recent
> releases:
> > > >
> > > > ***************************
> > > > * http://hadoop.anzix.net *
> > > > ***************************
> > > >
> > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > > >> 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
> > > >> feedback rapidly and get it in.
> > > >>
> > > >> For (2), how about we do it in a different way in the interest
> of
> > > >> progress?
> > > >> - We create a hadoop.apache.org/new-site/ where this new site
> > > goes.
> > > >> - We then modify the existing web-site to say that there is a
> > new
> > > >> site/experience that folks can click on a link and navigate to
> > > >> - As this new website matures and gets feedback & fixes, we
> > > finally
> > > >> pull the plug at a later point of time when we think we are good
> > to
> > > go.
> > > >>
> > > >> Thoughts?
> > > >>
> > > >> +Vinod
> > > >>
> > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org>
> > wrote:
> > > >>>
> > > >>> 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:
> > > >>>
> > > >>> This thread started long time ago to use a more modern hadoop
> > site:
> > > >>>
> > > >>> Goals were:
> > > >>>
> > > >>> 1. To make it easier to manage it (the release entries could be
> > > >>> created by a script as part of the release process)
> > > >>> 2. To use a better look-and-feel
> > > >>> 3. Move it out from svn to git
> > > >>>
> > > >>> I proposed to:
> > > >>>
> > > >>> 1. Move the existing site to git and generate it with hugo
> (which
> > > is
> > > >>> a single, standalone binary)
> > > >>> 2. Move both the rendered and source branches to git.
> > > >>> 3. (Create a jenkins job to generate the site automatically)
> > > >>>
> > > >>> NOTE: this is just about forrest based hadoop.apache.org, NOT
> > > about
> > > >>> the documentation which is generated by mvn-site (as before)
> > > >>>
> > > >>>
> > > >>> I got multiple valuable feedback and I improved the proposed
> site
> > > >>> according to the comments. Allen had some concerns about the
> used
> > > >>> technologies (hugo vs. mvn-site) and I answered all the
> questions
> > > why
> > > >>> I think mvn-site is the best for documentation and hugo is best
> > > for
> > > >>> generating site.
> > > >>>
> > > >>>
> > > >>> I would like to finish this effort/jira: I would like to start
> a
> > > >>> discussion about using this proposed version and approach as a
> > new
> > > >>> site of Apache Hadoop. Please let me know what you think.
> > > >>>
> > > >>>
> > > >>> Thanks a lot,
> > > >>> Marton
> > > >>>
> > > >>>
> > > ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >>> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>>
> > > >>
> > > >>
> > > >>
> > > ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> > >
> > >
> >
>
>
> --
> Weiwei Yang
>
--
John
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Mukul Kumar Singh <ms...@hortonworks.com>.
+1, Thanks for working on this Marton.
-Mukul
On 03/09/18, 9:02 AM, "John Zhuge" <jo...@gmail.com> wrote:
+1 Like the new site.
On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang <ab...@gmail.com> wrote:
> That's really nice, +1.
>
> --
> Weiwei
>
> On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wh...@gmail.com> wrote:
>
> > +1, thanks for working on this, Marton!
> >
> > Best,
> > Wangda
> >
> > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <aagarwal@hortonworks.com
> >
> > wrote:
> >
> > > +1
> > >
> > > Thanks for initiating this Marton.
> > >
> > >
> > > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
> > > hadoop.apache.org
> > >
> > > 3. I will sync manually all of the changes in the next two months
> > back
> > > to the svn site from the git (release announcements, new
> committers)
> > >
> > > IN CASE OF ANY PROBLEM we can switch back to the svn without any
> > > problem.
> > >
> > > If no-one objects within three days, I'll assume lazy consensus and
> > > start with this plan. Please comment if you have objections.
> > >
> > > Again: it allows immediate fallback at any time as svn repo will be
> > > kept
> > > as is (+ I will keep it up-to-date in the next 2 months)
> > >
> > > Thanks,
> > > Marton
> > >
> > >
> > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > > >
> > > > 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 tools.
> > > >
> > > > Hugo has more simple compared to jekyll. Just one binary, without
> > > > dependencies, works everywhere (mac, linux, windows)
> > > >
> > > > Hugo has much more powerful compared to "mvn site". Easier to
> > > create/use
> > > > more modern layout/theme, and easier to handle the content (for
> > > example
> > > > new release announcements could be generated as part of the
> release
> > > > process)
> > > >
> > > > I think it's very low risk to try out a new approach for the site
> > > (and
> > > > easy to rollback in case of problems)
> > > >
> > > > Marton
> > > >
> > > > ps: I just updated the patch/preview site with the recent
> releases:
> > > >
> > > > ***************************
> > > > * http://hadoop.anzix.net *
> > > > ***************************
> > > >
> > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > > >> 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
> > > >> feedback rapidly and get it in.
> > > >>
> > > >> For (2), how about we do it in a different way in the interest
> of
> > > >> progress?
> > > >> - We create a hadoop.apache.org/new-site/ where this new site
> > > goes.
> > > >> - We then modify the existing web-site to say that there is a
> > new
> > > >> site/experience that folks can click on a link and navigate to
> > > >> - As this new website matures and gets feedback & fixes, we
> > > finally
> > > >> pull the plug at a later point of time when we think we are good
> > to
> > > go.
> > > >>
> > > >> Thoughts?
> > > >>
> > > >> +Vinod
> > > >>
> > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org>
> > wrote:
> > > >>>
> > > >>> 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:
> > > >>>
> > > >>> This thread started long time ago to use a more modern hadoop
> > site:
> > > >>>
> > > >>> Goals were:
> > > >>>
> > > >>> 1. To make it easier to manage it (the release entries could be
> > > >>> created by a script as part of the release process)
> > > >>> 2. To use a better look-and-feel
> > > >>> 3. Move it out from svn to git
> > > >>>
> > > >>> I proposed to:
> > > >>>
> > > >>> 1. Move the existing site to git and generate it with hugo
> (which
> > > is
> > > >>> a single, standalone binary)
> > > >>> 2. Move both the rendered and source branches to git.
> > > >>> 3. (Create a jenkins job to generate the site automatically)
> > > >>>
> > > >>> NOTE: this is just about forrest based hadoop.apache.org, NOT
> > > about
> > > >>> the documentation which is generated by mvn-site (as before)
> > > >>>
> > > >>>
> > > >>> I got multiple valuable feedback and I improved the proposed
> site
> > > >>> according to the comments. Allen had some concerns about the
> used
> > > >>> technologies (hugo vs. mvn-site) and I answered all the
> questions
> > > why
> > > >>> I think mvn-site is the best for documentation and hugo is best
> > > for
> > > >>> generating site.
> > > >>>
> > > >>>
> > > >>> I would like to finish this effort/jira: I would like to start
> a
> > > >>> discussion about using this proposed version and approach as a
> > new
> > > >>> site of Apache Hadoop. Please let me know what you think.
> > > >>>
> > > >>>
> > > >>> Thanks a lot,
> > > >>> Marton
> > > >>>
> > > >>>
> > > ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >>> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>>
> > > >>
> > > >>
> > > >>
> > > ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> > >
> > >
> >
>
>
> --
> Weiwei Yang
>
--
John
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Mukul Kumar Singh <ms...@hortonworks.com>.
+1, Thanks for working on this Marton.
-Mukul
On 03/09/18, 9:02 AM, "John Zhuge" <jo...@gmail.com> wrote:
+1 Like the new site.
On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang <ab...@gmail.com> wrote:
> That's really nice, +1.
>
> --
> Weiwei
>
> On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wh...@gmail.com> wrote:
>
> > +1, thanks for working on this, Marton!
> >
> > Best,
> > Wangda
> >
> > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <aagarwal@hortonworks.com
> >
> > wrote:
> >
> > > +1
> > >
> > > Thanks for initiating this Marton.
> > >
> > >
> > > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
> > > hadoop.apache.org
> > >
> > > 3. I will sync manually all of the changes in the next two months
> > back
> > > to the svn site from the git (release announcements, new
> committers)
> > >
> > > IN CASE OF ANY PROBLEM we can switch back to the svn without any
> > > problem.
> > >
> > > If no-one objects within three days, I'll assume lazy consensus and
> > > start with this plan. Please comment if you have objections.
> > >
> > > Again: it allows immediate fallback at any time as svn repo will be
> > > kept
> > > as is (+ I will keep it up-to-date in the next 2 months)
> > >
> > > Thanks,
> > > Marton
> > >
> > >
> > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > > >
> > > > 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 tools.
> > > >
> > > > Hugo has more simple compared to jekyll. Just one binary, without
> > > > dependencies, works everywhere (mac, linux, windows)
> > > >
> > > > Hugo has much more powerful compared to "mvn site". Easier to
> > > create/use
> > > > more modern layout/theme, and easier to handle the content (for
> > > example
> > > > new release announcements could be generated as part of the
> release
> > > > process)
> > > >
> > > > I think it's very low risk to try out a new approach for the site
> > > (and
> > > > easy to rollback in case of problems)
> > > >
> > > > Marton
> > > >
> > > > ps: I just updated the patch/preview site with the recent
> releases:
> > > >
> > > > ***************************
> > > > * http://hadoop.anzix.net *
> > > > ***************************
> > > >
> > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > > >> 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
> > > >> feedback rapidly and get it in.
> > > >>
> > > >> For (2), how about we do it in a different way in the interest
> of
> > > >> progress?
> > > >> - We create a hadoop.apache.org/new-site/ where this new site
> > > goes.
> > > >> - We then modify the existing web-site to say that there is a
> > new
> > > >> site/experience that folks can click on a link and navigate to
> > > >> - As this new website matures and gets feedback & fixes, we
> > > finally
> > > >> pull the plug at a later point of time when we think we are good
> > to
> > > go.
> > > >>
> > > >> Thoughts?
> > > >>
> > > >> +Vinod
> > > >>
> > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org>
> > wrote:
> > > >>>
> > > >>> 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:
> > > >>>
> > > >>> This thread started long time ago to use a more modern hadoop
> > site:
> > > >>>
> > > >>> Goals were:
> > > >>>
> > > >>> 1. To make it easier to manage it (the release entries could be
> > > >>> created by a script as part of the release process)
> > > >>> 2. To use a better look-and-feel
> > > >>> 3. Move it out from svn to git
> > > >>>
> > > >>> I proposed to:
> > > >>>
> > > >>> 1. Move the existing site to git and generate it with hugo
> (which
> > > is
> > > >>> a single, standalone binary)
> > > >>> 2. Move both the rendered and source branches to git.
> > > >>> 3. (Create a jenkins job to generate the site automatically)
> > > >>>
> > > >>> NOTE: this is just about forrest based hadoop.apache.org, NOT
> > > about
> > > >>> the documentation which is generated by mvn-site (as before)
> > > >>>
> > > >>>
> > > >>> I got multiple valuable feedback and I improved the proposed
> site
> > > >>> according to the comments. Allen had some concerns about the
> used
> > > >>> technologies (hugo vs. mvn-site) and I answered all the
> questions
> > > why
> > > >>> I think mvn-site is the best for documentation and hugo is best
> > > for
> > > >>> generating site.
> > > >>>
> > > >>>
> > > >>> I would like to finish this effort/jira: I would like to start
> a
> > > >>> discussion about using this proposed version and approach as a
> > new
> > > >>> site of Apache Hadoop. Please let me know what you think.
> > > >>>
> > > >>>
> > > >>> Thanks a lot,
> > > >>> Marton
> > > >>>
> > > >>>
> > > ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >>> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>>
> > > >>
> > > >>
> > > >>
> > > ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> > >
> > >
> >
>
>
> --
> Weiwei Yang
>
--
John
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Mukul Kumar Singh <ms...@hortonworks.com>.
+1, Thanks for working on this Marton.
-Mukul
On 03/09/18, 9:02 AM, "John Zhuge" <jo...@gmail.com> wrote:
+1 Like the new site.
On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang <ab...@gmail.com> wrote:
> That's really nice, +1.
>
> --
> Weiwei
>
> On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wh...@gmail.com> wrote:
>
> > +1, thanks for working on this, Marton!
> >
> > Best,
> > Wangda
> >
> > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <aagarwal@hortonworks.com
> >
> > wrote:
> >
> > > +1
> > >
> > > Thanks for initiating this Marton.
> > >
> > >
> > > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
> > > hadoop.apache.org
> > >
> > > 3. I will sync manually all of the changes in the next two months
> > back
> > > to the svn site from the git (release announcements, new
> committers)
> > >
> > > IN CASE OF ANY PROBLEM we can switch back to the svn without any
> > > problem.
> > >
> > > If no-one objects within three days, I'll assume lazy consensus and
> > > start with this plan. Please comment if you have objections.
> > >
> > > Again: it allows immediate fallback at any time as svn repo will be
> > > kept
> > > as is (+ I will keep it up-to-date in the next 2 months)
> > >
> > > Thanks,
> > > Marton
> > >
> > >
> > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > > >
> > > > 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 tools.
> > > >
> > > > Hugo has more simple compared to jekyll. Just one binary, without
> > > > dependencies, works everywhere (mac, linux, windows)
> > > >
> > > > Hugo has much more powerful compared to "mvn site". Easier to
> > > create/use
> > > > more modern layout/theme, and easier to handle the content (for
> > > example
> > > > new release announcements could be generated as part of the
> release
> > > > process)
> > > >
> > > > I think it's very low risk to try out a new approach for the site
> > > (and
> > > > easy to rollback in case of problems)
> > > >
> > > > Marton
> > > >
> > > > ps: I just updated the patch/preview site with the recent
> releases:
> > > >
> > > > ***************************
> > > > * http://hadoop.anzix.net *
> > > > ***************************
> > > >
> > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > > >> 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
> > > >> feedback rapidly and get it in.
> > > >>
> > > >> For (2), how about we do it in a different way in the interest
> of
> > > >> progress?
> > > >> - We create a hadoop.apache.org/new-site/ where this new site
> > > goes.
> > > >> - We then modify the existing web-site to say that there is a
> > new
> > > >> site/experience that folks can click on a link and navigate to
> > > >> - As this new website matures and gets feedback & fixes, we
> > > finally
> > > >> pull the plug at a later point of time when we think we are good
> > to
> > > go.
> > > >>
> > > >> Thoughts?
> > > >>
> > > >> +Vinod
> > > >>
> > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org>
> > wrote:
> > > >>>
> > > >>> 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:
> > > >>>
> > > >>> This thread started long time ago to use a more modern hadoop
> > site:
> > > >>>
> > > >>> Goals were:
> > > >>>
> > > >>> 1. To make it easier to manage it (the release entries could be
> > > >>> created by a script as part of the release process)
> > > >>> 2. To use a better look-and-feel
> > > >>> 3. Move it out from svn to git
> > > >>>
> > > >>> I proposed to:
> > > >>>
> > > >>> 1. Move the existing site to git and generate it with hugo
> (which
> > > is
> > > >>> a single, standalone binary)
> > > >>> 2. Move both the rendered and source branches to git.
> > > >>> 3. (Create a jenkins job to generate the site automatically)
> > > >>>
> > > >>> NOTE: this is just about forrest based hadoop.apache.org, NOT
> > > about
> > > >>> the documentation which is generated by mvn-site (as before)
> > > >>>
> > > >>>
> > > >>> I got multiple valuable feedback and I improved the proposed
> site
> > > >>> according to the comments. Allen had some concerns about the
> used
> > > >>> technologies (hugo vs. mvn-site) and I answered all the
> questions
> > > why
> > > >>> I think mvn-site is the best for documentation and hugo is best
> > > for
> > > >>> generating site.
> > > >>>
> > > >>>
> > > >>> I would like to finish this effort/jira: I would like to start
> a
> > > >>> discussion about using this proposed version and approach as a
> > new
> > > >>> site of Apache Hadoop. Please let me know what you think.
> > > >>>
> > > >>>
> > > >>> Thanks a lot,
> > > >>> Marton
> > > >>>
> > > >>>
> > > ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >>> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>>
> > > >>
> > > >>
> > > >>
> > > ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> > >
> > >
> >
>
>
> --
> Weiwei Yang
>
--
John
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by John Zhuge <jo...@gmail.com>.
+1 Like the new site.
On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang <ab...@gmail.com> wrote:
> That's really nice, +1.
>
> --
> Weiwei
>
> On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wh...@gmail.com> wrote:
>
> > +1, thanks for working on this, Marton!
> >
> > Best,
> > Wangda
> >
> > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <aagarwal@hortonworks.com
> >
> > wrote:
> >
> > > +1
> > >
> > > Thanks for initiating this Marton.
> > >
> > >
> > > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
> > > hadoop.apache.org
> > >
> > > 3. I will sync manually all of the changes in the next two months
> > back
> > > to the svn site from the git (release announcements, new
> committers)
> > >
> > > IN CASE OF ANY PROBLEM we can switch back to the svn without any
> > > problem.
> > >
> > > If no-one objects within three days, I'll assume lazy consensus and
> > > start with this plan. Please comment if you have objections.
> > >
> > > Again: it allows immediate fallback at any time as svn repo will be
> > > kept
> > > as is (+ I will keep it up-to-date in the next 2 months)
> > >
> > > Thanks,
> > > Marton
> > >
> > >
> > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > > >
> > > > 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 tools.
> > > >
> > > > Hugo has more simple compared to jekyll. Just one binary, without
> > > > dependencies, works everywhere (mac, linux, windows)
> > > >
> > > > Hugo has much more powerful compared to "mvn site". Easier to
> > > create/use
> > > > more modern layout/theme, and easier to handle the content (for
> > > example
> > > > new release announcements could be generated as part of the
> release
> > > > process)
> > > >
> > > > I think it's very low risk to try out a new approach for the site
> > > (and
> > > > easy to rollback in case of problems)
> > > >
> > > > Marton
> > > >
> > > > ps: I just updated the patch/preview site with the recent
> releases:
> > > >
> > > > ***************************
> > > > * http://hadoop.anzix.net *
> > > > ***************************
> > > >
> > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > > >> 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
> > > >> feedback rapidly and get it in.
> > > >>
> > > >> For (2), how about we do it in a different way in the interest
> of
> > > >> progress?
> > > >> - We create a hadoop.apache.org/new-site/ where this new site
> > > goes.
> > > >> - We then modify the existing web-site to say that there is a
> > new
> > > >> site/experience that folks can click on a link and navigate to
> > > >> - As this new website matures and gets feedback & fixes, we
> > > finally
> > > >> pull the plug at a later point of time when we think we are good
> > to
> > > go.
> > > >>
> > > >> Thoughts?
> > > >>
> > > >> +Vinod
> > > >>
> > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org>
> > wrote:
> > > >>>
> > > >>> 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:
> > > >>>
> > > >>> This thread started long time ago to use a more modern hadoop
> > site:
> > > >>>
> > > >>> Goals were:
> > > >>>
> > > >>> 1. To make it easier to manage it (the release entries could be
> > > >>> created by a script as part of the release process)
> > > >>> 2. To use a better look-and-feel
> > > >>> 3. Move it out from svn to git
> > > >>>
> > > >>> I proposed to:
> > > >>>
> > > >>> 1. Move the existing site to git and generate it with hugo
> (which
> > > is
> > > >>> a single, standalone binary)
> > > >>> 2. Move both the rendered and source branches to git.
> > > >>> 3. (Create a jenkins job to generate the site automatically)
> > > >>>
> > > >>> NOTE: this is just about forrest based hadoop.apache.org, NOT
> > > about
> > > >>> the documentation which is generated by mvn-site (as before)
> > > >>>
> > > >>>
> > > >>> I got multiple valuable feedback and I improved the proposed
> site
> > > >>> according to the comments. Allen had some concerns about the
> used
> > > >>> technologies (hugo vs. mvn-site) and I answered all the
> questions
> > > why
> > > >>> I think mvn-site is the best for documentation and hugo is best
> > > for
> > > >>> generating site.
> > > >>>
> > > >>>
> > > >>> I would like to finish this effort/jira: I would like to start
> a
> > > >>> discussion about using this proposed version and approach as a
> > new
> > > >>> site of Apache Hadoop. Please let me know what you think.
> > > >>>
> > > >>>
> > > >>> Thanks a lot,
> > > >>> Marton
> > > >>>
> > > >>>
> > > ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >>> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>>
> > > >>
> > > >>
> > > >>
> > > ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> > >
> > >
> >
>
>
> --
> Weiwei Yang
>
--
John
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by John Zhuge <jo...@gmail.com>.
+1 Like the new site.
On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang <ab...@gmail.com> wrote:
> That's really nice, +1.
>
> --
> Weiwei
>
> On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wh...@gmail.com> wrote:
>
> > +1, thanks for working on this, Marton!
> >
> > Best,
> > Wangda
> >
> > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <aagarwal@hortonworks.com
> >
> > wrote:
> >
> > > +1
> > >
> > > Thanks for initiating this Marton.
> > >
> > >
> > > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
> > > hadoop.apache.org
> > >
> > > 3. I will sync manually all of the changes in the next two months
> > back
> > > to the svn site from the git (release announcements, new
> committers)
> > >
> > > IN CASE OF ANY PROBLEM we can switch back to the svn without any
> > > problem.
> > >
> > > If no-one objects within three days, I'll assume lazy consensus and
> > > start with this plan. Please comment if you have objections.
> > >
> > > Again: it allows immediate fallback at any time as svn repo will be
> > > kept
> > > as is (+ I will keep it up-to-date in the next 2 months)
> > >
> > > Thanks,
> > > Marton
> > >
> > >
> > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > > >
> > > > 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 tools.
> > > >
> > > > Hugo has more simple compared to jekyll. Just one binary, without
> > > > dependencies, works everywhere (mac, linux, windows)
> > > >
> > > > Hugo has much more powerful compared to "mvn site". Easier to
> > > create/use
> > > > more modern layout/theme, and easier to handle the content (for
> > > example
> > > > new release announcements could be generated as part of the
> release
> > > > process)
> > > >
> > > > I think it's very low risk to try out a new approach for the site
> > > (and
> > > > easy to rollback in case of problems)
> > > >
> > > > Marton
> > > >
> > > > ps: I just updated the patch/preview site with the recent
> releases:
> > > >
> > > > ***************************
> > > > * http://hadoop.anzix.net *
> > > > ***************************
> > > >
> > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > > >> 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
> > > >> feedback rapidly and get it in.
> > > >>
> > > >> For (2), how about we do it in a different way in the interest
> of
> > > >> progress?
> > > >> - We create a hadoop.apache.org/new-site/ where this new site
> > > goes.
> > > >> - We then modify the existing web-site to say that there is a
> > new
> > > >> site/experience that folks can click on a link and navigate to
> > > >> - As this new website matures and gets feedback & fixes, we
> > > finally
> > > >> pull the plug at a later point of time when we think we are good
> > to
> > > go.
> > > >>
> > > >> Thoughts?
> > > >>
> > > >> +Vinod
> > > >>
> > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org>
> > wrote:
> > > >>>
> > > >>> 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:
> > > >>>
> > > >>> This thread started long time ago to use a more modern hadoop
> > site:
> > > >>>
> > > >>> Goals were:
> > > >>>
> > > >>> 1. To make it easier to manage it (the release entries could be
> > > >>> created by a script as part of the release process)
> > > >>> 2. To use a better look-and-feel
> > > >>> 3. Move it out from svn to git
> > > >>>
> > > >>> I proposed to:
> > > >>>
> > > >>> 1. Move the existing site to git and generate it with hugo
> (which
> > > is
> > > >>> a single, standalone binary)
> > > >>> 2. Move both the rendered and source branches to git.
> > > >>> 3. (Create a jenkins job to generate the site automatically)
> > > >>>
> > > >>> NOTE: this is just about forrest based hadoop.apache.org, NOT
> > > about
> > > >>> the documentation which is generated by mvn-site (as before)
> > > >>>
> > > >>>
> > > >>> I got multiple valuable feedback and I improved the proposed
> site
> > > >>> according to the comments. Allen had some concerns about the
> used
> > > >>> technologies (hugo vs. mvn-site) and I answered all the
> questions
> > > why
> > > >>> I think mvn-site is the best for documentation and hugo is best
> > > for
> > > >>> generating site.
> > > >>>
> > > >>>
> > > >>> I would like to finish this effort/jira: I would like to start
> a
> > > >>> discussion about using this proposed version and approach as a
> > new
> > > >>> site of Apache Hadoop. Please let me know what you think.
> > > >>>
> > > >>>
> > > >>> Thanks a lot,
> > > >>> Marton
> > > >>>
> > > >>>
> > > ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >>> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>>
> > > >>
> > > >>
> > > >>
> > > ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> > >
> > >
> >
>
>
> --
> Weiwei Yang
>
--
John
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by John Zhuge <jo...@gmail.com>.
+1 Like the new site.
On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang <ab...@gmail.com> wrote:
> That's really nice, +1.
>
> --
> Weiwei
>
> On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wh...@gmail.com> wrote:
>
> > +1, thanks for working on this, Marton!
> >
> > Best,
> > Wangda
> >
> > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <aagarwal@hortonworks.com
> >
> > wrote:
> >
> > > +1
> > >
> > > Thanks for initiating this Marton.
> > >
> > >
> > > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
> > > hadoop.apache.org
> > >
> > > 3. I will sync manually all of the changes in the next two months
> > back
> > > to the svn site from the git (release announcements, new
> committers)
> > >
> > > IN CASE OF ANY PROBLEM we can switch back to the svn without any
> > > problem.
> > >
> > > If no-one objects within three days, I'll assume lazy consensus and
> > > start with this plan. Please comment if you have objections.
> > >
> > > Again: it allows immediate fallback at any time as svn repo will be
> > > kept
> > > as is (+ I will keep it up-to-date in the next 2 months)
> > >
> > > Thanks,
> > > Marton
> > >
> > >
> > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > > >
> > > > 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 tools.
> > > >
> > > > Hugo has more simple compared to jekyll. Just one binary, without
> > > > dependencies, works everywhere (mac, linux, windows)
> > > >
> > > > Hugo has much more powerful compared to "mvn site". Easier to
> > > create/use
> > > > more modern layout/theme, and easier to handle the content (for
> > > example
> > > > new release announcements could be generated as part of the
> release
> > > > process)
> > > >
> > > > I think it's very low risk to try out a new approach for the site
> > > (and
> > > > easy to rollback in case of problems)
> > > >
> > > > Marton
> > > >
> > > > ps: I just updated the patch/preview site with the recent
> releases:
> > > >
> > > > ***************************
> > > > * http://hadoop.anzix.net *
> > > > ***************************
> > > >
> > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > > >> 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
> > > >> feedback rapidly and get it in.
> > > >>
> > > >> For (2), how about we do it in a different way in the interest
> of
> > > >> progress?
> > > >> - We create a hadoop.apache.org/new-site/ where this new site
> > > goes.
> > > >> - We then modify the existing web-site to say that there is a
> > new
> > > >> site/experience that folks can click on a link and navigate to
> > > >> - As this new website matures and gets feedback & fixes, we
> > > finally
> > > >> pull the plug at a later point of time when we think we are good
> > to
> > > go.
> > > >>
> > > >> Thoughts?
> > > >>
> > > >> +Vinod
> > > >>
> > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org>
> > wrote:
> > > >>>
> > > >>> 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:
> > > >>>
> > > >>> This thread started long time ago to use a more modern hadoop
> > site:
> > > >>>
> > > >>> Goals were:
> > > >>>
> > > >>> 1. To make it easier to manage it (the release entries could be
> > > >>> created by a script as part of the release process)
> > > >>> 2. To use a better look-and-feel
> > > >>> 3. Move it out from svn to git
> > > >>>
> > > >>> I proposed to:
> > > >>>
> > > >>> 1. Move the existing site to git and generate it with hugo
> (which
> > > is
> > > >>> a single, standalone binary)
> > > >>> 2. Move both the rendered and source branches to git.
> > > >>> 3. (Create a jenkins job to generate the site automatically)
> > > >>>
> > > >>> NOTE: this is just about forrest based hadoop.apache.org, NOT
> > > about
> > > >>> the documentation which is generated by mvn-site (as before)
> > > >>>
> > > >>>
> > > >>> I got multiple valuable feedback and I improved the proposed
> site
> > > >>> according to the comments. Allen had some concerns about the
> used
> > > >>> technologies (hugo vs. mvn-site) and I answered all the
> questions
> > > why
> > > >>> I think mvn-site is the best for documentation and hugo is best
> > > for
> > > >>> generating site.
> > > >>>
> > > >>>
> > > >>> I would like to finish this effort/jira: I would like to start
> a
> > > >>> discussion about using this proposed version and approach as a
> > new
> > > >>> site of Apache Hadoop. Please let me know what you think.
> > > >>>
> > > >>>
> > > >>> Thanks a lot,
> > > >>> Marton
> > > >>>
> > > >>>
> > > ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >>> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>>
> > > >>
> > > >>
> > > >>
> > > ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> > >
> > >
> >
>
>
> --
> Weiwei Yang
>
--
John
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by John Zhuge <jo...@gmail.com>.
+1 Like the new site.
On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang <ab...@gmail.com> wrote:
> That's really nice, +1.
>
> --
> Weiwei
>
> On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wh...@gmail.com> wrote:
>
> > +1, thanks for working on this, Marton!
> >
> > Best,
> > Wangda
> >
> > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <aagarwal@hortonworks.com
> >
> > wrote:
> >
> > > +1
> > >
> > > Thanks for initiating this Marton.
> > >
> > >
> > > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
> > > hadoop.apache.org
> > >
> > > 3. I will sync manually all of the changes in the next two months
> > back
> > > to the svn site from the git (release announcements, new
> committers)
> > >
> > > IN CASE OF ANY PROBLEM we can switch back to the svn without any
> > > problem.
> > >
> > > If no-one objects within three days, I'll assume lazy consensus and
> > > start with this plan. Please comment if you have objections.
> > >
> > > Again: it allows immediate fallback at any time as svn repo will be
> > > kept
> > > as is (+ I will keep it up-to-date in the next 2 months)
> > >
> > > Thanks,
> > > Marton
> > >
> > >
> > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > > >
> > > > 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 tools.
> > > >
> > > > Hugo has more simple compared to jekyll. Just one binary, without
> > > > dependencies, works everywhere (mac, linux, windows)
> > > >
> > > > Hugo has much more powerful compared to "mvn site". Easier to
> > > create/use
> > > > more modern layout/theme, and easier to handle the content (for
> > > example
> > > > new release announcements could be generated as part of the
> release
> > > > process)
> > > >
> > > > I think it's very low risk to try out a new approach for the site
> > > (and
> > > > easy to rollback in case of problems)
> > > >
> > > > Marton
> > > >
> > > > ps: I just updated the patch/preview site with the recent
> releases:
> > > >
> > > > ***************************
> > > > * http://hadoop.anzix.net *
> > > > ***************************
> > > >
> > > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > > >> 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
> > > >> feedback rapidly and get it in.
> > > >>
> > > >> For (2), how about we do it in a different way in the interest
> of
> > > >> progress?
> > > >> - We create a hadoop.apache.org/new-site/ where this new site
> > > goes.
> > > >> - We then modify the existing web-site to say that there is a
> > new
> > > >> site/experience that folks can click on a link and navigate to
> > > >> - As this new website matures and gets feedback & fixes, we
> > > finally
> > > >> pull the plug at a later point of time when we think we are good
> > to
> > > go.
> > > >>
> > > >> Thoughts?
> > > >>
> > > >> +Vinod
> > > >>
> > > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org>
> > wrote:
> > > >>>
> > > >>> 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:
> > > >>>
> > > >>> This thread started long time ago to use a more modern hadoop
> > site:
> > > >>>
> > > >>> Goals were:
> > > >>>
> > > >>> 1. To make it easier to manage it (the release entries could be
> > > >>> created by a script as part of the release process)
> > > >>> 2. To use a better look-and-feel
> > > >>> 3. Move it out from svn to git
> > > >>>
> > > >>> I proposed to:
> > > >>>
> > > >>> 1. Move the existing site to git and generate it with hugo
> (which
> > > is
> > > >>> a single, standalone binary)
> > > >>> 2. Move both the rendered and source branches to git.
> > > >>> 3. (Create a jenkins job to generate the site automatically)
> > > >>>
> > > >>> NOTE: this is just about forrest based hadoop.apache.org, NOT
> > > about
> > > >>> the documentation which is generated by mvn-site (as before)
> > > >>>
> > > >>>
> > > >>> I got multiple valuable feedback and I improved the proposed
> site
> > > >>> according to the comments. Allen had some concerns about the
> used
> > > >>> technologies (hugo vs. mvn-site) and I answered all the
> questions
> > > why
> > > >>> I think mvn-site is the best for documentation and hugo is best
> > > for
> > > >>> generating site.
> > > >>>
> > > >>>
> > > >>> I would like to finish this effort/jira: I would like to start
> a
> > > >>> discussion about using this proposed version and approach as a
> > new
> > > >>> site of Apache Hadoop. Please let me know what you think.
> > > >>>
> > > >>>
> > > >>> Thanks a lot,
> > > >>> Marton
> > > >>>
> > > >>>
> > > ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >>> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>>
> > > >>
> > > >>
> > > >>
> > > ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail:
> common-dev-unsubscribe@hadoop.apache.org
> > > >> For additional commands, e-mail:
> > common-dev-help@hadoop.apache.org
> > > >>
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > >
> > >
> > >
> >
>
>
> --
> Weiwei Yang
>
--
John
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Weiwei Yang <ab...@gmail.com>.
That's really nice, +1.
--
Weiwei
On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wh...@gmail.com> wrote:
> +1, thanks for working on this, Marton!
>
> Best,
> Wangda
>
> On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <aa...@hortonworks.com>
> wrote:
>
> > +1
> >
> > Thanks for initiating this Marton.
> >
> >
> > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
> > hadoop.apache.org
> >
> > 3. I will sync manually all of the changes in the next two months
> back
> > to the svn site from the git (release announcements, new committers)
> >
> > IN CASE OF ANY PROBLEM we can switch back to the svn without any
> > problem.
> >
> > If no-one objects within three days, I'll assume lazy consensus and
> > start with this plan. Please comment if you have objections.
> >
> > Again: it allows immediate fallback at any time as svn repo will be
> > kept
> > as is (+ I will keep it up-to-date in the next 2 months)
> >
> > Thanks,
> > Marton
> >
> >
> > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > >
> > > 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 tools.
> > >
> > > Hugo has more simple compared to jekyll. Just one binary, without
> > > dependencies, works everywhere (mac, linux, windows)
> > >
> > > Hugo has much more powerful compared to "mvn site". Easier to
> > create/use
> > > more modern layout/theme, and easier to handle the content (for
> > example
> > > new release announcements could be generated as part of the release
> > > process)
> > >
> > > I think it's very low risk to try out a new approach for the site
> > (and
> > > easy to rollback in case of problems)
> > >
> > > Marton
> > >
> > > ps: I just updated the patch/preview site with the recent releases:
> > >
> > > ***************************
> > > * http://hadoop.anzix.net *
> > > ***************************
> > >
> > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > >> 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
> > >> feedback rapidly and get it in.
> > >>
> > >> For (2), how about we do it in a different way in the interest of
> > >> progress?
> > >> - We create a hadoop.apache.org/new-site/ where this new site
> > goes.
> > >> - We then modify the existing web-site to say that there is a
> new
> > >> site/experience that folks can click on a link and navigate to
> > >> - As this new website matures and gets feedback & fixes, we
> > finally
> > >> pull the plug at a later point of time when we think we are good
> to
> > go.
> > >>
> > >> Thoughts?
> > >>
> > >> +Vinod
> > >>
> > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org>
> wrote:
> > >>>
> > >>> 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:
> > >>>
> > >>> This thread started long time ago to use a more modern hadoop
> site:
> > >>>
> > >>> Goals were:
> > >>>
> > >>> 1. To make it easier to manage it (the release entries could be
> > >>> created by a script as part of the release process)
> > >>> 2. To use a better look-and-feel
> > >>> 3. Move it out from svn to git
> > >>>
> > >>> I proposed to:
> > >>>
> > >>> 1. Move the existing site to git and generate it with hugo (which
> > is
> > >>> a single, standalone binary)
> > >>> 2. Move both the rendered and source branches to git.
> > >>> 3. (Create a jenkins job to generate the site automatically)
> > >>>
> > >>> NOTE: this is just about forrest based hadoop.apache.org, NOT
> > about
> > >>> the documentation which is generated by mvn-site (as before)
> > >>>
> > >>>
> > >>> I got multiple valuable feedback and I improved the proposed site
> > >>> according to the comments. Allen had some concerns about the used
> > >>> technologies (hugo vs. mvn-site) and I answered all the questions
> > why
> > >>> I think mvn-site is the best for documentation and hugo is best
> > for
> > >>> generating site.
> > >>>
> > >>>
> > >>> I would like to finish this effort/jira: I would like to start a
> > >>> discussion about using this proposed version and approach as a
> new
> > >>> site of Apache Hadoop. Please let me know what you think.
> > >>>
> > >>>
> > >>> Thanks a lot,
> > >>> Marton
> > >>>
> > >>>
> > ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > >>> For additional commands, e-mail:
> common-dev-help@hadoop.apache.org
> > >>>
> > >>
> > >>
> > >>
> > ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > >> For additional commands, e-mail:
> common-dev-help@hadoop.apache.org
> > >>
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> >
> >
> >
> >
>
--
Weiwei Yang
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Weiwei Yang <ab...@gmail.com>.
That's really nice, +1.
--
Weiwei
On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan <wh...@gmail.com> wrote:
> +1, thanks for working on this, Marton!
>
> Best,
> Wangda
>
> On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <aa...@hortonworks.com>
> wrote:
>
> > +1
> >
> > Thanks for initiating this Marton.
> >
> >
> > On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
> > hadoop.apache.org
> >
> > 3. I will sync manually all of the changes in the next two months
> back
> > to the svn site from the git (release announcements, new committers)
> >
> > IN CASE OF ANY PROBLEM we can switch back to the svn without any
> > problem.
> >
> > If no-one objects within three days, I'll assume lazy consensus and
> > start with this plan. Please comment if you have objections.
> >
> > Again: it allows immediate fallback at any time as svn repo will be
> > kept
> > as is (+ I will keep it up-to-date in the next 2 months)
> >
> > Thanks,
> > Marton
> >
> >
> > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > >
> > > 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 tools.
> > >
> > > Hugo has more simple compared to jekyll. Just one binary, without
> > > dependencies, works everywhere (mac, linux, windows)
> > >
> > > Hugo has much more powerful compared to "mvn site". Easier to
> > create/use
> > > more modern layout/theme, and easier to handle the content (for
> > example
> > > new release announcements could be generated as part of the release
> > > process)
> > >
> > > I think it's very low risk to try out a new approach for the site
> > (and
> > > easy to rollback in case of problems)
> > >
> > > Marton
> > >
> > > ps: I just updated the patch/preview site with the recent releases:
> > >
> > > ***************************
> > > * http://hadoop.anzix.net *
> > > ***************************
> > >
> > > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > >> 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
> > >> feedback rapidly and get it in.
> > >>
> > >> For (2), how about we do it in a different way in the interest of
> > >> progress?
> > >> - We create a hadoop.apache.org/new-site/ where this new site
> > goes.
> > >> - We then modify the existing web-site to say that there is a
> new
> > >> site/experience that folks can click on a link and navigate to
> > >> - As this new website matures and gets feedback & fixes, we
> > finally
> > >> pull the plug at a later point of time when we think we are good
> to
> > go.
> > >>
> > >> Thoughts?
> > >>
> > >> +Vinod
> > >>
> > >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org>
> wrote:
> > >>>
> > >>> 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:
> > >>>
> > >>> This thread started long time ago to use a more modern hadoop
> site:
> > >>>
> > >>> Goals were:
> > >>>
> > >>> 1. To make it easier to manage it (the release entries could be
> > >>> created by a script as part of the release process)
> > >>> 2. To use a better look-and-feel
> > >>> 3. Move it out from svn to git
> > >>>
> > >>> I proposed to:
> > >>>
> > >>> 1. Move the existing site to git and generate it with hugo (which
> > is
> > >>> a single, standalone binary)
> > >>> 2. Move both the rendered and source branches to git.
> > >>> 3. (Create a jenkins job to generate the site automatically)
> > >>>
> > >>> NOTE: this is just about forrest based hadoop.apache.org, NOT
> > about
> > >>> the documentation which is generated by mvn-site (as before)
> > >>>
> > >>>
> > >>> I got multiple valuable feedback and I improved the proposed site
> > >>> according to the comments. Allen had some concerns about the used
> > >>> technologies (hugo vs. mvn-site) and I answered all the questions
> > why
> > >>> I think mvn-site is the best for documentation and hugo is best
> > for
> > >>> generating site.
> > >>>
> > >>>
> > >>> I would like to finish this effort/jira: I would like to start a
> > >>> discussion about using this proposed version and approach as a
> new
> > >>> site of Apache Hadoop. Please let me know what you think.
> > >>>
> > >>>
> > >>> Thanks a lot,
> > >>> Marton
> > >>>
> > >>>
> > ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > >>> For additional commands, e-mail:
> common-dev-help@hadoop.apache.org
> > >>>
> > >>
> > >>
> > >>
> > ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > >> For additional commands, e-mail:
> common-dev-help@hadoop.apache.org
> > >>
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> >
> >
> >
> >
>
--
Weiwei Yang
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Wangda Tan <wh...@gmail.com>.
+1, thanks for working on this, Marton!
Best,
Wangda
On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <aa...@hortonworks.com>
wrote:
> +1
>
> Thanks for initiating this Marton.
>
>
> On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any
> problem.
>
> If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be
> kept
> as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
> >
> > 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 tools.
> >
> > Hugo has more simple compared to jekyll. Just one binary, without
> > dependencies, works everywhere (mac, linux, windows)
> >
> > Hugo has much more powerful compared to "mvn site". Easier to
> create/use
> > more modern layout/theme, and easier to handle the content (for
> example
> > new release announcements could be generated as part of the release
> > process)
> >
> > I think it's very low risk to try out a new approach for the site
> (and
> > easy to rollback in case of problems)
> >
> > Marton
> >
> > ps: I just updated the patch/preview site with the recent releases:
> >
> > ***************************
> > * http://hadoop.anzix.net *
> > ***************************
> >
> > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> >> 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
> >> feedback rapidly and get it in.
> >>
> >> For (2), how about we do it in a different way in the interest of
> >> progress?
> >> - We create a hadoop.apache.org/new-site/ where this new site
> goes.
> >> - We then modify the existing web-site to say that there is a new
> >> site/experience that folks can click on a link and navigate to
> >> - As this new website matures and gets feedback & fixes, we
> finally
> >> pull the plug at a later point of time when we think we are good to
> go.
> >>
> >> Thoughts?
> >>
> >> +Vinod
> >>
> >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> >>>
> >>> 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:
> >>>
> >>> This thread started long time ago to use a more modern hadoop site:
> >>>
> >>> Goals were:
> >>>
> >>> 1. To make it easier to manage it (the release entries could be
> >>> created by a script as part of the release process)
> >>> 2. To use a better look-and-feel
> >>> 3. Move it out from svn to git
> >>>
> >>> I proposed to:
> >>>
> >>> 1. Move the existing site to git and generate it with hugo (which
> is
> >>> a single, standalone binary)
> >>> 2. Move both the rendered and source branches to git.
> >>> 3. (Create a jenkins job to generate the site automatically)
> >>>
> >>> NOTE: this is just about forrest based hadoop.apache.org, NOT
> about
> >>> the documentation which is generated by mvn-site (as before)
> >>>
> >>>
> >>> I got multiple valuable feedback and I improved the proposed site
> >>> according to the comments. Allen had some concerns about the used
> >>> technologies (hugo vs. mvn-site) and I answered all the questions
> why
> >>> I think mvn-site is the best for documentation and hugo is best
> for
> >>> generating site.
> >>>
> >>>
> >>> I would like to finish this effort/jira: I would like to start a
> >>> discussion about using this proposed version and approach as a new
> >>> site of Apache Hadoop. Please let me know what you think.
> >>>
> >>>
> >>> Thanks a lot,
> >>> Marton
> >>>
> >>>
> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
>
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Wangda Tan <wh...@gmail.com>.
+1, thanks for working on this, Marton!
Best,
Wangda
On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <aa...@hortonworks.com>
wrote:
> +1
>
> Thanks for initiating this Marton.
>
>
> On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any
> problem.
>
> If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be
> kept
> as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
> >
> > 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 tools.
> >
> > Hugo has more simple compared to jekyll. Just one binary, without
> > dependencies, works everywhere (mac, linux, windows)
> >
> > Hugo has much more powerful compared to "mvn site". Easier to
> create/use
> > more modern layout/theme, and easier to handle the content (for
> example
> > new release announcements could be generated as part of the release
> > process)
> >
> > I think it's very low risk to try out a new approach for the site
> (and
> > easy to rollback in case of problems)
> >
> > Marton
> >
> > ps: I just updated the patch/preview site with the recent releases:
> >
> > ***************************
> > * http://hadoop.anzix.net *
> > ***************************
> >
> > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> >> 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
> >> feedback rapidly and get it in.
> >>
> >> For (2), how about we do it in a different way in the interest of
> >> progress?
> >> - We create a hadoop.apache.org/new-site/ where this new site
> goes.
> >> - We then modify the existing web-site to say that there is a new
> >> site/experience that folks can click on a link and navigate to
> >> - As this new website matures and gets feedback & fixes, we
> finally
> >> pull the plug at a later point of time when we think we are good to
> go.
> >>
> >> Thoughts?
> >>
> >> +Vinod
> >>
> >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> >>>
> >>> 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:
> >>>
> >>> This thread started long time ago to use a more modern hadoop site:
> >>>
> >>> Goals were:
> >>>
> >>> 1. To make it easier to manage it (the release entries could be
> >>> created by a script as part of the release process)
> >>> 2. To use a better look-and-feel
> >>> 3. Move it out from svn to git
> >>>
> >>> I proposed to:
> >>>
> >>> 1. Move the existing site to git and generate it with hugo (which
> is
> >>> a single, standalone binary)
> >>> 2. Move both the rendered and source branches to git.
> >>> 3. (Create a jenkins job to generate the site automatically)
> >>>
> >>> NOTE: this is just about forrest based hadoop.apache.org, NOT
> about
> >>> the documentation which is generated by mvn-site (as before)
> >>>
> >>>
> >>> I got multiple valuable feedback and I improved the proposed site
> >>> according to the comments. Allen had some concerns about the used
> >>> technologies (hugo vs. mvn-site) and I answered all the questions
> why
> >>> I think mvn-site is the best for documentation and hugo is best
> for
> >>> generating site.
> >>>
> >>>
> >>> I would like to finish this effort/jira: I would like to start a
> >>> discussion about using this proposed version and approach as a new
> >>> site of Apache Hadoop. Please let me know what you think.
> >>>
> >>>
> >>> Thanks a lot,
> >>> Marton
> >>>
> >>>
> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
>
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Wangda Tan <wh...@gmail.com>.
+1, thanks for working on this, Marton!
Best,
Wangda
On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <aa...@hortonworks.com>
wrote:
> +1
>
> Thanks for initiating this Marton.
>
>
> On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any
> problem.
>
> If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be
> kept
> as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
> >
> > 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 tools.
> >
> > Hugo has more simple compared to jekyll. Just one binary, without
> > dependencies, works everywhere (mac, linux, windows)
> >
> > Hugo has much more powerful compared to "mvn site". Easier to
> create/use
> > more modern layout/theme, and easier to handle the content (for
> example
> > new release announcements could be generated as part of the release
> > process)
> >
> > I think it's very low risk to try out a new approach for the site
> (and
> > easy to rollback in case of problems)
> >
> > Marton
> >
> > ps: I just updated the patch/preview site with the recent releases:
> >
> > ***************************
> > * http://hadoop.anzix.net *
> > ***************************
> >
> > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> >> 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
> >> feedback rapidly and get it in.
> >>
> >> For (2), how about we do it in a different way in the interest of
> >> progress?
> >> - We create a hadoop.apache.org/new-site/ where this new site
> goes.
> >> - We then modify the existing web-site to say that there is a new
> >> site/experience that folks can click on a link and navigate to
> >> - As this new website matures and gets feedback & fixes, we
> finally
> >> pull the plug at a later point of time when we think we are good to
> go.
> >>
> >> Thoughts?
> >>
> >> +Vinod
> >>
> >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> >>>
> >>> 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:
> >>>
> >>> This thread started long time ago to use a more modern hadoop site:
> >>>
> >>> Goals were:
> >>>
> >>> 1. To make it easier to manage it (the release entries could be
> >>> created by a script as part of the release process)
> >>> 2. To use a better look-and-feel
> >>> 3. Move it out from svn to git
> >>>
> >>> I proposed to:
> >>>
> >>> 1. Move the existing site to git and generate it with hugo (which
> is
> >>> a single, standalone binary)
> >>> 2. Move both the rendered and source branches to git.
> >>> 3. (Create a jenkins job to generate the site automatically)
> >>>
> >>> NOTE: this is just about forrest based hadoop.apache.org, NOT
> about
> >>> the documentation which is generated by mvn-site (as before)
> >>>
> >>>
> >>> I got multiple valuable feedback and I improved the proposed site
> >>> according to the comments. Allen had some concerns about the used
> >>> technologies (hugo vs. mvn-site) and I answered all the questions
> why
> >>> I think mvn-site is the best for documentation and hugo is best
> for
> >>> generating site.
> >>>
> >>>
> >>> I would like to finish this effort/jira: I would like to start a
> >>> discussion about using this proposed version and approach as a new
> >>> site of Apache Hadoop. Please let me know what you think.
> >>>
> >>>
> >>> Thanks a lot,
> >>> Marton
> >>>
> >>>
> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
>
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Wangda Tan <wh...@gmail.com>.
+1, thanks for working on this, Marton!
Best,
Wangda
On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal <aa...@hortonworks.com>
wrote:
> +1
>
> Thanks for initiating this Marton.
>
>
> On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any
> problem.
>
> If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be
> kept
> as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
> >
> > 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 tools.
> >
> > Hugo has more simple compared to jekyll. Just one binary, without
> > dependencies, works everywhere (mac, linux, windows)
> >
> > Hugo has much more powerful compared to "mvn site". Easier to
> create/use
> > more modern layout/theme, and easier to handle the content (for
> example
> > new release announcements could be generated as part of the release
> > process)
> >
> > I think it's very low risk to try out a new approach for the site
> (and
> > easy to rollback in case of problems)
> >
> > Marton
> >
> > ps: I just updated the patch/preview site with the recent releases:
> >
> > ***************************
> > * http://hadoop.anzix.net *
> > ***************************
> >
> > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> >> 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
> >> feedback rapidly and get it in.
> >>
> >> For (2), how about we do it in a different way in the interest of
> >> progress?
> >> - We create a hadoop.apache.org/new-site/ where this new site
> goes.
> >> - We then modify the existing web-site to say that there is a new
> >> site/experience that folks can click on a link and navigate to
> >> - As this new website matures and gets feedback & fixes, we
> finally
> >> pull the plug at a later point of time when we think we are good to
> go.
> >>
> >> Thoughts?
> >>
> >> +Vinod
> >>
> >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> >>>
> >>> 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:
> >>>
> >>> This thread started long time ago to use a more modern hadoop site:
> >>>
> >>> Goals were:
> >>>
> >>> 1. To make it easier to manage it (the release entries could be
> >>> created by a script as part of the release process)
> >>> 2. To use a better look-and-feel
> >>> 3. Move it out from svn to git
> >>>
> >>> I proposed to:
> >>>
> >>> 1. Move the existing site to git and generate it with hugo (which
> is
> >>> a single, standalone binary)
> >>> 2. Move both the rendered and source branches to git.
> >>> 3. (Create a jenkins job to generate the site automatically)
> >>>
> >>> NOTE: this is just about forrest based hadoop.apache.org, NOT
> about
> >>> the documentation which is generated by mvn-site (as before)
> >>>
> >>>
> >>> I got multiple valuable feedback and I improved the proposed site
> >>> according to the comments. Allen had some concerns about the used
> >>> technologies (hugo vs. mvn-site) and I answered all the questions
> why
> >>> I think mvn-site is the best for documentation and hugo is best
> for
> >>> generating site.
> >>>
> >>>
> >>> I would like to finish this effort/jira: I would like to start a
> >>> discussion about using this proposed version and approach as a new
> >>> site of Apache Hadoop. Please let me know what you think.
> >>>
> >>>
> >>> Thanks a lot,
> >>> Marton
> >>>
> >>>
> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
>
>
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Arpit Agarwal <aa...@hortonworks.com>.
+1
Thanks for initiating this Marton.
On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
hadoop.apache.org
3. I will sync manually all of the changes in the next two months back
to the svn site from the git (release announcements, new committers)
IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
If no-one objects within three days, I'll assume lazy consensus and
start with this plan. Please comment if you have objections.
Again: it allows immediate fallback at any time as svn repo will be kept
as is (+ I will keep it up-to-date in the next 2 months)
Thanks,
Marton
On 06/21/2018 09:00 PM, Elek, Marton wrote:
>
> 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 tools.
>
> Hugo has more simple compared to jekyll. Just one binary, without
> dependencies, works everywhere (mac, linux, windows)
>
> Hugo has much more powerful compared to "mvn site". Easier to create/use
> more modern layout/theme, and easier to handle the content (for example
> new release announcements could be generated as part of the release
> process)
>
> I think it's very low risk to try out a new approach for the site (and
> easy to rollback in case of problems)
>
> Marton
>
> ps: I just updated the patch/preview site with the recent releases:
>
> ***************************
> * http://hadoop.anzix.net *
> ***************************
>
> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
>> 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
>> feedback rapidly and get it in.
>>
>> For (2), how about we do it in a different way in the interest of
>> progress?
>> - We create a hadoop.apache.org/new-site/ where this new site goes.
>> - We then modify the existing web-site to say that there is a new
>> site/experience that folks can click on a link and navigate to
>> - As this new website matures and gets feedback & fixes, we finally
>> pull the plug at a later point of time when we think we are good to go.
>>
>> Thoughts?
>>
>> +Vinod
>>
>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>>
>>> 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:
>>>
>>> This thread started long time ago to use a more modern hadoop site:
>>>
>>> Goals were:
>>>
>>> 1. To make it easier to manage it (the release entries could be
>>> created by a script as part of the release process)
>>> 2. To use a better look-and-feel
>>> 3. Move it out from svn to git
>>>
>>> I proposed to:
>>>
>>> 1. Move the existing site to git and generate it with hugo (which is
>>> a single, standalone binary)
>>> 2. Move both the rendered and source branches to git.
>>> 3. (Create a jenkins job to generate the site automatically)
>>>
>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
>>> the documentation which is generated by mvn-site (as before)
>>>
>>>
>>> I got multiple valuable feedback and I improved the proposed site
>>> according to the comments. Allen had some concerns about the used
>>> technologies (hugo vs. mvn-site) and I answered all the questions why
>>> I think mvn-site is the best for documentation and hugo is best for
>>> generating site.
>>>
>>>
>>> I would like to finish this effort/jira: I would like to start a
>>> discussion about using this proposed version and approach as a new
>>> site of Apache Hadoop. Please let me know what you think.
>>>
>>>
>>> Thanks a lot,
>>> Marton
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Brahma Reddy Battula <br...@apache.org>.
+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 <sj...@apache.org> wrote:
> +1. Thanks for the work, Marton!
>
> On Fri, Aug 31, 2018 at 8:37 AM Vinod Kumar Vavilapalli <
> vinodkv@apache.org>
> 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 <el...@apache.org> 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 ask infra to use the new repository as the source of
> > hadoop.apache.org
> > >
> > > 3. I will sync manually all of the changes in the next two months back
> > to the svn site from the git (release announcements, new committers)
> > >
> > > IN CASE OF ANY PROBLEM we can switch back to the svn without any
> problem.
> > >
> > > If no-one objects within three days, I'll assume lazy consensus and
> > start with this plan. Please comment if you have objections.
> > >
> > > Again: it allows immediate fallback at any time as svn repo will be
> kept
> > as is (+ I will keep it up-to-date in the next 2 months)
> > >
> > > Thanks,
> > > Marton
> > >
> > >
> > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > >> 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
> > tools.
> > >> Hugo has more simple compared to jekyll. Just one binary, without
> > dependencies, works everywhere (mac, linux, windows)
> > >> Hugo has much more powerful compared to "mvn site". Easier to
> > create/use more modern layout/theme, and easier to handle the content
> (for
> > example new release announcements could be generated as part of the
> release
> > process)
> > >> I think it's very low risk to try out a new approach for the site (and
> > easy to rollback in case of problems)
> > >> Marton
> > >> ps: I just updated the patch/preview site with the recent releases:
> > >> ***************************
> > >> * http://hadoop.anzix.net *
> > >> ***************************
> > >> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > >>> 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
> > feedback rapidly and get it in.
> > >>>
> > >>> For (2), how about we do it in a different way in the interest of
> > progress?
> > >>> - We create a hadoop.apache.org/new-site/ where this new site
> goes.
> > >>> - We then modify the existing web-site to say that there is a new
> > site/experience that folks can click on a link and navigate to
> > >>> - As this new website matures and gets feedback & fixes, we finally
> > pull the plug at a later point of time when we think we are good to go.
> > >>>
> > >>> Thoughts?
> > >>>
> > >>> +Vinod
> > >>>
> > >>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> > >>>>
> > >>>> 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:
> > >>>>
> > >>>> This thread started long time ago to use a more modern hadoop site:
> > >>>>
> > >>>> Goals were:
> > >>>>
> > >>>> 1. To make it easier to manage it (the release entries could be
> > created by a script as part of the release process)
> > >>>> 2. To use a better look-and-feel
> > >>>> 3. Move it out from svn to git
> > >>>>
> > >>>> I proposed to:
> > >>>>
> > >>>> 1. Move the existing site to git and generate it with hugo (which is
> > a single, standalone binary)
> > >>>> 2. Move both the rendered and source branches to git.
> > >>>> 3. (Create a jenkins job to generate the site automatically)
> > >>>>
> > >>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
> > the documentation which is generated by mvn-site (as before)
> > >>>>
> > >>>>
> > >>>> I got multiple valuable feedback and I improved the proposed site
> > according to the comments. Allen had some concerns about the used
> > technologies (hugo vs. mvn-site) and I answered all the questions why I
> > think mvn-site is the best for documentation and hugo is best for
> > generating site.
> > >>>>
> > >>>>
> > >>>> I would like to finish this effort/jira: I would like to start a
> > discussion about using this proposed version and approach as a new site
> of
> > Apache Hadoop. Please let me know what you think.
> > >>>>
> > >>>>
> > >>>> Thanks a lot,
> > >>>> Marton
> > >>>>
> > >>>>
> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > >>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >>>>
> > >>>
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >>>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > >> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
> >
> >
>
--
--Brahma Reddy Battula
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Brahma Reddy Battula <br...@apache.org>.
+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 <sj...@apache.org> wrote:
> +1. Thanks for the work, Marton!
>
> On Fri, Aug 31, 2018 at 8:37 AM Vinod Kumar Vavilapalli <
> vinodkv@apache.org>
> 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 <el...@apache.org> 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 ask infra to use the new repository as the source of
> > hadoop.apache.org
> > >
> > > 3. I will sync manually all of the changes in the next two months back
> > to the svn site from the git (release announcements, new committers)
> > >
> > > IN CASE OF ANY PROBLEM we can switch back to the svn without any
> problem.
> > >
> > > If no-one objects within three days, I'll assume lazy consensus and
> > start with this plan. Please comment if you have objections.
> > >
> > > Again: it allows immediate fallback at any time as svn repo will be
> kept
> > as is (+ I will keep it up-to-date in the next 2 months)
> > >
> > > Thanks,
> > > Marton
> > >
> > >
> > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > >> 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
> > tools.
> > >> Hugo has more simple compared to jekyll. Just one binary, without
> > dependencies, works everywhere (mac, linux, windows)
> > >> Hugo has much more powerful compared to "mvn site". Easier to
> > create/use more modern layout/theme, and easier to handle the content
> (for
> > example new release announcements could be generated as part of the
> release
> > process)
> > >> I think it's very low risk to try out a new approach for the site (and
> > easy to rollback in case of problems)
> > >> Marton
> > >> ps: I just updated the patch/preview site with the recent releases:
> > >> ***************************
> > >> * http://hadoop.anzix.net *
> > >> ***************************
> > >> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > >>> 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
> > feedback rapidly and get it in.
> > >>>
> > >>> For (2), how about we do it in a different way in the interest of
> > progress?
> > >>> - We create a hadoop.apache.org/new-site/ where this new site
> goes.
> > >>> - We then modify the existing web-site to say that there is a new
> > site/experience that folks can click on a link and navigate to
> > >>> - As this new website matures and gets feedback & fixes, we finally
> > pull the plug at a later point of time when we think we are good to go.
> > >>>
> > >>> Thoughts?
> > >>>
> > >>> +Vinod
> > >>>
> > >>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> > >>>>
> > >>>> 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:
> > >>>>
> > >>>> This thread started long time ago to use a more modern hadoop site:
> > >>>>
> > >>>> Goals were:
> > >>>>
> > >>>> 1. To make it easier to manage it (the release entries could be
> > created by a script as part of the release process)
> > >>>> 2. To use a better look-and-feel
> > >>>> 3. Move it out from svn to git
> > >>>>
> > >>>> I proposed to:
> > >>>>
> > >>>> 1. Move the existing site to git and generate it with hugo (which is
> > a single, standalone binary)
> > >>>> 2. Move both the rendered and source branches to git.
> > >>>> 3. (Create a jenkins job to generate the site automatically)
> > >>>>
> > >>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
> > the documentation which is generated by mvn-site (as before)
> > >>>>
> > >>>>
> > >>>> I got multiple valuable feedback and I improved the proposed site
> > according to the comments. Allen had some concerns about the used
> > technologies (hugo vs. mvn-site) and I answered all the questions why I
> > think mvn-site is the best for documentation and hugo is best for
> > generating site.
> > >>>>
> > >>>>
> > >>>> I would like to finish this effort/jira: I would like to start a
> > discussion about using this proposed version and approach as a new site
> of
> > Apache Hadoop. Please let me know what you think.
> > >>>>
> > >>>>
> > >>>> Thanks a lot,
> > >>>> Marton
> > >>>>
> > >>>>
> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > >>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >>>>
> > >>>
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >>>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > >> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
> >
> >
>
--
--Brahma Reddy Battula
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Brahma Reddy Battula <br...@apache.org>.
+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 <sj...@apache.org> wrote:
> +1. Thanks for the work, Marton!
>
> On Fri, Aug 31, 2018 at 8:37 AM Vinod Kumar Vavilapalli <
> vinodkv@apache.org>
> 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 <el...@apache.org> 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 ask infra to use the new repository as the source of
> > hadoop.apache.org
> > >
> > > 3. I will sync manually all of the changes in the next two months back
> > to the svn site from the git (release announcements, new committers)
> > >
> > > IN CASE OF ANY PROBLEM we can switch back to the svn without any
> problem.
> > >
> > > If no-one objects within three days, I'll assume lazy consensus and
> > start with this plan. Please comment if you have objections.
> > >
> > > Again: it allows immediate fallback at any time as svn repo will be
> kept
> > as is (+ I will keep it up-to-date in the next 2 months)
> > >
> > > Thanks,
> > > Marton
> > >
> > >
> > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > >> 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
> > tools.
> > >> Hugo has more simple compared to jekyll. Just one binary, without
> > dependencies, works everywhere (mac, linux, windows)
> > >> Hugo has much more powerful compared to "mvn site". Easier to
> > create/use more modern layout/theme, and easier to handle the content
> (for
> > example new release announcements could be generated as part of the
> release
> > process)
> > >> I think it's very low risk to try out a new approach for the site (and
> > easy to rollback in case of problems)
> > >> Marton
> > >> ps: I just updated the patch/preview site with the recent releases:
> > >> ***************************
> > >> * http://hadoop.anzix.net *
> > >> ***************************
> > >> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > >>> 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
> > feedback rapidly and get it in.
> > >>>
> > >>> For (2), how about we do it in a different way in the interest of
> > progress?
> > >>> - We create a hadoop.apache.org/new-site/ where this new site
> goes.
> > >>> - We then modify the existing web-site to say that there is a new
> > site/experience that folks can click on a link and navigate to
> > >>> - As this new website matures and gets feedback & fixes, we finally
> > pull the plug at a later point of time when we think we are good to go.
> > >>>
> > >>> Thoughts?
> > >>>
> > >>> +Vinod
> > >>>
> > >>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> > >>>>
> > >>>> 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:
> > >>>>
> > >>>> This thread started long time ago to use a more modern hadoop site:
> > >>>>
> > >>>> Goals were:
> > >>>>
> > >>>> 1. To make it easier to manage it (the release entries could be
> > created by a script as part of the release process)
> > >>>> 2. To use a better look-and-feel
> > >>>> 3. Move it out from svn to git
> > >>>>
> > >>>> I proposed to:
> > >>>>
> > >>>> 1. Move the existing site to git and generate it with hugo (which is
> > a single, standalone binary)
> > >>>> 2. Move both the rendered and source branches to git.
> > >>>> 3. (Create a jenkins job to generate the site automatically)
> > >>>>
> > >>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
> > the documentation which is generated by mvn-site (as before)
> > >>>>
> > >>>>
> > >>>> I got multiple valuable feedback and I improved the proposed site
> > according to the comments. Allen had some concerns about the used
> > technologies (hugo vs. mvn-site) and I answered all the questions why I
> > think mvn-site is the best for documentation and hugo is best for
> > generating site.
> > >>>>
> > >>>>
> > >>>> I would like to finish this effort/jira: I would like to start a
> > discussion about using this proposed version and approach as a new site
> of
> > Apache Hadoop. Please let me know what you think.
> > >>>>
> > >>>>
> > >>>> Thanks a lot,
> > >>>> Marton
> > >>>>
> > >>>>
> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > >>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >>>>
> > >>>
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >>>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > >> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
> >
> >
>
--
--Brahma Reddy Battula
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Brahma Reddy Battula <br...@apache.org>.
+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 <sj...@apache.org> wrote:
> +1. Thanks for the work, Marton!
>
> On Fri, Aug 31, 2018 at 8:37 AM Vinod Kumar Vavilapalli <
> vinodkv@apache.org>
> 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 <el...@apache.org> 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 ask infra to use the new repository as the source of
> > hadoop.apache.org
> > >
> > > 3. I will sync manually all of the changes in the next two months back
> > to the svn site from the git (release announcements, new committers)
> > >
> > > IN CASE OF ANY PROBLEM we can switch back to the svn without any
> problem.
> > >
> > > If no-one objects within three days, I'll assume lazy consensus and
> > start with this plan. Please comment if you have objections.
> > >
> > > Again: it allows immediate fallback at any time as svn repo will be
> kept
> > as is (+ I will keep it up-to-date in the next 2 months)
> > >
> > > Thanks,
> > > Marton
> > >
> > >
> > > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> > >> 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
> > tools.
> > >> Hugo has more simple compared to jekyll. Just one binary, without
> > dependencies, works everywhere (mac, linux, windows)
> > >> Hugo has much more powerful compared to "mvn site". Easier to
> > create/use more modern layout/theme, and easier to handle the content
> (for
> > example new release announcements could be generated as part of the
> release
> > process)
> > >> I think it's very low risk to try out a new approach for the site (and
> > easy to rollback in case of problems)
> > >> Marton
> > >> ps: I just updated the patch/preview site with the recent releases:
> > >> ***************************
> > >> * http://hadoop.anzix.net *
> > >> ***************************
> > >> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> > >>> 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
> > feedback rapidly and get it in.
> > >>>
> > >>> For (2), how about we do it in a different way in the interest of
> > progress?
> > >>> - We create a hadoop.apache.org/new-site/ where this new site
> goes.
> > >>> - We then modify the existing web-site to say that there is a new
> > site/experience that folks can click on a link and navigate to
> > >>> - As this new website matures and gets feedback & fixes, we finally
> > pull the plug at a later point of time when we think we are good to go.
> > >>>
> > >>> Thoughts?
> > >>>
> > >>> +Vinod
> > >>>
> > >>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> > >>>>
> > >>>> 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:
> > >>>>
> > >>>> This thread started long time ago to use a more modern hadoop site:
> > >>>>
> > >>>> Goals were:
> > >>>>
> > >>>> 1. To make it easier to manage it (the release entries could be
> > created by a script as part of the release process)
> > >>>> 2. To use a better look-and-feel
> > >>>> 3. Move it out from svn to git
> > >>>>
> > >>>> I proposed to:
> > >>>>
> > >>>> 1. Move the existing site to git and generate it with hugo (which is
> > a single, standalone binary)
> > >>>> 2. Move both the rendered and source branches to git.
> > >>>> 3. (Create a jenkins job to generate the site automatically)
> > >>>>
> > >>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
> > the documentation which is generated by mvn-site (as before)
> > >>>>
> > >>>>
> > >>>> I got multiple valuable feedback and I improved the proposed site
> > according to the comments. Allen had some concerns about the used
> > technologies (hugo vs. mvn-site) and I answered all the questions why I
> > think mvn-site is the best for documentation and hugo is best for
> > generating site.
> > >>>>
> > >>>>
> > >>>> I would like to finish this effort/jira: I would like to start a
> > discussion about using this proposed version and approach as a new site
> of
> > Apache Hadoop. Please let me know what you think.
> > >>>>
> > >>>>
> > >>>> Thanks a lot,
> > >>>> Marton
> > >>>>
> > >>>>
> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > >>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >>>>
> > >>>
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >>>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > >> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
> >
> >
>
--
--Brahma Reddy Battula
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Sangjin Lee <sj...@apache.org>.
+1. Thanks for the work, Marton!
On Fri, Aug 31, 2018 at 8:37 AM Vinod Kumar Vavilapalli <vi...@apache.org>
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 <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
> >
> > 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
> >
> > IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
> >
> > If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
> >
> > Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
> >
> > Thanks,
> > Marton
> >
> >
> > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> >> 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
> tools.
> >> Hugo has more simple compared to jekyll. Just one binary, without
> dependencies, works everywhere (mac, linux, windows)
> >> Hugo has much more powerful compared to "mvn site". Easier to
> create/use more modern layout/theme, and easier to handle the content (for
> example new release announcements could be generated as part of the release
> process)
> >> I think it's very low risk to try out a new approach for the site (and
> easy to rollback in case of problems)
> >> Marton
> >> ps: I just updated the patch/preview site with the recent releases:
> >> ***************************
> >> * http://hadoop.anzix.net *
> >> ***************************
> >> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> >>> 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
> feedback rapidly and get it in.
> >>>
> >>> For (2), how about we do it in a different way in the interest of
> progress?
> >>> - We create a hadoop.apache.org/new-site/ where this new site goes.
> >>> - We then modify the existing web-site to say that there is a new
> site/experience that folks can click on a link and navigate to
> >>> - As this new website matures and gets feedback & fixes, we finally
> pull the plug at a later point of time when we think we are good to go.
> >>>
> >>> Thoughts?
> >>>
> >>> +Vinod
> >>>
> >>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> >>>>
> >>>> 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:
> >>>>
> >>>> This thread started long time ago to use a more modern hadoop site:
> >>>>
> >>>> Goals were:
> >>>>
> >>>> 1. To make it easier to manage it (the release entries could be
> created by a script as part of the release process)
> >>>> 2. To use a better look-and-feel
> >>>> 3. Move it out from svn to git
> >>>>
> >>>> I proposed to:
> >>>>
> >>>> 1. Move the existing site to git and generate it with hugo (which is
> a single, standalone binary)
> >>>> 2. Move both the rendered and source branches to git.
> >>>> 3. (Create a jenkins job to generate the site automatically)
> >>>>
> >>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
> the documentation which is generated by mvn-site (as before)
> >>>>
> >>>>
> >>>> I got multiple valuable feedback and I improved the proposed site
> according to the comments. Allen had some concerns about the used
> technologies (hugo vs. mvn-site) and I answered all the questions why I
> think mvn-site is the best for documentation and hugo is best for
> generating site.
> >>>>
> >>>>
> >>>> I would like to finish this effort/jira: I would like to start a
> discussion about using this proposed version and approach as a new site of
> Apache Hadoop. Please let me know what you think.
> >>>>
> >>>>
> >>>> Thanks a lot,
> >>>> Marton
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Sangjin Lee <sj...@apache.org>.
+1. Thanks for the work, Marton!
On Fri, Aug 31, 2018 at 8:37 AM Vinod Kumar Vavilapalli <vi...@apache.org>
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 <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
> >
> > 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
> >
> > IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
> >
> > If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
> >
> > Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
> >
> > Thanks,
> > Marton
> >
> >
> > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> >> 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
> tools.
> >> Hugo has more simple compared to jekyll. Just one binary, without
> dependencies, works everywhere (mac, linux, windows)
> >> Hugo has much more powerful compared to "mvn site". Easier to
> create/use more modern layout/theme, and easier to handle the content (for
> example new release announcements could be generated as part of the release
> process)
> >> I think it's very low risk to try out a new approach for the site (and
> easy to rollback in case of problems)
> >> Marton
> >> ps: I just updated the patch/preview site with the recent releases:
> >> ***************************
> >> * http://hadoop.anzix.net *
> >> ***************************
> >> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> >>> 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
> feedback rapidly and get it in.
> >>>
> >>> For (2), how about we do it in a different way in the interest of
> progress?
> >>> - We create a hadoop.apache.org/new-site/ where this new site goes.
> >>> - We then modify the existing web-site to say that there is a new
> site/experience that folks can click on a link and navigate to
> >>> - As this new website matures and gets feedback & fixes, we finally
> pull the plug at a later point of time when we think we are good to go.
> >>>
> >>> Thoughts?
> >>>
> >>> +Vinod
> >>>
> >>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> >>>>
> >>>> 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:
> >>>>
> >>>> This thread started long time ago to use a more modern hadoop site:
> >>>>
> >>>> Goals were:
> >>>>
> >>>> 1. To make it easier to manage it (the release entries could be
> created by a script as part of the release process)
> >>>> 2. To use a better look-and-feel
> >>>> 3. Move it out from svn to git
> >>>>
> >>>> I proposed to:
> >>>>
> >>>> 1. Move the existing site to git and generate it with hugo (which is
> a single, standalone binary)
> >>>> 2. Move both the rendered and source branches to git.
> >>>> 3. (Create a jenkins job to generate the site automatically)
> >>>>
> >>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
> the documentation which is generated by mvn-site (as before)
> >>>>
> >>>>
> >>>> I got multiple valuable feedback and I improved the proposed site
> according to the comments. Allen had some concerns about the used
> technologies (hugo vs. mvn-site) and I answered all the questions why I
> think mvn-site is the best for documentation and hugo is best for
> generating site.
> >>>>
> >>>>
> >>>> I would like to finish this effort/jira: I would like to start a
> discussion about using this proposed version and approach as a new site of
> Apache Hadoop. Please let me know what you think.
> >>>>
> >>>>
> >>>> Thanks a lot,
> >>>> Marton
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Sangjin Lee <sj...@apache.org>.
+1. Thanks for the work, Marton!
On Fri, Aug 31, 2018 at 8:37 AM Vinod Kumar Vavilapalli <vi...@apache.org>
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 <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
> >
> > 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
> >
> > IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
> >
> > If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
> >
> > Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
> >
> > Thanks,
> > Marton
> >
> >
> > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> >> 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
> tools.
> >> Hugo has more simple compared to jekyll. Just one binary, without
> dependencies, works everywhere (mac, linux, windows)
> >> Hugo has much more powerful compared to "mvn site". Easier to
> create/use more modern layout/theme, and easier to handle the content (for
> example new release announcements could be generated as part of the release
> process)
> >> I think it's very low risk to try out a new approach for the site (and
> easy to rollback in case of problems)
> >> Marton
> >> ps: I just updated the patch/preview site with the recent releases:
> >> ***************************
> >> * http://hadoop.anzix.net *
> >> ***************************
> >> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> >>> 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
> feedback rapidly and get it in.
> >>>
> >>> For (2), how about we do it in a different way in the interest of
> progress?
> >>> - We create a hadoop.apache.org/new-site/ where this new site goes.
> >>> - We then modify the existing web-site to say that there is a new
> site/experience that folks can click on a link and navigate to
> >>> - As this new website matures and gets feedback & fixes, we finally
> pull the plug at a later point of time when we think we are good to go.
> >>>
> >>> Thoughts?
> >>>
> >>> +Vinod
> >>>
> >>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> >>>>
> >>>> 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:
> >>>>
> >>>> This thread started long time ago to use a more modern hadoop site:
> >>>>
> >>>> Goals were:
> >>>>
> >>>> 1. To make it easier to manage it (the release entries could be
> created by a script as part of the release process)
> >>>> 2. To use a better look-and-feel
> >>>> 3. Move it out from svn to git
> >>>>
> >>>> I proposed to:
> >>>>
> >>>> 1. Move the existing site to git and generate it with hugo (which is
> a single, standalone binary)
> >>>> 2. Move both the rendered and source branches to git.
> >>>> 3. (Create a jenkins job to generate the site automatically)
> >>>>
> >>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
> the documentation which is generated by mvn-site (as before)
> >>>>
> >>>>
> >>>> I got multiple valuable feedback and I improved the proposed site
> according to the comments. Allen had some concerns about the used
> technologies (hugo vs. mvn-site) and I answered all the questions why I
> think mvn-site is the best for documentation and hugo is best for
> generating site.
> >>>>
> >>>>
> >>>> I would like to finish this effort/jira: I would like to start a
> discussion about using this proposed version and approach as a new site of
> Apache Hadoop. Please let me know what you think.
> >>>>
> >>>>
> >>>> Thanks a lot,
> >>>> Marton
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Sangjin Lee <sj...@apache.org>.
+1. Thanks for the work, Marton!
On Fri, Aug 31, 2018 at 8:37 AM Vinod Kumar Vavilapalli <vi...@apache.org>
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 <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
> >
> > 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
> >
> > IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
> >
> > If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
> >
> > Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
> >
> > Thanks,
> > Marton
> >
> >
> > On 06/21/2018 09:00 PM, Elek, Marton wrote:
> >> 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
> tools.
> >> Hugo has more simple compared to jekyll. Just one binary, without
> dependencies, works everywhere (mac, linux, windows)
> >> Hugo has much more powerful compared to "mvn site". Easier to
> create/use more modern layout/theme, and easier to handle the content (for
> example new release announcements could be generated as part of the release
> process)
> >> I think it's very low risk to try out a new approach for the site (and
> easy to rollback in case of problems)
> >> Marton
> >> ps: I just updated the patch/preview site with the recent releases:
> >> ***************************
> >> * http://hadoop.anzix.net *
> >> ***************************
> >> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> >>> 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
> feedback rapidly and get it in.
> >>>
> >>> For (2), how about we do it in a different way in the interest of
> progress?
> >>> - We create a hadoop.apache.org/new-site/ where this new site goes.
> >>> - We then modify the existing web-site to say that there is a new
> site/experience that folks can click on a link and navigate to
> >>> - As this new website matures and gets feedback & fixes, we finally
> pull the plug at a later point of time when we think we are good to go.
> >>>
> >>> Thoughts?
> >>>
> >>> +Vinod
> >>>
> >>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> >>>>
> >>>> 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:
> >>>>
> >>>> This thread started long time ago to use a more modern hadoop site:
> >>>>
> >>>> Goals were:
> >>>>
> >>>> 1. To make it easier to manage it (the release entries could be
> created by a script as part of the release process)
> >>>> 2. To use a better look-and-feel
> >>>> 3. Move it out from svn to git
> >>>>
> >>>> I proposed to:
> >>>>
> >>>> 1. Move the existing site to git and generate it with hugo (which is
> a single, standalone binary)
> >>>> 2. Move both the rendered and source branches to git.
> >>>> 3. (Create a jenkins job to generate the site automatically)
> >>>>
> >>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
> the documentation which is generated by mvn-site (as before)
> >>>>
> >>>>
> >>>> I got multiple valuable feedback and I improved the proposed site
> according to the comments. Allen had some concerns about the used
> technologies (hugo vs. mvn-site) and I answered all the questions why I
> think mvn-site is the best for documentation and hugo is best for
> generating site.
> >>>>
> >>>>
> >>>> I would like to finish this effort/jira: I would like to start a
> discussion about using this proposed version and approach as a new site of
> Apache Hadoop. Please let me know what you think.
> >>>>
> >>>>
> >>>> Thanks a lot,
> >>>> Marton
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
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 <el...@apache.org> 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 ask infra to use the new repository as the source of hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
>> 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 tools.
>> Hugo has more simple compared to jekyll. Just one binary, without dependencies, works everywhere (mac, linux, windows)
>> Hugo has much more powerful compared to "mvn site". Easier to create/use more modern layout/theme, and easier to handle the content (for example new release announcements could be generated as part of the release process)
>> I think it's very low risk to try out a new approach for the site (and easy to rollback in case of problems)
>> Marton
>> ps: I just updated the patch/preview site with the recent releases:
>> ***************************
>> * http://hadoop.anzix.net *
>> ***************************
>> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
>>> 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 feedback rapidly and get it in.
>>>
>>> For (2), how about we do it in a different way in the interest of progress?
>>> - We create a hadoop.apache.org/new-site/ where this new site goes.
>>> - We then modify the existing web-site to say that there is a new site/experience that folks can click on a link and navigate to
>>> - As this new website matures and gets feedback & fixes, we finally pull the plug at a later point of time when we think we are good to go.
>>>
>>> Thoughts?
>>>
>>> +Vinod
>>>
>>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>>>
>>>> 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:
>>>>
>>>> This thread started long time ago to use a more modern hadoop site:
>>>>
>>>> Goals were:
>>>>
>>>> 1. To make it easier to manage it (the release entries could be created by a script as part of the release process)
>>>> 2. To use a better look-and-feel
>>>> 3. Move it out from svn to git
>>>>
>>>> I proposed to:
>>>>
>>>> 1. Move the existing site to git and generate it with hugo (which is a single, standalone binary)
>>>> 2. Move both the rendered and source branches to git.
>>>> 3. (Create a jenkins job to generate the site automatically)
>>>>
>>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about the documentation which is generated by mvn-site (as before)
>>>>
>>>>
>>>> I got multiple valuable feedback and I improved the proposed site according to the comments. Allen had some concerns about the used technologies (hugo vs. mvn-site) and I answered all the questions why I think mvn-site is the best for documentation and hugo is best for generating site.
>>>>
>>>>
>>>> I would like to finish this effort/jira: I would like to start a discussion about using this proposed version and approach as a new site of Apache Hadoop. Please let me know what you think.
>>>>
>>>>
>>>> Thanks a lot,
>>>> Marton
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by larry mccay <lm...@apache.org>.
+1 from me
On Fri, Aug 31, 2018, 5:30 AM Steve Loughran <st...@hortonworks.com> wrote:
>
>
> > On 31 Aug 2018, at 09:07, Elek, Marton <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
> >
> > 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
> >
> > IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
> >
> > If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
> >
> > Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
> >
> > Thanks,
> > Marton
>
> sounds good to me
>
> +1
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by larry mccay <lm...@apache.org>.
+1 from me
On Fri, Aug 31, 2018, 5:30 AM Steve Loughran <st...@hortonworks.com> wrote:
>
>
> > On 31 Aug 2018, at 09:07, Elek, Marton <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
> >
> > 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
> >
> > IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
> >
> > If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
> >
> > Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
> >
> > Thanks,
> > Marton
>
> sounds good to me
>
> +1
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by larry mccay <lm...@apache.org>.
+1 from me
On Fri, Aug 31, 2018, 5:30 AM Steve Loughran <st...@hortonworks.com> wrote:
>
>
> > On 31 Aug 2018, at 09:07, Elek, Marton <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
> >
> > 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
> >
> > IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
> >
> > If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
> >
> > Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
> >
> > Thanks,
> > Marton
>
> sounds good to me
>
> +1
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by larry mccay <lm...@apache.org>.
+1 from me
On Fri, Aug 31, 2018, 5:30 AM Steve Loughran <st...@hortonworks.com> wrote:
>
>
> > On 31 Aug 2018, at 09:07, Elek, Marton <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
> >
> > 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
> >
> > IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
> >
> > If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
> >
> > Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
> >
> > Thanks,
> > Marton
>
> sounds good to me
>
> +1
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Steve Loughran <st...@hortonworks.com>.
> On 31 Aug 2018, at 09:07, Elek, Marton <el...@apache.org> 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 ask infra to use the new repository as the source of hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
sounds good to me
+1
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by "Elek, Marton" <el...@apache.org>.
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 javadocs
(289003 file)
3. The old site (as suggested by Vinod. I added a link back to the old
site). https://hadoop.apache.org/old
Infra has already changed the pubsub script. The new site is live.
Please let me know if you see any problem...
I will update the wiki pages / release instruction very soon.
Thanks,
Marton
ps:
Please give me write permission to the OLD wiki
(https://wiki.apache.org/hadoop/), if you can. My username is MartonElek
Thanks a lot.
On 08/31/2018 10: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 content as the existing
> site).
>
> 2. I will ask infra to use the new repository as the source of
> hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
>>
>> 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 tools.
>>
>> Hugo has more simple compared to jekyll. Just one binary, without
>> dependencies, works everywhere (mac, linux, windows)
>>
>> Hugo has much more powerful compared to "mvn site". Easier to
>> create/use more modern layout/theme, and easier to handle the content
>> (for example new release announcements could be generated as part of
>> the release process)
>>
>> I think it's very low risk to try out a new approach for the site (and
>> easy to rollback in case of problems)
>>
>> Marton
>>
>> ps: I just updated the patch/preview site with the recent releases:
>>
>> ***************************
>> * http://hadoop.anzix.net *
>> ***************************
>>
>> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
>>> 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
>>> feedback rapidly and get it in.
>>>
>>> For (2), how about we do it in a different way in the interest of
>>> progress?
>>> - We create a hadoop.apache.org/new-site/ where this new site goes.
>>> - We then modify the existing web-site to say that there is a new
>>> site/experience that folks can click on a link and navigate to
>>> - As this new website matures and gets feedback & fixes, we finally
>>> pull the plug at a later point of time when we think we are good to go.
>>>
>>> Thoughts?
>>>
>>> +Vinod
>>>
>>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>>>
>>>> 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:
>>>>
>>>> This thread started long time ago to use a more modern hadoop site:
>>>>
>>>> Goals were:
>>>>
>>>> 1. To make it easier to manage it (the release entries could be
>>>> created by a script as part of the release process)
>>>> 2. To use a better look-and-feel
>>>> 3. Move it out from svn to git
>>>>
>>>> I proposed to:
>>>>
>>>> 1. Move the existing site to git and generate it with hugo (which is
>>>> a single, standalone binary)
>>>> 2. Move both the rendered and source branches to git.
>>>> 3. (Create a jenkins job to generate the site automatically)
>>>>
>>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
>>>> the documentation which is generated by mvn-site (as before)
>>>>
>>>>
>>>> I got multiple valuable feedback and I improved the proposed site
>>>> according to the comments. Allen had some concerns about the used
>>>> technologies (hugo vs. mvn-site) and I answered all the questions
>>>> why I think mvn-site is the best for documentation and hugo is best
>>>> for generating site.
>>>>
>>>>
>>>> I would like to finish this effort/jira: I would like to start a
>>>> discussion about using this proposed version and approach as a new
>>>> site of Apache Hadoop. Please let me know what you think.
>>>>
>>>>
>>>> Thanks a lot,
>>>> Marton
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Mingliang Liu <li...@gmail.com>.
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 <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
> >
> > 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 tools.
> >
> > Hugo has more simple compared to jekyll. Just one binary, without
> > dependencies, works everywhere (mac, linux, windows)
> >
> > Hugo has much more powerful compared to "mvn site". Easier to create/use
> > more modern layout/theme, and easier to handle the content (for example
> > new release announcements could be generated as part of the release
> > process)
> >
> > I think it's very low risk to try out a new approach for the site (and
> > easy to rollback in case of problems)
> >
> > Marton
> >
> > ps: I just updated the patch/preview site with the recent releases:
> >
> > ***************************
> > * http://hadoop.anzix.net *
> > ***************************
> >
> > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> >> 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
> >> feedback rapidly and get it in.
> >>
> >> For (2), how about we do it in a different way in the interest of
> >> progress?
> >> - We create a hadoop.apache.org/new-site/ where this new site goes.
> >> - We then modify the existing web-site to say that there is a new
> >> site/experience that folks can click on a link and navigate to
> >> - As this new website matures and gets feedback & fixes, we finally
> >> pull the plug at a later point of time when we think we are good to go.
> >>
> >> Thoughts?
> >>
> >> +Vinod
> >>
> >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> >>>
> >>> 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:
> >>>
> >>> This thread started long time ago to use a more modern hadoop site:
> >>>
> >>> Goals were:
> >>>
> >>> 1. To make it easier to manage it (the release entries could be
> >>> created by a script as part of the release process)
> >>> 2. To use a better look-and-feel
> >>> 3. Move it out from svn to git
> >>>
> >>> I proposed to:
> >>>
> >>> 1. Move the existing site to git and generate it with hugo (which is
> >>> a single, standalone binary)
> >>> 2. Move both the rendered and source branches to git.
> >>> 3. (Create a jenkins job to generate the site automatically)
> >>>
> >>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
> >>> the documentation which is generated by mvn-site (as before)
> >>>
> >>>
> >>> I got multiple valuable feedback and I improved the proposed site
> >>> according to the comments. Allen had some concerns about the used
> >>> technologies (hugo vs. mvn-site) and I answered all the questions why
> >>> I think mvn-site is the best for documentation and hugo is best for
> >>> generating site.
> >>>
> >>>
> >>> I would like to finish this effort/jira: I would like to start a
> >>> discussion about using this proposed version and approach as a new
> >>> site of Apache Hadoop. Please let me know what you think.
> >>>
> >>>
> >>> Thanks a lot,
> >>> Marton
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
--
Mingliang Liu
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by "Elek, Marton" <el...@apache.org>.
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 javadocs
(289003 file)
3. The old site (as suggested by Vinod. I added a link back to the old
site). https://hadoop.apache.org/old
Infra has already changed the pubsub script. The new site is live.
Please let me know if you see any problem...
I will update the wiki pages / release instruction very soon.
Thanks,
Marton
ps:
Please give me write permission to the OLD wiki
(https://wiki.apache.org/hadoop/), if you can. My username is MartonElek
Thanks a lot.
On 08/31/2018 10: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 content as the existing
> site).
>
> 2. I will ask infra to use the new repository as the source of
> hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
>>
>> 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 tools.
>>
>> Hugo has more simple compared to jekyll. Just one binary, without
>> dependencies, works everywhere (mac, linux, windows)
>>
>> Hugo has much more powerful compared to "mvn site". Easier to
>> create/use more modern layout/theme, and easier to handle the content
>> (for example new release announcements could be generated as part of
>> the release process)
>>
>> I think it's very low risk to try out a new approach for the site (and
>> easy to rollback in case of problems)
>>
>> Marton
>>
>> ps: I just updated the patch/preview site with the recent releases:
>>
>> ***************************
>> * http://hadoop.anzix.net *
>> ***************************
>>
>> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
>>> 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
>>> feedback rapidly and get it in.
>>>
>>> For (2), how about we do it in a different way in the interest of
>>> progress?
>>> - We create a hadoop.apache.org/new-site/ where this new site goes.
>>> - We then modify the existing web-site to say that there is a new
>>> site/experience that folks can click on a link and navigate to
>>> - As this new website matures and gets feedback & fixes, we finally
>>> pull the plug at a later point of time when we think we are good to go.
>>>
>>> Thoughts?
>>>
>>> +Vinod
>>>
>>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>>>
>>>> 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:
>>>>
>>>> This thread started long time ago to use a more modern hadoop site:
>>>>
>>>> Goals were:
>>>>
>>>> 1. To make it easier to manage it (the release entries could be
>>>> created by a script as part of the release process)
>>>> 2. To use a better look-and-feel
>>>> 3. Move it out from svn to git
>>>>
>>>> I proposed to:
>>>>
>>>> 1. Move the existing site to git and generate it with hugo (which is
>>>> a single, standalone binary)
>>>> 2. Move both the rendered and source branches to git.
>>>> 3. (Create a jenkins job to generate the site automatically)
>>>>
>>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
>>>> the documentation which is generated by mvn-site (as before)
>>>>
>>>>
>>>> I got multiple valuable feedback and I improved the proposed site
>>>> according to the comments. Allen had some concerns about the used
>>>> technologies (hugo vs. mvn-site) and I answered all the questions
>>>> why I think mvn-site is the best for documentation and hugo is best
>>>> for generating site.
>>>>
>>>>
>>>> I would like to finish this effort/jira: I would like to start a
>>>> discussion about using this proposed version and approach as a new
>>>> site of Apache Hadoop. Please let me know what you think.
>>>>
>>>>
>>>> Thanks a lot,
>>>> Marton
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Arpit Agarwal <aa...@hortonworks.com>.
+1
Thanks for initiating this Marton.
On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
hadoop.apache.org
3. I will sync manually all of the changes in the next two months back
to the svn site from the git (release announcements, new committers)
IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
If no-one objects within three days, I'll assume lazy consensus and
start with this plan. Please comment if you have objections.
Again: it allows immediate fallback at any time as svn repo will be kept
as is (+ I will keep it up-to-date in the next 2 months)
Thanks,
Marton
On 06/21/2018 09:00 PM, Elek, Marton wrote:
>
> 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 tools.
>
> Hugo has more simple compared to jekyll. Just one binary, without
> dependencies, works everywhere (mac, linux, windows)
>
> Hugo has much more powerful compared to "mvn site". Easier to create/use
> more modern layout/theme, and easier to handle the content (for example
> new release announcements could be generated as part of the release
> process)
>
> I think it's very low risk to try out a new approach for the site (and
> easy to rollback in case of problems)
>
> Marton
>
> ps: I just updated the patch/preview site with the recent releases:
>
> ***************************
> * http://hadoop.anzix.net *
> ***************************
>
> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
>> 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
>> feedback rapidly and get it in.
>>
>> For (2), how about we do it in a different way in the interest of
>> progress?
>> - We create a hadoop.apache.org/new-site/ where this new site goes.
>> - We then modify the existing web-site to say that there is a new
>> site/experience that folks can click on a link and navigate to
>> - As this new website matures and gets feedback & fixes, we finally
>> pull the plug at a later point of time when we think we are good to go.
>>
>> Thoughts?
>>
>> +Vinod
>>
>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>>
>>> 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:
>>>
>>> This thread started long time ago to use a more modern hadoop site:
>>>
>>> Goals were:
>>>
>>> 1. To make it easier to manage it (the release entries could be
>>> created by a script as part of the release process)
>>> 2. To use a better look-and-feel
>>> 3. Move it out from svn to git
>>>
>>> I proposed to:
>>>
>>> 1. Move the existing site to git and generate it with hugo (which is
>>> a single, standalone binary)
>>> 2. Move both the rendered and source branches to git.
>>> 3. (Create a jenkins job to generate the site automatically)
>>>
>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
>>> the documentation which is generated by mvn-site (as before)
>>>
>>>
>>> I got multiple valuable feedback and I improved the proposed site
>>> according to the comments. Allen had some concerns about the used
>>> technologies (hugo vs. mvn-site) and I answered all the questions why
>>> I think mvn-site is the best for documentation and hugo is best for
>>> generating site.
>>>
>>>
>>> I would like to finish this effort/jira: I would like to start a
>>> discussion about using this proposed version and approach as a new
>>> site of Apache Hadoop. Please let me know what you think.
>>>
>>>
>>> Thanks a lot,
>>> Marton
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
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 <el...@apache.org> 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 ask infra to use the new repository as the source of hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
>> 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 tools.
>> Hugo has more simple compared to jekyll. Just one binary, without dependencies, works everywhere (mac, linux, windows)
>> Hugo has much more powerful compared to "mvn site". Easier to create/use more modern layout/theme, and easier to handle the content (for example new release announcements could be generated as part of the release process)
>> I think it's very low risk to try out a new approach for the site (and easy to rollback in case of problems)
>> Marton
>> ps: I just updated the patch/preview site with the recent releases:
>> ***************************
>> * http://hadoop.anzix.net *
>> ***************************
>> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
>>> 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 feedback rapidly and get it in.
>>>
>>> For (2), how about we do it in a different way in the interest of progress?
>>> - We create a hadoop.apache.org/new-site/ where this new site goes.
>>> - We then modify the existing web-site to say that there is a new site/experience that folks can click on a link and navigate to
>>> - As this new website matures and gets feedback & fixes, we finally pull the plug at a later point of time when we think we are good to go.
>>>
>>> Thoughts?
>>>
>>> +Vinod
>>>
>>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>>>
>>>> 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:
>>>>
>>>> This thread started long time ago to use a more modern hadoop site:
>>>>
>>>> Goals were:
>>>>
>>>> 1. To make it easier to manage it (the release entries could be created by a script as part of the release process)
>>>> 2. To use a better look-and-feel
>>>> 3. Move it out from svn to git
>>>>
>>>> I proposed to:
>>>>
>>>> 1. Move the existing site to git and generate it with hugo (which is a single, standalone binary)
>>>> 2. Move both the rendered and source branches to git.
>>>> 3. (Create a jenkins job to generate the site automatically)
>>>>
>>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about the documentation which is generated by mvn-site (as before)
>>>>
>>>>
>>>> I got multiple valuable feedback and I improved the proposed site according to the comments. Allen had some concerns about the used technologies (hugo vs. mvn-site) and I answered all the questions why I think mvn-site is the best for documentation and hugo is best for generating site.
>>>>
>>>>
>>>> I would like to finish this effort/jira: I would like to start a discussion about using this proposed version and approach as a new site of Apache Hadoop. Please let me know what you think.
>>>>
>>>>
>>>> Thanks a lot,
>>>> Marton
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Steve Loughran <st...@hortonworks.com>.
> On 31 Aug 2018, at 09:07, Elek, Marton <el...@apache.org> 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 ask infra to use the new repository as the source of hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
sounds good to me
+1
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
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 <el...@apache.org> 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 ask infra to use the new repository as the source of hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
>> 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 tools.
>> Hugo has more simple compared to jekyll. Just one binary, without dependencies, works everywhere (mac, linux, windows)
>> Hugo has much more powerful compared to "mvn site". Easier to create/use more modern layout/theme, and easier to handle the content (for example new release announcements could be generated as part of the release process)
>> I think it's very low risk to try out a new approach for the site (and easy to rollback in case of problems)
>> Marton
>> ps: I just updated the patch/preview site with the recent releases:
>> ***************************
>> * http://hadoop.anzix.net *
>> ***************************
>> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
>>> 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 feedback rapidly and get it in.
>>>
>>> For (2), how about we do it in a different way in the interest of progress?
>>> - We create a hadoop.apache.org/new-site/ where this new site goes.
>>> - We then modify the existing web-site to say that there is a new site/experience that folks can click on a link and navigate to
>>> - As this new website matures and gets feedback & fixes, we finally pull the plug at a later point of time when we think we are good to go.
>>>
>>> Thoughts?
>>>
>>> +Vinod
>>>
>>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>>>
>>>> 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:
>>>>
>>>> This thread started long time ago to use a more modern hadoop site:
>>>>
>>>> Goals were:
>>>>
>>>> 1. To make it easier to manage it (the release entries could be created by a script as part of the release process)
>>>> 2. To use a better look-and-feel
>>>> 3. Move it out from svn to git
>>>>
>>>> I proposed to:
>>>>
>>>> 1. Move the existing site to git and generate it with hugo (which is a single, standalone binary)
>>>> 2. Move both the rendered and source branches to git.
>>>> 3. (Create a jenkins job to generate the site automatically)
>>>>
>>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about the documentation which is generated by mvn-site (as before)
>>>>
>>>>
>>>> I got multiple valuable feedback and I improved the proposed site according to the comments. Allen had some concerns about the used technologies (hugo vs. mvn-site) and I answered all the questions why I think mvn-site is the best for documentation and hugo is best for generating site.
>>>>
>>>>
>>>> I would like to finish this effort/jira: I would like to start a discussion about using this proposed version and approach as a new site of Apache Hadoop. Please let me know what you think.
>>>>
>>>>
>>>> Thanks a lot,
>>>> Marton
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
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 <el...@apache.org> 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 ask infra to use the new repository as the source of hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
>> 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 tools.
>> Hugo has more simple compared to jekyll. Just one binary, without dependencies, works everywhere (mac, linux, windows)
>> Hugo has much more powerful compared to "mvn site". Easier to create/use more modern layout/theme, and easier to handle the content (for example new release announcements could be generated as part of the release process)
>> I think it's very low risk to try out a new approach for the site (and easy to rollback in case of problems)
>> Marton
>> ps: I just updated the patch/preview site with the recent releases:
>> ***************************
>> * http://hadoop.anzix.net *
>> ***************************
>> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
>>> 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 feedback rapidly and get it in.
>>>
>>> For (2), how about we do it in a different way in the interest of progress?
>>> - We create a hadoop.apache.org/new-site/ where this new site goes.
>>> - We then modify the existing web-site to say that there is a new site/experience that folks can click on a link and navigate to
>>> - As this new website matures and gets feedback & fixes, we finally pull the plug at a later point of time when we think we are good to go.
>>>
>>> Thoughts?
>>>
>>> +Vinod
>>>
>>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>>>
>>>> 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:
>>>>
>>>> This thread started long time ago to use a more modern hadoop site:
>>>>
>>>> Goals were:
>>>>
>>>> 1. To make it easier to manage it (the release entries could be created by a script as part of the release process)
>>>> 2. To use a better look-and-feel
>>>> 3. Move it out from svn to git
>>>>
>>>> I proposed to:
>>>>
>>>> 1. Move the existing site to git and generate it with hugo (which is a single, standalone binary)
>>>> 2. Move both the rendered and source branches to git.
>>>> 3. (Create a jenkins job to generate the site automatically)
>>>>
>>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about the documentation which is generated by mvn-site (as before)
>>>>
>>>>
>>>> I got multiple valuable feedback and I improved the proposed site according to the comments. Allen had some concerns about the used technologies (hugo vs. mvn-site) and I answered all the questions why I think mvn-site is the best for documentation and hugo is best for generating site.
>>>>
>>>>
>>>> I would like to finish this effort/jira: I would like to start a discussion about using this proposed version and approach as a new site of Apache Hadoop. Please let me know what you think.
>>>>
>>>>
>>>> Thanks a lot,
>>>> Marton
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by "Elek, Marton" <el...@apache.org>.
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 javadocs
(289003 file)
3. The old site (as suggested by Vinod. I added a link back to the old
site). https://hadoop.apache.org/old
Infra has already changed the pubsub script. The new site is live.
Please let me know if you see any problem...
I will update the wiki pages / release instruction very soon.
Thanks,
Marton
ps:
Please give me write permission to the OLD wiki
(https://wiki.apache.org/hadoop/), if you can. My username is MartonElek
Thanks a lot.
On 08/31/2018 10: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 content as the existing
> site).
>
> 2. I will ask infra to use the new repository as the source of
> hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
>>
>> 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 tools.
>>
>> Hugo has more simple compared to jekyll. Just one binary, without
>> dependencies, works everywhere (mac, linux, windows)
>>
>> Hugo has much more powerful compared to "mvn site". Easier to
>> create/use more modern layout/theme, and easier to handle the content
>> (for example new release announcements could be generated as part of
>> the release process)
>>
>> I think it's very low risk to try out a new approach for the site (and
>> easy to rollback in case of problems)
>>
>> Marton
>>
>> ps: I just updated the patch/preview site with the recent releases:
>>
>> ***************************
>> * http://hadoop.anzix.net *
>> ***************************
>>
>> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
>>> 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
>>> feedback rapidly and get it in.
>>>
>>> For (2), how about we do it in a different way in the interest of
>>> progress?
>>> - We create a hadoop.apache.org/new-site/ where this new site goes.
>>> - We then modify the existing web-site to say that there is a new
>>> site/experience that folks can click on a link and navigate to
>>> - As this new website matures and gets feedback & fixes, we finally
>>> pull the plug at a later point of time when we think we are good to go.
>>>
>>> Thoughts?
>>>
>>> +Vinod
>>>
>>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>>>
>>>> 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:
>>>>
>>>> This thread started long time ago to use a more modern hadoop site:
>>>>
>>>> Goals were:
>>>>
>>>> 1. To make it easier to manage it (the release entries could be
>>>> created by a script as part of the release process)
>>>> 2. To use a better look-and-feel
>>>> 3. Move it out from svn to git
>>>>
>>>> I proposed to:
>>>>
>>>> 1. Move the existing site to git and generate it with hugo (which is
>>>> a single, standalone binary)
>>>> 2. Move both the rendered and source branches to git.
>>>> 3. (Create a jenkins job to generate the site automatically)
>>>>
>>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
>>>> the documentation which is generated by mvn-site (as before)
>>>>
>>>>
>>>> I got multiple valuable feedback and I improved the proposed site
>>>> according to the comments. Allen had some concerns about the used
>>>> technologies (hugo vs. mvn-site) and I answered all the questions
>>>> why I think mvn-site is the best for documentation and hugo is best
>>>> for generating site.
>>>>
>>>>
>>>> I would like to finish this effort/jira: I would like to start a
>>>> discussion about using this proposed version and approach as a new
>>>> site of Apache Hadoop. Please let me know what you think.
>>>>
>>>>
>>>> Thanks a lot,
>>>> Marton
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Arpit Agarwal <aa...@hortonworks.com>.
+1
Thanks for initiating this Marton.
On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
hadoop.apache.org
3. I will sync manually all of the changes in the next two months back
to the svn site from the git (release announcements, new committers)
IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
If no-one objects within three days, I'll assume lazy consensus and
start with this plan. Please comment if you have objections.
Again: it allows immediate fallback at any time as svn repo will be kept
as is (+ I will keep it up-to-date in the next 2 months)
Thanks,
Marton
On 06/21/2018 09:00 PM, Elek, Marton wrote:
>
> 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 tools.
>
> Hugo has more simple compared to jekyll. Just one binary, without
> dependencies, works everywhere (mac, linux, windows)
>
> Hugo has much more powerful compared to "mvn site". Easier to create/use
> more modern layout/theme, and easier to handle the content (for example
> new release announcements could be generated as part of the release
> process)
>
> I think it's very low risk to try out a new approach for the site (and
> easy to rollback in case of problems)
>
> Marton
>
> ps: I just updated the patch/preview site with the recent releases:
>
> ***************************
> * http://hadoop.anzix.net *
> ***************************
>
> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
>> 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
>> feedback rapidly and get it in.
>>
>> For (2), how about we do it in a different way in the interest of
>> progress?
>> - We create a hadoop.apache.org/new-site/ where this new site goes.
>> - We then modify the existing web-site to say that there is a new
>> site/experience that folks can click on a link and navigate to
>> - As this new website matures and gets feedback & fixes, we finally
>> pull the plug at a later point of time when we think we are good to go.
>>
>> Thoughts?
>>
>> +Vinod
>>
>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>>
>>> 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:
>>>
>>> This thread started long time ago to use a more modern hadoop site:
>>>
>>> Goals were:
>>>
>>> 1. To make it easier to manage it (the release entries could be
>>> created by a script as part of the release process)
>>> 2. To use a better look-and-feel
>>> 3. Move it out from svn to git
>>>
>>> I proposed to:
>>>
>>> 1. Move the existing site to git and generate it with hugo (which is
>>> a single, standalone binary)
>>> 2. Move both the rendered and source branches to git.
>>> 3. (Create a jenkins job to generate the site automatically)
>>>
>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
>>> the documentation which is generated by mvn-site (as before)
>>>
>>>
>>> I got multiple valuable feedback and I improved the proposed site
>>> according to the comments. Allen had some concerns about the used
>>> technologies (hugo vs. mvn-site) and I answered all the questions why
>>> I think mvn-site is the best for documentation and hugo is best for
>>> generating site.
>>>
>>>
>>> I would like to finish this effort/jira: I would like to start a
>>> discussion about using this proposed version and approach as a new
>>> site of Apache Hadoop. Please let me know what you think.
>>>
>>>
>>> Thanks a lot,
>>> Marton
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Mingliang Liu <li...@gmail.com>.
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 <el...@apache.org> 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 ask infra to use the new repository as the source of
> hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back
> to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and
> start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept
> as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
>
>
> On 06/21/2018 09:00 PM, Elek, Marton wrote:
> >
> > 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 tools.
> >
> > Hugo has more simple compared to jekyll. Just one binary, without
> > dependencies, works everywhere (mac, linux, windows)
> >
> > Hugo has much more powerful compared to "mvn site". Easier to create/use
> > more modern layout/theme, and easier to handle the content (for example
> > new release announcements could be generated as part of the release
> > process)
> >
> > I think it's very low risk to try out a new approach for the site (and
> > easy to rollback in case of problems)
> >
> > Marton
> >
> > ps: I just updated the patch/preview site with the recent releases:
> >
> > ***************************
> > * http://hadoop.anzix.net *
> > ***************************
> >
> > On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> >> 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
> >> feedback rapidly and get it in.
> >>
> >> For (2), how about we do it in a different way in the interest of
> >> progress?
> >> - We create a hadoop.apache.org/new-site/ where this new site goes.
> >> - We then modify the existing web-site to say that there is a new
> >> site/experience that folks can click on a link and navigate to
> >> - As this new website matures and gets feedback & fixes, we finally
> >> pull the plug at a later point of time when we think we are good to go.
> >>
> >> Thoughts?
> >>
> >> +Vinod
> >>
> >>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
> >>>
> >>> 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:
> >>>
> >>> This thread started long time ago to use a more modern hadoop site:
> >>>
> >>> Goals were:
> >>>
> >>> 1. To make it easier to manage it (the release entries could be
> >>> created by a script as part of the release process)
> >>> 2. To use a better look-and-feel
> >>> 3. Move it out from svn to git
> >>>
> >>> I proposed to:
> >>>
> >>> 1. Move the existing site to git and generate it with hugo (which is
> >>> a single, standalone binary)
> >>> 2. Move both the rendered and source branches to git.
> >>> 3. (Create a jenkins job to generate the site automatically)
> >>>
> >>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
> >>> the documentation which is generated by mvn-site (as before)
> >>>
> >>>
> >>> I got multiple valuable feedback and I improved the proposed site
> >>> according to the comments. Allen had some concerns about the used
> >>> technologies (hugo vs. mvn-site) and I answered all the questions why
> >>> I think mvn-site is the best for documentation and hugo is best for
> >>> generating site.
> >>>
> >>>
> >>> I would like to finish this effort/jira: I would like to start a
> >>> discussion about using this proposed version and approach as a new
> >>> site of Apache Hadoop. Please let me know what you think.
> >>>
> >>>
> >>> Thanks a lot,
> >>> Marton
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
--
Mingliang Liu
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Arpit Agarwal <aa...@hortonworks.com>.
+1
Thanks for initiating this Marton.
On 8/31/18, 1:07 AM, "Elek, Marton" <el...@apache.org> 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 ask infra to use the new repository as the source of
hadoop.apache.org
3. I will sync manually all of the changes in the next two months back
to the svn site from the git (release announcements, new committers)
IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
If no-one objects within three days, I'll assume lazy consensus and
start with this plan. Please comment if you have objections.
Again: it allows immediate fallback at any time as svn repo will be kept
as is (+ I will keep it up-to-date in the next 2 months)
Thanks,
Marton
On 06/21/2018 09:00 PM, Elek, Marton wrote:
>
> 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 tools.
>
> Hugo has more simple compared to jekyll. Just one binary, without
> dependencies, works everywhere (mac, linux, windows)
>
> Hugo has much more powerful compared to "mvn site". Easier to create/use
> more modern layout/theme, and easier to handle the content (for example
> new release announcements could be generated as part of the release
> process)
>
> I think it's very low risk to try out a new approach for the site (and
> easy to rollback in case of problems)
>
> Marton
>
> ps: I just updated the patch/preview site with the recent releases:
>
> ***************************
> * http://hadoop.anzix.net *
> ***************************
>
> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
>> 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
>> feedback rapidly and get it in.
>>
>> For (2), how about we do it in a different way in the interest of
>> progress?
>> - We create a hadoop.apache.org/new-site/ where this new site goes.
>> - We then modify the existing web-site to say that there is a new
>> site/experience that folks can click on a link and navigate to
>> - As this new website matures and gets feedback & fixes, we finally
>> pull the plug at a later point of time when we think we are good to go.
>>
>> Thoughts?
>>
>> +Vinod
>>
>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>>
>>> 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:
>>>
>>> This thread started long time ago to use a more modern hadoop site:
>>>
>>> Goals were:
>>>
>>> 1. To make it easier to manage it (the release entries could be
>>> created by a script as part of the release process)
>>> 2. To use a better look-and-feel
>>> 3. Move it out from svn to git
>>>
>>> I proposed to:
>>>
>>> 1. Move the existing site to git and generate it with hugo (which is
>>> a single, standalone binary)
>>> 2. Move both the rendered and source branches to git.
>>> 3. (Create a jenkins job to generate the site automatically)
>>>
>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
>>> the documentation which is generated by mvn-site (as before)
>>>
>>>
>>> I got multiple valuable feedback and I improved the proposed site
>>> according to the comments. Allen had some concerns about the used
>>> technologies (hugo vs. mvn-site) and I answered all the questions why
>>> I think mvn-site is the best for documentation and hugo is best for
>>> generating site.
>>>
>>>
>>> I would like to finish this effort/jira: I would like to start a
>>> discussion about using this proposed version and approach as a new
>>> site of Apache Hadoop. Please let me know what you think.
>>>
>>>
>>> Thanks a lot,
>>> Marton
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Steve Loughran <st...@hortonworks.com>.
> On 31 Aug 2018, at 09:07, Elek, Marton <el...@apache.org> 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 ask infra to use the new repository as the source of hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
sounds good to me
+1
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Steve Loughran <st...@hortonworks.com>.
> On 31 Aug 2018, at 09:07, Elek, Marton <el...@apache.org> 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 ask infra to use the new repository as the source of hadoop.apache.org
>
> 3. I will sync manually all of the changes in the next two months back to the svn site from the git (release announcements, new committers)
>
> IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
>
> If no-one objects within three days, I'll assume lazy consensus and start with this plan. Please comment if you have objections.
>
> Again: it allows immediate fallback at any time as svn repo will be kept as is (+ I will keep it up-to-date in the next 2 months)
>
> Thanks,
> Marton
sounds good to me
+1
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by "Elek, Marton" <el...@apache.org>.
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
3. I will sync manually all of the changes in the next two months back
to the svn site from the git (release announcements, new committers)
IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
If no-one objects within three days, I'll assume lazy consensus and
start with this plan. Please comment if you have objections.
Again: it allows immediate fallback at any time as svn repo will be kept
as is (+ I will keep it up-to-date in the next 2 months)
Thanks,
Marton
On 06/21/2018 09:00 PM, Elek, Marton wrote:
>
> 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 tools.
>
> Hugo has more simple compared to jekyll. Just one binary, without
> dependencies, works everywhere (mac, linux, windows)
>
> Hugo has much more powerful compared to "mvn site". Easier to create/use
> more modern layout/theme, and easier to handle the content (for example
> new release announcements could be generated as part of the release
> process)
>
> I think it's very low risk to try out a new approach for the site (and
> easy to rollback in case of problems)
>
> Marton
>
> ps: I just updated the patch/preview site with the recent releases:
>
> ***************************
> * http://hadoop.anzix.net *
> ***************************
>
> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
>> 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
>> feedback rapidly and get it in.
>>
>> For (2), how about we do it in a different way in the interest of
>> progress?
>> - We create a hadoop.apache.org/new-site/ where this new site goes.
>> - We then modify the existing web-site to say that there is a new
>> site/experience that folks can click on a link and navigate to
>> - As this new website matures and gets feedback & fixes, we finally
>> pull the plug at a later point of time when we think we are good to go.
>>
>> Thoughts?
>>
>> +Vinod
>>
>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>>
>>> 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:
>>>
>>> This thread started long time ago to use a more modern hadoop site:
>>>
>>> Goals were:
>>>
>>> 1. To make it easier to manage it (the release entries could be
>>> created by a script as part of the release process)
>>> 2. To use a better look-and-feel
>>> 3. Move it out from svn to git
>>>
>>> I proposed to:
>>>
>>> 1. Move the existing site to git and generate it with hugo (which is
>>> a single, standalone binary)
>>> 2. Move both the rendered and source branches to git.
>>> 3. (Create a jenkins job to generate the site automatically)
>>>
>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
>>> the documentation which is generated by mvn-site (as before)
>>>
>>>
>>> I got multiple valuable feedback and I improved the proposed site
>>> according to the comments. Allen had some concerns about the used
>>> technologies (hugo vs. mvn-site) and I answered all the questions why
>>> I think mvn-site is the best for documentation and hugo is best for
>>> generating site.
>>>
>>>
>>> I would like to finish this effort/jira: I would like to start a
>>> discussion about using this proposed version and approach as a new
>>> site of Apache Hadoop. Please let me know what you think.
>>>
>>>
>>> Thanks a lot,
>>> Marton
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by "Elek, Marton" <el...@apache.org>.
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
3. I will sync manually all of the changes in the next two months back
to the svn site from the git (release announcements, new committers)
IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
If no-one objects within three days, I'll assume lazy consensus and
start with this plan. Please comment if you have objections.
Again: it allows immediate fallback at any time as svn repo will be kept
as is (+ I will keep it up-to-date in the next 2 months)
Thanks,
Marton
On 06/21/2018 09:00 PM, Elek, Marton wrote:
>
> 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 tools.
>
> Hugo has more simple compared to jekyll. Just one binary, without
> dependencies, works everywhere (mac, linux, windows)
>
> Hugo has much more powerful compared to "mvn site". Easier to create/use
> more modern layout/theme, and easier to handle the content (for example
> new release announcements could be generated as part of the release
> process)
>
> I think it's very low risk to try out a new approach for the site (and
> easy to rollback in case of problems)
>
> Marton
>
> ps: I just updated the patch/preview site with the recent releases:
>
> ***************************
> * http://hadoop.anzix.net *
> ***************************
>
> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
>> 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
>> feedback rapidly and get it in.
>>
>> For (2), how about we do it in a different way in the interest of
>> progress?
>> - We create a hadoop.apache.org/new-site/ where this new site goes.
>> - We then modify the existing web-site to say that there is a new
>> site/experience that folks can click on a link and navigate to
>> - As this new website matures and gets feedback & fixes, we finally
>> pull the plug at a later point of time when we think we are good to go.
>>
>> Thoughts?
>>
>> +Vinod
>>
>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>>
>>> 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:
>>>
>>> This thread started long time ago to use a more modern hadoop site:
>>>
>>> Goals were:
>>>
>>> 1. To make it easier to manage it (the release entries could be
>>> created by a script as part of the release process)
>>> 2. To use a better look-and-feel
>>> 3. Move it out from svn to git
>>>
>>> I proposed to:
>>>
>>> 1. Move the existing site to git and generate it with hugo (which is
>>> a single, standalone binary)
>>> 2. Move both the rendered and source branches to git.
>>> 3. (Create a jenkins job to generate the site automatically)
>>>
>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
>>> the documentation which is generated by mvn-site (as before)
>>>
>>>
>>> I got multiple valuable feedback and I improved the proposed site
>>> according to the comments. Allen had some concerns about the used
>>> technologies (hugo vs. mvn-site) and I answered all the questions why
>>> I think mvn-site is the best for documentation and hugo is best for
>>> generating site.
>>>
>>>
>>> I would like to finish this effort/jira: I would like to start a
>>> discussion about using this proposed version and approach as a new
>>> site of Apache Hadoop. Please let me know what you think.
>>>
>>>
>>> Thanks a lot,
>>> Marton
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by "Elek, Marton" <el...@apache.org>.
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
3. I will sync manually all of the changes in the next two months back
to the svn site from the git (release announcements, new committers)
IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
If no-one objects within three days, I'll assume lazy consensus and
start with this plan. Please comment if you have objections.
Again: it allows immediate fallback at any time as svn repo will be kept
as is (+ I will keep it up-to-date in the next 2 months)
Thanks,
Marton
On 06/21/2018 09:00 PM, Elek, Marton wrote:
>
> 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 tools.
>
> Hugo has more simple compared to jekyll. Just one binary, without
> dependencies, works everywhere (mac, linux, windows)
>
> Hugo has much more powerful compared to "mvn site". Easier to create/use
> more modern layout/theme, and easier to handle the content (for example
> new release announcements could be generated as part of the release
> process)
>
> I think it's very low risk to try out a new approach for the site (and
> easy to rollback in case of problems)
>
> Marton
>
> ps: I just updated the patch/preview site with the recent releases:
>
> ***************************
> * http://hadoop.anzix.net *
> ***************************
>
> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
>> 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
>> feedback rapidly and get it in.
>>
>> For (2), how about we do it in a different way in the interest of
>> progress?
>> - We create a hadoop.apache.org/new-site/ where this new site goes.
>> - We then modify the existing web-site to say that there is a new
>> site/experience that folks can click on a link and navigate to
>> - As this new website matures and gets feedback & fixes, we finally
>> pull the plug at a later point of time when we think we are good to go.
>>
>> Thoughts?
>>
>> +Vinod
>>
>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>>
>>> 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:
>>>
>>> This thread started long time ago to use a more modern hadoop site:
>>>
>>> Goals were:
>>>
>>> 1. To make it easier to manage it (the release entries could be
>>> created by a script as part of the release process)
>>> 2. To use a better look-and-feel
>>> 3. Move it out from svn to git
>>>
>>> I proposed to:
>>>
>>> 1. Move the existing site to git and generate it with hugo (which is
>>> a single, standalone binary)
>>> 2. Move both the rendered and source branches to git.
>>> 3. (Create a jenkins job to generate the site automatically)
>>>
>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
>>> the documentation which is generated by mvn-site (as before)
>>>
>>>
>>> I got multiple valuable feedback and I improved the proposed site
>>> according to the comments. Allen had some concerns about the used
>>> technologies (hugo vs. mvn-site) and I answered all the questions why
>>> I think mvn-site is the best for documentation and hugo is best for
>>> generating site.
>>>
>>>
>>> I would like to finish this effort/jira: I would like to start a
>>> discussion about using this proposed version and approach as a new
>>> site of Apache Hadoop. Please let me know what you think.
>>>
>>>
>>> Thanks a lot,
>>> Marton
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by "Elek, Marton" <el...@apache.org>.
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
3. I will sync manually all of the changes in the next two months back
to the svn site from the git (release announcements, new committers)
IN CASE OF ANY PROBLEM we can switch back to the svn without any problem.
If no-one objects within three days, I'll assume lazy consensus and
start with this plan. Please comment if you have objections.
Again: it allows immediate fallback at any time as svn repo will be kept
as is (+ I will keep it up-to-date in the next 2 months)
Thanks,
Marton
On 06/21/2018 09:00 PM, Elek, Marton wrote:
>
> 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 tools.
>
> Hugo has more simple compared to jekyll. Just one binary, without
> dependencies, works everywhere (mac, linux, windows)
>
> Hugo has much more powerful compared to "mvn site". Easier to create/use
> more modern layout/theme, and easier to handle the content (for example
> new release announcements could be generated as part of the release
> process)
>
> I think it's very low risk to try out a new approach for the site (and
> easy to rollback in case of problems)
>
> Marton
>
> ps: I just updated the patch/preview site with the recent releases:
>
> ***************************
> * http://hadoop.anzix.net *
> ***************************
>
> On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
>> 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
>> feedback rapidly and get it in.
>>
>> For (2), how about we do it in a different way in the interest of
>> progress?
>> - We create a hadoop.apache.org/new-site/ where this new site goes.
>> - We then modify the existing web-site to say that there is a new
>> site/experience that folks can click on a link and navigate to
>> - As this new website matures and gets feedback & fixes, we finally
>> pull the plug at a later point of time when we think we are good to go.
>>
>> Thoughts?
>>
>> +Vinod
>>
>>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>>
>>> 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:
>>>
>>> This thread started long time ago to use a more modern hadoop site:
>>>
>>> Goals were:
>>>
>>> 1. To make it easier to manage it (the release entries could be
>>> created by a script as part of the release process)
>>> 2. To use a better look-and-feel
>>> 3. Move it out from svn to git
>>>
>>> I proposed to:
>>>
>>> 1. Move the existing site to git and generate it with hugo (which is
>>> a single, standalone binary)
>>> 2. Move both the rendered and source branches to git.
>>> 3. (Create a jenkins job to generate the site automatically)
>>>
>>> NOTE: this is just about forrest based hadoop.apache.org, NOT about
>>> the documentation which is generated by mvn-site (as before)
>>>
>>>
>>> I got multiple valuable feedback and I improved the proposed site
>>> according to the comments. Allen had some concerns about the used
>>> technologies (hugo vs. mvn-site) and I answered all the questions why
>>> I think mvn-site is the best for documentation and hugo is best for
>>> generating site.
>>>
>>>
>>> I would like to finish this effort/jira: I would like to start a
>>> discussion about using this proposed version and approach as a new
>>> site of Apache Hadoop. Please let me know what you think.
>>>
>>>
>>> Thanks a lot,
>>> Marton
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by "Elek, Marton" <el...@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 tools.
Hugo has more simple compared to jekyll. Just one binary, without
dependencies, works everywhere (mac, linux, windows)
Hugo has much more powerful compared to "mvn site". Easier to create/use
more modern layout/theme, and easier to handle the content (for example
new release announcements could be generated as part of the release
process)
I think it's very low risk to try out a new approach for the site (and
easy to rollback in case of problems)
Marton
ps: I just updated the patch/preview site with the recent releases:
***************************
* http://hadoop.anzix.net *
***************************
On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> 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 feedback rapidly and get it in.
>
> For (2), how about we do it in a different way in the interest of progress?
> - We create a hadoop.apache.org/new-site/ where this new site goes.
> - We then modify the existing web-site to say that there is a new site/experience that folks can click on a link and navigate to
> - As this new website matures and gets feedback & fixes, we finally pull the plug at a later point of time when we think we are good to go.
>
> Thoughts?
>
> +Vinod
>
>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>
>> 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:
>>
>> This thread started long time ago to use a more modern hadoop site:
>>
>> Goals were:
>>
>> 1. To make it easier to manage it (the release entries could be created by a script as part of the release process)
>> 2. To use a better look-and-feel
>> 3. Move it out from svn to git
>>
>> I proposed to:
>>
>> 1. Move the existing site to git and generate it with hugo (which is a single, standalone binary)
>> 2. Move both the rendered and source branches to git.
>> 3. (Create a jenkins job to generate the site automatically)
>>
>> NOTE: this is just about forrest based hadoop.apache.org, NOT about the documentation which is generated by mvn-site (as before)
>>
>>
>> I got multiple valuable feedback and I improved the proposed site according to the comments. Allen had some concerns about the used technologies (hugo vs. mvn-site) and I answered all the questions why I think mvn-site is the best for documentation and hugo is best for generating site.
>>
>>
>> I would like to finish this effort/jira: I would like to start a discussion about using this proposed version and approach as a new site of Apache Hadoop. Please let me know what you think.
>>
>>
>> Thanks a lot,
>> Marton
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by "Elek, Marton" <el...@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 tools.
Hugo has more simple compared to jekyll. Just one binary, without
dependencies, works everywhere (mac, linux, windows)
Hugo has much more powerful compared to "mvn site". Easier to create/use
more modern layout/theme, and easier to handle the content (for example
new release announcements could be generated as part of the release
process)
I think it's very low risk to try out a new approach for the site (and
easy to rollback in case of problems)
Marton
ps: I just updated the patch/preview site with the recent releases:
***************************
* http://hadoop.anzix.net *
***************************
On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> 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 feedback rapidly and get it in.
>
> For (2), how about we do it in a different way in the interest of progress?
> - We create a hadoop.apache.org/new-site/ where this new site goes.
> - We then modify the existing web-site to say that there is a new site/experience that folks can click on a link and navigate to
> - As this new website matures and gets feedback & fixes, we finally pull the plug at a later point of time when we think we are good to go.
>
> Thoughts?
>
> +Vinod
>
>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>
>> 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:
>>
>> This thread started long time ago to use a more modern hadoop site:
>>
>> Goals were:
>>
>> 1. To make it easier to manage it (the release entries could be created by a script as part of the release process)
>> 2. To use a better look-and-feel
>> 3. Move it out from svn to git
>>
>> I proposed to:
>>
>> 1. Move the existing site to git and generate it with hugo (which is a single, standalone binary)
>> 2. Move both the rendered and source branches to git.
>> 3. (Create a jenkins job to generate the site automatically)
>>
>> NOTE: this is just about forrest based hadoop.apache.org, NOT about the documentation which is generated by mvn-site (as before)
>>
>>
>> I got multiple valuable feedback and I improved the proposed site according to the comments. Allen had some concerns about the used technologies (hugo vs. mvn-site) and I answered all the questions why I think mvn-site is the best for documentation and hugo is best for generating site.
>>
>>
>> I would like to finish this effort/jira: I would like to start a discussion about using this proposed version and approach as a new site of Apache Hadoop. Please let me know what you think.
>>
>>
>> Thanks a lot,
>> Marton
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by "Elek, Marton" <el...@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 tools.
Hugo has more simple compared to jekyll. Just one binary, without
dependencies, works everywhere (mac, linux, windows)
Hugo has much more powerful compared to "mvn site". Easier to create/use
more modern layout/theme, and easier to handle the content (for example
new release announcements could be generated as part of the release
process)
I think it's very low risk to try out a new approach for the site (and
easy to rollback in case of problems)
Marton
ps: I just updated the patch/preview site with the recent releases:
***************************
* http://hadoop.anzix.net *
***************************
On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> 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 feedback rapidly and get it in.
>
> For (2), how about we do it in a different way in the interest of progress?
> - We create a hadoop.apache.org/new-site/ where this new site goes.
> - We then modify the existing web-site to say that there is a new site/experience that folks can click on a link and navigate to
> - As this new website matures and gets feedback & fixes, we finally pull the plug at a later point of time when we think we are good to go.
>
> Thoughts?
>
> +Vinod
>
>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>
>> 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:
>>
>> This thread started long time ago to use a more modern hadoop site:
>>
>> Goals were:
>>
>> 1. To make it easier to manage it (the release entries could be created by a script as part of the release process)
>> 2. To use a better look-and-feel
>> 3. Move it out from svn to git
>>
>> I proposed to:
>>
>> 1. Move the existing site to git and generate it with hugo (which is a single, standalone binary)
>> 2. Move both the rendered and source branches to git.
>> 3. (Create a jenkins job to generate the site automatically)
>>
>> NOTE: this is just about forrest based hadoop.apache.org, NOT about the documentation which is generated by mvn-site (as before)
>>
>>
>> I got multiple valuable feedback and I improved the proposed site according to the comments. Allen had some concerns about the used technologies (hugo vs. mvn-site) and I answered all the questions why I think mvn-site is the best for documentation and hugo is best for generating site.
>>
>>
>> I would like to finish this effort/jira: I would like to start a discussion about using this proposed version and approach as a new site of Apache Hadoop. Please let me know what you think.
>>
>>
>> Thanks a lot,
>> Marton
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by "Elek, Marton" <el...@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 tools.
Hugo has more simple compared to jekyll. Just one binary, without
dependencies, works everywhere (mac, linux, windows)
Hugo has much more powerful compared to "mvn site". Easier to create/use
more modern layout/theme, and easier to handle the content (for example
new release announcements could be generated as part of the release
process)
I think it's very low risk to try out a new approach for the site (and
easy to rollback in case of problems)
Marton
ps: I just updated the patch/preview site with the recent releases:
***************************
* http://hadoop.anzix.net *
***************************
On 06/21/2018 01:27 AM, Vinod Kumar Vavilapalli wrote:
> 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 feedback rapidly and get it in.
>
> For (2), how about we do it in a different way in the interest of progress?
> - We create a hadoop.apache.org/new-site/ where this new site goes.
> - We then modify the existing web-site to say that there is a new site/experience that folks can click on a link and navigate to
> - As this new website matures and gets feedback & fixes, we finally pull the plug at a later point of time when we think we are good to go.
>
> Thoughts?
>
> +Vinod
>
>> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>>
>> 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:
>>
>> This thread started long time ago to use a more modern hadoop site:
>>
>> Goals were:
>>
>> 1. To make it easier to manage it (the release entries could be created by a script as part of the release process)
>> 2. To use a better look-and-feel
>> 3. Move it out from svn to git
>>
>> I proposed to:
>>
>> 1. Move the existing site to git and generate it with hugo (which is a single, standalone binary)
>> 2. Move both the rendered and source branches to git.
>> 3. (Create a jenkins job to generate the site automatically)
>>
>> NOTE: this is just about forrest based hadoop.apache.org, NOT about the documentation which is generated by mvn-site (as before)
>>
>>
>> I got multiple valuable feedback and I improved the proposed site according to the comments. Allen had some concerns about the used technologies (hugo vs. mvn-site) and I answered all the questions why I think mvn-site is the best for documentation and hugo is best for generating site.
>>
>>
>> I would like to finish this effort/jira: I would like to start a discussion about using this proposed version and approach as a new site of Apache Hadoop. Please let me know what you think.
>>
>>
>> Thanks a lot,
>> Marton
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
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 feedback rapidly and get it in.
For (2), how about we do it in a different way in the interest of progress?
- We create a hadoop.apache.org/new-site/ where this new site goes.
- We then modify the existing web-site to say that there is a new site/experience that folks can click on a link and navigate to
- As this new website matures and gets feedback & fixes, we finally pull the plug at a later point of time when we think we are good to go.
Thoughts?
+Vinod
> On Feb 16, 2018, at 3:10 AM, Elek, Marton <el...@apache.org> wrote:
>
> 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:
>
> This thread started long time ago to use a more modern hadoop site:
>
> Goals were:
>
> 1. To make it easier to manage it (the release entries could be created by a script as part of the release process)
> 2. To use a better look-and-feel
> 3. Move it out from svn to git
>
> I proposed to:
>
> 1. Move the existing site to git and generate it with hugo (which is a single, standalone binary)
> 2. Move both the rendered and source branches to git.
> 3. (Create a jenkins job to generate the site automatically)
>
> NOTE: this is just about forrest based hadoop.apache.org, NOT about the documentation which is generated by mvn-site (as before)
>
>
> I got multiple valuable feedback and I improved the proposed site according to the comments. Allen had some concerns about the used technologies (hugo vs. mvn-site) and I answered all the questions why I think mvn-site is the best for documentation and hugo is best for generating site.
>
>
> I would like to finish this effort/jira: I would like to start a discussion about using this proposed version and approach as a new site of Apache Hadoop. Please let me know what you think.
>
>
> Thanks a lot,
> Marton
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by "Elek, Marton" <el...@apache.org>.
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:
This thread started long time ago to use a more modern hadoop site:
Goals were:
1. To make it easier to manage it (the release entries could be
created by a script as part of the release process)
2. To use a better look-and-feel
3. Move it out from svn to git
I proposed to:
1. Move the existing site to git and generate it with hugo (which is a
single, standalone binary)
2. Move both the rendered and source branches to git.
3. (Create a jenkins job to generate the site automatically)
NOTE: this is just about forrest based hadoop.apache.org, NOT about the
documentation which is generated by mvn-site (as before)
I got multiple valuable feedback and I improved the proposed site
according to the comments. Allen had some concerns about the used
technologies (hugo vs. mvn-site) and I answered all the questions why I
think mvn-site is the best for documentation and hugo is best for
generating site.
I would like to finish this effort/jira: I would like to start a
discussion about using this proposed version and approach as a new site
of Apache Hadoop. Please let me know what you think.
Thanks a lot,
Marton
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Akira Ajisaka <aa...@apache.org>.
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 <aa...@apache.org> 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 pages and push them to asf-site branch
>> 4. Create a CI job to run 3. automatically when ./asf-site directory is changed
>
>
> Yup. To be more specific on the Jenkins part:
>
> MultiSCM build. Build should be set to poll SCM, probably @daily or equally reasonable.
>
> first SCM: clone hadoop/trunk to one dir
> second SCM: clone hadoop/asf-site to another dir
>
> (Letting Jenkins manage those dirs takes quite a bit of the work out of it)
>
> Run a (modified?) form of create-release so that you get an exact replica of what a released site looks like.
>
> Take site tarball and unpack it into asf-site/.../trunk (or current? or whatever?)
>
> build main site then commit back to asf-site
>
> commit an empty commit to asf-site to work around INFRA-10751. Recommend comment be the git hash of the current hadoop/trunk
>
> FWIW, what we do in Yetus is we actually have the src for the main yetus site as part of our source tree. It gets built as part of the release.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Allen Wittenauer <aw...@effectivemachines.com>.
> On Aug 8, 2017, at 12:36 AM, Akira Ajisaka <aa...@apache.org> 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 pages and push them to asf-site branch
> 4. Create a CI job to run 3. automatically when ./asf-site directory is changed
Yup. To be more specific on the Jenkins part:
MultiSCM build. Build should be set to poll SCM, probably @daily or equally reasonable.
first SCM: clone hadoop/trunk to one dir
second SCM: clone hadoop/asf-site to another dir
(Letting Jenkins manage those dirs takes quite a bit of the work out of it)
Run a (modified?) form of create-release so that you get an exact replica of what a released site looks like.
Take site tarball and unpack it into asf-site/.../trunk (or current? or whatever?)
build main site then commit back to asf-site
commit an empty commit to asf-site to work around INFRA-10751. Recommend comment be the git hash of the current hadoop/trunk
FWIW, what we do in Yetus is we actually have the src for the main yetus site as part of our source tree. It gets built as part of the release.
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Akira Ajisaka <aa...@apache.org>.
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 of the site source easily.
Con: We need to manage the two different repositories.
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 pages and push them to asf-site branch
4. Create a CI job to run 3. automatically when ./asf-site directory is changed
-Akira
On 2017/08/07 23:06, Allen Wittenauer wrote:
>
>> On Aug 7, 2017, at 3:53 AM, Akira Ajisaka <aa...@apache.org> 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.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Allen Wittenauer <aw...@effectivemachines.com>.
> On Aug 7, 2017, at 3:53 AM, Akira Ajisaka <aa...@apache.org> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Akira Ajisaka <aa...@apache.org>.
Hi folks,
I'd like to create a separate git repository for the web site (now managed in svn).
For more details, please see the discussion in https://issues.apache.org/jira/browse/HADOOP-14163.
I'll ask INFRA to create a git repository if there are no objections.
Thanks Marton Elek for the continuous work.
Regards,
Akira
On 2017/03/25 3:35, Andrew Wang wrote:
> Thanks again for working on this Marton!
>
> Based on my read of the blog post you linked, we should have the git branch
> ready before asking infra to switch it over.
>
> I can do a more detailed review on the JIRA once you rev, and can help with
> the INFRA ticket once it's ready. We'll also have to update BUILDING.txt
> and the wiki instructions as part of this.
>
> Best,
> Andrew
>
> On Fri, Mar 24, 2017 at 3:06 AM, Marton Elek <me...@hortonworks.com> wrote:
>
>>
>>
>> Thank you all of the feedbacks, I fixed all of them (except one, see the
>> comment below) and updated the http://hadoop.anzix.net preview site.
>>
>> So the next steps:
>>
>> 0. Let me know if you have any comment about the latest version
>>
>> 1. I wait for the 2.8.0 announcement, and migrate the new announcement as
>> well. (wouldn't like to complicate the 2.8.0 with the site change)
>>
>> 2. I like the suggestion of Owen to move the site to a specific git
>> branch. I wouldn't like to pending on it if it's too much time, but if any
>> of the commiters could pick it up, I would wait for it.
>>
>> I tested it, and seems to be easy:
>>
>> git svn clone https://svn.apache.org/repos/asf/hadoop/common/site/main
>> cd main
>> git remote add elek git@github.com:elek/hadoop.git
>> git push elek master:asf-site
>>
>> According to the blog entry, an INFRA issue should be opened (I guess by a
>> commiter or maybe a pmc member):
>>
>> https://blogs.apache.org/infra/entry/git_based_websites_available
>>
>> 3. After that I can submit the new site as a regular patch against the
>> asf-site branch.
>>
>> 4. If it's merged, I can update the release wiki pages
>>
>> Marton
>>
>> ps:
>>
>> The only suggested item which is not implemented is the short version
>> names in the documentation menu (2.7 instead of 2.7.3).
>>
>> I think there are two forces: usability of the site and the simplicity of
>> the site generation. Ideally a new release could be added to the site as
>> easy as possible (that was one of the motivation of the migration).
>>
>> While a new tag could be added to the header of the markdown files (eg:
>> versionLine: 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.
>>
>> 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.
>>
>>
>> ________________________________________
>> From: Owen O'Malley <om...@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 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. It
>> should use the direct links, such as
>>
>> https://dist.apache.org/repos/dist/release/hadoop/common/
>> hadoop-2.7.3/hadoop-2.7.3-src.tar.gz.asc
>> https://dist.apache.org/repos/dist/release/hadoop/common/
>> hadoop-2.7.3/hadoop-2.7.3-src.tar.gz.mds
>>
>> Speaking of which, Hadoop's dist directory is huge and should be heavily
>> pruned. We should probably take it down to just hadoop-2.6.5, hadoop-2.7.3,
>> and hadoop-3.0.0-alpha2.
>>
>> You might also want to move us to git-pubsub so that we can use a branch in
>> our source code git repository to publish the html. Typically this uses the
>> asf-site branch.
>>
>> .. Owen
>>
>> On Mon, Mar 13, 2017 at 7:28 AM, Marton Elek <me...@hortonworks.com>
>> wrote:
>>
>>>
>>> Hi,
>>>
>>> In the previous thread the current forrest based hadoop site is
>> identified
>>> as one of the pain points of the release process.
>>>
>>> I created a new version of the site with exactly the same content.
>>>
>>> As it uses newer site generator (hugo), now:
>>>
>>> 1. It’s enough to create one new markdown file per release, and all the
>>> documentation/download links will be automatically added.
>>> 2. It requires only one single binary to render.
>>>
>>>
>>> A preview version is temporary hosted at
>>>
>>> http://hadoop.anzix.net/
>>>
>>> to make it easier to review.
>>>
>>>
>>> For more details, you can check my comments on the issue
>>> https://issues.apache.org/jira/browse/HADOOP-14163
>>>
>>> I would be thankful to get any feedback/review.
>>>
>>> Cheers,
>>> Marton
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Andrew Wang <an...@cloudera.com>.
Thanks again for working on this Marton!
Based on my read of the blog post you linked, we should have the git branch
ready before asking infra to switch it over.
I can do a more detailed review on the JIRA once you rev, and can help with
the INFRA ticket once it's ready. We'll also have to update BUILDING.txt
and the wiki instructions as part of this.
Best,
Andrew
On Fri, Mar 24, 2017 at 3:06 AM, Marton Elek <me...@hortonworks.com> wrote:
>
>
> Thank you all of the feedbacks, I fixed all of them (except one, see the
> comment below) and updated the http://hadoop.anzix.net preview site.
>
> So the next steps:
>
> 0. Let me know if you have any comment about the latest version
>
> 1. I wait for the 2.8.0 announcement, and migrate the new announcement as
> well. (wouldn't like to complicate the 2.8.0 with the site change)
>
> 2. I like the suggestion of Owen to move the site to a specific git
> branch. I wouldn't like to pending on it if it's too much time, but if any
> of the commiters could pick it up, I would wait for it.
>
> I tested it, and seems to be easy:
>
> git svn clone https://svn.apache.org/repos/asf/hadoop/common/site/main
> cd main
> git remote add elek git@github.com:elek/hadoop.git
> git push elek master:asf-site
>
> According to the blog entry, an INFRA issue should be opened (I guess by a
> commiter or maybe a pmc member):
>
> https://blogs.apache.org/infra/entry/git_based_websites_available
>
> 3. After that I can submit the new site as a regular patch against the
> asf-site branch.
>
> 4. If it's merged, I can update the release wiki pages
>
> Marton
>
> ps:
>
> The only suggested item which is not implemented is the short version
> names in the documentation menu (2.7 instead of 2.7.3).
>
> I think there are two forces: usability of the site and the simplicity of
> the site generation. Ideally a new release could be added to the site as
> easy as possible (that was one of the motivation of the migration).
>
> While a new tag could be added to the header of the markdown files (eg:
> versionLine: 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.
>
> 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.
>
>
> ________________________________________
> From: Owen O'Malley <om...@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 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. It
> should use the direct links, such as
>
> https://dist.apache.org/repos/dist/release/hadoop/common/
> hadoop-2.7.3/hadoop-2.7.3-src.tar.gz.asc
> https://dist.apache.org/repos/dist/release/hadoop/common/
> hadoop-2.7.3/hadoop-2.7.3-src.tar.gz.mds
>
> Speaking of which, Hadoop's dist directory is huge and should be heavily
> pruned. We should probably take it down to just hadoop-2.6.5, hadoop-2.7.3,
> and hadoop-3.0.0-alpha2.
>
> You might also want to move us to git-pubsub so that we can use a branch in
> our source code git repository to publish the html. Typically this uses the
> asf-site branch.
>
> .. Owen
>
> On Mon, Mar 13, 2017 at 7:28 AM, Marton Elek <me...@hortonworks.com>
> wrote:
>
> >
> > Hi,
> >
> > In the previous thread the current forrest based hadoop site is
> identified
> > as one of the pain points of the release process.
> >
> > I created a new version of the site with exactly the same content.
> >
> > As it uses newer site generator (hugo), now:
> >
> > 1. It’s enough to create one new markdown file per release, and all the
> > documentation/download links will be automatically added.
> > 2. It requires only one single binary to render.
> >
> >
> > A preview version is temporary hosted at
> >
> > http://hadoop.anzix.net/
> >
> > to make it easier to review.
> >
> >
> > For more details, you can check my comments on the issue
> > https://issues.apache.org/jira/browse/HADOOP-14163
> >
> > I would be thankful to get any feedback/review.
> >
> > Cheers,
> > Marton
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Marton Elek <me...@hortonworks.com>.
Thank you all of the feedbacks, I fixed all of them (except one, see the comment below) and updated the http://hadoop.anzix.net preview site.
So the next steps:
0. Let me know if you have any comment about the latest version
1. I wait for the 2.8.0 announcement, and migrate the new announcement as well. (wouldn't like to complicate the 2.8.0 with the site change)
2. I like the suggestion of Owen to move the site to a specific git branch. I wouldn't like to pending on it if it's too much time, but if any of the commiters could pick it up, I would wait for it.
I tested it, and seems to be easy:
git svn clone https://svn.apache.org/repos/asf/hadoop/common/site/main
cd main
git remote add elek git@github.com:elek/hadoop.git
git push elek master:asf-site
According to the blog entry, an INFRA issue should be opened (I guess by a commiter or maybe a pmc member):
https://blogs.apache.org/infra/entry/git_based_websites_available
3. After that I can submit the new site as a regular patch against the asf-site branch.
4. If it's merged, I can update the release wiki pages
Marton
ps:
The only suggested item which is not implemented is the short version names in the documentation menu (2.7 instead of 2.7.3).
I think there are two forces: usability of the site and the simplicity of the site generation. Ideally a new release could be added to the site as easy as possible (that was one of the motivation of the migration).
While a new tag could be added to the header of the markdown files (eg: versionLine: 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.
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.
________________________________________
From: Owen O'Malley <om...@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 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. It
should use the direct links, such as
https://dist.apache.org/repos/dist/release/hadoop/common/hadoop-2.7.3/hadoop-2.7.3-src.tar.gz.asc
https://dist.apache.org/repos/dist/release/hadoop/common/hadoop-2.7.3/hadoop-2.7.3-src.tar.gz.mds
Speaking of which, Hadoop's dist directory is huge and should be heavily
pruned. We should probably take it down to just hadoop-2.6.5, hadoop-2.7.3,
and hadoop-3.0.0-alpha2.
You might also want to move us to git-pubsub so that we can use a branch in
our source code git repository to publish the html. Typically this uses the
asf-site branch.
.. Owen
On Mon, Mar 13, 2017 at 7:28 AM, Marton Elek <me...@hortonworks.com> wrote:
>
> Hi,
>
> In the previous thread the current forrest based hadoop site is identified
> as one of the pain points of the release process.
>
> I created a new version of the site with exactly the same content.
>
> As it uses newer site generator (hugo), now:
>
> 1. It’s enough to create one new markdown file per release, and all the
> documentation/download links will be automatically added.
> 2. It requires only one single binary to render.
>
>
> A preview version is temporary hosted at
>
> http://hadoop.anzix.net/
>
> to make it easier to review.
>
>
> For more details, you can check my comments on the issue
> https://issues.apache.org/jira/browse/HADOOP-14163
>
> I would be thankful to get any feedback/review.
>
> Cheers,
> Marton
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: HADOOP-14163 proposal for new hadoop.apache.org
Posted by Owen O'Malley <om...@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 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. It
should use the direct links, such as
https://dist.apache.org/repos/dist/release/hadoop/common/hadoop-2.7.3/hadoop-2.7.3-src.tar.gz.asc
https://dist.apache.org/repos/dist/release/hadoop/common/hadoop-2.7.3/hadoop-2.7.3-src.tar.gz.mds
Speaking of which, Hadoop's dist directory is huge and should be heavily
pruned. We should probably take it down to just hadoop-2.6.5, hadoop-2.7.3,
and hadoop-3.0.0-alpha2.
You might also want to move us to git-pubsub so that we can use a branch in
our source code git repository to publish the html. Typically this uses the
asf-site branch.
.. Owen
On Mon, Mar 13, 2017 at 7:28 AM, Marton Elek <me...@hortonworks.com> wrote:
>
> Hi,
>
> In the previous thread the current forrest based hadoop site is identified
> as one of the pain points of the release process.
>
> I created a new version of the site with exactly the same content.
>
> As it uses newer site generator (hugo), now:
>
> 1. It’s enough to create one new markdown file per release, and all the
> documentation/download links will be automatically added.
> 2. It requires only one single binary to render.
>
>
> A preview version is temporary hosted at
>
> http://hadoop.anzix.net/
>
> to make it easier to review.
>
>
> For more details, you can check my comments on the issue
> https://issues.apache.org/jira/browse/HADOOP-14163
>
> I would be thankful to get any feedback/review.
>
> Cheers,
> Marton
>
>
>