Zeroconf/Bonjour/Avahi is a very interesting technique that targets at freeing users of services from tedious IP-based network configuration by automatic-distributed address-assigning, name-assigning and service discovery/browsing. It's named officially as zeroconf, Bonjour is the implementation in OS X, iOS and Windows, while Avahi is for Unix-like system.
However, while Bonjour is popular and widely used in Apple products, few users take advantage of Avahi in Linux world and the number of applications that do integrate Avahi are still just a few and this feature is not often used.
Wicked is a network configuration infrastructure incorporating a number of existing frameworks into a unified architecture, providing a DBUS interface to network configuration.
When developing for SUSE Manager, it gets tiresome to setup clients in order to debug and test with clients.
The idea is to create a nice shell (with history, command completion, colors) that allows to simulate being a client.
over 3 years
3 hacker ♥️.
Has no hacker:
Which package currently provides libfoo.so.6 ?
A question for/from packagers and currently not easy to answer, even if the Build Service might know about the content of packages inside a repository as he created the nice filelist.gz files inside the repomd directories with all the needed information already.
over 3 years
12 hacker ♥️.
Has no hacker:
Those working remotely or managing a distributed team know it: face time is invaluable. The former openSUSE team has been using http://sqwiggle.com to keep in touch and Google hangout to hold a stand up meeting every morning.
We like the Sqwiggle approach. Although the last updates have made it worse, the concept of having a peep to your colleagues' desks to know if they are there (even if they are working hard or just talking to someone) and the possibility of starting a video conversation just clicking on the face shot can do a lot in reducing distances (and in killing the temptation of working naked for home-officers).
Twopence is (will be) a remote execution engine for tests, able to run tests in virtual machines and real hardware through various means of communication : virtio for KVM / QEmu, ssh on top of libssh, serial lines. This library can be called from shell and ruby wrappers.
While it is already functional (and used), it still needs polishing, stabilizing, and extending. It is also planned to integrate it with Pennyworth (project Machinery) and let it go fully Open Source.
Sometimes a user might want to build her own kernel instead of using the provided binary, for various reasons. This means creating own .config and maintaining it through kernel version bumps, which often results in running "make oldconfig" and mostly holding down the enter button to accept upstream defaults.
What I envision instead is a way to say where I want my own config to deviate from the distro default (as provided by e.g. kernel-stable on openSUSE), and only those options will override the distro default configuration. This distro default configuration is always updated for new upstream releases, so there should be no need to (manually or automatically) accept new upstream defaults, thus less risk of producing a broken kernel, as e.g. any new kernel options will be configured in the distro kernel so that they work with the distro itself (while upstream defaults might not be safe or desired).
many bugs filed for openSUSE go to the screening-team by default and often remain there for weeks, so that developers (who would be interested in analyzing or fixing these bugs) do not learn about them. However, the screening process is a hard one
RandR is X11 extension for configuring monitors and since version 1.4 also secondary GPUs. These secondary GPUs can either provide additional monitors to output to or can render individual applications instead of the main GPU. (Or even both at once.) Once a secondary GPU is configured to do render offloading, applications can be started with DRI_PRIME=<id> environment variable to actually render on it instead of the main one. There are also USB GPUs (dummy framebuffers) that can be hot-plugged.
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!
It doesn't concentrate on what it should do: Tell people about the distro so they download it. It's design is 5 years old, it's not mobile, it's not accessible. There is absolutely no interactive, engaging content at all and the technology used goes as far as a shell script/cron to update dynamic content.
OpenCV (Open Source Computer Vision Library) is an open source computer vision and machine learning software library.
The goal is to get familiar with OpenCV API and with the available algorithms. Specifically, I want to look into these particular tasks:
Package a basic, stripped down version of sysvinit for emergency cases, so you can repair a failed system without interference. My goal is not to replace systemd with sysvinit again, but to provide a sysvinit-base package that does not have any dependencies at all and can just be installed on any system. sysvinit will only be used in exception situations by specifying the kernel parameter "init=/sbin/init" or something like that. The package will come with the binary, a minimal inittab and a basic boot script that does only the really needed stuff.
Experiment with an extension to have sysvinit execve systemd, so people can boot into their allmighty uber-daemon once the system has been fixed.
The virtualization team's automated testing has a long history. It was born in the old Novell Integration Test framework. The virtualization lab ran an instance of this framework for many years. Over time, those who knew the framework left the company, taking their knowledge and leaving little documentation behind. As our testing needs increased, we found the old framework insufficient, but saw little value in improving it given the available open source CI frameworks.
Before burying ourselves in SLE12 development, we took some time to move our automated tests under control of a Jenkins instance running in our lab. Tests were configured to run when new packages landed in our SLE12 devel project, ensuring our queued SLE12 submissions were continuously tested. But more is needed.
Occasionally, new versions of openQA break things. How do you stop that? MORE TESTING!
Testing openQA by using openQA to ensure the new versions don't break should be a good example of how openQA can test everything and anything, even itself.
I am using yakuake terminal with many openning tabs for my daily works, and yakuake doesn't provide the feature to save and restore the sessions.
What I want to do is to write a perl snippet to save and restore all info of yakuake including:
over 3 years
3 hacker ♥️.
Has no hacker:
Working remotely has many advantages, but you sometimes lack some infrastructure. Specially if you use several computers or you share space with other SUSE co-workers. We are 3 Susers in Gran Canaria and we plan to share an office. So we have bought a Cubietruck, a tiny device with minimum power consumption, an ARM processor, a SATA interface and a Gigabit ethernet.
The plan is to come-up with a set of recipes to configure such device to:
<p>There are numerous testing tools for the GFX stack available - the oldes being the xtest suite. At the same time, we are still lacking automated test environments for the funktionalities of DRM, Mesa and X. Ideally the tests should be performed automatically and unattended and the results should be compared to previous runs to detect regressions.</p>
<p>Research what tools exist to date and how they can be employed.</p>
Writing code is wonderful, but it gets its real value, when it's released and shipped to the world. You know the mantra: "Release early, release often".
Releasing code is not hard, but it involves a lot of details, and you want to get them right, because a release is this public statement "Hey, it's done, it works, you can use it." and you can't take a release back, once it's out there. To help with releases there are tons of release scripts which try to automate things. But they usually are quite fragile in case something goes wrong and a pain to test and maintain.
Networkmanager uses some simple dbus interfaces of firewalld to allow configuring a firewall zone for connections. FWZS offers similar features on top of SuSEfirewall2.
I'd like to adjust fwzsd to provide the minimal interfacess NM needs to offer the firewall integration.
As detailed previously on devel and opensuse-factory the KDE team didn't have access to their bugs and could not actively subscribe.
This is changed now by introduction of firstname.lastname@example.org mailinglist.
Dochazka is a long-term project to replace the obsolete Attendance & Time Tracking system used by the Prague office since 2007. Dochazka is a complex system consisting of three major components:
- RESTful backend App::Dochazka::REST (with lots of help from Web::MREST)
Since there is no real documentation about openQA's lib/ functions I wanted to kill two birds with one stone and write a parser in perl that extracts all function names (and maybe preceding comments) in said directory and improve my perl knowledge by doing this.
C3OS is a lightweight Kubernetes-focused GNU/Linux elemental derivative that optionally supports automatic node discovery, automatic role assignment and optionally VPN out of the box with no kubernetes networking configuration required.