You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@metamodel.apache.org by Andrew Wetmore <an...@apache.org> on 2021/01/16 14:11:01 UTC
Re: Migration of project website from Apache CMS
Hi, and happy New Year!
Has there been a vote on migrating the project's website, or other progress on the migration?
Thanks!
Andrew
On 2020/08/28 15:07:22, Kasper Sørensen <i....@gmail.com> wrote:
> I think you should probably call for a vote yes. Let's use this thread for
> any discussion on it.
>
> I am fine with more or less either of the options. But I have a bit of
> experience using Jekyll since that's what you use to build sites on github
> pages, too. So my preference is slightly towards Jekyll.
>
> Den tir. 25. aug. 2020 kl. 15.54 skrev Arjan Seijkens Hagemans <
> arjansh@gmail.com>:
>
> > Hi,
> >
> > Since our project website is still running on Apache CMS and that has
> > reached end-of-life, we need to migrate.
> >
> > These pages describe some options for the migration:
> > https://infra.apache.org/project-site.html
> >
> > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> >
> > To summarize, Apache offers these options:
> >
> > 1. Pelican
> > 2. Github Pages
> > 3. Jekyll
> > 4. Hugo
> > 5. JBake
> >
> > The first thing that is expected from us is to decide on one of these
> > options and to record a PMC decision to make the move and to authorize
> > Infra to remove metamodel artifacts from the CMS once the move is
> > done.
> >
> > Should I call for a vote on this?
> >
> > Kind regards,
> > Arjan Seijkens
> >
>
Re: Migration of project website from Apache CMS
Posted by Andrew Wetmore <an...@apache.org>.
Thank you for letting me know.
Andrew
On Mon, Jan 18, 2021 at 3:25 AM Arjan Seijkens Hagemans <ar...@gmail.com>
wrote:
> Hi Andrew,
>
> Happy New Year to you too!
>
> The vote was resolved on September 7 last year, see
> http://mail-archives.apache.org/mod_mbox/metamodel-dev/202009.mbox/browser
> .
>
> I subsequently created a JIRA issue as requested, see
> https://issues.apache.org/jira/browse/INFRA-20844.
>
> I hope this answers your question.
>
> Kind regards,
> Arjan Seijkens
>
> Op za 16 jan. 2021 om 15:11 schreef Andrew Wetmore <an...@apache.org>:
> >
> > Hi, and happy New Year!
> >
> > Has there been a vote on migrating the project's website, or other
> progress on the migration?
> >
> > Thanks!
> >
> > Andrew
> >
> > On 2020/08/28 15:07:22, Kasper Sørensen <i....@gmail.com>
> wrote:
> > > I think you should probably call for a vote yes. Let's use this thread
> for
> > > any discussion on it.
> > >
> > > I am fine with more or less either of the options. But I have a bit of
> > > experience using Jekyll since that's what you use to build sites on
> github
> > > pages, too. So my preference is slightly towards Jekyll.
> > >
> > > Den tir. 25. aug. 2020 kl. 15.54 skrev Arjan Seijkens Hagemans <
> > > arjansh@gmail.com>:
> > >
> > > > Hi,
> > > >
> > > > Since our project website is still running on Apache CMS and that has
> > > > reached end-of-life, we need to migrate.
> > > >
> > > > These pages describe some options for the migration:
> > > > https://infra.apache.org/project-site.html
> > > >
> > > >
> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> > > >
> > > > To summarize, Apache offers these options:
> > > >
> > > > 1. Pelican
> > > > 2. Github Pages
> > > > 3. Jekyll
> > > > 4. Hugo
> > > > 5. JBake
> > > >
> > > > The first thing that is expected from us is to decide on one of these
> > > > options and to record a PMC decision to make the move and to
> authorize
> > > > Infra to remove metamodel artifacts from the CMS once the move is
> > > > done.
> > > >
> > > > Should I call for a vote on this?
> > > >
> > > > Kind regards,
> > > > Arjan Seijkens
> > > >
> > >
>
--
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Foundation*
andreww@apache.org
Re: Migration of project website from Apache CMS
Posted by Arjan Seijkens Hagemans <ar...@gmail.com>.
Hi Andrew,
Happy New Year to you too!
The vote was resolved on September 7 last year, see
http://mail-archives.apache.org/mod_mbox/metamodel-dev/202009.mbox/browser.
I subsequently created a JIRA issue as requested, see
https://issues.apache.org/jira/browse/INFRA-20844.
I hope this answers your question.
Kind regards,
Arjan Seijkens
Op za 16 jan. 2021 om 15:11 schreef Andrew Wetmore <an...@apache.org>:
>
> Hi, and happy New Year!
>
> Has there been a vote on migrating the project's website, or other progress on the migration?
>
> Thanks!
>
> Andrew
>
> On 2020/08/28 15:07:22, Kasper Sørensen <i....@gmail.com> wrote:
> > I think you should probably call for a vote yes. Let's use this thread for
> > any discussion on it.
> >
> > I am fine with more or less either of the options. But I have a bit of
> > experience using Jekyll since that's what you use to build sites on github
> > pages, too. So my preference is slightly towards Jekyll.
> >
> > Den tir. 25. aug. 2020 kl. 15.54 skrev Arjan Seijkens Hagemans <
> > arjansh@gmail.com>:
> >
> > > Hi,
> > >
> > > Since our project website is still running on Apache CMS and that has
> > > reached end-of-life, we need to migrate.
> > >
> > > These pages describe some options for the migration:
> > > https://infra.apache.org/project-site.html
> > >
> > > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
> > >
> > > To summarize, Apache offers these options:
> > >
> > > 1. Pelican
> > > 2. Github Pages
> > > 3. Jekyll
> > > 4. Hugo
> > > 5. JBake
> > >
> > > The first thing that is expected from us is to decide on one of these
> > > options and to record a PMC decision to make the move and to authorize
> > > Infra to remove metamodel artifacts from the CMS once the move is
> > > done.
> > >
> > > Should I call for a vote on this?
> > >
> > > Kind regards,
> > > Arjan Seijkens
> > >
> >