Implement GNOME Software's Distribution Upgrade in Leap(and possibly Tumbleweed)

a project by JonathanKang

GNOME Software supports distribution upgrade, that only requires a few clicks for upgrading your system. But it's not integrated into Leap. So this is that I plan to do this Hack Week.

Involved components

Updated 3 months ago. 7 hacker ♥️. 1 follower.

Support Pinebook Pro in openSUSE

a project by michals

Pinebook Pro SPECIFICATIONS

Updated 7 months ago. 3 hacker ♥️. 3 followers.

Zero-ish downtime deploy on da cheap!

a project by josegomezr

Zero-ish downtime deploy on da cheap!

This project aims to get a 0-ish downtime deployments (very easily achievable with Kubernetes) just using:

Updated over 2 years ago. No love. 1 follower.

make "predictable network interface names" more predictable

an idea by mkubecek

Since the so-called "predictable names" for network interfaces were introduced, the concept and mainly its implementation has been a target of a lot of critique and sometimes even hate. On the other hand, similar idea works reasonably well for block devices. In my opinion, the main reason why "predictable names" reception was not nearly as good as for block devices is the difference in how the implementation works. For block devices, the device name provided by kernel is preserved and other names based on multiple naming schemes (by path, by UUID, by various device identifiers) are created as symlinks so that all of them (including the original kernel one) can be used simultaneously. On the other hand, network interface has only one name and as it is not represented by a file, symlinks cannot be used for aliases. Therefore even if there are multiple naming schemes (e.g. based on BIOS enumeration, bus address etc.), only one of them can be used for each network device and it's rather unpredictable which one is it going to be. Moreover, some of the generated names are rather long, ugly and inconveninent and unlike with block devices, one cannot just ignore them and use a different name (e.g. one provided by kernel).

Updated over 2 years ago. 1 hackers ♥️. 2 followers. Has no hacker: grab it!

Golan no vendor

a project by rjschwei

At present it is our practice to "vendor" all dependencies for a Golang package. This has the advantage that everything is in one nice package and self contained but it has the disadvantage that dependencies are hidden and therefore security issues may slip through the cracks. The idea is to investigate and create automation "go2rpm" that generates a spec file with the necessary "BuildRequires:" such that the dependencies can be broken into golang- packages and we get rid of the implicit dependency inclusion via "vendor". The potential problem is scale, with some golang applications having thousands of dependencies.

Updated over 2 years ago. 1 hackers ♥️. 1 follower.

Package ROS for Opensuse and SLES

an idea by neotinker2

I have a few robotic projects I wanted to work on and didn't like the idea of run Ubuntu to control them... So I'm packaging all the Standard ROS stacks for Opensuse 15.1 and SLES 15 SP1. My goal is to build for all possible architectures. I currently build the ROS Infrastructure packages for aarch64, x86_64, and armv7l. These are required to perform a source install of ROS.

Updated over 2 years ago. 1 hackers ♥️. 1 follower. Has no hacker: grab it!

Modernize Mash deployment

a project by seanmarlow

Mash is a Python based CI/CD pipeline for automated testing and publishing of public cloud images. Currently the production and development deployment for the package is inconsistent, slow and manual. This is a barrier to rapid development, deployment and testing. It also means the development workflow is different than production. This can lead to production issues which were not seen during development. In order to modernize the Mash workflow I plan to spend the week digging into a plethora of tools to first learn then build out a new workflow. The goal is to simplify deployment by choosing tools that provide consistency, modularity and repeatability. By leveraging the best tools available we can harden the code and accelerate the release cycle.

Updated over 2 years ago. No love. 2 followers.

Try to write simple rope-base Python language-server for LSP protocol

a project by mcepl

Future of tools supporting editors in dealing with particular languages is in my opinion in the LSP protocol. Therefore I look with a bit of worry on the fact that there is no good LSP server based on the top of rope. python-language-server uses it a bit internally, the Microsoft Language Server for Python is in C#, so it is completely something different. The goal of this project is to write a very simple nucleus of the LSP server based solely on rope for the language analysis and actions, which would be at least able to do “jump to the definition of a symbol”.

Updated over 2 years ago. No love. 1 follower.

Deploy a Ceph Cluster in AWS using sesdev

an idea by LenzGr

For testing and development purposes, the SUSE Enterprise Storage team has created a tool called sesdev, that deploys a fully configured Ceph cluster on multiple VMs using Vagrant/libvirt. In this project, I would like to explore if it's possible to extend sesdev in such a way that it can perform the deployment on Amazon AWS instead.

Updated over 2 years ago. 1 hackers ♥️. 2 followers. Has no hacker: grab it!

Analyser for YaST logs

a project by jreidinger

Well, we often stuck in YaST team with knowledge what users really use and how much. But we have yast logs in many bug reports. And from those logs we can see which modules users use the most. So goal of this project is to write script that analyze given tarballs with logs and print result about usage of yast clients.

Updated over 1 year ago. No love. 1 follower.