Alright. I think I can put this task on hold. I was happy to do it and learn how the Wiki software works.

@ognarb I’ve just noticed that you already moved the information from https://utils.kde.org/projects/kgpg/building.php to the wiki back in July. As far as I can tell, there’s no other information worth adding to the wiki.

Good luck with your exam 👍

Thanks, I have an exam Monday, so I will review the change and merge all of it Tuesday 😁

@ognarb I think that we can mark this task as completed. I've moved inline styles from the most important Plasma pages.
There are still 200+ files left that contain inline styles, but they are mostly from announcements and info pages.

If it helps, do all the experiments you want on kate-editor.org.
The web-server will re-pull the git all 5 minutes after some change.

Now I see that you mean, I added an import function. python3 translations.py import directory/with/po/files

No, I think that's the structure required by sphinx. Make sure that import_po_dirs returns the structure that you need.
Please note that the use case of docs-krita-org involves multiple pot files. If you just need one (but again, it depends on the size), this is a simpler case:
https://cgit.kde.org/plasma-browser-integration.git/tree/StaticMessages.sh

Ok so I suppose the po files need to be located at locale/$lang/LC_MESSAGES, do I need to make a bash script instead?

Take a look at what krita does:

@ltoscano I created a merge request for translating the content of kate-editor.org https://invent.kde.org/websites/kate-editor-org/merge_requests/6

• if releaseme can fetch translations from SVN when creating the tarballs, I don't see how to do it
• size: it depends on how big the files are going to be
• not much; something is here: https://techbase.kde.org/Localization/Concepts/Auto_Assists#Daily_jobs_done_by_Scripty - but you don't need to know it, as long as you provide a script for extracting/merging, see what docs-krita-org does.

There seems to be an overlap with this task: https://phabricator.kde.org/T6842

@ognarb: I read the documentation again and I am able to create pages. Thank you.

❤ for having people that are not us look at it

@ognarb I’ve had a quick look, and to me the only content that seems worth migrating is https://utils.kde.org/projects/kgpg/building.php. Is there something else you think we should migrate to the wiki? If so, could you give some specific example? (e.g. what information from https://utils.kde.org/projects/ark/development.php is worth covering in the community wiki).

@KonqiDragon Translations are planed, but it will take time to write an interface between Jekyll or Hugo to the KDE translations workflow. I already wrote a parser which extracts the string from a file and create pot files and now I trying to find a solution to generate the translated files from mo files.

How about adding a language switch to redesigned sites?

For the user facing information, we already have kde.org/applications with autogenerated information. This is the major motivation of killing utils.kde.org since we don't need the website as much as before and it's one website less to maintain.

Hello @vladimirmikulic, you can follow the instruction at https://community.kde.org/Infrastructure/Phabricator#Using_Arcanist_to_post_patches. Note you will need to use arc diff --conduit-uri=https://phabricator.kde.org/ to create the diff instead of arc diff.

Since I didn't use SVN and arc before, how can I create a "pull request"?

The issue with responsiveness is fixed.

Having difficulty making new pages, so for now I am dumping the content under my 'Talks' page.

I've now converted evolve.kde.org into a redirect and have corrected the Phonon page redirection.

It's time to remove evolve.kde.org and redirect to https://community.kde.org/Goals.

That isn't even controlled by us unfortunately.

What about http://kde.com ? Some recently linked to it on Reddit, but it's an outdated copy of https://kde.org

For evolve.kde.org I guess it's ok to remove it and redirect it to the goals landing page.

Those four have now been eliminated.

@nalvarez wrong copy paste ;)

Necessitas is not Phonon, I don't think that redirect is correct.

I will create a subtask for the websites that shall be purged.

Shall we create sub-tasks for the websites that shall be purged?
And should one move the repos of that packages to some "obsolete" place on invent.kde.org to archive them (in case someone wants to pick them up again) and to avoid one confuses them with active repos?

I created an etherpad: https://notes.kde.org/p/websites_bof_2019

Awesome, thanks for investigating all of this.

In T8449#197298, @bcooksley wrote:

Adding fields at runtime isn't something we've got a hard requirement for, so that won't be a big deal.

The lack of 2FA and abuse preventation systems is a bit more of an issue though, and we'll probably need to add the account change notifications we need to keep sites up to date with account details as they change them. Otherwise it is looking like a very good base to start from.

Adding fields at runtime isn't something we've got a hard requirement for, so that won't be a big deal.

I looked at the blender id system as a replacement. Under the hood it's using django and the django authentication plugin

[spam comment removed by sysadmin]

[spam comment removed by sysadmin]

Current look in D23543

Thanks for the link @lydia. This makes the plain talk page a lot more interesting.

MediaWiki can do pings with https://www.mediawiki.org/wiki/Notifications. It's used on Wikipedia and co