The idea is about an easy way to allow users to make upgrades (e.g.: changing from one major version like 15.0 to version 15.1) using a GUI and as easy as they can in Ubuntu. Something like a notification with a button to perform the upgrade with just one-click, instead of having to deal with the terminal, that frights some new users and gives them the sensation of an outdated system.

Video Recording of openSUSE Conference session which introduced the project

Core Project

New Development In previous hack weeks, the first few days ended up being wasted on just getting it working. I'm pleased to share that the code quality has improved dramatically since the last hack week and there are now extensive test cases for both unit testing and testing against real vmcores, and we'll use both mypy and pylint (if installed) to perform static analysis. Packages for those are available in openSUSE or as part of the crash-python OBS repo for SLE15. It has been tested with kernels from 3.0 to 5.1.

Project Description

In the past year we've found ourselves in the middle of a pandemic, we merged two awesome companies together, and we have completely changed the trajectory of SUSE and Rancher. This project is intended to transfer knowledge of SUSE to Rancher and Rancher to SUSE for those who may be challenged with time and resources to try new things. This gives us a chance to explore other uses for Kubernetes all while taking advantage of older equipment (for use as workers) we may have to spare.

For events like engineering summit or hackweeks, it would be nice to have a SUSE instance of workadventu.re, and have our own maps, wired with (open)SUSE's jitsi! I am looking for folks willing to help on those 3 teams:

Let's pick some old classic game, reverse engineer the data formats and game rules and write an open source engine for it from scratch. Some games from 1990s are simple enough that we could have a playable prototype by the end of the week. Write which games you'd like to hack on in the comments. Don't forget to check e.g. on Github and SourceForge whether the game is ported already.

Once again, the SUSE band is coming together to make music and we're planning a party this time round!!! We have a band name :-)

Project Description

The SUSE Enterprise Storage team has embarked on a new open source project: Aquarium.

Primarily to support Hackweek, but also to gain experience for a potential future corporate use, I like to run the open source Jitsi in a SUSE context and within a setup that is close to what SUSE IT is doing. The service will be built in AWS/EKS within the SUSE E&I space and should be up and running on day 1, but will need love during the 5 Hackweek days to

Deploy Uyuni as an app from the Rancher marketplace - or install via Helm on any Kubernetes cluster, on any OS, or any Public Cloud.

The dream

Project Description

Phoeβe (/ˈfiːbi/) wants to add basic artificial intelligence capabilities to the Linux OS.

We already tried to improve the Jangouts data model in the past and, although we made quite some progress, we did not finish it. I've been playing a bit with React and Redux lately, and I would like now to try a different approach replacing Angular with that combo. Using Vue.js might be another option too. Of course, we are not going to rewrite Jangouts in just one week, but let's see how far we can go. By the way, the redesign branch contains some interesting stuff from one of the GSoC that we should consider.

Few months ago I switched my home workstation and media center to Micro OS desktop and I cannot imagine switching back to normal distribution. After some consideration I realized it should work fine (even better) on the notebook I am using for work.

Description

It can boot up from udisk/floppy.

Make a final attempt to implement a graphical user interface for grub2 (gfxboot2).

It's quite some work, unfortunately. Here's what's done so far:

Project Description

Provide image based transactional updates for MicroOS.

This is the tool I've been working on since HW11 and it needs more work. Actually, there's always something which could be done on it. It is basically an x86 instruction decoder with special emphasis on the kernel and decoding interesting pieces of it in order to help in the development of low-level patching techniques, among others. git repo: https://gitlab.suse.de/bp/x86d

The most relaxed testing framework of Kubernetes in the world

Dochazka is a long-term project to replace the obsolete Attendance & Time Tracking system used by the Prague office since 2007. Dochazka is a complex system consisting of three major components: - RESTful backend App::Dochazka::REST (with lots of help from Web::MREST)

www.opensuse.org is the single most accessed page in the SUSE/openSUSE universe. With 1.5 million visits per month it generates 2.5 million page views and has around 500 people on the page at any given time. Yet it's one of the oldest, crufty pages we have! It doesn't concentrate on what it should do: Tell people about the distro so they download it. It's design is 5 years old, it's not mobile, it's not accessible. There is absolutely no interactive, engaging content at all and the technology used goes as far as a shell script/cron to update dynamic content.

