The KItinerary data extraction engine recently got a command line interface, which can be pointed at any file KItinerary can consume (HTML, PDF, plain text, iCal, Apple Wallet passes, etc) and which then outputs JSON-LD according to the schema.org data model with the information that could be found in there. Adding this has been motivated by two separate goals: Increasing extractor robustness, and easing integration into 3rd party applications.
Regarding robustness we have the problem that the problem that the extractor when used in an email application is essentially exposed directly to remotely provided (hostile) content. When running in-process accidentally or intentionally corrupt documents might trigger hangs or crashes of the email application. That’s especially a problem for some of the more complex document types we deal with, such as PDF.
An effective way to mitigate this is moving the dangerous operations to a separate process. This way the host application is not only isolated from possible crashes, it also allows us to sandbox the extractor using tools like Bubblewrap or seccomp, to reduce the impact of possible security issues in the extractor or the underlying parsing libraries.
For users of the KItinerary API, such as the KMail plug-in this is straightforward to use:
Besides enabling the out-of-process mode, it’s important to feed raw data rather than pre-parsed documents in, otherwise the dangerous part of the process happens in the host application after all.
Another motivation for having external process for the data extraction is that it provides an easy way to integrate with applications that cannot or do not want to link against KItinerary and its dependencies, or for whom linking would bring in additional complications at this point. The browser integration work is such an example benefiting from this, there we have to deal with unaligned release cycles and two very different technology stacks.
Using the out-of-process extractor of course is not for free. The entire test suite currently needs about 8.5 seconds for extracting almost 600 samples, with out-of-process mode this roughly doubles. Per document that is about 15 and 30 miliseconds respectively, which isn’t all that bad. That is the average over all test samples though, PDFs tend to be more expensive to process than plain text files for example, while the overhead of spawning a new process is largely constant.
But even if the final integration might involve directly linking against the KItinerary stack, the command line interface can be useful for the initial evaluation and for building prototypes. To support this there’s a nightly Flatpak build available in KDE’s Flatpak repo. This is obviously not meant for production deployments, maintained distribution packages based on official releases are better for that. It however allows very fast turnaround times to receive the latest improvements in the extractor engine while still having the convenience of pre-built packages and co-installability.
Trying this is fairly straightforward:
As always, sample data donations are of invaluable help with this work! Of particular interest at the moment would be multi-leg Renfe tickets, as well as those with at least one international destination :)
For contributing in other ways than donating test data please see our Phabricator workboard
for what’s on the todo list, for coordinating work and for collecting ideas. For questions and suggestions, please feel free
to join us on the KDE PIM mailing list or in the
#kontact channel on Freenode or Matrix.
Como comenté recientemente, el pŕoximo sábado 21 de septiembre se va a celebrar el Software Freedom Day 2019, un día muy especial para la Comunidad ya que en él se conmemora el desarrollo de un proyecto que en realidad va mucho más lejos que el simple (o complicado) Software. Cuando publique la entrada esta semana no había ninguna ciudad españoal donde acudir, así que me congratula compartir con vosotros que Barcelona, Granada y Madrid son sede del Software Freedom Day 2019 en España. ¿Quieres conocer más detalles? Sigue leyendo.
Cada mes de septiembre se celebrar el Software Freedom Day, y este 2019 no es una excepción. De esta forma, la organización sin ánimo lucro Software Freedom International coordina los (SFD) Software Freedom Day SFD como un evento global, proporcionando soporte, material de promoción y puntos de colaboración.
El objetivo fundamental de esta celebración es educar al público sobre los beneficios de usar FLOSS de alta calidad en la enseñanza, en el gobierno, en el hogar y en el trabajo — en pocas palabras y resumiendo ¡en todas partes!
Así que tiene la ocasión de asistir a algunos de los eventos que hay programados para el 21 de septiembre y que en España se concretizan en las sede de Albacete, Barcelona y Madrid.
En definitiva, un excelente día para empezar a ser más activo en términos de Software Libre o de seguir siéndolo si ya lo eres.
Así que prepárate para el próximo sábado para ponerte su camiseta especial, mostrar con orgullo las aplicaciones que han hecho otras personas para ti y hablar a todo el mundo de una idea que poco a poco se va imponiendo en nuestra realidad digital, y que sería fantástica si se pudiera trasladar al mundo real.
Más información: Software Freedom Day 2019
Are you using Kubuntu 19.04 Disco Dingo, our current Stable release? Or are you already running our development builds of the upcoming 19.10 Eoan Ermine?
This is a Beta Plasma release, so testers should be aware that bugs and issues may exist.
If you are prepared to test, then…..
Add the PPA and then upgrade
sudo add-apt-repository ppa:kubuntu-ppa/beta && sudo apt update && sudo apt full-upgrade -y
Then reboot. If you cannot reboot from the application launcher,
from the terminal.
In case of issues, testers should be prepare to use ppa-purge to remove the PPA and revert/downgrade packages. This is especially required if you plan to upgrade a Disco system to Eoan when it is released, as Eoan will ship with Plasma 5.16 by default.
Kubuntu is part of the KDE community, so this testing will benefit both Kubuntu as well as upstream KDE Plasma software, which is used by many other distributions too.
* General tests:
– Does plasma desktop start as normal with no apparent regressions over 5.15.5 or 5.16.5?
– General workflow – testers should carry out their normal tasks, using the plasma features they normally do, and test common subsystems such as audio, settings changes, compositing, desktop affects, suspend etc.
* Specific tests:
– Check the changelog:
– Identify items with front/user facing changes capable of specific testing. e.g. “clock combobox instead of tri-state checkbox for 12/24 hour display.”
– Test the ‘fixed’ functionality.
Testing involves some technical set up to do, so while you do not need to be a highly advanced K/Ubuntu user, some proficiently in apt-based package management is advisable.
Testing is very important to the quality of the software Ubuntu and Kubuntu developers package and release.
We need your help to get this important beta release in shape for Kubuntu and the KDE community as a whole.
 – irc://irc.freenode.net/kubuntu-devel
 – https://t.me/kubuntu_support
 – https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Thursday, 19 September 2019.
