February 16, 2020

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.


De nuevo lo anuncio con un poco de retraso . Fieles a los periodos cuatrimestrales que los propios desarrolladores se han marcado, acaba de ser anunciado el calendario de lanzamientos de KDE Aplicaciones 20.04, el síntoma inequívoco de la continua evolución de la Comunidad KDE y su compromiso por la constancia y mejora continua.

Tener un plan de trabajo pre-establecido es algo fundamental para que los equipos funcionen. Este calendario de trabajo debe contener la respuesta a dos preguntas muy explícitas: qué hay que hacer y cuándo debe estar hecho. Además, en sus aplicaciones internas se responde a otra pregunta que también es sumamente importante: quien lo va a hacer.

Esta metodología de trabajo la tienen perfectamente clara y establecida los desarrolladores de KDE que, como viene siendo habitual, no solo se lo marcan en sus agendas sino que lo hacen público. De hecho, esta entrada es un calco de la que hice hace unos meses con KDE Aplicaciones 19.04.

Calendario de lanzamientos de KDE Aplicaciones 20.04

Calendario de lanzamientos de KDE Aplicaciones 20.04Si tenéis un calendario a mano y tenéis interés en los lanzamientos de KDE Aplicaciones os aconsejo que  anotéis en él las fechas principales de lanzamientos de KDE Aplicaciones 20.04. Hay que destacar que en esta ocasión se ha querido simplificar mucho el proceso en aras de ser más claros y efectivos. En anteriores lanzamientos ha resultado bastante acertado.

De este modo tenemos:

  • Jueves, 12 de Marzp de 2020:  Congelamiento de KDE Aplicaciones 20.04, marcado y lanzamiento de la primera beta
  • Jueves, 2 de Abril de  2020: Marcado y lanzamiento de KDE Aplicaciones 20.04 RC (Versión Candidata)
  • Jueves, 16 de Abril de 2020: Marcado de KDE Aplicaciones 20.04
  • Jueves, 23 de Abril de 2020:  Lanzamiento de KDE Aplicaciones 20.04 definitivo

En fin, un equipo incansable que nos ofrece la colección de aplicaciones más útil, integradas y funcionales para el escritorio libre más bello, funcional y dinámico que puede habitar en tu PC o portátil… y esperemos que pronto en otros dispositivos.

Más información: KDE TechbaseTSDgeos’ blog

 


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

Bugfixes & Performance Improvements

User Interface Improvements

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.


February 15, 2020

Afortunadamente me estoy poniendo al día con los podcast, y uno de los que más me gusta es el de Compilando Podcast. Así que, con conocimiento de causa hoy os quiero recomendar el episodio #48 Resumen 2019 y expectativas 2020 en GNU/Linux y FLOSS de Compilando Podcast, un audio que llega un poco tarde pero como todo lo bueno, llega cuando tiene que llegar.

Resumen 2019 y expectativas 2020 en GNU/Linux y FLOSS en Compilando Podcast #48

En palabras del gran Paco Estrada que sirven de introducción del episodio 48 de Compilando Podcast:

Resumen 2019 y expectativas 2020 en GNU/Linux y FLOSS en Compilando Podcast #48«Primera entrega del 2020 de Compilando Podcast que , con algo de retraso, explora las novedades que nos traerá 2020 y hace balance de lo que ha sido el 2019 en GNU/Linux y el software libre y de código abierto; todo ello en las voces de :

Antonio Larrosa, Lorenzo Carbonell (Atareao), Philippe Lardy, Maribel García Arenas, Juan Febles, Eduardo Collado, Arantxa Serantes, Baltasar Ortega (un servidor), Samuel Iglesias y Jorge Lama.

Todas ellos y ellas, voces autorizadas en diferentes aspectos del FLOSS a los que agradecemos su visión para la audiencia de Compilando Podcast.

Este episodio está dedicado a la memoria de SERGI QUILES PÉREZ , gran linuxero, divulgador y mejor persona y compañero que nos dejó, muy temprano, el pasado mes de Enero. D.E.P

En resumen, un podcast interesante por que es una forma de ver un crisol de proyectos libres que vuelven a demostrar lo viva que está la Comunidad y que nadie puede conocer al 100% todo lo que se crea a su alrededor.

Como siempre os invito a escuchar el podcast completo y compartirlo con vuestro entorno cercano y en vuestras redes sociales.

Más información: #48 Resumen 2019 y expectativas 2020 en GNU/Linux y FLOSS

 

