My car has it, nowadays every smartphone has it. But what's actually the math behind GPS (GLONASS) technique?

using perl's Inline::Python module, it should be possible to define openQA test modules in python instead of perl.

Writing code is wonderful, but it gets its real value, when it's released and shipped to the world. You know the mantra: "Release early, release often".

Given that Leap is now available, as installation media, we are going to dedicate some time to release ready to use 'Just enough Operating

using perl's Inline::Python module, it should be possible to define openQA test modules in python instead of perl.

Try to use Jenkins 2.0 CI environments to trigger jobs which running in openQA

QA wants to set up a new QA Portal to get an new organized entry point for all Information that is QA related. The Hackweek Project is to start a discussion with the different QA groups, SLE QA, CSS QA and QAM to collect ideas and make a concrete plan.

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.

reveal.js is a modern & lightweight HTML5/js-based presentation framework – much smarter than LibreOffice Impress can ever be (for a software developer). Richard Brown was so kind to create a proper LibreOffice presentation template for openSUSE and I would like to bring that design to reveal.js so next time I do a presentation I can happily use reveal.js while keeping up the openSUSE flag. :-)

Automation tools are our emotional friends. Know each other deeper and improve it, it's a way to be harmonious for our friendship.

Improving the openSUSE Websites

Utilities like git and quilt support customized difftools in some ways. It's would be great if this is introduced to osc for commands like diff, pdiff, prdiff, rdiff, rq --diff, sr --diff.

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

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

WEB_PAGES:

Distributed teams, cultural differences, expectations and habits are a natural enemy of vibrant, productive meetings (yes, meetings can be productive!). In this project I'd like to work on a different format and targeted exercises to provide ideas and a resource library to anyone interested in spicing up stale meetings.

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

Flatpak (previously known as xdg-app) is a bundle system, based on ostree, to easily make available applications bundle to users. Currently, flatpack is available on openSUSE Tumbleweed but we don't ship any runtime based on openSUSE (freedesktop or GNOME runtime).

Geeko's Hack Week Gazette - Nürnberg Edition

Discovery the latest SUSE Manager, what is missing there from user and system point of view to be use as Orthos reservation system

Investigation of the testing framework Avocado (successor of autotest) Virtualization tests within the framework - xen, kvm, libvirt, qemu tests (we have used kvm tests done in autotest framework)

Summary

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

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.

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

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.

djmount is a neat idea - see UPnP/AV resources in your directly in the file system. Unfortunately the code hasn't been maintained for ~10y, and - at least for me - seems to by plagued by various bugs causing crashes and what not. There's currently no official openSUSE package. This project aims to pick up the code, fix bugs, and make the tool actually useful again. The code itself seems to be in quite a good shape, so this should be doable.

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.

Phase 1: Melkor

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.

openSUSE Leap 42.3 goes for a rolling release model with automated openQA tests. That covers only so much though. We need manual testing too. In previous releases a google document spread sheet was used to coordinate and track the efforts.That's probably not the best method anymore.

Motivation / Problem

Hackweek 18 Update

The Kubic Project currently produces a "CaaSP-like" Tumbleweed OS, focused on Kubernetes clusters

Matrix.org is a project to create a protocol and server implementation to replace IRC.

There are a couple of interesting initiatives that make the openSUSE project interesting for SMB, such as

Since there is no real documentation about openQA's lib/ functions I wanted to kill two birds with one stone and write a parser in perl that extracts all function names (and maybe preceding comments) in said directory and improve my perl knowledge by doing this.

Quite a big part of openQA is testing the installation of SUSE products. All of them are installed by YaST. So a big quantity of problems found during openQA testruns are YaST problems.

Salt – The most intelligent, powerful and flexible open source software for remote execution, configuration automation, cloud control and event-driven orchestration

SLE Engineering have a large flatscreen in the shared space just outside of Thorsten Kukuk and Stefan Behlert's office

Within SUSE we are using various systems for different tasks. E.g. GitHub and GitLab as DVCS, Jenkins for building or testing, OBS for building… and the list continues. Some of those systems can be interconnected in some way. But not every system can do that, especially if you are behind a corporate firewall and some (I'm looking at you GitHub) have a quota. So wouldn't it be nice to have something like a Big SUSE event bus, where every event we'd be interested in could be queried or subscribed to?

The idea is to create a bootable medium (eg. pendrive) that allows:

Currently externaltools is deployed manually with RPM. This is a manual process and involves packaging gem dependencies.

Effort planning in large-scale agile projects with multiple stakeholders

Although availability of computer games on Linux has improved a lot there is way more potential for openSUSE to fire them up.

Description

Having done only very little with openQA in the past I would like to learn more about it. I would like to start writing a test suite for profanity.

Currently it's pretty difficult to create tests for some specific package. So something like TravisCI for OBS would be good.

or how to replace git push heroku master and cf push with Kubernetes

There are various email synchronization programs like offlineimap or mbsync, which have some inherent limitations:

We already tried to improve the Jangouts data model in the past and, although we made quite some progress, we did not finish it. I've been playing a bit with React and Redux lately, and I would like now to try a different approach replacing Angular with that combo. Using Vue.js might be another option too.

Metal³ is the idea to support a declarative bare metal cluster management for Kubernates by employing a simplified stand alone version of Ironic.

Out of nowhere the idea came up to organize a rum tasting session on one of the HackWeek evenings.

Well the see of openSUSE Infrastructure has been unrest and need our attention. I would like to invite you for this cruise trip.

A lot of openSUSE bugs are filed with plenty details but without a specific assignee so often many days are lost between filing and a developer seeing the report.

Currently, As QA, we design matrix for the test cases, then use matrix to generate test cases' name, then according the test cases' name to add related settings, then add those cases' name and settings to the openQA test suite. I hope, we can design matrix first, then other steps will be generated by automatically.

...because openQA isn't going anywhere anytime soon.

Instruction

Currently, way we distribute ssh keys within QAM on our testing infrustructure is a bit cumbersome - maybe we should try to (ab)use existing salt used by our internal infra team.

The monitoring in our internal infrastructure needs some love and attention. I want to spent some time during this hack week on the monitoring by fixing old checks, implementing new checks and making sure that those are configured and installed via configuration management.

The Goal is...

As the automation became a standard within Maintenance QA work, I would like to became more familiar with the whole magic behind. Plan is to go through internal docu a try to setup openQA and write some simple tests (and adjust the docu once there are any gaps):

What I do: learn the virtualization knowledge, get familiar with various ways to migrate guest, know the user's normal scenarios and requirement. Goals: give an introduction or a summary to share, including text and graphics about virtualization and guest migration.

[motivation]

Goals

So I have 469.icu :), it's currently doing nothing... (and for sale) but in the meantime, I'd like to write an url shortener from scratch and deploy it on my own server

