[Development] Reviving QtPIM

[Adriaan de Groot]

QtPIM development stopped in 2020 -- Luca Weiss bumped the module version to 
6.0.0, but it was never, AFAIK, part of any Qt 6 release. It also never was 
updated with CMake as a build-system.

There are consumers of QtPIM, though. Lomiri, a Free Software convergent 
software stack (think tablets, phones, and desktop), uses it. There's an effort 
going on to update that to Qt 6, which would include QtPIM.

I have dealt with the build-system and porting to Qt6, such that it builds and 
passes autotests. I haven't dealt with the QML, yet -- I presume that will 
need more work as the language itself changed a bit. That work happened on KDE 
Invent, because (a) there's a mirror there due to the KDE Free Qt Foundation 
work and KDE Free Qt Patch collection work -- that was relevant at the tail 
end of the Qt5 era -- and (b) that GitLab instance supports personal work-
branches even in mirrored repositories. The mirror is, however, supposed to 
just mirror upstream.

But it leaves me (and Lomiri) in a weird situation: there's work being done, 
and it is sort-of-upstreamable, but I can't point at an upstream and say "it 
goes there" because Qt hasn't done a release of this in years.

So what should I do here? I can throw things at Gerrit, but that only makes 
sense if this ends up in a releasable state eventually (I'd be personally 
satisfied it it was releaseable on common Free Software platforms, and don't 
care about esoteric ones ..). It could be hard-forked with the same name and a 
different "upstream", or renamed. I'm open to suggestions.

[ade]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20260514/36c05f08/attachment.sig>