mlin7442

Intel Rapid Start Technology(IRST) is a firmware mechanism enables your system to get up and running faster from sleep, saving time and power consumption, it will cause the system to wake up from S3 and suspend to S4(with SSD)[1]. Currently kernel 3.11 already support it[2], however there haven't a graphic tool to control its wakeup event and timeout, like as similar tool on Windows[3]. This Hackweek I'll create a YaST module to handle those parameters. [1] http://mjg59.dreamwidth.org/26022.html

Displays your openQA instance status, the feature/behavior should had at least like the list below,

Option page

CodeMirror is a text editor implemented in JavaScript for the browser, openQA introduced CodeMirror in its source viewer, this project is learn more things from CodeMirror and trying to improving the source viewer in openQA, already had a ticket related, even can polish source viewer more, eg. file folding, etc.

Intel Active Management Technology (AMT) is hardware and firmware technology for remote out-of-band management of personal computers, this hackweek I'd like to spend some time to learn how to setup Intel AMT on my workstation and X201 with VNC enabled.

We have a known defect exists in Staging Project process, according to the staging project design(in-ring/non-ring), the requests of a application stack can be dispatched to letter staging and adi staging both, in case the request staged in adi staging relies the request staged in letter staging which may causes sometimes the request in adi staging will not be checked-in at the same round, this leads that application stack have different version in TW and those package had request left in adi staging may does not work well as version unmatched to other library. We see this issue happened on Qt5 stack; KDE Applications, etc. For example: a Qt5 stack update, libqt5-qtbase will be staged in a letter staging however libqt5-qtwebview will be staged in a adi staging, once libqt5-qtbase be accepted that libqt5-qtwebview won't be accept in the same round due to it can not be built before libqt5-qtbase merged to Factory but after - 2-phase update. Therefore we need a way to handle those cases to reduce the gap between Letter staging and ADI staging. The concept of this idea:

I have a small tool called comparepkglist.py[1] which comparing packages between two build service project and it able to show the diff of package, this tool helps me to understand how many package I've missed and missing updates, it needs an improvement of the output format; show new package only; always check linkinfo; etc. [1] https://github.com/openSUSE/osc-plugin-factory/blob/master/comparepkglist.py

Aims to understand Flatpak(previously aka xdg-app), an application sandboxing and distribution framework (formerly xdg-app) on Linux. The final goal is "build my first app". Related docs: http://docs.flatpak.org/en/latest

Learn Go language by through The Go Programming Language book.

I got a Raspberry pi 4 not long ago, I'd like to install openSUSE Leap 15.2(Alpha) on it, and set up hass - Home Assistant, a open source home automation assistant on rpi4, then have some fun with it! Update: hassio dropped py3.6 support in Dec 2019, since Leap 15.2 stays with python 3.6 rather that python 3.7, I've to use Tumbleweed instead.

Project Description

As a noob in the deep learning world, I'd like to understand what is deep learning, to learn a new thing that better to find an interesting aspect, to me, face detection.

Project Description

I'm not familiar with Rancher K3S, I'm always want to have a opportunity to understand it more, since I've 3 Raspberry Pi 4, I will building a cluster on them with K3S. This will based on openSUSE 15.4.

Project Description

The Leap built ftp-tree is from a customized kiwi file, the ignored packages listed in this kiwi file is according to a predefined packagelist, not like openSUSE Tumbleweed or any other openSUSE distribution, this NON_FTP_PACKAGES file is auto-generated by a script - skippkg-finder, skippkg-finder don't support different conditional scenario, in other words, not handle the ignores for specific architecture, we found out we need this feature for some special cases, like binary rpm doesn't have an corresponding source rpm on an specific arch, the goal is aim to implement the conditional scenario support in skippkg-finder then it can generate a proper ignored packagelist into NON_FTP_PACKAGES file, and converted to a matched ignored packages into the ftp-tree file eventually.

Project Description

software.opensuse.org is a web-service part of openSUSE project which give users can search and download RPM packages from openSUSE Build Service, it has capability to mark package is released from the official distributions as a official release package, or get the package from a unsupported project, like EOL'ed distribution and/or user's personal project. I'd like dig into software-o-o source code, try to fix some known issues, like the search result from Leap 15.5 and Leap 15.4 official project has not recognized to be an official release package and are listed in unsupported projects.