In a quite natural and steady way, all my relatives (wife, kids, mother, aunt...) have adopted openSUSE in their computers. There is only one resistance spot. My father's computer (HP+Windows8) implements all kind of mechanisms to avoid dual boot. I plan to use the spare cycles of my Hack Week to get a dual Windows/openSUSE system on that haunted computer. Killing Windows would be a feasible last resort.

Using python's lib requests to write a small(PoC) Web spider. https://gitlab.suse.de/shukui/web-spider

Ceph is very robust for keeping data, beside using cephfs or exporting rbd. It is not too easy to access object directly with a client, let alone mobile. By using Rados gateway, android client can easily using S3/Swift http/s request to read object data from the internet. It is a simple idea to use an existing open source android FileManager e.g. https://github.com/arpitkh96/AmazeFileManager

See https://github.com/viccuad/salt-configs . The idea is to apply the Puppet code pattern to create salt config files to

Currently the main complaint people have about OCI tooling is the lack of a transition from Docker to OCI. With umoci you have a lot of low-level image configuration abilities, and skopeo and runC cover the other major parts of the picture, but you need something to tie them together. I'm not going to be implementing YAWAR (Yet Another Wrapper Around Runc). It's just going to be a single script that can take a Dockerfile and create an OCI image that is basically the same as the Docker image you would get -- with the big difference being that you didn't need Docker and everything used the OCI. The other cool benefit of this is that you could build images without privileges (since rootless containers now exist in runC and in umoci).