diff --git a/website/content/en/status/report-2024-10-2024-12/framework.adoc b/website/content/en/status/report-2024-10-2024-12/framework.adoc index 564e7dd8eb..7633303a04 100644 --- a/website/content/en/status/report-2024-10-2024-12/framework.adoc +++ b/website/content/en/status/report-2024-10-2024-12/framework.adoc @@ -1,27 +1,27 @@ === Framework Laptop support Links: + link:https://wiki.freebsd.org/Laptops/Framework_Laptop/[Framework Laptop page on FreeBSD Wiki] URL: https://wiki.freebsd.org/Laptops/Framework_Laptop/[] + link:https://github.com/FrameworkComputer/freebsd-on-framework[Guide on installing and using FreeBSD on Framework systems] URL: https://github.com/FrameworkComputer/freebsd-on-framework[] + link:https://bugs.freebsd.org/262152[Tracking ticket: Framework Laptop: Feature support, bugs and improvements] URL: https://bugs.freebsd.org/262152[] Contact: Daniel Schaefer + Contact: Li-Wen Hsu + -Contact: SHENG-YI HONG +Contact: Sheng-Yi Hong For a long time, Framework Laptop Inc is friendly to the FreeBSD project in many aspects, including providing engineering samples to Foundation for testing and working on support. Since 2024 summer, there are several small hackathons in Framework's Taipei office on testing FreeBSD on different models of Framework laptop, and the peripheral devices. Sheng-Yi is using the laptop provided by Framework Computer to add more device support, e.g. https://cgit.freebsd.org/src/commit/?id=d3b05d0ea10abe059dc63c6fb6ef3f061b758af2[d3b05d0ea10a: Add smbus and i2c device IDs for Meteor Lake]. Daniel from Framework Computer Inc started link:https://github.com/FrameworkComputer/freebsd-on-framework[a repository under Framework Computer's GitHub organization] to keep the notes of installation and miscellaneous information. He fixed fingerprint readers (libfprint) not just for Framework, but in general on FreeBSD. And working on the supoprt and fix to many related drivers on FreeBSD. In November, Foundation people and some FreeBSD developers visited Framework's San Francisco office and had a meeting for checking the current FreeBSD support status and discussing the possible future collaboration plans. Foundation will continue working on improving the general laptop support and using Framework as one of the link:https://github.com/FreeBSDFoundation/proj-laptop/blob/main/supported/laptops.md[target platforms] for the link:https://github.com/FreeBSDFoundation/proj-laptop/[Laptop Support and Usability Project]. Sponsor: The FreeBSD Foundation for Li-Wen's work + Sponsor: Framework Computer Inc for Daniel's work, hardware and space support diff --git a/website/content/en/status/report-2024-10-2024-12/gcc.adoc b/website/content/en/status/report-2024-10-2024-12/gcc.adoc index 7d7ba34512..35d14e8c8e 100644 --- a/website/content/en/status/report-2024-10-2024-12/gcc.adoc +++ b/website/content/en/status/report-2024-10-2024-12/gcc.adoc @@ -1,26 +1,27 @@ === GCC on FreeBSD Links: + link:https://gcc.gnu.org/[GCC Project] URL: link:https://gcc.gnu.org/[] + link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[] + link:https://gcc.gnu.org/gcc-12/[GCC 12 release series] URL: link:https://gcc.gnu.org/gcc-12/[] + link:https://gcc.gnu.org/gcc-13/[GCC 13 release series] URL: link:https://gcc.gnu.org/gcc-13/[] + link:https://gcc.gnu.org/gcc-14/[GCC 14 release series] URL: link:https://gcc.gnu.org/gcc-14/[] + Contact: Lorenzo Salvadore The link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281091[exp-run to update GCC default version from 13 to 14] is getting forward. As usual, thanks to everyone involved. If you maintain any of the affected ports or want to give a hand preparing and testing some patches, you can consider trying adding `-fpermissive` to `CFLAGS` in affected ports as a temporary solution: GCC 14 has transformed some warnings into errors, which is the cause of many of the failed builds. The `-fpermissive` flag switches those errors back to warnings. However, it is preferable that upstream updates its code to remove those warnings completely so that `-fpermissive` is not necessary, possibly with FreeBSD ports maintainers support. If the code is not maintained upstream anymore, the time might have come to deprecate the port. Work has been done on some bugs too, mainly upstream: + - link:https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117210[] has been fixed: a recent change in the FreeBSD headers caused a regression in the GCC 15 development version; - link:https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115008[] has been fixed: this was an issue with posix_fallocate failing on FreeBSD on a ZFS filesystem; - an attempt to fix bug link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282797[] specific to aarch64 for -devel ports has failed. If you are able to give a hand on this, it would be very much appreciated. Thanks to everyone who has helped with these issues. 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 bbe0d50089..5b467cd29c 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,46 @@ === 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 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. 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, 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]. 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. Hope to see you there! - 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 3164a78e87..ecd05f52fa 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,31 @@ === Tor-Browser 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.