[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-promo
Subject: Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)
From: Ben Cooksley <bcooksley () kde ! org>
Date: 2023-01-15 9:33:06
Message-ID: CA+XidOGBVeuig_vT7DQh=v52fKqgy6ZxzwOsik4fPD8BWD7mog () mail ! gmail ! com
[Download RAW message or body]
On Sun, Jan 15, 2023 at 10:21 PM Paul Brown <paul.brown@kde.org> wrote:
> On Sunday, 15 January 2023 08:04:18 CET Ben Cooksley wrote:
> > Hi all,
> >
> > For some time now it has been known to us that the upgrade path from one
> > given Drupal major version to the next is usually a very difficult road
> > with lots of breakage involved.
> > The conversion from Drupal 7 or 8 to Drupal 9 is no different in this
> > regard - basically being a content export and then reimport.
> >
> > Due to the level of disruption and risk of breakage involved this isn't
> > something done lightly but with the end of support for Drupal 8 and the
> > incoming end of support for Drupal 7 we need to take action on this
> sooner
> > rather later.
> >
> > At this time I'm only focusing on the smaller sites, so akademy.kde.org
> (in
> > the process of moving to Hugo) and dot.kde.org (to be figured out) are
> out
> > of scope for this email.
> >
> > We currently have the following sites running on Drupal 7/8:
> > - dot.kde.org
> > - akademy.kde.org
> > - kdevelop.org
> > - skrooge.org
> > - behindkde.org
> > - blogs.kde.org
> >
> > Given that promo is currently not making active use of the site, at this
> > time my intention is to create a static archive of behindkde.org.
> >
> > In the case of KDevelop and Skrooge, it would make the most sense to
> > convert them both into Hugo websites to minimise the long term
> maintenance
> > cost and to make them part of the KDE family of sites.
> > If anyone would like to work on this please contact me and I will arrange
> > for a sanitized database copy to be made available to you.
> >
> > In the event that doesn't happen, converting them into static sites seems
> > like the best path forward.
>
> Hi Ben,
>
Hi Paul,
>
> Drupal is, not to put too fine a point on it, terrible in every
> conceivable way
> and we dread having to post to the dot. We welcome the transition away
> from
> it.
>
> Promo has repeatedly asked for WordPress to supersede Drupal for the Dot,
> as
> we have found creating content for a Hugo site (something we do at least
> every
> 2 months for KDE Gear and Plasma announcements) difficult, inflexible,
> slow,
> convoluted, and error-prone. So not much better than Drupal.
>
> As there are already several WordPress-based websites on the KDE
> infrastructure, such as hattps://labplot.kde.org and https://kdenlive.org,
> we
> think that having this is not too much to ask.
>
As noted in my email we'll be tackling the Dot in a separate thread, this
is about the smaller sites for now.
Points duly noted though.
>
> Cheers
>
> Paul
>
Regards.
Ben
> --
> Promotion & Communication
>
> www: http://kde.org
> Mastodon: https://floss.social/@kde
> Facebook: https://www.facebook.com/kde/
> Twitter: https://twitter.com/kdecommunity
> LinkedIn: https://www.linkedin.com/company/kde
>
>
>
[Attachment #3 (text/html)]
<div dir="ltr"><div dir="ltr">On Sun, Jan 15, 2023 at 10:21 PM Paul Brown <<a \
href="mailto:paul.brown@kde.org">paul.brown@kde.org</a>> wrote:<br></div><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Sunday, 15 January \
2023 08:04:18 CET Ben Cooksley wrote:<br> > Hi all,<br>
> <br>
> For some time now it has been known to us that the upgrade path from one<br>
> given Drupal major version to the next is usually a very difficult road<br>
> with lots of breakage involved.<br>
> The conversion from Drupal 7 or 8 to Drupal 9 is no different in this<br>
> regard - basically being a content export and then reimport.<br>
> <br>
> Due to the level of disruption and risk of breakage involved this isn't<br>
> something done lightly but with the end of support for Drupal 8 and the<br>
> incoming end of support for Drupal 7 we need to take action on this sooner<br>
> rather later.<br>
> <br>
> At this time I'm only focusing on the smaller sites, so <a \
href="http://akademy.kde.org" rel="noreferrer" target="_blank">akademy.kde.org</a> \
(in<br> > the process of moving to Hugo) and <a href="http://dot.kde.org" \
rel="noreferrer" target="_blank">dot.kde.org</a> (to be figured out) are out<br> > \
of scope for this email.<br> > <br>
> We currently have the following sites running on Drupal 7/8:<br>
> - <a href="http://dot.kde.org" rel="noreferrer" \
target="_blank">dot.kde.org</a><br> > - <a href="http://akademy.kde.org" \
rel="noreferrer" target="_blank">akademy.kde.org</a><br> > - <a \
href="http://kdevelop.org" rel="noreferrer" target="_blank">kdevelop.org</a><br> > \
- <a href="http://skrooge.org" rel="noreferrer" target="_blank">skrooge.org</a><br> \
> - <a href="http://behindkde.org" rel="noreferrer" \
target="_blank">behindkde.org</a><br> > - <a href="http://blogs.kde.org" \
rel="noreferrer" target="_blank">blogs.kde.org</a><br> > <br>
> Given that promo is currently not making active use of the site, at this<br>
> time my intention is to create a static archive of <a \
href="http://behindkde.org" rel="noreferrer" target="_blank">behindkde.org</a>.<br> \
> <br> > In the case of KDevelop and Skrooge, it would make the most sense \
to<br> > convert them both into Hugo websites to minimise the long term \
maintenance<br> > cost and to make them part of the KDE family of sites.<br>
> If anyone would like to work on this please contact me and I will arrange<br>
> for a sanitized database copy to be made available to you.<br>
> <br>
> In the event that doesn't happen, converting them into static sites \
seems<br> > like the best path forward.<br>
<br>
Hi Ben,<br></blockquote><div><br></div><div>Hi Paul,</div><div> </div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> <br>
Drupal is, not to put too fine a point on it, terrible in every conceivable way <br>
and we dread having to post to the dot. We welcome the transition away from <br>
it.<br>
<br>
Promo has repeatedly asked for WordPress to supersede Drupal for the Dot, as <br>
we have found creating content for a Hugo site (something we do at least every <br>
2 months for KDE Gear and Plasma announcements) difficult, inflexible, slow, <br>
convoluted, and error-prone. So not much better than Drupal.<br>
<br>
As there are already several WordPress-based websites on the KDE <br>
infrastructure, such as hattps://<a href="http://labplot.kde.org" rel="noreferrer" \
target="_blank">labplot.kde.org</a> and <a href="https://kdenlive.org" \
rel="noreferrer" target="_blank">https://kdenlive.org</a>, we <br> think that having \
this is not too much to ask.<br></blockquote><div><br></div><div>As noted in my email \
we'll be tackling the Dot in a separate thread, this is about the smaller sites \
for now.</div><div>Points duly noted though.</div><div> </div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> <br>
Cheers<br>
<br>
Paul<br></blockquote><div><br></div><div>Regards.</div><div>Ben</div><div> \
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px \
solid rgb(204,204,204);padding-left:1ex">
-- <br>
Promotion & Communication<br>
<br>
www: <a href="http://kde.org" rel="noreferrer" target="_blank">http://kde.org</a><br>
Mastodon: <a href="https://floss.social/@kde" rel="noreferrer" \
target="_blank">https://floss.social/@kde</a><br>
Facebook: <a href="https://www.facebook.com/kde/" rel="noreferrer" \
target="_blank">https://www.facebook.com/kde/</a><br>
Twitter: <a href="https://twitter.com/kdecommunity" rel="noreferrer" \
target="_blank">https://twitter.com/kdecommunity</a><br>
LinkedIn: <a href="https://www.linkedin.com/company/kde" rel="noreferrer" \
target="_blank">https://www.linkedin.com/company/kde</a><br> <br>
<br>
</blockquote></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic