From owner-dev-commits-doc-all@freebsd.org Sat Jan 16 14:26:25 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1AFED4E037A for ; Sat, 16 Jan 2021 14:26:25 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DJ0jF0C83z3sMh; Sat, 16 Jan 2021 14:26:25 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id E992C7FF1; Sat, 16 Jan 2021 14:26:24 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 10GEQO8F089024; Sat, 16 Jan 2021 14:26:24 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 10GEQO31089023; Sat, 16 Jan 2021 14:26:24 GMT (envelope-from git) Date: Sat, 16 Jan 2021 14:26:24 GMT Message-Id: <202101161426.10GEQO31089023@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Daniel Ebdrup Jensen Subject: git: af1a126124 - main - Add 2020Q4 quarterly status report MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: debdrup X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: af1a1261248bc08dec900f9ae6c2ded35482b8c7 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jan 2021 14:26:25 -0000 The branch main has been updated by debdrup: URL: https://cgit.FreeBSD.org/doc/commit/?id=af1a1261248bc08dec900f9ae6c2ded35482b8c7 commit af1a1261248bc08dec900f9ae6c2ded35482b8c7 Author: Daniel Ebdrup Jensen AuthorDate: 2021-01-15 15:49:08 +0000 Commit: Daniel Ebdrup Jensen CommitDate: 2021-01-16 11:01:14 +0000 Add 2020Q4 quarterly status report While here, bump deadline for new submissions Reviewed by: PauAmma Differential Revision: https://reviews.freebsd.org/D28175 --- en_US.ISO8859-1/htdocs/news/status/Makefile | 2 + .../htdocs/news/status/report-2020-10-2020-12.xml | 2703 ++++++++++++++++++++ en_US.ISO8859-1/htdocs/news/status/status.xml | 4 +- 3 files changed, 2707 insertions(+), 2 deletions(-) diff --git a/en_US.ISO8859-1/htdocs/news/status/Makefile b/en_US.ISO8859-1/htdocs/news/status/Makefile index d44428f747..f9b4351fd8 100644 --- a/en_US.ISO8859-1/htdocs/news/status/Makefile +++ b/en_US.ISO8859-1/htdocs/news/status/Makefile @@ -89,6 +89,8 @@ XMLDOCS+= report-2019-10-2019-12 XMLDOCS+= report-2020-01-2020-03 XMLDOCS+= report-2020-04-2020-06 XMLDOCS+= report-2020-07-2020-09 +XMLDOCS+= report-2020-10-2020-12 + XSLT.DEFAULT= report.xsl # Install a sample entry. diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2020-10-2020-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2020-10-2020-12.xml new file mode 100644 index 0000000000..79f68f72a1 --- /dev/null +++ b/en_US.ISO8859-1/htdocs/news/status/report-2020-10-2020-12.xml @@ -0,0 +1,2703 @@ + + + + + + + + + + 10-12 + + 2020 + + +
+ Introduction +

This report covers FreeBSD related projects for the period between +October and December, and is the fourth of four planned reports for 2020. +

+

This quarter had quite a lot of work done, including but certainly not +limited to, in areas relating to everything from multiple architectures +such as x86, aarch64, riscv, and ppc64 for both base and ports, over kernel +changes such as vectored aio, routing lookups and multipathing, an +alternative random(4) implementation, zstd integration for kernel +dumps, log compression, zfs and preparations for pkg(8), along with +wifi changes, changes to the toolchain like the new elfctl utility, +and all the way to big changes like the git migration and moving the +documentation from DocBook to Hugo/AsciiDoctor, as well as many other +things too numerous to mention in an introduction. +

+

This report with 42 entries, which don't hold the answer to life, the +universe and everything, couldn't have happened without all the people +doing the work also writing an entry for the report, so the quarterly +team would like to thank them, as otherwise, we wouldn't have anything +to do. +

+

Please note that the deadline for submissions covering the period +between January and March is March 31st. +

+

We hope you'll enjoy reading as much as we enjoyed compiling it. +Daniel Ebdrup Jensen, on behalf of the quarterly team. +

+ +FreeBSD Foundation + + + +Deb Goodkin +deb@FreeBSDFoundation.org + + + +

