Hello Tomasz,
thank you for your comments about the road map.
My main achievement for last year is the complete switch to Sculpt as my main OS on my personal computer (laptop). Since I managed to configure "native" Linux in a VM on Sculpt about 2 months ago, I did not boot it as first OS - only inside Sculpt.
That's reassuring feedback and wonderful to know!
I think, as a user, I can declare myself as a tester of Sculpt. I had it running with uptime for about three weeks till today. Unfortunately I was forced to reboot due to some strange global performance issues. I can try to help in the future in diagnosing such issues by providing some data in case there is a need for it.
I'd appreciate that a lot because testing over long periods is still a somewhat blind spot. E.g. in my case, I'm powering off my laptop each evening and rebooting it in the morning. So I won't casually hit such issues that show up only after weeks.
The next time you observe such an anomaly, it would be good to have a look at the top tool or to enable the trace-logger option to observe the CPU utilization, hoping for clues. It would also be interesting to see if the issue disappears when restarting the VM.
For immediate plans I will try to invest time in vnc client as I use it for accessing my development machine. Two aspects are currently most pressing:
* understanding configuration and internals of keyboard handling (enter key is repeated in an uncontrolled way, modifiers handling is blocking some shortcuts like Ctrl+Shif+C for copy, somehow I was able to get into a state when Caps Lock is inverted between Sculpt and remote desktop, etc.)
* analyze performance - sometimes redrawing of remote screen (size of 2 full hd monitors) takes few seconds in a LAN, so it is far from convenient.
For other tasks I'd like to be able to go back to my unfinished, abandoned do to lack of time activities like support for Raspberry Pi devices and exploring improvements for Genode development. Those ideas are unfortunately more wishes than plans.
Thanks for sharing. I think that the Raspberry Pi remains an interesting target from the community perspective, especially compared to the rather expensive i.MX hardware.
Cheers Norman