[proposal] KSecretsService components moving from playground

Will Stephenson wstephenson at kde.org
Sun Oct 16 14:30:38 BST 2011

On Wednesday 12 October 2011 00:24:00 Valentin Rusu wrote:
> As KSecretsService becomes quite usable, I think it's time to prepare to
> get it integrated into the next release.
> http://techbase.kde.org/Schedules/KDE4/4.8_Release_Schedule
> The code is not yet fully mature, all the components are not yet
> finished, but the main parts are there and it is now possible to have
> secrets stored in KSecretsService and konqi or microblog successfully
> getting them upon session start. There is a checkbox in the KDE Wallet
> configuration tool that switch KWAllet API to KSecretsService when
> checked. It will be left unchecked for the next release.
> Components are:
> 1. KWallet API - already in kdelibs branch ksecretsservice,
> 2. ksecretsserviced - still in playground,
> 3. kwl2kss -  still in playground,
> 4. ksecrets - still in playground
> 5. secretsync - still in playground.
> 6. kio - still in playground
> Components needed for 4.8 are 1., 2., 3. and 4. Therefore I propose to
> move them out of the playground as following:
> 1. get merged into 4.7 branch before 4.8 branch is created
> 2. goes to kde-runtime,
> 3. make it part of kdeutils/kwallet [see complement below]
> 4. create a kdeutils/ksecrets repo for it and for 5. and 6.
> Complement:
> kdeutils/kwallet has a branch containing code specific to
> ksecretsservice (e.g. the checkbox to activate ksecretsservice
> infrastructure). This branch should also be merged when releasing 4.8.
> Any thoughts?

This all sounds good.  A couple of questions:
1) Are the KWallet API changes additions, or will some parts of the kwallet 
api be deprecated?  If so, when do you plan to add the deprecated tag?

2) When and how is migration performed under this model? When the checkbox is 
changed?  Does this handle cases where a wallet request is already showing (on 
another desktop, for example) or when a wallet request comes in during the 
migration process?

3) When is migration performed during a mandatory migration? Is there a chance 
that migration will cause login to block?


More information about the kde-core-devel mailing list