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,

2019

Oficina, a mechanical workshop application developed in Qt/C++ Hackweek 17: Work on TODO - Test. Make it very stable, after that, insert it in openQA.

Customers are using complex storage stacks such as LVM over dm-crypt over MD RAID over multipath over iSCSI and FC with LOTs of LUNs, and we're facing problems in that area which are usually very hard to reproduce. It's also hard to guard against regressions. Being able to quickly and reliably set up VMs with various types of storage / multipath is a key part of testing multipath. It's doable, but cumbersome and has a steep learning curve. I want to create easy-to-understand manual recipes plus scripts that are both easy to understand / customize and deploy.

While it is important for package maintainers to track the upstream code base activities and backport significant patches in a timely manner, it could be a tedious work when there's hundreds of packages in a project (ahem, GNOME) to follow manually. So I wish to get mail notifications when new commits with certain keywords (e.g. SIG, {crash, hang}{s, ing, ed}, leak(age), CVE-, https://bugzilla.gnome.org/show_bug.cgi?id=*, etc, etc) come in.

There seems to be an overall consensus that the ioctl interface used by ethtool is a poor design as it's inflexible, error prone and notoriously hard to extend. It should clearly be replaced by netlink and obsoleted. Unfortunately not much actual work has been done in that direction until this project started. The project started in Hackweek 16 (fall 2017) and has been worked on since, both in Hackweek 17-19 and outside. First two parts of kernel implementation are in mainline since 5.6-rc1, first part of userspace implementation (ethtool utility) has been submitted to upstream at the end of Hackweek 19 (2020-02-16).

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.

I would like to dedicate my time to the improvement of the Czech localization of KF5. * Trunk

Hackweek is a place for fun and things and also great things and a lot of fun. Some things don't require a reason - they are fun, that's all to it. Here goes a small competition with a lot of fun to it. Find Klaas in the office.

Try to get back an automatic email notification about new or changed SAP Notes. Since SAP has closed down some of their internal servers, which hosted an unofficial database/API to the SAP Notes, the nice email notification service of the SAP LinuxLab is terminated.

A successor of - https://github.com/viccuad/salt-configs

Ceph offers a highly scalable and fault-tolerant storage system. Samba is already capable of sharing data located on the Ceph Filesystem, however scale-out sharing (the same data exposed by multiple Samba nodes) currently requires the use of CTDB for consistent and coherent state across Samba cluster nodes. In such a setup CTDB provides a clustered database with persistent key-value data storage and locking. Database usage is abstracted out via a generic dbwrap interface. Ceph's librados library provides an API for the storage and retrieval of arbitrary key-value data via the omap functions. A watch/notify protocol is also provided as a mechanism for synchronising client state (locking). Key-value data stored in the RADOS back-end inherits the same redundancy features as regular objects, making it a potentially good candidate as a replacement for CTDB in scale-out Samba clusters.

Mottainai - Task/Job/Build Server for everyone!

Written in Golang. You can find the source code on GitHub and docs here.

Hackweek 18 Update

What Has Been Done During HackWeek 18

An initial prototype from the last hackweek can be found on YouTube Some may know the reality TV show shark tank where entrepreneurs pitch their startup ideas to get an investment. There is a German franchise of this show called "Höhle der Löwen".

Let's use the Hackweek to improve Ruby, the programming language I use every day. It is while using a language when you can realised that things that need/can to be improved, so there are many things that only Ruby developers can raise up. Also, getting involved in the development of Ruby will help to get a better understanding of how it works. So I will take my ideas/concerns to the Ruby community and implement some of the them in the code of the Ruby core. Ruby features and bugs are tracked in https://bugs.ruby-lang.org/projects/ruby-trunk/issues

There are some interesting and promising new tools for kabi checking that have been developed in the past 2-3 years (e.g. abidiff/libabigail, kabi-dw) . See if any of them prove to be viable alternatives to our current dependence on the brittle genksyms/modversions infrastructure in the kernel.

strace can parse syscall arg structures and print them in user-friendly way. For ioctl syscalls there is greater variety of the structures and not all are supported. Let's start with covering autofs data.

Fix https://gitlab.com/m2crypto/m2crypto/issues/204, see more discussion therein.

GNU Guix is a functional package manager that is also available on openSUSE Leap 15 and Tumbleweed. The goal of this project is to port it to ppc64le.

I'd like to consider the possibilities for redesigning SUSE documentation. Mark Baker ("Every Page is Page One") says "include it all, filter it afterwards" which is the exact antithesis of what we currently offer. Let's consider how we can move documentation into the future: search driven, user friendly, accessible, and in line with the way our readers use the rest of the internet.

Overview

With the recent explosion of product extensions, modules, bases, the decomposition of monolithic base products into modules, and the amount of churn in product composition between releases, the task of calculating product dependencies and migrations between products has approached the complexity of package management. We have a state of the art tool for solving package dependencies, so why not apply it to the new domain?

The current crash-setup source is located here. Pretty much is working nicely but it doesn't care for the debug source making it impossible to use the crash> gdb list *<symbol> command right away. This is bug 997558 which should be worked on.

The OpenStack Infra team has been running on the EOL'd puppet 3 for too long, they need help updating. The plan is here: https://review.openstack.org/449933

During the hackweek i want also to learn more about this topic. https://github.com/dastergon/awesome-chaos-engineering

i want to spend some day of my hackweek to improve salt-toaster https://github.com/openSUSE/salt-toaster

I want to write a new rubocop cop that verifies that a schema.rb file in a Rails project, references a valid migration.

Right now our concourse instance http://salzbreze.suse.de:8080 runs containerized (via docker-compose) on bare metal We already have a production caasp instance, so we can already move it there

I just got the FST-01G device from my friend, which could work as the Gnuk token. I'm going to try to make it work for ssh authentication.

Since Firefox 57, SUSE's default browser no longer supports XUL extensions. This is a problem for those of us who customized Firefox extensively with multiple addons. There are other Firefox forks out there, but Waterfox is based on v56, the most recent version of Firefox before the switch to Quantum -- https://www.waterfoxproject.org/en-US/

Translations get more and more important in packages live. Currently, translation-update-upstream is the only tool capable to update packages translation. It was designed 10 years ago. It is a hard to use monolithic tool that does not use advantages of openSUSE Build Service.

I use Calibre (calibre.com) in my opensuse. This tool manage ebooks, convert for many formats and control a ebook reader device. I would use my time to finish portuguese Translation to this project.

The result for xfstests in osd seems always red[1], but actually it's only a few test fail in a group(around 1/50). If we want to keep use openQA to handle those test, we need some enhancement for that. Try to enhancement test result to make it shows in a better way. - Make more reasonable group for those test

Idea is to have SUSE system with OpenZFS as root FS. Why ZFS