Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 25 Nov 2019 19:20:33 +0000 (UTC)
From:      Edward Tomasz Napierala <trasz@FreeBSD.org>
To:        doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org
Subject:   svn commit: r53636 - head/en_US.ISO8859-1/htdocs/news/status
Message-ID:  <201911251920.xAPJKXSl064588@repo.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: trasz
Date: Mon Nov 25 19:20:33 2019
New Revision: 53636
URL: https://svnweb.freebsd.org/changeset/doc/53636

Log:
  Add Quarterly Status Report for 2019Q3.
  
  Reviewed by:	allanjude
  Differential Revision:	https://reviews.freebsd.org/D22323

Added:
  head/en_US.ISO8859-1/htdocs/news/status/report-2019-07-2019-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	Sun Nov 24 21:16:43 2019	(r53635)
+++ head/en_US.ISO8859-1/htdocs/news/status/Makefile	Mon Nov 25 19:20:33 2019	(r53636)
@@ -84,6 +84,7 @@ XMLDOCS+=	report-2018-01-2018-09
 XMLDOCS+=	report-2018-09-2018-12
 XMLDOCS+=	report-2019-01-2019-03
 XMLDOCS+=	report-2019-04-2019-06
+XMLDOCS+=	report-2019-07-2019-09
 
 XSLT.DEFAULT=	report.xsl
 

