Lets start a merge vote that will run for 3 days, so that this gets
committed later this week.

On Mon, Dec 18, 2017 at 4:21 AM, Tsz Wo Sze <szets...@gmail.com> wrote:

> The web site looks really good.  Thanks a lot for all the hard and
> beautiful works!
> Nicholas
>
> On Sat, Dec 16, 2017 at 3:22 AM, anu engineer <anu.engin...@gmail.com>
> wrote:
> > Since it is a Ratis branch, should we do a formal vote and merge like
> > Hadoop?  I have looked at the changes very deeply and I am happy with it,
> > but I would like to establish conventions on how to merge code into
> Ratis.
> > Thoughts ?
> >
> > Thanks
> > Anu
> >
> >
> > On Fri, Dec 15, 2017 at 3:09 AM, Elek, Marton <h...@anzix.net> wrote:
> >
> >> Hi,
> >>
> >> The final proposed version could be checked here:
> >>
> >> https://elek.github.io/ratis-site/
> >>
> >> The source is attached to the jira https://issues.apache.org/jira
> >> /browse/RATIS-5
> >>
> >> Please have a final look and comment.
> >>
> >> If no more objections, I will commit both the source and rendered
> version
> >> to separated branches (asf-site-source/asf-site) and open an INFRA
> ticket
> >> to use it as the source of http://ratis.incubator.apache.org/
> >>
> >> Thanks,
> >> Marton
> >>
> >>
> >> On 11/18/2017 03:49 PM, Anu Engineer wrote:
> >>
> >>> Let us move this discussion to the JIRA,
> https://issues.apache.org/jira
> >>> /browse/RATIS-5
> >>> That way we will not lose these ideas/work items.
> >>>
> >>> Thanks
> >>> Anu
> >>>
> >>>
> >>> On 11/18/17, 5:18 AM, "Mukul Kumar Singh" <msi...@hortonworks.com>
> wrote:
> >>>
> >>>      +1, Excellent idea.
> >>>           I was also thinking if we an add pages for some example on
> how
> >>> to setup and use ratis in applications.
> >>>           Thanks,
> >>>      Mukul
> >>>           > On 18-Nov-2017, at 4:12 AM, Hugo Louro <hmclo...@gmail.com
> >
> >>> wrote:
> >>>      >
> >>>      > +1 - Great idea. I wonder if there are some templates around
> >>>      > incubator/Apache projects that you can use that will make it
> >>> easier and
> >>>      > more consistent with other projects.
> >>>      >
> >>>      > I am not sure I follow the reason to have this in a google doc.
> >>> Why not use
> >>>      > html/markdown with Git alone. You can have this in it's own
> branch
> >>> to
> >>>      > start, and then when it's ready you can simply create a pull
> >>> request.
> >>>      >
> >>>      > Thanks
> >>>      > Hugo
> >>>      >
> >>>      > On Fri, Nov 17, 2017 at 11:20 AM, Tsz Wo Sze <
> szets...@gmail.com>
> >>> wrote:
> >>>      >
> >>>      >> Thanks a lot, Marton.  I just have assigned RATIS-5 "Setup
> >>> website" to you.
> >>>      >> Nicholas
> >>>      >>
> >>>      >> On Fri, Nov 17, 2017 at 11:10 AM, Jing Zhao <ji...@apache.org>
> >>> wrote:
> >>>      >>> +1. Thanks Marton!
> >>>      >>>
> >>>      >>> On Fri, Nov 17, 2017 at 9:43 AM, Anu Engineer <
> >>> aengin...@hortonworks.com
> >>>      >>>
> >>>      >>> wrote:
> >>>      >>>
> >>>      >>>> +1, great idea. I would like to work with you on this.
> >>>      >>>>
> >>>      >>>> Thanks
> >>>      >>>> Anu
> >>>      >>>>
> >>>      >>>> On 11/17/17, 12:55 AM, "Elek, Marton" <h...@anzix.net> wrote:
> >>>      >>>>
> >>>      >>>>    Hi,
> >>>      >>>>
> >>>      >>>>    Is there any plan for ratis webpage? I didn't find any
> Jira.
> >>>      >>>>
> >>>      >>>>    My proposal is the following:
> >>>      >>>>
> >>>      >>>>    1. I can create a draft site similar to my hadoop site
> >>> proposal:
> >>>      >>>>    https://hadoop.anzix.net/
> >>>      >>>>
> >>>      >>>>    2. I can collect the content from ratis presentations.
> >>>      >>>>
> >>>      >>>>    3. I can copy the content to a google docs to make it
> easier
> >>> to
> >>>      >>>>    fix/improve the content together.
> >>>      >>>>
> >>>      >>>>    4. I will copy back the content to the html/markdown files
> >>> and we
> >>>      >> can
> >>>      >>>>    commit it to the git repo using a separated branch.
> >>>      >>>>
> >>>      >>>>    I propose to do a simple page (what is ratis?) as a first
> >>> step and
> >>>      >>>> after
> >>>      >>>>    that we can extend with more detailed/version specific
> >>> documentation
> >>>      >>>>    (such like a getting started guide...)
> >>>      >>>>
> >>>      >>>>    Any thoughts?
> >>>      >>>>
> >>>      >>>>    Thanks,
> >>>      >>>>    Marton
> >>>      >>>>
> >>>      >>>>
> >>>      >>>>
> >>>      >>>>
> >>>      >>
> >>>
> >>>
> >>
>

Reply via email to