Junior Jobs for all projects within KDE.
Wed, Oct 2
@johanneszarl I think its almost the new website is almost done, I just need to fix one bug in the theme. Not sure I can finish it before the end of next week. Sorry for the delay, I'am quite busy with life and other KDE related stuff :(
Tue, Oct 1
@simonkr: Just checking in on this - is there anything that you need from us?
Sat, Sep 21
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.
It would take weeks to move all of them, instead, you should warn content writers to NOT write inline styles :)
Fri, Sep 20
Sep 18 2019
Sep 17 2019
@ognarb: I read the documentation again and I am able to create pages. Thank you.
@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).
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.
Sep 16 2019
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.
Sep 15 2019
Aug 20 2019
Aug 17 2019
Aug 15 2019
I've improved the texts a bit (see merge request), removing some paragraphs as I saw fit.
It's on KDE's svn server: svn+ssh://firstname.lastname@example.org/home/kde/trunk/www/sites/kphotoalbum
Apart from that, I currently have no idea (yet) how that Jekyll thingy works … but probably, the existing PHP code of the news page could be used here?!
Unsplash is not okay :(
The KPA demo database could also be used, to be accessed via kphotoalbum --demo. The images are also a bit dated, but I think we won't have a copyright problem with it.
@tleupold Okay. But i reeaalllyyy have no idea, how i can convert the news site...
I never used KPhotoAlbum, but it looks like very similar to Gwenview. You can view a images in KPA and Gwenview.
Like you can view files with LibreOffice Writer's "open" dialog and Dolphin.
It's very nice that somebody volunteers to rework the site. It's definitely dated. I cared about it the last few years, but I only worked on it under the hood and never touched the design … the most important thing is the News section I think where we announce releases etc. The "Getting involved" part is nice when it comes to the active and former developers, but I don't know if we need the rest here. Perhaps, one should simply advice somebody who wants to join us (a rare case ;-) to log in on our Freenode channel and simply talk with (one of) us. Same for "Testimonials", I'm not sure if we need this. As of "Documentation", I think the only really relevant thing is the "3 Minute Tour" to show what we have/can do, but it definitely needs a makeover. The rest can probably be linked, but the wiki stuff on KDE's servers is most probably also a bit out of date (we simply lack the manpower …)
Exactly! :). I see no Reason to stop supporting KPA.
@KonqiDragon: Seems like you never used KPA (or thought about what you're writing here). It's not "old", it's actively developed and up-to-date. And it serves a complete different purpose than Gwenview. Gwenview is a viewer, KPA is a tagging and archiving program. Don't compare apples and oranges.
It seems like KPhotoAlbum is made for a different usecase than gwenview. KPhotoAlbum seems more about managing and tagging photos than gwenview, which is more like a basic viewer with a few editing features.
Why do KDE need to support the old KPhotoAlbum when we have a modern Gwenview? Let's just stop supporting KPhotoAlbum.