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

Hallo Welt!, the company behind Blue Spice Media Wiki (an open source, subscription based enterprise wiki) is interested in howto package their PHP software, get it into OBS and into the whole workflow with openQA and learn how to write automated tests. This is such a generic task that I though documenting it might be worth an afternoon at hackweek together with Richard (openQA) and Darix (OBS and packaging). I'll reserve a meeting room, doc team will provide the documentation of this workflow in a "SUSE best practice guide"

The goal of openQA is "test as a QA engineer". But openQA has no ears - all we can test for are DTMF sounds. And even those are very bad. So my hackweek project is to do research on how to do proper sound verification. The keys are proper normalization of the volume and the sample rate.

As we know, we have ABC notation or GNU Lilypond for music staff. It takes ASCII as input and generates music scores and even MIDI format, which is very convenient for people to type music in computer.

PXEAT (stand for PXE Administration Tool) is a tool to easily deploy and manage PXE service. It's NOT a tool for automatic deployment. It can enable user to add their own PXE items by themselves, but of course, very limited for security reasons. The tool will be developed with the light-weight framework - flask, as well as a sqlite database.

The idea would be to create a qt5/kde5 based utility that can use local raw images as well as download a list of sources from a remote site. The idea is to provide a user interface that can be used by any user as well as a user interface that can be used in kiosk mode for booths so that a visitor can put a usb pendrive in any usb slot, select the image he/she wants to write to it and get it written in parallel to other usb memories. https://github.com/openSUSE/imagewriter seems to be abandoned, so probably part of the backend will be reused and the user interface will be rewritten from scratch, but anyway this will be reconsidered at the first task in the project.

Working remotely has many advantages, but you sometimes lack some infrastructure. Specially if you use several computers or you share space with other SUSE co-workers. We are 3 Susers in Gran Canaria and we plan to share an office. So we have bought a Cubietruck, a tiny device with minimum power consumption, an ARM processor, a SATA interface and a Gigabit ethernet. The plan is to come-up with a set of recipes to configure such device to:

At SUSE LabsConf 2015 we decided to run some sort of automated tests on the SLE and openSUSE kernels after each push to kerncvs.suse.de In order to make this work the kernel has to be build, a initrd and a rootfs image has to be generated for use with qemu, it has to be booted and tests have to be run.

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

During the last CSM workshop we identified the need to have a good way to share the images we use for testing. We have documented the requirements and the current status in this wiki page (we even have a diagram). So analysis is done... it's time for action. The solution should be relatively easy to implement using our portfolio of solutions. Coordinating all the potential users should be easier during Hackweek, specially since I'll be in Nuremberg (and I can physically chase most people ;-) ).

I'm trying to write a static analyzer for Lua programming language. And I've ready done some parts, say, lexer/parser/AST/types...etc. The challenge part at present, is to write comment-based type annotation, for later type-inference. I plan to implement it in a week. I've spent years on this area. Hope I'm lucky in hackweek.

The software is a rails app with an Angular.js frontend using the gphoto2 library to trigger a Nikon D60 camera. Features: take pictures, browse pictures, automatic upload to a gallery (tumblr, flickr, owncloud), qr code for download,

Micro-service for - making a report

open-sTeam is a platform for cooperative work and cooperative learning developed at the university of paderborn in germany. the platform is being used at http://societyserver.org/ and is being developed further.

While in the past MIPS boards were either low-end PIC32 or found in routers running OpenWRT at most, Imagination themselves have recently released the Creator CI20 board (Ingenic, MIPS32) running Debian. And the Shield Pro (previously iGuardian) kickstarter project (Octeon-III, MIPS64) promises to become a playground for testing KVM hardware virtualization. Porting openSUSE to MIPS will involve setting up an OBS instance linked to Factory (update: done) and cross-compiling a set of packages for an initial bootstrap (update: in progress). Maybe this can be scripted to some degree, as there will be some overlap with the ARM ILP32 port project.

In https://github.com/SUSE-Cloud/automation/ we already have mkcloud, which can setup a whole SUSE Cloud on a single host for testing. However, it would be cool, if (instead of a single machine) we could use cloud.suse.de with its capability to add extra networks as requested. This can be pretty easy, as much of the mkcloud code is about making libvirt do the right thing

Python is well known all over the world and has wide range of usage. Lets dive into to a bit.

The Nvidia Jetson TK1 is an SBC with Nvidia Tegra K1 SoC (quad-core Cortex-A15, 32-bit ARMv7). I have openSUSE running on the Jetson TK1, but KVM is currently not usable as the CPUs are not booted in HYP mode. Thierry Reding of Nvidia has some work-in-progress for U-Boot and upstream kernel that I would like to test.

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

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

Once again, the SUSE band is coming together to make music and we're planning a party this time round!!! We have a band name :-)

Dochazka is a long-term project to replace the obsolete Attendance & Time Tracking system used by the Prague office since 2007. Dochazka is a complex system consisting of three major components: - RESTful backend App::Dochazka::REST (with lots of help from Web::MREST)

New Development In previous hack weeks, the first few days ended up being wasted on just getting it working. I'm pleased to share that the code quality has improved dramatically since the last hack week and there are now extensive test cases for both unit testing and testing against real vmcores, and we'll use both mypy and pylint (if installed) to perform static analysis. Packages for those are available in openSUSE or as part of the crash-python OBS repo for SLE15. It has been tested with kernels from 3.0 to 5.1.

Read in a crash or oops-style backtrace and access DWARF information to output the current content of the stack and registers in term of symbols, and the the crash commands to dump/pretty print them. In other words, when looking at a crash dump, answer the questions "Which variable is currently stored in $rax? What is the structure of the stack? Which variable is stored at $rsp+16?"

Status at the end of hackweek 10

froxlor Server Management Panel create and start a push request upstream the openSUSE Leap 42.1 configuration tab