It is busy days at the moment – but in a positive way.

First of all – a huge thanks to everyone who submitted to the Call for Papers for foss-north 2020. We have over 70 hours (!!!) of contents to squeeze into two tracks over two days. As always, it will be hard to pick the speakers to create the very best program.

Other foss-north activities includes starting to populate the community day activities, as well as getting a whole bunch on sponsors onboard. An extra big thanks to Luxoft and Red Hat Ansible for helping us by picking up the Gold Sponsorship packages. Ansible are even running their European Contributor Summit as a part of the foss-north Community Day together with events by KDE, Gnome, FreeBSD, Debian, and a hardware hacking workshop. I’m really looking forward to this – if you want to join in with your own project, workshop, hackaton, etc – just ping me!

The other big foss-north change for this year is that we are finally abandoning Eventbrite for a self-hosted system. Big thanks to Magnus Hagander helping us getting the pgeu-system up and running. At the moment, we offer login via Github and Google OAUTH. We’re looking into setting up a self-hosted OAUTH service as well, to let you log in locally, but that will not happen for the 2020 event due to time reasons.

Closer in time is the next local foss-gbg meetup. We are running an event around React together with our good friends at Edument. We already have 50+ registered attendees, so it will be fun!

In other news – I’ve also released Ordmonster – if anyone has kids who wants to get started reading. This is a complement to the Mattemonster app for basic maths launched earlier. Both are made with Godot, a tool that I enjoy more and more.

Plasma 5.18 has been released! A ton of work went into this release and we’re very proud of it. However I’d like to apologize for it being a bit buggier than we’d have preferred. We’ve gone balls-to-the-wall off the chain bananas fixing the issues you folks are reporting! Almost all of the highest-profile issues are fixed already, to be released with Plasma 5.18.1 in a few days! And we’ve got the less major regressions in our sights too! But still, we know that stability hasn’t always been our strong suit and we’re aiming for a higher standard next time, discussing how we can get there. So thank you for your patience and understanding, and enjoy Plasma 5.18!

Oh and we also fixed some of the most long-standing issues with Samba shares. Check it all out:

New Features

• Konsole now lets you set a custom color for the text under the block-style insertion point (Arthur Kasimov, Konsole 20.04.0):
  
• In Elisa, it’s now possible to disable the feature of showing the current song’s playback position on the app’s Task Manager entry (Matthieu Gallien, Elisa 20.04.0)

Bugfixes & Performance Improvements

