The idea is quite simple, and all the pieces should already be there - but what is, IMO, lacking is putting them all together:

Tasks

Description

Small non profit organisations or activist groups need a Web presence that is easy to maintain by several authors. When using a CMS they do not have the resources to secure the CMS from the various possible attacs most CMSes are notorious for. Defacement or placing malicious content can damage the reputation of such non profit organisations.

https://github.com/MalloZup/go-verdura

From the kernel-source git repository for SUSE kernels we can extract the people who backported a patch and the files a patch touches. Use this information to build a database for which paths are touched by which developers and write a tool to find the most relevant people for a given source path or upstream patch.

I wanted to work on something test related this hackweek since we always need more automated testing of our virtualization-related packages. There are many possible test-related topics, but I think a good addition would be more unit tests that are run during build time, e.g. during 'make check'. Additional tests of this nature would then be run by upstream developers and the various distro CI setups, exposing the tests to more environments than would typically be available within SUSE.

http://squarefootgardening.org/ is a form of intensive gardening that packs plants closely together. It depends on companion planting to encourage growth and protection for pests.

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.

Having worked on KVM for a long time, it's time I actually start using it myself! I now have a high enough powered laptop to have a permanent setup on my laptop to do almost all the testing needed for releases, as well as maintaining playgrounds for upstream work and involvement. This will include nested virtualization, which is getting pretty bulletproof in latest kernels, as well as being able to play more with these other architectures that we now support KVM on, via improved TCG emulation (of course some testing and development will always rely on the physical hardware, but still a lot can be done via TCG incl. user-linux mode. I'm also seeing which aspects of pass-through testing will make the most sense to perform on the laptop (pci, usb, video, filesystem, etc.).

Overview

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.

See https://github.com/viccuad/salt-configs .

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.