From owner-svn-doc-head@freebsd.org  Sat Feb  4 05:29:05 2017
Return-Path: <owner-svn-doc-head@freebsd.org>
Delivered-To: svn-doc-head@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 611B3CD06E4;
 Sat,  4 Feb 2017 05:29:05 +0000 (UTC) (envelope-from bjk@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 mx1.freebsd.org (Postfix) with ESMTPS id 2E85E197;
 Sat,  4 Feb 2017 05:29:05 +0000 (UTC) (envelope-from bjk@FreeBSD.org)
Received: from repo.freebsd.org ([127.0.1.37])
 by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id v145T4iK090386;
 Sat, 4 Feb 2017 05:29:04 GMT (envelope-from bjk@FreeBSD.org)
Received: (from bjk@localhost)
 by repo.freebsd.org (8.15.2/8.15.2/Submit) id v145T4Gr090385;
 Sat, 4 Feb 2017 05:29:04 GMT (envelope-from bjk@FreeBSD.org)
Message-Id: <201702040529.v145T4Gr090385@repo.freebsd.org>
X-Authentication-Warning: repo.freebsd.org: bjk set sender to bjk@FreeBSD.org
 using -f
From: Benjamin Kaduk <bjk@FreeBSD.org>
Date: Sat, 4 Feb 2017 05:29:04 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
 svn-doc-head@freebsd.org
Subject: svn commit: r49916 - head/en_US.ISO8859-1/htdocs/news/status
X-SVN-Group: doc-head
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.23
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: Sat, 04 Feb 2017 05:29:05 -0000

Author: bjk
Date: Sat Feb  4 05:29:04 2017
New Revision: 49916
URL: https://svnweb.freebsd.org/changeset/doc/49916

Log:
  Editing pass through the 2016Q4 report

Modified:
  head/en_US.ISO8859-1/htdocs/news/status/report-2016-10-2016-12.xml

Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2016-10-2016-12.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2016-10-2016-12.xml	Fri Feb  3 15:52:50 2017	(r49915)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2016-10-2016-12.xml	Sat Feb  4 05:29:04 2017	(r49916)
@@ -103,7 +103,7 @@
 
       <p>&os;/EC2 is now part of the regular &os; release build,
 	with snapshots and releases being automatically uploaded and
-	copied to all available regions.  Due to legal restrictions
+	copied to all available regions.  Due to legal restrictions,
 	this does not currently include the GovCloud or China
 	(Beijing) regions; anyone wishing to use &os; in those regions
 	is encouraged to contact the author.</p>
@@ -111,11 +111,11 @@
       <p>The AWS Marketplace reports that approximately 800 users
 	are running roughly 2000 &os; EC2 instances.  This does not
 	count the likely significantly larger number of EC2 instances
-	launched "directly" through the EC2 API and Console, but at
+	launched &quot;directly&quot; through the EC2 API and Console, but at
 	least places a lower bound on usage.</p>
 
-      <p>&os; 11.0-RELEASE shipped with support for the "enhanced
-	networking" support in EC2 C3, C4, R3, I2, D2, and M4
+      <p>&os; 11.0-RELEASE shipped with support for the &quot;enhanced
+	networking&quot; support in EC2 C3, C4, R3, I2, D2, and M4
 	(excluding m4.16xlarge) instances.  This provides
 	significantly higher network performance than the virtual
 	networking available on older EC2 instances and with older
@@ -147,7 +147,7 @@
 	&os;/EC2 configuration.</task>
 
       <task>Continue ongoing interoperability testing between &os;'s
-	NFS client and Amazon Elastic File System
+	NFS client and the Amazon Elastic File System
 	(NFS-as-a-service).</task>
     </help>
   </project>
@@ -221,11 +221,11 @@
 	GEOM-based RAID arrays?  Is such information even exported
 	through <tt>sysctl</tt>?</task>
 
-      <task>Prometheus uses a pretty nifty format for exporting
+      <task>Prometheus uses a rather clever format for exporting
 	histograms.  Histograms are useful for expressing the amount
 	of time taken to complete certain events (for example, disk
 	operations).  Would it be possible to add histograms as native
-	datatypes to sysctl?  If so, is there any chance they can be
+	data types to <tt>sysctl</tt>?  If so, is there any chance they can be
 	implemented without picking up any kernel locks?</task>
     </help>
   </project>
@@ -312,7 +312,7 @@
 	and releases.  Currently only 11.0-RELEASE-amd64 gets tested
 	via an automated Jenkins job.</task>
 
-      <task>As every commit to libarchive may influence the build
+      <task>As every commit to <tt>libarchive</tt> may influence the build
 	process of &os; ports, the ability to trigger a
 	(semi-)automated exp-run for the ports tree would be
 	great.</task>
@@ -362,6 +362,10 @@
     </links>
 
     <body>
+      <p>This project provides native virtualized interfaces
+	for &os; systems running on Hyper-V virtualization, improving
+	on the performance of traditional emulated evices.</p>
+
       <p>Per-ring polling, multi-packet RNDIS messages, and system RSS
 	integration have been implemented, further optimizing the
 	throughput and latency of the Hyper-V network driver.</p>
@@ -413,7 +417,7 @@
     </contact>
 
     <body>
-      <p>The port has been updated to GDB 7.12.</p>
+      <p>The <tt>devel/gdb</tt> port has been updated to GDB 7.12.</p>
 
       <p>7.12 includes additional fixes related to tracing
 	<tt>vfork()</tt>s.  Some of these fixes depend on changes to
@@ -633,9 +637,9 @@
       <task>Apply the changes discussed in
 	<a href="https://reviews.FreeBSD.org/D8416">D8416</a>
 	(simplify the <tt>MASTER_SITES</tt> macro in port
-	Makefiles)</task>
+	Makefiles).</task>
 
