diff --git a/website/content/en/status/report-2024-04-2024-06/audio.adoc b/website/content/en/status/report-2024-04-2024-06/audio.adoc index a7e759f7e8..502c8a16fe 100644 --- a/website/content/en/status/report-2024-04-2024-06/audio.adoc +++ b/website/content/en/status/report-2024-04-2024-06/audio.adoc @@ -1,31 +1,33 @@ === Audio Stack Improvements Contact: Christos Margiolis The FreeBSD audio stack is one of those fields that does not attract the same attention and development as others do, since it has been left largely unmaintained, and, although high in quality, there is still room for improvement -- from lack of audio development frameworks, to missing userland utilities and kernel driver-related bugs. This project is meant to touch on all those areas, and as such, is more of a general improvement project, than an implementation of a specific feature. Important work since link:https://www.freebsd.org/status/report-2024-01-2024-03/#_audio_stack_improvements[last report]: * Asynchronous audio device detach link:https://cgit.freebsd.org/src/commit/?id=44e128fe9d92c1a544b801cb56e907a66ef34691[is now possible]. This functionality already ships with FreeBSD 14.1-RELEASE, as well as 14-STABLE. -* Got rid of the "snd_clone" device cloning framework used in man:sound[4] and replaced it with DEVFS_CDEVPRIV(9). More info about behavior changes in the link:https://cgit.freebsd.org/src/commit/?id=e8c0d15a64fadb4a330f2da7244becaac161bb70[commit description]. Also ships with 14.1-RELEASE and 14-STABLE. +* Got rid of the "snd_clone" device cloning framework used in man:sound[4] and replaced it with DEVFS_CDEVPRIV(9). +More info about behavior changes in the link:https://cgit.freebsd.org/src/commit/?id=e8c0d15a64fadb4a330f2da7244becaac161bb70[commit description]. +Also ships with 14.1-RELEASE and 14-STABLE. * Several man:sound[4] crash and bug fixes. * More out of the box support for man:snd_hda[4] laptop sound. * Series of commits that clean up and simplify parts of man:sound[4]. * Several fixes regarding the OSS API, with the most notable so far being a link:https://cgit.freebsd.org/src/commit/?id=e07f9178502b7cbc0769fc10e99ad0d013f437fd[proper implementation] of the `SNDCTL_AUDIOINFO` and `SNDCTL_ENGINEINFO` IOCTLs. * Started implementing man:audio[3], an OSS audio and MIDI library. * Took over maintenance of man:virtual_oss[8]. Future work includes: * Implementation of an man:audio[8] utility, in similar fashion to man:mixer[8]. * Implementation of a bluetooth device management utility. * Improve man:mixer[3] and man:mixer[8]. * Improve documentation and test suite where needed. * Attempt to find a better (ideally automatic) way to handle man:snd_hda[4] pin-patching. This is an experimental attempt and is not guaranteed to actually yield a working result. You can also follow the development process in link:https://lists.freebsd.org/subscription/freebsd-multimedia[freebsd-multimedia@], where I post regular reports. Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2024-04-2024-06/capsicum-rs.adoc b/website/content/en/status/report-2024-04-2024-06/capsicum-rs.adoc index bef15d253c..4197e746f7 100644 --- a/website/content/en/status/report-2024-04-2024-06/capsicum-rs.adoc +++ b/website/content/en/status/report-2024-04-2024-06/capsicum-rs.adoc @@ -1,19 +1,14 @@ -=== capsicum-rs +=== Capsicum-rs Links: + link:https://github.com/dlrobertson/capsicum-rs[capsicum-rs on GitHub] URL: https://github.com/dlrobertson/capsicum-rs[] link:https://github.com/asomers/capsicum-net[capsicum-net on GitHub] URL: https://github.com/asomers/capsicum-net[] Contact: Alan Somers -Capsicum is a lightweight OS capability and sandbox framework implementing a -hybrid capability system model. +Capsicum is a lightweight OS capability and sandbox framework implementing a hybrid capability system model. -I've adopted the library providing Rust bindings for Capsicum, and extended it -with support for man:libcasper[3] and man:cap_net[3]. -It's already being used by package:net-mgmt/nfs-exporter[] and by a TLS-enabled -FTP server (the FTP server is closed-source, but all of the interesting bits -reside in an open source library, and an example server can be found at -link:https://github.com/bolcom/libunftp/tree/master/crates/unftp-sbe-fs/examples[]). +I have adopted the library providing Rust bindings for Capsicum, and extended it with support for man:libcasper[3] and man:cap_net[3]. +It is already being used by package:net-mgmt/nfs-exporter[] and by a TLS-enabled FTP server (the FTP server is closed-source, but all of the interesting bits reside in an open source library, and an example server can be found at link:https://github.com/bolcom/libunftp/tree/master/crates/unftp-sbe-fs/examples[]). Sponsor: Axcient diff --git a/website/content/en/status/report-2024-04-2024-06/github.adoc b/website/content/en/status/report-2024-04-2024-06/github.adoc index 97eceda17e..be5a1348fa 100644 --- a/website/content/en/status/report-2024-04-2024-06/github.adoc +++ b/website/content/en/status/report-2024-04-2024-06/github.adoc @@ -1,39 +1,39 @@ === FreeBSD GitHub Pull Request Report Links: + link:https://wiki.freebsd.org/WorkingGroup/Github[GitHub Working Group wiki page] URL: link:https://wiki.freebsd.org/WorkingGroup/GitHub[] + link:https://github.com/freebsd/freebsd-src/pulls[FreeBSD Base System Pull Requests] URL: link:https://github.com/freebsd/freebsd-src/pulls[] Contact: Warner Losh The FreeBSD Project has been trying an experiment to accept contributions via GitHub pull requests. We have learned a lot in the last year that we've been doing this. We have created a number of rules relating to the pull requests. In general, pull requests should only be for things that are user-visible, add value to the project and are ready to go, modulo final review. Current status: * We are able to keep up with the pull requests doing everything by hand, but only if we do it at least weekly. * We have discovered the by-hand process is tedious and error-prone. * We can stage multiple pull requests in a testing branch so we can batch-up testing. * We can automatically land the result so merged pull requests show up as merged in GitHub infrastructure. We need help with automating the process: - * Add automated testing that's context specific (for example, run igor over man pages). + * Add automated testing that is context specific (for example, run igor over man pages). * Add build/install tests that test-boot the resulting image. * Automate common tasks, like man page corrections, into staging process. * Add simple smoke testing for the staging branch for tier 1 architectures. * Investigate optionally integrating Jenkins testing to scale up the size of changes we can accept. * Integrate with Bugzilla problem reports and Phabricator reviews. * Improve the submitter experience on GitHub by automating common feedback to mistakes in the pull requests. * Create checklists for submitters to reduce errors. * Create better reporting about pull requests, especially the frequent contributors of good pull requests. We are coordinating on FreeBSD's Discord in the #github-hacking channel. Join us there to pitch in, or just chat about the project. Once things are fine-tuned, we want to publicity to steer contributors, at least the base system, to GitHub pull requests. We need more developers looking at the FreeBSD GitHub pull requests. We will also need more developers to review and land pull requests once it is automated and the automation has matured. We sincerely hope that we can improve the FreeBSD contribution experience with this, as well as gain useful fixes from the community. diff --git a/website/content/en/status/report-2024-04-2024-06/kde.adoc b/website/content/en/status/report-2024-04-2024-06/kde.adoc index 5aca5509dd..981fb6c324 100644 --- a/website/content/en/status/report-2024-04-2024-06/kde.adoc +++ b/website/content/en/status/report-2024-04-2024-06/kde.adoc @@ -1,39 +1,39 @@ === KDE on FreeBSD Links: + link:https://freebsd.kde.org/[KDE/FreeBSD initiative] URL: link:https://freebsd.kde.org/[] + link:https://community.kde.org/FreeBSD[FreeBSD -- KDE Community Wiki] URL: link:https://community.kde.org/FreeBSD[] Contact: Adriaan de Groot The KDE on FreeBSD project packages CMake, Qt, and software from the KDE Community, for the FreeBSD ports tree. The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine. -The mailto:kde@FreeBSD.org[KDE team] is part of mailto:desktop@FreeBSD.org[desktop@], building the software stack to make FreeBSD beautiful and usable as a daily-driver graphical desktop workstation. +The mailto:kde@FreeBSD.org[KDE team] is part of mailto:desktop@FreeBSD.org[desktop@], building the software stack to make FreeBSD beautiful and usable as a daily driver graphical desktop workstation. We missed a quarter, while the broader KDE community celebrated the KDE Megarelease of KDE Frameworks 6, KDE Plasma 6 and KDE Gear. The latest software is still not available on FreeBSD, pending more testing and some integration work. ==== Infrastructure CMake was updated several times and is now version 3.29.6, the latest upstream release. CMake in the ports framework now supports setting parallel-build for tests. Qt5 is now on long-term support and updates only rarely. An update to 5.15.14 and WebEngine to 5.15.17 was landed in May. Qt6 and the Python bindings for Qt, Pyside, were updated to version 6.7.2. ==== KDE Stack KDE Gear, Plasma and Frameworks release happen very regularly. These updates arrive in the FreeBSD ports tree only piecemeal, due to lagging work on compatibility and testing. * KDE Frameworks reached version 6.3.0 * KDE Plasma 6 Desktop was updated to version 6.0.4 * KDE Gear 6 has not yet arrived in the ports tree ==== Related Ports The KDE ecosystem includes a wide range of ports -- most maintained by mailto:kde@FreeBSD.org[kde@], all building on a shared base of Qt and KDE Frameworks. The mailto:kde@FreeBSD.org[KDE team] updates them all as needed. This quarter the KDE team would like to thank mailto:tcberner@FreeBSD.org[Tobias C. Berner], mailto:arrowd@FreeBSD.org[Gleb Popov] and mailto:jhale@FreebSD.org[Jason E. Hale] again for keeping things up-to-date.