All our packages have a *.changes file and ideally that file would mention relevant changes from upstream, i.e. during version updates. Currently, we find that information manually when packaging Haskell software. This is unsatisfactory because of the sheer size of the package set and the massive number of updates we receive from Hackage. The packaging itself is completely automatic, but editing the *.changes files is not and this issue prevents us from shipping more packages in Tumbleweed and elsewhere.
Now, during this Hackweek I'd like to write code that given two Haskell package versions old and new can determine the upstream changelog entries between those two and create a pleasantly formatted entry for the *.changes file that won't need any manual editing to pass the review team. Then I'd like to integrate this into cabal2obs, or maybe even cabal2spec.
RPMlint upstream milestone 2.0 is shaping up but there are still ticket that needs to be tackled to finalize the release and enjoy the freshness of awesome QA on Tumbleweed/SLE16.
In this hackweek we plan to look on various problems as described at:
I intend to work on translation of KDE to Czech language.
There are lot of typos and fuzzy messages accumulated in Summit project of KDE. I intend to work on them and increase KDE translation coverage.
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.