Added: head/en_US.ISO8859-1/htdocs/news/status/report-2019-07-2019-09.xml
==============================================================================
--- /dev/null	00:00:00 1970	(empty, because file is newly added)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2019-07-2019-09.xml	Mon Nov 25 19:20:33 2019	(r53636)
@@ -0,0 +1,3108 @@
+<?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$ -->
+<!-- This file was generated with https://github.com/trasz/md2docbook -->
+<!--
+     Variables to replace:
+     %%START%%     - report month start
+     %%STOP%%      - report month end
+     %%YEAR%%      - 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 %%YEAR%%)
+     %%DUENEXT%%   - next report due date (i.e., June 6)
+-->
+
+<report>
+  <date>
+    <month>07-09</month>
+
+    <year>2019</year>
+  </date>
+
+  <section>
+    <title>Introduction</title>
+<p>Here is the third quarterly status report for 2019.</p>
+
+<p>This quarter the reports team has been more active than usual thanks
+to a better organization: calls for reports and reminders have been
+sent regularly, reports have been reviewed and merged quickly (I would
+like to thank debdrup@ in particular for his reviewing work).</p>
+<p>Efficiency could still be improved with the help of our community.
+In particular, the quarterly team has found that many reports have
+arrived in the last days before the deadline or even after. I would
+like to invite the community to follow the guidelines below that
+can help us sending out the reports sooner.</p>
+<ul>
+<li>Send a first draft of your report when you receive the first call
+for reports (1 month before the deadline).</li>
+<li>Update your report, if needed, when you receive reminders: you will
+normaly receive two (2 weeks and 1 week before the deadline).</li>
+<li>If after the deadline you still have some more updates ask the team
+(either on IRC via #freebsd-wiki or send an email at monthly@) to
+wait for you if you feel that they are urgent, otherwise start
+putting them in a draft for the next quarter.</li></ul>
+
+<p>Starting from next quarter, all quarterly status reports will be
+prepared the last month of the quarter itself, instead of the first
+month after the quarter's end. This means that deadlines for
+submitting reports will be the 1st of January, April, July and
+October.</p>
+<p>Next quarter will then be a short one, covering the months of November
+and December only and the report will probably be out in mid January.</p>
+
+<p>-- Lorenzo Salvadore</p>
+  </section>
+
+  <category>
+    <name>team</name>
+
+    <description>&os; Team Reports</description>
+
+    <p>Entries from the various official and semi-official teams,
+      as found in the <a href="&enbase;/administration.html">Administration
+        Page</a>.</p>
+  </category>
+
+  <category>
+    <name>proj</name>
+
+    <description>Projects</description>
+
+    <p>Projects that span multiple categories, from the kernel and userspace
+      to the Ports Collection or external projects.</p>
+  </category>
+
+  <category>
+    <name>kern</name>
+
+    <description>Kernel</description>
+
+    <p>Updates to kernel subsystems/features, driver support,
+      filesystems, and more.</p>
+  </category>
+
+  <category>
+    <name>arch</name>
+
+    <description>Architectures</description>
+
+    <p>Updating platform-specific features and bringing in support
+      for new hardware platforms.</p>.
+  </category>
+
+  <category>
+    <name>bin</name>
+
+    <description>Userland Programs</description>
+
+    <p>Changes affecting the base system and programs in it.</p>
+  </category>
+
+  <category>
+    <name>ports</name>
+
+    <description>Ports</description>
+
+    <p>Changes affecting the Ports Collection, whether sweeping
+      changes that touch most of the tree, or individual ports
+      themselves.</p>
+  </category>
+
+  <category>
+    <name>third</name>
+
+    <description>Third-Party Projects</description>
+
+    <p>Many projects build upon &os; or incorporate components of
+      &os; into their project.  As these projects may be of interest
+      to the broader &os; community, we sometimes include brief
+      updates submitted by these projects in our quarterly report.
+      The &os; project makes no representation as to the accuracy or
+      veracity of any claims in these submissions.</p>
+  </category>
+
+  <project cat='team'>
+    <title>FreeBSD Core Team</title>
+
+    <contact>
+      <person>
+	<name>FreeBSD Core Team</name>
+	<email>core@FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <body>
+      <p>The FreeBSD Core Team is the governing body of FreeBSD.</p>
+
+      <ul>
+	<li>Core has provisionally accepted the BSD+patent license for
+	use in some cases.
+	The Core Team must approve the import of new BSD+Patent
+	licensed components or
+	the change of license of existing components to the
+	BSD+Patent License.
+      <br/>
+	https://opensource.org/licenses/BSDplusPatent</li>;
+
+	<li>Kernel Pseudo Random Number Generator (PRNG)
+	maintainership was updated to
+	reduce the contribution barrier for committers who have
+	demonstrated
+	competence in this part of the tree.</li>
+	<li>Core approved a source commit bit for Paweł Biernacki.
+	Konstantin Belousov
+	&lt;kib@&gt; will mentor Paweł and Mateusz Guzik
+	&lt;mjg@&gt; will be co-mentor.</li>
+	<li>The Core-initiated Git Transition Working Group met over
+	the last quarter,
+	however a report is still forthcoming. Discussions will
+	continue in the
+	fourth quarter of 2019. There are many issues to resolve
+	including how to
+	deal with contrib/, whether to re-generate hashes in the
+	current Git
+	repository, and how to best implement commit testing.</li>
+      </ul>
+
+    </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/11.3R/announce.html">FreeBSD 11.3-RELEASE announcement</url>
+      <url href="https://www.freebsd.org/releases/12.1R/schedule.html">FreeBSD 12.1-RELEASE schedule</url>
+      <url href="https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.1/">FreeBSD 12.1-RELEASE BETA/RC 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 2019, the FreeBSD Release
+	Engineering team
+	finished the 11.3-RELEASE cycle, with the final release
+	build started on
+	July 5th and the official announcement sent on July 9th.</p>
+
+      <p>FreeBSD 11.3-RELEASE is the fourth release from the
+	<i>stable/11</i> branch,
+	building on the stability and reliability of 11.2-RELEASE.</p>
+
+      <p>The FreeBSD Release Engineering Team also started work on
+	the upcoming
+	12.1-RELEASE, which started September 6th. This release
+	cycle is the
+	first "freeze-less" release from the Subversion
+	repository, and the test bed
+	for eliminating the requirement of a hard code freeze on
+	development branches.
+	Commits to the <i>releng/12.1</i> branch still
+	require explicit approval from
+	the Release Engineering Team, however.</p>
+
+      <p>At present, there have been three BETA builds, and so far,
+	two RC builds, with
+	the final 12.1-RELEASE build scheduled for November 4th.</p>
+
+      <p>Additionally throughout the quarter, several development
+	snapshots builds
+	were released for the <i>head</i> and
+	<i>stable/11</i> branches; snapshots for
+	<i>stable/12</i> were released as well although
+	not during the 12.1-RELEASE cycle.</p>
+
+      <p>Much of this work was sponsored by Rubicon Communications,
+	LLC (Netgate)
+	and the FreeBSD Foundation.</p>
+
+    </body>
+
+  </project>
+
+  <project cat='team'>
+    <title>FreeBSD Security Team</title>
+
+    <contact>
+      <person>
+	<name>Security Team</name>
+	<email>secteam@FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="https://www.freebsd.org/security/">FreeBSD security information</url>
+    </links>
+
+    <body>
+      <p>Several members of the security team met at the Vendor
+	Summit in October to
+	formalize team structure dedicated for architecture and
+	crypto engineering in
+	addition to the existing product security incident
+	response function.</p>
+
+      <p>Since June we have started having fortnightly conference
+	calls to discuss
+	important issues and to collaborate closely on advisories
+	and errata notices in
+	the pipeline.</p>
+
+      <ul>
+	<li>Security advisories sent out in 2019-Q3: 7</li>
+
+	<li>Errata Notices sent out in 2019-Q3: 5</li>
+      </ul>
+
+    </body>
+
+  </project>
+
+  <project cat='team'>
+    <title>Cluster Administration Team</title>
+
+    <contact>
+      <person>
+	<name>Cluster Administration Team</name>
+	<email>clusteradm@FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <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>Change IPv6 address in TWN site.</li>
+
+	<li>Solved hardware issues in KWC site (with hrs@).</li>
+
+	<li>Moved remaining infrastructure from the YSV (Yahoo!) site
+	to NYI (New York Internet) (peter@).</li>
+
+	<ul><li>YSV hosted most of FreeBSD.org between 2000 and 2019.</li></ul>
+
+	<li>Installed new machines for portmgr@ courtesy of the
+	FreeBSD Foundation.</li>
+
+	<li>Resolved outtages (thanks uqs@) with GitHub exporter,
+	Bugzilla and hg-beta (thanks bapt@).</li>
+
+	<li>PowerPC64 servers are online (power8) building pkgs and
+	reference hosts.</li>
+
+	<li>Ongoing systems administration work:</li>
+
+	<ul><li>Creating accounts for new committers.</li>
+
+	<li>Backups of critical infrastructure.</li>
+
+	<li>Keeping up with security updates in 3rd party software.</li></ul>
+      </ul>
+
+      <p>
+	Work in progress:</p>
+
+      <ul>
+	<li>Review the service jails and service administrators
+	operation.</li>
+
+	<li>South Africa Mirror (JINX) in progress.</li>
+
+	<li>NVME issues on PowerPC64 Power9 blocking dual socket
+	machine from being used as pkg builder.</li>
+
+	<li>Drive upgrade test for pkg builders (SSDs) courtesy of the
+	FreeBSD Foundation.</li>
+
+	<li>Boot issues with Aarch64 reference machines.</li>
+
+	<li>New NYI.net sponsored colocation space in Chicago-land
+	area.</li>
+
+	<li>Setup new host for CI staging environment.</li>
+      </ul>
+
+    </body>
+
+  </project>
+
+  <project cat='team'>
+    <title>Continuous Integration</title>
+
+    <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>
+
+    <links>
+      <url href="https://ci.FreeBSD.org">FreeBSD Jenkins Instance</url>
+      <url href="https://artifact.ci.FreeBSD.org/">FreeBSD CI artifact archive</url>
+      <url href="https://wiki.freebsd.org/Jenkins">FreeBSD Jenkins wiki</url>
+      <url href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing">freebsd-testing Mailing List</url>
+      <url href="https://github.com/freebsd/freebsd-ci">FreeBSD CI Repository</url>
+      <url href="https://preview.tinyurl.com/y9maauwg">Tickets related to freebsd-testing@</url>
+      <url href="https://wiki.freebsd.org/HostedCI">Hosted CI wiki</url>
+      <url href="https://hackmd.io/@FreeBSD-CI">FreeBSD CI weekly report</url>
+    </links>
+
+    <body>
+      <p>The FreeBSD CI team maintains continuous integration
+	system and related tasks
+	for the FreeBSD project. The CI system regularly checks
+	the committed changes
+	can be successfully built, then performs various tests and
+	analysis of the
+	results. The results from build jobs are archived in an
+	artifact server, for
+	the further testing and debugging needs. The CI team
+	members examine the
+	failing builds and unstable tests, and work with the
+	experts in that area to
+	fix the code or adjust test infrastructure. The details
+	are of these efforts
+	are available in the weekly CI reports.</p>
+
+      <p>We had a testing working group at the <a
+	href="https://wiki.freebsd.org/DevSummit/201909">201909
+	DevSummit</a>
+	lwhsu@ has presented the Testing/CI project status and
+	"how to work with the FreeBSD CI system", slides
+	are available at the DevSummit page.
+	Some contents have been migrated to
+	https://wiki.freebsd.org/Jenkins/Debug , extending
+	is welcomed.</p>
+
+      <p>We continue publishing CI Weekly Report and moved the
+	archive to https://hackmd.io/@FreeBSD-CI</p>;
+
+      <p>Work in progress:</p>
+
+      <ul>
+	<li>Collecting and sorting CI tasks and ideas at
+	https://hackmd.io/bWCGgdDFTTK_FG0X7J1Vmg</li>;
+
+	<li>Setup the CI stage environment and put the experimental
+	jobs on it</li>
+
+	<li>Extending and publishing the embedded boards testbed</li>
+
+	<li>Implementing automatic tests on bare metal hardware</li>
+
+	<li>Adding drm ports building test against -CURRENT</li>
+
+	<li>Testing and merging pull requests at
+	https://github.com/freebsd/freebsd-ci/pulls</li>;
+
+	<li>Planning for running ztest and network stack tests</li>
+
+	<li>Help more 3rd software get CI on FreeBSD through a hosted
+	CI solution</li>
+      </ul>
+
+      <p>
+	Please see freebsd-testing@ related tickets for more WIP
+	information.</p>
+
+    </body>
+
+    <sponsor>
+      The FreeBSD Foundation
+    </sponsor>
+
+  </project>
+
+  <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 and quality
+	assurance 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>
+
+      <p>Partnerships and Commercial User Support
+	We help facilitate collaboration between commercial users
+	and FreeBSD
+	developers. We also meet with companies to discuss their
+	needs and bring
+	that information back to the Project. In Q3, Ed Maste and
+	Deb Goodkin met
+	with a few commercial users in the US. It is not only
+	beneficial for the
+	above, but it also helps us understand some of the
+	applications where
+	FreeBSD is used. We were also able to meet with a good
+	number of commercial
+	users at vBSDCon and EuroBSDCon. These venues provide an
+	excellent
+	opportunity to meet with commercial and individual users
+	and contributors
+	to FreeBSD.</p>
+
+      <p>Fundraising Efforts
+	Our work is 100% funded by your donations. We are
+	continuing to work hard
+	to get more commercial users to give back to help us
+	continue our work
+	supporting FreeBSD. More importantly, we'd like to thank
+	our individual
+	donors for making $10-$1,000 donations last quarter, for
+	more than $16,000!</p>
+
+      <p>Please consider
+	<a href="https://www.FreeBSDfoundation.org/donate/">making
+	a donation</a> to help us
+	continue and increase our support for FreeBSD!</p>
+
+      <p>We also have the Partnership Program, to provide more
+	benefits for our
+	larger commercial donors. Find out more information at
+	<a
+	href="https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/">www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/</a>;
+	and share with your companies.</p>
+
+      <p>OS Improvements
+	The Foundation supports software development projects to
+	improve the FreeBSD
+	operating system through our full time technical staff,
+	contractors, and
+	project grant recipients. They maintain and improve
+	critical kernel
+	subsystems, add new features and functionality, and fix
+	problems.</p>
+
+      <p>Over the last quarter there were 345 commits to the
+	FreeBSD base system
+	repository sponsored by the FreeBSD Foundation - this
+	represents about
+	one fifth of all commits during this period. Many of these
+	projects have
+	their own entries in this quarterly report (and are not
+	repeated here).</p>
+
+      <p>Foundation staff member Konstantin Belousov committed many
+	improvements to
+	multiple kernel subsystems, as well as low-level 32-bit
+	and 64-bit x86
+	infrastructure. These included fixes for robust mutexes,
+	unionfs, the
+	out of memory (OOM) handler, and per-cpu allocators.</p>
+
+      <p>Additional work included fixes for security issues and
+	introduction and
+	maintenance of vulnerability mitigations, and improving
+	POSIX conformance.</p>
+
+      <p>Ed Maste committed a number of minor security bug fixes
+	and improvements,
+	as well as the first iteration of a tool for editing the
+	mitigation control
+	ELF note. Additional work included effort on build
+	infrastructure and the
+	tool chain.</p>
+
+      <p>Clang's integrated assembler (IAS) is now used more
+	widely, as part of the
+	path to retiring the assembler from GNU binutils 2.17.50.
+	The readelf tool
+	now decodes some additional ELF note information.</p>
+
+      <p>Ed also enabled the Linuxulator (Linux binary support
+	layer) on arm64, and
+	added a trivial implementation of the renameat2 system
+	call (handling common
+	options).</p>
+
+      <p>Mark Johnston added Capsicum support to a number of ELF
+	Tool Chain utilities,
+	and committed a number of other Capsicum kernel and
+	userland fixes.</p>
+
+      <p>Mark worked on a number of changes related to security
+	improvements, including
+	integration and support of the Syzkaller automated system
+	call fuzzer, and
+	fixing issues identified by Syzkaller. Other changes
+	included addressing
+	failures caused by refcount wraparound, improvements to
+	the <tt>prot_max</tt> memory
+	protection. Other work included NUMA, locking, kernel
+	debugging, RISC-V and
+	arm64 kernel improvements.</p>
+
+      <p>Edward Napierala continued working on Linuxulator
+	improvements over the
+	quarter. The primary focus continued to be tool
+	improvements - strace is now
+	more usable for diagnosing issues with Linux binaries
+	running under the
+	Linuxulator. That said, as with previous work a number of
+	issues have been
+	fixed along the way. These are generally minor issues with
+	a large impact -
+	for example, every binary linked against up-to-date glibc
+	previously
+	segfaulted on startup. This is now fixed.</p>
+
+      <p>Continuous Integration and Quality Assurance
+	The Foundation provides a full-time staff member who is
+	working on improving
+	our automated testing, continuous integration, and overall
+	quality assurance
+	efforts.</p>
+
+      <p>During the third quarter of 2019, Foundation staff
+	continued to improve the
+	project's CI infrastructure, worked with contributors to
+	fix the failing build
+	and test cases, and worked with other teams in the Project
+	for their testing
+	needs. We added several new CI jobs and worked on getting
+	the hardware
+	regression testing lab ready.</p>
+
+      <p>Li-Wen Hsu gave presentations "Testing/CI status update"
+	and "How to work with
+	the FreeBSD CI system" at the
+	<a href="https://wiki.freebsd.org/DevSummit/201909">201909
+	DevSummit</a>.
+	Slides are available at the DevSummit page.</p>
+
+      <p>We continue publishing the CI weekly report on the
+	<a
+	href="https://lists.freebsd.org/mailman/listinfo/freebsd-testing">freebsd-testing@</a>.
+	mailing list, and an <a
+	href="https://hackmd.io/@freebsd-ci">archive</a>;
+	is available.</p>
+
+      <p>See the FreeBSD CI section of this report for completed
+	work items and
+	detailed information.</p>
+
+      <p>Supporting FreeBSD Infrastructure
+	The Foundation provides hardware and support to improve
+	the FreeBSD
+	infrastructure. Last quarter, we continued supporting
+	FreeBSD hardware
+	located around the world.</p>
+
+      <p>FreeBSD Advocacy and Education
+	A large part of our efforts are dedicated to advocating
+	for the Project.
+	This includes promoting work being done by others with
+	FreeBSD; producing
+	advocacy literature to teach people about FreeBSD and help
+	make the path to
+	starting using FreeBSD or contributing to the Project
+	easier; and attending
+	and getting other FreeBSD contributors to volunteer to run
+	FreeBSD events,
+	staff FreeBSD tables, and give FreeBSD presentations.</p>
+
+      <p>The FreeBSD Foundation sponsors many conferences, events,
+	and summits around
+	the globe. These events can be BSD-related, open source,
+	or technology events
+	geared towards underrepresented groups. We support the
+	FreeBSD-focused events
+	to help provide a venue for sharing knowledge, to work
+	together on projects,
+	and to facilitate collaboration between developers and
+	commercial users.
+	This all helps provide a healthy ecosystem. We support the
+	non-FreeBSD events
+	to promote and raise awareness of FreeBSD, to increase the
+	use of FreeBSD in
+	different applications, and to recruit more contributors
+	to the Project.</p>
+
+      <p>Check out some of the advocacy and education work we did
+	last quarter:</p>
+
+      <ul>
+	<li>Sponsored USENIX 2019 Annual Technical Conference as an
+	Industry Partner</li>
+
+	<li>Represented FreeBSD at OSCON 2019 in Portland, OR</li>
+
+	<li>Represented FreeBSD at COSCUP 2019 in Taiwan</li>
+
+	<li>Presented at the Open Source Summit, North American in San
+	Diego, CA</li>
+
+	<li>Executive Director Deb Goodkin was interviewed by TFiR
+	https://www.freebsdfoundation.org/news-and-events/latest-news/tfir-interview-freebsd-meets-linux-at-the-open-source-summit/</li>;
+
+	<li>Sponsored FreeBSD Hackathon at vBSDcon 2019 in Reston, VA</li>
+
+	<li>Sponsored the attendee bags and attended vBSDcon 2019 in
+	Reston VA</li>
+
+	<li>Represented FreeBSD at APNIC-48 in Chiang Mai, Thailand</li>
+
+	<li>Represented FreeBSD at MNNOG-1 in Ulaanbaatar, Mongolia</li>
+
+	<li>Served as an administrator for the Project’s Google Summer
+	of Code Session. See the Google Summer of Code
+	section of this report for more information.</li>
+
+	<li>Sponsored FreeBSD Developers Summit at EuroBSDCon in
+	Lillehammer, Norway</li>
+
+	<li>Sponsored and attended EuroBSDcon 2019 in Lillehammer,
+	Norway</li>
+
+	<li>Applied and was accepted for a FreeBSD Miniconf at
+	linux.conf.au, in Gold Coast, Australia, Jan 14,
+	2020</li>
+
+	<li>Our FreeBSD talk was accepted at seaGL, Seattle, WA,
+	November 15 and 16.</li>
+      </ul>
+
+      <p>
+	We continued producing FreeBSD advocacy material to help
+	people promote
+	FreeBSD. Learn more about our recent efforts to advocate
+	for FreeBSD
+	around the world:
+	https://www.freebsdfoundation.org/blog/freebsd-around-the-world/</p>;
+
+      <p>Our Faces of FreeBSD series is back. Check out the latest
+	post:
+	<a
+	href="https://www.freebsdfoundation.org/blog/faces-of-freebsd-2019-roller-angel/">Roller
+	Angel</a>.</p>
+
+      <p>Read more about our conference adventures in the
+	conference recaps and trip
+	reports in our monthly newsletters:
+	
+	https://www.freebsdfoundation.org/news-and-events/newsletter/</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
+	<a
+	href="https://www.FreeBSDfoundation.org/news-and-events/">events
+	we attended and upcoming events</a>.</p>
+
+      <p>We opened our official FreeBSD Swag Store. Get stickers,
+	shirts, mugs and
+	more at <a
+	href="https://www.zazzle.com/store/shopfreebsd">ShopFreeBSD</a>.</p>;
+
+      <p>We have continued our work with a new website developer to
+	help us improve
+	our website. Work has begun to make it easier for
+	community members to find
+	information and to make the site more efficient.</p>
+
+      <p>Legal/FreeBSD IP
+	The Foundation owns the FreeBSD trademarks, and it is our
+	responsibility to
+	protect them. We also provide legal support for the core
+	team to investigate
+	questions that arise.</p>
+
+      <p>Go to http://www.FreeBSDfoundation.org to find out how we
+	support FreeBSD and
+	how we can help you!</p>
+
+    </body>
+
+  </project>
+
+  <project cat='team'>
+    <title>FreeBSD Graphics Team status report</title>
+
+    <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>
+
+    <links>
+      <url href="https://github.com/FreeBSDDesktop">Project GitHub page</url>
+    </links>
+
+    <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>During the last period, several changes have been made,
+	but most of them has
+	been behind the scene.
+	We have also worked on general clean up of old xorg ports
+	that have been
+	deprecated upstream.</p>
+
+      <p>The ports infrastructure for xorg ports and ports that
+	depend on xorg ports have
+	been updated.
+	We have switched <tt>USE_XORG</tt> and <tt>XORG_CAT</tt>
+	to use the <tt>USES</tt> framework, instead
+	of the old way of including <tt>bsd.xorg.mk</tt> from
+	<tt>bsd.port.mk</tt>.
+	This infrastructure work has been fairly substantial, and
+	new ports depending on
+	xorg ports should add <tt>USES=xorg</tt> to their
+	makefiles.
+	As part of this <tt>bsd.xorg.mk</tt> was split up, and the
+	<tt>XORG_CAT</tt> part was split
+	out to <tt>USES=xorg-cat</tt>.
+	This is used for the xorg ports themselves, and sets up a
+	common environment for
+	building all xorg ports.
+	In addition, framework for pulling xorg ports directly
+	from freedesktop.org
+	gitlab was added, which will make improve development and
+	testing, since it
+	makes it possible to create ports of unreleased versions.
+	Further improvements in this area includes framework for
+	using meson instead of
+	autotools for building xorg ports.
+	This is still a work in progress.</p>
+
+      <p>We have also worked to clean up and deprecate several old
+	xorg ports and
+	libraries.
+	Some of these ports have already been removed, and some
+	are still waiting on
+	removal after a sufficient deprecation period.
+	Most notably amongst the deprecations are
+	<tt>x11/libXp</tt>, which required to fix
+	several dependencies.
+	Several other old libraries have also been deprecated,
+	such as <tt>x11/Xxf86misc</tt>,
+	<tt>x11-fonts/libXfontcache</tt> and
+	<tt>graphics/libGLw</tt>.
+	Some applications and drivers have also been deprecated
+	during the period.
+	With the remaining removals in this area, we should be up
+	to speed with
+	deprecations upstream.
+	We are currently investigating if there are new software
+	added upstream that we
+	need to port to FreeBSD.</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 gitter chat: <a
+	href="https://gitter.im/FreeBSDDesktop/Lobby">https://gitter.im/FreeBSDDesktop/Lobby</a>.
+	We are also available in #freebsd-xorg on EFNet.</p>
+
+      <p>We also have a team area on GitHub where our work
+	repositories can be found:
+	<a
+	href="https://github.com/FreeBSDDesktop">https://github.com/FreeBSDDesktop</a></p>;
+
+    </body>
+
+  </project>
+
+  <project cat='proj'>
+    <title>Google Summer of Code 2019</title>
+
+    <contact>
+      <person>
+	<name>Summer of Code Admins</name>
+	<email>soc-admins@freebsd.org</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="https://wiki.freebsd.org/SummerOfCode2019Projects">2019 Summer of Code Project Wikis</url>
+      <url href="https://summerofcode.withgoogle.com/archive/2019/organizations/6504969929228288/">2019 Summer of Code Projects</url>
+    </links>
+
+    <body>
+      <p>The FreeBSD Project is pleased to have participated in
+	Google Summer of Code 2019 marking our 14th year of
+	participation.
+	This year we had six successful projects:</p>
+
+      <ul>
+	<li><i>Dual-stack ping command</i> by Ján Sučan</li>
+
+	<li><i>Firewall test suite</i> by Ahsan Barkati</li>
+
+	<li><i>Kernel sanitizers</i> by Costin Carabaș</li>
+
+	<li><i>MAC policy on IP addresses for FreeBSD
+	Jail</i> by Shivank Garg</li>
+
+	<li><i>Separation of ports build process from local
+	installation</i> by Theron Tarigo</li>
+
+	<li><i>Virtual memory compression</i> by
+	Paavo-Einari Kaipila</li>
+      </ul>
+
+      <p>
+	We thank Google for the opportunity to work with these
+	students and hope
+	they continue to work with FreeBSD in the future.</p>
+
+    </body>
+
+    <sponsor>
+      Google Summer of Code
+    </sponsor>
+
+  </project>
+
+  <project cat='proj'>
+    <title>GSoC'19 Project - MAC policy on IP addresses in Jail: mac_ipacl</title>
+
+    <contact>
+      <person>
+	<name>Shivank Garg</name>
+	<email>shivank@FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="https://reviews.freebsd.org/D20967">FreeBSD's Phabricator Differential Link</url>
+      <url href="https://github.com/freebsd/freebsd/compare/master...shivankgarg98:shivank_MACPolicyIPAddressJail">Github Diff Link</url>
+      <url href="https://wiki.freebsd.org/SummerOfCode2019Projects/MACPolicyIPAddressJail">Project Wiki Page</url>
+    </links>
+
+    <body>
+      <p><b>About -</b> With the introduction of VNET(9)
+	in FreeBSD, Jails are free to
+	set their IP addresses. However, this privilege may need
+	to be limited by
+	the host as per its need for multiple security reasons.
+	This project uses mac(9) for an access control framework
+	to impose
+	restrictions on FreeBSD jails according to rules defined
+	by the root of the
+	host using sysctl(8). It involves the development of a
+	dynamically loadable
+	kernel module (mac_ipacl) based on The TrustedBSD MAC
+	Framework to
+	implement a security policy for configuring the network
+	stack.
+	This project allows the root of the host to define the
+	policy rules to
+	limit the root of a jail to a set of IP (v4 or v6)
+	addresses and/or subnets
+	for a set of interfaces.</p>
+
+      <p>Features this new MAC policy module are:</p>
+
+      <ul>
+	<li>The host can define one or more lists of IP
+	addresses/subnets
+      	for the jail to choose from.</li>
+
+	<li>The host can restrict the jail from setting certain IP
+	addresses or
+      	prefixes (subnets).</li>
+
+	<li>The host can restrict this privilege to a few network
+	interfaces.</li>
+      </ul>
+

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



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