The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to +supporting and promoting the FreeBSD Project and community worldwide. Funding +comes from individual and corporate donations and is used to fund and manage +software development projects, conferences and developer summits, and provide +travel grants to FreeBSD contributors. The Foundation purchases and supports +hardware to improve and maintain FreeBSD infrastructure and provides resources +to improve security, quality assurance, and release engineering efforts; +publishes marketing material to promote, educate, and advocate for the FreeBSD +Project; facilitates collaboration between commercial vendors and FreeBSD +developers; and finally, represents the FreeBSD Project in executing contracts, +license agreements, and other legal arrangements that require a recognized +legal entity. +

+

Here are some highlights of what we did to help FreeBSD last quarter: +

+

COVID-19 Impact to the Foundation

+ +

Like most organizations, we transitioned all of our staff to work from home. +We also put a temporary ban on travel for staff members, which didn't affect +our output too much, since most conferences went virtual. We continued +supporting the community and Project, even though some of our work and +responses may have been delayed because of changes in some of our priorities +and the impact of limited childcare for a few of our staff members. +

+

Partnerships and Commercial User Support

+ +

We help facilitate collaboration between commercial users and FreeBSD +developers. We also meet with companies to discuss their needs and bring that +information back to the Project. Not surprisingly, the stay at home orders, +combined with our company ban on travel during Q4 made in-person meetings +non-existent. However, the team was able to continue meeting with our partners +and commercial users virtually. These meetings help us understand some of the +applications where FreeBSD is used. +

+

An event we help plan and organize, that helps with vendor/developer +engagement, is the annual Bay Area Vendor Summit. We weren't going to let a +pandemic stop us from holding this invaluable yearly event, so we went virtual! +From the feedback we received from the vendor community on how we should run +this, so it would be beneficial for them, we decided to hold this over 3 half +days in November. One unexpected result was that more commercial users from +around the world attended. Since a Vendor/Developer Summit is typically +invitation only, we opened this up to FreeBSD contributors from around the +world to watch the livestream. Because of the success and excitement of this +event, we are planning to hold another one around June or July. +

+

Fundraising Efforts

+ +

We want to take a moment to say thank you to all the individuals and +corporations that stepped up to help fund our efforts last year. As of this +writing, we raised $1,235,926, and will have the final tally by mid-January. +The companies that gave generous financial contributions include Arm, NetApp, +Netflix, Juniper Networks, Beckhoff, VMware, Stormshield, Tarsnap, and Google. +We also want to say thank you to the Koum Family Foundation for awarding us a +large grant, and to "the employees of Ngnix" who also made generous financial +contributions. +

+

We truly appreciate these large contributions, which makes the most impact on +how much we can contribute back to the Project. However, it's the individual +donations that have the most meaning to us. Those are the folks who are giving +because they trust we will invest their personal donations, whether large or +small, into improving the operating system and Project. As stewards of your +donations, we want to thank you for your trust in us and your commitment to +making FreeBSD the best platform for products, education, research, computing, +and more. +

+

You'll find out how we used your donations for Q4 in our report, as well as in +individual reports throughout this status report. +

+

Though we know this is a Q4 status report, we are excited about our plans for +2021, including growing our software development team! We'll be posting two +job descriptions for a Senior Software Developer and Project Coordinator soon. +

+

Please consider making a donation to help us continue and increase our support +for FreeBSD in 2021: https://www.FreeBSDfoundation.org/donate/. +

+

We also have the Partnership Program, to provide more benefits for our larger +commercial donors. Find out more information at +https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/ +and share with your companies! +

+

OS Improvements

+ +

The Foundation provided many project grants over the last quarter, and you +can read about OpenZFS Zstd support, Linuxulator application compatibility +improvements, LLDB target support, test lab infrastructure, and WiFi projects +in other entries in this quarterly report. +

+

The Foundation hired six co-op students from the University of Waterloo during +the 2020 fall term, as well as one intern. Former co-op student Tiger +returned, and new students Yang and Zac joined us for the first time. +

+

Tiger worked on improvements to the code-coverage guided kernel fuzzing tool +Syzkaller, adding new system call definitions so that Syzkaller can expand the +code it tests. A number of FreeBSD kernel bug fixes have already resulted from +this work. Tiger also contributed a number of improvements to the ELF Tool +Chain set of binary utilities, and worked on tooling to run tests from other +tool suites against ELF Tool Chain. +