-      <task>Commit the stable panel plugins</task>
+      <task>Commit the stable panel plugins.</task>
     </help>
   </project>
 
@@ -709,7 +713,7 @@
     </help>
 
     <sponsor>
-      Portions of this work were sponsored by DARPA/AFRL.
+      DARPA/AFRL (in part)
     </sponsor>
   </project>
 
@@ -809,13 +813,13 @@
 	<li>
 	  The European Court of Justice's &quot;Right to be
 	  Forgotten&quot; only applies to search engines, and the &os;
-	  project is not one of those, so need not take any
+	  project is not one of those, so it need not take any
 	  action.
 	</li>
 
 	<li>
 	  Core is following closely discussions within the LLVM
-	  project regarding a change of license which if implemented,
+	  project regarding a change of license which, if implemented,
 	  might require an audit of the entire ports tree to discover
 	  all packages that contain binaries linked against libc++ and
 	  ensure that they are licensed compatibly with LLVM.
@@ -975,7 +979,7 @@
 	  <p>Object Storage</p>
 
 	  <p>Ceph provides seamless access to objects using native
-	    language bindings or radosgw, a REST interface that is
+	    language bindings or <tt>radosgw</tt>, a REST interface that is
 	    compatible with applications written for S3 and
 	    Swift.</p>
 	</li>
@@ -1001,11 +1005,11 @@
 	that are running ZFS.  User stations would be running
 	<tt>bhyve</tt> on RBD disks that are stored in Ceph.</p>
 
-      <p>The &os; build will build most of the tools in Ceph.  Note
+      <p>The &os; build includes most of the tools in Ceph.  Note
 	that the RBD-dependent items will not work, since &os; does
 	not have RBD (yet).</p>
 
-      <p>Most notable progress since the last report:</p>
+      <p>The most notable progress since the last report:</p>
 
       <ul>
 	<li>
@@ -1053,10 +1057,9 @@
 	its clang 3.9.0, but 11-RELEASE will probably also work, given
 	experience with clang 3.7.0 from 11-CURRENT.  Interestingly,
 	when 12-CURRENT had clang 3.8.0, that did not work as well as
-	either 3.7.0 or 3.9.0..</p>
-
-      <p>The clang 3.4 present in 10-STABLE does not have the
-	required capabilities to compile everything.</p>
+	either 3.7.0 or 3.9.0.  The clang 3.4 present in 10-STABLE
+	does not have the required capabilities to compile
+	everything.</p>
 
       <p>The following setup will get things running for &os;:</p>
 
@@ -1120,7 +1123,7 @@
 	developed akin to &os;'s <tt>ggate</tt>.</task>
 
       <task>Investigate the keystore, which could be embedded in the
-	kernel on Linux, and currently prevents building Cephfs and
+	kernel on Linux, and currently prevents building CephFS and
 	some other components.  The first question whether it is
 	really required, or if only KRBD require it.</task>
 
@@ -1220,22 +1223,22 @@
 	unit up to Kaby Lake CPUs.  To facilitate out-of-the-box
 	support on CURRENT, most of the branch-local VM changes were
 	reverted and the graphics fault routines converted to use
-	pg_populate.  This new interface is the source of a couple of
-	regressions causing panics on i915 and severe artifacts with
-	amdgpu on integrated GPUs.  Mark Johnston (markj@) has
+	<tt>pg_populate</tt>.  This new interface is the source of a couple of
+	regressions causing panics on <tt>i915</tt> and severe artifacts with
+	<tt>amdgpu</tt> on integrated GPUs.  Mark Johnston (markj@) has
 	volunteered to analyze these issues.  Please show your support
 	and encouragement to Mark for helping to move this project
 	towards the finish line.</p>
 
       <p>The xserver-mesa-next-udev branch was created for the ports
 	development repository, and holds Mesa 13.0 and fixes for
