hurhaj
openSUSE Landing Page Prototype
a project by hennevogel
www.opensuse.org is the single most accessed page in the SUSE/openSUSE universe. With 1.5 million visits per month it generates 2.5 million page views and has around 500 people on the page at any given time. Yet it's one of the oldest, crufty pages we have!
SSH Connection Manager
a project by jschmid1
My idea was created out of a need in my current team(Hardware-enablement). Whilst excessive SLE testing on multiple machines i was forced to remember tons of ips to debug remotely. Since i had to reinstall new releases over and over again, ips differ, obviously.
Provide tools to analyze the life-time of maintenance and release requests in IBS/OBS
an invention by psimons
We need statistical analysis and key performance indicators to describe the lifetime of maintenance and release requests in IBS, for example:
Replace ctcs2 with avocado
a project by pluskalm
We need to package avocado, get it into distro and migrate some of our testsuites from ctcs2. Atm avocado is present in openSUSE:Factory and Backports exist at my home project
bugzilla nick completion privacy extension
an idea by AndreasStieger
Bugzilla supports automatic username completion.
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.
Prototype new LTP upstream runltp script
an invention by metan
Currently the upstream LTP is executed by a hacked up and old runltp script that executes even worse and fairly old mess called ltp-pan which in turn actually executes the test cases. This whole thing is a unmaintainable mess that should have been replaced with something simpler a long time ago. It should also have a few more features that has been requested in the meantime and not implemented since nobody wants to touch the code. For instance executing the test cases on a different machine via ssh and writing the results locally. Another feature I've been thinking about for quite some time is a parallel test execution, since most of the test cases in fact could be executed in parallel which could easily speed up the test run twice. There are other tests that cannot, mostly stress tests, but also test cases that modify global system state, i.e. system time, make use of sysv IPC, use loop devices, etc. These kind of tests should be annotated somehow so that we do not end up with a test cases competing for a global resources in a parallel test run.
Little systemd utilities improvements
an invention by mkoutny
Some ideas from the list:
Improving the T-shirt size system for our Updates
a project by ONalmpantis
Suggest a new T shirt system using data mining techniques.
Learn about Rancher products
a project by mgrifalconi
Looking for projects around:
Nothing at the moment
Activity