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 a0a0e33c50..3bdc5bd802 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,72 +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. + Perhaps it has 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. * 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/core.adoc b/website/content/en/status/report-2024-10-2024-12/core.adoc index aab214ce8e..0ca2b420ae 100644 --- a/website/content/en/status/report-2024-10-2024-12/core.adoc +++ b/website/content/en/status/report-2024-10-2024-12/core.adoc @@ -1,20 +1,20 @@ === FreeBSD Core Team Contact: FreeBSD Core Team The FreeBSD Core Team is the governing body of FreeBSD. ==== Following up with the FreeBSD Foundation Core had a video conference with the FreeBSD Foundation on 2024-12-12 to follow-up on their in-person meeting held in Dublin during EuroBSDCon. Core and the Foundation continue discussing how to improve the collaboration and how to support developers and contributors: * The next round of community survey -* Identifiying projects where core would like help from the Foundation +* Identifying projects where core would like help from the Foundation * Work on the technical roadmap with the Foundation ==== Work in Progress Core is currently working on the following items: * Policy on generative AI created code and documentation diff --git a/website/content/en/status/report-2024-10-2024-12/freebsd-foundation.adoc b/website/content/en/status/report-2024-10-2024-12/freebsd-foundation.adoc index 77360bd880..c551869d8b 100644 --- a/website/content/en/status/report-2024-10-2024-12/freebsd-foundation.adoc +++ b/website/content/en/status/report-2024-10-2024-12/freebsd-foundation.adoc @@ -1,153 +1,154 @@ === FreeBSD Foundation Links: + link:https://freebsdfoundation.org/[FreeBSD Foundation] URL: link:https://freebsdfoundation.org/[] + link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[] + link:https://freebsdfoundation.org/donate/[Donate] URL: link:https://freebsdfoundation.org/donate/[] + link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[] + link:https://freebsdfoundation.org/journal/[FreeBSD Journal] URL: link:https://freebsdfoundation.org/journal/[] + link:https://freebsdfoundation.org/our-work/events/[Foundation Events] URL: link:https://freebsdfoundation.org/our-work/events/[] Contact: Deb Goodkin -The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to advancing FreeBSD through technical and non-technical support. Funded entirely by donations, the Foundation supports software development, infrastructure, security, and collaboration efforts; organizes events and developer summits; provides educational resources; and represents the FreeBSD Project in legal matters. +The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to advancing FreeBSD through technical and non-technical support. +Funded entirely by donations, the Foundation supports software development, infrastructure, security, and collaboration efforts; organizes events and developer summits; provides educational resources; and represents the FreeBSD Project in legal matters. The following report covers just some of the ways we supported FreeBSD in Q4. Deb Goodkin here. On behalf of the Foundation, I want to start out by saying thank you to this amazing community! Your financial contributions have allowed us to step up and take on some significant projects, including large, multi-phase software development work, greater security improvements, and important infrastructure improvements that will continue through 2025. We also increased our FreeBSD advocacy efforts over many different technical and social media platforms, including creating more content to promote and advocate for FreeBSD. You'll find more information about all of this work below. For a more in-depth look at our efforts in 2024, be sure to check out the year-end blog posts and my year-end reflections in the advocacy section below. We are hiring! Check out our jobs page here for our Solutions Specialist and Technical Marketing Manager job postings. Plus, we are looking for part-time technical writers and will be opening up another position soon, so keep an eye on this page link:https://freebsdfoundation.org/open-positions/[]. -We are still finalizing our 2024 fundraising numbers, but at this writing, we've raised around $1,324,000. -You might be thinking, why don't we have a final tally now that it's 2025? -First, we haven't yet received all the checks postmarked 2024 . -We're also waiting on a few payments from invoices issued last year. -We'll have a final report in the next quarterly status report. +We are still finalizing our 2024 fundraising numbers, but at this writing, we have raised around $1,324,000. +You might be thinking, why do not we have a final tally now that it is 2025? +First, we have not yet received all the checks postmarked 2024 . +We are also waiting on a few payments from invoices issued last year. +We will have a final report in the next quarterly status report. Thank you to the individuals and organizations that made a financial contribution in Q4! We received 325 donations from individuals totaling $120,841 and six financial contributions from organizations totaling $326,000. We also received a grant from the Silicon Valley Community Fund. I would also like to send a shoutout to the anonymous donor who wanted us to help get Framework laptops into developers' hands. Pietro Cerutti has been coordinating that effort, and we are close to finalizing the process with Framework so developers can place their orders directly with them. We also funded almost $5,000 worth of AV equipment for the BSDCon AV team to minimize the amount of equipment needed to rent at each of the two main BSD conferences. Now, back to our financials. We will be publishing 2024 financial documents and reports in Q1. Our updated Q1-Q3 2024 Financial reports will be published by the end of January and will better match the budget format. The Final 2024 financial reports will be published in early Q2. Going forward, our budget and financial reports will provide more details on how funding is allocated to the major software development projects. For example, we will include how much was spent on the laptop project each quarter. -We're working with our accountant to improve our accounting systems to be more transparent on how we spend our money. +We are working with our accountant to improve our accounting systems to be more transparent on how we spend our money. We are excited about the opportunities for FreeBSD in 2025 and beyond, and are growing our team to help support the work needed to take advantage of these opportunities. However, we need your help to sustain this. Our investments will only carry on this work for a year or two at most. If your company is invested in the long-term sustainability of FreeBSD, please consider giving a financial contribution so we can ensure it stays the secure, reliable, and innovative platform you depend on. Not sure how to go about asking? Please reach out. We can help you navigate the process. Please go here to make a donation: link:https://freebsdfoundation.org/donate/[]. To find out more about our Partnership Program, go here: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[]. ==== Advocacy During the 4th quarter of 2024, we continued to raise awareness, advocate for the project, showcase users, while also providing educational content to the FreeBSD community. Here are some highlights of those efforts. * Sponsored and helped to organize the link:https://freebsdfoundation.org/news-and-events/event-calendar/fall-2024-freebsd-summit/[Fall 2024 FreeBSD Summit] which took place November 7-8, 2024 in San Jose, CA. Check out the link:https://freebsdfoundation.org/blog/reflecting-on-the-fall-2024-freebsd-summit-insights-and-innovations/[event recap]. Videos are available on the link:https://youtube.com/playlist?list=PLugwS7L7NMXwhtfVdd3m2Ro0TV1XDzl3t&si=FjFDkeaiXqRKS1Lq[FreeBSD YouTube channel]. * Updated the community on two of the new releases: ** link:https://freebsdfoundation.org/blog/freebsd-13-4-whats-new-and-how-did-we-get-here/[FreeBSD 13.4: What's new, and how did we get here?] ** link:https://freebsdfoundation.org/blog/freebsd-14-2-whats-new-and-how-did-we-get-here/[FreeBSD 14.2: What's new, and how did we get here?] * link:https://freebsdfoundation.org/end-user-stories/case-study-how-freebsd-fuels-nyis-success-as-a-managed-infrastructure-services-provider/[Published the NYI Case Study] * Shared link:https://freebsdfoundation.org/wp-content/uploads/2024/11/2024_Code_Audit_Capsicum_Bhyve_FreeBSD_Foundation.pdf[the FreeBSD Foundation 2024 Report on the Security Audit of the Capsicum and bhyve subsystems]. Learn more in the Security Audit. * Created a series of year end retrospectives on the work we did in 2024. ** link:https://freebsdfoundation.org/blog/your-impact-on-freebsd-2024-milestones-and-whats-next/[Your Impact on FreeBSD: 2024 Milestones and What's Next] ** link:https://freebsdfoundation.org/blog/2024-a-year-of-advocacy-and-growth-for-the-freebsd-foundation/[2024: A Year of Advocacy and Growth for the FreeBSD Foundation] ** link:https://freebsdfoundation.org/blog/celebrating-2024s-collaborative-achievements-at-the-freebsd-foundation/[Celebrating 2024's Collaborative Achievements at the FreeBSD Foundation] ** link:https://freebsdfoundation.org/blog/freebsd-foundation-a-year-of-sponsored-development-in-2024/[FreeBSD Foundation: A Year of Sponsored Development in 2024] ** link:https://freebsdfoundation.org/blog/reflecting-on-a-successful-2024/[Reflecting on a Successful 2024] * Published additional blogs including: ** link:https://freebsdfoundation.org/blog/why-your-open-source-project-should-prioritize-security-lessons-from-freebsds-proactive-approach/[Why Your Open Source Project Should Prioritize Security: Lessons from FreeBSD's Proactive Approach] ** link:https://freebsdfoundation.org/blog/why-freebsd-should-be-the-foundation-for-your-security-product/[Why FreeBSD Should Be the Foundation for Your Security Product] ** link:https://freebsdfoundation.org/blog/celebrating-freebsd-day-with-tara-stella-a-journey-from-linux-to-freebsd/[Celebrating FreeBSD Day with Tara Stella: A Journey from Linux to FreeBSD] ** link:https://freebsdfoundation.org/blog/advancing-cloud-native-containers-on-freebsd-podman-testing-highlights/[Advancing Cloud Native Containers on FreeBSD: Podman Testing Highlights] * Participated in the following contributed articles, interviews and podcasts: ** link:https://freebsdfoundation.org/news-and-events/latest-news/all-things-open-blog-prioritizing-security-lessons-from-freebsds-proactive-approach/[All Things Open Blog: Prioritizing Security: Lessons from FreeBSD's Proactive Approach] ** link:https://freebsdfoundation.org/news-and-events/latest-news/freebsd-foundation-releases-bhyve-and-capsicum-security-audit-funded-by-alpha-omega-project/[FreeBSD Foundation Releases Bhyve and Capsicum Security Audit Funded by Alpha-Omega Project] ** link:https://freebsdfoundation.org/news-and-events/latest-news/why-we-use-freebsd-over-linux-a-ctos-perspective/[Why We Use FreeBSD Over Linux: A CTO's Perspective] * Published the link:https://freebsdfoundation.org/news-and-events/newsletter/october-2024-newsletter/[October 2024], link:https://freebsdfoundation.org/our-work/latest-updates/?filter=newsletter#:~:text=November%202024%20Newsletter[November 2024], and link:https://freebsdfoundation.org/our-work/latest-updates/?filter=newsletter#:~:text=December%202024%20Newsletter[December 2024] FreeBSD Foundation Newsletters. * Released the link:https://freebsdfoundation.org/our-work/journal/browser-based-edition/kernel-development/[September/October 2024] issue of the FreeBSD Journal with HTML versions of the articles. ==== OS Improvements During the fourth quarter of 2024, 382 `src`, 135 `ports`, and 17 `doc` tree commits identified The FreeBSD Foundation as a sponsor. The Foundation and its investment partners supported four major projects: * {kib} continued work on an AMD IOMMU driver for FreeBSD, a project jointly funded by AMD and the Foundation. This effort aims to enhance support for large-core AMD systems and other scenarios requiring interrupt remapping. The driver was link:https://cgit.freebsd.org/src/commit/?id=0f5116d7efe33c81f0b24b56eec78af37898f500[pushed to the src tree] in early November and continues to undergo testing and refinement. * link:https://alpha-omega.dev/[Alpha-Omega] and the Foundation have been jointly funding a project to improve FreeBSD security. For the latest updates, refer to the <<_security_engineering_at_the_FreeBSD_Foundation,Security Engineering at the FreeBSD Foundation>> entry for the latest updates. * A project to link:https://freebsdfoundation.org/blog/why-laptop-support-why-now-freebsds-strategic-move-toward-broader-adoption/[improve FreeBSD laptop usability] began this quarter. For details, refer to the <<_laptop_support_and_usability_improvements_project,Laptop Support and Usability Improvements Project>> report entry. * <<_infrastructure_modernization,Work commissioned by the Sovereign Tech Agency to modernize FreeBSD's infrastructure>> continued this quarter. The goal of this work is to help achieve and sustain a manageable bug backlog. As part of this effort, The Foundation worked with link:https://bitergia.com/[Bitergia] to analyze and assess open Bugzilla bugs. {bofh} finished porting Grimoirelab and deploying link:https://grimoire.freebsd.org/[Grimoire] in the FreeBSD cluster. Other projects: * {asiciliano} provided a <<_ports_collection_accessibility_colors_low_vision,FreeBSD Accessibility Project update>>. * Aymeric Wibo began implementing <<_suspendresume_improvements,suspend-to-idle and S0ix sleep support>>. * {bz} shared a <<_linuxkpi_802_11_wireless_update, LinuxKPI 802.11 Wireless Update>>. * Chih-Hsin Chang continued work to <<_openstack_on_freebsd,improve OpenStack on FreeBSD>>. * {christos} shared an update on work to <<_audio_stack_improvements,improve the FreeBSD audio stack>>. * Harald Eilersten began working on a project to <<_improve_openjdk_on_freebsd,improve OpenJDK on FreeBSD>>. * Isaac Freund worked on <<_pkgbase_motivated_improvements_to_pkg,PkgBase-motivated improvements to pkg>>. * Jian-Lin Li began a project to <<_syzkaller_improvement_on_freebsd,improve Syzkaller on FreeBSD>>. * {jrm} spent time on a personal project to <<_improving_common_lisp_infrastructure_in_freebsd_ports,improve Common Lisp support in the ports tree>>. * {olce} submitted a report entry describing the work he completed with Baptiste Daroussin to <<_mac_do4_setcred2_mdo1, allow controlled process credentials transitions using the MAC framework>>. * Pierre Pronchery returned to working on a <<_umb4_driver_for_mbim_usb_4g5g_modems,umb(4) driver for MBIM USB 4G/5G modems>> and he shared <<_progress_on_the_freebsd_installer,an update on work to improve the FreeBSD Installer>>. * {thj} started <<_wireless_update,porting the iwx WiFi driver from OpenBSD (via Haiku)>>. Other members of the Foundation's development team contributed to FreeBSD development efforts. For example: * {mhorne} worked with community contributor Julien Cassette to add link:https://cgit.freebsd.org/src/commit/?id=c5c02a131a0e2ef52771e683269bc8778fe511f3[a RISC-V Allwinner D1 clock and reset driver]. * {chuck}, {jhb}, and Pierre Pronchery fixed a few bhyve issues: ** link:https://cgit.freebsd.org/src/commit/?id=e94a1d6a7f2eb932850e1db418bf34d5c6991ce8[bounds checks in hda_codec] ** link:https://cgit.freebsd.org/src/commit/?id=b0a24be007d83f7929de5b3fc320a29e6868067d[out-of-bounds read in NVMe log page] ** link:https://cgit.freebsd.org/src/commit/?id=5374b9e146811757540e35553a7712c5b9b29239[infinite loop in queue processing] ** link:https://cgit.freebsd.org/src/commit/?id=b34a4edefb0a40ced9b17ffd640f52fe55edc1f5[buffer overflow in pci_vtcon_control_send] ** link:https://cgit.freebsd.org/src/commit/?id=8c8ebbb045185396083cd3e4d333fe1851930ee7[robustness of TRIM handling]. * In the ports tree, {bofh} converted `USE_OCAML` and `USE_JAVA` to the `USES` framework. * {emaste} squashed a couple of man:makefs[8] bugs related to creating ISO9660 filesystems via the man:cd9660[4] driver: ** link:https://cgit.freebsd.org/src/commit/?id=2e09cef8dc6f46faba8bab87c42c3f19ba2ffe87[cd9660 filename buffer maximum length] ** link:https://cgit.freebsd.org/src/commit/?id=1f31d437428014e864bcce1223cf7017180e2608[cd9660 duplicate directory names]. ==== Continuous Integration and Workflow Improvement As part of our continued support of the FreeBSD Project, the Foundation supports a full-time staff member dedicated to <<_ci,improving the Project's continuous integration system and test infrastructure>>. ==== Legal/FreeBSD IP The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them. We also provide legal support for the core team to investigate questions that arise. Go to link:https://freebsdfoundation.org[] to find more about how we support FreeBSD and how we can help you! 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 277c520777..5b4c14d8af 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,19 @@ === 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[] + 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. +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/qemu_l4b.adoc b/website/content/en/status/report-2024-10-2024-12/qemu_l4b.adoc index 1ce2344dd9..99e6fd14fc 100644 --- a/website/content/en/status/report-2024-10-2024-12/qemu_l4b.adoc +++ b/website/content/en/status/report-2024-10-2024-12/qemu_l4b.adoc @@ -1,32 +1,33 @@ === BSD-USER 4 LINUX Contact: Maksym Sobolyev Links: link:https://github.com/sobomax/qemu-bsd-user-l4b[Project Page] URL: link:https://github.com/sobomax/qemu-bsd-user-l4b[] + link:https://github.com/sobomax/qemu_l4b[Tooling] URL: link:https://github.com/sobomax/qemu_l4b[] The `bsd-user-4-linux` project ports BSD user-mode emulation for QEMU to Linux. The primary goal is to enable unmodified FreeBSD binaries to run on modern Linux systems. Additionally, the project aims to provide multi-platform container images with a functional FreeBSD environment and ready-to-use GitHub Actions templates. Current Status: * The initial port successfully runs `make -jN buildworld`. * Most command-line tools are working as expected (`sh`, `bash`, `find`, `grep`, `git`, `clang`, etc). * A link:https://github.com/sobomax/qemu-bsd-user-l4b/actions[GitHub Actions pipeline] builds x86_64 emulation images for: ** linux/386 ** linux/amd64 ** linux/arm/v5 ** linux/arm64/v8 Next Steps: * Implement container integration. How You Can Help: * Test with your preferred toolchain, report issues, or contribute fixes. -* Build and test non-x86_64 emulation images (e.g., FreeBSD/arm64 on Linux/x86_64). The code works on BSD but needs testing on Linux. +* Build and test non-x86_64 emulation images (e.g., FreeBSD/arm64 on Linux/x86_64). + The code works on BSD but needs testing on Linux. * Support us on link:https://patreon.com/sippylabs[Patreon]. Sponsor: Sippy Software, Inc.