Hello,

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?


-- 
Valentin Rusu (IRC valir, KDE vrusu)
KSecretsService (former KSecretService, KWallet replacement)