svn commit: r54351 - head/en_US.ISO8859-1/htdocs/news/status
Edward Tomasz Napierala
trasz at FreeBSD.org
Wed Jul 15 17:31:00 UTC 2020
Author: trasz
Date: Wed Jul 15 17:30:58 2020
New Revision: 54351
URL: https://svnweb.freebsd.org/changeset/doc/54351
Log:
Create 2020Q2 quarterly status report, covering April 2020 - June 2020.
Submitted by: debdrup
Differential Revision: https://reviews.freebsd.org/D25678
Added:
head/en_US.ISO8859-1/htdocs/news/status/report-2020-04-2020-06.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 Wed Jul 15 13:57:41 2020 (r54350)
+++ head/en_US.ISO8859-1/htdocs/news/status/Makefile Wed Jul 15 17:30:58 2020 (r54351)
@@ -87,7 +87,7 @@ XMLDOCS+= report-2019-04-2019-06
XMLDOCS+= report-2019-07-2019-09
XMLDOCS+= report-2019-10-2019-12
XMLDOCS+= report-2020-01-2020-03
-
+XMLDOCS+= report-2020-04-2020-06
XSLT.DEFAULT= report.xsl
# Install a sample <project> entry.
Added: head/en_US.ISO8859-1/htdocs/news/status/report-2020-04-2020-06.xml
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2020-04-2020-06.xml Wed Jul 15 17:30:58 2020 (r54351)
@@ -0,0 +1,2878 @@
+<?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:
+ 04 - report month start
+ 06 - 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>04-06</month>
+
+ <year>2020</year>
+ </date>
+
+ <section>
+ <title>Introduction</title>
+<p>This report will be covering FreeBSD related projects between April and June,
+and covers a diverse set of topics ranging from kernel updates over userland
+and ports, as well to third-party work.
+</p>
+<p>Some hilights picked with the roll of a d100 include, but are not limited to,
+the ability to forcibly unmounting UFS when the underlying media becomes
+inaccessible, added preliminary support for Bluetooth Low Energy, a introduction to the
+FreeBSD Office Hours, and a repository of software collections called potluck
+to be installed with the pot utility, as well as many many more things.
+</p>
+<p>As a little treat, readers can also get a rare report from the quarterly team.
+</p>
+<p>Finally, on behalf of the quarterly team, I would like to extend my deepest
+appreciation and thank you to salvadore@, who decided to take down his shingle.
+His contributions not just the quarterly reports themselves, but also the
+surrounding tooling to many-fold ease the work, are immeassurable.
+</p>
+<p>We hope you find the report as interesting as we have,<br />
+Daniel Ebdrup Jensen (debdrup@), on behalf of the quarterly team.
+</p></section>
+<project cat='team'>
+<title>FreeBSD Foundation</title>
+
+<contact>
+<person>
+<name>Deb Goodkin</name>
+<email>deb at 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 Q2 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>
+<h3>Fundraising Efforts</h3>
+
+<p>Last quarter we raised $268,400! Thank you to the individuals and organizations
+that stepped in to help fund our efforts. We’d like to thank Netflix, employees
+of Nginx, Beckhoff Automation, and Mozilla Foundation for their large
+contributions last quarter, which helped bring our 2020 fundraising effort to
+$339k. 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 second quarter. These include:
+</p><ul>
+<li><p>WiFi 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>if_bridge performance improvements
+</p>
+</li></ul>
+<p>You can find more details about most of these projects in other quarterly
+reports.
+</p>
+<p>Staff members also worked on a number of larger projects, including:
+</p><ul>
+<li><p>Run-Time Dynamic Linker (rtld) improvements
+</p></li>
+<li><p>Improved FreeBSD support on Microsoft HyperV and Azure
+</p></li>
+<li><p>Fine-grained locking for amd64 pmap
+</p></li>
+<li><p>5-level paging structures for amd64
+</p></li>
+<li><p>Non-transparent superpages
+</p></li>
+<li><p>Migration to a Git repository
+</p></li>
+<li><p>Tool chain modernization
+</p>
+</li></ul>
+<p>Many of these projects also have detailed entries in other quarterly report
+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>Foundation co-op students Colin, Tiger, and Yang completed their winter 2020
+work term during the second quarter, and continued on with the next school term
+in their respective programs. Although COVID-19 presented a unique challenge
+and prompted an abrupt transition to remote work just over half way through the
+term, all three learned a lot and provided positive contributions to the FreeBSD
+Project and to the Foundation.
+</p>
+<p>A few projects that were in progress or completed during the work term were
+committed to the FreeBSD tree in the second quarter.
+</p>
+<h3>Continuous Integration and Quality Assurance</h3>
+
+<p>The Foundation provides a full-time staff member who is working on improving
+continuous integration, automated testing, and overall quality assurance
+efforts for the FreeBSD project.
+</p>
+<p>During the second quarter of 2020, Foundation staff continued improving the
+Project's CI infrastructure, monitoring regressions and working with
+contributors to fix the failing build and test cases. The setting up of VM host
+for CI jobs and staging environment is in progress. We are also working with
+other teams in the Project for their testing needs. For example, we added jobs
+for running full tests on non-x86 architectures. We are also working with many
+external projects and companies to improve their support of 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 FreeBSD infrastructure.
+Last quarter, we continued supporting FreeBSD hardware located around the world.
+We started working on getting the new NYI Chicago colocation facility prepared
+for some of the new FreeBSD hardware we are planning on purchasing.
+NYI generously provides this for free to the Project.
+</p>
+<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>Silver sponsor of BSDCan 2020. The event was held virtually, June 2-6, 2020
+</p></li>
+<li><p>Community Sponsor of Rootconf 2020. The event was held virtually, June 19-20, 2020
+</p></li>
+<li><p>Annual FreeBSD Day, June 19. This year’s celebration was postponed in
+ support of Juneteeth. However the activities surrounding FreeBSD Day have
+ been transformed into an ongoing series of online sessions. See
+ <i>FreeBSD Fridays</i> below for more information.
+</p></li>
+<li><p>Presented
+ <a href='https://www.youtube.com/watch?v=Wi5yMvavhQM'>27 Years of FreeBSD and Why You Should Get Involved</a>
+ as part of a Linux Professional Institute series of webinars on June 24, 2020.
+</p></li>
+<li><p>Attended and presented at the virtual Open Source Summit 2020.
+</p></li>
+<li><p>Announced <i>FreeBSD Fridays</i>: A series of 101 classes designed to get you
+ started with FreeBSD. Find out more in the
+ <a href='https://www.freebsdfoundation.org/blog/announcing-freebsd-fridays-a-series-of-101-classes/'>announcement</a>
+</p></li>
+<li><p>Participated as an Admin for Google Summer of Code 2020
+</p></li>
+<li><p>Participated in the new FreeBSD Office Hours series including holding our own
+ Foundation led office hours. Videos from the one hour sessions can be found
+ on the <a href='https://www.youtube.com/channel/UCxLxR_oW-NAmChIcSkAyZGQ'>Project’s YouTube Channel</a>.
+ You can watch ours <a href='https://www.youtube.com/watch?v=Ji4ux4FWpRU'>here</a>.
+</p>
+</li></ul>
+<p>In addition to the information found in the Development Projects update section
+of this report, take a minute to check out the latest update blogs:
+</p>
+<ul>
+<li><p><a href='https://www.freebsdfoundation.org/blog/500-if_bridge-performance-improvement/'>5x if_bridge Performance Improvement</a>
+</p></li>
+<li><p><a href='https://www.freebsdfoundation.org/blog/my-experience-as-a-freebsd-foundation-co-op-student/'>My Experience as a FreeBSD Foundation Co-Op Student</a>
+</p>
+</li></ul>
+<p>Keep up to date with our latest work in our <a href='https://www.freebsdfoundation.org/news-and-events/newsletter/'>Bi-Monthly newsletters</a>.
+</p>
+<p>Mellanox provided an update on how and why they use FreeBSD in our latest
+<a href='https://www.freebsdfoundation.org/freebsd-case-study-mellanox/'>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
+<a href='https://www.FreeBSDfoundation.org/journal/'>access the latest issues</a> on the
+Journal site.
+</p>
+<p>You can find out more about
+<a href='https://www.FreeBSDfoundation.org/news-and-events/'>events we attended and upcoming events</a>.
+</p>
+<p>We have continued our work with a new website developer to help us improve our
+website. Work is nearly complete to make it easier for community members to
+find information more easily and to make the site more efficient. We look
+forward to unveiling the refreshed site in Q3.
+</p>
+<h3>Foundation Board Meeting</h3>
+
+<p>Our annual board meeting was held on Tuesday June 2, 2020. We normally hold
+this meeting the Tuesday before BSDCan, in Ottawa, Ontario, Canada, but with the
+company travel ban, and the conference going virtual, our meeting went virtual
+for the first time. The purpose of the annual board meeting is to hold our
+board director and officer elections, review work accomplished over the past
+year, and put together strategic goals for the upcoming 12 months.
+</p>
+<p>The board generally has two all-day board meetings each year, this one, and a
+more informal one in January, typically held in Berkeley. Both meetings allow
+us to connect, reevaluate and discuss new ideas, while assessing what we should
+do to help the Project.
+</p>
+<p>Some of our longer-term goals include Growing User and Developer Communities,
+Developing Training and OS Course Content, Improving desktop/laptop experience,
+Promoting FreeBSD (as you can see in all the advocacy work listed above), and
+Improving Testing Capabilities.
+</p>
+<p>Results of the director and officer elections were:
+</p><ul>
+<li><p>Justin Gibbs (President)
+</p></li>
+<li><p>Benedict Reuschling (Vice President)
+</p></li>
+<li><p>Kirk McKusick (Treasurer)
+</p></li>
+<li><p>Philip Paeps (Secretary)
+</p></li>
+<li><p>Deb Goodkin (Assistant Secretary)
+</p></li>
+<li><p>Robert Watson (Director)
+</p></li>
+<li><p>Hiroki Sato (Director)
+</p></li>
+<li><p>George Neville-Neil (Director)
+</p>
+</li></ul>
+<p>Find out more about the
+<a href='https://www.freebsdfoundation.org/about/board-of-directors/'>FreeBSD Foundation Board of Directors</a>
+on our website.
+</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 <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></body></project>
+<project cat='team'>
+<title>FreeBSD Core Team</title>
+
+<contact>
+<person>
+<name>FreeBSD Core Team</name>
+<email>core at FreeBSD.org</email>
+</person>
+</contact>
+
+<body><p>The FreeBSD Core Team is the governing body of FreeBSD.
+</p>
+<p>The Core Team held 10 meetings during the second quarter of 2020, including a
+2020-05-21 joint meeting with members of the FreeBSD Foundation. Here are some
+highlights from that meeting:
+</p>
+<ul>
+<li><p>Deb requested guidance on how the Foundation can support the community.
+ Core and Foundation members believe that more developer support is necessary
+ to fill gaps in areas where commercial customers do not provide backing.
+ The clearest example of such a gap is the desktop experience, including
+ graphics and wireless support. What makes this request different from past
+ requests is that rather than support for one-time projects, ongoing
+ positions are necessary for a consistently high-quality desktop experience.
+</p>
+<p> "FreeBSD not being able to run on your laptop is the first step to
+ irrelevance." Ed Maste
+</p>
+</li>
+<li><p>Both teams discussed topics for upcoming sessions of FreeBSD Office Hours,
+ informal FreeBSD video conferences that anyone can attend. Everyone agreed
+ that the Office Hours have been a useful way for different parts of the
+ Project to engage with each other and with the wider community. Kudos to
+ Allan Jude for initiating the Office Hours and for everyone who has helped
+ make them a success by hosting or attending sessions.
+</p>
+</li>
+<li><p>Both teams agreed that they should meet once per quarter.
+</p>
+</li></ul>
+<p>The second annual community survey closed on 2020-06-16. The purpose of the
+survey is to collect data from the public to help guide the Project's efforts
+and priorities. As an example, last year's survey results helped initiate the
+Project's conversion to Git. Thank you to all who took the time to respond. The
+results will be released soon.
+</p>
+<p>The Core-initiated Git Working Group continued to make progress, but there are
+still some remaining issues to be worked out with the translation from
+Subversion. Hopefully the new Git src repository will be ready for use this
+summer. A <a href='https://cgit-beta.freebsd.org/'>beta version</a> has been published for
+people to test and a preliminary version of a <code>Using Git for FreeBSD
+Development</code> primer will soon be ready to share. Core, the Git Working Group,
+and Release Engineering are working towards the goal of releasing 12.2 from the
+new Git repository.
+</p>
+<p>Following the results of a Core-initiated developer survey, The FreeBSD Project
+has adopted a new LLVM-derived [code of
+conduct](https://www.freebsd.org/internal/code-of-conduct.html).
+</p>
+<p>The eleventh FreeBSD Core Team was elected by active developers. From a pool of
+23, the 9 successful candidates for core.11 are:
+</p>
+<ul>
+<li><p>Sean Chittenden (seanc, incumbent)
+</p></li>
+<li><p>Baptiste Daroussin (bapt)
+</p></li>
+<li><p>Kyle Evans (kevans)
+</p></li>
+<li><p>Mark Johnston (markj)
+</p></li>
+<li><p>Scott Long (scottl)
+</p></li>
+<li><p>Warner Losh (imp, incumbent)
+</p></li>
+<li><p>Ed Maste (emaste)
+</p></li>
+<li><p>George V. Neville-Neil (gnn)
+</p></li>
+<li><p>Hiroki Sato (hrs, incumbent)
+</p>
+</li></ul>
+<p>A new Core Team secretary, Muhammad Moinur Rahman (bofh), was unanimously
+approved by core.11. The outgoing core team met three times with the new core
+team to help with the transition. Core.10 wishes core.11 a successful term.
+</p></body></project>
+<project cat='team'>
+<title>FreeBSD Release Engineering Team</title>
+
+<contact>
+<person>
+<name>FreeBSD Release Engineering Team</name>
+<email>re at FreeBSD.org</email>
+</person>
+</contact>
+
+<links>
+<url href='https://www.freebsd.org/releases/11.4R/announce.html'>FreeBSD 11.4-RELEASE announcement</url>
+<url href='https://www.freebsd.org/releases/11.4R/schedule.html'>FreeBSD 11.4-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 slushes, and maintaining the respective
+branches, among other things.
+</p>
+<p>During the second quarter of 2020, the Release Engineering Team started
+work on the 11.4-RELEASE cycle, the fifth release from the stable/11
+branch. The release cycle went quite smoothly, with both BETA3 and RC3
+removed from the schedule. This allowed the final release to occur one
+week earlier than originally scheduled, which was announced June 16.
+FreeBSD 11.4-RELEASE is expected to be the final 11.x release.
+</p>
+<p>The FreeBSD Release Engineering Team would like to thank everyone involved
+in this cycle for their hard work.
+</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>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 at 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>Upgrade all x86 ref- and universe-machines
+</p></li>
+<li><p>Setup Amsterdam (PKT) mirror
+</p></li>
+<li><p>Solve hardware issue for bugzilla and svnweb backend
+</p></li>
+<li><p>Setup public <a href='https://cgit-beta.freebsd.org'>beta git server</a>
+</p></li>
+<li><p>Decommission CyberOne Data (CYB) mirror
+</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>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
+</p></li>
+<li><p>Check new hardware requirement from other teams
+</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 at FreeBSD.org</email>
+</person>
+<person>
+<name>Li-Wen Hsu</name>
+<email>lwhsu at 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
+for 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 the build jobs 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 second quarter of 2020, we continue working with the contributors and developers in the project for their testing needs and also keep working with external projects and companies to improve their support of FreeBSD.
+</p>
+<p>Important changes:
+</p><ul>
+<li><p>All -test jobs will run tests under <code>/usr/tests</code>, previously only x86 architectures doing this. See the Continuous Integration on !x86 section in this report for more information.
+</p></li>
+<li><p>Compression algorithm of disk images on the <a href='https://artifacts.ci.freebsd.org'>artifact server</a> has been changed to zstd to speed up compression and decompression.
+</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>
+New jobs added:
+<ul>
+<li><p>https://ci.freebsd.org/job/FreeBSD-head-armv7-test/
+</p></li>
+<li><p>https://ci.freebsd.org/job/FreeBSD-head-aarch64-test/
+</p></li>
+<li><p>https://ci.freebsd.org/job/FreeBSD-head-mips64-test/
+</p></li>
+<li><p>https://ci.freebsd.org/job/FreeBSD-head-powerpc64-test/
+</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>Setting up a builder dedicated to run jobs using provisioned VMs.
+</p></li>
+<li><p>Setting up the CI stage environment and putting the experimental jobs on it
+</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 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 hesistate 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 at FreeBSD.org</email>
+</person>
+<person>
+<name>FreeBSD Ports Management Team</name>
+<email>portmgr at 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>There are currently 2,373 open ports PRs of which 526 are
+unassigned, for a total of 39,628 ports. In the last quarter
+there were 10,315 commits to HEAD and 476 to the quarterly
+branch by respectively 178 and 65 committers. Compared to the
+quarter before, this means a significant increase in commits and
+also a slight decrease in open PRs.
+</p>
+<p>During the last quarter, we welcomed Hiroki Tagato (tagattie@).
+We said goodbye to seanc@, zleslie@, gnn@ and salvadore at .
+</p>
+<p>A few default versions got bumped:
+</p><ul>
+<li><p>Java (new) at 8
+</p></li>
+<li><p>Lazarus to 2.0.8
+</p>
+</li></ul>
+It is now possible to write pkg scripts in Lua instead of sh.
+<p>They have two advantages over their sh versions:
+</p><ul>
+<li><p>they run in a Capsicum sandbox
+</p></li>
+<li><p>they respect rootdir, the directory which pkg will use as
+ the starting point to install all packages under.
+</p>
+</li></ul>
+Some user-facing packages were also updated:
+<ul>
+<li><p>pkg to 1.14.6
+</p></li>
+<li><p>Firefox to 78.0.1
+</p></li>
+<li><p>Thunderbird to 68.10.0
+</p></li>
+<li><p>Chromium to 83.0.4103.116
+</p></li>
+<li><p>Ruby to 2.5.8, 2.6.6, and 2.7.1
+</p></li>
+<li><p>Qt5 to 5.14.2
+</p>
+</li></ul>
+<p>During the last quarter, antoine@ ran 55 exp-runs to test port
+version updates, make liblzma use libmd, flavor devel/scons and
+Lua ports, add and update library functions in the base system,
+make malloc.h usable again, remove as(1) from the base system, and
+augment sed(1) with -f.
+</p></body></project>
+<project cat='team'>
+<title>FreeBSD Office Hours</title>
+
+<links>
+<url href='https://wiki.freebsd.org/OfficeHours'>Office Hours on the FreeBSD Wiki</url>
+<url href='https://forms.gle/3HjjRx9KMcM3SL4H7'>Poll: What time would you prefer Office Hours be at</url>
+<url href='https://live.freebsd.org/'>live.FreeBSD.org: Aggregation of Live streams</url>
+</links>
+
+<contact>
+<person>
+<name>Allan Jude</name>
+<email>allanjude at freebsd.org</email>
+</person>
+</contact>
+
+<body><p>Starting on the first of April 2020, the FreeBSD project has started
+hosting regular video streams to foster greater communication within
+the wider FreeBSD community. The first of these sessions took the form
+of a public question and answer session, which drew over 60 participants.
+A second session was held two weeks later at a time more appropriate for
+those in Asia, but only drew 20 participants. With the help of the FreeBSD
+Foundation, we ran a poll to discover what times worked best for the
+greatest number of people.
+</p>
+<p>On May 13th the FreeBSD Foundation hosted a session where the community
+could ask questions of or about the foundation. On May 27th many of the
+candidates for the new FreeBSD Core Team joined an office hours session to
+answer questions from the community. Finally on June 24th another general
+question and answer office hours was held.
+</p>
+<p>Each office hours session consists of a video meeting of some FreeBSD
+developers or other subject matter experts, live streamed along with an IRC
+chat room for viewers to pose questions to the panel. The stream is recorded
+and posted to the official FreeBSD youtube channel.
+</p>
+<p>If you would like to host an office hours session, please contact:
+</p><ul>
+<li><p><a href='mailto:allanjude at freebsd.org'>Allan Jude</a>
+</p></li>
+<li><p><a href='mailto:anne at freebsdfoundation.org'>Anne Dickison</a>
+</p>
+</li></ul>
+<p>Sponsor: ScaleEngine Inc. (video streaming)
+</p></body></project>
+<project cat='team'>
+<title>Quarterly Status Reports Team</title>
+
+<contact>
+<person>
+<name>Quarterly Status Reports</name>
+<email>quarterly at FreBSD.org</email>
+</person>
+<person>
+<name>Daniel Ebdrup Jensen</name>
+<email>debdrup at FreeBSD.org</email>
+</person>
+</contact>
+
+<links>
+<url href='https://www.freebsd.org/news/status/'>Quarterly status reports</url>
+<url href='https://github.com/freebsd/freebsd-quarterly'>Git repository</url>
+</links>
+
+<body><p>The Quarterly Status Reports Team collects and publish the reports that you are
+reading right now.
+</p>
+<p>Many improvements have been done recently and thus we believe it is useful that
+the Quarterly Status Reports Team submits a report. Not all the changes below
+are specific to the last quarter, but we list them here anyway since we did not
+write an entry for earlier reports.
+</p>
+<ul>
+<li><p>Reports are now built using Makefiles. Among the many advantages, this allows
+ us to easily sort reports logically. Indeed, starting with 2019Q4, all reports
+ are sorted logically, while before they were sorted alphabetically within each
+ category.
+</p>
+</li>
+<li><p>The conversion from markdown to docbook was performed using a python script,
+ with some known bugs. Salvadore has rewritten the script using perl fixing
+ most of the bugs. Some features are missing and many improvements are
+ possible, but the script is very unlikely to receive any change since it will
+ become obsolete as soon as the conversion to Hugo/AsciiDoctor is completed.
+</p>
+</li>
+<li><p>Another perl script to ease the preparation of the mail version of the
+ reports was written.
+</p>
+</li>
+<li><p>One more perl script has been written to allow the quarterly team to send
+ quarterly calls automatically using a cron job. We used it this quarter for
+ the first time.
+</p>
+</li>
+<li><p>As you might have noticed, last quarterly calls have been sent to
+ freebsd-quarterly-calls@: this is a new mailing list to which you can
+ <a href='https://lists.freebsd.org/mailman/listinfo/freebsd-quarterly-calls'>subscribe</a>
+ to receive calls for quarterly reports. Please note this is a moderated list,
+ with very low traffic and a high signal to noise ratio.
+</p>
+</li>
+<li><p>If you read carefully the last quarterly calls, you should have noticed that
+ we now ask you to send reports to quarterly-submissions@ instead of
+ quarterly at . This was done to help the quarterly team distinguishing internal
+ discussions from submissions. Please keep in mind however that the quarterly
+ team prefers receiving pull requests, as they ease the administrative work.
+</p>
+</li></ul>
+<p>We would like to thank philip@, from the postmaster team, for having created the
+freebsd-quarterly-calls@ mailing list and the quarterly-submissions@ address for
+us.
+</p></body></project>
+<project cat='proj'>
+<title>FreeBSD on Microsoft HyperV and Azure</title>
+
+<links>
+<url href='https://wiki.freebsd.org/MicrosoftAzure'>FreeBSD on MicrosoftAzure wiki</url>
+<url href='https://wiki.freebsd.org/HyperV'>FreeBSD on Microsoft HyperV</url>
+</links>
+
+<contact>
+<person>
+<name>FreeBSD Integration Services Team</name>
+<email>bsdic at microsoft.com</email>
+</person>
+<person>
+<name>Wei Hu</name>
+<email>whu at FreeBSD.org</email>
+</person>
+<person>
+<name>Li-Wen Hsu</name>
+<email>lwhsu at FreeBSD.org</email>
+</person>
+</contact>
+
+<body><p>HyperV socket for FreeBSD implemented by Wei was checked into FreeBSD head
+branch on May 20th as
+<a href='https://svnweb.freebsd.org/changeset/base/r361275'>r361275</a>. It supports
+guest/host communications without the need for networking. Some HyperV
+and Azure features rely on this to be available in guests.
+</p>
+<p>Details of HyperV Socket is available <a href='https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/make-integration-service'>here</a>.
+</p>
+<p>This project is sponsored by Microsoft.
+</p>
+<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-12_1'>12.1-RELEASE image on Azure Marketplace</a> is published.
+The work on the 11.4-RELEASE image on Azure Marketplace is in progress.
+</p>
+<p>This project is sponsored by The FreeBSD Foundation.
+</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 at FreeBSD.org</email>
+</person>
+<person>
+<name>Warner Losh</name>
+<email>imp at FreeBSD.org</email>
+</person>
+<person>
+<name>Ulrich Spörlein</name>
+<email>uqs at FreeBSD.org</email>
+</person>
+</contact>
+
+<body><p>Work continues on FreeBSD's migration from Subversion to Git. Ulrich has
+iterated on updates to svn2git in order to improve the fidelity of the
+conversion, particularly in regards to vendor (contrib) code updates.
+We believe the conversion is now at an acceptable state, but may make minor
+adjustments if additional issues are found. We expect to push modifications
+to the converter every two weeks (first and third Sunday of the month). This
+means that commit hashes in the beta repo will remain stable for at least two
+weeks at a time, to allow others to test and experiment with the beta repo.
+</p>
+<p>We are now working on updating FreeBSD processes and documentation.
+This includes:
+</p><ul>
+<li><p>Writing a Git Primer, akin to the existing Subversion primer
+</p></li>
+<li><p>Updates to the Security Team's tools and processes
+</p></li>
+<li><p>Release engineering updates
+</p></li>
+<li><p>Ports and packages process updates
+</p>
+</li></ul>
+<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 expect to be ready for the migration in the next quarter.
+</p>
+<p>Sponsor: The FreeBSD Foundation (in part)
+</p></body></project>
+<project cat='proj'>
+<title>Lua Usage in FreeBSD</title>
+
+<contact>
+<person>
+<name>Ed Maste</name>
+<email>emaste at FreeBSD.org</email>
+</person>
+<person>
+<name>Kyle Evans</name>
+<email>kevans at FreeBSD.org</email>
+</person>
+<person>
+<name>Ryan Moeller</name>
+<email>freqlabs at FreeBSD.org</email>
+</person>
+</contact>
+
+<body><p>Lua is a small, efficient scripting language that FreeBSD imported before
+FreeBSD 12.0 for use in the bootloader. Since then, several projects
+outside of the bootloader have gained some amount of traction with Lua usage:
+</p>
+<ul>
+<li><p>/usr/libexec/flua is now installed for internal usage
+</p></li>
+<li><p>makesyscalls.sh was rewritten in Lua
+</p></li>
+<li><p>pkg has gained support for lua scripts
+</p></li>
+<li><p>lldb in the base system now supports lua scripting
+</p>
+</li></ul>
+<p>FreeBSD Lua ("flua") is a version of the lua interpreter that has several
+modules built-in for convenient usage within the base system. flua is
+installed with a non-standard name and in a location not included in $PATH
+so that it is not accidentally found by third-party software or configure
+scripts. The FreeBSD project makes no guarantees about upgrade cadence or
+module stability. That said, it is available for use by downstream projects
+and FreeBSD users aware of those limitations.
+</p>
+<p>Previous work with flua includes, for example, adding libucl support and
+future work includes libifconfig support for scripting usage.
+</p>
+<p>People interested in working with Lua in FreeBSD are welcome to get in
+contact to discuss other project ideas. To name a couple of potential
+projects, some interesting modules that have not been started but could
+prove useful (listed in no particular order):
+</p>
+<ul>
+<li><p>libcrypt
+</p></li>
+<li><p>libexpat
+</p></li>
+<li><p>libjail
+</p></li>
+<li><p>libnv
+</p></li>
+<li><p>libxo
+</p></li></ul>
+</body></project>
+<project cat='proj'>
+<title>Linux compatibility layer update</title>
+
+<contact>
+<person>
+<name>Edward Tomasz Napierala</name>
+<email>trasz at 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 is 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>Example problems fixed include buggy madvise(2) handling, which could
+break applications linked against jemalloc; uname(2) returning wrong
+results for 32 bit apps, which caused problems for Steam; recvmsg(2)
+and accept(2) being broken in some circumstances, which was breaking
+Redis; and missing support for <code>SO_REUSEPORT</code>, <code>SO_SNDBUFFORCE</code>,
+<code>SO_RCVBUFFORCE</code>, and <code>SO_PROTOCOL</code>, which spammed the log files when
+running the Python regression test suite. The default soft open files
+limit is now automatically adjusted to 1024, as several Linux apps
+iterate over all the file descriptors up to that limit instead of using
+closefrom(2).
+</p>
+<p>There's ongoing work on cleanups and the debugging framework for Linux
+compatibility, such as logging warnings for unrecognized system call
+parameters, or adding the <code>compat.linux.debug</code> sysctl to turn the warnings
+off.
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
More information about the svn-doc-all
mailing list