Description

The current util-linux package contains a lot of tests. These tests are called during the build process. But the build environment is limited, and many of the tests cannot be ran properly.

The aim of this project is to make openSUSE/SUSE more known in Turkey, to atract students there to more participate in opensuse community:

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.

Unfortunately there is no UI designer or editor for YaST dialogs. All dialogs are hand crafted in Ruby code. The idea of this project is to provide some way how to create or edit the existing dialogs in a user friendly way, without touching any code.

I am currently using odpdown for presentations (tl;dr: it lets you write your slides in Markdown and generates Libreoffice slides from that and a Libreoffice slide master (such as a corporate identity template)). It is currently not available in OpenSUSE so it needs to be packaged and submitted to Factory.

During the last year Askbot, a question and answer oriented internet tool, similar to stack overflow has been tested for internal usage.

Following a FOSDEM presentation on Angr for binary analysis, I started packaging it in OBS.

Project Description

Project Description

Project Description

Description

Project Description

Project Description

Description

Tahoe-LAFS is an open-source decentralized cloud storage system. It distributes your data across multiple servers. Even if some of the servers fail or are taken over by an attacker, the entire file store continues to function correctly, preserving your privacy and security.

With all the changes in the qa_virtauto world, our local CI testing has become rather fragile. This project is all about stabilizing the CI testing and ensuring all builds are fully tested - without manual intervention. :)

Small non profit organisations or activist groups need a Web presence that is easy to maintain by several authors. When using a CMS they do not have the resources to secure the CMS from the various possible attacs most CMSes are notorious for. Defacement or placing malicious content can damage the reputation of such non profit organisations.

Develop a proof of concept frontend based on React and Material-UI as an alternative to the JSP/Struts based frontend currently available.

...because openQA isn't going anywhere anytime soon.

Features I'd like to implement:

Description

Project Description

We're always struggling at home with the lunches and dinners. Most of the time we realize that by the end of the week that our diet has diverged from what WHO and many other organizations suggest. My idea is to create a scalable database of meals, a web interface and some logic that generates a balanced meal plan for a 5-day or 7-day week.

Project Description

Description

Once images/repo are built from IBS/OBS, there is a tool to sync the image from IBS/OBS to openqa asset directory and trigger openqa jobs accordingly.

Description

In previous Hackweeks, we've gone to warp speed in our virtualization CI testing through:

A utility to make beautifully printed maps from OpenStreetMap data.

Basically $topic, as of the latest release of ceph, we have some not so trivial support to pull off something like this at least for metadata, need to see if data sync is also permitted, and then probably hook it to sync to AWS itself

port notmuch/muchsync to android, with some java ui on top

There are customer use cases where sharing information via internet or uploading data somewhere is not acceptable for security reasons: this avoid the usage of some tool like the most famous Google Analytics, and prevent developers from understanding how the web application is used by the customers. I don't want to reinvent the wheel and re-implement a copy of Google Analytics, but getting inspired from it, the goal is to reuse information that we already have to extrapolate an analysis of the WebApp customer usage.

Very often people find themselves wanting to store secrets in a way that either they can recover even if (for instance) their house burns down, or allow friends and family to recover if they pass away. Existing solutions to this problem are:

Current Situation [bsc#1201271]

Description

The compressed image of e.g. SLE Micro 6.0 is ~ 900Mb. ** The overall goal of this project is to make a smaller footprint (in terms of image size) flavor of the image. This is to be achieved by limiting the target use-case to simple RPi (4, 400, Pi Zero 2) server for home IoT. **

Project Description

Description

The project aims to explore how to design effective system messages and prompts tailored for AI-driven code refactoring tasks. By refining these prompts, we can guide AI models to better understand code structure, identify improvement opportunities, and execute refactorings with minimal manual intervention. The project will delve into creating system messages that balance technical detail with flexibility, enabling AI to perform refactorings that maintain code functionality while improving readability, efficiency, and maintainability.

This Hackweek I would like to finish enhancing of the mysql-packaging git repository [1]. This improvement mainly consists of scripts for a kind of simple continuous integration and git hooks to enforce a few policies for our project. If there is a time I will also take a look at the mysql package itself and check if there is anything to improve.

I heard that MVC is at the top of design pattern. I'm not sure it's true .

Adding some API documentation for Crowbar, which is still missing. There are some API comments along with the Rails controller methods, but some of them are outdated.

I want to understand the basics and architecture of KMS / DRM drivers in the kernel (also in mesa, but this project is more about the kernel-side). I will read docs and attempt to implement a virtual kernel-mode-setting driver (vkms) as described in Documentation/gpu/todo. This would be a KMS driver for a fake modesetting graphics device, just using normal system memory. This can be useful for learning, but judging from dri-developer discussions, also useful for testing hotplug races, plane blending and finding other KMS/DRI infrastructure bugs.

I will implement the ReaR upstream issue https://github.com/rear/rear/issues/1399