I followed this conversation almost live... seeing persons show off with simple oneliners and bad code, but never looked at the (context in) the code, let alone ever having used the program itself or have any intention to do so. As I stated earlier, I am not proud of the code. It wasn't in a good shape, and I seriously doubt I it made it any better. I'm not a true developer by profession, but just tried to fix/improve issues that no one was willing to pick up. No idea what kind of mess the original worldclock code is, because we don't have it and can't adapt it. So that's some things solved. Then I suddenly see all sorts of additional requirements popping up. And what is more to come? I can think of a dozen in the future. All the substantial aid I got from the current active cssu members is from Pali, with the packaging and some small adaptions. Freemangordon would do a code review, but never got to that. Yes, there are always other and new priorites, I know. For me, the replacement clock has turned into a stable tool I use intensively. Cssu or not will not change that. Bottom line: I have no desire to continue this project within this rudderless cssu frame. I hope it finds a new maintainer that not just talks in oneliners, but actually works on it. Besides Gidzzz, there are not many talented and active gui developers left If your goal would be cssu: be warned for a very bumpy road