Sysadmin/IdentityFAQ

FAQ identity.kde.org

When I upload my ssh key, it tells me that the key is invalid. I'm sure my public key is fine! This is probably caused by your public key not having a comment. Open your public key file and look if it ends with a small comment. If not, add one. It should like something like:

ssh-rsa AAAAB3NzaC1yc2EA...q89tLQDeeLAiiQt80P2tiNIOw== Comment

How have the accounts from the past been imported into gosa? If you were an active developer, your svn username has become your gosa login and your ssh-key has been imported, together with your name and email. You are marked as 'developer', so you have push access.

If you were an active developer with a https based account, this applies too, but of course your ssh-key list is empty. Simply set a ssh-key and you are able to commit again.

If you have been an active developer and have been disabled at some point of time, for example on your own request, you are are imported into gosa as a 'user', that means your loginname equals your former svn username, but you don't have push rights.

TODO's identity.kde.org

These is a small todo list, mostly internal for the sysadmin crew, but so you all know what still needs to be done:

Layout

The page layout on identity.kde.org forces a rather wide window for penalty of a horizontal scrollbar otherwise

KHTML has misaligned text at top right

Technical bugs:

Default language should be english, not browser dependent.

Setting an avatar fails and leads to a timeout when saving the profile

Show the groups you are in somewhere

People can still fill in a new devel application despite having a pending one.

Send out an automatic confirmation to a user when his account is upgraded to developer.

The developers-addressbook is currently to-be-ported by the gosa devs to 2.7.

Long term:

Make po's available for tranlators