Infrastructure-by-code + full-build-pipeline with the example of OBS+openQA an invention by okurz motivation Lots of crucial steps in the SUSE/openSUSE product build workflow are not known or not even accessible by many people but hidden as "custom scripts" on "some machine" in the worst cases. Nowadays infrastructure and build pipelines should be written as code, e.g. in git repos, with UI frontends to show the always current state of what is going on, what needs to be done to release products, where are problems. The least we can do is learn a bit more in this direction. Updated over 2 years ago. 3 hacker ♥️. 1 follower.
Create packages for maintenance tools an invention by pluskalm Currently helpers for maintenance of SLE/openSUSE such as `osc omg` exist just as git repo, lets have them as packages. Updated over 5 years ago. 3 hacker ♥️.
Chrome plugin to watch openQA jobs an invention by asmorodskyi 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. Updated almost 6 years ago. 3 hacker ♥️.
Gnome applet for a wicked a project by asmorodskyi Idea is create applet with same functionality which provided by network-manager applet . Gather more detailed requirements is part of fun :) Updated almost 6 years ago. 3 hacker ♥️.
Extend urlwatch to support monitoring of GitHub (and other git) repos an idea by kbabioch I'm currently using urlwatch to watch for new releases in upstream projects. It monitors the output of a URL and notifies you about any changes. This works fine for URLs, but there is currently no official support for GitHub. Due to the nature of the GitHub webpages, there is a some change each time you access the page and it is difficult to come up with the right set of filters. Updated over 5 years ago. 3 hacker ♥️. 1 follower. Has no hacker: grab it!
Information Architecture Redesign a project by loquacity 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. Updated almost 3 years ago. 3 hacker ♥️.
Clean up the Uyuni frontend stack a project by j_renner 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? Updated almost 6 years ago. 3 hacker ♥️.
Teach rubocop about schemas and migrations a project by bergmannf I want to write a new rubocop cop that verifies that a `schema.rb` file in a Rails project, references a valid migration. Updated almost 6 years ago. 3 hacker ♥️.
Make Yast CA Mgm-Ng out of Yast RMT module an idea by ikapelyukhin Bold and crazy ideas down below, read only if you dare Updated almost 6 years ago. 3 hacker ♥️. Has no hacker: grab it!
Get a basic understanding about MD software RAID setup an invention by jsmeix I need to get a basic understanding about MD software RAID setup only via command line tools to be able to understand, Updated almost 6 years ago. 3 hacker ♥️.

Infrastructure-by-code + full-build-pipeline with the example of OBS+openQA

an invention by okurz

motivation

Lots of crucial steps in the SUSE/openSUSE product build workflow are not known or not even accessible by many people but hidden as "custom scripts" on "some machine" in the worst cases. Nowadays infrastructure and build pipelines should be written as code, e.g. in git repos, with UI frontends to show the always current state of what is going on, what needs to be done to release products, where are problems. The least we can do is learn a bit more in this direction.

Updated over 2 years ago. 3 hacker ♥️. 1 follower.

Create packages for maintenance tools

an invention by pluskalm

Currently helpers for maintenance of SLE/openSUSE such as osc omg exist just as git repo, lets have them as packages.

Updated over 5 years ago. 3 hacker ♥️.

Chrome plugin to watch openQA jobs

an invention by asmorodskyi

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.

Updated almost 6 years ago. 3 hacker ♥️.

Gnome applet for a wicked

a project by asmorodskyi

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

Updated almost 6 years ago. 3 hacker ♥️.

Extend urlwatch to support monitoring of GitHub (and other git) repos

an idea by kbabioch

I'm currently using urlwatch to watch for new releases in upstream projects. It monitors the output of a URL and notifies you about any changes. This works fine for URLs, but there is currently no official support for GitHub. Due to the nature of the GitHub webpages, there is a some change each time you access the page and it is difficult to come up with the right set of filters.

Updated over 5 years ago. 3 hacker ♥️. 1 follower. Has no hacker: grab it!

Information Architecture Redesign

a project by loquacity

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.

Updated almost 3 years ago. 3 hacker ♥️.

Clean up the Uyuni frontend stack

a project by j_renner

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?