• Moving or copying files onto Samba shares no longer resets their timestamps to the current time (Harald Sitter, Dolphin 19.12.3)
• In Dolphin, it’s now possible to create and paste files on Samba shares (Harald Sitter, Dolphin 19.12.3)
• When trying to connect to a Samba share, you now have the opportunity to specify the domain, allowing connections to shares with a non-default domain (Harald Sitter, Dolphin 19.12.3)
• URLs beginning with cifs:// are now accepted as valid paths to Samba shares (Harald Sitter, Dolphin 19.12.3)
• Files on Samba no longer nonsensically show up as belonging to random local users (Harald Sitter, Dolphin 19.12.3)
• Samba shares now show their available amount of free space in Dolphin (Harald Sitter, Dolphin 19.12.3)
• Dolphin now correctly hides files on Samba shares that have been marked as hidden (Harald Sitter, Dolphin 19.12.3)
• Okular no longer crashes when showing a print preview (Albert Astals Cid, Okular 20.04.0
• Okular no longer permits PDF documents with embedded JavaScript code to exhaust all system resources (Harri Porten, Okular 20.04.0)
• Konsole’s dark background detection feature now works again (Manuel Rüger, Konsole 20.04.0)
• Those of you who had your widgets locked in Plasma 5.17 or earlier can now access the new global edit mode. In the meantime, before Plasma 5.18.1 is released, as a workaround you can run qdbus org.kde.plasmashell /PlasmaShell evaluateScript "lockCorona(false)" to fix the issue immediately (Marco Martin, Plasma 5.18.1)
• Then “Apply” button on the System Settings Fonts page now activates normally again so you can actually save changes you’ve made to the default font configuration (Benjamin Port, Plasma 5.18.1)
• Mouse input in GTK apps using XWayland now works properly (Vlad Zahorodnii, Plasma 5.18.1)
• Closing windows using the Present Windows effect no longer messes up the window stacking order and prevents windows from being focused or de-focused (David Edmundson, Plasma 5.18.1)
• Snap apps no longer get stuck in a half-installed state if you cancel the installation after being told that installing the app will require disabling security confinement (Aleix Pol Gonzalez, Plasma 5.18.1)
• Plasma no longer crashes when you switch virtual desktops after changing the layout on Waylandno longer crashes when you switch virtual desktops after changing the layout on Wayland (David Edmundson, Plasma 5.18.1)
• Menubar text in Electron-based apps is now readable (Carson Black, Plasma 5.18.1)
• The desktop’s chord keyboard shortcuts (e.g. Alt + d, then a) once again work (David Edmundson, Plasma 5.18.1)
• System Settings pages once again prompt you to save or discard your changes if you try to navigate to another page with unsaved changes (David Edmundson, Plasma 5.18.1)
• The Plasma Wayland session is no longer sometimes called “Plasma (Wayland) (Wayland)” on the System Settings Login Screen (SDDM) page (David Edmundson, Plasma 5.18.1)
• The System Settings Search page no longer allows content in the scrollable list view to overlap with the scrollbar (Plasma 5.18.1):
  
• The content layout of the “Advanced” tab in the System Settings Login Screen page no longer hilariously stretches vertically with large window sizes (Filip Fila, Plasma 5.18.1)
• Recent files that are located on Samba shares can now be accessed properly using the application launcher menus (Méven Car, Plasma 5.19.0)
• The Baloo file indexer can now be enabled and disabled and paused and resumed again (David Edmundson, Frameworks 5.68)
• The Baloo file indexer now correctly resumes indexing, both automatically and manually, after the machine has woken from sleep (Stefan Brüns, Frameworks 5.68)
• Fixed various Plasma apps and System Settings pages crashing when needed plugins aren’t available for some reason (Kai Uwe Broulik, Frameworks 5.68)
• Fixed a recent regression in how controls in FormLayouts throughout Plasma and Kirigami apps were positioned (Marco Martin, Frameworks 5.68)
• Non-maximized panels using non-default color schemes or Plasma themes no longer have odd white corners (Niccolò Venerandi, Frameworks 5.68)

User Interface Improvements

• Dolphin’s context menu now has “Create New” back at the top again (me: Nate Graham, Dolphin 20.04.0):
  
• Elisa’s Now Playing view now uses a blurred and lightened version of the album art as the background rather than showing a slice of it at the top (me: Nate Graham. Elisa 20.04.0):
  

• Elisa’s grid items are now opened by simply clicking/tapping once on them (me: Nate Graham, Elisa 20.04.0):
  
• When a notification pop-up tracking the progress of an extended job is expanded to show more details, it no longer ever repeatedly resizes itself to be smaller and then larger again as the height of the text inside changes (Kai Uwe Broulik, Plasma 5.18.1)
• After feedback that Task Manager tooltips with album art in them looked a bit crowded, we redesigned them to look better and have better usability (me: Nate Graham, Manuel Jésus de la Fuente, and Tranter Madi, Plasma 5.19.0):
  
• The “audio playing” indicator on Task Manager items are now a bit smaller and closer to the edge when using an Icons-Only Task Manager so that you aren’t so likely to click on them by mistake (George Vogiatzis, Plasma 5.19.0). Also as a reminder, if you hate them, you can turn them off! Just right-click on an empty area of the Task manager, click “Configure Task Manager…”, and uncheck “Mark applications that play audio”.
• Large titles throughout KDE software are no longer quite so huge (me: Nate Graham, Frameworks 5.68):
  Click to view slideshow.

• icons that incorporate the symbol now have the slash going through it in the exact same orientation (Matej Mrenica, Frameworks 5.68)

How You Can Help

Upgrade to Plasma 5.18 and find all the bugs we missed! The first point release (i.e. Plasma 5.18.1) will be released in two days, so every bug report we get soon is super important.

More generally, have a look at https://community.kde.org/Get_Involved and find out more ways to help be part of a project that really matters. Each contributor makes a huge difference in KDE; you are not a number or a cog in a machine! You don’t have to already be a programmer, either. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!

Finally, consider making a tax-deductible donation to the KDE e.V. foundation.

Hello, everyone! There has been some time since my last blog post. It has happened because of a good cause, since I was focusing on my undergraduate thesis. Now I have finished it and finally have completed my graduation, yay! Soon I will include my thesis on my blog and share it with the world... … Continue reading Akademy 2019 – Late Report

hey there it is me again.
Has you probably should know I am participating in SoK 2020, see this post first otherwise. We are near the end of the project, and I had like to say what more I have done after my first post. you can see all the commits in this repo. Recently I have made an Merge Request(!1) to apply all the commits that I have done.

Things that I want to point it out:

• Auto save functionality
• Fix of the function that added new classes
• Navigating through items with arrow keys
• Support to images bigger than 1280 X 960
• Refactor
• Thanks

Auto save functionality

To this one I have made an checkable action in the menu “edit”, you can select it if you want to auto save a json or xml file automatically in the current working directory. This functionality can be pretty handy when annotating a big amount of items.

Fix of the function that added new classes

A bit of context, when loading a temporary state or a json/xml file, the marked classes name were duplicate (actually nth-ed) in the combo box that contained them. I am mentioning this one because it made me think a lot, with the help of Caio it turned out to be pretty simple to solve.

Navigation through items with arrow keys

This one is useful too, I got the idea of doing this because, as an user, I wanted navigate through items more easily, so I thought that using the arrow key up and down may be the right choice for the job.

Support to images bigger than 1280 X 960

The annotation for images smaller than these proportions works fine but when bigger it turn it out to be in the wrong place. To solve this one, a bit of math was needed.

Refactor

Refactoring the code can be a lot harder than writing, but it is a must if you are a developer that not only want the code to work as intended but also be maintainable and more likely to get help from another person.

I thought a lot in how to make what I have wrote more understandable and show the intent of the code, although it was improved a lot by Caio later, it was a good experience and for sure I improved as developer.

It is also worth mentioning that we now are focusing in making the API more stable to later improve image annotation and also implement support to text and others data types format as well.

Thanks

I want to say thanks to Tomaz Canabrava, Sandro Andrade and, of course, my mentor in this project Caio Jordão, I have learned a lot with their help during this period and I will continue to contribute to this community and learn more as well.

That is it, see you soon (hopefully in my whoAmI post ; )

Last week saw the by now traditional early February combination of FOSDEM in Brussels, followed by a week-long Plasma Mobile sprint in Berlin.

FOSDEM

This was the 20th anniversary for FOSDEM, I first attended 15 years ago, but this year was the first time I actually managed to present a talk there. The subject was, unsurprisingly, KDE Itinerary. You can find the slides and the video recording on the corresponding FOSDEM talk page.

KDE had a very busy presence at FOSDEM, Plasma Mobile draw a lot of attention, as did efforts for truly free and user-controlled mobile platforms in general. I’m particularly happy seeing the cross-community collaborations going on in that space.

FOSDEM is a great place to connect and coordinate with other communities, and by now that’s probably one of the main reasons for me to attend. The collaboration with Nextcloud on integrating itinerary extraction into Nextcloud Hub started there last year for example.

FOSDEM two years ago saw the first successful flight using a KDE Itinerary rendered boarding pass, this year we had the first ever Thalys ride with a ticket presented in KDE Itinerary. We also made a bit of progress with decoding Thalys binary barcodes, more samples would help a lot here though.

Plasma Mobile Sprint

Following FOSDEM there was a Plasma Mobile sprint in Berlin, this time at the KDAB office. I couldn’t attend the full time, but it was nevertheless useful to move a few topics I’m interested in forward:

• Upgrading our Android build environment to Qt 5.14 and NDK r20. This has been complicated considerably by breaking changes in Qt regarding plug-in and QML loading as well as APK generation and deployment, up to the point where we consider it unfeasible to support Qt 5.14 and older Qt versions at the same time (you’d need different Android manifest files for this, per application). See T12520 and D26749.

• Investigate a fairly fundamental binding loop issue between Qt Quick layout and Text elements with word wrapping enabled. This is responsible for at least half of the layouting glitches all over KDE Itinerary, and so far only partially effective but very dirty workarounds exist. See QTBUG-81707. Thanks to Marco for doing the hard work here!

• It looks like binary factory APKs all use the Qt Quick fallback style, rather than the Material one. This is another fairly basic issue for various UI issues such as the active element in a combo box being invisible or toggle switches showing no visual difference between on and off. There is no generic solution yet, but at least this is easy to fix per application.

• KDE Itinerary finally got a proper icon, thanks to the work of Mathis Brüchert!

KDE Itinerary icon.

• We discussed how to provide a platform abstraction for different intent/content sharing platforms such as Purpose, Content Hub or Android. Having such an abstraction would simplify application development by avoid platform-specific code.

• And of course I had to collect travel documents for improving the itinerary extractor from everyone, the first improvements following from that have already been integrated.

You can help!

Attending events like FOSDEM or meetings like the Plasma Mobile Sprint is extremely productive, and only possible thanks to KDE e.V. and our venue sponsors, something worth supporting if you happen to have access to a suitable venue or happen to have some extra cash :)

