zypper is magic

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.

My idea was created out of a need in my current team(Hardware-enablement). Whilst excessive SLE testing on multiple machines i was forced to remember tons of ips to debug remotely. Since i had to reinstall new releases over and over again, ips differ, obviously.

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

L10N for the book entitled Designing with LibreOffice by Bruce Byfield

I am currently using odpdown for presentations (tl;dr: it lets you write your slides in Markdown and generates Libreoffice slides from that and a Libreoffice slide master (such as a corporate identity template)). It is currently not available in OpenSUSE so it needs to be packaged and submitted to Factory.

I am currently using odpdown for presentations (tl;dr: it lets you write your slides in Markdown and generates Libreoffice slides from that and a Libreoffice slide master (such as a corporate identity template)). It is currently not available in OpenSUSE so it needs to be packaged and submitted to Factory.

Learn how openQA was implemented in details.

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.

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.

DevOps teams face double sided challenges: development tasks should be planable and maintenance tasks should maintain their flow to provide maximum value through the queue. Build a prototype JIRA project to help them organize their workload with a Scrum board for their development tasks and a Kanban board for their maintenance work, all fed from a common backlog.

Join the Gitter channel! https://gitter.im/uyuni-project/hackweek

Description

Currently create a dev environment on Uyuni might be complicated. The steps are:

Description

Description

Description

To test, check, and verify the latest changes in the master branch, we want to easily set up an ephemeral environment.

Description

The new workflow for releasing maintenance updates for SLES 16.0 is very different from the previous (SLE 15 and before) one and involves various stages with reviews, approvals, etc. As it's rather complex and I didn't find anything like that I decided to create a flow chart based on Public Cloud packages and images - a picture explains more than a 1000 words.