diff --git a/website/content/en/status/report-2024-10-2024-12/appjail.adoc b/website/content/en/status/report-2024-10-2024-12/appjail.adoc index a40bed9f0b..ebac7efb90 100644 --- a/website/content/en/status/report-2024-10-2024-12/appjail.adoc +++ b/website/content/en/status/report-2024-10-2024-12/appjail.adoc @@ -1,32 +1,32 @@ === Containers and FreeBSD: AppJail, Director, OCI and more Links: + -link:https://github.com/DtxdF/AppJail[AppJail on Github] URL: link:https://github.com/DtxdF/AppJail[] + -link:https://github.com/DtxdF/Director[Director on Github] URL: link:https://github.com/DtxdF/Director[] + -link:https://github.com/DtxdF/LittleJet[LittleJet on Github] URL: link:https://github.com/DtxdF/LittleJet[] + -link:https://github.com/DtxdF/reproduce[Reproduce on Github] URL: link:https://github.com/DtxdF/reproduce[] +link:https://github.com/DtxdF/AppJail[AppJail on GitHub] URL: link:https://github.com/DtxdF/AppJail[] + +link:https://github.com/DtxdF/Director[Director on GitHub] URL: link:https://github.com/DtxdF/Director[] + +link:https://github.com/DtxdF/LittleJet[LittleJet on GitHub] URL: link:https://github.com/DtxdF/LittleJet[] + +link:https://github.com/DtxdF/reproduce[Reproduce on GitHub] URL: link:https://github.com/DtxdF/reproduce[] Contact: Jesús Daniel Colmenares Oviedo AppJail is an open-source BSD-3 licensed framework entirely written in POSIX shell and C to create isolated, portable and easy to deploy environments using FreeBSD jails that behaves like an application. Director is a tool for running multi-jail environments on AppJail using a simple YAML specification. A Director file is used to define how one or more jails that make up your application are configured. Once you have a Director file, you can create and start your application with a single command: `appjail-director up`. LittleJet is an open source, easy-to-use orchestrator for managing, deploying, scaling and interconnecting FreeBSD jails anywhere in the world. Their goals are to simplify life for sysadmins and developers by providing a unified interface that automates the jail workflow by combining the base FreeBSD tools. AppJail and all its meta-projects extensively follow link:https://man.freebsd.org/cgi/man.cgi?query=appjail-ephemeral&apropos=0&sektion=0&manpath=FreeBSD+14.2-RELEASE+and+Ports&arch=default&format=html[The Ephemeral Concept] which helps update/upgrade jails more easily as they become disposable. I have used this extensively to deploy my jails with services since this concept was implemented in AppJail. Although there have been great people working on OCI for a long time, this month the featured topic is OCI, and the advances related to this technology in FreeBSD make it possible to implement it in AppJail. The latest release adds more useful features, improves on existing things and link:https://appjail.readthedocs.io/en/latest/OCI[implements OCI]. I'm continually adding more Makejails, a simple text file that automates the deployment of services in jails. -There is an organization on Github that I call link:https://github.com/AppJail-makejails[The Centralized Repository] if you want to make a contribution. +There is an organization on GitHub that I call link:https://github.com/AppJail-makejails[The Centralized Repository] if you want to make a contribution. link:https://github.com/AppJail-makejails/#status[The last improvement was to implement BuildBot as the CI/CD of AppJail images], so any change made to a repository that is tracked by BuildBot will generate a new task to build and deploy an image to the mirrors. And if mirrors are not an option, link:https://github.com/DtxdF/reproduce[appjail-reproduce] can be used to build images using your own resources. Sponsor: https://www.patreon.com/appjail diff --git a/website/content/en/status/report-2024-10-2024-12/audio.adoc b/website/content/en/status/report-2024-10-2024-12/audio.adoc index c585f04f80..3df1584e41 100644 --- a/website/content/en/status/report-2024-10-2024-12/audio.adoc +++ b/website/content/en/status/report-2024-10-2024-12/audio.adoc @@ -1,28 +1,29 @@ === 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-07-2024-09/#_audio_stack_improvements[last report]: * man:sound[4] and driver bug fixes, including panics and races. Several cleanup and refactor patches. * Committed man:mididump[1]. Ships with 14.2-RELEASE and 14-STABLE. -* Implementing link:https://reviews.freebsd.org/D47638[AFMT_FLOAT] support. This fixes ports, such as package:emulators/wine[], that require `AFMT_FLOAT` support from OSS. +* Implementing link:https://reviews.freebsd.org/D47638[AFMT_FLOAT] support. + This fixes ports, such as package:emulators/wine[], that require `AFMT_FLOAT` support from OSS. Related bug reports: link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184380[PR 184380], link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281390[PR 281390], link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264973[PR 264973], link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=157050[PR 157050]. Future work includes: * More bug fixes, optimizations and general improvements. * Implement a generic MIDI layer, similar to pcm/, and improve/modernize the MIDI codebase in general. * Implement a bluetooth device management utility. * virtual_oss patches and improvements. * Attempt to automate man:snd_hda[4] pin-patching. * Investigate SOF/DMIC support. 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-10-2024-12/bhyvemgr.adoc b/website/content/en/status/report-2024-10-2024-12/bhyvemgr.adoc index 27c3f2062d..ceb21c9395 100644 --- a/website/content/en/status/report-2024-10-2024-12/bhyvemgr.adoc +++ b/website/content/en/status/report-2024-10-2024-12/bhyvemgr.adoc @@ -1,33 +1,34 @@ === A bhyve management GUI written in Freepascal/Lazarus Links: + link:https://github.com/alonsobsd/bhyvemgr[Bhyvemgr] URL: link:https://github.com/alonsobsd/bhyvemgr/[] + Contact: José Alonso Cárdenas Márquez -Bhyvemgr is a bhyve management GUI written in Freepascal/Lazarus on FreeBSD. It needs a bunch of tools mostly installed on base system and some installed from ports/packages. +Bhyvemgr is a bhyve management GUI written in Freepascal/Lazarus on FreeBSD. +It needs a bunch of tools mostly installed on base system and some installed from ports/packages. The application is being developed for desktop users to easily and quickly setup and run virtual machines on FreeBSD hosts. During this quarter, there were many bugfixes and improvements to Bhyvemgr. These are some new features that were added: - Support for Trusted Platform Module (TPM through software via swtpm) on CURRENT - Bootvars support - Bios, system, board and chassis information can be modified - Systray icon support on almost all desktop environment (tested on Plasma, Gnome, Xfce, LXQt and IceWM) Bhyvemgr supports aarch64 only on 15-CURRENT and amd64 from FreeBSD 13.x to 15-CURRENT. Also bhyvemgr can be * compiled and installed from link:https://www.freshports.org/sysutils/bhyvemgr[ports], * installed as binaries through `pkg` with gtk2, qt5 or qt6 interface support. Anyone interested in helping or supporting the project are welcome. Current version: 1.3.1 TODO * Testing on real aarch64 hardware (aarch64 device donation for testing is welcome) * Add uart device support diff --git a/website/content/en/status/report-2024-10-2024-12/bugmeister.adoc b/website/content/en/status/report-2024-10-2024-12/bugmeister.adoc index 6400b5e129..a0a0e33c50 100644 --- a/website/content/en/status/report-2024-10-2024-12/bugmeister.adoc +++ b/website/content/en/status/report-2024-10-2024-12/bugmeister.adoc @@ -1,71 +1,72 @@ === Bugmeister Team Links: + link:https://wiki.freebsd.org/Bugzilla[FreeBSD Bugzilla] URL: link:https://wiki.freebsd.org/Bugzilla[] Contact: Bugmeister In this quarter we came even closer to steady-state; we are dealing with incoming PRs more quickly these days. For reference: link:https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html&days=90[] The overall number of PRs came down from slightly over 11,600 to right at 11,000. This was due to work from several people to go over entire groups of PRs (see below). Mark Linimon attended several video calls with various src committers. They are doing some experimentation to learn what kind of effort is sustainable. The most recent effort was to evaluate the latest incoming src PRs; you will note that many of them from the past few weeks have been marked as requesting feedback. Bugmeister folks also did some passes through the database to clean up metadata: * reassigned bugs away from committers who had had their commit bits safekept over the last year. * cleaned up bugs for Product: `Base` System Status: `In Progress`. A number of these were not being actively worked on. The count is down to 184. ** In particular, Mark Linimon believes "assigned to mailing list" means "it is not really In Progress". Perhaps it's been discussed, but we do not really have a state for that. (We can make an argument that that itself is a bug.) ** We are now down to only a handful of the above, from "too many". The concept is to make sure `In Progress` has some real meaning. * evaluated PRs for mfc-stableN. In particular, any having mfc-stable12 had that flag cleared. ** The concept is to make sure these metadata have some real meaning as well: e.g. "a commit has been made and should be evaluated for MFCs". ** There are now a much smaller number of these. * closed numerous PRs as "Overcome By Events": ** (old version) + (contains the string "boot") ** (old version) + (contains the strings "alpha" or "beta") * evaluated "PR shows a commit" (possibly via Phabricator)" and "there was no trailing discussion". ** In a few cases of the above we simply assigned them and made sure that mfc-stable[13|14] was set, if it seemed appropriate. - ** This does leave many that have a commit and then have trailing discussion. I think we will need more volunteers to go through those. + ** This does leave many that have a commit and then have trailing discussion. + I think we will need more volunteers to go through those. * removed many of the 'patch' keywords from PRs. In the optimal case these should now be imputed by metadata in each attachment. In a few cases where patches are submitted inline instead of as an attachment, the keyword stays. There may be a few of these left over from the GNATS conversion. The use of inline patches should be discouraged, as automation has no way to detect them. Thanks to our triagers, especially Alexander Ziaee. There were various discussions about bug futures that came up in various video chats. One is that there is a (supported) successor to Phabricator, which itself is now no longer developed. Multiple groups will need to coordinate to evaluate it. Jan Bramkamp has volunteered to help with the task "automate harvesting PRs and evaluating whether they still apply". Mark Linimon to collaborate. Clusteradm@ helped us fend off yet another crawler site. While that was ongoing, bugzilla was nearly unusable due to timeouts, as were other services hosted on the same machine (wiki and cgit among others). We also welcomed our newest Triage member, Lexi (aka 'ivy' on Discord). Finally, glebius was added to bugmeister@ alias as core.13 liaison. See also: link:https://wiki.freebsd.org/Bugzilla/SearchQueries[] diff --git a/website/content/en/status/report-2024-10-2024-12/gvm.adoc b/website/content/en/status/report-2024-10-2024-12/gvm.adoc index df1ba39e3d..402a197464 100644 --- a/website/content/en/status/report-2024-10-2024-12/gvm.adoc +++ b/website/content/en/status/report-2024-10-2024-12/gvm.adoc @@ -1,30 +1,30 @@ === Greenbone Vulnerability Management Community Edition Links: + link:https://www.greenbone.net/en/[Greenbone] URL: link:https://www.greenbone.net/en/[] + -link:https://github.com/greenbone/[Greenbone Github] URL: link:https://github.com/greenbone/[] + +link:https://github.com/greenbone/[Greenbone GitHub] URL: link:https://github.com/greenbone/[] + Contact: José Alonso Cárdenas Márquez The Greenbone Community Edition (GVM) covers the actual source code of the Greenbone Vulnerability Management software stack, which is also known as OpenVAS scanner, a security feed with more than 160.000 vulnerability tests, a vulnerability management application, and much more. During this quarter, package:security/gvm[] metaport was updated to 24.1.2. This update includes the following: - package:databases/pg-gvm[]: Updated to 22.6.6 - package:security/gsa[]: Updated to 24.1.0 (Only amd64 and aarch64) - package:security/gsad[]: Updated to 24.1.0 - package:security/openvas[]: Updated to 23.14.0 - package:security/gvmd[]: Updated to 24.1.2 - package:security/gvm-libs[]: Updated to 22.15.0 - package:security/py-notus-scanner[]: Updated to 22.6.5 - package:security/py-greenbone-feed-sync[]: Updated to 24.9.0 - package:security/py-ospd-openvas[]: Bump PORTREVISION - package:security/py-gvm-tools[]: Updated to 24.12.1 - package:security/py-python-gvm[]: Updated to 24.12.0 A quick GVM jail installation to test it can be done using link:https://github.com/DtxdF/AppJail[AppJail], link:https://github.com/alonsobsd/greenbone-openvas-makejail[makejail], or link:https://github.com/AppJail-makejails/greenbone-openvas[]. Anyone interested in helping with the project or interested in aarch64 device donation for testing is welcome. Current version: 24.1.2 diff --git a/website/content/en/status/report-2024-10-2024-12/ldwg.adoc b/website/content/en/status/report-2024-10-2024-12/ldwg.adoc index a49d53bf58..bbe0d50089 100644 --- a/website/content/en/status/report-2024-10-2024-12/ldwg.adoc +++ b/website/content/en/status/report-2024-10-2024-12/ldwg.adoc @@ -1,48 +1,48 @@ -=== Laptop and Desktop Workgroup (LDWG) +=== Laptop and Desktop Work Group (LDWG) Links: + link:https://lists.freebsd.org/archives/freebsd-desktop/[Desktop mailing list] URL: link:https://lists.freebsd.org/archives/freebsd-desktop/[] + link:https://wiki.freebsd.org/LaptopDesktopWorkingGroup[Wiki Page] URL: link:https://wiki.freebsd.org/LaptopDesktopWorkingGroup[] Contact: Chris Moerz -October 2024 marked the inception of the Laptop and Desktop Workgroup (LDWG), affectionately known as "Ludwig". +October 2024 marked the inception of the Laptop and Desktop Work Group (LDWG), affectionately known as "Ludwig". This initiative provides a collaborative platform for the community to engage in development, testing, knowledge exchange, and advocacy for FreeBSD on laptops and desktops. -We welcome anyone interested to join us. +Everyone is welcome to join, if interested. Scope of Work: * Content Creation: Develop recordings, articles, tutorials, documentation, and system configurations for stakeholders interested in FreeBSD on laptops and desktops. * Encouraging Contributions: Invite developers, testers, and industry experts to enhance the usability of FreeBSD on laptops and desktops. * Facilitating Collaboration: Promote code contributions, testing initiatives, operational support, and hardware insights. * Supporting User Stories and Ongoing Projects: Assist in the creation, validation, prioritization, and delivery of user stories identified in the FreeBSD Foundation’s “Laptop” investment work package. On November 16, 2024, the LDWG held its inaugural virtual meeting. The strong interest in FreeBSD for laptops and desktops was evident from the diverse group of participants, including developers, contributors, Discord community moderators, users, and FreeBSD Foundation members. Meeting slides, minutes, and recordings are available on the Group’s link:https://wiki.freebsd.org/LaptopDesktopWorkingGroup[wiki page]. -During the meeting, we identified and prioritized gaps and potential improvements in the following areas: +During the meeting, the group identified prioritized gaps and potential improvements in the following areas: * Console * Desktop Environment * Documentation * Hardware ** Graphics ** Wireless (WiFi and Bluetooth) ** USB/Thunderbolt * Installer * Performance * Software and Port Availability All activities are documented on the link:https://docs.google.com/spreadsheets/d/15btrze2sZrprSBd3Hb3YG27cZqG0AFjcvLlcTTifpIE/edit?gid=0#gid=0[Group's worksheet]. -We encourage anyone interested in contributing add their name. -If you have any planned or ongoing work, please include it in the worksheet. +The Group encourages anyone interested in contributing to add their name. +If there is any planned or ongoing work, please include it in the worksheet. Alice Sowerby provided an update on the link:https://github.com/FreeBSDFoundation/proj-laptop[The Foundation’s Laptop project], highlighting the need for volunteers to support testing efforts. The Group is running an link:https://docs.google.com/forms/d/e/1FAIpQLSd6-AOHpnae4o40CSr0tt6GlmfgfP7A9REdulJmPw9Nn0Uo_w/viewform?usp=sf_link[online survey] to gather input from non-participants. The survey will remain open until the next call in January, where results will be presented and discussed. The next call is scheduled for January 20, 2025 at 10AM PT / 1PM ET / 6PM UTC. -We hope to see you there! +Hope to see you there! diff --git a/website/content/en/status/report-2024-10-2024-12/lxqt.adoc b/website/content/en/status/report-2024-10-2024-12/lxqt.adoc index b693f3d8a5..277c520777 100644 --- a/website/content/en/status/report-2024-10-2024-12/lxqt.adoc +++ b/website/content/en/status/report-2024-10-2024-12/lxqt.adoc @@ -1,18 +1,18 @@ === LXQt on FreeBSD Links: + link:https://lxqt-project.org/[LXQt Project] URL: link:https://lxqt-project.org/[] + -link:https://github.com/lxqt/[LXQt Project Github] URL: link:https://github.com/lxqt[] + +link:https://github.com/lxqt/[LXQt Project GitHub] URL: link:https://github.com/lxqt[] + Contact: LXQt Team LXQt is an advanced, easy-to-use, and fast desktop environment based on Qt technologies. It has been tailored for users who value simplicity, speed, and an intuitive interface. Unlike most desktop environments, LXQt also works fine with less powerful machines. During this quarter, the package:x11-wm/lxqt[] metaport was updated to 2.1.0. This update adds initial link:https://github.com/lxqt/lxqt/wiki/ConfigWaylandSettings/[Wayland support] to the LXQt desktop. You can link:https://lxqt-project.org/release/2024/11/05/release-lxqt-2-1-0/[read some release highlights here]. Anyone interested in helping with the project is welcome. Current version: 2.1.0 diff --git a/website/content/en/status/report-2024-10-2024-12/torbrowser.adoc b/website/content/en/status/report-2024-10-2024-12/torbrowser.adoc index 72aafb62d0..3164a78e87 100644 --- a/website/content/en/status/report-2024-10-2024-12/torbrowser.adoc +++ b/website/content/en/status/report-2024-10-2024-12/torbrowser.adoc @@ -1,30 +1,30 @@ === Tor-Browser -Links: -link:https://www.torproject.org/[Tor Project Homepage] URL: link:https://www.torproject.org/[] +Links: + +link:https://www.torproject.org/[Tor Project Homepage] URL: link:https://www.torproject.org/[] + link:https://gitlab.torproject.org/tpo/applications/tor-browser[GitLab Repository] URL: link:https://gitlab.torproject.org/tpo/applications/tor-browser[] Contact: Martin Filla Since the last report, significant progress has been made in building and packaging Tor Browser for FreeBSD. Additionally, the Tor Browser version has been updated to 14.0.3, which is now available from the link:https://www.torproject.org/download/[Tor Browser download page] and also from our link:https://www.torproject.org/dist/[distribution directory]. This update includes important security updates to Firefox, ensuring that users benefit from enhanced security and privacy features. Expanding FreeBSD compatibility remains a priority to provide seamless and native privacy solutions for the platform. What is new: Tor Browser version 14.0.3 includes: * Rebase to Firefox 128.5.0esr. * Backporting of security fixes from Firefox 133. * Platform-specific updates such as disabling Microsoft SSO on macOS and updating GeckoView for Android. * Updated Go to version 1.22.9 in the build system. Help Needed: To move forward, assistance is required in the following areas: Code Review: Ensure patches meet the required coding and security standards. Testing: Volunteers are needed to test Tor Browser 14.0.3 on FreeBSD to identify edge cases. Bug Fixing: Developers familiar with FreeBSD and Firefox’s codebase are encouraged to resolve known issues. Feedback: If you find a bug or have suggestions for improving this release, please let us know through the link:https://gitlab.torproject.org/tpo/applications/tor-browser[GitLab Repository] or the provided contact email.