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.

boot: to find logs with both kernel and user-space parts, be able to add debug flags etc. to the failing service configuration... suspend/resume: what services are configured? Something triggered via DBus? How to find? And how to debug that?

I want to understand the basics and architecture of KMS / DRM drivers in the kernel (also in mesa, but this project is more about the kernel-side). I will read docs and attempt to implement a virtual kernel-mode-setting driver (vkms) as described in Documentation/gpu/todo. This would be a KMS driver for a fake modesetting graphics device, just using normal system memory. This can be useful for learning, but judging from dri-developer discussions, also useful for testing hotplug races, plane blending and finding other KMS/DRI infrastructure bugs. Some items to implement:

The SMBIOS specification includes an informative annex providing conformance guidelines for DMI table implementations. I would like to write a checker tool to verify the conformance of DMI tables, based on this document. Such a tool could be useful for system firmware writers. We already have dmidecode which is able to locate and decode DMI tables. It should be fairly easy to reuse the same core and add an alternative structure parser, which would perform the checks instead of printing the decoded information.

It would be excellent if Hackweek projects had a standard way to include URLs for their code repositories, as well as URLs for communication methods like chat and email. This would allow folks who are interested in a project to either lurk a bit to learn more, or directly reach out to the folks running the project. While I understand that you can add these here in the Markdown, I'd like a way that's also programmatically accessible. I'd also like to be able to obfuscate email address in a way that tends to discourage or protect from spammers.

libpsoas is a C++ library for writing Ceph clients. Some of its design goals include:

Content:

Record several time lapse video for this HackWeek.

The new features below were added for the cluster (shared disk) scenario of LVM2 in upstream half year ago. I'm new to LVM2, and have been busy with bugfix things this days. This hackweek