¿Qué es Compilando Podcast?

Dentro del mundo de los audios de Software Libre, que los hay muchos y de calidad, destaca uno por la profesionalidad de la voz que lo lleva, el gran Paco Estrada, y por el mimo con el que está hecho. No es por nada que ganó el Open Awards’18 al mejor medio, un reconocimiento al trabajo realizado por la promoción .

A modo de resumen, Compilando Podcast es un proyecto personal de su locutor Paco Estrada que aúna sus pasiones y que además, nos ofrece una voz prodigiosa y una dicción perfecta.

Más información: Compilando Podcast


February 14, 2020

Con las novedades de las Preferencias del Sistema de Plasma 5.18 LTS doy finalizada la trilogía de estas en el blog. Eso no significa que vayan apareciendo noticias sobre esta buena versión que nos ha ofrecido el equipo de desarrollo de la Comunidad KDE y que pronto empezará sus versiones actualizadas.

Novedades de las Preferencias del Sistema de Plasma 5.18 LTS

Recodemos que Plasma 5.18 LTS fue lanzado el martes, y que tanto el miércoles como el jueves le he dedicado artículos a sus novedades.

Cierro hoy esta serie con las novedades de las Preferencias del Sistema, que nos llega con muchos cambios y con una nueva funcionalidad que merece la pena destacar, la telemetría.

No obstante, antes de empezar con los detalles os sigo recomendando el vídeo de presentación de Plasma 5.18 LTS y, ya que estamos a 14 de febrero, no olvides agradecer a las personas que hacen posible el Software Libre posible su trabajo.

 

Las Preferencias del Sistema

La novedad principal de estas Preferencias del Sistema de Plasma 5.18 radica en la introducción de la famosa y temida telemetría, de la que algún medio como Muy Linux nos hizo un adelanto y que tanta expectación levantó en el mundillo del Software Libre.

La Comunidad KDE ha decidido implementar la posibilidad de que el usuario envíe información sobre su sistema de forma automática y esta nueva funcionalidad ha recibido el nombre de «User Feedback» o «Comentarios de los usuarios».

 

En este punto haz que resaltar que aunque parezca una intromisión a nuestra intimidad es conveniente resaltar que no es ese el objetivo de los desarrolladores de KDE. Las intenciones de la Comunidad KDE es poder recopilar las características técnicas de los equipos en los que los usuarios ejecutan sus entornos de escritorio.

Tanto es así que:

  • Son los usuarios los que deciden compartir su información sobre su instalación. Por defecto no está seleccionado.
  • No se envía información personal ni de navegación. Se puede ver y auditar que ninguno de los parámetros de la telemetría lo solicita.
  • Los usuarios tienen el control del deslizador de las Preferencias de los comentarios del usuario que les permite decidir cuánto le gustaría compartir con los desarrolladores de KDE.

Novedades de las Preferencias del Sistema de Plasma 5.18 LTS #ilovefs

Los desarrolladores insisten en que está información será utilizada para mejorar Plasma aún más y hacer que se adapte mejor a sus necesidades de la gran mayoría de usuarios.

Otros aspectos que han cambiado es la sección de las preferencias del Estilo de las aplicaciones y los Temas Globales (antiguo Look & Feel) con una vista en cuadrícula, con lo que ahora es más sencillo previsualizar cómo se mostrarán las aplicaciones o el escritorio Plasma tras escoger un nuevo estilo.

También se ha añadido una deslizador a la sección de Comportamiento General que controla la velocidad de aparición de las ventanas, desde desesperadamente lento a movimiento instantáneo.

Por último, se ha mejorado la función de búsqueda de las Preferencias del sistema , con lo que encontrar el ajuste del parámetro deseado es más fácil que nunca.

Y hasta aquí las novedades principales de este Plasma 5.18 LTS, una versión que nos ha ofrecido muchas novedades, que en breve (si todo va bien el martes) recibirá su primera actualización y que promete dar muchas alegrías a sus usuarios.

 

Más información: KDE

 


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


I am happy to inform you we have released Qt 5.15 Alpha today.



Celebrate Valentines' Day with some KStars Love! Happy to announce the release of KStars 3.4.0 on February 14th, 2020 on Linux, MacOS, and Windows.

What's new with this release?

The Linear Focus Algorithm.


Hy Murveit continued to work on linear focusing algorithm. This is an alternative auto-focus algorithm available in the Process section of the Focus tab.



