<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Ben,<span class="HwtZe" lang="en"><span class="jCAhz ChMk0b"><span
class="ryNqvb"><br>
</span></span></span></p>
<p><span class="HwtZe" lang="en"><span class="jCAhz ChMk0b"><span
class="ryNqvb">As the main developer of Skrooge and
administrator and developer of skrooge.org (currently on
Drupal), <u>it is normal that I am in charge of the
migration</u>.</span></span> <span class="jCAhz ChMk0b"><span
class="ryNqvb"><br>
But, I don't know Hugo and I already have other websites on
wordpress, <br>
so I would appreciate if I could make skrooge.org on
wordpress.</span></span><span class="jCAhz"><span
class="ryNqvb">
</span></span><span class="jCAhz ChMk0b"><span class="ryNqvb"><br>
<b>Is it possible ?</b></span></span></span></p>
<p><span class="HwtZe" lang="en"><span class="jCAhz ChMk0b"><span
class="ryNqvb">Regards,<br>
Stéphane<br>
</span></span></span></p>
<div class="moz-cite-prefix">Le 15/01/2023 à 10:21, Paul Brown a
écrit :<br>
</div>
<blockquote type="cite" cite="mid:13180915.dW097sEU6C@tyrell">
<pre class="moz-quote-pre" wrap="">On Sunday, 15 January 2023 08:04:18 CET Ben Cooksley wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">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.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Hi Ben,
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 <a class="moz-txt-link-freetext" href="https://kdenlive.org">https://kdenlive.org</a>, we
think that having this is not too much to ask.
Cheers
Paul
</pre>
</blockquote>
<div id="grammalecte_menu_main_button_shadow_host" style="width:
0px; height: 0px;"></div>
</body>
</html>