reading a book: <<How Google Tests Software>>a project by llzhao Project Description |
Improve mtk scripts and improve on python skillsa project by bfilho |
The Missing Middle: Add an intermediate brightness setting for auxiliary LEDs in Andúril 2a project by gkenion |
Hackweek Mini-Project: Get Started with K3sa project by parag.jain DescriptionA small, hands-on Hackweek project to learn the basics of k3s — a lightweight Kubernetes distribution. |
Build and validate a scale-out Samba/CTDB cluster atop CephFSan invention by dmdiss Samba and CTDB rely heavily on POSIX fcntl locks for data and meta-data integrity. This functionality was recently fixed in CephFS, opening up the possibility to use CephFS as an underlying filesystem for a scale-out Samba/CTDB cluster. |
All documentation as program codean invention by jsmeix I like to try out if it is possible to write a program that does not have any kind of the traditionally separated documentation (like external files that contain the documentation texts or comments in the program code). Instead all documentation must be implemented as code at the same place where the matching functiomnality is implemented (i.e. each function implements also its documentation). In the end the user should get only the executable that he can run to let it do the intended functionality and also to provide any kind of documentation. What I do not want is a dumb '--help' option that lets the program spit out its built-in documentation. What I would like to have is that the user can run the executable in some kind of self-inspecting way. I mean: While it does the intended functionality, it can also provide documentation so that the user can explore the program while running it. In the end the user experience should be more like a text adventure ;-) |
Check p2v tool (guestfs)a project by aginies Test the latest release of guesfs tools, and chech new p2v. Package it for openSUSE |
Easily Deploy an HA cluster in Virtual Machinesa project by aginies GOAL |
Use nfc device to control Raspberry Pia project by acho-novell Goal |
Add testcases introduction for kernel testsuitesa project by yosun Since sometime we have limited time to file a bug, especially during daily review of testsuites result. Then some bugs are lake of introduction about what the testsuite are tested, it makes developer take more time to debug this issue. I'd like to find a way to add some description in somewhere convenient to use, when file a kernel function bug. |