3 coders, 1 year and 29 days, and 5 “New” queue rejections

…is apparently how much it takes to get userconfig ported to KDE4. It’s epic in an awesomely pathetic manner. 😀

You may remember userconfig from the KDE3 days. It was the user configuration module inside of System Settings, developed as part of the Guidance project for KDE. It was a bit easier to use than KUser and was integrated into System Settings. Due to lack of manpower and insufficient bindings at the time, the Guidance project was discontinued around the start of KDE4. About the only project that survived was guidance-power-manager, since it was needed to fill an important niche (power management) and people were maintaining it.

Work on the KDE4 port of userconfig was initially kicked off by Yuriy Kozlov 1 year and 29 days from yesterday. (http://code.launchpad.net/~kubuntu-members/guidance/userconfig-kde4) Yuriy got it to the point to where it ran as a standalone application (no python bindings for System Settings modules yet), but didn’t really do much else. The guts were there, it’s just that the interface code didn’t fair well in the KDE3 -> KDE4 porting. The layouts were all messed up and such to the point where it wasn’t all that usable.. Unfortunately, real life set in(tm), and Yuriy found himself unable to continue work on the project.

After that, I came along and rewrote the GUI using Qt Designer files. Now everything looked ok, but there were still quite a few bugs and everything was still very alpha– definitely not something that we could include in Kubuntu 9.04.

Ralph Janke (txwikinger) then came and fixed things up quite a bit more, but I think both of us either forgot or were unable to contribute more to the project, and userconfig languished in bzr for several months.

A few months ago, Yuriy found the time to code a bit more, and ported userconfig from being a standalone application to a System Settings module, just as it was in KDE3 times. Now things were looking pretty good, and userconfig was ready for release. Jonathan Riddell and myself collaborated and were able to get a package up in a PPA for testing, where it was promptly forgotten about until the day of Feature Freeze. Oops.

So a few days ago I got the Feature Freeze exception all approved and spent yesterday uploading userconfig to Ubuntu. I ended up getting it rejected out of New queue 4 times before it was accepted (Sorry for the abuse, ScottK); the failures were due to problems with userconfig itself, copyright problems introduced fixing said problems, or a mix of the two. I think I now hold the record for most rejections of a package in a day. 😀

All in all, it feels like a war has been fought just to get this piece of software out in the wild. Picture the three of us, straggling in with ripped clothes, posting a flag triumphantly on the mountain top. It missed Kubuntu 9.10 alpha 5, but you can install it from the archives now no problem. (sudo apt-get install userconfig) Please test, etc. If everything goes well, you can expect this to be default in Kubuntu 9.10 alpha 6, replacing KUser as the default user management tool. Yay!

Here’s to a grand alpha 5 release! 🙂


7 Responses to 3 coders, 1 year and 29 days, and 5 “New” queue rejections

  1. Stefan says:

    I had idea about this on KDE Brainstorm.


    Can you post more snapshots?

    I never liked KUser. It's good application, but difficult to use.

    So, please post more snapshots so I can see if it's better…

    Thank you,

  2. Alejandro Nova says:

    Please, fork.

    Let Ubuntu do GNOME and have a little of respect for yourself. The pathetic status that Kubuntu hardly earned release after release is damaging KDE as a whole, and you, developers, are not guilty of this. It's just your management. It's just being part of Ubuntu, a GNOME distro. Please, fork, keep the manpower on board, kick out any Ubuntu reference, and become the best Debian-based KDE distro. We really need one, and Kubuntu isn't even close.

  3. ggrabler says:

    @Stefan: Just use it, check it out, compile it, and try to use it. It's really a lot better than what I've been used to in KDE3.

    @Alejandro: Stop bashing on what people are using KUbuntu. They're making use of their freedom to use what they want, and if their choice is KUbuntu, let them use KUbuntu. If yours is not KUbuntu, stick with what ever you want.

  4. Lastnico says:


    You problably forgot another step in rewritting in porting Userconfig :


    The next real important step would be to fully integrate Userconfig into KDE Admin module, and definitively replacing KUser.

    In any case, that's a good work, and I'm happy to see this project moving again!


  5. JontheEchidna says:

    Yeah, getting it in to KDE proper is somethine that'd we'd like to do in the near future.

  6. gamemank says:

    There are more (some outdated) screenshots here:
    If you have ideas for improvement, please post them on that wiki page.
    I do hope to get it into KDE, but seems someone will have to implement an LDAP backend before it can replace KUser.

  7. agateau says:

    Nice work.

    I am probably a bit late at this, but I have some UI suggestions:

    In the listview, the second column is labeled "Username", but in the details pane this information is labeled "Login Name". They should be made consistent

    Using two columns in the details pane is confusing IMO: I suggest going for a single "key: value" column. To do so you would have to turn the "Secondary Groups" listbox into a wrapping label containing the group names separated by commas.

    You could also try moving the detail pane to the right of the list.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: