Re: March/April KDE PIM summary blog post

=== Calendaring ===

* Kalendar and KOrganizer now use the same unified reminder daemon, replacing 
the previous app-specific implementations.

=== KOrganizer ===

* Fix the the progress indicator in the todo tree view being rendered 
vertically.

=== Kalendar ===

* There's is an ongoing effort to refactor and move around commonly used 
calendaring code with the goal to reduce Kalendar's dependencies, and in 
particular any remaining widget-based UI code paths that aren't well suited 
for mobile use.

=== Itinerary ===

There's a dedicated post with status updates here: https://volkerkrause.eu/
2022/04/02/kde-itinerary-february-march-2022.html

In very recent news, we are unfortunately no longer able to publish updates in 
the Google Play store, due to KDE Itinerary being able to store health 
certificates. New rules by Google do not allow such a feature unless you are a 
government or public health entity. The only way around that would be building 
a separate version just for the Play store with that feature as well as any 
references to it in the application metadata removed. That's something our 
build and deployment pipeline doesn't support at this point though. KDE 
Itinerary in the Play store will be therefore be stuck at 21.12.3 for the 
foreseeable future, for continuing to receive updates we recommend [KDE's F-
Droid repositories](https://community.kde.org/Android/FDroid) instead.

=== KMail ===

* Fix travel information extraction for certain combinations of email and text 
codecs used in Asia.


On Monday, 25 April 2022 17:02:43 CEST Volker Krause wrote:
> Hello everyone,
> 
> it's time for the bi-monthly blog post again :)
> 
> If you have contributed in March or April, a summary of your most
> noteworthy changes would be helpful, bonus points for corresponding
> screenshots or links to already existing blog posts. If you noticed
> something noteworthy during the past two months, feel free to add that as
> well of course!
> 
> To help refresh your memories and to make sure we aren't missing anything
> important, there's two files attached here, an auto-generated detailed
> changelog (this tends to be 30-50% of the commits, using David F's changelog
> scripts for KF5 releases), and basic commit stats for the PIM repositories.
> 
> Secondly, we need help with compiling, editing and eventually publishing the
> blog post. Ideally this rotates between a number of people so that everyone
> has to do that only once per year or so.
> 
> Sandro did the last one
> (https://blog.sandroknauss.de/kde-pim-Januar-februar-2022/), who wants to
> do this one?
> 
> Thanks for you help!
> Volker

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQQAnu3FVHA48KjZ07R/lszWTRLSRwUCYmo6fwAKCRB/lszWTRLS
R+r4AJ4s3q6zjNrifEWySr37pbu7fAdXXwCgrgk34aJvfZ5cxC/L/uaEYIeOl4s=
=2Oz5
-----END PGP SIGNATURE-----