As you know, SUSE acquired Openattic last year, which is a great storage management system. I want to learn and use openattic during this hack week.

SUSE has lots of information in a jungle of tools within the company network. We want to create a platform to extract and refine (distil) the available information and display it in a meaningful manner. The overarching goal is to make available data more accessible. The initial idea sparked in a Knowledge management workshop for the SUSE Documentation Team. A first, refined version was presented as OpenDoc at openSUSE Conference 2016

[Description] I'd like to devote efforts to get the main IO paths of linux network stack from the source codes and related details, such as kernel network initialization/configurations/monitoring/analyzing issues/network traffic scenarios/workloads generating tools/firewall policies, etc.

There are several popular ways of controlling home automation with voice today. Amazon Echo and Google Home both allow users to control lights, speakers, etc. with a simple voice command. For this project, I want to replicate some of the simple voice commands supported by projects like those, but in a way that does all processing from within the local network, and doesn't upload any voice clips to a server outside the home. There's something that feels a little uncomfortable about Amazon or Google having the ability to listen in on all conversations, so I'm trying to eliminate that while still being able to turn my lights on or off by voice.

yast2-storage-ng is a reimplementation of the YaST storage module (yast2-storage) based on the also reimplemented library for storage manager

After joined Gary's BCC workshop a few days ago. The BCC is interesting to me, so I'd like to look into it. - Go through the tutorial. https://github.com/iovisor/bcc/blob/master/docs/tutorial_bcc_python_developer.md

Since eBPF was introduced into linux kernel, the eBPF verifier keeps the eBPF programs from any wrong-doing. I would like to look into the verifier and see if it's possible to extend the check to avoid reading any sensitive data in the memory.

Parametrizable formulas is a normal salt module plus some metadata in order to interactively parametrize them. The metadata is used to automatically generate forms that are then injected as pillar data. See original Hackweek project, SUSE Manager support for formulas blog article and its (internal for now) docs.

There is a number of possible improvements to the architecture of SUSE Manager / Salt integration that should be investigated in order to improve the reliability and scalability of the backend: 1. Actions are currently scheduled in the minions using the schedule module of Salt. This brings problems with reliability as for instance a minion can be down at the specified schedule time which leads to actions not being executed. Scalability can be an issue as actions being scheduled for many minions might return results to the server at the same time. Instead it might be better to keep control over scheduled actions on the server to allow batching of actions as well as downtimes of minions or even the server. There is a work in progress branch to get started.

The purpose of this project is to implement an Android application which shows some images (or dice) which you must use to create a short story. The requirements and desired features for the app are:

OpenStack is, undoubtedly, a really huge ecosystem of cooperative services. Rally is a benchmarking tool that answers the question: “How does OpenStack work at scale?”. To make this possible, Rally automates and unifies multi-node OpenStack deployment, cloud verification, benchmarking & profiling. Rally does it in a pluggable way, making it possible to check whether OpenStack is going to work well on, say, a 1k-servers installation under high load. Thus it can be used as a basic tool for an OpenStack CI/CD system that would continuously improve its SLA, performance, and stability. <img src="https://wiki.openstack.org/w/images/thumb/e/ee/Rally-Actions.png/850px-Rally-Actions.png" width="700">

I would like to learn more about ARM/AArch64 emulation in QEMU, especially the boot process and different board emulation. Goals:

Lay out a mock version of an existing SUSE R&D process in JIRA. The process should have a reasonable amount of complexity, like

terraform-provider-libvirt supports CoreOS ignition file/content, which end rendered as kernel command line options (the provider does some nice stuff like allowing you to pass the json content and it will take care of putting it into a temporary file). The idea is to:

froxlor Server Management Panel create and start a push request upstream the openSUSE Leap 42.1 configuration tab

The idea is to produce a standalone, independent tool to save and restore windows positions and sizes, analogous to a similar feature in KDE desktop. This would be handy in various lightweight desktop enviroments.

LVM support for Guix System Distribution

With GNU Guix 0.8.1 and it's distribution there is still lack of LVM support. As I'm probably the only user of LVM, I need to hack support into initrd myself.

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.

posixovl is a FUSE based successor of the old UMSDOS. It has a goal to provide POSIX file system functionality on top of vfat. Its code is nice and well written, but its feature set is not complete yet. It just supports: POSIX modes and user/group, hard and symbolic links, device nodes and named pipes. Much more can be done:

open-sTeam is a platform for cooperative work and cooperative learning developed at the university of paderborn in germany. the platform is being used at http://societyserver.org/ and is being developed further.

• 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.

GOAL

Live audio tools could use some work in openSUSE and are fun to play with. Finally many of these tools are making it into tumbleweed (And Leap 15.3) especially Cadence.

jikos:~ # tc qdisc show qdisc tbf 10: dev eth0 root refcnt 2 rate 800Mbit burst 131000b lat 1.0ms

Every packager encounters boring manual tasks every once in a while and these tasks can most probably be automated to some extent. During Hackweek I aim to try and identify such cases in various packagers' workflow and consider creating a tool that would make these tasks easier. Also, I would like to find out whether there is a demand for such tool. In that case, this Hackweek project will turn into a long-term task I plan to keep working on.

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)

In the previous hackweek (14), the following objectives from project "A generic mechanism for analysing and manipulating diverse software configuration files" were worked on: <pre>

The purpose would be to have the equivalent of Ubuntu's "apt-get autoremove" functionality. When you install package P, it might draw in dependancies D1, D2, ... Dn automatically.

There are many fun peripherials that you can connect to a RPi but PC users are not left out either * attiny85 <a href="http://www.banggood.com/ATTINY85-Mini-Usb-MCU-Development-Board-For-Arduino-p-971122.html&quot;&gt;&lt;img height="48" src="http://img2.banggood.com/thumb/large/2014/xiemeijuan/03/SKU207366/SKU207366-3.jpg&quot;/&gt;&lt;/a> has SPI and i2c interface so could be possibly used as USB<->i2c or USB<->SPI bridge. Unfortunately, the USB support needs some non-standard timings so there is quite a bit of integration and debugging needed.

Using docker as a development platform for nontrivial development environments sounds interesting. This project is about learning basic docker handling, about exploring how to use it for simplifying development, and maybe (but just maybe) about providing ready-made docker containers for new team members.

Unity3D : Moba : (Multiplayer Online Battle Arena) on SUSE Linux

This page is under development:

This is an idea that's been kicking around for a while... maybe it's finally time to "make it so." Minimally:

BPF Compiler Collection (BCC) https://github.com/iovisor/bcc