The Nokia N900 is a versatile phone/tablet/mini-computer. While its specs are outdated by today's standards, it's still hard to find something equivalently useful to hack on-the-go. Most of it's drivers are already upstream, with just a few components missing:

This is a project to create a "larp" game for SUSE employees (or anyone geeky enough to play this) which will be based on computer related knowledge. The core of the game is to search for other people and clues for solving the main goal by "connecting" or "hacking" according to given HW and SW roles. E.g. a person will play router, another one will play PC and they will need to find a person playing TCP/IP protocol to communicate and eventually create a working setup to solve the goal. They they need to work as a group and solve riddles/ciphers which will let them go further. There are more game mechanics i have in mind, but don't want to spoil all of them now :)

Currently the Open Container Initiative doesn't specify a distribution protocol or system, and the current "standard" format is the Docker registry protocol. Aside from technical reservations with Docker registry, it is also not an OCI-compliant system and will require a lot of work to integrate it into all of the openSUSE/SUSE tooling. So, a very insane idea I came up with is to convert OCI images to RPMs and then distribute them as simple RPMs. The idea would be to use capabilities (Provides: oci(...)) to implement the different names of images and then also the dependency graph of blobs (which would naturally be de-duplicated).

Connect is the "social network" of the openSUSE community. While this might not sound so important, the problem is that the tool is used for membership management and all the other "administrative" stuff for the openSUSE community, which makes it a very important tool. The bad news is that - since years(!) - there is no-one actively maintaining the application. While the openSUSE Heroes keep the basic infrastructure up and running, they are not responsible for the application itself. Following the standard policy for such services, this would mean that connect has to be shut down immediately. But the openSUSE board heavily depends on this tool and asks every time when it comes to "shut it down" - to not do it.

COBOL is weird. COBOL is strange.

From the manual: "Org is a mode for keeping notes, maintaining TODO lists, and doing

The goal of this project is to write a proof of concept of a new philosophy for yast2-storage-ng. Instead of just extending the API offered by libstorage-ng, the idea is wrap libstorage-ng so the Ruby code using yast2-storage-ng does not have direct visibility (unless explicitly desired) on the libstorage-ng classes and methods. If you don't know what all that means, keep reading.

There is plenty of documentation wiki articles, forum posts, etc., but even with Google or local search engines the answer may be hard to find. Sometimes categorisation is missing or just basic information. 1. Look at existing openSUSE options and their usability.

Perl-apparmor is obsolete in the apparmor community. No one is maintaining it. However, opensuse has to keep it to interact with yast, which is the main consumer of perl-apparmor. Getting rid of perl-apparmor would mean: + Creating a new interface (JSON) to interact with outside world (IOW, yast)