I've sent merge requests for all our sites that are either:
a) Static; or
b) Built using a Static Site Generator

What's the best page to link to instead? https://kde.org/community/donations/ probably

It looks like forum.kde.org is even redirecting to discuss.kde.org now, so I can't verify the change. But, that's acceptable too, so whatever! 😆

The banner has been added (by Harald Sitter I think).

IIRC it was lost accidentally in some technical migration, and was not a deliberate thing. It needs to come back to avoid confusing the heck out of users, yeah.

It has been explaine, don't reply instead reread those messages. This is completely unacceptable behaviour. You're sabotaging your own cause.

We spoke in a previous task about this. You cannot just reopen the same ticket again and again.

In T16730#295630, @davidedmundson wrote:

Wording like this does not help convince people to join your mission but instead close this whole issue off hand.

If so, KDE should add a clear exception to the KDE Vision for benevolent Western

We're focusing on moving everything to donorbox instead.

We're moving everything to donorbox where this tracking is working as we need it to.

We've been through this.

• Pages being statically generated resolves points 1 and 5;
• Getting CI artifacts and repositories is apparently the way to go if we want to systematically obtain updated app data. Anyway, with recent efforts, the build time is considerably reduced;
• appstsreamcli convert has been replaced by the py-appstream package which can be updated when we want to get more kinds of data;
• The staticweb image has been used to build the website, instead of the `suse-qt515 one.

Beautiful!

Yeah, I think so!

Should we add these pieces of info into the same section where we are now showing links to Windows versions? With some text modification, of course, so that it doesn't mention only Windows ones?

Not only AppStream download button but other ones have all been redesigned to be visually uniform, less redundant, more familiar to users, and support l10n better, with this MR. You can see the discussion related to the MR here.

The redesign has finished. Let's close this.

@cblack Thank you so much, it was a kind offer but I don't want to increase the amount of workload on you. Thank you!
@aacid We can try and make some automation for approved strings but I can't estimate the effort required for SVN.

Update: all, except the archiving step, are done for games.k.o:

• "How to play" sections are shown for games having the data. These sections can also be translated;
• Accessing games.k.o pages will redirect to corresponding parts on apps.k.o, except games.k.o/old and its subpages which are left untouched.

Well, this tangent is kinda moot now since some chatting & it's probably not going to work out having Hebrew team work on the instance I set up for the Toki Pona team.

That's probably acceptable but I am going to maybe wrongly assume you don't also speak Hebrew?

I'm going to warn you against that, you can't create a system to automatically commit things from other people into KDE servers without human interaction, that's basically giving out your user for anyone else to [ab]use, and that's obviously not allowed.

@aacid That's maybe relevant to pootle, in Weblate there's an ACL and a string approval system.

I'm going to warn you against that, you can't create a system to automatically commit things from other people into KDE servers without human interaction, that's basically giving out your user for anyone else to [ab]use, and that's obviously not allowed.

Could we chat on a more real-time platform to hash out the details of that? My matrix is @pontaoski:kde.org and Telegram is https://t.me/pontaoski

@cblack Yes, I'd love that.

You want to use the Weblate instance set up for the Toki Poka team for the Hebrew localisation?