I assume that many people at Matrix have been pretty busy with the whole Riot -> Element migration thing, which is also absolutely fine. Still, do we have a progress update from the Matrix side here?

Was moved to https://invent.kde.org/frameworks/kxmlgui/-/merge_requests/10, closing this revision here.

Seems as if this change was implemented but the accompanying revision wasn't closed.

Probably no longer important given the migration to Jekyll from the 2019 report onwards, since frankly ~nobody will read the older reports anymore.

This effort is (luckily) no longer WIP but live :)
So probably this revision can be closed.

Should probably be migrated to invent and be reviewed there.

Seems done. Can probably close revision.

Probably no longer relevant if we go ahead with the plan of a developer portal (https://invent.kde.org/carlschwan/developer-kde-org).

Given that kde.org has been completely overhauled by Carl since this revision anyway, this review can probably be closed.

Done by meven in D29002.

In T13296#234459, @ognarb wrote:

No need for fixing #kde-chat anymore, the irc bridge was disconnected and instead use matrix instead: https://webchat.kde.org/#/room/#kde-chat:tchncs.de. This is very much better experience for everyone, thanks @cblack :)

In T13287#233268, @bshah wrote:

Once concern regarding "matrix" to "telegram" native bridge is that it creates the IRC users for each of the "bridged" users in telegram room, for some channels like e.g Plasma Mobile channel this is 500+ users on matrix side, and same amount of users added on IRC side.

Currently we are hitting our IRC connection limits as-is with freenode folks as I understand. So we also need to ask freenode people if they are fine with it as well.

Agreed. I think it is be sensible to separate possible migration of the forums to Discourse from the Dot migration to Hugo, given that the Discourse migration likely will still take some time which would block the Dot to Hugo project.

Can probably be closed now, the new site has launched and everything is now neatly stored in git over in invent.

The website is now live and it's fabulous!

This is long implemented, so I guess this review can be abandoned?

The EoL is now more than a month past and there isn't much more to be promoted at this point, so I think we can close this task now. Measuring success will be nearly impossible, but I hope that the campaign had at least some impact.

I think this is closeable now. Maybe it'll become relevant again for the next GSoC, but I think it's better to create a new task for that than to necrobump a very old one.

Released for quite a while now (https://kde.org/announcements/releases/2020-02-apps-update/), so I think we can close this task.

Looking at the schedule (https://community.kde.org/Schedules/Plasma_5), I see 5.19 due in June and 5.20 in October. As far as I am aware, Qt 6 is planned for November, and the release page mentions the last Plasma 5 LTS at the same time as the first Plasma 6 release. All together, that means that we will probably still have at least 3, more likely 4 or 5 Plasma 5 releases. If we continue updating the wallpaper with every second release, we would probably need 2 wallpapers for the Plasma 5 cycle.

Draft for a generic post for the respective forums/subreddits. Again, feedback more than welcome.

First draft for a "I'd like to post this KDE promotion thingy here" to send to moderators of the respective forums/subreddits. I'm not great at writing these things, so please edit/update/improve as you'd like.

This didn't really work out. Let's investigate for the next time we get a bigger Apps update on how to progress.

Possibly we could post in the various Windows forums that are around (get permission to do so first, but that shouldn't be too hard):

• https://www.sevenforums.com/
• https://windowsforum.com/#windows-7-forums.251
• https://www.windowsforum.org/forum/63-windows-client-os-support/
• https://www.techrepublic.com/forums/windows/
• https://forum.thewindowsclub.com/
• ...

I don't have a dev account yet, so it'd be great if you could push it for me.

In T12029#213738, @paulb wrote:

Suggested rules for the video competition:

1. Even if your work is not win, your submission may still be used to promote KDE's software

In T11108#196342, @ognarb wrote:

In T11108#196337, @ngraham wrote:

Another advantage is unifying our infrastructure by moving the git repo hosting and continuous integration to the same all-under-one-roof infrastructure.

This is probably a point that need to be confirmed with the sysadmin. I was told that the websites need to be deployed with binary-factory (see https://invent.kde.org/sysadmin/ci-tooling/merge_requests/17), but it's probably an exception.

Here Carl points out that currently not all our infrastructure can be unified in GitLab, because we still need binary-factory to rebuild our websites if there are any code changes.

I agree with @niccolove that we should not rename a project without strong reasons to do so, because tutorials, docs and a lot of other things would suddenly be outdated and not easy to find anymore.

Great work! Two small things:

1. I would suggest either removing the "Information" and "Note" titles in the boxes or to format them differently than the body text. Right now, there is no clear separation between the content and these words, which feels a bit akward.
2. In my opinion the visited links look a bit too "washed out"/bright - there isn't a lot of contrast anymore. Maybe tone down the brightness a bit, or even make them darker than the unvisited links? (Probably something for our VDG group...)

In T10855#183381, @paulb wrote:

In T10855#183349, @GB_2 wrote:

Got no response from @kvermette to the email I sent a few days ago. If we want to do the wallpaper contest we should start preparing it now, before it's too late.

Agreed. We need somewhere participants can upload and display their entries. How can we do that?

In T10827#182890, @johanneszarl wrote:

Should KPhotoAlbum enter this discussion?

In T10318#182551, @mludwig wrote:

In T10318#175542, @xyquadrat wrote:

My idea is to host it under kile.kde.org eventually, but for that I'll need to talk with Sysadmin and set everything up. Right now I simply created a demo hosted on my own server because that was easier and I would not have wasted the precious resources of our sysadmins if in the end the site is not wanted.

Thanks, but Kile's website is just fine under https://kile.sourceforge.io/. You are welcome to propose a new style but it shouldn't be the same as for *.kde.org.

I totally agree that it'd be great to update most of these websites to a unified design similar to the one used in kontact.kde.org. That would require us to create a boilerplate-style repository where all the CSS and JS lives. The HTML is probably very site-dependent, but we should still try to reduce maintenance as much as possible and to unify parts that are common in multiple sites.

In T10636#182505, @aacid wrote:

In T10636#182497, @xyquadrat wrote:

• The release announcement is currently only translated into 5 languages, whereas 18.12 was translated into 10. I don't know much about our translation process - can anyone provide further insight on why this might have been the case?

Unfair comparison, it's been 3 days since the release so you shouldn't compare current state of 18.12.0 but the state on December 16, which was

applications-18.12.0: en,ca,pt,uk

so one language more now than for 18.12.0

Now that the release is over, I'd like to share a few thoughts on how the release announcement went and what we might want to improve:

In T10812#182284, @jtamate wrote:

In T10812#182201, @ngraham wrote:

In T10812#182195, @aacid wrote:

Apps that are in the bundle have inconsistent versioning; most use the bundle's own versioning scheme, but others use their own

I personally disagree this is a problem. It let's applications hop on and off the release and keep their versioning number intact.

I'm using Dolphin 18.12.3, which comes from KDE Applications 18.12.3. But the bundle also comes with Okular. Am I using Okular 18.12.3? Or Okular 1.6.3? The promo material says 18.12.3. The version number in my distro's packaging says 18.12.3. Discover, which uses the distro packaging metadata, says 18.12.3. But the About Okular window says 1.6.3. This is confusing and problematic from a user, packager, and promo perspective because it's not clear which version number they should use.

What about an hybrid versioning system for the apps?
Perhaps something like "Okular 1.6.3, distributed with KDE Applications 18.12.3", something that remarks that Okular has an individual release cycle, but this version comes from KDE Applications 18.12.3 bundle.

I do plan to make a release video; will start working on it this weekend so that it should be finished by April 17 or earlier.

What is the status of this patch? @rkflx is not around any more, but maybe someone else can take this review?

Welcome text sounds good to me.

My idea is to host it under kile.kde.org eventually, but for that I'll need to talk with Sysadmin and set everything up. Right now I simply created a demo hosted on my own server because that was easier and I would not have wasted the precious resources of our sysadmins if in the end the site is not wanted.

Friendly ping to @mludwig, do you have any objections?

@acrouthamel I was just thinking about the fact that we need to kick off some more Bug days for this year when I saw the notification that you were a tiny bit faster than me... :)
List sounds very reasonable, and I do agree that it is important to contact as many of the developers in advance to ensure we are as efficient and productive as possible. My only concern is that we might not have enough KCalc bugs to triage for two sessions, so we might need to search an additional alternative. Are we going to keep the two-week-rhythm?

You are amazing, thanks for your hard work! I'll see if I can help out this weekend.

Thanks @trickyricky26, I would never have noticed that. Fixed.

I'll try to finish my "release annoucement" video (it's pretty bad, but whatever) this weekend, thanks @ngraham and all others for collecting all the new features :)

@jriddell I think it would be great if we could use the modern theme for this, what needs to be done to make this happen? It would make it visually consistent with the Plasma release announcements (which already use the new theme) and works much better on mobile than the current theme.

Regarding Digikam: I am not sure where on their website (https://digikam.org) to put a "Made by KDE"... Maybe to the left of the "Download" button? I think it'd also be great if we could somehow have a presence in the application, as Digikam is one of the projects that is often used standalone, without any other KDE software (similar to Krita). According to the git history, @cgilles is probably the most active Digikam developer, so we should discuss this with him.

5.14 has been released and while we didn't have an official video, there was a nice number of other videos that also showed off the new features. Let's wait and see if 5.15 brings something more exciting to the table.

KDE is a cooperative enterprise in which no single entity controls the efforts or efforts or products of KDE to the exclusion of others.

As the GitHub repository is now officially unmaintained and the source has moved to Phabricator, it would be a good idea to open up a new product on bugs.kde.org so that users can report bugs. You'll probably need to contact Sysadmin for this.

Abandoning revision as @araceletorres already updated the content until the end of 2017.

In D16153#342645, @bcooksley wrote:

Linking to outside sites is fine, it's the hotlinking to images that i'd rather avoid. People's personal blogs have been known to go down in the past when their post hit Planet due to the images from that post being embedded on Planet and thus generating quite a bit of load on their blog server.

In D16153#342264, @bcooksley wrote:

One thing i'm curious about: why are you removing the Facebook/Twitter infrastructural points?

Surely those could be used in the future?

Include suggestions from Paul

It's great to hear that you've already been updating screenshots on userbase @ognarb ! I am currently on vacation, so I won't be able to help you until next week. +1 for your proposal, we really need a more clearly defined structure for the application pages. I also experienced some problems when updating screenshots, this might be related to the fact that userbase currently needs to be based upon an older version of MediaWiki. If the problem persists we should ask the Sysadmin team if they could take a look.

Ideas for niches to take over:

• Kdenlive should become the go-to free video editor for hobbyists and semi-professionals
• KMail should establish itself as a valid free alternative to Outlook (and simliar) for small businesses and schools

Are we going to have a release video for 5.14? They are always a great way to make people aware of the new feature/fixes, but it obviously take quite a lot of time to produce one.

@drosca Picture of a blog page:

I'd suggest:

+1. If we do start following that schedule, that'd mean the dates left for 2018 would be:

As mentioned in this official post by Twitter, the current feeds are broken since September 10th. This means that it'd be great if we could go ahead with the implementation of this task such that we have a working widget on the Planet again. Is there anything that is currently unclear/needs to be done?

I have tried it on mobile and most elements adapt perfectly, so we don't need to change anything there. One thing that I'd change is the "Made by KDE" logo: The top row looks too crowded with the logo, so we should consider moving it at the bottom of the link bar instead. (Falkon.org also does this)

Ah, I knew that I was not clear enough with this description... The slide show has those fancy blocks at the bottom where you can click to reach another slide easily:

This task is a bit stuck in the pipeline. I think we can generally all agree that it'd be a good idea to host our videos on a public Peertube instance, as Peertube better reflects our values and priorities. Now, https://nsa.ovh has recently encountered a total data loss according to their Twitter account, so I don't think they'll be a viable option in the near future. Currently https://peertube.mastodon.host sounds like the best option to me (high data cap that we can surely ask to be upgraded if needed, 1080p video and the admin(s) seems to have quite a lot of experience). A good start would be if we could upload the Akademy videos there, as they are mainly thought for a specific audience and not for the general public to randomly stumble into. When will the videos be ready & who manages them?

This would probably have to be done by the KDE Sysadmin team, so we should probably forward this list to them. Right now I am a bit concerned that not everybody might be content with the decision to simply remove all of those from Bugzilla... But then again, all products that would be deleted are unmaintained and the big majority does not have a single bug reported against the product.

I do not have commit access, so unless somebody has any objections to this change I'd be glad if you could land it for me. Thanks!