Currently we use openQA for the the YaST integration tests. It runs YaST in a VM and controls it via emulating keyboard input. The result is checked by comparing the screenshots. This approach has several disadvantages:

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.

there is a small security, data manipulation bug on the hackweek-tool. You can try to find it, i will then post it at the end of the hackweek

gitbot

https://github.com/MalloZup/gitbot

For testing Hawk, we're currently using a Vagrant configuration, and for testing HA releases we've been using a set of scripts originally authored by Antoine Ginies as a Hackweek project. My vague idea is to combine Terraform, Salt and a custom web frontend to make a tool that can be used by us as developers but also for others that want to try Hawk or play around with a cluster, for example for the UX team when testing modifications to the Hawk UI. I would base this on the work done by the SUSE Manager team:

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.

The goal is to reduce the number of applications installed on the mobile phone (which consequently reduces the number of ads and spyware) and transfer some of the functionality of the commonly installed apps to a personal Telegram Bot. Bots are a great way of implementing integration with external services, and, to this end, we expect the following functionality:

Oficina, a mechanical workshop application developed in Qt/C++ Hackweek 17: Work on TODO - Test. Make it very stable, after that, insert it in openQA.

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)

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.

Sonnenhut is a simple Pythong web app that provides basic info useful for planning photographic activities. The current iteration does the job, but it can be improved and extended in a number of ways. If you are interested in photography and familiar with Python, you are welcome to join and contribute to the project.

It would be nice to have trendy and hip editor [0] in openSUSE. Currently however some nodejs dependencies are missing.

What needs to be done:

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

This page is under development:

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.

The GPD Win is a Nintendo 3DS XL sized PC featuring a keyboard and gaming controls. Having openSUSE working on it would be great, unfortunately Tumbleweed doesn't work at all on it and Leap 42.2 is lacking many important features.

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

From the manual: "Org is a mode for keeping notes, maintaining TODO lists, and doing

COBOL is weird. COBOL is strange.

While osc is growing and getting more and more complex and hard to maintain, there is an object oriented rewrite of osc which key points are:

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.

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

I want to create devel project for cryptocurrencies/mining tools/blockchain related stuff, fill it with packages and submit at least some of them to Tumbleweed. Lets go on as Standa took care of creating network:cryptocurrencies

Continuing last year tweaks of packman project we should proceed in the good work and reduce the packman to provide smallest set of packages possible on Tumbleweed (later on inherited by 43.0...). One of the cool results planned is that on stock openSUSE Tumbleweed user will be able to run most of the multimedia apps and play youtube (this is already working) and also with addition of non-free repository being able to run netflix.

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 :)

https://github.com/viccuad/gomoduino Gomoduino

There is a super cool framework for mobile phone apps available: ionic (http://ionicframework.com/) ionic allows you to write apps in HTML, (Angular) JavaScript, and TypeScript for any mobile phone platforms: iOS, Android, and Windows Phone. You just need to know how to use HTML and JavaScript and you can start writing an app and convert it to any mobile phone platform.

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.

GOAL

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:

Tumbleweed wouldn't be possible without staging projects and managing staging projects isn't possible with a nice GUI. The staging dashboard is there to help but needs some love, esp when comparing

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

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.

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

Last time I checked QEMU lacked support for >= z10 processors. Thus one cannot run SLE12 and newer in a virtual machine on non-s390x host. I'd like to improve the situation during Hackweeks.

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.