We've developed a bit of a habit within the Cloud Solutions leadership team to talk about new culinary endeavors after the weekend, telling the others about what fine dishes were created and sharing photos. We discovered that if we combine them to a menu we'll probably have the best international Dinner in the world but since we're all far away from each other we need to share the recipes to make it work. We're likely not the only ones doing that, so why not start a SUSE cookbook in a open source developer fashion, in a git repository and jointly feed - pardon - fill it with recipes for food the SUSE family likes.

openSUSE code

What is?

Project Description

The idea of this project is to produce some short videos/screencasts, maximum 5 minutes, where you show some cool feature from some of our projects/products.

Project Description

Since it has been near impossible to collaborate with other musicians at SUSE during the pandemic, I was considering an alternative music project for this Hackweek with any musicians at SUSE who might be willing to join.

Join the Gitter channel! https://gitter.im/uyuni-project/hackweek

openQA currently supports different architectures: x86(_64), ppc64le, aarch64 and s390x. In this project I would like to add support for RISC-V[1]. First emulated ontop of x86, like we previously did with aarch64. As openSUSE images for that processor are already generated, it could be useful to do some basic automated tests on them.

The situation of maintained ansible roles for boring server stuff like setting up a LEMP stack (Linux, nginx, mariadb, php) is dire and I would like to improve that. This project is about creating a handful of ansible roles with focus on * Fully supported in openSUSE (Leap and Tumbleweed)

There are various email synchronization programs like offlineimap or mbsync, which have some inherent limitations: - mbsync does not support IMAP IDLE

I have bought a Raspberry Pi 400 and would like to experiment how it integrates into SUSE ecosystem.

Project Description

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

Set up Rancher Cluster on bare metal in Provo datacenter to host SUSE infrastructure projects like JIRA, Confluence, RocketChat and Jitsi.