-	newer AMD GPUs.  It uses a fork of the libudev-devd shim, also
-	bringing Mesa closer to Linux upstream.  I plan to keep
+	newer AMD GPUs.  It uses a fork of the <tt>libudev-devd</tt> shim, also
+	bringing Mesa closer to the Linux upstream.  I plan to keep
 	updating <tt>drm</tt> and <tt>amdgpu</tt> (for use on my
 	desktop and potentially longer term for GPGPU computations) as
 	well as work with Mark to address the existing bugs in
 	<tt>i915</tt> (assuming that two new porters are approved).
-	However, the Linux <tt>i915</tt> developers seems to
+	However, the Linux <tt>i915</tt> developers seem to
 	aggressively explore the space of possible implementations and
 	use of Linux internal APIs, making it prohibitively time
 	consuming to track upstream.  I am helping someone to learn
@@ -1317,7 +1320,7 @@
     </contact>
 
     <links>
-      <url href="https://wiki.FreeBSD.org/LLD">&os; lld Wiki Page</url>
+      <url href="https://wiki.FreeBSD.org/LLD">&os; LLD Wiki Page</url>
       <url href="http://llvm.org/pr23214">&os;/LLD Tracking PR (LLVM Bugzilla)</url>
     </links>
 
@@ -1350,7 +1353,7 @@
       <task>Fix <tt>libtool</tt> to detect LLD and pass the same
 	command line arguments as for GNU ld and gold.</task>
 
-      <task>Investigate remaining amd64 port build
+      <task>Investigate the remaining amd64 port build
 	failures.</task>
 
       <task>Investigate and improve LLD on arm64, i386, arm, and
@@ -1482,7 +1485,7 @@
 
       <p><tt>lang/gcc6</tt> has been updated first to GCC 6.2 and then
 	GCC 6.3, bringing a fair number of fixes, and should now be
-	finely suitable for production use.</p>
+	suitable for production use.</p>
     </body>
 
     <help>
@@ -1529,10 +1532,10 @@
 	of Nuget packages.  This extension has been used adopted by
 	FSharp, MonoDevelop and OpenRA.</p>
 
-      <p>Work has started on porting the Microsoft's open-sourced
+      <p>Work has started on porting Microsoft's open-sourced
 	Dotnet Core.  Thanks to the work of another team, the native
 	components of <tt>coreclr</tt> and <tt>corefx</tt> already
-	support &os;, however there is further work required in
+	support &os;, however, there is further work required in
 	bootstrapping the build process and compiling the managed
 	code.</p>
     </body>
@@ -1566,7 +1569,7 @@
     </contact>
 
     <links>
-      <url href="https://wiki.FreeBSD.org/arm64">&os; arm64 Wiki Entry</url>
+      <url href="https://wiki.FreeBSD.org/arm64">&os; arm64 Wiki Page</url>
     </links>
 
     <body>
@@ -1651,7 +1654,7 @@
 	kernel subsystems, add features and functionality, and fix
 	problems.  This also includes funding separate project grants
 	like the arm64 port, <tt>blacklistd</tt> access control
-	daemon, and integration of VIMAGE support, to make sure &os;
+	daemon, and integration of VIMAGE support, to make sure that &os;
 	remains a viable solution for research, education, computing,
 	products and more.</p>
 
@@ -1664,7 +1667,7 @@
 
 	<li>Toolchain work</li>
 
-	<li><tt>lacklistd</tt> access control daemon</li>
+	<li><tt>blacklistd</tt> access control daemon</li>
       </ul>
 
       <p>The Foundation team worked on a technology roadmap for
@@ -1685,7 +1688,7 @@
 	reliable releases over the last few years.</p>
 
       <p>Last quarter, our full-time staff member worked with the
-	&os; Release Engineering and Security Teams to finalize the
+	&os; Release Engineering and Security Teams to finalize
 	11.0-RELEASE.  He also added support for the powerpcspe
 	architecture to the 12-CURRENT snapshot builds, and continued
 	work on packaging the base system with <tt>pkg(8)</tt>.  He
@@ -1820,7 +1823,7 @@
 	facilitate collaboration between developers and commercial
 	users.  This all helps provide a healthy ecosystem.  We
 	support the non-&os; events to promote and raise awareness
-	about &os;, to increase the use of &os; in different
+	of &os;, to increase the use of &os; in different
 	applications, and to recruit more contributors to the
 	Project.</p>