Project Description

The Problem: many bugs filed for openSUSE go to the screening-team by default and often remain there for weeks, so that developers (who would be interested in analyzing or fixing these bugs) do not learn about them. However, the screening process is a hard one

Project Description

Why

I'm currently using LastPass as password manager but it has several drawbacks:

Let's make reposync faster

Learn the inner workings of TCP as implemented in the Linux kernel. This will involve

Try to use Jenkins 2.0 CI environments to trigger jobs which running in openQA

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.

What's about an app that helps you with downloading openSUSE documentation?

For years we have been discussing the idea to modularize SUSE Manager. This would enable developers to create their own extensions to SUSE Manager without needing to touch the core repository.

I want to create devel project for cryptocurrencies/mining tools/blockchain related stuff, fill it with packages and submit at least some of them to Tumbleweed.

Description

I have several future learning goals which require being proficient in C. I'd like to have this HackWeek as an opportunity to get better at the language and understand some of its advanced features like memory management and multithreading.

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.

Build Service needs an openid.