oholecek

Zeroconf/Bonjour/Avahi is a very interesting technique that targets at freeing users of services from tedious IP-based network configuration by automatic-distributed address-assigning, name-assigning and service discovery/browsing. It's named officially as zeroconf, Bonjour is the implementation in OS X, iOS and Windows, while Avahi is for Unix-like system. However, while Bonjour is popular and widely used in Apple products, few users take advantage of Avahi in Linux world and the number of applications that do integrate Avahi are still just a few and this feature is not often used.

Wicked is a network configuration infrastructure incorporating a number of existing frameworks into a unified architecture, providing a DBUS interface to network configuration. https://github.com/openSUSE/wicked

Those working remotely or managing a distributed team know it: face time is invaluable. The former openSUSE team has been using http://sqwiggle.com to keep in touch and Google hangout to hold a stand up meeting every morning. We like the Sqwiggle approach. Although the last updates have made it worse, the concept of having a peep to your colleagues' desks to know if they are there (even if they are working hard or just talking to someone) and the possibility of starting a video conversation just clicking on the face shot can do a lot in reducing distances (and in killing the temptation of working naked for home-officers).

The Problem: many bugs filed for openSUSE go to the screening-team by default and often remain there for weeks, so that developers (who would be interested in analyzing or fixing these bugs) do not learn about them. However, the screening process is a hard one

Plan

RandR is X11 extension for configuring monitors and since version 1.4 also secondary GPUs. These secondary GPUs can either provide additional monitors to output to or can render individual applications instead of the main GPU. (Or even both at once.) Once a secondary GPU is configured to do render offloading, applications can be started with DRI_PRIME=<id> environment variable to actually render on it instead of the main one. There are also USB GPUs (dummy framebuffers) that can be hot-plugged.

Use machine learning and natural language processing techniques to analyze the changes made in a project, and classify them in: * Small / unimportant fix

www.opensuse.org is the single most accessed page in the SUSE/openSUSE universe. With 1.5 million visits per month it generates 2.5 million page views and has around 500 people on the page at any given time. Yet it's one of the oldest, crufty pages we have! It doesn't concentrate on what it should do: Tell people about the distro so they download it. It's design is 5 years old, it's not mobile, it's not accessible. There is absolutely no interactive, engaging content at all and the technology used goes as far as a shell script/cron to update dynamic content.

OpenCV (Open Source Computer Vision Library) is an open source computer vision and machine learning software library. The goal is to get familiar with OpenCV API and with the available algorithms. Specifically, I want to look into these particular tasks:

The goal of Project MySelf is to build a system to collect data about yourself in a safe and private way, so that you control your data and you can decide what happens with it. Read more

The virtualization team's automated testing has a long history. It was born in the old Novell Integration Test framework. The virtualization lab ran an instance of this framework for many years. Over time, those who knew the framework left the company, taking their knowledge and leaving little documentation behind. As our testing needs increased, we found the old framework insufficient, but saw little value in improving it given the available open source CI frameworks. Before burying ourselves in SLE12 development, we took some time to move our automated tests under control of a Jenkins instance running in our lab. Tests were configured to run when new packages landed in our SLE12 devel project, ensuring our queued SLE12 submissions were continuously tested. But more is needed.

Occasionally, new versions of openQA break things. How do you stop that? MORE TESTING! Testing openQA by using openQA to ensure the new versions don't break should be a good example of how openQA can test everything and anything, even itself.

Working remotely has many advantages, but you sometimes lack some infrastructure. Specially if you use several computers or you share space with other SUSE co-workers. We are 3 Susers in Gran Canaria and we plan to share an office. So we have bought a Cubietruck, a tiny device with minimum power consumption, an ARM processor, a SATA interface and a Gigabit ethernet. The plan is to come-up with a set of recipes to configure such device to:

<p>There are numerous testing tools for the GFX stack available - the oldes being the xtest suite. At the same time, we are still lacking automated test environments for the funktionalities of DRM, Mesa and X. Ideally the tests should be performed automatically and unattended and the results should be compared to previous runs to detect regressions.</p> <p>Research what tools exist to date and how they can be employed.</p>

By analysing a VNC session, we can create a draft of an openQA testcase (detecting keystroke, mouse click and generating fullscreen needles). The project is to :

CodeMirror is a text editor implemented in JavaScript for the browser, openQA introduced CodeMirror in its source viewer, this project is learn more things from CodeMirror and trying to improving the source viewer in openQA, already had a ticket related, even can polish source viewer more, eg. file folding, etc.

While in general everything still works, the current (patached/extended) planet installation behind planet.opensuse.org is a bit outdated and not maintained any more. The initial plan is to:

To make OpenQA work with real ARM devices, we need to control * Reset

Project Description

The main goal is to enable the use of plain dm-crypt (as btrfs makes LVM2 unnecessary overhead) and a separate ephemeral key for the swap partition.

Project Description

Store the OS root-tree on a container storage. The idea is to build a minimal golang tool capable to init a container storage to a custom location, store remote OCI images in there and mount them into a custom mountpoint. Next step is to craft a dracut based initrd including such a tool to mount the OS at boot. Finally, craft a disk with an EFI partition including the kernel, initrd and systemd-boot.