You can think of this algorithm as "slow and steady". It should be less sensitive to backlash and measurement noise, but will likely take more samples to achieve its minimum HFR than a successful polynomial search. If you are having issues with auto-focus, you should consider trying this out.

It takes regularly sampled HFR values, i.e. (mostly) moving the position inward by a fixed amount--step size in the 1st pass of the algorithm, and 1/2 step size in the 2nd pass. The polynomial algorithm varies the change in position. Linear rarely changes direction, and mostly moves inward. In its first pass it takes a number of samples inward to establish a V-curve and an approximate minimum-HFR position, then makes a 2nd inward pass looking for that minimum. It only samples the HFR after an inward move. When it needs to move outward, e.g. in between the the 1st and 2nd passes, it moves outward much further than needed, and then moves back in before capturing an image.

The system should be at rough focus before the algorithm starts. The most important parameter is the step size, which needs to be found experimentally. See the screenshot as to how it was chosen (step size = 25) for a Moonlight v2 focuser. Recommend that full-field and the SEP detection algorithm be used with it.

Faster Astrometry.net Solver


Robert Lancaster added an option to use Sextrator as the primary method to identify stars within an image. This has two benefits:

1. It removes the python dependency, which was a painful issue for MacOS users.
2. It vastly improves the solver speed, according to some early reports from our beta testers.



You can turn on the Sextrator option in Astrometry.net settings. 



You can see the astrometry.net solver in now noticeably faster and more reliable than before!

Improvements & Bug Fixes

  • Fixed a few memory allocation issues to reduce the process memory usage.
  • Fixed DSLR ImageToFITS loading when auto convert is used.
  • Fixed focus direction for relative DC focusers.
  • Improved reliability of setting snoop property for the active profile.
  • Fixed File name sanitization issues.
  • Communication with remote INDI Web Manager is now mostly asynchronous.
  • Align property labels in the INDI dialog vertically on top.


In recent decades, Free and open source software (FOSS) has increasingly been the enabling factor for advances in areas we probably aren’t even aware of. If software is still spreading around the world, FOSS had already spread through the software world. All of that is only possible because of striving communities that push solutions forward with an amazing flow of continuous passion and love for nice technology, open knowledge, and supporting people. KDE is not any different - we have all been involved in such a lovely addiction for 23 years.

Today, February 14th 2020, The Free Software Foundation Europe calls everyone to express their gratitude to all FOSS contributors around the world with the eleventh annual “I Love Free Software” campaign. It’s a day when we focus on drawing everyone’s attention to the amazing work done by thousands of FOSS contributors from many communities, most of them voluntarily dedicating their spare time to create high-quality software technology readily and openly available to everyone.

What about you? Have you or your company/university been using Free software lately? Have you already thought about contributing back to that amazing FOSS community that creates the applications you use daily? It’s certainly a very rewarding and inspiring experience, with a lot of contributions made possible by people from different backgrounds.

For now, how about enjoying this day by telling us why you love Free software, or expressing your gratitude to the people behind those projects? Use #ilovefs and #ilovekde tags on your social media to share that picture of you with your favorite Free software T-shirt, or show off all those amazing stickers on your laptop’s lid. Organize a meet-up, submit a bug fix or documentation improvement, make a donation, or just hang out with some friends to celebrate! Everything counts when letting the world know how grateful and passionate we are about Free software.

As nearly all large and experienced Free software communities, KDE is made out of people who strongly believe that enabling everyone to take control of their digital lives can really make a difference. We love being part of this, and that love unfolds into many different actions. We develop almost 200 applications translated to 76 languages plus a full-fledged modern desktop environment (KDE Plasma). We run many contribution sprints around the world in addition to our main yearly gathering (Akademy), where we renew our energy by meeting old and new friends in person. What a lovely way to enjoy our lives!

Today, we invite you to join us in this vibrant flow of gratitude by sharing your FOSS love stories on social media. Use #ilovefs and #ilovekde tags in your posts, so we can find them more easily. We would love to hear about your favorite KDE things.

KDE on Facebook
KDE on Twitter
KDE on Diaspora
KDE on Mastodon
KDE on LinkedIn
KDE on Reddit


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 ; )


February 13, 2020

Did you miss the past Qt World Summit?

Were you there, but you couldn’t attend that talk or two that you really wanted to see because the conference was so, so packed with awesome content?

Fear no more! We are glad to announce that the talks at the past Qt World Summit 2019 in Berlin (or QtWS19, for the friends) have been video recorded and are now available online! You can now catch up with the latest news, improvements and best practices around Qt and its ecosystem, all from the comfort of your sofa office chair.

