L10N for the book entitled Designing with LibreOffice by Bruce Byfield

Learning boot loader related knowledge

Learn about boot manager, including trusted computing, disk encryption, EFI, storage and more

There is always something to do if you run the infrastructure for such a big project like openSUSE.... Our Admin wiki currently lists over 80 machines - and while we already "salted" some of them, there is always room for improvement and room to learn something new just by making your hands dirty and diving into the administrator role for a machine.

Project Description

This idea has been partially implemented for JeOS images, where we are collecting some data from the images whenever a new build ends up in openQA. For instance, https://openqa.opensuse.org/tests/2419705#step/image_info/9 is collecting the size of the image, as well as total number of RPMs, the list of RPMs with their size and some filesystem information.

In https://github.com/SUSE-Cloud/automation/ we already have mkcloud, which can setup a whole SUSE Cloud on a single host for testing. However, it would be cool, if (instead of a single machine) we could use cloud.suse.de with its capability to add extra networks as requested. This can be pretty easy, as much of the mkcloud code is about making libvirt do the right thing

RISC-V is an open ISA (Instruction Set Architecture) based on RISC architecture. It's originated from UC Berkeley and it's attracting more attention in recent years because of its full open architecture so every developer has opportunities to get involved in application processor design or apply it into different applications, such as IoT, Robotics, ... etc. Any topic about RISC-V is welcome, here are some topics you might be interested in:

This is mostly a learning activity for myself, others may benefit from documentation.

Project Description

Project Description

Make sure that as many as possible packages in openSUSE:Factory are up to date

Project Description

Just hook up a webserver framework for rust with things like opentelemetry for tracing, prometheus endpoint for monitoring, structured logging (to systemd) instead of line based logging.

PXEAT (stand for PXE Administration Tool) is a tool to easily deploy and manage PXE service. It's NOT a tool for automatic deployment. It can enable user to add their own PXE items by themselves, but of course, very limited for security reasons. The tool will be developed with the light-weight framework - flask, as well as a sqlite database.

DAPS is the tool used by the SUSE documentation team to generate HTML, ePUB, PDF, ... output of the SUSE manuals from DocBook XML sources. It uses the suse-xsl-stylesheets for this purpose. Currently three different suse-xsl-stylesheet brands exist: SUSE, DAPS, openSUSE. Branding is done by adjusting the xsl-stylesheets directly. It would be desirable to be able to easily change the branding, e.g. via a simple config file in the style of /etc/sysconfig files, since most people cannot hack XSLT. This is also the number one enhancement request we get from DAPS users outside of SUSE.

Within SUSE we are using various systems for different tasks. E.g. GitHub and GitLab as DVCS, Jenkins for building or testing, OBS for building… and the list continues. Some of those systems can be interconnected in some way. But not every system can do that, especially if you are behind a corporate firewall and some (I'm looking at you GitHub) have a quota. So wouldn't it be nice to have something like a Big SUSE event bus, where every event we'd be interested in could be queried or subscribed to? But before conquering the world, we have to start small. Let's start with GitHub! GitHub has a decent API that let's you query their system. The goal looks like this: Allow multiple clients to query information from GitHub without using the quota irresponsibly. It should also be possible to push state changes to subscribers.

We kinda need more flexible PXE in Prague office, UEFI would also not hurt - so lets check what we can do to make it better. EDIT (ggherdovich):

If nothing is changed, no Hackweek T-Shirt awaits us. So, taking the initiative, I am searching for other creative minds to collaborate with.

Project Description

A settings center akin to GNOME/KDE/XFCE settings panel but built for window managers like sway, i3 and hyprland.

More and more customers use our products in mission critical environment. They have a huge need that things run smooth. With Hack Week we have the challenge

Project Description

Since now we have a system that take real time data from progress to generate metrics

We have some internal systems for videoconferencing like Big Blue Button or OpenMeetings. But in my experience none of them can compare to Google Hangouts, which is still the best free (as in free beer) alternative for videoconferencing with integrated screen sharing. While implementing an alternative to Sqwiggle on previous hackweek, I discovered Janus, a lightweight WebRTC gateway that proved to be a quite capable tool to implement video applications.