You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by Nicolò Boschi <bo...@gmail.com> on 2022/03/09 20:30:49 UTC
New Docusaurus website - ready for review
Dear community,
I resumed the initial work intended to migrate the website to the
Docusaurus engine.
I recreated the whole website under the 'site3' directory. This is the pull
https://github.com/apache/bookkeeper/pull/3088
There are a couple of changes I have had to do and they are all mentioned
in the pull request.
I pushed the website here:
https://nicoloboschi.github.io/bookkeeper
My plan would be the following:
- Have people try it out, find bugs, problems, typos and fix them all
- Create the apache staging deployment (as explained here [0]). Basically
we'll need to create a github action to push to the asf-staging-site branch
and enable deployment with .asf.yaml file
- After a while, make the official switch
WDYT ?
[0]
https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Stagingawebsitepreviewdomain
BR,
Nicolò Boschi
Re: New Docusaurus website - ready for review
Posted by Henry Saputra <he...@gmail.com>.
Ack and Sounds good to me, Andrey.
- Henry
On Wed, Mar 16, 2022 at 1:46 PM Andrey Yegorov <an...@datastax.com>
wrote:
> I merged it to let Nicolo continue on this.
> I cannot review all 64000 lines there ;) but I cursory looked at the
> changes + they are isolated
> in their own directory and we can always rebuild the old site.
>
> On Wed, Mar 16, 2022 at 8:18 AM Nicolò Boschi <bo...@gmail.com>
> wrote:
>
> > Since I didn't get any feedback, I think we can merge the work
> >
> > I will follow up with a PR to deploy it to staging
> > Thanks Enrico
> >
> > Nicolò Boschi
> >
> >
> > Il giorno mer 9 mar 2022 alle ore 22:06 Nicolò Boschi <
> > boschi1997@gmail.com>
> > ha scritto:
> >
> > > Thanks Enrico
> > >
> > > In general it is possible that we cherry pick new little features and
> > that
> > >> we have to have versioned docs.
> > >
> > >
> > > I would prefer to specify this change in the specific doc, saying
> > > something like "this flag has been introduced in 4.15.y"
> > >
> > >
> > >
> > > Il giorno mer 9 mar 2022 alle ore 21:40 Enrico Olivelli <
> > > eolivelli@gmail.com> ha scritto:
> > >
> > >> I totally support this initiative!
> > >> Especially if we can simply working on the website, adding docs and
> > >> writing
> > >> release notes.
> > >>
> > >> The point I have about your PR is that we are keeping only one version
> > per
> > >> each major release.
> > >> In general it is possible that we cherry pick new little features and
> > that
> > >> we have to have versioned docs.
> > >> That said, I have been following this projects for much time and I
> guess
> > >> it
> > >> won't happen often.
> > >>
> > >> I am +1 to committing your PR as it is in the current form as soon as
> > >> possible.
> > >>
> > >> Thank you very much!
> > >>
> > >> Enrico
> > >>
> > >>
> > >> Side note: we should exclude running tests for changes in the 'site3'
> > >> directory
> > >>
> > >> Il Mer 9 Mar 2022, 21:31 Nicolò Boschi <bo...@gmail.com> ha
> > scritto:
> > >>
> > >> > Dear community,
> > >> >
> > >> > I resumed the initial work intended to migrate the website to the
> > >> > Docusaurus engine.
> > >> > I recreated the whole website under the 'site3' directory. This is
> the
> > >> pull
> > >> > https://github.com/apache/bookkeeper/pull/3088
> > >> >
> > >> > There are a couple of changes I have had to do and they are all
> > >> mentioned
> > >> > in the pull request.
> > >> > I pushed the website here:
> > >> >
> >
> https://urldefense.com/v3/__https://nicoloboschi.github.io/bookkeeper__;!!PbtH5S7Ebw!aBgi8sqV9ztSRdKefg9Eb2BRM7I1CBVx0hT1AMUErTfeif1CTLkb6-_RzgvlDTCkfZ_cwM9JEqVGb3k5P6d4PzmxMA$
> > >> >
> > >> > My plan would be the following:
> > >> > - Have people try it out, find bugs, problems, typos and fix them
> all
> > >> > - Create the apache staging deployment (as explained here [0]).
> > >> Basically
> > >> > we'll need to create a github action to push to the asf-staging-site
> > >> branch
> > >> > and enable deployment with .asf.yaml file
> > >> > - After a while, make the official switch
> > >> >
> > >> > WDYT ?
> > >> >
> > >> >
> > >> > [0]
> > >> >
> > >> >
> > >>
> >
> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Stagingawebsitepreviewdomain
> > >> >
> > >> >
> > >> >
> > >> > BR,
> > >> > Nicolò Boschi
> > >> >
> > >>
> > >
> > >
> > > Nicolò Boschi
> > >
> >
>
>
> --
> Andrey Yegorov
>
Re: New Docusaurus website - ready for review
Posted by Andrey Yegorov <an...@datastax.com>.
I merged it to let Nicolo continue on this.
I cannot review all 64000 lines there ;) but I cursory looked at the
changes + they are isolated
in their own directory and we can always rebuild the old site.
On Wed, Mar 16, 2022 at 8:18 AM Nicolò Boschi <bo...@gmail.com> wrote:
> Since I didn't get any feedback, I think we can merge the work
>
> I will follow up with a PR to deploy it to staging
> Thanks Enrico
>
> Nicolò Boschi
>
>
> Il giorno mer 9 mar 2022 alle ore 22:06 Nicolò Boschi <
> boschi1997@gmail.com>
> ha scritto:
>
> > Thanks Enrico
> >
> > In general it is possible that we cherry pick new little features and
> that
> >> we have to have versioned docs.
> >
> >
> > I would prefer to specify this change in the specific doc, saying
> > something like "this flag has been introduced in 4.15.y"
> >
> >
> >
> > Il giorno mer 9 mar 2022 alle ore 21:40 Enrico Olivelli <
> > eolivelli@gmail.com> ha scritto:
> >
> >> I totally support this initiative!
> >> Especially if we can simply working on the website, adding docs and
> >> writing
> >> release notes.
> >>
> >> The point I have about your PR is that we are keeping only one version
> per
> >> each major release.
> >> In general it is possible that we cherry pick new little features and
> that
> >> we have to have versioned docs.
> >> That said, I have been following this projects for much time and I guess
> >> it
> >> won't happen often.
> >>
> >> I am +1 to committing your PR as it is in the current form as soon as
> >> possible.
> >>
> >> Thank you very much!
> >>
> >> Enrico
> >>
> >>
> >> Side note: we should exclude running tests for changes in the 'site3'
> >> directory
> >>
> >> Il Mer 9 Mar 2022, 21:31 Nicolò Boschi <bo...@gmail.com> ha
> scritto:
> >>
> >> > Dear community,
> >> >
> >> > I resumed the initial work intended to migrate the website to the
> >> > Docusaurus engine.
> >> > I recreated the whole website under the 'site3' directory. This is the
> >> pull
> >> > https://github.com/apache/bookkeeper/pull/3088
> >> >
> >> > There are a couple of changes I have had to do and they are all
> >> mentioned
> >> > in the pull request.
> >> > I pushed the website here:
> >> >
> https://urldefense.com/v3/__https://nicoloboschi.github.io/bookkeeper__;!!PbtH5S7Ebw!aBgi8sqV9ztSRdKefg9Eb2BRM7I1CBVx0hT1AMUErTfeif1CTLkb6-_RzgvlDTCkfZ_cwM9JEqVGb3k5P6d4PzmxMA$
> >> >
> >> > My plan would be the following:
> >> > - Have people try it out, find bugs, problems, typos and fix them all
> >> > - Create the apache staging deployment (as explained here [0]).
> >> Basically
> >> > we'll need to create a github action to push to the asf-staging-site
> >> branch
> >> > and enable deployment with .asf.yaml file
> >> > - After a while, make the official switch
> >> >
> >> > WDYT ?
> >> >
> >> >
> >> > [0]
> >> >
> >> >
> >>
> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Stagingawebsitepreviewdomain
> >> >
> >> >
> >> >
> >> > BR,
> >> > Nicolò Boschi
> >> >
> >>
> >
> >
> > Nicolò Boschi
> >
>
--
Andrey Yegorov
Re: New Docusaurus website - ready for review
Posted by Nicolò Boschi <bo...@gmail.com>.
Since I didn't get any feedback, I think we can merge the work
I will follow up with a PR to deploy it to staging
Thanks Enrico
Nicolò Boschi
Il giorno mer 9 mar 2022 alle ore 22:06 Nicolò Boschi <bo...@gmail.com>
ha scritto:
> Thanks Enrico
>
> In general it is possible that we cherry pick new little features and that
>> we have to have versioned docs.
>
>
> I would prefer to specify this change in the specific doc, saying
> something like "this flag has been introduced in 4.15.y"
>
>
>
> Il giorno mer 9 mar 2022 alle ore 21:40 Enrico Olivelli <
> eolivelli@gmail.com> ha scritto:
>
>> I totally support this initiative!
>> Especially if we can simply working on the website, adding docs and
>> writing
>> release notes.
>>
>> The point I have about your PR is that we are keeping only one version per
>> each major release.
>> In general it is possible that we cherry pick new little features and that
>> we have to have versioned docs.
>> That said, I have been following this projects for much time and I guess
>> it
>> won't happen often.
>>
>> I am +1 to committing your PR as it is in the current form as soon as
>> possible.
>>
>> Thank you very much!
>>
>> Enrico
>>
>>
>> Side note: we should exclude running tests for changes in the 'site3'
>> directory
>>
>> Il Mer 9 Mar 2022, 21:31 Nicolò Boschi <bo...@gmail.com> ha scritto:
>>
>> > Dear community,
>> >
>> > I resumed the initial work intended to migrate the website to the
>> > Docusaurus engine.
>> > I recreated the whole website under the 'site3' directory. This is the
>> pull
>> > https://github.com/apache/bookkeeper/pull/3088
>> >
>> > There are a couple of changes I have had to do and they are all
>> mentioned
>> > in the pull request.
>> > I pushed the website here:
>> > https://nicoloboschi.github.io/bookkeeper
>> >
>> > My plan would be the following:
>> > - Have people try it out, find bugs, problems, typos and fix them all
>> > - Create the apache staging deployment (as explained here [0]).
>> Basically
>> > we'll need to create a github action to push to the asf-staging-site
>> branch
>> > and enable deployment with .asf.yaml file
>> > - After a while, make the official switch
>> >
>> > WDYT ?
>> >
>> >
>> > [0]
>> >
>> >
>> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Stagingawebsitepreviewdomain
>> >
>> >
>> >
>> > BR,
>> > Nicolò Boschi
>> >
>>
>
>
> Nicolò Boschi
>
Re: New Docusaurus website - ready for review
Posted by Nicolò Boschi <bo...@gmail.com>.
Thanks Enrico
In general it is possible that we cherry pick new little features and that
> we have to have versioned docs.
I would prefer to specify this change in the specific doc, saying something
like "this flag has been introduced in 4.15.y"
Il giorno mer 9 mar 2022 alle ore 21:40 Enrico Olivelli <eo...@gmail.com>
ha scritto:
> I totally support this initiative!
> Especially if we can simply working on the website, adding docs and writing
> release notes.
>
> The point I have about your PR is that we are keeping only one version per
> each major release.
> In general it is possible that we cherry pick new little features and that
> we have to have versioned docs.
> That said, I have been following this projects for much time and I guess it
> won't happen often.
>
> I am +1 to committing your PR as it is in the current form as soon as
> possible.
>
> Thank you very much!
>
> Enrico
>
>
> Side note: we should exclude running tests for changes in the 'site3'
> directory
>
> Il Mer 9 Mar 2022, 21:31 Nicolò Boschi <bo...@gmail.com> ha scritto:
>
> > Dear community,
> >
> > I resumed the initial work intended to migrate the website to the
> > Docusaurus engine.
> > I recreated the whole website under the 'site3' directory. This is the
> pull
> > https://github.com/apache/bookkeeper/pull/3088
> >
> > There are a couple of changes I have had to do and they are all mentioned
> > in the pull request.
> > I pushed the website here:
> > https://nicoloboschi.github.io/bookkeeper
> >
> > My plan would be the following:
> > - Have people try it out, find bugs, problems, typos and fix them all
> > - Create the apache staging deployment (as explained here [0]). Basically
> > we'll need to create a github action to push to the asf-staging-site
> branch
> > and enable deployment with .asf.yaml file
> > - After a while, make the official switch
> >
> > WDYT ?
> >
> >
> > [0]
> >
> >
> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Stagingawebsitepreviewdomain
> >
> >
> >
> > BR,
> > Nicolò Boschi
> >
>
Nicolò Boschi
Re: New Docusaurus website - ready for review
Posted by Enrico Olivelli <eo...@gmail.com>.
I totally support this initiative!
Especially if we can simply working on the website, adding docs and writing
release notes.
The point I have about your PR is that we are keeping only one version per
each major release.
In general it is possible that we cherry pick new little features and that
we have to have versioned docs.
That said, I have been following this projects for much time and I guess it
won't happen often.
I am +1 to committing your PR as it is in the current form as soon as
possible.
Thank you very much!
Enrico
Side note: we should exclude running tests for changes in the 'site3'
directory
Il Mer 9 Mar 2022, 21:31 Nicolò Boschi <bo...@gmail.com> ha scritto:
> Dear community,
>
> I resumed the initial work intended to migrate the website to the
> Docusaurus engine.
> I recreated the whole website under the 'site3' directory. This is the pull
> https://github.com/apache/bookkeeper/pull/3088
>
> There are a couple of changes I have had to do and they are all mentioned
> in the pull request.
> I pushed the website here:
> https://nicoloboschi.github.io/bookkeeper
>
> My plan would be the following:
> - Have people try it out, find bugs, problems, typos and fix them all
> - Create the apache staging deployment (as explained here [0]). Basically
> we'll need to create a github action to push to the asf-staging-site branch
> and enable deployment with .asf.yaml file
> - After a while, make the official switch
>
> WDYT ?
>
>
> [0]
>
> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Stagingawebsitepreviewdomain
>
>
>
> BR,
> Nicolò Boschi
>