In last hackweek, I implemented a RSA private key parser in kernel: https://github.com/SUSE/hackweek/wiki/RSA-private-key-parser-in-kernel

Those working remotely or managing a distributed team know it: face time is invaluable. The former openSUSE team has been using http://sqwiggle.com to keep in touch and Google hangout to hold a stand up meeting every morning. We like the Sqwiggle approach. Although the last updates have made it worse, the concept of having a peep to your colleagues' desks to know if they are there (even if they are working hard or just talking to someone) and the possibility of starting a video conversation just clicking on the face shot can do a lot in reducing distances (and in killing the temptation of working naked for home-officers).

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

The webVTT standard (nearly the same as the older SRT subtitles) allows to add subtitles to a video. We could use this in openQA to show which keys were pressed at that point in the video, in which line of code we were or on what event we waited. This could make debugging easier and might be instructive to users, too.

We have some internal systems for videoconferencing like Big Blue Button or OpenMeetings. But in my experience none of them can compare to Google Hangouts, which is still the best free (as in free beer) alternative for videoconferencing with integrated screen sharing. While implementing an alternative to Sqwiggle on previous hackweek, I discovered Janus, a lightweight WebRTC gateway that proved to be a quite capable tool to implement video applications.

We have some internal systems for videoconferencing like Big Blue Button or OpenMeetings. But in my experience none of them can compare to Google Hangouts, which is still the best free (as in free beer) alternative for videoconferencing with integrated screen sharing. While implementing an alternative to Sqwiggle on previous hackweek, I discovered Janus, a lightweight WebRTC gateway that proved to be a quite capable tool to implement video applications.

dropwatch is a utility which can help you to see if data is been dropped in linux network stack. The plan is to learn what actually dropwath can do and learn how does dropwatch work? and also learn how to use dropwatch? I'd like to get it working on openSUSE 13.2.

For Hibernate Signature Verification - HMAC version, I need a hash algorithm in EFI stub environment before ExitBootServices() to mix / mess random seed from different sources (rdtsc, rdrand...) for generating the HMAC key to sign the hibernate image in runtime environment. There have no any hash functions provides by EFI services, so need implement it in EFI stub. I choice SHA1 to be the target algorithm because currently I choice HMAC-SHA1 to be the algorithm to generate signature of hibernate image.

I previously created a semi-auto test script() for MOK. The script controls the QEMU virtual machine a pre-setup image and performs two simple test cases. It's tedious to setup the images for every SLE and openSUSE. My goal is to write a script to automatically set up the virtual machines and images and do a full test. I would also like to set up a test for weekly-built OVMF. openQA might be a good reference. () https://github.com/lcp/mok-autotest

Today OpenQA mostly runs on virtual machines, but it can get really tricky to find bugs triggered by real hardware. There are only few interfaces required to interact with a machine though: 1) HDMI<br>

VNC protocol transfers key symbols (= basically characters), not key codes (= "coordinates" on keyboard). Therefore pressing the same keys may result in sending different commands over VNC depending on the keyboard layout and state of modifiers on the client side. The server however can not directly send the key symbol to the application, it must instead find or create key code that will translate to that symbol and send that. This is hard to implement correctly and there was already several bugs about it.

By analysing a VNC session, we can create a draft of an openQA testcase (detecting keystroke, mouse click and generating fullscreen needles). The project is to :

The Idea

Since some time I am interested in getting better at C++ and learn more about Qt framework. Since I learn best with having a project/goal I came up with this:

To say it's a review, it's better to say it's a good way to learn from others. I'll review test scripts in openQA project as much as I can, digest them and learn how to write Perl script more pretty. I'll make some notes for sharing.

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.

For our daily work, usually we need to check running result from openQA as a good reference for the quality of a specific build. I'd like to take this chance to make openQA deployed and try to review the test scripts.

CodeMirror is a text editor implemented in JavaScript for the browser, openQA introduced CodeMirror in its source viewer, this project is learn more things from CodeMirror and trying to improving the source viewer in openQA, already had a ticket related, even can polish source viewer more, eg. file folding, etc.

Intel Active Management Technology (AMT) is hardware and firmware technology for remote out-of-band management of personal computers, this hackweek I'd like to spend some time to learn how to setup Intel AMT on my workstation and X201 with VNC enabled.

Recently I became a (not very proud) owner of Acer Aspire Switch 10E, a small notebook/tablet convertible based on Intel baytrail platform. Replacing preinstalled (32-bit!) Windows 8.1 with (64-bit) openSUSE proved more challenging than expected, mostly because the device is haunted by a 32-bit UEFI so that it took me a week to make it boot without an external USB flash disk. Even today, a lot of issues persist. As I do not want to waste a (partially) good hardware, I would like to make it as usable as possible. This is much less selfish than it sounds as there are many other devices based on Intel baytrail platform so that the effort is going to help their owners as well (if successful, that is).

<p>There are numerous testing tools for the GFX stack available - the oldes being the xtest suite. At the same time, we are still lacking automated test environments for the funktionalities of DRM, Mesa and X. Ideally the tests should be performed automatically and unattended and the results should be compared to previous runs to detect regressions.</p> <p>Research what tools exist to date and how they can be employed.</p>

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

The openSUSE build service could build hundreds of packages in parallel but in practice serial package dependencies prevent that.

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.

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

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

Implement a basic file search for a given OBS project. An example of basic functionality can already be found for Ubuntu or Debian. The goal is to implement,

Features

Time for technical housekeeping in the shared Gran Canaria office. For the last couple of weeks, the Cubieboard powering our "SUSE office in a box" has been unresponsive. I want to check why. Fix it, update the system, etc.

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.

Learn about ALP

https://documentation.suse.com/alp/all/html/alp/index.html