Hello, Now that frameworks splitting is almost done ;-) with some people even running KF5-based sessions on their systems, I'd like to plan kwallet porting and integration. BTW, I'd like also to announce that I agreed with Michael Leupold to take over the maintainership of KWallet and I'm now committed to do that. I also plan to add new features to kwallet, as some of you may remember from our Randa discussions. But I'll make another announcement(s) regarding these new features and ksecretsservice.
Here are my questions about kwallet in KF5: * what tier will kwallet end-in? Note that kwallet.h is included only by khtml, whose tier is not yet defined * AFAIK, frameworks should be independent and self-contained. kwallet depends on kde-runtime/kwalletd. This component should be detached from kde-runtime sources and attached inside kwallet/src/kwalletd, preserving history if possible. I can handle this task if that's OK for you (Aron, David, Kevin?) * Another piece of software related to kwallet is KWalletManager from kdeutils. I think that component should also be detached from kdeutils and attached under kwallet/src/manager. I can also handle this task if that's OK (Aron, David, Kevin but also Raphael?) * kwallet is now in staging ; should I wait for it to go to it's final tier? I can do this tier adjusting changing task and I'd also like to start these tasks as quick as possible. Thanks for reading and I'd be grateful for a quick reply on these topics. Regards, -- Valentin Rusu (IRC valir, KDE vrusu) KSecretsService (former KSecretService, KWallet replacement)
signature.asc
Description: OpenPGP digital signature