Project Description

Most developers are comfortable with the workflows of git hosting services like gitlab and github, including their CI/CD capabilities. This project aims to experiment with new downstream package development and maintenance workflows based on upstream git repositories cloned at gitlab.suse.de. I'll be using the libvirt package for these experiments since it typically contains a healthy mixture of downstream-only patches along with upstream cherry picks.

Project Description

Currently gnome-remote-desktop only supports remote-assistance sessions, where a VNC connection is tied to a physical local session . WIth this use case, the monitor configuration is provided by the server (mutter/gnome-remote-desktop), and this configuration matches the physical session monitor on the server.

Project Description

OpenEMS — the Open Source Energy Management System — is a modular platform for energy management applications. It was developed around the requirements of monitoring, controlling, and integrating energy storage together with renewable energy sources and complementary devices and services like electric vehicle charging stations, heat-pumps, electrolysers, time-of-use electricity tariffs and more.

Create a openSUSE 13.2 Live CD. As enlightenment doesn't fit on the standard openSUSE CD I'd like to create a Image with it.

I have several themes in progress, they all need lots of work before they could be used with openSUSE. * The gtk people keep changing things so the gtk theme I use to match my enlightenment theme also needs fixing.

• Enlightenment already has some minimal openQA tests but more can be written.
• A extended test Setup using extra repositorys in order to run tests on upstream pre release tarballs and potentially "Nightly/Weekly" builds.

Idea is to have SUSE system with OpenZFS as root FS. Why ZFS

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

I made a smart car with raspberry pi in the hackweek18, brought up ultrasound sensor and camera module in hackweek20. Now I want to finish the remaining part of the code.