It has been more than a year that I had push rights for all the KDE repositories. So this is an obligatory anniversary post. I got introduced to Linux while searching for development environments that came with all sorts of compilers & interpreters by default and I don't have to manually install those stuff.

One of the things that is typical when working with gitlab/github is work with different git remotes.

This is sometimes because you don't have commit access to the original repository so you fork it into your own repository and work over there, but you still want to have the original repository around so you can rebase your changes over it.

In this blog we will see how to do that with the okular repository.

First off, we start by cloning the original repository

Since we don't know the URL by memory, we go to https://invent.kde.org/kde/okular/ and press the Clone button to get a hint, if we have commit access we can use both urls, otherwise we have to use the https one, for the sake of this let's assume we do not have commit access.


$ git clone https://invent.kde.org/kde/okular.git
$ cd okular


Ok, at this point we have clone the upstream Okular repository, we can see we only have one remote, called origin


$ git remote -v
origin https://invent.kde.org/kde/okular.git (fetch)
origin https://invent.kde.org/kde/okular.git (push)


Now we want to do some fixes, since we can't commit into the main repository, we need to fork, for that we press the fork button in https://invent.kde.org/kde/okular/. Once done we end up in the fork of Okular under our name, e.g. https://invent.kde.org/aacid/okular.

Now what we want is to add our remote to the existing one, so we press the blue button (here we use the git@ one since we can always commit to our fork)


