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.

Are you interested in pairing? Are you wondering whether it is something that would help you and your team members in your current project? Would you like to try it out before you fully commit to such an extreme idea? Then this is your lucky day Sir/Madam!

After an internal call for help to take over software.opensuse.org deployment, I spend some time studying the code in order to find out what would it mean to take it over.

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.

A good way of getting to know a new programming language is... writing some code. So although there are some good IRC bouncers, like ZNC, we want to write another one just for learning.

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.

2019