You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Dave Fisher <wa...@apache.org> on 2021/06/01 23:34:40 UTC
Re: CMS Migration for River
Hi -
Please find your staged migrated site at https://river.staged.apache.org <https://river.staged.apache.org/>
The repository is at https://github.com/apache/river-site <https://github.com/apache/river-site>
I’ll be updating the README.md files in the next day or two including notes on the migration.
All The Best,
Dave
> On May 29, 2021, at 12:45 PM, Dave Fisher <wa...@apache.org> wrote:
>
> I may have questions once the migration is started.
>
> I’ll definitely need review once the new repository with the migrated content is ready.
>
>> On May 29, 2021, at 11:28 AM, Jeremy R. Easton-Marks <J....@gmail.com> wrote:
>>
>> Thanks Dave. Do you need anything from the River team for this process?
>>
>> On Sat, May 29, 2021 at 11:43 AM Dave Fisher <wa...@apache.org> wrote:
>>
>>> As you may recall the Apache CMS has been deprecated for over five years
>>> now and will be decommissioned
>>> by July 31, 2021.
>>>
>>> I’ve been tasked with moving River's website away from the Apache CMS.
>>> I will migrate your website to a Pelican build with GitHub Flavored
>>> Markdown (GFM).
>>> For your reference the already migrated www-site is here
>>> https://github.com/apache/www-site/
>>>
>>> The following will occur.
>>> - A new git repository is created. river-site is preferred.
>>> - CMS mdtext files are converted to md and stored in the content tree.
>>> - Permalinks are created in the same manner.
>>> - Page templates will be converted essentially as is with some minor
>>> improvements.
>>> - Site data feeds are analyzed. If required a data model will be created.
>>> - HTML files (apidocs) built separately are copied into the content tree.
>>> I’ll make a judgement call on
>>> if these can be wrapped into the template.
>>>
>>> The Apache CMS had a cumbersome process of individual checkouts -> staging
>>> -> publishing.
>>> The new branching strategy is as follows:
>>> - main will have the site content sources and any additional docs (like
>>> api docs).
>>> - asf-site will have the production website which is automatically
>>> deployed to river.apache.org.
>>> During the migration we will deploy to river.staged.apache.org
>>> - preview/release will have the website prepared for the next release. You
>>> will add release specific docs to this branch
>>> - preview/release-staging will have the built preview website which is
>>> automatically deployed to river-release.staged.apache.org
>>>
>>> This new plan allows for a redesign of your site without danger of
>>> premature deployment.
>>> If you decide that GFM is not for river then you can switch to a different
>>> process within a preview branch.
>>>
>>> Release steps for the website could be:
>>> - Branch main as preview/release
>>> - Make your updates to preview/release
>>> - Confirm your changes on river-release.staged.apache.org
>>> - Pull your changes from preview/release to main. river.apache.org is
>>> automatically updated.
>>>
>>> All The Best,
>>> Dave Fisher
>>
>>
>>
>> --
>> Jeremy R. Easton-Marks
>>
>> "être fort pour être utile"
>
Re: CMS Migration for River
Posted by Dave Fisher <wa...@apache.org>.
The Migration from CMS to ASF-Pelican is completed!
https://river.apache.org/ is ready.
https://github.com/apache/river-site/
For information about ASF-Pelican: https://infra.apache.org/asf-pelican.html
Enjoy!
Dave
> On Jun 14, 2021, at 6:17 AM, Jeremy R. Easton-Marks <J....@gmail.com> wrote:
>
> +1 Thanks for the work in converting this.
>
> On Sun, Jun 13, 2021 at 5:56 PM Roy T. Fielding <fi...@gbiv.com> wrote:
>
>>> On Jun 13, 2021, at 3:28 PM, Dave Fisher <wa...@apache.org> wrote:
>>>
>>> Hi,
>>>
>>> The site is ready to go. https://river.staged.apache.org
>>>
>>> The README on https://github.com/apache/river-site has a pointer to the
>> Infra documentation and to migration notes which includes a diff on the
>> markdown including the PR.
>>>
>>> I would like to make this migration live in 72 hours.
>>>
>>> All The Best,
>>> Dave
>>
>> +1. I will update the people page after the switch.
>>
>> ....Roy
>>
>>
>
> --
> Jeremy R. Easton-Marks
>
> "être fort pour être utile"
Re: CMS Migration for River
Posted by "Jeremy R. Easton-Marks" <J....@gmail.com>.
+1 Thanks for the work in converting this.
On Sun, Jun 13, 2021 at 5:56 PM Roy T. Fielding <fi...@gbiv.com> wrote:
> > On Jun 13, 2021, at 3:28 PM, Dave Fisher <wa...@apache.org> wrote:
> >
> > Hi,
> >
> > The site is ready to go. https://river.staged.apache.org
> >
> > The README on https://github.com/apache/river-site has a pointer to the
> Infra documentation and to migration notes which includes a diff on the
> markdown including the PR.
> >
> > I would like to make this migration live in 72 hours.
> >
> > All The Best,
> > Dave
>
> +1. I will update the people page after the switch.
>
> ....Roy
>
>
--
Jeremy R. Easton-Marks
"être fort pour être utile"
Re: CMS Migration for River
Posted by "Roy T. Fielding" <fi...@gbiv.com>.
> On Jun 13, 2021, at 3:28 PM, Dave Fisher <wa...@apache.org> wrote:
>
> Hi,
>
> The site is ready to go. https://river.staged.apache.org
>
> The README on https://github.com/apache/river-site has a pointer to the Infra documentation and to migration notes which includes a diff on the markdown including the PR.
>
> I would like to make this migration live in 72 hours.
>
> All The Best,
> Dave
+1. I will update the people page after the switch.
....Roy
Re: CMS Migration for River
Posted by Dave Fisher <wa...@apache.org>.
Hi,
The site is ready to go. https://river.staged.apache.org
The README on https://github.com/apache/river-site has a pointer to the Infra documentation and to migration notes which includes a diff on the markdown including the PR.
I would like to make this migration live in 72 hours.
All The Best,
Dave
> On Jun 2, 2021, at 7:54 AM, Dave Fisher <wa...@apache.org> wrote:
>
> For your Apache River permissions to synchronize with your GitHub access to this repository you need to link accounts.
>
> Follow the instructions here: https://gitbox.apache.org/setup/
>
> I’ve merged your PR.
>
> Regards,
> Dave
>
>> On Jun 1, 2021, at 7:08 PM, Jeremy R. Easton-Marks <J....@gmail.com> wrote:
>>
>> I created a PR <https://github.com/apache/river-site/pull/1> to fix some of
>> the dead links and spelling mistakes. I don't have write access yet for
>> this repo so please merge it when you can.
>>
>> On Tue, Jun 1, 2021 at 8:52 PM Jeremy R. Easton-Marks <
>> J.R.EastonMarks@gmail.com> wrote:
>>
>>> Hi Dave,
>>> This looks good. Every link looks like it worked and the site material
>>> looks like it moved over correctly. I found some stuff that we need to
>>> update on our end that I am going to take a look at.
>>>
>>> ~Jeremy
>>>
>>> On Tue, Jun 1, 2021 at 6:35 PM Dave Fisher <wa...@apache.org> wrote:
>>>
>>>> Hi -
>>>>
>>>> Please find your staged migrated site at https://river.staged.apache.org
>>>> <https://river.staged.apache.org/>
>>>>
>>>> The repository is at https://github.com/apache/river-site <
>>>> https://github.com/apache/river-site>
>>>>
>>>> I’ll be updating the README.md files in the next day or two including
>>>> notes on the migration.
>>>>
>>>> All The Best,
>>>> Dave
>>>>
>>>>> On May 29, 2021, at 12:45 PM, Dave Fisher <wa...@apache.org> wrote:
>>>>>
>>>>> I may have questions once the migration is started.
>>>>>
>>>>> I’ll definitely need review once the new repository with the migrated
>>>> content is ready.
>>>>>
>>>>>> On May 29, 2021, at 11:28 AM, Jeremy R. Easton-Marks <
>>>> J.R.EastonMarks@gmail.com> wrote:
>>>>>>
>>>>>> Thanks Dave. Do you need anything from the River team for this process?
>>>>>>
>>>>>> On Sat, May 29, 2021 at 11:43 AM Dave Fisher <wa...@apache.org> wrote:
>>>>>>
>>>>>>> As you may recall the Apache CMS has been deprecated for over five
>>>> years
>>>>>>> now and will be decommissioned
>>>>>>> by July 31, 2021.
>>>>>>>
>>>>>>> I’ve been tasked with moving River's website away from the Apache CMS.
>>>>>>> I will migrate your website to a Pelican build with GitHub Flavored
>>>>>>> Markdown (GFM).
>>>>>>> For your reference the already migrated www-site is here
>>>>>>> https://github.com/apache/www-site/
>>>>>>>
>>>>>>> The following will occur.
>>>>>>> - A new git repository is created. river-site is preferred.
>>>>>>> - CMS mdtext files are converted to md and stored in the content tree.
>>>>>>> - Permalinks are created in the same manner.
>>>>>>> - Page templates will be converted essentially as is with some minor
>>>>>>> improvements.
>>>>>>> - Site data feeds are analyzed. If required a data model will be
>>>> created.
>>>>>>> - HTML files (apidocs) built separately are copied into the content
>>>> tree.
>>>>>>> I’ll make a judgement call on
>>>>>>> if these can be wrapped into the template.
>>>>>>>
>>>>>>> The Apache CMS had a cumbersome process of individual checkouts ->
>>>> staging
>>>>>>> -> publishing.
>>>>>>> The new branching strategy is as follows:
>>>>>>> - main will have the site content sources and any additional docs
>>>> (like
>>>>>>> api docs).
>>>>>>> - asf-site will have the production website which is automatically
>>>>>>> deployed to river.apache.org.
>>>>>>> During the migration we will deploy to river.staged.apache.org
>>>>>>> - preview/release will have the website prepared for the next
>>>> release. You
>>>>>>> will add release specific docs to this branch
>>>>>>> - preview/release-staging will have the built preview website which is
>>>>>>> automatically deployed to river-release.staged.apache.org
>>>>>>>
>>>>>>> This new plan allows for a redesign of your site without danger of
>>>>>>> premature deployment.
>>>>>>> If you decide that GFM is not for river then you can switch to a
>>>> different
>>>>>>> process within a preview branch.
>>>>>>>
>>>>>>> Release steps for the website could be:
>>>>>>> - Branch main as preview/release
>>>>>>> - Make your updates to preview/release
>>>>>>> - Confirm your changes on river-release.staged.apache.org
>>>>>>> - Pull your changes from preview/release to main. river.apache.org is
>>>>>>> automatically updated.
>>>>>>>
>>>>>>> All The Best,
>>>>>>> Dave Fisher
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Jeremy R. Easton-Marks
>>>>>>
>>>>>> "être fort pour être utile"
>>>>>
>>>>
>>>>
>>>
>>> --
>>> Jeremy R. Easton-Marks
>>>
>>> "être fort pour être utile"
>>>
>>
>>
>> --
>> Jeremy R. Easton-Marks
>>
>> "être fort pour être utile"
>
Re: CMS Migration for River
Posted by Dave Fisher <wa...@apache.org>.
For your Apache River permissions to synchronize with your GitHub access to this repository you need to link accounts.
Follow the instructions here: https://gitbox.apache.org/setup/
I’ve merged your PR.
Regards,
Dave
> On Jun 1, 2021, at 7:08 PM, Jeremy R. Easton-Marks <J....@gmail.com> wrote:
>
> I created a PR <https://github.com/apache/river-site/pull/1> to fix some of
> the dead links and spelling mistakes. I don't have write access yet for
> this repo so please merge it when you can.
>
> On Tue, Jun 1, 2021 at 8:52 PM Jeremy R. Easton-Marks <
> J.R.EastonMarks@gmail.com> wrote:
>
>> Hi Dave,
>> This looks good. Every link looks like it worked and the site material
>> looks like it moved over correctly. I found some stuff that we need to
>> update on our end that I am going to take a look at.
>>
>> ~Jeremy
>>
>> On Tue, Jun 1, 2021 at 6:35 PM Dave Fisher <wa...@apache.org> wrote:
>>
>>> Hi -
>>>
>>> Please find your staged migrated site at https://river.staged.apache.org
>>> <https://river.staged.apache.org/>
>>>
>>> The repository is at https://github.com/apache/river-site <
>>> https://github.com/apache/river-site>
>>>
>>> I’ll be updating the README.md files in the next day or two including
>>> notes on the migration.
>>>
>>> All The Best,
>>> Dave
>>>
>>>> On May 29, 2021, at 12:45 PM, Dave Fisher <wa...@apache.org> wrote:
>>>>
>>>> I may have questions once the migration is started.
>>>>
>>>> I’ll definitely need review once the new repository with the migrated
>>> content is ready.
>>>>
>>>>> On May 29, 2021, at 11:28 AM, Jeremy R. Easton-Marks <
>>> J.R.EastonMarks@gmail.com> wrote:
>>>>>
>>>>> Thanks Dave. Do you need anything from the River team for this process?
>>>>>
>>>>> On Sat, May 29, 2021 at 11:43 AM Dave Fisher <wa...@apache.org> wrote:
>>>>>
>>>>>> As you may recall the Apache CMS has been deprecated for over five
>>> years
>>>>>> now and will be decommissioned
>>>>>> by July 31, 2021.
>>>>>>
>>>>>> I’ve been tasked with moving River's website away from the Apache CMS.
>>>>>> I will migrate your website to a Pelican build with GitHub Flavored
>>>>>> Markdown (GFM).
>>>>>> For your reference the already migrated www-site is here
>>>>>> https://github.com/apache/www-site/
>>>>>>
>>>>>> The following will occur.
>>>>>> - A new git repository is created. river-site is preferred.
>>>>>> - CMS mdtext files are converted to md and stored in the content tree.
>>>>>> - Permalinks are created in the same manner.
>>>>>> - Page templates will be converted essentially as is with some minor
>>>>>> improvements.
>>>>>> - Site data feeds are analyzed. If required a data model will be
>>> created.
>>>>>> - HTML files (apidocs) built separately are copied into the content
>>> tree.
>>>>>> I’ll make a judgement call on
>>>>>> if these can be wrapped into the template.
>>>>>>
>>>>>> The Apache CMS had a cumbersome process of individual checkouts ->
>>> staging
>>>>>> -> publishing.
>>>>>> The new branching strategy is as follows:
>>>>>> - main will have the site content sources and any additional docs
>>> (like
>>>>>> api docs).
>>>>>> - asf-site will have the production website which is automatically
>>>>>> deployed to river.apache.org.
>>>>>> During the migration we will deploy to river.staged.apache.org
>>>>>> - preview/release will have the website prepared for the next
>>> release. You
>>>>>> will add release specific docs to this branch
>>>>>> - preview/release-staging will have the built preview website which is
>>>>>> automatically deployed to river-release.staged.apache.org
>>>>>>
>>>>>> This new plan allows for a redesign of your site without danger of
>>>>>> premature deployment.
>>>>>> If you decide that GFM is not for river then you can switch to a
>>> different
>>>>>> process within a preview branch.
>>>>>>
>>>>>> Release steps for the website could be:
>>>>>> - Branch main as preview/release
>>>>>> - Make your updates to preview/release
>>>>>> - Confirm your changes on river-release.staged.apache.org
>>>>>> - Pull your changes from preview/release to main. river.apache.org is
>>>>>> automatically updated.
>>>>>>
>>>>>> All The Best,
>>>>>> Dave Fisher
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Jeremy R. Easton-Marks
>>>>>
>>>>> "être fort pour être utile"
>>>>
>>>
>>>
>>
>> --
>> Jeremy R. Easton-Marks
>>
>> "être fort pour être utile"
>>
>
>
> --
> Jeremy R. Easton-Marks
>
> "être fort pour être utile"
Re: CMS Migration for River
Posted by "Jeremy R. Easton-Marks" <J....@gmail.com>.
I created a PR <https://github.com/apache/river-site/pull/1> to fix some of
the dead links and spelling mistakes. I don't have write access yet for
this repo so please merge it when you can.
On Tue, Jun 1, 2021 at 8:52 PM Jeremy R. Easton-Marks <
J.R.EastonMarks@gmail.com> wrote:
> Hi Dave,
> This looks good. Every link looks like it worked and the site material
> looks like it moved over correctly. I found some stuff that we need to
> update on our end that I am going to take a look at.
>
> ~Jeremy
>
> On Tue, Jun 1, 2021 at 6:35 PM Dave Fisher <wa...@apache.org> wrote:
>
>> Hi -
>>
>> Please find your staged migrated site at https://river.staged.apache.org
>> <https://river.staged.apache.org/>
>>
>> The repository is at https://github.com/apache/river-site <
>> https://github.com/apache/river-site>
>>
>> I’ll be updating the README.md files in the next day or two including
>> notes on the migration.
>>
>> All The Best,
>> Dave
>>
>> > On May 29, 2021, at 12:45 PM, Dave Fisher <wa...@apache.org> wrote:
>> >
>> > I may have questions once the migration is started.
>> >
>> > I’ll definitely need review once the new repository with the migrated
>> content is ready.
>> >
>> >> On May 29, 2021, at 11:28 AM, Jeremy R. Easton-Marks <
>> J.R.EastonMarks@gmail.com> wrote:
>> >>
>> >> Thanks Dave. Do you need anything from the River team for this process?
>> >>
>> >> On Sat, May 29, 2021 at 11:43 AM Dave Fisher <wa...@apache.org> wrote:
>> >>
>> >>> As you may recall the Apache CMS has been deprecated for over five
>> years
>> >>> now and will be decommissioned
>> >>> by July 31, 2021.
>> >>>
>> >>> I’ve been tasked with moving River's website away from the Apache CMS.
>> >>> I will migrate your website to a Pelican build with GitHub Flavored
>> >>> Markdown (GFM).
>> >>> For your reference the already migrated www-site is here
>> >>> https://github.com/apache/www-site/
>> >>>
>> >>> The following will occur.
>> >>> - A new git repository is created. river-site is preferred.
>> >>> - CMS mdtext files are converted to md and stored in the content tree.
>> >>> - Permalinks are created in the same manner.
>> >>> - Page templates will be converted essentially as is with some minor
>> >>> improvements.
>> >>> - Site data feeds are analyzed. If required a data model will be
>> created.
>> >>> - HTML files (apidocs) built separately are copied into the content
>> tree.
>> >>> I’ll make a judgement call on
>> >>> if these can be wrapped into the template.
>> >>>
>> >>> The Apache CMS had a cumbersome process of individual checkouts ->
>> staging
>> >>> -> publishing.
>> >>> The new branching strategy is as follows:
>> >>> - main will have the site content sources and any additional docs
>> (like
>> >>> api docs).
>> >>> - asf-site will have the production website which is automatically
>> >>> deployed to river.apache.org.
>> >>> During the migration we will deploy to river.staged.apache.org
>> >>> - preview/release will have the website prepared for the next
>> release. You
>> >>> will add release specific docs to this branch
>> >>> - preview/release-staging will have the built preview website which is
>> >>> automatically deployed to river-release.staged.apache.org
>> >>>
>> >>> This new plan allows for a redesign of your site without danger of
>> >>> premature deployment.
>> >>> If you decide that GFM is not for river then you can switch to a
>> different
>> >>> process within a preview branch.
>> >>>
>> >>> Release steps for the website could be:
>> >>> - Branch main as preview/release
>> >>> - Make your updates to preview/release
>> >>> - Confirm your changes on river-release.staged.apache.org
>> >>> - Pull your changes from preview/release to main. river.apache.org is
>> >>> automatically updated.
>> >>>
>> >>> All The Best,
>> >>> Dave Fisher
>> >>
>> >>
>> >>
>> >> --
>> >> Jeremy R. Easton-Marks
>> >>
>> >> "être fort pour être utile"
>> >
>>
>>
>
> --
> Jeremy R. Easton-Marks
>
> "être fort pour être utile"
>
--
Jeremy R. Easton-Marks
"être fort pour être utile"
Re: CMS Migration for River
Posted by "Jeremy R. Easton-Marks" <J....@gmail.com>.
Hi Dave,
This looks good. Every link looks like it worked and the site material
looks like it moved over correctly. I found some stuff that we need to
update on our end that I am going to take a look at.
~Jeremy
On Tue, Jun 1, 2021 at 6:35 PM Dave Fisher <wa...@apache.org> wrote:
> Hi -
>
> Please find your staged migrated site at https://river.staged.apache.org <
> https://river.staged.apache.org/>
>
> The repository is at https://github.com/apache/river-site <
> https://github.com/apache/river-site>
>
> I’ll be updating the README.md files in the next day or two including
> notes on the migration.
>
> All The Best,
> Dave
>
> > On May 29, 2021, at 12:45 PM, Dave Fisher <wa...@apache.org> wrote:
> >
> > I may have questions once the migration is started.
> >
> > I’ll definitely need review once the new repository with the migrated
> content is ready.
> >
> >> On May 29, 2021, at 11:28 AM, Jeremy R. Easton-Marks <
> J.R.EastonMarks@gmail.com> wrote:
> >>
> >> Thanks Dave. Do you need anything from the River team for this process?
> >>
> >> On Sat, May 29, 2021 at 11:43 AM Dave Fisher <wa...@apache.org> wrote:
> >>
> >>> As you may recall the Apache CMS has been deprecated for over five
> years
> >>> now and will be decommissioned
> >>> by July 31, 2021.
> >>>
> >>> I’ve been tasked with moving River's website away from the Apache CMS.
> >>> I will migrate your website to a Pelican build with GitHub Flavored
> >>> Markdown (GFM).
> >>> For your reference the already migrated www-site is here
> >>> https://github.com/apache/www-site/
> >>>
> >>> The following will occur.
> >>> - A new git repository is created. river-site is preferred.
> >>> - CMS mdtext files are converted to md and stored in the content tree.
> >>> - Permalinks are created in the same manner.
> >>> - Page templates will be converted essentially as is with some minor
> >>> improvements.
> >>> - Site data feeds are analyzed. If required a data model will be
> created.
> >>> - HTML files (apidocs) built separately are copied into the content
> tree.
> >>> I’ll make a judgement call on
> >>> if these can be wrapped into the template.
> >>>
> >>> The Apache CMS had a cumbersome process of individual checkouts ->
> staging
> >>> -> publishing.
> >>> The new branching strategy is as follows:
> >>> - main will have the site content sources and any additional docs (like
> >>> api docs).
> >>> - asf-site will have the production website which is automatically
> >>> deployed to river.apache.org.
> >>> During the migration we will deploy to river.staged.apache.org
> >>> - preview/release will have the website prepared for the next release.
> You
> >>> will add release specific docs to this branch
> >>> - preview/release-staging will have the built preview website which is
> >>> automatically deployed to river-release.staged.apache.org
> >>>
> >>> This new plan allows for a redesign of your site without danger of
> >>> premature deployment.
> >>> If you decide that GFM is not for river then you can switch to a
> different
> >>> process within a preview branch.
> >>>
> >>> Release steps for the website could be:
> >>> - Branch main as preview/release
> >>> - Make your updates to preview/release
> >>> - Confirm your changes on river-release.staged.apache.org
> >>> - Pull your changes from preview/release to main. river.apache.org is
> >>> automatically updated.
> >>>
> >>> All The Best,
> >>> Dave Fisher
> >>
> >>
> >>
> >> --
> >> Jeremy R. Easton-Marks
> >>
> >> "être fort pour être utile"
> >
>
>
--
Jeremy R. Easton-Marks
"être fort pour être utile"