Problem statement

Once a kernel is built, a developer/janitor may want to boot the kernel for various reasons, such as performing simple boot test or running tests and workloads from user space or simply playing around in a shell. However, an easy to use and a descriptive tool to perform those tasks doesn't exist to our knowledge.

SLE Engineering have a large flatscreen in the shared space just outside of Thorsten Kukuk and Stefan Behlert's office It runs Windows

Build a base image and template (both kiwi and Dockerfile) for openSUSE Leap 42.3 using the native OBS container building feature. Results/WIP will be available here:

• Setup Tensorflow on OpenSUSE 42.3
• Look for a way to package it

First part is to support automated builds on git pushes also with gitlab, similar to what we do already with github.com. This means OBS would get notificated in a save way to refetch sources and start build on each commit. Second part is to support automated branching when a pull request gets created. This allows CI similar to travis on pull requests.

This is a UEFI only device where openSUSE does not boot, hanging after loading the kernel and the initramfs even disabling secure boot. The goal of this project is to learn as much as possible about UEFI, secure boot and finally install openSUSE on this device.

We got a couple of GSoC projects around Jangouts this year: - https://code-master5.github.io/Aug-22-2017

YaST dumps quite information to its own log file (placed at /var/log/YaST2/y2log). That info is very useful to understand and discover what is happening when an issue appears. All YaST modules write into this log file, and the brand new yast2-storage-ng is not an exception. Some improvements are necessary regarding to the logging of this new module: * Libstorage-ng is the C++ library powering the rewrite of the YaST storage stack. For using libstorage-ng from yast2-storage-ng in a more Ruby-like way, we created a wrapper that provides several features like automatic downcasting. But the current downcasting mechanism used by the wrapper causes libstorage-ng to introduce a lot of noise in the YaST logs. It would be nice to reduce that noise.

The theory behind the partitioning proposal of yast2-storage-ng is that all possible distributions of partitions in the disk are evaluated and the best one, according to this criteria, is chosen. But I have found several examples in which is hard believe that the result is actually the optimal distribution of partitions. So I want to invest some time checking if the error is on my side and the code is indeed proposing the best solution and, if that's not the case, improving the decision making of the code.

Time for technical housekeeping in the shared Gran Canaria office. For the last couple of weeks, the Cubieboard powering our "SUSE office in a box" has been unresponsive. I want to check why. Fix it, update the system, etc.

We have a known defect exists in Staging Project process, according to the staging project design(in-ring/non-ring), the requests of a application stack can be dispatched to letter staging and adi staging both, in case the request staged in adi staging relies the request staged in letter staging which may causes sometimes the request in adi staging will not be checked-in at the same round, this leads that application stack have different version in TW and those package had request left in adi staging may does not work well as version unmatched to other library. We see this issue happened on Qt5 stack; KDE Applications, etc. For example: a Qt5 stack update, libqt5-qtbase will be staged in a letter staging however libqt5-qtwebview will be staged in a adi staging, once libqt5-qtbase be accepted that libqt5-qtwebview won't be accept in the same round due to it can not be built before libqt5-qtbase merged to Factory but after - 2-phase update. Therefore we need a way to handle those cases to reduce the gap between Letter staging and ADI staging. The concept of this idea:

I planned to write a GUI for mokutil since I started the project. I guess now it's time to do that.

When doing the backport, I sometimes spend some time to check if the commit comes from a patch series and list all commits of a patch series. So I'd like to create a tool for doing this quickly.

Aim of this project is to create scenarios for manual deployment using limited feature set of mkcloud. Useful for situations when full mkcloud deployment is broken. It would help qam-cloud team a big time. We can reuse the result later in automation.

The idea is getting a general knowledge of how QT Linguist works, and help FET with some translations. FET is a timetable creator, that is available for openSUSE at https://en.opensuse.org/FET, and allows a user to create a timetable, usually for educational institutions, with a lot of different available constraints.

Functionality

Yes this project is yet another project for creating a Suse Manager clone. The motivation for that comes mainly from my need for a simple suse manager that i can easily run at home without the massive overhead involved in suse manager setup. Also since i mainly need to manage opensuse machines most of which are tumbleweed, suse managers repository model does not really work well in that case.

Mottainai - Task/Job/Build Server for everyone!

Written in Golang. You can find the source code on GitHub and docs here.

DAPS, the "DocBook Authoring and Publishing Suite" provides a tool set for easy creation and publication of DocBook sources on Linux. DAPS lets you create HTML (incl. webhelp), PDF, EPUB, man pages, and other formats with a single command. DAPS is used and developed by the SUSE documentation team and hosted on https://opensuse.github.io/daps/ . Currently DAPS supports building documentation from DocBook 4 and 5 sources. The goal of this project is to add support for ASCIIDOC to DAPS. This will allow to easily create all output formats mentioned above with the official SUSE brand from ASCIIDOC without having to take care about templates and other stuff.