The recent glibc 2.33 version recently available in Tumbleweed includes this change: ```

Project Description

• Create an automated L0-support-like analytics solution for supportconfig data that is tiered across a customer's environment and SUSE environment (similar to a very modular AIOps Edge-Core approach). A pictorial overview of the ecosystem

Bug reports can be a great source of information, but usually finding the information requires extensive work in reading through all of the discussions and understanding the details about it. Could it be that machine learning can be used to extract meaningful information out of that? That's what this project is about.

Let's make reposync faster

Every day,

Goal: I will look during this project for existing tools and test suites Upstream, used by others distros (like 1) Fedora, 2) Arch-Linux, 3) Debian), and try to learn how they test, use their tool, projects.

I've attempted this several times already and each attempt had different shortcomings. I'm kind of curious about how exactly will I fail this time. And it looks like I haven't failed this time.

Language Server Protocol (LSP for friends) is used in a number of code editors these days. There are implementations for various languages, but none for Salt States. The idea is to leverage Salt state module to parse edited files to provide completion of the state ids or paths.

Project Description

Do you need to record podcasts or interviews remotely?

zypper is magic

A number of experiments suggest that it may be feasible to run zypper from an openSUSE 'live' media against a 'foreign' RPM based OS installation (eg. CentOS) and then 'zypper dup' to openSUSE

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. The potential area where this idea could have positive implications are:

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. This project has the goal to test out an automatic way to transform the Suse Manager UI into a Single Page Application.

RPMlint upstream milestone 2.0 is shaping up but there are still ticket that needs to be tackled to finalize the release and enjoy the freshness of awesome QA on Tumbleweed/SLE16. In this hackweek we plan to look on various problems as described at:

Project Description

The kdump plumbing is implemented as a dracut module. The original intention was to reuse the logic that dracut uses to deal with storage and network, but it turns out that kdump needs are often very different, so a lot of time is spent on avoiding dracut features that are undesirable.

The idea is to create a bootable medium (eg. pendrive) that allows: * Selection of either SLES, Leap or Tumbleweed.

It's been a little while since I last needed to do some binary reverse engineering, so I want to up my game. Goals

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:

Project Description

Terraform's remote backend requires a Terraform Cloud account and has an initial limited offering. While the initial offering is suitable for small resource management and teams this quickly becomes an issue as usage demands increase. In addition Terraform's remote operations (plan,apply, etc) are executed on HashiCorp's cloud resources which present issues for sensitive data such as passwords and access keys. Users are also constrained to as what tooling is available on the remote execution environment for example having kubectl as part of a local-resource. This project aims to address these shortcomings in a native Kubernetes implementation.

There is a running gag built into openQA called interactive mode. It goes like this: "if you need the interactive mode, it's broken". The reason: the so called interactive mode is a collection of hacks - in theory making it possible to update needles in a running test. But in fact it's a UI desaster that almost never works. So the goal of this hackweek project is to get rid of it - and instead build a real control from the webui into the backend allowing tests to be written on the fly including needle creation/updates. Easy as that.

Project Description

So you have an idea for a machine learning project for HackWeek. Have you thought about what tools you'll be using? Choosing the right set of machine learning tools and making them work together can be time consuming, not to mention the unavoidable learning curve. Perhaps you could use some help with that.

Project Description

krunvm is vagrant for lightweight, isolated VMs... well, at least mostly.

Project Description

Kanidm is a modern, fast, opensource IDM aiming to be an alternative to projects like 389-ds, freeipa, samba 4 and others. Inspired by many identity as a services, many features of this project aim to advance the state of what is possible with opensource security and IDM today.

Create a set of ready to use Dockerfiles based on OpenSUSE, and find a nice home for them to live in. Useful containers or just for fun, let's dockerize-it all.

Project Description

Build a tool that provides a GUI for Terraform and is able to spin up machines directly on KVM.

Project Description

During the last 3 years working on zypper we constantly reiterated the idea to refactor zypper to get rid of a lot of cruft that has collected over the years ,but just recently I realized that we maybe should go one step further.

Project Description

Did this ever happen to you?:

Learn opencv and Face recognition related knowledge to build Face recognition project on raspberry 4b

Project Description

~> osc my pkg | wc -l 699

The goal of this project is two fold. The first is to better learn and understand why Kubernetes might do something in the way that it does (especially in the control plane)

During the previous Hackweek [0], I have successfully implemented, tested and merged [1] an implementation of the entire C++ standard header <future>. This time, my aim is to modernize the C++14-esque standard library [2] of HelenOS [3][4] with a C++17 feature - the <filesystem> header. The <filesystem> header is much larger than the <future> header which I barely managed to implement and test in the allocated time for the previous Hackweek, but <future> was mostly OS-independent as it relied only on previously implemented features of the standard library. The <filesystem> header, however, is limited by the filesystem API of the OS and as such implementing of the entirety of it might not be possible, limiting the scope of the project (which is a good thing due to the time constraints). The primary features of the header [5] that should be implemented:

Project Description

openSUSE claims quite a lot of Arm boards to be supported. But we lack testing on that boards.

__Idea is to have SUSE system with OpenZFS as root FS. Main goal

I want to learn more about robotics. The goal is to have a small robot at the end of the week. Since I have no clue of what I can do with robotics / what is possible I leave it open what the

Those working remotely or managing a distributed team know it: face time is invaluable. The former openSUSE team has been using http://sqwiggle.com to keep in touch and Google hangout to hold a stand up meeting every morning. We like the Sqwiggle approach. Although the last updates have made it worse, the concept of having a peep to your colleagues' desks to know if they are there (even if they are working hard or just talking to someone) and the possibility of starting a video conversation just clicking on the face shot can do a lot in reducing distances (and in killing the temptation of working naked for home-officers).

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 wonder if, for qemu/kvm instances, it would be possible to use virtio-serial possibilities : from the guest, it is seen as a serial port, and from the outside, it is seen as a UNIX socket, or as something else. It is fast, as it does not go through virtualization and device drivers.

Project Description

It's becoming less and less likely that server-class machine support booting with legacy BIOS. The industry standard is now UEFI, and has been for 15 years; this is what vendors test and support.

Simplify the codebase by using a more modern toolkit to accelerate maintenance and future development. Enjoy Hakkaweek!

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.

Packman reduction

I'll continue the effort I started at last Hackweek to support Windows clients in Uyuni/SUSE Manager using Salt. When this is done, SUSE Manager would act as a WSUS server to Windows clients. https://hackweek.suse.com/20/projects/suse-manager-windows-client-support

Project Description

Continue the port of btrfs kernel code to fscontext, started here