QtPIM and newer Qt releases (e.g. port to 6.10)
-
In Qt 5 times, there was a QtPIM module. It was updated to compile against Qt 6.0 around when that was released -- there are upstream commits from six years ago by Luca setting MODULE_VERSION to 6.0.0. I've been doing some downstream work on the module -- using current Qt 6.10 standards, switching to CMake as a build-system, .. -- which lives vaguely-downstream on KDE Invent.
Does it make sense to try to upstream that? I don't think QtPIM is part of Qt6, so where should development happen?
- In Gerrit, (follow-up question then "so how to get a release out then?")
- In KDE Invent, (but that's more a mirror done by the KDE community)
- Elsewhere (e.g. Codeberg, just fork it already)
-
In Qt 5 times, there was a QtPIM module. It was updated to compile against Qt 6.0 around when that was released -- there are upstream commits from six years ago by Luca setting MODULE_VERSION to 6.0.0. I've been doing some downstream work on the module -- using current Qt 6.10 standards, switching to CMake as a build-system, .. -- which lives vaguely-downstream on KDE Invent.
Does it make sense to try to upstream that? I don't think QtPIM is part of Qt6, so where should development happen?
- In Gerrit, (follow-up question then "so how to get a release out then?")
- In KDE Invent, (but that's more a mirror done by the KDE community)
- Elsewhere (e.g. Codeberg, just fork it already)
@Adriaan-de-Groot Hi and welcome to devnet,
I think it's something that should be discussed on the development mailing list. There are only a few people from the Qt Company following this forum and I think they will be better suited to answer your question.
That said, I think that if the module is still actively used e.g. by KDE, it's worth upstreaming your changes.
If the development happened to be moved, I think that Invent would be the right place since it already hosts quite a lot of Qt related libraries / projects.
If memory serves well, extra modules may have a different release schedule than the official ones although I don't think it happened in practice.
-
In Qt 5 times, there was a QtPIM module. It was updated to compile against Qt 6.0 around when that was released -- there are upstream commits from six years ago by Luca setting MODULE_VERSION to 6.0.0. I've been doing some downstream work on the module -- using current Qt 6.10 standards, switching to CMake as a build-system, .. -- which lives vaguely-downstream on KDE Invent.
Does it make sense to try to upstream that? I don't think QtPIM is part of Qt6, so where should development happen?
- In Gerrit, (follow-up question then "so how to get a release out then?")
- In KDE Invent, (but that's more a mirror done by the KDE community)
- Elsewhere (e.g. Codeberg, just fork it already)
@Adriaan-de-Groot There is already https://github.com/qt/qtpim - or do you want to fork?
-
In Qt 5 times, there was a QtPIM module. It was updated to compile against Qt 6.0 around when that was released -- there are upstream commits from six years ago by Luca setting MODULE_VERSION to 6.0.0. I've been doing some downstream work on the module -- using current Qt 6.10 standards, switching to CMake as a build-system, .. -- which lives vaguely-downstream on KDE Invent.
Does it make sense to try to upstream that? I don't think QtPIM is part of Qt6, so where should development happen?
- In Gerrit, (follow-up question then "so how to get a release out then?")
- In KDE Invent, (but that's more a mirror done by the KDE community)
- Elsewhere (e.g. Codeberg, just fork it already)
@Adriaan-de-Groot Hi and welcome to devnet,
I think it's something that should be discussed on the development mailing list. There are only a few people from the Qt Company following this forum and I think they will be better suited to answer your question.
That said, I think that if the module is still actively used e.g. by KDE, it's worth upstreaming your changes.
If the development happened to be moved, I think that Invent would be the right place since it already hosts quite a lot of Qt related libraries / projects.
If memory serves well, extra modules may have a different release schedule than the official ones although I don't think it happened in practice.
-
A Adriaan de Groot has marked this topic as solved
-
Thanks, I'll take it to the devel-list; while KDE doesn't use QtPIM, Lomiri does, and that is doing a Qt6 conversion-effort.
