Occasionally, new versions of openQA break things. How do you stop that? MORE TESTING! Testing openQA by using openQA to ensure the new versions don't break should be a good example of how openQA can test everything and anything, even itself.

Use machine learning and natural language processing techniques to analyze the changes made in a project, and classify them in: * Small / unimportant fix

Python is well known all over the world and has wide range of usage. Lets dive into to a bit.

The Unreal 4 game engine has been ported to Linux! The goal will be to install Unreal 4 engine native from source on openSUSE 13.2. If successful we can work on building a small fun game using one of UE4 blueprints and game templates: Top Down, Side-Scroll, or FPS.

This is about starting to use functional programming paradigms that get used more and more? It is mainly about rewriting a small test program (repclean) in a functional style, using immutablity, parallelism and async techniques.

I'm currently using LastPass as password manager but it has several drawbacks: * closed-source

The goal is to use the work from the debug-early GCC branch to generate better debug information for LTO compiled objects, especially with regarding to language specifics like classes and templates. This has now been achieved and openSUSE Factory

Air Pollution Forecast

Summary

DAPS, the "DocBook Authoring and Publishing Suite" provides a tool set for easy creation and publication of DocBook sources on Linux. DAPS lets you create HTML (incl. webhelp), PDF, EPUB, man pages, and other formats with a single command. DAPS is used and developed by teh SUSE documentation team. The official DAPS release is 1.1.7. SUSE internally DAPS 2.0 rc2 has been released. A few issues need to be fixed (mainly closing open bugs and adding missing test cases). The goal of this project is to fix these issues, so DAPS 2.0 can be publicly released.