We have gathered all the talks given by KDAB engineers on this summary page, where you can find also more information about the contents of each talk and download the slides. For your convenience, we have also collected all of KDAB talks in a YouTube playlist:

The talks by other speakers are available for viewing in the Resource Center on www.qt.io.

Happy hacking!

About KDAB

If you like this blog and want to read similar articles, consider subscribing via our RSS feed.

Subscribe to KDAB TV for similar informative short video content.

KDAB provides market leading software consulting and development services and training in Qt, C++ and 3D/OpenGL. Contact us.

The post Qt World Summit 2019 talk videos are online appeared first on KDAB.


February 12, 2020

FOSDEM is one of the world's largest Free software conferences and was held last weekend in Brussels. There were hundreds of talks and videos are available for most of them. KDE had a stall there and KDE contributors delivered three talks spread between different devrooms.

Rendering QML to make videos in Kdenlive

With Akhil Gangadharan Kurungadathil

How QML, a language prominently used for designing UI, could be used to create title video clips containing text and/or images. The videos can then be rendered and composited over other videos in the video-editing process. Kdenlive's Google Summer of Code 2019 project tried to achieve this and is still under active development.

QML is used primarily for UI development in Qt Applications. It provides an easy way of designing and creating interactive, clean and a modern UI. Kdenlive is a popular non-linear open-source video editor and it currently makes use of XML to describe title clips -- clips which contain text or images used to composite over videos. XML requires more processing in the backend as one needs to explicitly write code for, say an animation of the text. Using QML eases this restriction, making the backend more robust and maintainable as rendering in QML makes use of a dedicated Qt Scene Graph. Kdenlive's Google Summer of Code 2019 student Akhil Gangadharan Kurungadathil tried to achieve this by creating a new rendering backend library and a new MLT QML producer which is still under active development. Owing to the dedicated scene graph while rendering, this could also possibly lead to greater overall performance.

KDE on FreeBSD

With Adriaan de Groot

The state of KDE (the Plasma desktop and applications) on FreeBSD, what works, what needs better support lower in the stack. How do we get rid of HAL?

KDE Itinerary

With Volker Krause

A privacy by design travel assistant.


February 11, 2020

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!

New KDE Itinerary icon by 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 :)


KDE’s flagship project Plasma has released 5.18 LTS. That means we’ve crunched the code and ran the QA and slid out the packages and installable images.

Upgrade your KDE neon to get Plasma 5.18. Download the ISOs to install the live images. And to give it a try run the Docker images with neondocker.


As of version 5.14.0 Qt is relocatable, i.e. it is possible to move the Qt installation to a different directory without breaking functionality or loading of plugins.


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.


A brand new version of the Plasma desktop is now available.

In Plasma 5.18 you will find neat new features that make notifications clearer, settings more streamlined and the overall look more attractive. Plasma 5.18 is easier and more fun to use, while at the same time allowing you to be more productive when it is time to work.

Apart from all the cool new stuff, Plasma 5.18 also comes with an LTS status. LTS stands for "Long Term Support". This means 5.18 will be updated and maintained by KDE contributors for the next two years (regular versions are maintained for 4 months). If you are thinking of updating or migrating your school, company or organization to Plasma, this version is your best bet, as you get the most stable version of Plasma *and* all the new features too.

Check out the Official announcement for more details and the full changelog for every single change that went into this version.


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

February 10, 2020

              

In an upcoming release of the Qt Visual Studio Tools, scheduled for this summer, we plan to add support for Visual Studio Linux projects. Since the introduction of the C++ Linux workload, users have had the possibility of working on Linux development in Visual Studio. This feature is of potential interest to Qt developers, given the cross-platform nature of Qt itself, which is why we are now planning to add support for it in the Qt VS Tools extension.

As to how the cross compilation actually works, when building Linux projects in VS, the build process and overall orchestration will rely on either MSVC (MSBuild) or CMake, in the same way as traditional Win32 projects. The build tools themselves will then run in a compilation server, accessible through SSH. For MSVC projects, Visual Studio allows selecting either gcc or clang as the C++ compiler.


February 09, 2020

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.

Screenshot_20200209_161434

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

Bugfixes & Performance Improvements

User Interface Improvements

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.


KDE Connect Website

View the Website under work here.

Week 3 Overview

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!!”


KDE Connect Website

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

Week 4 Overview

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!!.


February 08, 2020

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:

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!


February 07, 2020

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.



Older blog entries