Comment 1 for bug 1642249

I think this will be, at least, not easy... We want quality software, right? So here we go...

From what I see, this is not really a nice and well (at the current state) for the end user because of certain limitations:

1. timekpr locks user out, in linux there is no way of really telling that user is locked instead of password is wrong (I found quite suitable solution, but not 100% nice), so in the end, user gets "password is wrong", which is misleading for timekpr users.

2. Not yet an integration to software settings, this is separate issue. As I see it to be part of ubuntu, I would like to have it integrated into settings.

3. There is client (indicator) and daemon (actual worker) integration problems here. Both are totally async, I would like it to make them sync, like a true client, most likely based on dbus, which I implemented for notifications for latest verision. This means rewrite of timekpr, which is not really a couple of days, especially for busy person.

4. Audience for this is quite small tbh, 3074 downloads of latest version (0.3.6) to date, from precise to zesty. 1/3rd of all are xenial, closely followed by trusty (almost 1/3rd), so LTS rulez :) This, of course, does not stop me really (I'm still exploring ways of slowly implementing a new solution in "my right way"), I'm all for the sensible limits and against abuse of computer time, but my free time stops me. My family basic needs are satisfied with current version and there is really nothing very urgent to implement at this feature level which will make big difference, tbh.

5. Configuration, at this point, is not really satisfactory, I would like to make it a bit leaner, so usage is more realistic, for instance, time slot can cross midnight, there can be extra time added to account despite all limits, etc. I mean - make it more real world user friendly, which takes time to pland and develop.

6. Some more... I won't go into details right now, but if I'll design a good solution, I'll inform users of timekpr, for sure...

So conclusion is that it's not ready for official repo right now, more work needed. No need to change programming language etc. Sensible ideas, what has to be implemented, from user perspective are more than welcome!

So, if this is me trying to push this into official Ubuntu, I'm not doing it unless this is quality one, yes, even for this simple task to limit kids using computer, it has be to refined and working like a charm, not less.