Fresh air and motion helps your brain to come up with new and creative ideas.

Build an open-source appliance editor for SUSE Studio that interacts only with the API, using modern JS web frameworks.

YaST code organization is a mess at many levels (files location, namespaces, code dependencies...). Recently we created this gist to put some of the issues on the table

In case any of the source files changed, openSUSE Build Service rebuilds the dependent packages regardless of whether that particular modification affects the dependency. This makes our resources footprint bigger (and the electrical power bills higher). It also affects users, because every new package build causes the package manager to include that package in the next update thus consuming network bandwidth and resources of users' computers.

Now we are lack of using internal wiki page to solve problem. One of the reason is that we don't know if it contain the solution we need, and it's not convenient to search it manually in wiki page. It's much more slower than using google. In one group, we are most likely facing the same problem during work. So keeping the best solution, which we got from searching engine, in internal wiki is an efficiency way to collect standard workflow.