Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On 1/16/23 02:33, Ben Cooksley wrote: On Mon, Jan 16, 2023 at 12:08 PM Phu Hung Nguyen > wrote: On 15/01/2023 08:04, bcooks...@kde.org wrote: > For blogs.kde.org , I am in two minds as to the best approa

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

Hey, yes, I did start working on an update for the website, but got myself busy with other things and never finished it (sorry about that). AFAIR, it was in early stages, since I got trouble making it work with Hugo. It was not usable since most information was outdated, but the Hugo part (AFAIR) w

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

In data 16/01/2023 09:27:59 CET, Milian Wolff ha scritto: > On Sonntag, 15. Januar 2023 08:04:18 CET Ben Cooksley wrote: > > Hi all, Hello > > > > > 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 maintenan

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On Montag, 16. Januar 2023 11:12:58 CET Tarcísio Fischer wrote: > Hey, yes, I did start working on an update for the website, but got myself > busy with other things and never finished it (sorry about that). No worries, thanks for your work already! > AFAIR, it was in early stages, since I got tr

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

At this point it is looking like Hugo may be the preferred candidate for blogs.kde.org, but we'll see if anyone else has a view first. Ingo Klöcker expressed preference for Hugo (for blogs-k-o), but he wrote only to kde-community ML. Just want to make things clear, just in case you missed his

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On Mon, Jan 16, 2023 at 12:08 PM Phu Hung Nguyen wrote: > On 15/01/2023 08:04, bcooks...@kde.org wrote: > > For blogs.kde.org, I am in two minds as to the best approach here, with > > Wordpress and Hugo both appearing as candidates for this site. > > Opinions welcome, especially if you are someon

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On Mon, Jan 16, 2023 at 9:28 PM Milian Wolff wrote: > On Sonntag, 15. Januar 2023 08:04:18 CET Ben Cooksley wrote: > > Hi all, > > > > > 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

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On Montag, 16. Januar 2023 09:59:51 CET Alexander Zhigalin wrote: > In data 16/01/2023 09:27:59 CET, Milian Wolff ha scritto: > > On Sonntag, 15. Januar 2023 08:04:18 CET Ben Cooksley wrote: > > > Hi all, > > Hello > > > > > > > > In the case of KDevelop and Skrooge, it would make the most sens

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On Sonntag, 15. Januar 2023 08:04:18 CET Ben Cooksley wrote: > Hi all, > 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 li

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On 15/01/2023 08:04, bcooks...@kde.org wrote: For blogs.kde.org, I am in two minds as to the best approach here, with Wordpress and Hugo both appearing as candidates for this site. Opinions welcome, especially if you are someone that currently uses it. I don't use this site, so I'm not gonna pi

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On Sunday, 15 January 2023 19:50:54 CET Ingo Klöcker wrote: > On Sonntag, 15. Januar 2023 18:34:50 CET Paul Brown wrote: > > On Sunday, 15 January 2023 16:24:48 CET Ingo Klöcker wrote: > > > On Sonntag, 15. Januar 2023 08:04:18 CET Ben Cooksley wrote: > > > > For blogs.kde.org, I am in two minds as

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On Sonntag, 15. Januar 2023 18:34:50 CET Paul Brown wrote: > On Sunday, 15 January 2023 16:24:48 CET Ingo Klöcker wrote: > > On Sonntag, 15. Januar 2023 08:04:18 CET Ben Cooksley wrote: > > > For blogs.kde.org, I am in two minds as to the best approach here, with > > > Wordpress and Hugo both appea

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

Thanks, but we already know what we want. Cheers Paul -- 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

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On Sunday, 15 January 2023 16:24:48 CET Ingo Klöcker wrote: > On Sonntag, 15. Januar 2023 08:04:18 CET Ben Cooksley wrote: > > For blogs.kde.org, I am in two minds as to the best approach here, with > > Wordpress and Hugo both appearing as candidates for this site. > > Opinions welcome, especially

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

Hey, Just to intervene, I think another problem is that commiting changes to any SSG though git and having to understand the stack can slow down promo's work, especially when less experienced contributors would like to help in adding content. But I know working Wordpress can be a pita for everyone

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On Sonntag, 15. Januar 2023 08:04:18 CET Ben Cooksley wrote: > For blogs.kde.org, I am in two minds as to the best approach here, with > Wordpress and Hugo both appearing as candidates for this site. > Opinions welcome, especially if you are someone that currently uses it. I think I'd very much pr

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

Hi Paul, On Sun, 15 Jan 2023 10:21:50 +0100 Paul Brown 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 >

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

Hi Ben, As the main developer of Skrooge and administrator and developer of skrooge.org (currently on Drupal), _it is normal that I am in charge of the migration_. But, I don't know Hugo and I already have other websites on wordpress, so I would appreciate if I could make skrooge.org on wordpr

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On Sunday, 15 January 2023 10:33:06 CET Ben Cooksley wrote: > On Sun, Jan 15, 2023 at 10:21 PM Paul Brown 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 ma

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On Sun, Jan 15, 2023 at 10:21 PM Paul Brown 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 o

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

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 Drup

Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

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 a