+

Zac worked on an improvement to the pkg package management tool, investigating +and upstreaming patches for FreeBSD support in FreePBX, and investigating +compiler support for addressing the stack clash vulnerability. +

+

Yang investigated and fixed a compilation bug with the kernel's Skein-1024 +assembly implementation (used by ZFS), and then a number of projects related to +Capsicum: applying Capsicum to sort(1), implementing a Capsicum service to +execute utilities, and finally working with developers of the Game of Trees +(got) version control system to adapt it for Capsicum support. +

+

Our intern Ka Ho focused on improving the desktop experience of the FreeBSD. +He fixed and improved many items of OBS (Open Broadcaster Software) on +FreeBSD, worked on FreeBSD native audio support on Firefox, adding a facility +that user-space audio programs could make use of to enumerate a list of audio +devices. He also ported the fcitx5 input method framework. +

+

The five Foundation staff members continued contributions in 2020 in both +ongoing operational tasks (including the Git working group and security team) +and software development for a number of projects. +

+

Staff members responded to reported security vulnerabilities and release +errata, prepared patches, and participated in the security advisory process. +We also worked on proactive security vulnerability mitigations. Syzkaller +also provided many reports of kernel issues that resulted in +Foundation-sponsored bug fixes. We worked on several issues relating to +FreeBSD/arm64 to move it along the path of being a Tier-1 architecture. +

+

We participated in code reviews and supported community members in integrating +changes into FreeBSD, and triaged incoming bug reports. +

+

We contributed enhancements to many kernel and userland subsystems, including +the x86 pmap layer, ELF run-time linker and kernel loader, the Capsicum +sandboxing framework and Casper services, the threading library, some RISC-V +changes, the build system, tool chain and freebsd-update, network stack +stability improvements, machine-dependent optimizations, new kernel interfaces, +DTrace bug fixes, documentation improvements, and others. +

+

### Continuous Integration and Quality Assurance +

+

The Foundation provides a full-time staff member and funds projects on +improving continuous integration, automated testing, and overall quality +assurance efforts for the FreeBSD Project. +

+

During the fourth quarter of 2020, Foundation staff continued improving and +monitoring the Project's CI infrastructure, and working with experts to fix +the failing builds and the regressions found by tests. The work was focused +on pre-commit tests and development of the CI staging environment. The other +main working item is working on the VCS migration to change the src and doc +source from Subversion to Git. There are also many work-in-progress tasks like +analysis and improve the tests of non-x86 platforms. +

+

See the FreeBSD CI section of this report for completed work items and detailed +information. +

+

Supporting FreeBSD Infrastructure

+ +

The Foundation provides hardware and support to improve the FreeBSD +infrastructure. Last quarter, we continued supporting FreeBSD hardware located +around the world. We coordinated efforts between the new NYI Chicago facility +and clusteradm to start working on getting the facility prepared for some of +the new FreeBSD hardware we are planning on purchasing. NYI generously +provides this for free to the Project. We also worked on connecting with the +new owners of the NYI Bridgewater site, where most of the existing FreeBSD +infrastructure is located. +

+

Some of the purchases we made for the Project last quarter to support +infrastructure includes: +

+
    +
  • 5 application servers to run tasks like bugzilla, wiki, website, cgi, + Phabricator, host git, etc. +

  • +
  • 1 server to replace the old pkg server, which will provide a lot more IOPS + to avoid the slowdowns seen during peak times of the day where the disks + simply cannot keep up with the request volume. +

  • +
  • 1 server for exp-runs and to make them faster. +

  • +
  • 1 server to build packages more frequently. +

    +
+

FreeBSD Advocacy and Education

+ +

A large part of our efforts are dedicated to advocating for the Project. This +includes promoting work being done by others with FreeBSD; producing advocacy +literature to teach people about FreeBSD and help make the path to starting +using FreeBSD or contributing to the Project easier; and attending and getting +other FreeBSD contributors to volunteer to run FreeBSD events, staff FreeBSD +tables, and give FreeBSD presentations. +

+