Today KDE launches the beta release of Plasma 5.17.
We've added a bunch of new features and improvements to KDE's lightweight yet full featured desktop environment.
Plasma's updated web page gives more background on why you should use it on your computer.
System Settings has gained new features to help you manage your fancy Thunderbolt hardware, plus Night Color is now on X11 and a bunch of pages got redesigned to help you get your configuration done easier. Our notifications continue to improve with a new icon and automatic do-not-disturb mode for presentations. Our Breeze GTK theme now provides a better appearance for the Chromium/Chrome web browsers and applies your color scheme to GTK and GNOME apps. The window manager KWin has received many HiDPI and multi-screen improvements, and now supports fractional scaling on Wayland.
You can test the Plasma 5.17 beta for the next three weeks until the final release in mid-October. Give it a whirl with your favorite distribution!
The Plasma 5.17 series is dedicated to our friend Guillermo Amaral. Guillermo was an enthusiastic KDE developer who rightly self described as 'an incredibly handsome multidisciplinary self-taught engineer'. He brought cheer to anyone he met. He lost his battle with cancer last summer but will be remembered as a friend to all he met.
The easiest way to try it out is with a live image booted off a USB disk. Docker images also provide a quick and easy way to test Plasma.
Distributions have created, or are in the process of creating, packages listed on our wiki page.
You can install Plasma 5 directly from source.
You can give us feedback and get updates on our social media channels: Post on Facebook
Share on Twitter
Share on Diaspora
Share on Reddit
Share on YouTube
Share on Mastodon
Share on LinkedIn
Share on PeerTube
Discuss Plasma 5 on the KDE Forums Plasma 5 board.
Your feedback is greatly appreciated.
Una vez finalizado el periodo de mantenimiento de Plasma 5.16 es hora de ir preparando el lanzamiento de la siguiente versión. Es por ello que me complace compartir con vosotros que ha sido lanzada la beta de Plasma 5.17, la próxima versión del escritorio de la Comunidad KDE, para que sea probada y que se reporten los errores que se encuentren. ¡No pierdas la oportunidad de contribuir al desarrollo de Plasma!
Hoy 19 de septiembre ha sido lanzada la beta de Plasma 5.17. En esta tercera versión liberada del 2019, no apta todavía para el usuario domésticos, se ha centrado en hacer todavía más ligero el escritorio sin deja de proporcionar la potencia que lo caracteriza.
Algunas de las novedades más destacada serán:
Y muchas más pequeñas mejoras que hará las delicias de los usuarios de este entorno de trabajo.
Para finalizar comentar que esta versión Plasma 5.17 estará dedicada a Guillermo Amaral, desarrollar entusiata del proyecto KDE que recientemente nos ha dejado y cuyas entradas en su blog fueron leídas por un servidor en su tiempo.
Más información: KDE.org
Todas las tareas dentro del mundo del Software Libre son importantes: desarrollar, traducir, empaquetar, diseñar, promocionar, etc. Pero hay una que se suele pasar por alto y de la que solo nos acordamos cuando las cosas no nos funcionan como debería: buscar errores.
Desde el blog te animo a que tú seas una de las personas responsables del éxito del nuevo lanzamiento de Plasma 5.17 de la Comunidad KDE. Para ello debes participar en la tarea de buscar y reportar errores, algo básico para que los desarrolladores los solucionen para que el despegue del escritorio esté bien pulido. Debéis pensar que en muchas ocasiones los errores existen porque no le han aparecido al grupo de desarrolladores ya que no se han dado las circunstancias para que lo hagan.
Parece que se ha abierto al veda a los iconos estilo Neon para Plasma. Si hace unos mesme pareció curioso el tema Oie Icons y el Epsilon Icons, los cuales destacaban por su simpleza y su semejanza al típico cartel luminoso de neon, hoy toca hablar de Punk Theme, otro tema similar realizado a base de gruesas líneas, colores degradados y muy vistoso.
Cambiar el tema de iconos de un escritorio es una de las formas de personalización casi más completa que puedes realizar sobre tu PC,ya que cambia totalmente el aspecto del mismo a la hora de interaccionar con tus aplicaciones, documentos y servicios.
Para el escritorio Plasma de la Comunidad KDE hay cientos de temas disponibles, y en el blog le hemos dedicado muchos artículos a ir presentando algunos de ellos, pero siempre aparece alguno nuevo o remozado que hace que siempre le volvamos a dedicar una nueva entrada.
De esta forma me complace presentar el tema de iconos Punk Theme un trabajo de rtl88 nos ofrece un pack de iconos estilo neon, con degradados coloridos, simples y divertidos, que hará las delicias de los usuarios minimalistas y que combina a la perfección con temas oscuros.
Punk Theme está disponible en cuatro estilos: Pain, Sweet, Ozone y Gamma, para abarcar el máximo de gustos posibles.
Y como siempre digo, si os gusta el pack de iconos Punk Theme podéis “pagarlo” de muchas formas en la nueva página de KDE Store, que estoy seguro que el desarrollador lo agradecerá: puntúale positivamente, hazle un comentario en la página o realiza una donación. Ayudar al desarrollo del Software Libre también se hace simplemente dando las gracias, ayuda mucho más de lo que os podéis imaginar, recordad la campaña I love Free Software Day 2017 de la Free Software Foundation donde se nos recordaba esta forma tan sencilla de colaborar con el gran proyecto del Software Libre y que en el blog dedicamos un artículo.
Más información: KDE Store
Let's continue where we left off in the first post. We saw an example of a Qt Quick application running on Linux on top of OpenGL and Vulkan. We also saw a Vulkan frame capture in RenderDoc, which is not just an invaluable tool during Qt development work, but can also be useful to anyone who wants to dig deeper and understand better how Qt Quick renders a frame (or for that matter troubleshoot problems in an application's rendering). Now in this post we are going to focus on what Qt 5.14 offers for macOS and Windows.
Quite unsprisingly, running the qt5-cinematic-experience demo with QSG_RHI=1 (and QSG_INFO=1) on macOS 10.13 or 10.14 results in:
While we’re spending quite some time now finalizing the next release of LabPlot which will be announced soon, we continue getting feedback from our users and we try to incorporate as much as possible into the upcoming release.
This feedback usually consists of different discussions around the existing features in LabPlot or features that need to be added in near future, around bugs, etc. Recently we’ve got a somewhat different feedback informing us about the availability of a Chocolatey package for LabPlot.
Chocolatey is an advanced package manager for Windows allowing to manage the installation, configuration, update and uninstallation of applications on Windows.
Installing LabPlot on Windows with chocolatey from the PowerShell is as simple as
C:\> choco install labplot
Similarly, upgrading to a new version is done via
C:\> choco upgrade labplot
I just released version 1.3.0 of SFXR Qt, my Qt port of the SFXR sound effect generator.
There aren't that many new features for end users:
The new file format opens the road to adding new features. I have a few ideas in mind, will see how it goes.
Nevertheless, this release brings several under the hood changes:
That's it, hope you enjoy generating fun sound effects!
Sure. I’m Julius Grels, and “I like to call myself an artist whenever I’m wasted enough”. In all seriousness though, I think I’d describe myself more as a self-taught caricaturist or illustrator. I usually like to take some existing premise from real life or history, e.g. painting a picture of a (famous) person, depicting wildlife, et cetera. I’m also very fond of making comics, music and video games whenever I have the time (if only?).
I’m most definitely a hobbyist, since I haven’t done any professional commissions (apart from some miniscule design work in the past), and what I do for living right now isn’t even remotely connected to art! That said, I’d most certainly would love to work as an illustrator, comic artist, or anything alike! My biggest wish would be to illustrate (and/or write) a children’s book someday.
I’m most comfortable when doing caricatures and comics; in the latter I can also infuse my story-telling abilities, the little there are. I prefer to illustrate living things; people, animals and nature itself. I’m not exactly keen on drawing in-animate objects, though I’m learning to force myself out of this comfort zone. I like to keep things simple and clean, or at least I try my best not to get lost in time-consuming detailing. Guess that’s one argument I can use as to why I prefer using simple black background on most of my works…
I mostly draw (clever, eh?) influence and inspiration from animation, comics and video game art. I’m hesitant to drop any names because I don’t really have role models per se, and I tend to find pretty much any artist’s work interesting and inspiring. I guess as a Finn I could mention Tove Jansson and Mauri Kunnas. Jansson is of course famous for creating the Moomins, but she was also an accomplished artist and writer in her own right. Kunnas is a well-loved artist best known for his children’s books – pretty much every child in Finland has read at least one of his stories. In my opinion he’s also one of the greatest illustrators this country has to offer.
In addition to the aforementioned, I basically inhaled Franco-Belgian comics as a child; I loved reading Astérix, Lucky Luke, Iznogoud and the rest, so artists like Uderzo, Tabary and Tardi have also had a huge influence on me. Whenever possible, I browse through concept art of different video games. Video games are an interesting subject anyway because they not only combine art, design and technology but have to make all three work together even-handedly to create an enjoyable interactive experience.
If we don’t count MS Paint doodles, I think my first real try at digital painting was at elementary school somewhere around the late 90’s where we were introduced to Paint Shop Pro as a part of some “build your own website” -course. We were only able to use mouse for drawing, which was extremely clunky and made me think the whole idea of drawing and painting with a computer was just insane; I’d rather stick to my pencils and brushes, thank you very much. It wasn’t until later when I realised there are equipment specifically made for digital artwork, and once I got my hands on a Wacom tablet, I was sold.
Nothing? I mean, they are completely different working methods, and I still paint traditionally. Nevertheless, I’ve started to slowly leer towards digital painting, since it’s much easier to control your work and you can experiment more without the fear of ruining something irreversibly (especially when it comes to inking comics and other drawings). While it’s arguable whether digital painting is more cost-efficient than traditional methods in the long run, I think it’s at least less painful to start working with; you only need to set up your computer and programs ready, while with traditional painting you need to take out easel, canvas, gesso, colours, brushes, pencils? you get the idea. Furthermore, in my case where I don’t have a separate studio I have to find and clear a space in my apartment to set all that stuff up. Hassle, hassle!
At one point I started to search for open source alternatives for the myriad number of programs I was using, and Krita was a recommendation somewhere to replace Photoshop, with high ratings from users.
I guess I’m still languishing in my first impression, because I haven’t been able to use Krita as much as I have wanted. In any case, my very first impression upon opening the program was a relieved “this looks familiar” sigh, and it was incredibly easy to start using Krita from there on.
Like I mentioned above, I find the interface very easy to use. I also love the fact the community is so alive, and you can find answers to just about any dilemma. All in all, Krita is a magnificent tool for making 2d artwork.
Majority of my problems with Krita are due to the fact I’ve yet to learn most of its nuances, so I can’t really say about improvements that much. Krita seems to be quite a memory-hog, which can cause lot of lag and freezing especially when working with bigger canvases. That, and I’m not too happy with the text tool/editor either and prefer not to use it at all. It’s the one thing in Krita that’s needlessly complicated in my opinion.
Krita is the only digital painting software I use. Being open source is probably what makes it stand out the most. I use other open source programs as well, e.g. Blender, OpenToonz and Aseprite, but they obviously aren’t that much similar to Krita?
Not much to choose from, but nevertheless, I’d say Megantereon, which was my first serious Krita artwork that I actually managed to finish. The main reason why I like it so much is simply because I had no initial planning; I took my Wacom, opened Krita and started doodling “something tiger-like”. After an hour or so, I began to realise there might be more to it, and continued working. The first version had plain fur, simplistic ear and lifeless green eye. I published it on deviantart.com, but wasn’t happy with the result, and later on decided to tweak the cat a bit. The fur got more detailed with stripes and spots, and I completely overhauled both the ear and the eye. The final result is what you see here, and I quickly replaced my previous attempt with this better version. I also like Megantereon as it neatly represents my interests (wildlife, history) and my preferred style (stylized, semi-realistic).
Every brush I used is a Krita default. I used Basic and Fill Circle for outlining and some detail, Bristle Texture and Square for texturing and Inkpens for smaller detailing. There might be some Smudge tool I used too, but I honestly can’t remember.
I made a rough outlining on one layer against a black background and constructed the beast from bones to muscles to fur et cetera from there on. In the end I had laid out 23 layers with such genius descriptions as “skull”, “Layer 17”, “BLOOD SALIVA”, “hideTheBeard” and “washing”. In retrospect, I highly recommend people to use layers more scarcely if possible – they slow down the program, and the whole working process ends up confusing. At least name your layers better than I did!
I have two versions of the final work; with and without Noise Effect, which I used to achieve a more horror-esque vibe. I send the noiseless version here so the details aren’t obstructed too much.
At the moment, my most recent work will be published at https://www.deviantart.com/jgrels . Don’t hold your breath, though; I publish work at a snail’s pace. You can also follow me on Twitter @JuliusGrels if you so desire, where I’m giving more information about my possible future projects, like a couple of webcomics I’ve planned to do.
Maybe just some general advice to any aspiring artist: never stop honing your skills, get out of your comfort zone, don’t fear experimenting, and most importantly; have confidence. Believe in yourself. Even if you don’t think you’re that great of an artist but love doing art, just keep working and publishing your work for everyone to see. You can doubt your talent, but never doubt your passion.
Finally, I want to send my thanks to the Krita Foundation and give my highest appreciation for the great work you’ve done. Thank you!
In my quest to improve the website of KDE, I updated the Plasma Desktop webpage. This is a huge improvement to the old website, which didn’t show any screenshots and didn’t list any Plasma features.
I already teased the improvements I made in the Plasma BoF in Milan to the Akademy.
The redesign got a lot of positive feedback by the Plasma team and after some small modifications the changes landed.
The webpage looks like this now:
If you want to help improving the web presence of KDE, I regularly add some Junior Job to this Phabricator Workboard. Lots of things need to be updated, so don’t hesitate to propose other changes in the kde-www mailing list.
Now that the first beta of Qt 5.14 is getting closer, it is time to start talking about one of the big new features. We cannot possibly cover all the details around the graphics stack improvements and the road to Qt 6 in one post, so in part 1 and 2 we will describe the background and take a closer look at what 5.14 will ship with, and then dive into the technical details and future directions in another set of posts later on.
See, I told you I’d continue to blog about the cool things that have happened in KDE-land.
On that subject… Kate is now available for free on the Microsoft Store! So far the ratings are quite good. KDE has always aspired to make our apps available to as many users as possible, and getting them on today’s distribution platforms continues that.
For those of you who switched from Windows or macOS, think back to how helpful it was that a bunch of your favorite apps (Firefox, Chrome, VLC, LibreOffice, Inkscape, Blender, Krita, etc) were already available on Linux and you already knew how to use them. Getting more of our apps on other platforms is a key part of easing the transition for future generations of switchers.
Beyond that, it’s been a somewhat light week because everybody was off at Akademy planning the future. A lot of really great things got discussed and decided, the results of which should start to trickle into subsequent weeks’ blog posts. So stay tuned!
This is a new section I’m adding to these weekly blog posts, highlighting a new way to get involved every week!
Do you have any web design experience? KDE community members are currently working on redoing the ancient and inconsistent assortment of websites hosted on kde.org, and help is needed! If this sounds like your cup of tea, join the kde-www mailing list and check out the tasks on the Phabricator Workboard.
You can also check out https://community.kde.org/Get_Involved, and find out other ways to help be a part of something that really matters. You don’t have to already be a programmer. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!
After eight densely packed days Akademy 2019 is over. As always it was very nice to meet everyone again, as well as to meet some people I have been working with online for the first time in real life.
There was some interesting feedback for my talks, and overlap with work of others:
The yearly Akademy awards ceremony provided a very unexpected surprise as I was given this year’s Jury Award. Thanks to David for the nice words, and to everyone for signing the award :)
Monday to Friday saw a large number of meetings on a wide range of topics, the BoF wrap-up session videos (Monday, Tuesday, Wednesday/Thursday) provide a good overview on those. The below are my key takeaways from some of the sessions I participated in.
With Qt 6 on the horizon we need to start looking into what we want to achieve with KF6, beyond just porting to Qt 6 and cleaning up obsolete/deprecated API. We now have a Phabricator workboard to collect and discuss plans and tasks around that, and hopefully we’ll have a sprint in the not too distant future to plan this in more detail. If you have issues with or wishes for KDE Frameworks that might require breaking API or ABI, or otherwise require more invasive changes such as moving functionality between libraries, now is the time to bring this up.
More details: David’s summary
The most important goal for me here was to get some more collaboration between the Plasma Mobile team and the currently desktop-focused PIM team going, and it looks like we made progress there :)
The move of KContacts and KCalendarCore to KDE Frameworks also got its final go and should be executed next week. The next module to look at is the KDAV protocol library, which ties in with reviewing the KF5 HTTP stack.
I hosted a session on how to create custom extractors for KItinerary in which we looked at the kinds of data we can encounter, the methods and tools we have available for processing this, as well as on how KItinerary Workbench can help with writing and debugging extractors. As a result there were a few new extractor contributions already.
More details: Slides
Aleix had already addressed my top agenda item before the meeting, the F-Droid repository holding the nightly builds from binary factory is synchronized again correctly and should be distributing continuous updates again.
Other topics included where to put the JNI helpers from KDE Itinerary,
and how to improve packaging with
androiddeployqt for plug-ins with mandatory dependencies.
More details: Notes
More details: Notes
Next to all the meetings and discussions there was of course also some time for more hands-on work. My personal highlight is Kai’s work on KDE Itinerary browser integration, it has come a long way since our initial research on this.
We also managed to collect quite some sample data for improving KDE Itinerary, thanks to everyone who donated their data! Some of the immediate results are Daniele’s work on completing our understanding of the barcodes from Trenitalia, as well as initial support for Renfe tickets thanks to Luca.
A big thanks to everyone who made this event possible, the Kennys, the local team and everyone else who helped, as well as the sponsors and the KDE e.V.! Akademy is immensely valuable, the above is just a tiny glimpse into the productivity we achieve when having everyone together for a week, not to mention the massive motivational boost we get out of this.
The last week I was in Milan with my wife Aiswarya to attend Akademy 2019, the yearly event of the KDE community. Once again it was a great experience, with lots of interesting conferences and productive BoF sessions (“Birds of a Feather”, a common name for a project meeting during a conference).
On Sunday, we presented our talk “GCompris in Kerala, part 2”. First, Aiswarya told some bits of Free-Software history in Kerala, gave examples of how GCompris is used there, and explained her work to localize the new version of GCompris in Malayalam (the language of this Indian state). Then I made a quick report of what happened in GCompris the last 2 years, and talked about the things to come for our next release.
On Monday, I attended the KDE e.V assembly. On a side note, if you are a KDE contributor, you should probably consider joining KDE e.V. as an active member.
On Tuesday morning, we attended the KDE India BoF, where we discussed why the conf.kde.in conference didn’t happen for 2 years and how we can make sure it will happen next year.
On Tuesday afternoon, we had the GCompris BoF. We discussed about using the KDE Wiki for our documentation instead of self-hosting our own wiki. We also discussed the state of some translations that need to be updated. On that topic, if your language is not yet supported in the latest version of GCompris, maybe you can help us (you can check the translation status on this page). Also during this session, Aiswarya started working on some new options to adapt the speed in some activities to make them usable for people with cognitive or physical difficulties.
On Wednesday morning, we attended the “Wayland user feedback” BoF. I discussed with the plasma team about the biggest issues for using Krita on Wayland, namely tablet support and color management. The team seemed very interested to fix those, so I’ll try to provide useful feedback to help them.
On Wednesday afternoon, it was the “Day trip” to the Lake Como, a great occasion to relax and have fun with old and new friends in a beautiful place.
Congratulations to the team for organizing a great event, and also big thanks to KDE e.V. for providing travel support.
“Who are you people?”
That’s what the woman selling the ferry tickets at Varenna asked me once she realized I speaked Italian. She was definitely not used to a group of ~80 people wearing a blue badge. Another woman who was selling stuff on the street asked me if we were a school.
It’s been an amazing week and a very productive Akademy. A lot has been discussed and a lot has been decided. On my side, I’ve hosted a Dolphin BoF where we discussed both boring things (e.g. where to send bugzilla notification mails) as well as the awesome new features we are getting into Dolphin. Alexander talked about the status of the KIO Fuse project, while Méven talked about his work on the kioslave for the recently used files.
On the coding side, I wish I could have done more, but I lost a lot of times fighting with Google bureaucracy which was required to create a new API key for KIO GDrive. We need to urgently sort this out because it is blocking a working Google support in Kontact. Despite that, I managed to write a simple PoC of KUserFeedback usage in Dolphin. KUserFeedback is very easy to use if you just want the basic reportings (OS version, Qt version, and so on.). Hopefully it won’t be too hard to also get more interesting information, such as which are the features that our users use the most.
And finally, a big thanks goes to the Akademy team and the local team for the organization of the event. See you next year!
When test engineers hear about test automation the first word that comes to mind is of course Selenium which is the most popular testing library that helps us writing scripts for web applications. There are also ready solutions for mobile apps like Appium, Robotium, Espresso, UI Automator and others. The challenge is when we have some project-specific technologies that are not as easy to automate as web applications. But while using Qt we have some advantage over other non-web applications because there is some ready solution that we can use.
I attended my first ever Akademy! The event was held at the University of Milano-Bicocca in Milan, Italy this year. And the experience was splendid. During the 2 day conference, I had the opportunity to talk at the Student Showcase, where all of the SoC students presented their work to the community. There were about 8 students, and everyone gave a good briefing on their project.
My project this summer was with Kdenlive, the open source non linear professional video editor. I proposed to revamp one of the frequently used tools in the editor, called the Titler tool, which is used to create title clips. Title clips are video clips that contain text and/or images that are composited or appended to your video (eg: subtitles). The problem with the titler tool as it is, is that it uses QGraphicsView to describe a title clip and QGraphicsView was deprecated since the release of Qt5. This obviously leads to problems - upstream bugs crawling affecting the functionality of the tool and an overall degradation in the ease of maintenance of the codebase. Moreover, adding new features to the existing code base was no easy task and therefore, a complete revamp was something in sights of the developer community in Kdenlive for a long time now. I proposed to rework on the backend for the period of GSoC replacing the use of XML with QML and use a new rendering backend with QQuickRenderControl, along with a new MLT module to handle the QML frames. I was able to cover most of the proposed work, I seek to continue working on it and finish evolving the titler tool.
The folks from Kdenlive have always been very warm and helpful especially with the whole learning curve (which definitely was steep) and working with the community so far has been great, I’ve learned a lot from the experienced developers in Kdenlive and from the Kdenlive community. I seek to continue working with the Kdenlive team and KDE to continue making Kdenlive a great tool to use and a great community to be a part of.
All in all, Akademy was an unforgettable experience, I met a lot of brilliant people from the KDE community in person and the other SoC students from other parts of the world. I’m extremely thankful to the KDE community for presenting us, students, with such a fine opportunity and a platform to work and talk on our projects. Kudos to the Akademy Team for orchestrating such an event!
Here’s my GSoC Work Report: https://community.kde.org/GSoC/2019/StatusReports/AkhilKGangadharan
Wednesday continued the Akademy BoFs, group sessions and hacking in the morning followed by the daytrip in the afternoon to Lake Como, to have some fun, get away from laptops and get to know each other better. Thursday was back to BoFs, meetings and hacking culminating in a wrapup session at the end covering the last two days so that what happened in the different rooms can be shared with everyone including those not present.
Watch Thursday's wrapup session in the video below
Our Windows Store submission succeeded, we are now officially in the store.
Try out how the Kate text editor performs on Windows for your personal workflow.
If you see issues and want to help out, contributions are welcome on our GitLab instance.
Our Windows team is small, any help is very welcome! Thanks again to all the people that made it possible to use Kate nicely on Windows.
A few Kubuntu Members (and Councillors!) met Thursday before KDE Akademy’s end. We discussed the coming release (will be 19.10) and the upcoming LTS (20.10) – which will be Plasma LTS *and* Qt LTS. This combination will make this LTS super-supported and stable.
We also discussed snaps and when Ubuntu possibly moves to “all snaps all the time” for applications at least. This may be in our future, so it is worth thinking and discussing.
Tobias Fischbach came by the BOF and told us about Limux which is based on Kubuntu. This has been the official computer distribution of Munich for the past few years. Now however, unless the Mayor changes (or changes his mind) the city is moving to Windows again, which will be unfortunate for the City.
Slightly off-topic but relevent is that KDE neon will be moving to 20.04 base soon after release, but they will not stay on the Plasma LTS or Qt LTS. So users who want the very latest in KDE Plasma and applications will continue to have the option of using Neon, while our users, who expect more testing and stability can choose between the LTS for the ultimate in stability and our interim releases for newer Plasma and applications.
Of course we continue to ask for those of our users who want to help the Kubuntu project to volunteer, especially to test. We’ll soon need testers for the upcoming Eoan, which will become 19.10. Drop into the development IRC channel: #kubuntu-devel on freenode, or subscribe to the Kubuntu Development list: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Since a few years Kate is working well on Windows. You can grab fresh installers since then from our download page.
But the visibility of it was very low for Windows users.
Like always, Akademy is a great chance to get the last bits ironed out and the stuff done!
Now, thanks to the help of Hannah von Reth and others, we finally got Kate submitted to the Windows Store!
The submission still needs to be processed by Microsoft, stay tuned when our nifty editor will really be available there for download!
Thanks to all people that contributed to this!
Following Volker's last blog on this topic, here are some highlights of the recent work that has been done around Kontact / PIM during this summer. First of all, stats: there were around 1200 commits in the past two months, leading to the new 19.08 release.
You can have a good overview of Volker's work by following this blog.
It seems our team was mostly focused on cleaning, fixing and introducing little UI features during summer:
Laurent added folder specific exportation from PIM within its PIM data exporter, contact selection from LDAP servers, refactoring some PIM libraries to new ECM macros and cleaned up deprecated method preparing for a Qt 6 future.
In addition to that some bug fixes got in, most notably adding reminders to new events in KOrganizer, text-to-speech fixes and general KMail behavior corrections.
Reminders to new events in Korganizer:
Choosing a contact from LDAP server :
All of the libraries have been adapted to compile with Qt 5.13 and soonish we should reach 5.14 compilation state.
Volker spent time unifying instant message address storage in vCards to KContacts, KContacts soon to be its own framework. The visual style for inline messages in KMail's message viewer was updated too, following the Breeze style as you can see in the picture.
Visuals for inline message boxes in the mail view :
Sandro Knauß worked on the begining of an implementation for MemoryHole support : the idea is to encrypt the mail header (containing metadata) to enforce even further user privacy. In order to achieve that, they wrote a new interface between MimeTreeParser and MessageViewer so we now can update mail headers for later extraction, stay tune for more deails about that next blog posts. In addition and with the help of Glen Ditchfield they put their effort on making messagelib tests green again!
David Faure ported the all of KDE PIM to D-Bus activation as a way to start applications, which enabled the deprecation of KDBusServiceTrader and maybe in a long term future a refactor to simplify KLauncher.
Dan worked on a better support of PostgreSQL (better handling of table name case sensitivity and the sorting of versioned directories). Akonadi server received some love with a few cleanup and modernization treats, you will have more detail about what Dan cooked in his kitchen in his blog so stay tuned!
Volker and Laurent made sure all KDE PIM modules would appear correctly under the api.kde.org, to make the KDE PIM codebase easier to follow and discover.
Help us make Kontact even better!
All these efforts to provide good free software to the world would not be possible without our committers, if you want to take part on that feel free to contact us #kontact and #akonadi IRC channels on Freenode, see the below section to get started:
And again, if you are attending Akademy, feel free to come see us !
This is a guest post from Franck Arrecot due to technical issues with his blog.
Thanks Franck for writing up the above!
According to the now traditional schedule, Akademy 2019 started with two days of conference talks. Hosted by unixMIB at the University of Milano-Bicocca in Milan, Italy, the central conference of the KDE community attracted more than a hundred attendees during this past weekend. Many of them were attending Akademy for the first time ever, which is always a reason to celebrate.
For those of you who were not able to join us, we've prepared a recap of all the talks from this year's Akademy. The conference program on both Saturday and Sunday was split into two tracks after the lunch break, and included plenty of time for socializing (and hacking!) in between.
Akademy 2019 started in the morning of September 7 with an introductory session by Lydia Pintscher, President of KDE e.V., followed by the first keynote. In the keynote, Lars Knoll from Qt presented the path towards Qt 6 all the way from the very beginning of the project. Lars also spoke of what upcoming changes in Qt 6 may potentially impact the KDE ecosystem.
The next batch of talks was dedicated to the KDE community goals. Ivan Čukić started by presenting the progress of the Privacy and Security goal in his talk "Everything to hide: Helping protect the privacy of our users". Ivan pointed out that security and privacy should come before usability, even if some users hate it, because it's our duty and responsibility to protect them.
Eike Hein talked about the Usability and Productivity goal and wondered: "Are we there yet?". Massive improvements have been made to KDE software as part of this goal, and Eike emphasized the importance of communicating this progress (as illustrated in weekly blog posts by Nate Graham). The achievements of the third community goal - Onboarding New Contributors - were presented by Neofytos Kolokotronis, who listed the adoption of Matrix as a communication tool, the on-going adoption of GitLab, and the creation of the KDE Welcome team as some of the major moments.
After looking back at the previous set of goals, it was time to look forward to the new ones. During the panel with Ivan Čukić, Eike Hein, and Neofytos Kolokotronis, Lydia Pintscher announced the three new goals that the KDE community is going to focus on. The creators of the goal proposals spent some time talking about their plans and tasks that will kick off the new goals.
In the afternoon round of quick talks, Adriaan de Groot presented QuatBot, a meeting-managing bot he wrote for the Matrix IM service, and talked about the power and versatility of KDE Frameworks. Attendees also got a chance to hear how Carl Schwan brought in new contributors from Reddit and Aleix Pol dispensing valuable advice on how to organize a sprint.
Over in the Security track, Albert Astals talked about the cool ways developers can use oss-fuzz to test their code, and encouraged KDE developers to use it for projects such as Baloo, kfilemetadata, and PIM-related code. Volker Krause presented parts of the work carried out for the Privacy goal in his talk "Secure HTTP Usage", and warned about the importance of having secure defaults in KDE software.
The Community session included a talk on building developer portals by Ivana Isadora Devcic, followed by Ray Paik's talk on making a difference in the community. As a Community Manager at GitLab, Ray shared his experience with identifying crucial community metrics, attracting new contributors, and improving leadership and inclusivity efforts.
Meanwhile, the tech talk session continued with Marco Martin and Bhushan Shah discussing the future of Plasma on embedded devices. They rightfully pointed out that the assumption your software will only be used on a desktop is not true anymore, and explained how KDE Frameworks enable creating software for different platforms. Aleix Pol talked about the details of optimizing Plasma to run fast on low-end hardware; more specifically, on the Pinebook. Aditya Mehra presented a demo of Plasma and Mycroft being used to voice-control a car, and Kai Uwe Broulik gave an in-depth look into the overhauled notification system shipped with the latest version of Plasma.
The first day of Akademy 2019 closed with reports by Google Summer of Code students developing fresh new code for KDE, and the KDE e.V. Board and Working Group reports that provided an insight into growth and health of the KDE community.
The second day of Akademy 2019 opened with a keynote "Developers Italia and the New Guidelines: Let the Open Source Revolution Start" by Leonardo Favario from the Team Digitale IT. Leonardo presented the work that his team has been doing to establish guidelines for Free and open source software distribution in the Italian administration. Continuing on a similar topic, Michiel Leenaars talked about NGIO (Next Generation Internet Zero); a EU initiative focused on helping non-profit organizations build a better Internet for everyone.
The tech talks on Sunday were fascinating, with new, innovative technology introduced left and right. Cristoph Haag explained how Collabora made Plasma desktop usable in a Virtual Reality environment, and set up demos that the attendees could play with during the day. Trung Thanh Dinh showed how AI face recognition can be used in digiKam, KDE's photo management app, and Eike Hein presented a completely new KDE application called Kirogi, which provides a FLOSS ground control for consumer drones that works on mobile devices.
In the afternoon sessions, Katarina Behrens from the Document Foundation talked about integrating LibreOffice products with KDE Plasma, while Timothée Giet and Aiswarya Kaitheri Kandoth told the story of how a single floppy disk with LaTeX on it resulted in schools using GNU/Linux and GCompris in Kerala, India.
Volker Krause gave two more talks - one about the development and usage of KPublicTransport, a framework for interacting with data from public transport operators; and another on how the limitations of the Android development platform impact KDE Frameworks. In another developer-oriented talk, Daniel Vràtil gave his perspective on using C++ to build APIs. Attendees also heard from Caio Jordao Carvalho, who presented the progress on kpmcore, the heart of KDE's partitioning and disk management tools.
Meanwhile, a session on different ways to package and distribute KDE software was chaired by Dan Leinir Turthra Jensen, with participants explaining advantages and shortcomings of different solutions (AppImage, Flatpak, Snap, Steam, Google Play...).
The session was followed by two community-related talks. In "What We Do in the Promos", Paul Brown gave a realistic look into how people outside the FOSS bubble perceive (or do not perceive) KDE software, and explained the reasoning behind activities carried out by KDE Promo. Afterwards, Aniketh Girish explained how code reviews can be toxic and put off new contributors, so he offered some advice to prevent that. Last but not least, Dan Leinir Turthra Jensen presented the "Get Hot New Stuff" project and its development.
Following the lightning talks from Akademy 2019 sponsors, the second day of the conference closed with the announcement of Akademy Awards winners:
Akademy 2019 continues this week with daily BoF (Birds of a Feather) sessions, meetings, and various activities that help us strengthen the community bonds. The recap video of the first BoF day is already available - stay tuned for more. And for something completely different, take a look at the sketchnotes from Akademy 2019 talks by Kevin Ottens.
For most of the year, KDE - one of the largest free and open software communities in the world - works online by email, IRC, forums and mailing lists. Akademy provides all KDE contributors the opportunity to meet in person to foster social bonds, work on concrete technology issues, consider new ideas, and reinforce the innovative, dynamic culture of KDE. Akademy brings together artists, designers, developers, translators, users, writers, sponsors and many other types of KDE contributors to celebrate the achievements of the past year and help determine the direction for the next year. Hands-on sessions offer the opportunity for intense work bringing those plans to reality. The KDE community welcomes companies building on KDE technology, and those that are looking for opportunities. For more information, please contact the Akademy Team.
Tuesday continued the Akademy BoFs, group sessions and hacking. There is a wrapup session at the end of the day so that what happened in the different rooms can be shared with everyone including those not present.
Watch Tuesday's wrapup session in the video below
The OpenForum Academy held its second 2019 workshop in Brussels this week. OpenForum Academy is a European-based independent think tank which explains the merits of openness in computing to policy makers, industry and communities across Europe. This workshop series aims at being a forum for practitioners, academics and policy makers to collaborate on various topics of openness and freedom. It is organized by OpenForum Europe, enabling it to bridge between the abstract academic world and policy discussions at the European Commissions. We set out to explore focus topics to answer current challenges to openness that the academy will develop insights and recommendations for. These topics will shape the work of OpenForum Academy for the near future.
A bit later than expected, because of a regression found during beta testing, we’re releasing Krita 4.2.6. Over 120 people have participated in the beta test survey, so this is something we’ll repeat for the next release.
This release also contains an important workaround for users with an AMD Ryzen 5 3500 CPU. This CPU has a bug in its hardware random generator that caused crashes.
We want to especially thank Karl Ove Hufthammer for his extensive work on polishing the translatable string.
Note for Windows users: if you encounter crashes, please follow these instructions to use the debug symbols so we can figure out where Krita crashes.
(If, for some reason, Firefox thinks it needs to load this as text: to download, right-click on the link.)
Note: the gmic-qt is not available on OSX.
For all downloads:
Krita is a free and open source project. Please consider supporting the project with donations or by buying training videos or the artbook! With your support, we can keep the core team working on Krita full-time.