Nightwatch.js is a Node.js based End-to-End (E2E) testing solution for browser based apps. It's based on Webdrive, meaning it's a very reliable way for me to test HAWK UI! It's a great opportunity to learn Webpack, PhantomJS nightwatch and to set up a TDD approach with any new features written with vue.js, the framework which we will be using in HAWK from now on.

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:

HTTPBoot was added into UEFI SPEC since 2.5. It aims to replace PXE and provides more features. Actually, the concept of HTTPBoot is similar to PXE. It starts with the HTTP URL from the DHCP server and fetches the data with the HTTP protocol. The key difference between HTTPBoot and PXE is the support of DNS. With DNS, the firmware and the bootloader can resolve the domain name so it's possible to pass the well-known URL to download the image instead of the explicit IP URL. Besides, HTTP is designed to cross different domains, while tftp (PXE) is only for the local network. Part1:

I want to use this Hackweek to explore (Functional) Reactive Programming to be able to use it in my day-to-day work. This includes checking out basic literature about (F)RP as well as domain modelling to get a better understanding, when this paradigm makes sense to use, as well as looking into concrete implementation of (F)RP libraries.

Take the source rpm of a package (e.g. systemd), find the upstream tests, run them, store the results to a database that a web ui can access and display them. Now, do this automatically, for every qam-sle update.

It is always nice to extend the translations for openSUSE packages/projects using Weblate.
Everyone is encouraged to improve on his native language.

I want to get started with developing apps for phones and tablets. It is a very general idea, rather open ended. To have tangible results, I want to make a trivial app and publish it in the official Google Play store: Just Roll One Die.

I plan to learn openQA during this hack week. Below are the details: - Basic concepts

In general plan for YaST is to use ruby only in future. So goal of this project is to move it forward and replace more parts with ruby. Current ideas is to replace binary y2base with ruby script, which allows easier integration with ruby tools and more important it solve some issues with embedding ruby, as it will be then first citizen.

There have some kernel mechanisms that they keep symmetric key or password in memory. Those password or key may leak through /dev/mem, kdump, hibernation, bpf print to userland. I want to think a design to:

Phase 1: Melkor

After gathering the feedback of qam (transcription of brainstorming for problems and requirements), it's time to start fixing things. Let's build the first step of a shipping skeleton solution that addresses all of the problems listed in the aforementioned document. (draft)

In the last hackweeks and my free time, I've been developing several tools to various degrees of completion. The purpose of this hackweek is to finish three of them, publish them on github and create openSUSE packages. * finddupmusic

Hackweek is here! I think this is the best week of the year to sit down altogether and exchange ideas and suggestions. The main topic is Automation. The goal is that many of these ideas might help various teams within SUSE to engage their business reasons better in defining key expectations and improve the quality of our software products. No fear of change -- the aim is to propose a modern pipeline in a less-invasive manner. Everybody has an idea, everybody has a voice! Brainstorming together can be useful to many different roles, including testers, analysts and developers. Let's have a chit-chat and write down some of those; Hopefully we will come up with plenty of tips on how to organise testing activities better.

Coming together is a beginning. Keeping together is a progress. Working together is a success. - Henry Ford

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.

I promised to start this project way earlier, but I think Hackweek will be a great time to make a start. The project once was called $BABELFISH, later "Rumsfeld", to honor the creator of the "Unknown unknowns" meme, now it's name is Maxfeld.

libmarpa is an parsing library based on Earley's algorithm, by Jeffrey Kegler.