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).
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.
Our beloved competitor developed and use project-wide message bus called Fedora Infrastructure Message Bus. This project was already adapted, or is being adapted, also by Debian community.
During Lucky Thirteen I want to get deeply familiar with the concept and implementation, deploy test scenario and write plugins for OBS and openQA to talk to each other.
We are right now testing a patch to Janus that will hopefully give us the stability we were missing in http://jangouts.suse.de. As a consequence, it's reasonable to expect a wider usage of Jangouts inside the company. Thus, I want to share maintainership of Jangouts as much as possible. The more developers know how to fix errors and implement features, the better.
We already have a roadmap for the next two versions (0.4.0 and 0.5.0) but I don't want to spend my whole hackweek implementing those features in isolation. I would rather follow a workshop approach to welcome new contributors within the company (or outside, of course), so we get the stuff done and fix the single point of failure for the same price.
Some months ago I was diagnosed with quite some allergies and I've been using a home-made google drive spreadsheet to track everything I eat for the last 6 months in the hope to have some raw data that can be processed and I can obtain information on which exact food (or foods) produce bad symptoms.
Using a spreadsheet in the cloud is nice, but it's not perfect, so in this project I intend to write an application for android/linux (using Qt) that I can use for that.
over 4 years
3 hacker ♥️.
Has no hacker:
The plan is to gather ideas about how SUSE can become a more integral part of the local tech community scene (in PRG, NUE, or other locations).
As a person who has been involved in educating women about tech for some time, I am thinking of introductory workshops and meetups, aimed not necessarily only at female audience.
Make openSUSE the first distribution to support LetsEncrypt/ACME natively, in order to provide easy TLS encryption for all services. openSUSE users should be able to
1. Request certificates for associated host names and keep them up-to-date.
openQA currently supports different architectures: x86(_64), ppc64le, aarch64 and s390x. In this project I would like to add support for RISC-V. First emulated ontop of x86, like we previously did with aarch64.
As openSUSE images for that processor are already generated, it could be useful to do some basic automated tests on them.
For events like engineering summit or hackweeks, it would be nice to have a SUSE instance of workadventu.re, and have our own maps, wired with (open)SUSE's jitsi!
I am looking for folks willing to help on those 3 teams: