Re: March/April KDE PIM summary blog post

Volker Krause <[email protected]>
Newsgroups gmane.comp.kde.devel.pim
Organization KDE
Message-ID <5588407.DvuYhMxLoT@vkpc19>
That's quite some material already, I'll try to assemble that into a post 
tomorrow.

I'd still have two wishes though:
- Ingo, any chance we can get a summary of the Kleopatra work? Quite a few 
things happened there again.
- Does anyone have some vaguely related screenshots? So far this is just a big 
wall of text.

Thank you!
Volker

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
signature.asc (application/pgp-signature, 195 B)
-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQQAnu3FVHA48KjZ07R/lszWTRLSRwUCYm65sQAKCRB/lszWTRLS
R3xXAJ48rUfnKvNKCp6nLG411g6tP63uGQCfX8+DFWU4wTax25p5XaPkcXy+C+g=
=1+Te
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.