Re: September/October KDE PIM summary blog post

--nextPart2757670.ElGaqSPkdT
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Carl Schwan <[email protected]>
To: KDE PIM <[email protected]>
Cc: Claudio Cambra <[email protected]>
Subject: Re: September/October KDE PIM summary blog post
Date: Mon, 28 Oct 2024 18:10:55 +0100
Message-ID: <5017910.LvFx2qVVIh@fedora>
In-Reply-To: <10550702.nUPlyArG6x@vkpc5>
References: <10550702.nUPlyArG6x@vkpc5>
MIME-Version: 1.0

On Friday, October 25, 2024 4:19:08=E2=80=AFPM Central European Standard Ti=
me Volker=20
Krause wrote:
> Hello everyone,
>=20
> it's time for the bi-monthly blog post again :)
>=20
> If you have contributed in the past two months 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!
>=20
> 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 change=
log
> scripts for KF releases), and basic commit stats for the PIM repositories.
>=20
> K=C3=A9vin had signed up to manage this iteration:
> https://invent.kde.org/pim/pim-technical-roadmap/-/issues/69.

## Merkuro

Claudio has been busy fixing regressions and improving the stability of=20
Merkuro. Notably, maps are now displayed again (if the event contains=20
coordinates), the collection combobox in the editors are now initialized wi=
th=20
a valid collection, filtering by name or tag works again, ...

> However, with the rise of the "This Week in KDE Apps" (TWIKA) blog series
> since Akademy, there is now some amount of overlap. TWIKA has the higher
> production value usually, the much higher frequency and presumably higher
> reach, so one option could be to fold the PIM series into that and not
> having a dedicated series anymore at all. If we want to do that we can
> decide to do this now or with one of the future iterations, but I'd sugge=
st
> we do a final post pointing to TWIKA as the continuation in that case.
>=20
> Personally I'd be in favor of doing that (but I'm biased as that would mo=
ve
> work off my plate), it does require a bit more discipline from all of us
> though to basically immediately add noteworthy features to the next TWIKA
> MR.
>=20
> What do you think?

Yes, for Twika I collect the list of changes from the list of merge request=
s=20
closed in the last 7 days. So if you want your changes to be mentioned, mak=
e=20
sure to either create a merge request with your changes or suggest your=20
changes to the merge request for the blog post.

https://invent.kde.org/websites/blogs-kde-org/-/merge_requests/53/
diffs#983daff0bd6fe590c24877c0b6eb4f09a84312eb_0_28

I can't realistically look at the git history of every repos to see if ther=
e=20
is anything worth mentioning myself.

Cheers,
Carl
>=20
> Regards,
> Volker


--nextPart2757670.ElGaqSPkdT
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

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

iQEzBAABCAAdFiEEOf+pPK6cavwhKtACAjJUSCBORSoFAmcfxZ8ACgkQAjJUSCBO
RSpGvgf/fSe2q7XvVVch2J7BynlxAsLlVU/QKFz3l28WpuWerctcE71ooLdtcD6F
MEfwfGeyxs6A0BboDFalsd1n/iZteFU4c4Hms2Qo1X0CjzA5tZv82folxZ5CZZ1C
mfsua7vgAjfnlDblezUDnpVQU13tqmrIbMZaoEb69Po4cZIRr03Nsg/tl8dxxBw8
FQN1JsFbYP352UlXzj9fGWBWQf5U2Q++MXbeE88Y6j9eN4CSvKTZ3+OKvVqNNdZT
f0fg97cmpiLDQbNJfJ4j4eVmtv3400gYmc6VgUSukxAmsi3FKLdcx04rF3Dg0Zb1
MRycURXT8KAJmvZstGtAD5omke2W2Q==
=yF83
-----END PGP SIGNATURE-----

--nextPart2757670.ElGaqSPkdT--