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

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

Any new on this?

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:

• components/accounts
• components/mail
• components/people
• components/..

Absolutely!
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.)

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/.

This should eventually turn into a more generic undo action.

Yes, I think its done.

@aheinecke: is this also done from your side?

We have a simple model-based autocompletion solution.

Switching to qwebengine didn't fix the problem.

sounds good

Probably just a simple timeout to avoid syncing i.e. more than every 5 minutes?

makes sense to me.
what heuristics do you have in mind?

We can now synchronize individual imap folders. The maildir resource still syncs everything (since it shouldn't matter too much for performance.

We only have one patch on top of master to support gpgme 1.7.2 if this is released we can switch to messagelib master

@jensreuterberg and I will have a pixel pushing session this weekend to tackle this

thanks to @knauss we now have an attachment model. now I just need to make it pretty