The FreeBSD Foundation sponsors many conferences, events, and summits around +the globe. These events can be BSD-related, open source, or technology events +geared towards underrepresented groups. We support the FreeBSD-focused events +to help provide a venue for sharing knowledge, to work together on projects, +and to facilitate collaboration between developers and commercial users. This +all helps provide a healthy ecosystem. We support the non-FreeBSD events to +promote and raise awareness of FreeBSD, to increase the use of FreeBSD in +different applications, and to recruit more contributors to the Project. +

+

While we were still unable to attend in-person meetings due to COVID-19, we +were able to attend virtual events at new venues and facilitate the first +online FreeBSD Vendor Summit. In addition to attending and planning virtual +events, we are continually working on new training initiatives and updating our +selection of how-to guides to facilitate getting more folks to try out FreeBSD. +

+

Check out some of the advocacy and education work we did last quarter: +

+
    +
  • Continued our FreeBSD Fridays series of 101 classes. Topics included an + Introduction to Capsicum, Introduction to Bhyve, Introduction to DTrace, and + more. Videos of the past sessions can be found here. We'll be back with new + sessions in early 2021. +

  • +
  • Gave a FreeBSD talk at the nerdear.la conference on October 20th. +

  • +
  • Participated in the podcast: What the Dev: A Dive into the FreeBSD Foundation on its 20th Anniversary +

  • +
  • Promoted the Foundation's 20th Anniversary in the FossBytes article: + 20 Years of The FreeBSD Foundation +

  • +
  • Continued to promote the FreeBSD Office Hours series. Videos from the one hour + sessions can be found on the Project's YouTube Channel. See the Office Hours + section of this report for more information. +

  • +
  • Added two new How-To Guides: Contributing FreeBSD Documentation + and How to Submit a Bug Report. +

  • +
  • Worked with the organizing committee to host the November 2020 Vendor Summit +

  • +
  • Promoted the use of FreeBSD in regards to CHERI and ARM's Morello Processor +

  • +
  • Authored a Beginners Guide to FreeBSD for Fosslife. +

  • +
  • Sponsored All Things Open as a Media Sponsor. +

  • +
  • Sponsored OpenZFS Developers Summit at the Bronze level. +

  • +
  • Applied for a virtual stand at FOSDEM 2021. +

  • +
  • Committed to attend the online Apricot 2021. +

    +
+Keep up to date with our latest work in our newsletters: +

https://www.freebsdfoundation.org/news-and-events/newsletter/ +

+

Netflix provided an update on how and why they use FreeBSD in our latest +Contributor Case Study. +

+

We help educate the world about FreeBSD by publishing the professionally +produced FreeBSD Journal. As we mentioned previously, the FreeBSD Journal is +now a free publication. Find out more and access the latest issues at +https://www.FreeBSDfoundation.org/journal/. +

+

You can find out more about events we attended and upcoming events at +https://www.FreeBSDfoundation.org/news-and-events/. +

+

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 http://www.FreeBSDfoundation.org to find out how we support FreeBSD and +how we can help you! +

+ +FreeBSD Release Engineering Team + + + +FreeBSD Release Engineering Team +re@FreeBSD.org + + + + +FreeBSD 12.2-RELEASE schedule +FreeBSD 13.0-RELEASE schedule +FreeBSD development snapshots + + +

The FreeBSD Release Engineering Team is responsible for setting +and publishing release schedules for official project releases +of FreeBSD, announcing code freezes and maintaining the respective +branches, among other things. +

+

During the fourth quarter of 2020, the Release Engineering Team completed +work on 12.2-RELEASE, the third release from the stable/12 branch, released +on October 27. Thank you to all involved for the hard work that went into +this release. +

+

Additionally throughout the quarter, several development snapshots builds +were released for the head, stable/12, and stable/11 branches. +Development snapshot builds for 13.0-CURRENT have recently been built from +the Git tree within the project, while further snapshot builds for 12.x and +11.x will continue to be built from Subversion. As we approach the end of +2020, continued preparations are being put in place for the upcoming 13.0 +release, which will be the first release from Git. +

+

Much of this work was sponsored by Rubicon Communications, LLC (netgate.com) +and the FreeBSD Foundation. +

+ +Cluster Administration Team + + + +Cluster Administration Team +clusteradm@FreeBSD.org + + + + +Cluster Administration Team members + + +

