Why

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:

The experience while navigating throughout the UI of Suse Manager it's not that nice. Whenever we navigate to a new page, the whole page gets refreshed and recreated, even when half of it didn't change a thing, for instance, the menu, topbar, and the notifications WebSocket connection, which in my opinion doesn't provide a smooth experience.

What is ResourceSpace

Description

Project Description

Description

Many requested the ability to "preload" cache content for the Uyuni/SUMA proxy or retail branch server. This was not possible with a VM proxy - but what about a containerized one? Now that this is the direction and standard, it is worth testing this and then documenting a working procedure.

SeaMonkey is the successor of the Mozilla Suite. The mail client allows connections over POPv3 and IMAPv4. In some cases one wants to leave the program running for longer periods of time, but once the mail client has password for a mail server it just stays connected. In case of "keep everything on server" profiles this means that the mail may stay accessible even when the machine is left unattended (which it often is). The purpose of the extension is to enable requesting the client to forget mail server passwords, so that the mail is no longer accessible without entering it again.

The goal is to use the work from the debug-early GCC branch to generate better debug information for LTO compiled objects, especially with regarding to language specifics like classes and templates. This has now been achieved and openSUSE Factory

Record two songs by the end of the week.

See my Relax-and-Recover upstream issue https://github.com/rear/rear/issues/841

Are you interested in pairing? Are you wondering whether it is something that would help you and your team members in your current project? Would you like to try it out before you fully commit to such an extreme idea? Then this is your lucky day Sir/Madam!

We got a couple of GSoC projects around Jangouts this year:

The idea is to explore the technologies and the various components to realize some AI to predict pitfalls in source code which can potentially generate run-time misbehaviours.

I'd like a way to have a device on my desk which lights up to indicate that I have something I should be paying attention to. Initially, I'd like this to be for Office365 calendar events and GitHub mentions, but ideally it should support arbitrary messages. The plan is to assign specific colors (ideally "patterns" consisting of a sequence of colors and time) to specific message types.

Description

SUSE Observability pre-processes topology data during ingestion and stores it in its custom graph database.

Description

Currently our daily CI/CD UI e2e job deploys Rancher in RKE2/k3s AWS clusters. The purpose of this project is to study the viability of running our daily rancher UI e2e tests job in self-hosted runners, deploying rancher in harvester RKE2 clusters.