Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 16 Jan 2021 14:26:24 GMT
From:      Daniel Ebdrup Jensen <debdrup@FreeBSD.org>
To:        doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org
Subject:   git: af1a126124 - main - Add 2020Q4 quarterly status report
Message-ID:  <202101161426.10GEQO31089023@gitrepo.freebsd.org>

next in thread | raw e-mail | index | archive | help
The branch main has been updated by debdrup:

URL: https://cgit.FreeBSD.org/doc/commit/?id=af1a1261248bc08dec900f9ae6c2ded35482b8c7

commit af1a1261248bc08dec900f9ae6c2ded35482b8c7
Author:     Daniel Ebdrup Jensen <debdrup@FreeBSD.org>
AuthorDate: 2021-01-15 15:49:08 +0000
Commit:     Daniel Ebdrup Jensen <debdrup@FreeBSD.org>
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 <project> 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 @@
+<?xml version="1.0" encoding="utf-8" ?>
+<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for
+  Status Report//EN"
+  "http://www.FreeBSD.org/XML/share/xml/statusreport.dtd" >
+
+<!-- $FreeBSD$ -->
+
+<!--
+     Variables to replace:
+     10     - report month start
+     12      - report month end
+     2020      - report year
+     %%NUM%%       - report issue (first, second, third, fourth)
+     %%STARTNEXT%% - report month start
+     %%STOPNEXT%%  - report month end
+     %%YEARNEXT%%  - next report due year (if different than 2020)
+     %%DUENEXT%%   - next report due date (i.e., June 6)
+-->
+
+<report>
+  <date>
+    <month>10-12</month>
+
+    <year>2020</year>
+  </date>
+
+  <section>
+    <title>Introduction</title>
+<p>This report covers FreeBSD related projects for the period between
+October and December, and is the fourth of four planned reports for 2020.
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>Please note that the deadline for submissions covering the period
+between January and March is March 31st.
+</p>
+<p>We hope you'll enjoy reading as much as we enjoyed compiling it.
+Daniel Ebdrup Jensen, on behalf of the quarterly team.
+</p>  </section>
+<project cat='team'>
+<title>FreeBSD Foundation</title>
+
+<contact>
+<person>
+<name>Deb Goodkin</name>
+<email>deb@FreeBSDFoundation.org</email>
+</person>
+</contact>
+
+<body><p>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.
+</p>
+<p>Here are some highlights of what we did to help FreeBSD last quarter:
+</p>
+<h3>COVID-19 Impact to the Foundation</h3>
+
+<p>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.
+</p>
+<h3>Partnerships and Commercial User Support</h3>
+
+<p>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.
+</p>
+<p>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.
+</p>
+<h3>Fundraising Efforts</h3>
+
+<p>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.
+</p>
+<p>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.
+</p>
+<p>You'll find out how we used your donations for Q4 in our report, as well as in
+individual reports throughout this status report.
+</p>
+<p>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.
+</p>
+<p>Please consider making a donation to help us continue and increase our support
+for FreeBSD in 2021: https://www.FreeBSDfoundation.org/donate/.
+</p>
+<p>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!
+</p>
+<h3>OS Improvements</h3>
+
+<p>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.
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>We participated in code reviews and supported community members in integrating
+changes into FreeBSD, and triaged incoming bug reports.
+</p>
+<p>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.
+</p>
+<p>### Continuous Integration and Quality Assurance
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>See the FreeBSD CI section of this report for completed work items and detailed
+information.
+</p>
+<h3>Supporting FreeBSD Infrastructure</h3>
+
+<p>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.
+</p>
+<p>Some of the purchases we made for the Project last quarter to support
+infrastructure includes:
+</p>
+<ul>
+<li><p>5 application servers to run tasks like bugzilla, wiki, website, cgi,
+    Phabricator, host git, etc.
+</p></li>
+<li><p>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.
+</p></li>
+<li><p>1 server for exp-runs and to make them faster.
+</p></li>
+<li><p>1 server to build packages more frequently.
+</p>
+</li></ul>
+<h3>FreeBSD Advocacy and Education</h3>
+
+<p>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.
+</p>
+<p>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.
+</p>
+<p>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 <a href='https://freebsdfoundation.org/freebsd-project/resources/'>how-to guides</a> to facilitate getting more folks to try out FreeBSD.
+</p>
+<p>Check out some of the advocacy and education work we did last quarter:
+</p>
+<ul>
+<li><p>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 <a href='https://freebsdfoundation.org/freebsd-fridays/'>here</a>. We'll be back with new
+    sessions in early 2021.
+</p></li>
+<li><p>Gave a FreeBSD talk at the nerdear.la conference on October 20th.
+</p></li>
+<li><p>Participated in the podcast: <a href='https://freebsdfoundation.org/news-and-events/latest-news/what-the-dev-podcast-a-dive-into-the-freebsd-foundation-on-its-20th-anniversary/'>What the Dev: A Dive into the FreeBSD Foundation on its 20th Anniversary</a>
+</p></li>
+<li><p>Promoted the Foundation's 20th Anniversary in the FossBytes article:
+    <a href='https://freebsdfoundation.org/news-and-events/latest-news/fossbytes-20-years-of-the-freebsd-foundation/'>20 Years of The FreeBSD Foundation</a>
+</p></li>
+<li><p>Continued to promote the FreeBSD Office Hours series.  Videos from the one hour
+    sessions can be found on the Project's <a href='https://www.youtube.com/channel/UCxLxR_oW-NAmChIcSkAyZGQ'>YouTube Channel</a>.  See the Office Hours
+    section of this report for more information.
+</p></li>
+<li><p>Added two new How-To Guides: <a href='https://freebsdfoundation.org/contributing-freebsd-documentation/'>Contributing FreeBSD Documentation</a>
+    and <a href='https://freebsdfoundation.org/freebsd-project/resources/how-to-submit-a-bug-report/'>How to Submit a Bug Report</a>.
+</p></li>
+<li><p>Worked with the organizing committee to host the <a href='https://wiki.freebsd.org/DevSummit/202011'>November 2020 Vendor Summit</a>
+</p></li>
+<li><p>Promoted the <a href='https://freebsdfoundation.org/news-and-events/latest-news/freebsd-essential-to-bringing-cheri-and-arms-morello-processor-to-life/'>use of FreeBSD</a> in regards to CHERI and ARM's Morello Processor
+</p></li>
+<li><p>Authored a <a href='https://www.fosslife.org/beginners-guide-freebsd'>Beginners Guide to FreeBSD</a> for Fosslife.
+</p></li>
+<li><p>Sponsored All Things Open as a Media Sponsor.
+</p></li>
+<li><p>Sponsored OpenZFS Developers Summit at the Bronze level.
+</p></li>
+<li><p>Applied for a virtual stand at FOSDEM 2021.
+</p></li>
+<li><p>Committed to attend the online Apricot 2021.
+</p>
+</li></ul>
+Keep up to date with our latest work in our newsletters:
+<p>https://www.freebsdfoundation.org/news-and-events/newsletter/
+</p>
+<p>Netflix provided an update on how and why they use FreeBSD in our latest
+<a href='https://freebsdfoundation.org/blog/freebsd-case-study-netflix/'>Contributor Case Study</a>.
+</p>
+<p>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/.
+</p>
+<p>You can find out more about events we attended and upcoming events at
+https://www.FreeBSDfoundation.org/news-and-events/.
+</p>
+<h3>Legal/FreeBSD IP</h3>
+
+<p>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.
+</p>
+<p>Go to http://www.FreeBSDfoundation.org to find out how we support FreeBSD and
+how we can help you!
+</p></body></project>
+<project cat='team'>
+<title>FreeBSD Release Engineering Team
</title>
+
+<contact>
+<person>
+<name>FreeBSD Release Engineering Team</name>
+<email>re@FreeBSD.org</email>
+</person>
+</contact>
+
+<links>
+<url href='https://www.freebsd.org/releases/12.2R/schedule.html'>FreeBSD 12.2-RELEASE schedule</url>
+<url href='https://www.freebsd.org/releases/13.0R/schedule.html'>FreeBSD 13.0-RELEASE schedule</url>
+<url href='https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/'>FreeBSD development snapshots</url>
+</links>
+
+<body><p>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.
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>Much of this work was sponsored by Rubicon Communications, LLC (netgate.com)
+and the FreeBSD Foundation.
+</p></body></project>
+<project cat='team'>
+<title>Cluster Administration Team</title>
+
+<contact>
+<person>
+<name>Cluster Administration Team</name>
+<email>clusteradm@FreeBSD.org</email>
+</person>
+</contact>
+
+<links>
+<url href='https://www.freebsd.org/administration.html#t-clusteradm'>Cluster Administration Team members</url>
+</links>
+
+<body><p>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:
+</p>
+<ul>
+<li><p>Finished setting up the Malaysia mirror site, generously hosted by the
+    <a href='https://myren.net.my/'>Malaysian Research &amp; Education Network</a>.  Traffic
+    from Oceania and parts of Asia is now going to this mirror instead of
+    farther away sites like Japan and California.
+</p></li>
+<li><p>Upgraded the package building machines to a version of head from
+    mid-October 2020.
+</p></li>
+<li><p>Upgraded developer machines in the cluster (freefall, ref\* and universe\*) to
+    a version of head from mid-October 2020.
+</p></li>
+<li><p>Installed eight new x86 servers in our New Jersey site:
+    five application servers, two package builders and one mirror server.
+</p><ul>
+<li><p>The new mirror server is in production (pkg0.nyi.freebsd.org).
+</p></li>
+<li><p>The two package builders are in production.
+</p></li>
+<li><p>Two of the application servers have been put into production as the Git
+source of truth and the cgit web frontend, respectively.
+</p></li></ul>
+</li><li><p>Installed two new aarch64 servers in our New Jersey site.  Both are now
+    building aarch64 packages.
+</p></li>
+<li><p>Fixed package mirror synchronisation for powerpc64 packages.
+</p></li>
+<li><p>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.
+</p></li>
+<li><p>Ongoing systems administration work:
+</p><ul>
+<li><p>Accounts management for committers.
+</p></li>
+<li><p>Backups of critical infrastructure.
+</p></li>
+<li><p>Keeping up with security updates in 3rd party software.
+</p>
+</li></ul>
+</li></ul>
+Work in progress:
+
+<ul>
+<li><p>Hardware refreshing for web services, backup version control system in NYI
+</p></li>
+<li><p>Upgrading production machines in the FreeBSD cluster to 12.2
+</p><ul>
+<li><p>Most machines have been upgraded as of mid-December 2020
+</p></li>
+<li><p>Remaining machines will be decommissioned / repurposed after services
+migrate to newer hardware
+</p></li></ul>
+</li><li><p>Supporting Git migration and infrastructure setup
+</p></li>
+<li><p>powerpc pkgbuilder/ref/universal machines
+</p></li>
+<li><p>Preparations for a new mirror site in Australia, to be hosted by
+    <a href='https://www.ix.asn.au'>IX Australia</a>.
+</p></li>
+<li><p>Setup Brazil (BRA) mirror.
+</p></li>
+<li><p>Review the service jails and service administrators operation.
+</p></li>
+<li><p>Searching for more providers that can fit the requirements for a
+    <a href='https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout'>generic mirrored layout</a>
+    or a
+    <a href='https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror'>tiny mirror</a>.
+</p></li></ul>
+</body></project>
+<project cat='team'>
+<title>Continuous Integration</title>
+
+<links>
+<url href='https://ci.FreeBSD.org'>FreeBSD Jenkins Instance</url>
+<url href='https://ci.FreeBSD.org/hwlab'>FreeBSD Hardware Testing Lab</url>
+<url href='https://artifact.ci.FreeBSD.org'>FreeBSD CI artifact archive</url>
+<url href='https://hackmd.io/@FreeBSD-CI'>FreeBSD CI weekly report</url>
+<url href='https://wiki.freebsd.org/Jenkins'>FreeBSD Jenkins wiki</url>
+<url href='https://wiki.freebsd.org/HostedCI'>Hosted CI wiki</url>
+<url href='https://wiki.freebsd.org/3rdPartySoftwareCI'>3rd Party Software CI</url>
+<url href='https://preview.tinyurl.com/y9maauwg'>Tickets related to freebsd-testing@</url>
+<url href='https://github.com/freebsd/freebsd-ci'>FreeBSD CI Repository</url>
+</links>
+
+<contact>
+<person>
+<name>Jenkins Admin</name>
+<email>jenkins-admin@FreeBSD.org</email>
+</person>
+<person>
+<name>Li-Wen Hsu</name>
+<email>lwhsu@FreeBSD.org</email>
+</person>
+</contact>
+<body><p>Contact: <a href='https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing'>freebsd-testing Mailing List</a><br />
+Contact: IRC #freebsd-ci channel on EFNet<br />
+</p>
+<p>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 <a href='https://hackmd.io/@FreeBSD-CI'>weekly CI reports</a>.
+</p>
+<p>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.
+</p>
+<p>Important changes:
+</p>
+<ul>
+<li><p>doc jobs were changed to use git to follow VCS migration:
+</p><ul>
+<li><p>https://ci.freebsd.org/job/FreeBSD-doc-main/
+</p></li>
+<li><p>https://ci.freebsd.org/job/FreeBSD-doc-main-igor/
+    Thanks Brandon Bergren (bdragon@)
+</p></li></ul>
+</li><li><p>head and stable/12 build environment have been upgraded to 12.2-RELEASE
+</p>
+</li></ul>
+New jobs added:
+
+<ul>
+<li><p><a href='https://ci.freebsd.org/job/FreeBSD-head-riscv64-LINT'>LINT kernel of head on riscv64</a>
+</p>
+</li></ul>
+Work in progress:
+
+<ul>
+<li><p>Follow VCS migration, change src jobs to use Git - PRs are
+    <a href='https://github.com/freebsd/freebsd-ci/pull/121'>available</a>;
+    Thanks Brandon Bergren (bdragon@)
+</p></li>
+<li><p>Collecting and sorting CI tasks and ideas
+    <a href='https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo'>here</a>;
+</p></li>
+<li><p>Testing and merging pull requests in the
+    <a href='https://github.com/freebsd/freebsd-ci/pulls'>the FreeBSD-ci repo</a>
+</p></li>
+<li><p>Designing and implementing pre-commit CI building and testing
+</p></li>
+<li><p>Reducing the procedures of CI/test environment setting up for contributors and
+    developers
+</p></li>
+<li><p>Setting up the CI stage environment and putting the experimental jobs on it
+</p></li>
+<li><p>Setting up public network access for the VM guest running tests
+</p></li>
+<li><p>Implementing automatic tests on bare metal hardware
+</p></li>
+<li><p>Adding drm ports building tests against -CURRENT
+</p></li>
+<li><p>Planning to run ztest and network stack tests
+</p></li>
+<li><p>Adding more external toolchain related jobs
+</p></li>
+<li><p>Improving the hardware lab to be more mature and adding more hardware
+</p></li>
+<li><p>Helping more software get FreeBSD support in their CI pipeline
+    Wiki pages: <a href='https://wiki.freebsd.org/3rdPartySoftwareCI'>3rdPartySoftwareCI</a>,
+    <a href='https://wiki.freebsd.org/HostedCI'>HostedCI</a>;
+</p></li>
+<li><p>Working with hosted CI providers to have better FreeBSD support
+</p></li>
+<li><p>The build and test results will be sent to the
+    <a href='https://lists.freebsd.org/mailman/listinfo/dev-ci'>dev-ci mailing list</a>
+    soon. Feedback and help with analysis is very appreciated!
+</p>
+</li></ul>
+Please see freebsd-testing@ related tickets for more WIP information, and don't hesitate to join the effort!
+
+<p>Sponsor: The FreeBSD Foundation
+</p></body></project>
+<project cat='team'>
+<title>Ports Collection</title>
+
+<links>
+<url href='https://www.FreeBSD.org/ports/'>About FreeBSD Ports</url>
+<url href='https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html'>Contributing to Ports</url>
+<url href='http://portsmon.freebsd.org/index.html'>FreeBSD Ports Monitoring</url>
+<url href='https://www.freebsd.org/portmgr/index.html'>Ports Management Team</url>
+<url href='http://ftp.freebsd.org/pub/FreeBSD/ports/ports/'>Ports Tarball</url>
+</links>
+
+<contact>
+<person>
+<name>René Ladan</name>
+<email>portmgr-secretary@FreeBSD.org</email>
+</person>
+<person>
+<name>FreeBSD Ports Management Team</name>
+<email>portmgr@FreeBSD.org</email>
+</person>
+</contact>
+
+<body><p>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.
+</p>
+<p>For the last quarter the dashboard looks like:
+</p>
+<ul>
+<li><p>41500 ports (including flavors)
+</p></li>
+<li><p>2516 open PRs of which 625 are unassigned
+</p></li>
+<li><p>8715 commits to the HEAD branch by 164 committers
+</p></li>
+<li><p>420 commits to the 2020Q4 branch by 59 committers
+</p>
+</li></ul>
+Compared to the third quarter, the PR statistics mostly stayed the same. There
+<p>were slightly fewer commits by the same number of people. The number of ports
+again grew steadily, this time by almost 4 percent.
+</p>
+<p>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.
+</p>
+<p>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@.
+</p>
+<p>Patent limitations have been disconnected from the license framework, given
+that patents are a complex topic with implications varying from one jurisdiction
+to another.
+</p>
+<p>The last quarter saw a number of updates to default versions of ports:
+</p>
+<ul>
+<li><p>librsvg2: "rust" on supported platforms, "legacy"
+    otherwise
+</p></li>
+<li><p>Mono: 5.10
+</p></li>
+<li><p>FPC switched to 3.2.0
+</p></li>
+<li><p>GCC switched to 10 for powerpc64le
+</p></li>
+<li><p>Lazarus switched to 2.0.10
+</p></li>
+<li><p>Ruby switched to 2.7.X
+</p></li>
+<li><p>Samba switched to 4.12
+</p>
+</li></ul>
+During the last quarter, a new virtual category was added: "education" for ports
+<p>that for instance help the user to learn about a certain topic or help
+facilitating examinations.
+</p>
+<p>The @shell and @sample keywords have been rewritten in Lua which makes root-dir
+compliant (see pkg -r) and ensures they are Capsicum-sandboxed.
+</p>
+<p>The last quarter also saw updates to several user-facing ports:
+</p>
+<ul>
+<li><p>Firefox 84.0.1
+</p></li>
+<li><p>Firefox-esr 78.6.0
+</p></li>
+<li><p>Chromium 87.0.4280.88
+</p></li>
+<li><p>Ruby 2.7.2
+</p></li>
+<li><p>Qt5 5.15.2
+</p></li>
+<li><p>XFce 4.16
+</p>
+</li></ul>
+As always, antoine@ was busy running exp-runs, 37 this quarter, testing:
+
+<ul>
+<li><p>various ports upgrades
+</p></li>
+<li><p>changing sys/cdefs.h in base
+</p></li>
+<li><p>adding "set pipefail" to most framework scripts to catch errors earlier
+</p></li>
+<li><p>changing the default locale to C.UTF-8 in base
+</p></li>
+<li><p>using bsdgrep as /usr/bin/grep
+</p></li></ul>
+</body></project>
+<project cat='team'>
+<title>Office Hours</title>
+
+<contact>
+<person>
+<name>Allan Jude</name>
+<email>allanjude@freebsd.org</email>
+</person>
+<person>
+<name>Ed Maste</name>
+<email>emaste@freebsd.org</email>
+</person>
+</contact>
+
+<body><p>During the final quarter of 2020 three office hours sessions were held.
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>The third session was hosted by bhyve maintainers Peter Grehan and John Baldwin
+to present recent development efforts and answer questions about bhyve.
+</p>
+<p>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.
+</p>
+<p>You can find the schedule for future office hours, and videos of past
+office hours on the <a href='https://wiki.freebsd.org/OfficeHours'>FreeBSD Wiki</a>
+</p>
+<p>Sponsor: ScaleEngine Inc.
+</p></body></project>
+<project cat='proj'>
+<title>GPL in Base</title>
+
+<links>
+<url href='https://wiki.freebsd.org/GPLinBase'>GPL Software in the Base System</url>
+</links>
+
+<contact>
+<person>
+<name>Ed Maste</name>
+<email>emaste@FreeBSD.org</email>
+</person>
+<person>
+<name>Kyle Evans</name>
+<email>kevans@FreeBSD.org</email>
+</person>
+<person>
+<name>Baptiste Daroussin</name>
+<email>bapt@FreeBSD.org</email>
+</person>
+</contact>
+
+<body><p>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:
+</p>
+<ul>
+<li><p>gdb (<a href='https://cgit.freebsd.org/src/commit/?id=1c0ea326aa6d'>removed</a>; in favor of lldb in base or devel/gdb in ports)
+</p></li>
+<li><p>gnugrep (<a href='https://cgit.freebsd.org/src/commit/?id=b82a9ec5f53e'>replaced</a>; with bsdgrep)
+</p></li>
+<li><p>libgnuregex (<a href='https://cgit.freebsd.org/src/commit/?id=8aff76fb37b5'>removed</a>)
+</p>
+</li></ul>
+The following component(s) have yet to be claimed.  Some replacement prospects
+<p>may be listed on the above-linked wiki page. Interested parties are welcome to
+evaluate the options to restart the discussion:
+</p>
+<ul>
+<li><p>dialog
+</p></li>
+<li><p>gcov (kernel)
+</p>
+</li></ul>
+The following component(s) have a principal investigator to coordinate work.
+<p>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.
+</p>
+<ul>
+<li><p>diff3 (Contact bapt@ if interested)
+</p></li></ul>
+</body></project>
+<project cat='proj'>
+<title>Git Migration Working Group</title>
+
+<links>
+<url href='https://cgit.FreeBSD.org/src'>src (base system) git repo</url>
+<url href='https://cgit.FreeBSD.org/doc'>doc git repo</url>
+<url href='https://cgit-dev.FreeBSD.org/ports'>Beta ports git repo</url>
+<url href='https://github.com/bsdimp/freebsd-git-docs'>Warner's git documentation repo</url>
+<url href='https://lists.freebsd.org/mailman/listinfo/freebsd-git'>FreeBSD-git mailing list</url>
+<url href='https://github.com/freebsd/git_conv'>Git conversion tooling repo</url>
+<url href='http://gameoftrees.org/'>Game of Trees</url>
+<url href='https://github.com/johnmehr/gitup'>gitup</url>;
+</links>
+
+<contact>
+<person>
+<name>Li-Wen Hsu</name>
+<email>lwhsu@FreeBSD.org</email>
+</person>
+<person>
+<name>Warner Losh</name>
+<email>imp@FreeBSD.org</email>
+</person>
+<person>
+<name>Ed Maste</name>
+<email>emaste@FreeBSD.org</email>
+</person>
+<person>
+<name>Ulrich Spörlein</name>
+<email>uqs@FreeBSD.org</email>
+</person>
+</contact>
+
+<body><p>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.
+</p>
+<p>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.
+</p>
+<p>The doc tree migration occurred on December 8th and 9th.  After the conversion
+some minor changes to the documentation build infrastructure were necessary.
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>Sponsor: The FreeBSD Foundation (in part)
+</p></body></project>
+<project cat='proj'>
+<title>Linux compatibility layer update</title>
+
+<contact>
+<person>
+<name>Edward Tomasz Napierala</name>
+<email>trasz@FreeBSD.org</email>
+</person>
+</contact>
+
+<body><p>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 <a href='https://wiki.freebsd.org/LinuxApps'>Linux app status Wiki page</a>.
+The work has now shifted from command-line apps to desktop applications.
+</p>
+<p>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.
+</p>
+<p>There was a very significant contribution from Conrad Meyer in the form
+of <code>SO_PASSCRED</code> setsockopt(2) support, <code>PR_SETDUMPABLE</code> and <code>PR_GETDUMPABLE</code>
+prctl(2) flags, and also <code>CLONE_FS</code> and <code>CLONE_FILES</code> 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 (<code>--no-sandbox --no-zygote --in-process-gpu</code>)
+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.
+</p>
+<p>Sponsor: The FreeBSD Foundation
+</p></body></project>
+<project cat='proj'>
+<title>LLDB Debugger Improvements</title>
+
+<links>
+<url href='https://www.moritz.systems/blog/lldb-debugger-improvements-for-freebsd/'>Moritz Systems Project Description</url>
+<url href='https://freebsdfoundation.org/blog/guest-blog-foundation-sponsors-freebsd-lldb-improvements/'>FreeBSD Foundation Blog</url>
+<url href='https://github.com/moritz-systems/llvm-project'>Git Repository</url>
+</links>
+
+<contact>
+<person>
+<name>Kamil Rytarowski</name>
+<email>kamil@moritz.systems</email>
+</person>
+<person>
+<name>Michał Górny</name>
+<email>mgorny@moritz.systems</email>
+</person>
+</contact>
+
+<body><p>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.
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>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.
+</p>
+<p>The introduced changes are expected to be shipped with LLDB 12.0, and where
+applicable in FreeBSD 13.0.
+</p>
+<p>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.
+</p>
+
+<p>Sponsor: The FreeBSD Foundation<br />
+</p></body></project>
+<project cat='proj'>
+<title>Upstreaming NetApp Changes</title>
+
+<links>
+<url href='https://klarasystems.com/freebsd-development/'>Klara Inc.</url>
+</links>
+
*** 1772 LINES SKIPPED ***



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202101161426.10GEQO31089023>