From owner-svn-doc-head@freebsd.org  Wed Oct 21 18:50:28 2020
Return-Path: <owner-svn-doc-head@freebsd.org>
Delivered-To: svn-doc-head@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 3099D42A9A9;
 Wed, 21 Oct 2020 18:50:28 +0000 (UTC)
 (envelope-from trasz@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 "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 4CGfh40sWTz4dNX;
 Wed, 21 Oct 2020 18:50:28 +0000 (UTC)
 (envelope-from trasz@FreeBSD.org)
Received: from repo.freebsd.org (repo.freebsd.org
 [IPv6:2610:1c1:1:6068::e6a:0])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 00C089DFB;
 Wed, 21 Oct 2020 18:50:28 +0000 (UTC)
 (envelope-from trasz@FreeBSD.org)
Received: from repo.freebsd.org ([127.0.1.37])
 by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id 09LIoRUW080799;
 Wed, 21 Oct 2020 18:50:27 GMT (envelope-from trasz@FreeBSD.org)
Received: (from trasz@localhost)
 by repo.freebsd.org (8.15.2/8.15.2/Submit) id 09LIoROM080797;
 Wed, 21 Oct 2020 18:50:27 GMT (envelope-from trasz@FreeBSD.org)
Message-Id: <202010211850.09LIoROM080797@repo.freebsd.org>
X-Authentication-Warning: repo.freebsd.org: trasz set sender to
 trasz@FreeBSD.org using -f
From: Edward Tomasz Napierala <trasz@FreeBSD.org>
Date: Wed, 21 Oct 2020 18:50:27 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
 svn-doc-head@freebsd.org
Subject: svn commit: r54617 - head/en_US.ISO8859-1/htdocs/news/status
X-SVN-Group: doc-head
X-SVN-Commit-Author: trasz
X-SVN-Commit-Paths: head/en_US.ISO8859-1/htdocs/news/status
X-SVN-Commit-Revision: 54617
X-SVN-Commit-Repository: doc
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.33
Precedence: list
List-Id: SVN commit messages for the doc tree for head
 <svn-doc-head.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/svn-doc-head>,
 <mailto:svn-doc-head-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-head/>
List-Post: <mailto:svn-doc-head@freebsd.org>
List-Help: <mailto:svn-doc-head-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/svn-doc-head>,
 <mailto:svn-doc-head-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 18:50:28 -0000

Author: trasz
Date: Wed Oct 21 18:50:27 2020
New Revision: 54617
URL: https://svnweb.freebsd.org/changeset/doc/54617

Log:
  Create 2020q2 status report, covering June 2020 to September 2020.
  
  Submitted by:	debdrup
  Differential Revision:	https://reviews.freebsd.org/D26890

Added:
  head/en_US.ISO8859-1/htdocs/news/status/report-2020-07-2020-09.xml   (contents, props changed)
Modified:
  head/en_US.ISO8859-1/htdocs/news/status/Makefile

Modified: head/en_US.ISO8859-1/htdocs/news/status/Makefile
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/Makefile	Tue Oct 20 13:39:06 2020	(r54616)
+++ head/en_US.ISO8859-1/htdocs/news/status/Makefile	Wed Oct 21 18:50:27 2020	(r54617)
@@ -88,6 +88,7 @@ XMLDOCS+=	report-2019-07-2019-09
 XMLDOCS+=	report-2019-10-2019-12
 XMLDOCS+=	report-2020-01-2020-03
 XMLDOCS+=	report-2020-04-2020-06
+XMLDOCS+=	report-2020-07-2020-09
 XSLT.DEFAULT=	report.xsl
 
 # Install a sample <project> entry.

Added: head/en_US.ISO8859-1/htdocs/news/status/report-2020-07-2020-09.xml
==============================================================================
--- /dev/null	00:00:00 1970	(empty, because file is newly added)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2020-07-2020-09.xml	Wed Oct 21 18:50:27 2020	(r54617)
@@ -0,0 +1,2172 @@
+<?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:
+     07     - report month start
+     09      - 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>07-09</month>
+
+    <year>2020</year>
+  </date>
+
+  <section>
+    <title>Introduction</title>
+<p>This report covers FreeBSD related projects for the period between
+July and September, and is the third of four planned reports for 2020.
+</p>
+<p>This quarter brings a good mix of additions and changes to the FreeBSD
+Project and community, from a diverse number of teams and people covering 
+everything from architectures, continuous integration, wireless networking
+and drivers, over drm, desktop and third-party project work, as well as
+several team reports, along with many other interesting subjects too
+numerous to mention.
+</p>
+<p>As the world is still affected by the epidemic, we hope that this report
+can also serve as a good reminder that there is good work that can be done
+by people working together, even if we're apart.
+</p>
+<p>We hope you'll be as interested in reading it, as we've been in making 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 other organizations, we put policies in place for all of our staff members
+to work from home.  We also put a temporary ban on travel for staff members.
+We are continuing our work supporting the community and Project, but some of
+our work and responses may be 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 Q3 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>We are currently scheduling Zoom company meetings for Q4, please reach out if
+you would like to schedule a meeting with us.
+</p>
+<h3>Fundraising Efforts</h3>
+
+<p>Last quarter we raised $192,874.43!  Thank you to the individuals and
+organizations that stepped in, to help fund our efforts.  We'd like to thank
+Arm for their large contribution last quarter, which helped bring our 2020
+fundraising effort to $521k.  We hope other organizations will follow their
+lead and give back to help us continue supporting FreeBSD.
+</p>
+<p>These are trying times, and we deeply appreciate every donation that has come
+in from $5 to $150,000. We're still here giving 110% to supporting FreeBSD!
+</p>
+<p>We are 100% funded by donations, and those funds go towards software
+development work to improve FreeBSD, FreeBSD advocacy around the world, keeping
+FreeBSD secure, continuous integration improvements, sponsoring BSD-related and
+computing conferences (even the virtual events!), legal support for the
+Project, and many other areas.
+</p>
+<p>Please consider making a
+<a href='https://www.FreeBSDfoundation.org/donate/.'>donation to help us continue and increase our support for FreeBSD</a>.
+</p>
+<p>We also have the Partnership Program, to provide more benefits for our larger
+commercial donors.  Find out more information about the
+<a href='https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/'>partnership program</a>
+and share with your companies!
+</p>
+<h3>OS Improvements</h3>
+
+<p>A number of FreeBSD Foundation grant recipients started, continued working on,
+or completed projects during the third quarter.  These include:
+</p><ul>
+<li><p>Ongoing WiFi and Linux KPI layer improvements.
+</p></li>
+<li><p>Linuxulator application compatibility.
+</p></li>
+<li><p>DRM / Graphics driver updates.
+</p></li>
+<li><p>Zstd compression for OpenZFS.
+</p></li>
+<li><p>Online RAID-Z expansion.
+</p></li>
+<li><p>Modernized LLDB target support for FreeBSD.
+</p>
+</li></ul>
+You can find more details about most of these projects in other quarterly
+<p>reports.
+</p>
+<p>Staff members also worked on a number of larger projects, including:
+</p><ul>
+<li><p>Run-Time Dynamic Linker (rtld) and kernel ELF loader improvements.
+</p></li>
+<li><p>Rewritten UNIX domain socket locking.
+</p></li>
+<li><p>Build infrastructure.
+</p></li>
+<li><p>Open system call path handling support for O_BENEATH, O_RESOLVE_BENEATH.
+</p></li>
+<li><p>arm64 support.
+</p></li>
+<li><p>Migration to a Git repository.
+</p>
+</li></ul>
+Many of these projects also have detailed entries in other quarterly report
+<p>entries.
+</p>
+<p>Staff members also put in significant effort in many ways other than larger,
+individual projects.  These include assisting with code reviews, bug report
+triage, security report triage and advisory handling, addressing syzkaller
+reports, and ongoing maintenance and bug fixes in functional areas such as the
+tool chain, developer tools, virtual memory kernel subsystem, low-level x86
+infrastructure, sockets and protocols, and others.
+</p>
+<h3>University of Waterloo Co-op</h3>
+
+<p>With the transition to working from home, the Foundation decided to again take
+on three University of Waterloo Co-op students for the Fall 2020 term
+(September to December).  Tiger returns for a second term, joined by new
+students Yang and Zac.  Projects for the term include more work on
+ELF Tool Chain, application of Capsicum to additional utilities, testing and
+integration of FreePBX and Asterisk VOIP software, pkgbase, and exploring
+containerization tooling.
+</p>
+<h3>Continuous Integration and Quality Assurance</h3>
+
+<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 third 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 setting up of
+dedicated VM host for running tests is completed.  New feature developments
+and the CI staging environment is in progress.  We are also working with
+other teams in the Project for their testing needs. For example, tests of
+non-x86 architectures now run periodically, and improve the CI of the
+embedded systems. We are also working with many external projects and
+companies to improve the CI between their products and FreeBSD.
+</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 Bridgewater site, where most of the 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>Spamhaus spam filtering software to limit the amount of spam on the mailing
+   lists.
+</p></li>
+<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 and provide a lot more IOPS to
+   avoid the slowdowns seen during peak times of the day where the disks just
+   cannot keep up with the request volume.
+</p></li>
+<li><p>1 server for exp-runs 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.  As is
+the case for most of us in this industry, COVID-19 has put our in-person events
+on hold.  In addition to attending 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.
+</p>
+<p>Check out some of the advocacy and education work we did last quarter:
+</p><ul>
+<li><p>Launched our FreeBSD Fridays series of 101 classes.  Topics included an
+   Introduction to FreeBSD, FreeBSD Installfest, Introduction to Security,
+   Introduction to ZFS and more.  Videos of the past sessions and a schedule of
+   upcoming events can be found <a href='https://freebsdfoundation.org/freebsd-fridays/'>here</a>.
+</p></li>
+<li><p>Attended and presented at OSI's State of the Source conference.  The event
+   was held virtually, September 9-11, 2020.
+</p></li>
+<li><p>Launched the
+   <a href='https://freebsdfoundation.org/blog/weve-got-a-new-look/'>redesign</a>
+   of the FreeBSD Foundation Website.
+</p></li>
+<li><p><a href='https://freebsdfoundation.org/news-and-events/latest-news/freebsd-foundation-celebrates-20th-anniversary/'>Announced</a>
+   the 20th Anniversary of the FreeBSD Foundation.
+</p></li>
+<li><p>Participated as an Admin for Google Summer of Code 2020
+</p></li>
+<li><p>Continued to promote the FreeBSD Office Hours series including holding our
+   own Foundation led office hours.  Videos from the one hour sessions can be
+   found on the Project's
+   <a href='https://www.youtube.com/c/FreeBSDProject'>YouTube Channel</a>.  You can watch
+   ours <a href='https://www.youtube.com/watch?v=Ji4ux4FWpRU'>here</a>.
+</p></li>
+<li><p><a href='https://freebsdfoundation.org/blog/freebsd-core-team-10-in-review/'>Interviewed</a>
+   members of the outgoing FreeBSD Core Team to get their thoughts on their
+   term.
+</p></li>
+<li><p>Began working with the FreeBSD Vendor Summit planning committee on the
+   <a href='https://wiki.freebsd.org/DevSummit/202011'>November 2020 Vendor Summit</a>.
+</p></li>
+<li><p>Promoted the Foundation's 20th Anniversary and our work to support the
+   FreeBSD Project in the It's FOSS Article.
+   <a href='https://itsfoss.com/freebsd-foundation-20-years/'>FreeBSD Foundation Celebrates 20 Years of Promoting and Supporting FreeBSD Project</a>.
+</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>Committed to sponsoring All Things Open as a media Sponsor.
+</p></li>
+<li><p>Committed to sponsoring the OpenZFS Developers Summit at the Bronze level.
+</p></li>
+<li><p>Became an International RISC-V Member.
+</p></li>
+<li><p>Committed to giving a FreeBSD talk at the nerdear.la conference on
+   October 20th.
+</p>
+</li></ul>
+Keep up to date with our latest work in our
+<p><a href='https://www.freebsdfoundation.org/news-and-events/newsletter/'>monthly newsletters</a>.
+</p>
+<p>Netflix provided an update on how and why they use FreeBSD in our latest
+<a href='https://freebsdfoundation.org/wp-content/uploads/2020/10/netflixcasestudy_final.pdf'>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.  We updated our
+<a href='https://freebsdfoundation.org/legal/trademark-usage-terms-and-conditions/'>Trademark Usage Terms and Conditions</a>
+on July 1, 2020.
+</p>
+<p>Go to <a href='http://www.FreeBSDfoundation.org/'>the FreeBSD Foundation's web site</a> to
+find out how we support FreeBSD and how we can help you!
+</p>
+<p>### Other
+</p>
+<p>We welcomed Andrew Wafaa and Kevin Bowling to our board of directors, to help
+govern the Foundation and guide us with our strategic direction.  We have
+<a href='https://freebsdfoundation.org/blog/freebsd-foundation-welcomes-new-board-members-2/'>more information about our new board members</a>
+on our website.
+</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/where.html#helptest'>FreeBSD 12.2 test builds</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 third quarter of 2020, the Release Engineering Team started
+work on the 12.2-RELEASE cycle, the third release from the stable/12
+branch.
+</p>
+<p>As of this writing, two BETA builds have been released, with the
+expectation there will be a third BETA build currently remaining on the
+schedule.
+</p>
+<p>The 12.2-RELEASE cycle will continue throughout October, with two RC
+builds currently planned, and RC3 scheduled on an as-needed basis.  The
+12.2-RELEASE is so far scheduled for final release on October 27.
+</p>
+<p>In addition to the 12.2-RELEASE, Glen Barber of the Release Engineering
+Team finished work to the release build tools and scripts to prepare for
+the conversion from Subversion to Git for the 13.0-RELEASE cycle.  There
+are no plans to merge these changes to stable branches at this time; as
+discussed within the Git working group, we feel such a change on a stable
+branch would be too intrusive to our user base as well as downstream
+FreeBSD consumers.  Development snapshot builds for 13.0-CURRENT have
+recently been built from the Git tree within the project, and further
+snapshot builds for 12.x and 11.x will continue to be built from Subversion.
+</p>
+<p>Additionally throughout the quarter, several development snapshots builds
+were released for the <i>head</i>, <i>stable/12</i>, and <i>stable/11</i> branches.
+</p>
+<p>Finally, the Release Engineering Team would like to thank Marius Strobl
+for his time serving on the team; he had recently stepped down from the
+Deputy RE Lead role due to constraints on his time.  The Team welcomes
+Colin Percival, who has accepted fulfilling this role.
+</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>Work with the FreeBSD Foundation on hardware update for web services, mirror and package building servers.
+</p></li>
+<li><p>Disable directory indexing on the package mirrors to resolve performance issues of the machine.
+</p><ul>
+<li><p>This was later relaxed to allow indexing of the parent directories but still disallow the large package directories.
+</p></li></ul>
+</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>Setup Malaysia (KUL) mirror.
+</p></li>
+<li><p>Setup Brazil (BRA) mirror.
+</p></li>
+<li><p>Review the service jails and service administrators operation.
+</p></li>
+<li><p>Infrastructure of building aarch64 and powerpc64 packages.
+</p><ul>
+<li><p>NVMe issues on PowerPC64 POWER9 blocking dual socket machine from being used as pkg builder.
+</p></li>
+<li><p>Drive upgrade test for pkg builders (SSDs) courtesy of the FreeBSD Foundation.
+</p></li>
+<li><p>Boot issues with Aarch64 reference machines.
+</p></li></ul>
+</li><li><p>New NYI.net sponsored colocation space in Chicago-land area.
+</p></li>
+<li><p>Work with git working group for the git repository.
+</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 codes 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 third quarter of 2020, we continued working with the contributors and
+developers in the project to fulfill 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>All !x86 -test builds now trigger a new build on 22:00 UTC daily; this was
+   not running very often because running all the tests in qemu takes lots
+   of time.  The work on improving the test execution speed and parallelism is
+   in progress.  The following is a list of the jobs affected:
+</p><ul>
+<li><p><a href='https://ci.freebsd.org/job/FreeBSD-head-armv7-test/'>Test build for FreeBSD HEAD on ARMv7</a>.
+</p></li>
+<li><p><a href='https://ci.freebsd.org/job/FreeBSD-head-aarch64-test/'>Test build for FreeBSD HEAD on AArch64</a>.
+</p></li>
+<li><p><a href='https://ci.freebsd.org/job/FreeBSD-head-mips64-test/'>Test build for FreeBSD HEAD on MIPS64</a>.
+</p></li>
+<li><p><a href='https://ci.freebsd.org/job/FreeBSD-head-powerpc64-test/'>Test build for FreeBSD HEAD on PowerPC64</a>.
+</p></li>
+<li><p><a href='https://ci.freebsd.org/job/FreeBSD-head-riscv64-test/'>Test build for FreeBSD HEAD on RISC-V64</a>.
+</p>
+</li></ul>
+</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>
+<ul>
+<li><p>A builder dedicated to run jobs using provisioned VMs is setup, this
+    improves the stableness and reduces the execution time.
+</p>
+</li>
+<li><p>The result of <a href='https://ci.freebsd.org/job/FreeBSD-head-amd64-test_zfs'>FreeBSD-head-amd64-test_zfs</a>
+    is changed after OpenZFS importing; we encourage everyone to check and fix the
+    failing and skipped test cases.
+</p>
+</li></ul>
+</li></ul>
+New jobs added:
+<ul>
+<li><p><a href='https://ci.freebsd.org/job/FreeBSD-head-powerpc64le-build/'>CI build for FreeBSD HEAD on PowerPC64LE</a>.
+</p>
+</li></ul>
+Work in progress:
+<ul>
+<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>Reduce 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 3rd software get CI on FreeBSD through a hosted CI solution.
+</p></li>
+<li><p>Working with hosted CI providers to have better FreeBSD support.
+</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>  
+</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>We passed the landmark of 40,000 ports in the Ports Collection
+and are now around 40,400 ports.  The last quarter saw 9335
+commits to the HEAD branch and 481 commits to the 2020Q3 branch
+by respectively 167 and 63 committers.  There are currently 2525
+open problem reports of which 595 are unassigned.  Compared to
+last quarter, this means a slight decrease in activity and also
+a slight increase in open PRs.
+</p>
+<p>During the last quarter we welcomed Rainer Hurling (rhurlin@) and
+said goodbye to Kevin Lo (kevlo@) and Grzegorz Blach (gblach@).
+</p>
+<p>The last three months saw new default versions for Perl (5.32),
+PostgreSQL (12) and PHP (7.4). Various packages also got updated:
+Firefox to 81.0.1, Chromium to 84.0.4147.135, Gnome to 3.36,
+Xorg to 1.20.9, Qt5 to 5.15.0, Emacs to 27.1, KDE Frameworks to
+5.74.0 and pkg itself to 1.15.8.
+</p>
+<p>Never tired, antoine@ ran 30 exp-runs to test port version updates,
+on such diverse matters as:
+</p><ul>
+<li><p>Updating byacc in base to 20200330.
+</p></li>
+<li><p>Check balancing of sed "y" command.
+</p></li>
+<li><p>Use of brackets.
+</p></li>
+<li><p>Removing the now redundant "port" argument from USES=readline.
+</p></li></ul>
+</body></project>
+<project cat='team'>
+<title>FreeBSD Office team - 3rd quarter 2020 report</title>
+
+<links>
+<url href='https://wiki.freebsd.org/Office'>The FreeBSD Office project</url>  
+</links>
+
+<contact>
+<person>
+<name>FreeBSD Office team ML</name>
+<email>office@FreeBSD.org</email>
+</person>
+<person>
+<name>Dima Panov</name>
+<email>fluffy@FreeBSD.org</email>
+</person>
+<person>
+<name>Li-Wen Hsu</name>
+<email>lwhsu@FreeBSD.org</email>
+</person>
+</contact>
+
+
+<body><p>The FreeBSD Office team works on a number of office-related software suites 
+and tools such as OpenOffice and LibreOffice.<br />
+</p>
+<p>Work during this quarter focused on providing the latest stable release of 
+LibreOffice suite and companion apps to all FreeBSD users.
+</p>
+<ul>
+<li><p>Alongside with updating old stable branch to latest 6.4.x releases, 
+ current ports-tree now have a full-featured cutting-edge 7.0.1 bundle.<br />
+</p></li>
+<li><p>Conservative users can keep 6.4.x stable version by switching to use 
+ all-in-one editors/libreoffice6 port and even with i18n language pack (off by default). 
+ It will be kept updated at least till 7.1.0 version is released.<br />
+</p>
+</li></ul>
+We are looking for people to help the project.
+<p>All unstable work with LibreOffice snapshots is staged in our <a href='https://github.com/lwhsu/freebsd-ports-libreoffice'>WIP repository</a>.<br />
+The <a href='https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=open&amp;email1=office%40FreeBSD.org&amp;emailassigned_to1=1&amp;emailcc1=1&amp;emailreporter1=1&amp;emailtype1=substring&amp;query_format=advanced&amp;list_id=374316'>open bugs list</a>
+contains all filed issues which need some attention.
+Patches, comments and objections are always welcome in the mailing list and bugzilla.
+</p>
+</body></project>
+<project cat='team'>
+<title>FreeBSD Graphics Team status report</title>
+
+<links>
+<url href='https://github.com/FreeBSDDesktop'>Project GitHub page</url>
+</links>
+
+<contact>
+<person>
+<name>FreeBSD Graphics Team</name>
+<email>x11@freebsd.org</email>
+</person>
+<person>
+<name>Niclas Zeising</name>
+<email>zeising@freebsd.org</email>
+</person>
+</contact>
+
+<body><p>The FreeBSD X11/Graphics team maintains the lower levels of the FreeBSD graphics
+stack.
+This includes graphics drivers, graphics libraries such as the
+MESA OpenGL implementation, the X.org xserver with related libraries and
+applications, and Wayland with related libraries and applications.
+</p>
+<p>There have been several updates to the FreeBSD graphics stack and related
+libraries since the last report.
+</p>
+<p>Most notably, MESA related ports were changed to use the meson build system,
+instead of the autotools based one.
+This was needed since mesa upstream has deprecated and removed the autotools
+build system, and this paved the way for further mesa updates.
+While there was a need for a few minor corrections after the initial update,
+this update has been successful and made it possible to further update and
+improve the FreeBSD mesa port.
+</p>
+<p>There have also been several security fixes for <code>xorg-server</code> and <code>libX11</code>, so
+these ports have been updated to fix these issues.
+</p>
+<p>During the period, FreeBSD 12 was changed to improve the compatibility with
+input devices using udev/evdev and libinput.
+This change removes the need for local configuration and makes most mice,
+touchpads and keyboards work out of the box.
+This change will be in the upcoming FreeBSD 12.2 release.
+</p>
+<p>There have also been several updates to various libraries, both in the graphics
+and input stacks, and several userland drivers have been updated.
+Libraries such as <code>libdrm</code> and <code>libevdev</code> have been updated to include new 
+FreeBSD support, developed by team members and added upstream.
+</p>
+<p>There has also been ongoing work to keep the various drm-kmod ports and packages
+up to date, mostly in response to changes in various FreeBSD versions.
+</p>
+<p>We have also continued our regularly scheduled bi-weekly meetings.
+</p>
+<p>People who are interested in helping out can find us on the x11@FreeBSD.org
+mailing list, or on our <a href='https://gitter.im/FreeBSDDesktop/Lobby'>gitter chat</a>.
+We are also available in #freebsd-xorg on EFNet.
+</p>
+<p>We also have a team area <a href='https://github.com/FreeBSDDesktop'>on GitHub</a> where our work repositories can be found.
+</p></body></project>
+<project cat='proj'>
+<title>FreeBSD on Microsoft HyperV and Azure</title>
+
+<links>
+<url href='https://wiki.freebsd.org/MicrosoftAzure'>Microsoft Azure article on FreeBSD wiki</url>  
+<url href='https://wiki.freebsd.org/HyperV'>Microsoft HyperV article on FreeBSD wiki</url>  
+</links>
+
+<contact>
+<person>
+<name>FreeBSD Integration Services Team</name>
+<email>bsdic@microsoft.com</email>
+</person>
+<person>
+<name>Wei Hu</name>
+<email>whu@FreeBSD.org</email>
+</person>
+<person>
+<name>Li-Wen Hsu</name>
+<email>lwhsu@FreeBSD.org</email>
+</person>
+</contact>
+
+<body><p>Li-Wen is working on the FreeBSD release code related to Azure for
+the -CURRENT, 12-STABLE and 11-STABLE branches.
+The work-in-progress is available <a href='https://reviews.freebsd.org/D23804'>here</a>.
+The <a href='https://azuremarketplace.microsoft.com/marketplace/apps/thefreebsdfoundation.freebsd-11_4'>11.4-RELEASE image on Azure Marketplace</a> is published.
+We are testing the releng/12.2 branch and 12.2-RELEASE image will be
+published to Azure Marketplace soon after released.
+</p>
+<p>This project is sponsored by The FreeBSD Foundation, with resources provided by Microsoft.
+</p></body></project>
+<project cat='proj'>
+<title>Building FreeBSD on non-FreeBSD hosts</title>
+
+<links>
+<url href='https://wiki.freebsd.org/BuildingOnNonFreeBSD'>Wiki</url>  
+</links>
+
+<contact>
+<person>
+<name>Alex Richardson</name>
+<email>arichardson@freebsd.org</email>
+</person>
+</contact>
+
+<body><p>Until recently FreeBSD could only be built on a FreeBSD host.
+However, many popular free CI tools only allow building on Linux or macOS and
+therefore can not be used for building the FreeBSD base system. Furthermore, it
+is sometimes useful to cross-build FreeBSD for a remote machine or an emulator
+even if the build machine is not running FreeBSD.
+The goal of this project is to allow building the base system on Linux and macOS
+hosts.
+</p>
+<p>I started this project in 2017 to allow building <a href='https://github.com/CTSRD-CHERI/cheribsd'>CheriBSD</a> on the Linux servers
+and desktops that many of us working on the <a href='http://www.cheri-cpu.org'>CHERI project</a> use.
+The first few patches were upstreamed in 2018 (see the 2018q3 report) and
+I merged the full set of patches to CheriBSD shortly after. Over the past two
+years I have slowly been upstreaming the remaining patches and finally committed
+the last required change in time for this report.
+</p>
+<p>As of September 2020 it should be possible to use the <code>buildworld</code> and
+<code>buildkernel</code> make targets to build a fully-functional FreeBSD installation
+on macOS and Linux hosts. We use this in our continuous integration system to
+build and test CheriBSD disk images for multiple architectures.
+I have also committed a <a href='https://github.com/features/actions'>GitHub Actions</a> configuration upstream
+that takes approximately 10 minutes to build an amd64 kernel. 
+This will ensure that changes that break crossbuilding from Linux/macOS
+can be detected easily.
+</p>
+<p>Upstreaming the crossbuilding changes has resulted in various build system
+cleanups. For example, we now <a href='https://reviews.freebsd.org/rS365836'>no longer need to use lorder.sh</a>
+when building libraries which speeds up the linking step a bit.
+The portability and bootstrapping changes should also make it easier
+to upgrade from older versions since we no longer rely on host headers in
+<code>/usr/include</code> matching those of the target system (e.g. when bootstrapping
+localedef, etc.).
+</p>
+<p>While this support for building on Linux and macOS should still be considered
+experimental, it should work in many cases. If you would like to give it a try,
+the following command line should successfully build an amd64 world on Linux
+and macOS systems that have packages for LLVM 10 (or newer) installed:
+<code>MAKEOBJDIRPREFIX=/somewhere ./tools/build/make.py TARGET=amd64 TARGET_ARCH=amd64 buildworld</code>
+Builds must be performed using the <code>./tools/build/make.py</code> wrapper script since
+most Linux and macOS systems do not ship an appropriate version of bmake.
+Please let me know if you encounter any issues.
+</p>
+<p>Sponsor: DARPA
+</p></body></project>
+<project cat='proj'>
+<title>Git Migration Working Group</title>
+
+<links>
+<url href='https://github.com/freebsd/git_conv'>Git conversion tooling repo</url>  
+<url href='https://lists.freebsd.org/mailman/listinfo/freebsd-git'>FreeBSD-git mailing list</url>  
+<url href='https://cgit-beta.FreeBSD.org/doc'>Beta doc git repo</url>  
+<url href='https://cgit-beta.FreeBSD.org/ports'>Beta ports git repo</url>  
+<url href='https://cgit-beta.FreeBSD.org/src'>Beta src git repo</url>  
+</links>
+
+<contact>
+<person>
+<name>Ed Maste</name>
+<email>emaste@FreeBSD.org</email>
+</person>
+<person>
+<name>Warner Losh</name>
+<email>imp@FreeBSD.org</email>
+</person>
+<person>
+<name>Ulrich Spörlein</name>
+<email>uqs@FreeBSD.org</email>
+</person>
+</contact>
+
+<body><p>Work continues on FreeBSD's migration from Subversion to Git.  Ulrich has
+addressed all known issues with svn2git and has been able to work around the
+inconsistent metadata and forced commit issues in the Subversion history.
+</p>
+<p>We still have additional documentation to write, and need to finish installing
+commit hooks (e.g. restricting branch creation, or ensuring appropriate data
+exists on cherry-pick commits).
+</p>
+<p>We expect to open the beta repository to test commits before the end of
+October.  This is to allow testing of the commit hooks, and to allow developers
+to test access and become familiar with git operation.  Commits in this
+repository will be deleted and the repository will be recreated at least once
+prior to the final migration.
+</p>
+<p>Those with an interest in the migration to Git are encouraged to subscribe
+to the
+<a href='https://lists.freebsd.org/mailman/listinfo/freebsd-git'>FreeBSD-git mailing list</a>
+and test out the beta src, ports, and/or doc repositories.
+</p>
+<p>You are also welcome check out the wiki, issues, README and other documentation
+at the <a href='https://github.com/freebsd/git_conv'>Git conversion tooling repo</a>.
+</p>
+<p>We currently expect to transition the src and doc repositories in mid-November.
+Additional investigation and experimentation with the ports repository is still
+underway.
+</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>
+<person>
+<name>Mark Johnston</name>
+<email>markj@FreeBSD.org</email>
+</person>
+</contact>
+
+<body><p>Earlier Linuxulator work focused on code cleanups and improving
+diagnostic tools.
+Work has now shifted from cleanups to fixing actual applications.
+Current status is being tracked at <a href='https://wiki.freebsd.org/LinuxApps'>Linux app status Wiki page</a>.
+Initial focus was on applications that don't involve X11, mostly
+because they tend to be easier to test and debug, and the bug fixes
+are not application-specific.
+</p>
+<p>Foundation-sponsored work during this quarter included implementing
+a devfs(5) workaround to fix gettynam(3) inside jail/chroot, and
+workaround for the missing splice(2) syscall, which caused problems
+for grep and autotools. The Linux version reported to userspace was bumped
+to 3.10.0, which matches the kernel shipped with RHEL 7 and is neccessary
+for IBM's DB2 database installation to succeed.  The BLKPBSZGET ioctl neccessary for
+Oracle database is supported now.  There is now support for kcov(4),
+neccessary for syzcaller; as well as a number of fixes for issues
+reported by syzcaller, such as futex lock leaks.
+There were also more cleanups, including moving
+some Linuxulator-specific functionality related to error handling off
+from the syscall's fast code paths.  The sysutils/debootstrap port,
+which provides an easy way to create Debian or Ubuntu jail, was updated
+to version 1.0.123.  Finally there were some improvements
+to the <a href='https://wiki.freebsd.org/LinuxJails'>documentation</a>.
+</p>
+<p>Most of those changes have been merged to FreeBSD 12-STABLE, in order
+to ship with 12.2-RELEASE.
+</p>
+<p>There is increased involvement from other developers; this includes termios
+performance fixes, improved memfd support, implementing <code>CLOCK_MONOTONIC_RAW</code>
+required for Steam, madvise improvements, new <code>compat.linux.use_emul_path</code>
+sysctl.  There is also ongoing work
+on tracking down the causes of failures related to Steam and WebKit, with
+fixes being first implemented in <a href='https://github.com/shkhln/linuxulator-steam-utils/wiki/Compatibility'>linuxulator-steam-utils</a>.
+</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://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>FreeBSD includes LLDB, the debugger in the LLVM family, 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
+relies on an obsolete plugin model in LLDB that causes growing
+technical debt. This project aims 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 supports the executed 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 will both be performed using
+the same approach.
+</p>
+<p>After the migration to the new process model is complete, the project
+will include reviewing the results of LLDB's test suite and fixing
+tests as time permits. The work is expected to be complete in 2020.
+</p>
+<p>The project schedule is divided into three milestones, each taking approximately
+one month:
+</p>
+<p>  1. Introduce new FreeBSD Remote Process Plugin for x86_64 with basic support and upstream to LLVM.
+  2. Ensure and add the mandated features in the project (process launch, process attach (pid), process attach (name), userland core files, breakpoints, watchpoints, threads, remote debugging) for FreeBSD/amd64 and FreeBSD/i386.
+  3. Iterate over the LLDB tests. Detect, and as time permits, fix bugs. Ensure bug reports for each non-fixed and known problem. Add missing man pages and update the FreeBSD Handbook.
+</p>
+<p>We are nearing the completion of the first milestone. The new plugin is getting into
+shape, and it can already run simple single-threaded programs. The supported features
+include single-stepping, breakpoints, memory and register I/O on amd64.
+Both plugins are supported simultaneously. The new plugin is used if
+FREEBSD_REMOTE_PLUGIN environment variable is set to any value, or if lldb-server is
+spawned directly. Otherwise, the old plugin is used for compatibility. Once the new
+plugin matures, we are planning to enable it unconditionally on the architectures that
+it is ported to.
+</p>
+<p>Sponsor: The FreeBSD Foundation<br />
+</p></body></project>
+<project cat='proj'>
+<title>Lua usage in FreeBSD</title>
+
+<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>Ryan Moeller</name>
+<email>freqlabs@FreeBSD.org</email>
+</person>
+</contact>
+
+<body><p>During this quarter, flua (FreeBSD Lua) <a href='https://svnweb.freebsd.org/base/?view=revision&amp;revision=r364182'>was taught</a>
+where to find base .lua modules in order to support <code>require</code> of .lua modules
+to be provided by the base system.  flua also <a href='https://svnweb.freebsd.org/base/?view=revision&amp;revision=r364222'>gained support</a>
+for <code>require</code> of binary modules.
+</p>
+<p>A review for <a href='https://reviews.freebsd.org/D26080'>libjail bindings</a> has also
+been submitted, pending review.  libjail is an essential component if one wants
+to be able to write jail management utilities in flua.

*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***