$ git remote add aacid_fork git@invent.kde.org:aacid/okular.git
$ git remote -v
aacid_fork git@invent.kde.org:aacid/okular.git (fetch)
aacid_fork git@invent.kde.org:aacid/okular.git (push)
origin https://invent.kde.org/kde/okular.git (fetch)
origin https://invent.kde.org/kde/okular.git (push)


So now we have a remote called aacid_fork that points to url fork, aacid_fork is the name i chose because it's easy to remember, but we could have used any name we wanted there.

Now there's several things one may want to do

Do changes in master and push them to your fork

This is really not the recommended way but since it's what i do and it'll explain how to push from one branch name to another i'll explain it.

After doing the changes and doing the typical git commit now we have to push the changes to our aacid_fork, so we do

git push aacid_fork master:adding_since_to_function

What this does is push the local branch master to the branch named adding_since_to_function of the aacid_fork remote

Create a branch and then push that to your fork

This is what you should be doing, so what you should do is

git branch adding_since_to_function

and then change to work on that branch

git switch adding_since_to_function

After doing the changes and doing the typical git commit now we have to push the changes to our aacid_fork, so we do

git push aacid_fork adding_since_to_function

What this does is push the local branch adding_since_to_function to a branch with the same name of the aacid_fork

Get a branch from someone else's remote and push to it

Sometimes some people say "hey let's work on my branch together", so you need to push not to origin, not to your fork but to someone else's fork.

Let's say you want to work on joliveira's gsoc2019_numberFormat branch, so you would need to add his remote


$ git remote add joliveira_fork git@invent.kde.org:joliveira/okular.git
$ git remote -v
aacid_fork git@invent.kde.org:aacid/okular.git (fetch)
aacid_fork git@invent.kde.org:aacid/okular.git (push)
joliveira_fork git@invent.kde.org:joliveira/okular.git (fetch)
joliveira_fork git@invent.kde.org:joliveira/okular.git (push)
origin https://invent.kde.org/kde/okular.git (fetch)
origin https://invent.kde.org/kde/okular.git (push)


Then we would need to tell git, hey listen, please go and read the branches that remote i just added has

git fetch joliveira_fork

