Sysadmin Load Reduction: Project Specific Sites
bcooksley at kde.org
Wed Nov 13 09:42:33 GMT 2019
On Wed, Nov 13, 2019 at 10:00 PM Thomas Friedrichsmeier
<thomas.friedrichsmeier at ruhr-uni-bochum.de> wrote:
> On Tue, 12 Nov 2019 21:32:16 +0000
> Carl Schwan <carl at carlschwan.eu> wrote:
> > I now created a repository with the content automatically
> > extracted from mediawiki with a script. The extracted result is very
> > bad but I started cleaning it see commit. This need to be moved to
> > the website git namespace, but until this is done I granted every KDE
> > developer push access. I would be very grateful if some other peoples
> > could help clean some generated pages (you only need knowledge in
> > markdown) for inspiration you can look at 
> Thanks for that! This does sound like a very workable solution. Two
> 1) What will be the procedure for updating the website, once ready?
> Pushing to a specific git repo, AFAIU, but who exactly will have push
> access, and can we - as project maintainers - grant push access to
> additional KDE developers who would like to contribute to our pages?
Pushing to a Git repository in the websites/ namespace will trigger
automated processes on our side to regenerate the site and republish
The logs can be viewed on the Binary Factory on the Websites tab
(where you'll also find all the other websites that use this same
In terms of access, you'll need to ask Sysadmin to get people added,
but anyone with a KDE Developer account can be added yes.
> 2) Can I preview the converted page live? That would make it easier to
> scan for cases of bad conversion.
There are some Markdown renderers which may be able to provide this (I
think there is a kmarkdownviewer or something along those lines) but
there isn't anything we provide specifically for this.
As your site will likely be processed using either Hugo or Jekyll
though, it should be straight forward for you to run the exact same
generation process we run on the server locally on your system to
verify the results.
> > And it would be nice if the rkward devs could provide a new version
> > of https://rkward.kde.org/File:RKWard_060_450.png (using breeze theme
> > and icons and not from 2012).
> > Let's try to update this website very soon since the mediawiki
> > version is still 1.19 (EOL 2015)
> Will do my best (which may not be much, though).
> > Cheers
> > Carl Schwan
> > https://carlschwan.eu
> > : https://invent.kde.org/carlschwan/rkward-kde-org
> > :
> > https://invent.kde.org/carlschwan/rkward-kde-org/commit/f4a1ee44cf0d753c41cdf6cfc8a87ae6cee7fcae
> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > On Tuesday, November 12, 2019 7:27 PM, Ben Cooksley
> > <bcooksley at kde.org> wrote:
> > > On Sun, Nov 10, 2019 at 4:10 AM Thomas Friedrichsmeier
> > > thomas.friedrichsmeier at ruhr-uni-bochum.de wrote:
> > >
> > > > Hi Ben,
> > >
> > > Hi Thomas,
> > >
> > > > On Sat, 9 Nov 2019 12:50:07 +1300
> > > > Ben Cooksley bcooksley at kde.org wrote:
> > > >
> > > > > - RKWard (rkward.kde.org): This site is currently based on
> > > > > Mediawiki, which is substantially more difficult to maintain
> > > > > and keep updated compared to a site built using Hugo, Jekyll,
> > > > > Wordpress or Drupal.
> > > > >
> > > > > Given that the site was last updated back in early 2018, i'd
> > > > > like to make this static, and should updates need to be made in
> > > > > the future the content can then be converted at that time into
> > > > > something more easy to maintain.
> > > >
> > > > please not static. I know we have not been active of late, but it
> > > > totally won't help, if we need to climb a hill of administrative
> > > > tasks, before we can even get starting thinking about making a
> > > > new release. Frankly, we did not come to KDE back in the day in
> > > > order to increase our administrative overhead...
> > > > We're really open to solutions of all kinds. Twice sysadmin had
> > > > proposed to somehow unify the rkward mediawiki installation with
> > > > the techbase and userbase installation. We gave green light on
> > > > both occasions, but nothing happened after that.
> > >
> > > Apologies for that - in each instance the person who was going to
> > > work on it disappeared.
> > >
> > > > I wouldn't mind any other hosting solution, really, it doesn't
> > > > have to be wiki-based. Provided that we can have a - relatively -
> > > > smooth migration path, and that we don't have to switch to
> > > > something new yet again, in two or three years.
> > >
> > > Would something based on Markdown be sufficient for this?
> > > There appear to be Mediawiki -> Markdown converters out there we can
> > > use which will get us 95% of the way there.
> > >
> > > > Regards
> > > > Thomas
> > >
> > > Cheers,
> > > Ben
More information about the rkward-devel