All the things we need for a basic mail client.
Jul 3 2017
Apr 13 2017
Mar 3 2017
Mar 2 2017
KIMAP2 is done for the time being, release is tagged and pending the release announcement for which we have a ticket.
Tarballs are created and uploaded like this (sha256 for sysadmins):
$ git archive --format=tar.xz --prefix=kasync-0.1.0/ v0.1.0 > kasync-0.1.0.tar.xz $ sha256sum kasync-0.1.0.tar.xz 7cc451662fcf5c2f67cbebdeb03020 kasync-0.1.0.tar.xz $curl -T kasync-0.1.0.tar.xz ftp://upload.kde.org/incoming/
Tags are pushed, tarball uploads are pending: T5515
Mar 1 2017
We will disable the dav resource and thus the kdav dependency for the first release.
kasync has been taken out of the kf5 namespace and can be released.
This is currently pending on a release of kasync, because if we remove kasync from the kf5 namespace we'll have to adjust the cmake files accordingly.
kdav will normally be released with 17.04 as part of the applications release.
kf5-kmime, kf5-messagelib, kf5-kirigami are already packaged for f25
Feb 28 2017
Any new on this?
Feb 22 2017
Feb 21 2017
I don't think there are any concrete plans to share components with any other application. IMO it wouldn't make much sense as they are per definition Kube/Sink specific. If there is a desire to do so at some point we can of course revisit that aspect, but no need to plan for that now.
so in the end we will have:
Feb 20 2017
Feb 14 2017
Feb 11 2017
You're more than welcome to work on anything that doesn't seem to be very active, just let us know via phabricator (as you did now), and claim the task.
I was wondering if it would be OK for me to take this on? (I've already got the read/unread button working properly in a local build, I still need to work on marking messages read when opening them.)
Feb 10 2017
We have a messageparser that works for the time being.
As a first step we can have a single button to "download" the attachments and save it into ~/Downloads/Kube/.