Next we have to tell git to actually give us the gsoc2019_numberFormat branch, there's lots of ways to do that, one that works is

git checkout --track joliveira_fork/gsoc2019_numberFormat

This will create a local gsoc2019_numberFormat from the contents of the remote branch joliveira_fork/gsoc2019_numberFormat and that also "tracks" it, that means that if someone else does changes to it and you do git pull --rebase while on your local gsoc2019_numberFormat, you'll get them.

After doing the changes and doing the typical git commit now we have to push the changes to the joliveira_fork, so we do

git push joliveira_fork gsoc2019_numberFormat

What you don't want to do

Don't push to the master branch of your remote, it's weird, some people do, but it's note really recommended.

Things to remember

A git remote is another repository, it just so happens that it has "similar" code, but it's a fork, so you can push to it, checkout branches from it, etc.

Every time you want to get changes from a remote, remember to git fetch remote_name otherwise you're still on the "old" snapshot form your last fetch.

When git pushing the syntax is git push remote_name local_branch_name:remote_branch_name

Bonus track: Using git mr

As shown in my previous blog post you can use git mr to easy download the code of a mr. Let's use as example Okular's MR #20 https://invent.kde.org/kde/okular/merge_requests/20.

You can simply do git mr 20 and it will create a local branch named mr/20 with the contents of that MR. Unfortunately, if you want to commit changes to it, you still need to use the original remote and branch name name, so if you do some changes, after the git commit you should do

git push joliveira_fork mr/20:gsoc2019_percentFormat

My recent-ish (2019, 2020) talks have been added to the euroquis.nl website.

Some time ago I ran across remark-cmake, a CMake framework for building remark.js-based presentations. Since I’m a sucker for CMake I started using it, even if my presentations are rarely big-and-complicated enough to warrant a build-system.

Since then I’ve submitted a few pull-requests to remark-cmake, but also given eight (8) presentations using that framework at four (4) different conferences in four countries on two continents. Current scheduling suggests that one more continent and at least four more talks will be added before summer.

Generally my slides are just accompaniment to what I’m talking about, and they can be quite short compared to the talk itself. There was a time I tried to stick to one slide per five minutes of talk time. Something I’ve largely dropped now is the “About me” slide, that’s something that will show up in the conference speakers’-biographies page, if anyone cares. And I’ll probably mention Rick Astley, recumbent bicycles and cookies anyway.

But, on the off chance that the slides are useful to someone else, or you want to know about the kind of things I’m talking about, I’ve plunked them down on my website under presentations. The one I’m proud of is Hey guys, this conference is for everyone because it was spur-of-the-moment and the talk itself was full of other cultural-differences issues that were relevant to an international and diverse audience, and I learned things while on stage because Nuritzi corrected me from the front row.

It is available at the usual place https://community.kde.org/Schedules/release_service/20.04_Release_Schedule

Dependency freeze is in ~five weeks (March12) and Feature Freeze a week after that, make sure you start finishing your stuff!

Just a friendly reminder that the Call for Papers for foss-north 2020 is closing tonight. Make sure to get your talk submission in!

Also – if your project wants to join the community day – let us know at info -at- foss-north.se. We set up a venue and promote – you bring the contents!

Starting with the upcoming 20.04 release (or current master branch builds), Kate allows the user to turn on some telemetry submission. This is a purely opt-in approach. We will not submit any data if you not actively enable this feature!

Like Plasma we use the KUserFeedback framework for this task.

For details about how we handle the data, refer to KDE’s Applications Privacy Policy and specifically the Telemetry Policy.

We documented what kind of info we submit on the Telemetry Use page.

At the moment we collect maximal this information:

• Application version: to know which application versions are still in use
• Qt version: to know the underlying Qt version (e.g. to see how important workarounds for old issues are)
• Platform information: to know the operating system we are running on
• Screen parameters: to find out how common multi-screen usage is
• Start count: to find out how frequent users use our editor
• Usage time: to find out how many users are using the software heavily vs in passing

If you want to review the code that was used to add this, take a look at our merge request for the initial addition of this feature.

If you spot errors in the code, please inform us, either via mail to kwrite-devel@kde.org or via a bug report at bugs.kde.org.

I myself activated now the telemetry submission for my installations of the master branch version, this is possible via the Settings -> Configure Kate… -> User Feedback dialog page.

