Collecting and presenting statistics on the various aspects of the openSUSE:Factory/openSUSE:Leap:* staging process would be useful for determining if changes in tooling and automation have an impact on the workflow. Some examples or information of interest are as follows. request

Mitmproxy is a totally awesome tool to investigate http- and https-traffic and thus is a very useful debugging tool.
I built a package for mitmproxy some time ago, it resides in OBS project devel:languages:python called python-mitmproxy. This needs some love: It fails to work nowadays because its dependencies moved on, and requires an update. I am also sure there could be a better home repository for it.

Docker & Yast

Goals

Build opensource swift language package for Leap 42.3, Leap 15.0 on OBS. https://swift.org/

These project have two sub-object. * Develop a lite edition photo manage tool, use to export photos from cellphone, memory card and other usb device. It can mange the photos by Exif information (such as date, location, and lens information).

When GoldenDict enable scan popup functionality, if you want GoldenDict to show popup window, you need to select word by mouse and at same time press ALT or CTRL key. You can't show popup window only by mouse when needed. Add a function, when a word was selected by mouse, nearby the word there will be a small flag, when you move mouse on the flag, popup window appears.

For Relax-and-Recover (abbr. ReaR, RPM package rear) I like to implement a new kind of "backup" method:

Make openSUSE the first distribution to support LetsEncrypt/ACME natively, in order to provide easy TLS encryption for all services. openSUSE users should be able to 1. Request certificates for associated host names and keep them up-to-date.

https://software.opensuse.org/ is aging. Richard made a proposal using Jekyll to statically generate a new layout: https://software.opensuse.org/newsite/, code at https://github.com/sysrich/new-software.o.o

MALLOC_CHECK_ and MALLOC_PERTURB_ variables are environmental variables which help identify problems with Glibc's malloc() allocations. I intend to set them "globally" for every process via /etc/environment file and see, if test suites behave in usual way, identify problems.