The FreeBSD Cluster Administration Team consists of the people responsible for +administering the machines that the Project relies on for its distributed work +and communications to be synchronised. In this quarter, the team has worked +on the following: +

+
    +
  • Finished setting up the Malaysia mirror site, generously hosted by the + Malaysian Research & Education Network. Traffic + from Oceania and parts of Asia is now going to this mirror instead of + farther away sites like Japan and California. +

  • +
  • Upgraded the package building machines to a version of head from + mid-October 2020. +

  • +
  • Upgraded developer machines in the cluster (freefall, ref\* and universe\*) to + a version of head from mid-October 2020. +

  • +
  • Installed eight new x86 servers in our New Jersey site: + five application servers, two package builders and one mirror server. +

      +
    • The new mirror server is in production (pkg0.nyi.freebsd.org). +

    • +
    • The two package builders are in production. +

    • +
    • Two of the application servers have been put into production as the Git +source of truth and the cgit web frontend, respectively. +

    +
  • Installed two new aarch64 servers in our New Jersey site. Both are now + building aarch64 packages. +

  • +
  • Fixed package mirror synchronisation for powerpc64 packages. +

  • +
  • Rebuilt the ZFS pool on the UK mirror server (pkg0.bme.freebsd.org) for + better I/O parallelism. This should improve download performance + especially at peak times. +

  • +
  • Ongoing systems administration work: +

      +
    • Accounts management for committers. +

    • +
    • Backups of critical infrastructure. +

    • +
    • Keeping up with security updates in 3rd party software. +

      +
    +
+Work in progress: + +
    +
  • Hardware refreshing for web services, backup version control system in NYI +

  • +
  • Upgrading production machines in the FreeBSD cluster to 12.2 +

      +
    • Most machines have been upgraded as of mid-December 2020 +

    • +
    • Remaining machines will be decommissioned / repurposed after services +migrate to newer hardware +

    +
  • Supporting Git migration and infrastructure setup +

  • +
  • powerpc pkgbuilder/ref/universal machines +

  • +
  • Preparations for a new mirror site in Australia, to be hosted by + IX Australia. +

  • +
  • Setup Brazil (BRA) mirror. +

  • +
  • Review the service jails and service administrators operation. +

  • +
  • Searching for more providers that can fit the requirements for a + generic mirrored layout + or a + tiny mirror. +

+
+ +Continuous Integration + + +FreeBSD Jenkins Instance +FreeBSD Hardware Testing Lab +FreeBSD CI artifact archive +FreeBSD CI weekly report +FreeBSD Jenkins wiki +Hosted CI wiki +3rd Party Software CI +Tickets related to freebsd-testing@ +FreeBSD CI Repository + + + + +Jenkins Admin +jenkins-admin@FreeBSD.org + + +Li-Wen Hsu +lwhsu@FreeBSD.org + + +

Contact: freebsd-testing Mailing List
+Contact: IRC #freebsd-ci channel on EFNet
+

+

The FreeBSD CI team maintains the continuous integration system +of the FreeBSD project. The CI system firstly checks the committed changes +can be successfully built, then performs various tests and analysis over the +newly built results. +The artifacts from those builds are archived in the artifact server for +further testing and debugging needs. The CI team members examine the +failing builds and unstable tests and work with the experts in that area to +fix the code or adjust test infrastructure. The details of these efforts +are available in the weekly CI reports. +

+

During the fourth quarter of 2020, we continued working with the contributors and +developers in the project to fulfil their testing needs and also keep +collaborating with external projects and companies to improve their products +and FreeBSD. +

+

Important changes: +

+
    +
  • doc jobs were changed to use git to follow VCS migration: +

      +
    • https://ci.freebsd.org/job/FreeBSD-doc-main/ +

    • +
    • https://ci.freebsd.org/job/FreeBSD-doc-main-igor/ + Thanks Brandon Bergren (bdragon@) +

    +
  • head and stable/12 build environment have been upgraded to 12.2-RELEASE +

    +