I encourage you to do the same, if you want to provide us feedback which Kate versions are out in the wild and a bit about how often and long they are used.

In the future we might add some hint somewhere in the UI to ask once to take a look at the telemetry config page in a non-intrusive way. As we still need to think about how to do this in the least annoying way, at the moment no such hint is given at all.

I hope our very conservative approach to this shows that we value the privacy of our users and are not branded as “yet another spyware application” or get plenty of “Kate editor spies on users” stories.

Elisa is a music player developed by the KDE community that strives to be simple and nice to use. We also recognize that we need a flexible product to account for the different workflows and use-cases of our users.

We focus on a very good integration with the Plasma desktop of the KDE community without compromising the support for other platforms (other Linux desktop environments, Windows and Android).

We are creating a reliable product that is a joy to use and respects our users privacy. As such, we will prefer to support online services where users are in control of their data.

I am very happy to announce that Elisa has been published on the Windows Store.

The challenge now is to be able to attract users and improve the support for the Windows platform. You can get it there.

The most important issue is to add support for the Windows APIs that allow to search files faster. That would allow a speed up in music discovery like Baloo allows us to do it on Plasma desktops.

If you want to help us, you are very much welcome to contribute (code, design, bug triaging, promo, …). Get involved in the KDE community. You can also find specific information on Elisa.

All this would not be possible without the KDE community. I would like to encourage people to donate to KDE to keep this possible in the future.

You can also support my work on the Patreon, Liberapay and Paypal platforms.

 

Edit: added a direct link to the store page.

You only need to wait two more days for Plasma 5.18! We’re working overtime to get it in great shape for the release and already looking forward towards 5.19, which promises to be another very exciting release. Have a look-see:

New Features

• The Samba status page in Info Center has been completely rewritten and now actually works (Harald Sitter, Plasma 5.18.0):
  
• The System Settings Default Applications page has been completely rewritten to have a radically better and more comprehensible user interface (Méven Car, Plasma 5.19.0):

  And yes, we’re aware that these comboboxes should all have the same width

• Info Center now shows information about your graphics hardware (Harald Sitter, Plasma 5.19.0):
  

Bugfixes & Performance Improvements

• Elisa no longer lets you set up a radio station source with an invalid URL (Matthieu Gallien, Elisa 20.04.0)
• The System Settings Fonts page now enables its “Apply” button at the correct times, so it’s usable again (Benjamin Port, Plasma 5.18.0)
• GTK apps now automatically use the Breeze-GTK theme by default unless the distro overrides it (Mikhail Zolotukhin, Plasma 5.18.0)
• App windows now resize much faster and more smoothly (Vlad Zahorodnii, Plasma 5.18.0):
  
• The System Settings Removable Devices page no longer shows Snap app mount points (Méven Car, Plasma 5.18.0)
• The System Tray popup no longer sometimes shows blank items (Konrad Materka, Plasma 5.18.0)
• When dragging a file to the bottom-right corner of the desktop, the context menu that appears is now positioned correctly (Tranter Madi, Plasma 5.19.0)
• The correct drag cursor is now used when performing drag-and-drop operations on Wayland (Marco Martin, Plasma 5.19.0)
• Fixed a severe memory leak in apps (like Dolphin) that use the KUrlNavigator component, which could potentially result in gigabytes of wasted memory (Fabian Vogt, Frameworks 5.68)
• Canceling a file transfer operation now results in the operation actually stopping immediately, with no residual clean-up processes being left behind that can cause errors later (Méven Car, Frameworks 5.68)

User Interface Improvements

• Improved the margins and fonts of Elisa’s grid and list view items (Alexander Stippich, Elisa 20.04.0)
• The first time System Settings is opened, its main window no longer jarringly resizes itself to be larger after half a second; instead it just opens at the correct size (Marco Martin, Plasma 5.18.0)
• Discover no longer percent-encodes any HTML-unsafe characters in search terms; instead it just removes any HTML tags that were accidentally included in the search (me: Nate Graham, Plasma 5.18.1):
  
• The fancy new “Get New [stuff]” window that you’ll see throughout Plasma 5.18 no longer has an ugly white bar at the bottom, now has a more sensible default size, and its close button always has text (Dan Leinir Turthra Jensen, Frameworks 5.67):
  
