Akademy/2024/PIM BoF: Difference between revisions
(Created page with "== Agenda == * Presenting the milestones initiative * Discussion topic: what are the biggest barriers and obstacles when contributing to PIM == Notes ==") |
(→Notes) |
||
| Line 5: | Line 5: | ||
== Notes == | == Notes == | ||
* Dan presented the milestone-based project planning from the PIM spint in Toulouse. | |||
* KMime being made ready for KF, progressing but could use more review | |||
* Questions about the relation between Kleopatra and KGpg: co-existence is mostly historical, slightly different use-cases/priorities, both exist for Qt6 | |||
* QCA deprecation: used by EWS and DKIM. Qt API not enough for this, so needs gcrypt, OpenSSL, libsodium, or Botan. | |||
* EWS: hard to test all scenarios, and upstream plans to retire this in a few years anyway; the QCA part is untestable for us here, this is for public key authentication and largely superseded by OAuth anyway, so remove this as we can't properly port anyway? | |||
* PIM sprint should be more widely announced. Yes, see also the sprint notes (https://community.kde.org/Sprints/PIM/2024), add checklist for sprint prep (also not PIM specific, PIM is just one of the few regular sprints). | |||
* KNotes deprecation: our communication everywhere mentioned the replacement, but some distribution users didn't get that message. Probably not much we can do about that. | |||
* API doc migration from doxygen to qdoc; needs double-checking whether PIM's code-generation macros work; qdoc will not show undocumented functions, that could be a larger problem for PIM and KF! Defer to the API docs BoF on Thursday | |||
* Pending/planned NLnet funding proposals and alignment of those with other ongoing plans. | |||
* Trojita is considered unmaintained at this point. | |||
* Vakzination is currently unneeded it seems (EU-DGC retired in EU, no recent indications of SHC still in active use in the US), but rather than archiving kept in cold storage as the technology in there is expected to be needed again. | |||
* iframe messageviewer change is blocked on printing issues; longer term replacement will be QML/mimetreeparser based but that will take much longer. | |||
* Contribution blocker: too many repos, too strict and new version dependencies; repos are being removed/merged and moved to KF, but the progress is 1-2 repos per year only. | |||
Latest revision as of 13:23, 9 September 2024
Agenda
- Presenting the milestones initiative
- Discussion topic: what are the biggest barriers and obstacles when contributing to PIM
Notes
- Dan presented the milestone-based project planning from the PIM spint in Toulouse.
- KMime being made ready for KF, progressing but could use more review
- Questions about the relation between Kleopatra and KGpg: co-existence is mostly historical, slightly different use-cases/priorities, both exist for Qt6
- QCA deprecation: used by EWS and DKIM. Qt API not enough for this, so needs gcrypt, OpenSSL, libsodium, or Botan.
- EWS: hard to test all scenarios, and upstream plans to retire this in a few years anyway; the QCA part is untestable for us here, this is for public key authentication and largely superseded by OAuth anyway, so remove this as we can't properly port anyway?
- PIM sprint should be more widely announced. Yes, see also the sprint notes (https://community.kde.org/Sprints/PIM/2024), add checklist for sprint prep (also not PIM specific, PIM is just one of the few regular sprints).
- KNotes deprecation: our communication everywhere mentioned the replacement, but some distribution users didn't get that message. Probably not much we can do about that.
- API doc migration from doxygen to qdoc; needs double-checking whether PIM's code-generation macros work; qdoc will not show undocumented functions, that could be a larger problem for PIM and KF! Defer to the API docs BoF on Thursday
- Pending/planned NLnet funding proposals and alignment of those with other ongoing plans.
- Trojita is considered unmaintained at this point.
- Vakzination is currently unneeded it seems (EU-DGC retired in EU, no recent indications of SHC still in active use in the US), but rather than archiving kept in cold storage as the technology in there is expected to be needed again.
- iframe messageviewer change is blocked on printing issues; longer term replacement will be QML/mimetreeparser based but that will take much longer.
- Contribution blocker: too many repos, too strict and new version dependencies; repos are being removed/merged and moved to KF, but the progress is 1-2 repos per year only.