There are a number of items related to doing Virtualization CI and testing which I have a hard time getting to during my day job. I'll take Hackweek as an opportunity to get at least a little out of my normal space and improve our methods. This mainly focuses on QEMU/KVM and some of the efforts and infrastructure I've already got in various states of development, or at least investigation.

openSUSE now has a lot of black magic around building distributions for :Factory and :Leap

I want to study the knowledge of openQA I will read the online documents and do some experiment in virtal-machine.

Many cases are Client-Server testing or Multi-Machine testing in FIPS area, I plan to hack and learn more deeply about Multi-Machine test automation in openQA.

Put together a collection of ideas and resources to mentor people managers on how to make better decisions:

The idea is to hack os-autoinst-distri-opensuse infrastucture and explore design patterns that can fit. The end point of this is to restructure the framework in such a way that the main-common.pm is more efficient, functional and readable.

Idea is to write FF plugin which would process raw autoinst log and display it in more readable form .

Take the oportunity to learn Kubernetes, to play with AWS and compare performance and availability of openQA and OBS instances and openSUSE Mirrors running on AWS.

Diagnosing issues with stalling desktop application (or a whole desktop environment) is difficult these days as the application often requires multiple processes interconnected with sockets, pipes, futexes, etc. to work and often it is not clear which process is the one responsible for blocking the whole ecosystem. The idea of this project is to write a tool that gathers information about processes in the system and for each process that is sleeping display the resource (file, socket, futex) it is waiting on as well as the process that is likely responsible for unblocking (feeding pipe, sending data to socket, unlock futex, ...). Once the information is gathered, we can also plot it for graphical displaying with tools like graphviz.

I would like to set up a small backup server on my spare hardware

Primarily to support Hackweek, but also to gain experience for a potential future corporate use, I like to run the open source Jitsi in a SUSE context and within a setup that is close to what SUSE IT is doing.

Purpose:

Project Description

Bisection is a well known method of localizing which commit caused a regression in a code repository. git-bisect is a particularly used tool for this problem in git repositories. However it is often the case that the failure is probabilistic in nature - either because we don't have a reliable reproducer of the failure and thus not reproducing a problem on a particular commit does not mean the problem is not still present there, or because of inherent variability of e.g. performance regressions. Bisection for such failures is problematic as it takes only one false result for the bisection to end up in an unrelated part of code history. So in these cases we usually have to heavily extend runtime of a reproducer or do multiple test runs or multiple bisection runs to minimize a chance of error.

Since a few months it is now possible to build an upstream QEMU which includes only our supported VCPU accelerator.

Find where an openQA module is running

Project Description

State: vm snapshoting and resume are working, but everything is still in a very hacky state.

Project Description

We've developed a bit of a habit within the Cloud Solutions leadership team to talk about new culinary endeavors after the weekend, telling the others about what fine dishes were created and sharing photos. We discovered that if we combine them to a menu we'll probably have the best international Dinner in the world but since we're all far away from each other we need to share the recipes to make it work.

Project Description

Project Description

Project Description

This is mostly a learning activity for myself, others may benefit from documentation.

Project Description

spec-cleaner is an open-source project and command-line tool for automating the process of cleaning and improving RPM specfile quality and assuring that it follows a specific style guide. It can replace old elements with new ones and reorganize the specfile so it's clean and more readable.

Project Description

Currently openQA requires a reference image to be stored to do OCR based comparisons. It is not possible to pass a character string to openQA which should be compared to the text in the screenshot.

Often when we test maintenance updates or when we decide to push an update for a package we want to know what that change may cause. Right now it is really difficult to figure out what package depends on a given package.

Sometimes you search for a package, and you don't find it because you're not typing it right. Of course there's regex support behind the scenes but it requires conscious effort to make use of.

Project Description

Project Description

Following up on the experiment from last Hackweek ( https://confluence.suse.com/display/~digitaltomm/Business+Intelligence+in+SCC ), it would be great having a production instance of Metabase running in the SCC EKS cluster, connected to the production database of SCC.

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.

Project Description

Goal

Get a closer look at how developers work on the Engineering team (R & D) of SUSE, and close the collaboration gap between GSI and Engineering

Description

SUSE Best Practices around KVM, especially for SAP workloads. Early Google presentation already made from various customer projects and SUSE sources.