• Improved some commonly confusing terms in various KDE apps: “Redisplay” is now “Refresh” and “AutoSkip” is now “Skip All” (me: Nate Graham, Frameworks 5.68)

How You Can Help

Upgrade to Plasma 5.18 and find all the bugs we missed! The first point release (i.e. Plasma 5.18.1) will be released a week after launch day, so every bug report we get during that week is super important.

More generally, have a look at https://community.kde.org/Get_Involved and find out more ways to help be part of a project that really matters. Each contributor makes a huge difference in KDE; you are not a number or a cog in a machine! You don’t have to already be a programmer, either. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!

Finally, consider making a tax-deductible donation to the KDE e.V. foundation.

View the Website under work here.

Week 3 Overview

• Improved CSS on all pages using Bootstrap instead of Hard Coding
• Updated the Wordings on The Get-Involved Page
• Added Links

First of all sorry for the late overview of week 3. The week had been quite busy with other stuff in life and I was not able to find time to write this blog post till now. Week 3 had only some small work to be done as the project was reaching its final outcome.

The Website can be viewed here.

You can check out my proposal here. The repository that has the KDE Jekyll themed site is here.

I started off by improving the CSS on pages by changing from hard coded values to Bootstrap classes after the opinion from my mentor Carl Schwan. The wordings on the Get-Involved page were also updated with a lot of help from Mr.Philip from KDE Developers Telegram. Thanks a lot to him the get-involved page sounds great now.

All the missings links were also added. Since the week was busy for me, I did some more small works here and there and it got over quick.

While, I am writing this, I have also finished Week 4 and it is great and its the final outcome. Don’t forget to checkout the website. So with that I conclude this post. See you in the next one. “Happy KDEing!!”

The final website is up! The official one. here.

Week 4 Overview

• Made changes that were requested on Connect devel Telegram
• The final Website is up on the official link.

This is the overview of Week 4. This week marks the end of the SOK Project to develop KDE Connect Website. This week started of by moving the repository to the Websites Section at finally bringing it online officially at here. After the website went live more changes were suggested on the KDE Connect Developer Chats. I was happy to implement these changes as I think they were great opinions.

I am happy with the final version of the website and I am planning to contribute more to this community in the future. See you in the next Blog Post. Happy KDE’ing!!.

The Elisa music player is now in the Windows Store, too!

It is the sixth application published there with the KDE e.V. account.

And here are our current number of acquisitions (roughly equal to the number of installations, not mere downloads) for our applications:

• Kate - Advanced Text Editor - 23,524 acquisitions

• Okular - More than a reader - 16,154 acquisitions

• Filelight - Disk Usage Visualizer - 1,412 acquisitions

• KStars - Astronomy Software - 1,400 acquisitions

• Kile - A user-friendly TeX/LaTeX editor - 1,343 acquisitions

• Elisa - Modern Music Player - 40 acquisitions

If you want to help to bring more stuff KDE develops on Windows, we have some meta Phabricator task were you can show up and tell for which parts you want to do work on.

A guide how to submit stuff later can be found on our blog.

I hope the number of applications will grow further in the near future ;=)

Thanks to all the people that help out with submissions & updates & fixes!

Some bits and bobs from the KDE FreeBSD team in february 2020.

We met at the FreeBSD devsummit before FOSDEM, along with other FreeBSD people. Plans were made, schemes were forged, and Groff the Goat was introduced to some new people.

The big ticket things:

• Frameworks are at 5.66
• Plasma is at 5.17.5 (the beta 5.18 hasn’t been tried)
• KDE release service has landed 19.12.2 (same day it was released)

Developer-centric:

• KDevelop is at 5.5.0
• KUserfeedback landed its 1.0.0 release
• CMake is 3.16.3

Applications:

• Musescore is at 3.4.2
• Elisa now part of the KDE release service updates

Future work:

• KIO-Fuse probably needs extra real-world testing on FreeBSD. I don’t have that kind of mounts (just NFS in /etc/fstab) so I’m not the target audience.
• KTextEditor is missing .editorconfig support. That can come in with the next frameworks update, when consumers update anyway. Chasing it in an intermediate release is a bit problematic because it does require some rebuilds of consumers.

Honestly, you don't want to know the number of bugs in our bug tracker at this point. But I assure you these are just our broken unit tests rather than bugs.