+New jobs added: + + +Work in progress: + +
    +
  • Follow VCS migration, change src jobs to use Git - PRs are + available + Thanks Brandon Bergren (bdragon@) +

  • +
  • Collecting and sorting CI tasks and ideas + here +

  • +
  • Testing and merging pull requests in the + the FreeBSD-ci repo +

  • +
  • Designing and implementing pre-commit CI building and testing +

  • +
  • Reducing the procedures of CI/test environment setting up for contributors and + developers +

  • +
  • Setting up the CI stage environment and putting the experimental jobs on it +

  • +
  • Setting up public network access for the VM guest running tests +

  • +
  • Implementing automatic tests on bare metal hardware +

  • +
  • Adding drm ports building tests against -CURRENT +

  • +
  • Planning to run ztest and network stack tests +

  • +
  • Adding more external toolchain related jobs +

  • +
  • Improving the hardware lab to be more mature and adding more hardware +

  • +
  • Helping more software get FreeBSD support in their CI pipeline + Wiki pages: 3rdPartySoftwareCI, + HostedCI +

  • +
  • Working with hosted CI providers to have better FreeBSD support +

  • +
  • The build and test results will be sent to the + dev-ci mailing list + soon. Feedback and help with analysis is very appreciated! +

    +
+Please see freebsd-testing@ related tickets for more WIP information, and don't hesitate to join the effort! + +

Sponsor: The FreeBSD Foundation +

+ +Ports Collection + + +About FreeBSD Ports +Contributing to Ports +FreeBSD Ports Monitoring +Ports Management Team +Ports Tarball + + + + +René Ladan +portmgr-secretary@FreeBSD.org + + +FreeBSD Ports Management Team +portmgr@FreeBSD.org + + + +

The Ports Management Team is responsible for overseeing the +overall direction of the Ports Tree, building packages, and +personnel matters. Below is what happened in the last quarter. +

+

For the last quarter the dashboard looks like: +

+
    +
  • 41500 ports (including flavors) +

  • +
  • 2516 open PRs of which 625 are unassigned +

  • +
  • 8715 commits to the HEAD branch by 164 committers +

  • +
  • 420 commits to the 2020Q4 branch by 59 committers +

    +
+Compared to the third quarter, the PR statistics mostly stayed the same. There +

were slightly fewer commits by the same number of people. The number of ports +again grew steadily, this time by almost 4 percent. +

+

During the last quarter, we welcomed Juray Lutter (otis@) as a new ports +committer and said goodbye to cpm, jadawin, knu, araujo, mmokhi and scottl. +

+

Traditionally merges to the quarterly ports branches, which are more +conservative versions of the HEAD tree, required approval of either the +Ports Security Team (ports-secteam@) or portgmr@. There were already a number +of blanket approvals for tested commits, ranging from fixing typing mistakes to +upgrading web browsers to their latest version. As of last December, all +ports committers are free to merge on their own, lessening the burden on +ports-secteam@. +

+

Patent limitations have been disconnected from the license framework, given +that patents are a complex topic with implications varying from one jurisdiction +to another. +

+

The last quarter saw a number of updates to default versions of ports: +

+
    +
  • librsvg2: "rust" on supported platforms, "legacy" + otherwise +

  • +
  • Mono: 5.10 +

  • +
  • FPC switched to 3.2.0 +

  • +
  • GCC switched to 10 for powerpc64le +

  • +
  • Lazarus switched to 2.0.10 +

  • +
  • Ruby switched to 2.7.X +

  • +
  • Samba switched to 4.12 +

    +
+During the last quarter, a new virtual category was added: "education" for ports +

that for instance help the user to learn about a certain topic or help +facilitating examinations. +

+

The @shell and @sample keywords have been rewritten in Lua which makes root-dir +compliant (see pkg -r) and ensures they are Capsicum-sandboxed. +

+

The last quarter also saw updates to several user-facing ports: +

+
    +
  • Firefox 84.0.1 +

  • +
  • Firefox-esr 78.6.0 +

  • +
  • Chromium 87.0.4280.88 +

  • +
  • Ruby 2.7.2 +

  • +
  • Qt5 5.15.2 +

  • +
  • XFce 4.16 +

    +
+As always, antoine@ was busy running exp-runs, 37 this quarter, testing: + +
    +
  • various ports upgrades +

  • +
  • changing sys/cdefs.h in base +

  • +
  • adding "set pipefail" to most framework scripts to catch errors earlier +

  • +
  • changing the default locale to C.UTF-8 in base +

  • +
  • using bsdgrep as /usr/bin/grep +

