Glowing Nixie Clock

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.

In day to day job I often wait for openQA job to change a state. I plan to create chrome plugin which would allow to watch for some certain job and will send you notification when run is end.

I need to get a basic understanding about MD software RAID setup only via command line tools to be able to understand,

Explore the possibility to have a self sufficient frontend server running locally. This server would compile all the frontend code and act as a proxy/middleware pointing either for a dev ref-server or to a local SUMA instance. This way would be possible to do modifications in frontend even without having a SUMA server running locally.

Some ideas from the list:

What is it about?

git-deps and hatop deserve some more native packaging love.

SSO for kanku

I want to connect to matrix.org via weechat in Leap 15.0.