Hackweek 18 Update

Idea is create applet with same functionality which provided by network-manager applet . Gather more detailed requirements is part of fun :)

I'd like to consider the possibilities for redesigning SUSE documentation. Mark Baker ("Every Page is Page One") says "include it all, filter it afterwards" which is the exact antithesis of what we currently offer. Let's consider how we can move documentation into the future: search driven, user friendly, accessible, and in line with the way our readers use the rest of the internet.

Many of the Uyuni / SUSE Manager web UIs are still based on the no longer maintained Struts framework (version 1.2!) and implemented as JSP pages, while we added newer features based on the Spark framework and React. For me there is a vision of using only one technology stack (especially just one web framework, frontend framework and template engine) eventually, so it is about time to get rid of the old stack. While this is surely a huge effort, why not start with a new login page and then go from there rewriting other pages one by one?

I want to write a new rubocop cop that verifies that a schema.rb file in a Rails project, references a valid migration.

Currently Salt is using supportconfig utility alongside with the SUSE Manager installation. Every single bugreport for Salt, that contains its logs are always useless that regard. It might work for SUSE Manager, but for Salt it doesn't. And even after asking user to switch the cluster into a debug mode or even trace mode, it is still far away from being useful enough, so the supporter don't need to dance with the tambourine around the fire, guessing what ghost just munged what component.

At SUSE/openSUSE we are using (at least some times) Etherpad, whose functionality is really limited and looks as taken from the past. After taking a look to other possible Open Source alternatives, I think there is at the moment any which offers all the feature I would like to have. Because of that I would like to contribute to JetPad, with the idea of using it privately and that it can also be used by SUSE/openSUSE.

Intel Chen Yu developed a user land utility:

See Jonathan Dieter's chunk project.

We often struggle to get feedback from our people, in particular if it's supposed to be anonymous. There are external systems on the Internet which are typically commercial, where (free) usage is limited and situation with GDPR isn't clear.