This project is about advancing the tool you're currently browsing. It got started back in Hack Week 9 to retire all the weird tools we've used in the past to track ideas. As you can see it has gone far but is still far from done. There are lots of features missing and bugs to be fixed on github. Get going!

Meet up NBG meeting room Paris with fellow Ruby on Rails hackers, throw an editor/shell onto the wall, grab a cup of coffee and refactor OSEM code together. That way we can share knowledge about setting up the development environment, editor tricks, RSpec patterns, gems or general rails code. Interested? Join us!

Our beloved competitor developed and use project-wide message bus called Fedora Infrastructure Message Bus. This project was already adapted, or is being adapted, also by Debian community. During Lucky Thirteen I want to get deeply familiar with the concept and implementation, deploy test scenario and write plugins for OBS and openQA to talk to each other.

motivation

jenkins is a great CI system (continuous integration) with a plethora of plugins available. SUSE QA uses openQA extensively as it excels in distribution and product testing - not only image comparison (common misconception ;-) ). How about combining both in using jenkins with plugins to act as a UI for openQA?

See README for description of the Dove-eye project (poor man's Hawk-Eye). The main goal is to make 2D object tracking from a single camera more stable, so that it's reliable for 3D localization.

We have various individual tools to automate parts of the Haskell packaging process, like cabal-rpm, but those tools aren't integrated into a fully automated system that keeps Haskell packages up-to-date with as little human intervention as possible. I would like to build that system. Stackage provides us with an accurate list of packages and versions that are known to work together well, and there are basically two flavors: the nightly snapshot (bleeding edge) and the LTS release (stable API). The former is appropriate for Tumbleweed, IMHO, and the latter is appropriate for stable releases like SLE or Leap. Now, we can use cabal-rpm to generate spec files automatically for all packages in a Stackage release and check them into OBS. The process does need some tweaking, however, because cabal-rpm generates spec files that don't always work well for SUSE. We could (a) branch cabal-rpm and add SUSE-specific know-how to remedy that issue or we could (b) maintain a set of patches that adapt the generated spec files to our needs. Once the Stackage releases are available in an OBS development project, we need another automated process that submits all updated packages to openSUSE:Factory, etc.

FATE#319830, FATE#319843 and FATE#319842 propose integration of AutoYaST with different software configuration management systems like Salt, Chef and Puppet.

kanku make's installation and testing of kiwi images built by OBS very easy. https://github.com/M0ses/kanku

kanku make's installation and testing of kiwi images built by OBS very easy. https://github.com/M0ses/kanku

It is not a about make a new software. It is a service in fact. Everyone working in Beijing Office struggles with the tortoise network speed when doing zypper.