+
+ +Office Hours + + + +Allan Jude +allanjude@freebsd.org + + +Ed Maste +emaste@freebsd.org + + + +

During the final quarter of 2020 three office hours sessions were held. +

+

The first was hosted by the core team in a time slot conducive to Asia and +Australia, covering topics including the transition to git, recruiting for +project teams, and core's todo list. +

+

The second was hosted by the git transition team, and answered attendee +questions about the transition to git and how it would impact the project's +workflows. +

+

The third session was hosted by bhyve maintainers Peter Grehan and John Baldwin +to present recent development efforts and answer questions about bhyve. +

+

The project is looking for volunteers to host future office hours sessions, as +well as taking topic suggestions. We also hope to improve the system to allow people +to submit questions ahead of time, so that we can take maximum advantage of +subject matter experts when we have them for these calls. +

+

You can find the schedule for future office hours, and videos of past +office hours on the FreeBSD Wiki +

+

Sponsor: ScaleEngine Inc. +

+ +GPL in Base + + +GPL Software in the Base System + + + + +Ed Maste +emaste@FreeBSD.org + + +Kyle Evans +kevans@FreeBSD.org + + +Baptiste Daroussin +bapt@FreeBSD.org + + + +

A long-standing goal of the FreeBSD project is for the base system to migrate +to modern, copyfree or more permissively licensed components. In this quarter, +the following components have been successfully removed or replaced: +

+
    +
  • gdb (removed in favor of lldb in base or devel/gdb in ports) +

  • +
  • gnugrep (replaced with bsdgrep) +

  • +
  • libgnuregex (removed) +

    +
+The following component(s) have yet to be claimed. Some replacement prospects +

may be listed on the above-linked wiki page. Interested parties are welcome to +evaluate the options to restart the discussion: +

+
    +
  • dialog +

  • +
  • gcov (kernel) +

    +
+The following component(s) have a principal investigator to coordinate work. +

Note that partial completion likely means that a component is partially +compatible, but could use evaluation and patches to bring parity with the +component that it is replacing. +

+
    +
  • diff3 (Contact bapt@ if interested) +

+
+ +Git Migration Working Group + + +src (base system) git repo +doc git repo +Beta ports git repo +Warner's git documentation repo +FreeBSD-git mailing list +Git conversion tooling repo +Game of Trees +gitup + + + + +Li-Wen Hsu +lwhsu@FreeBSD.org + + +Warner Losh +imp@FreeBSD.org + + +Ed Maste +emaste@FreeBSD.org + + +Ulrich Spörlein +uqs@FreeBSD.org + + + +

The Git working group largely completed the migration of the doc and src +(base system) trees from Subversion to Git in December 2020. We are currently +working on some minor outstanding issues and preparing for the ports tree +migration. +

+

We set up new hosts to serve as the Git repositories and mirrors, and developed +commit hooks for restrictions on commits to various branches, generation of +commit mail, and similar needs. +

+

The doc tree migration occurred on December 8th and 9th. After the conversion +some minor changes to the documentation build infrastructure were necessary. +

+

The src tree migration occurred between December 20th and 23rd for the main +branch; some additional tasks occurred over the next week or so. These +included enabling the stable branches, vendor (contrib) code updates, and +the git->svn gateway. We are translating stable branch commits to Subversion +for the stable/11 and stable/12 branches and associated release branches. This +allows FreeBSD users who follow stable branches or releases to continue using +existing processes and tooling. +

+

An experimental Git conversion of the ports tree is available at the link +above. There are some unique challenges in the ports tree (that do not impact +the doc or src repos in the same way), so additional work is ongoing. The +window for migrating the ports tree is immediately prior to a quarterly +branch, so we anticipate a migration at the end of March 2021. Over the next +few months testing of the experimental ports repo is very welcome. +

+

Process documentation for developer and user interaction with FreeBSD's +repositories is currently available in Warner's GitHub repository at the link +above. It will be moved to the FreeBSD developer's handbook and/or other +suitable locations following the documentation project's asciidoc conversion. +

+

