This is about starting to use functional programming paradigms that get used more and more? It is mainly about rewriting a small test program (repclean) in a functional style, using immutablity, parallelism and async techniques.

Some people prefer LaTeX for creating documents and presentations. The templates provided by Marketing don't include one for Beamer

As every hackweek, lets package/update/cleanup some stuff fore factory: Update/package:

How many times have you created quick and dirty script to generate C tables, parameterized code, etc. ? Did the script ended up messy?

The Unreal 4 game engine has been ported to Linux! The goal will be to install Unreal 4 engine native from source on openSUSE 13.2. If successful we can work on building a small fun game using one of UE4 blueprints and game templates: Top Down, Side-Scroll, or FPS.

Cover more cornercases for spec-cleaner to allow the swap of formatspecfile due to its bugginess in comparsion.

We are using various tools, many of them are not yet in Tumbleweed (such as rst2html5, git-pimp and so on), aim of this project is to get them there.

"Let’s Encrypt is a new Certificate Authority: It’s free, automated, and open."[1]

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.

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.

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

I want to start working on translations which might be useful in our work (to focus on apps used by us during our work) and to push the rate of translation a bit further.

Supporttools are great and useful utilities to help support and development

We want to improve translation of dependencies done by spec-cleaner (i.e. cmake(blah)) and so on - see github.

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

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

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:

openQA has a well earned reputation as a 'full system' testing tool, able to test a system end-to-end from the operating system to it's applications on a number of different platforms and architectures, including VM's & Bare Metal. But one area of weakness is it's usefulness as a testing tool for developers or packagers. openQA can easily test a package once it's INSIDE a distribution, but how do you test that package BEFORE submitting it to the distribution?

We need to package avocado, get it into distro and migrate some of our testsuites from ctcs2. Atm avocado is present in openSUSE:Factory and Backports exist at my home project

To make OpenQA work with real ARM devices, we need to control * Reset

An introduction from minetest website: " Minetest is a near-infinite-world block sandbox game and a game engine, inspired by InfiniMiner, Minecraft, and the like. Minetest is available natively for Windows, OS X, GNU/Linux, Android, and FreeBSD. It is Free/Libre and Open Source Software, released under the LGPL 2.1 or later. " In short, MineTest is a Free and Open Source re-implementation of MineCraft, but it provide many flexible features compare MineCraft. It's not only a game but also a framework for developers to extend so to make their own worlds.

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.

As in near future, there will be python2python3 in Factory but no /usr/bin/python and in SLE-15 base no python2 it is necessary to start checking/switching dependencies. See also:

Overview

With the recent explosion of product extensions, modules, bases, the decomposition of monolithic base products into modules, and the amount of churn in product composition between releases, the task of calculating product dependencies and migrations between products has approached the complexity of package management. We have a state of the art tool for solving package dependencies, so why not apply it to the new domain?

Hackweek 21?

Postmaster desperately needs a mail spool. I need to come up with a good way to store meta information about queued messages. An sqlite database seems like a natural fit because I might want to do some nontrivial queries in there to figure out which messages to deliver (and where). On the other hand, interfacing with sqlite is a bit unpleasant, so instead I might want to write one big JSON file that contains all relevant information. That would certainly suffice for the first version ...

I am a beginner: I have read 1½ books on Haskell. I want to practice. Haskell is a purely functional, lazily evaluated, strongly typed (with

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: