posixovl is a FUSE based successor of the old UMSDOS. It has a goal to provide POSIX file system functionality on top of vfat. Its code is nice and well written, but its feature set is not complete yet. It just supports: POSIX modes and user/group, hard and symbolic links, device nodes and named pipes.

Some customers are still stuck in a world of 32bit. On ARM64, we have two options for those poor folks:

Nailed is a Sinatra app which currently shows Bugzilla, Github and Jenkins [WIP] data. The data gets fetched/refreshed by a ruby command line tool in the background.

Have a look at the library implementation and its API.

LVM support for Guix System Distribution

Due to the newly appointed PM of SLERT 11 SP4, I would like to try out the SLERT 11 SP3 to experience the REAL TIME features so that I can talk and share the knowledge to team and other people

Goal:

For Hibernate Signature Verification - HMAC version, I need a hash algorithm in EFI stub environment before ExitBootServices() to mix / mess random seed from different sources (rdtsc, rdrand...) for generating the HMAC key to sign the hibernate image in runtime environment.

The libvirt qemu hypervisor driver has long supported protecting disk devices from concurrent use via libvirt's lock manager interface. Xen used to support the same functionality in the old xend toolstack, but dropped support in the new libxl toolstack. The Xen community decided, rightly so, that this functionality is best provided by a higher-level management tool, e.g. libvirt.

Currently, the usual way to communicate with VM instances in the cloud from outside is ssh. This is okay for most uses, but a) does not work when you mess up with the guest's ability to network and b) requires a free floating IP.

I would like to have a programming language that has the performance characteristics of C, but integrates some programming language features that I like from other languages. My first goal would be to start with a language that is very limited in scope and compiles directly to C, and step by step add to it.

The current approach to having new hardware support and features in SLE kernels it to integrate changes to individual drivers from the mainline kernel back into the SLE kernel. The Linux Kernel Backports project (https://backports.wiki.kernel.org/) in comparison has an approach which consists in adding a shim layer between unmodified mainline drivers and older kernel interfaces. This project has its roots in wireless drivers. It currently supports only a handful of old ethernet adapters.

Objective

Port the Fiurefox extension FireTitle to SeaMonkey.

One of the winning factors of Docker is the Docker Hub. This the a place where the Docker community shares their images. Thanks to Docker's integrated build system it is possible to create new Docker images by just extending an existing one. That's why the Docker Hub is so useful.

I'm currently using LastPass as password manager but it has several drawbacks:

openSUSE Connect is almost forgotten tool used only for elections. It would be nice to update it, polish it a little bit, disable functions that nobody uses and fix those few that people would actually like to use.

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

In order to have complete cloud experience on Power platform it needs some missing pieces to be available: * SLEShammer image (SLE11-> SLE12)

Python is well known all over the world and has wide range of usage. Lets dive into to a bit.

Implement file system image build using the Builder infrastructure. The project will create additional builders for the ext filesystems laying the ground work for restructuring other filesystem builders.

Work towards release of Weblate 2.3, the roadmap is in the issue tracker:

I had presented the "Wicked Network Manager" talk at openSUSE Asia summit @Beijing. I would like to keep studying the topic continuously. Getting involve the source code and study the operating style and components. I also met some problem after discussing and testing issues while my research , I want to keep it as a record and writing the technical document on wiki too.

Tool to inspect the meta data from a mini DV firewire transfer and report any quality problems such as dropouts. Preferably a gstreamer 1.x based tool.

Report from the research mailing list:

Current kGraft implementation allows to apply new patch only when the previous one is applied to the whole system. Every task is handled separately and it needs to wait for a safe place to switch. It might take a while, especially when the task is sleeping.