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". Releasing code is not hard, but it involves a lot of details, and you want to get them right, because a release is this public statement "Hey, it's done, it works, you can use it." and you can't take a release back, once it's out there. To help with releases there are tons of release scripts which try to automate things. But they usually are quite fragile in case something goes wrong and a pain to test and maintain.

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 Topic 1:

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

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

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:

<https://slenkins.suse.de>

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. I am looking for your ideas, problems and examples - Feel free to join!

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). Also, it could be interesting to generate flatpak bundle directly from OBS, if possible, using either available packages or directly application sourcecode.

Geeko's Hack Week Gazette - Nürnberg Edition Provide a daily news mail what is going on during Hack Week

Discovery the latest SUSE Manager, what is missing there from user and system point of view to be use as Orthos reservation system The SUSE Manager is a great tool and his popularity is growing. It`s able to manage multiple Linux distributions from a single, centralized console. Its using by developers as well SUSE customers.

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

A software developer, in particular at SUSE, needs a reliable and robust mail client.

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.

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:

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

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

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. > Coming together is a beginning. Keeping together is a progress. Working together is a success. - Henry Ford

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)

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?

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. Come up with ideas and a prototype of how manual testing could be guided, tracked, visualized for a rolling development distribution with volunteers testing.

Motivation / Problem

Right now, our QA team tests YaST with OpenQA very much based on keyboard shortcuts: Set the keyboard focus to the "User Name" input field with Alt-U, enter a user name, [Tab] to get to the next field, enter more text, finally Alt-N to activate the "Next" button.

Hackweek 18 Update

What Has Been Done During HackWeek 18

The Kubic Project currently produces a "CaaSP-like" Tumbleweed OS, focused on Kubernetes clusters However many of the attributes of Kubic (read-only filesystem, transactional updates, containerised services) could be an interesting platform for another use A Chromebook-like Linux Desktop

Matrix.org is a project to create a protocol and server implementation to replace IRC. Unlike closed tools like Slack, or even open Slack clones like Rocket.chat, Matrix is not focused on a web-client only, but on the protocol to cover all types of clients (text, desktop, web), it is federated (no single server), and it covers good IRC integration (the public matrix server is even on Freenode), and it adds features that Slack clones have like persistent history, pictures, etc.

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

The Invis Server

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. Possible additions:

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. To find out what has gone wrong during installation YaST developers need to download the tarball containing the logs, unpack it and find the y2log among many other log files. That makes it quite complicated to just have a quick view on a problem.

Salt – The most intelligent, powerful and flexible open source software for remote execution, configuration automation, cloud control and event-driven orchestration The goal of the project is to bring its power into QAM, improving efficacy of work and possibly replacing other tools, where Salt could perform the task more naturally.

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

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? But before conquering the world, we have to start small. Let's start with GitHub! GitHub has a decent API that let's you query their system. The goal looks like this: Allow multiple clients to query information from GitHub without using the quota irresponsibly. It should also be possible to push state changes to subscribers.

The idea is to create a bootable medium (eg. pendrive) that allows: * Selection of either SLES, Leap or Tumbleweed.

Currently externaltools is deployed manually with RPM. This is a manual process and involves packaging gem dependencies. We do have a caasp cluster running internally which already hosts geekos.scc.suse.de and dash.scc.suse.de.

Effort planning in large-scale agile projects with multiple stakeholders The analysis and selection of requirements are important parts of any release planning process. Most practices focuse on release planning based on plan-driven optimization models. Nevertheless, solving the release planning problem mechanistically is difficult in an agile development context 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. This project is about improving the usability of openSUSE for gaming to appreciate the gamers who run openSUSE as their primary OS. The final goal for a number of improvements is that each gamer can play flawlessly without a single issue.

Description

Graphical application that is able to perform a git bisect on os-autoinst* tests and executes os-autoinst on it to look for the commit that introduced the regression.

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 PaaS has made deployment of applications very easy. Kubernetes has made deployment of applications very flexible but not easy. There are efforts to add the "easy" part to Kubernetes. That would make Kubernetes a good alternative to PaaS. With so many public cloud Kubernetes offerings nowadays, it would be nice if one could simply pick up their preferred cloud and have an app running in minutes. This HackWeek project will be and exploration of the available tools that can make Kubernetes as friendly as a PaaS for deployment but also how much Kubernetes can help development.

There are various email synchronization programs like offlineimap or mbsync, which have some inherent limitations: - mbsync does not support IMAP IDLE

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. Of course, we are not going to rewrite Jangouts in just one week, but let's see how far we can go. By the way, the redesign branch contains some interesting stuff from one of the GSoC that we should consider.

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

We should explore if

Out of nowhere the idea came up to organize a rum tasting session on one of the HackWeek evenings. There will be some information about the actual production of rum provided, as well as the different kind of rum existing.

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. Instead of training a neuronal network to do artificial intelligence, this project focuses on the integration of how we can make useful proposals of assignments. It will probably use perl regexps for the start.

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

• What is General Aviation? General aviation is the name or term given to all civil aviation aircraft operations with the exception of commercial air transport (CAT) or aerial work (AW). They are flight activities not involving commercial air transportation of passengers, cargo or mail for remuneration or hire, or an aerial work operation such as agriculture, construction, photography, surveying, observation and patrol, search and rescue, aerial advertisement, etc. It covers certain commercial and private flights that can be carried out under both visual flight (VFR) and instrument flight (IFR) rules, such as light aircraft, business and private jets or helicopters. General aviation thus represents the 'private transport' component of aviation. (Quoted from Wikipedia)

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. Checks I have in mind for instance are:

The Goal is... to connect all the sources of information from our houses to the lighting system to produce a dynamic home environment where information is streamed to the users through a noninvasive and disrupted channel and, this way, avoiding a chain of human micro mental interruptions, like the ones that we have during all day produced by the mobile apps notifications and/or wall panels sounds or blinks and that causes anxiety, stress, and human disconnection.

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): https://confluence.suse.com/display/openqa/QAM

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] - When we have clear idea to do something we could do month work in a week.

Goals * get used to some of this ugly buzzword tools as they are used in a broad audience

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. Part of this effort is to try to leverage what is available in this space upstream, and to focus on watching the state of CI as it exists upstream, not just in our shipping products.

openSUSE now has a lot of black magic around building distributions for :Factory and :Leap This includes all of the 000* packages and opensuse-release-tools doing very useful stuff like pkglistgen automatically managing the package lists for .kiwi files so release managers don't need to manually update which packages are going on which media

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. Refer to:

Put together a collection of ideas and resources to mentor people managers on how to make better decisions: - Useful mental models and how they work together

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. - https://aws.amazon.com/

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 What I have:

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. The service will be built in AWS/EKS within the SUSE E&I space and should be up and running on day 1, but will need love during the 5 Hackweek days to

Purpose: Use the container image to test Multi-Machine testsuite could be a nice way to reduce the network setup problem(i.g. NAT) between guest while Multi-Machine testing in openQA

Project Description

Make sure that as many as possible packages in openSUSE:Factory are up to date

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. The aim of the project is to implement stochastic bisection for git. I.e., a method that will count with the fact that test results at each point of code history have some error rate and provide points in code history to test to find commit in code history that is with high probability introducing the regression in the smallest possible number of tests. Then we can use this method for bisection of performance problems in our performance testing grid Marvin.

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

Project Description

Find where an openQA module is running

• OMM is an open source tool written in go

Project Description

This Hack Week i want to figure out how to best use Playwright to test Mojolicious applications like openQA in unit tests. Playwright is a (mostly better) alternative to Selenium for browser automation. I'd like to find a way to write entire unit tests in JavaScript, and have those run right next to existing Perl tests with the same test runner using Node Tap and the Test Anything Protocol.

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

Project Description

Project Description

openSUSE claims quite a lot of Arm boards to be supported. But we lack testing on that boards.

Project Description

Did this ever happen to you?:

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. We're likely not the only ones doing that, so why not start a SUSE cookbook in a open source developer fashion, in a git repository and jointly feed - pardon - fill it with recipes for food the SUSE family likes.

Project Description

SUSE IT needs help from fellow geekos with release engineering skills to define the requirements, process, infrastructure, and tools for building an openSUSE-based distribution bundled with SUSE IT-supported application stack. The resulting OS build will be offered as a standard distribution for new SUSE employees in addition to the existing Operating System library.

Project Description

Create views of OpenQA Test results in Grafana, grouped i.e. for Version, Builds, Flavor, Arch, in order to have a global view list, but also capability to explore details of each test, for a more integrated faults investigation environment.

Project Description

Try running openSUSE MicroOS on a home NAS.

Goal for this Hackweek

mrouted is the de facto standard for DVMRP multicast routing on Linux and other Unices.

Project Description

I'd like to explore a very popular desktop Linux distribution from last year -- the Steam Deck OS. It is said to be immutable, so I hope to get some inspiration from it to help our ALP.

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

Project Description

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

codename: opensuse-redir-cache

Project Description

The Steam Deck is a portable gaming handheld built around platform technology similar to the one found in AMD mobile laptops. Vendor Valve ships a custom Linux distribution with downstream patches on this device, but booting into other distributions is possible. Connecting the Steam Deck to a dock can turn it into a compact workstation.

Project Description

Base Linux is a new distribution developed from scratch. It aims to have the stricter packaging system, to be customizable and to work as a base for other Linux distributions in all kind of environments, from desktop to servers and embedded systems.

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.

Motivation

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.

Motivation

Project Description

Try container based openQA, including openQA webui, worker, postgres and etc. Setup complete openQA environment using various containers. I am expecting a more convenient way to deploy openQA service and, at the same time, migrate the service to another server.

Project Description

Our club has try-out trainings for kids that are interested in Ice-hockey. They can come 5 times free of charge and then they need to sign a contract. Actually this is done with excel lists which is not nice and is not working very well.

Project Description

Edge environments need highly available infrastructure but due to scale, they also need to reduce costs wherever possible. Lowering compute hardware costs by 1/3 can be the difference between success and failure in launching an edge Kubernetes offering.

Project Description

The intent of this Project is to create a website to allow the creation, posting, and sharing of Blog posts created by the Rancher QA Team. These posts will cover a broad level of subjects surrounding the Rancher space, and can be very high level walk throughs, very technical discussions, etc. This website is intended to be publicly available for viewing, and blogs will be targeted toward helping users, but contributors will only be internal.

Project Description

Make use of the Studio Kiosk in front of my office:

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

Project Description

The goals: