|Open||None||T10827 Website redesign|
|Open||None||T11657 Delete some websites|
|Resolved||jvandorp||T11668 Move information from utils.kde.org to the community Wiki|
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.
It's strange what you can't create new pages, anyway I changed your wiki user group to trusted. Let me know if the problem persists.
@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).
@ognarb: I read the documentation again and I am able to create pages. Thank you.
@adrianchavesfernandez: I can do it sometime tonight. I copy the content whenever I find a little bit of time and when I am tired of thinking too much.
So far I have done KCalc and KCharSelect.
This task should be finished before end of the week.
@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.
The information @jvandorp is copying, while nice, is hard to maintain in the wiki, and should already be available in other, more-appropriate channels.
For example, regarding the information currently in https://community.kde.org/KDE_Utils/KCalc, all of it should be accessible direct or indirectly from https://kde.org/applications/utilities/org.kde.kcalc
Alright. I think I can put this task on hold. I was happy to do it and learn how the Wiki software works.
If there is nothing of value lost by not copying over the rest we should likely mark this task as finished or no longer being required so that it doesn't block other work.