The working group is experimenting with two permissively-licensed tools that +are compatible with Git servers or repositories. Game of Trees is a version +control system that is compatible with Git repositories. It is being developed +by Stefan Sperling along with some OpenBSD developers and other contributions. +

+

John Mehr's gitup is a minimal, dependency-free program that clones and +synchronizes a local tree with a remote repository. It is intended for use +cases that would otherwise be served by tools like portsnap. +

+

Sponsor: The FreeBSD Foundation (in part) +

+ +Linux compatibility layer update + + + +Edward Tomasz Napierala +trasz@FreeBSD.org + + + +

Linuxulator improvements have been ongoing for the last two years, +with support from the FreeBSD foundation over a few distinct project +grants as well as contributions from the community. +The goal of this project is to improve FreeBSD's ability to execute +unmodified Linux binaries. +Current status is being tracked at Linux app status Wiki page. +The work has now shifted from command-line apps to desktop applications. +

+

There wasn't much Foundation-sponsored work done during this quarter, +apart from extending fuse(4) to make it possible to run Linux FUSE +servers, which is one of the things required to run AppImages. +The Foundation-sponsored effort will continue into the first quarter +of 2021 in order to make sure the 13.0-RELEASE ships with Linuxulator in a good shape. +

+

There was a very significant contribution from Conrad Meyer in the form +of SO_PASSCRED setsockopt(2) support, PR_SETDUMPABLE and PR_GETDUMPABLE +prctl(2) flags, and also CLONE_FS and CLONE_FILES handling. This, +along with some more cleanups and improvements, leads to working Linux +Chromium; it has been tested with Netflix and Spotify clients. It still +requires three flags (--no-sandbox --no-zygote --in-process-gpu) +to be passed on the command line to work around missing functionality, though. Also, +the name_to_handle_at(2) and open_by_handle_at(2) syscalls are now supported. +There are also much better debug messages for unrecognized socket options. +

+

Sponsor: The FreeBSD Foundation +

+ +LLDB Debugger Improvements + + +Moritz Systems Project Description +FreeBSD Foundation Blog +Git Repository + + + + +Kamil Rytarowski +kamil@moritz.systems + + +Michał Górny +mgorny@moritz.systems + + + +

The LLDB project builds on libraries provided by LLVM and Clang to provide a +great modern debugger. It uses the Clang ASTs and the expression parser, LLVM +JIT, LLVM disassembler, etc so that it provides an experience that “just +works”. It is also blazing fast and more permissively licensed than GDB, the +GNU Debugger. +

+

LLDB is the default debugger in Xcode on macOS and supports debugging C, +Objective-C, and C++ on the desktop and iOS devices and the simulator. +

+

FreeBSD includes LLDB in the base system. At present, it has some limitations +in comparison with the GNU GDB debugger, and does not yet provide a complete +replacement. It used to rely on an obsolete plugin model in LLDB that was a +growing technical debt. This project aimed to bring LLDB closer to a fully +featured replacement for GDB, and therefore for FreeBSD to feature a modern +debugger for software developers. +

+

The legacy monolithic target support executed the application being debugged in +the same process space as the debugger. The modern LLDB plugin approach, used +on other supported targets, executes the target process under a separate +lldb-server process. This improves reliability and simplifies the process / +thread model in LLDB itself. In addition, remote and local debugging is now +performed using the same approach. +

+

After the migration to the new process model on 32 and 64-bit x86 CPUs, the +project focused on reviewing the results of LLDB’s test suite and fixing tests +as time permits. +

+

During the Moritz Systems work, the FreeBSD Project gained numerous important +improvements: in the kernel, userland base libraries (the dynamic loader) and +the LLVM toolchain FreeBSD support. +

+

The introduced changes are expected to be shipped with LLDB 12.0, and where +applicable in FreeBSD 13.0. +

+

The overall experience of FreeBSD/LLDB developers and advanced users on this +rock solid Operating System reached the state known from other environments. +Furthermore, the FreeBSD-focused work also resulted in generic improvements, +enhancing the LLDB support for Linux and NetBSD. +

+ +

Sponsor: The FreeBSD Foundation
+

+ +Upstreaming NetApp Changes + + +Klara Inc. + + *** 1772 LINES SKIPPED ***