From owner-p4-projects@FreeBSD.ORG  Sun Oct 11 09:25:37 2009
Return-Path: <owner-p4-projects@FreeBSD.ORG>
Delivered-To: p4-projects@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 375221065670; Sun, 11 Oct 2009 09:25:37 +0000 (UTC)
Delivered-To: perforce@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id EC96E1065676
	for <perforce@FreeBSD.org>; Sun, 11 Oct 2009 09:25:36 +0000 (UTC)
	(envelope-from pgj@FreeBSD.org)
Received: from repoman.freebsd.org (repoman.freebsd.org
	[IPv6:2001:4f8:fff6::29])
	by mx1.freebsd.org (Postfix) with ESMTP id D9FC78FC0C
	for <perforce@FreeBSD.org>; Sun, 11 Oct 2009 09:25:36 +0000 (UTC)
Received: from repoman.freebsd.org (localhost [127.0.0.1])
	by repoman.freebsd.org (8.14.3/8.14.3) with ESMTP id n9B9Pagi096844
	for <perforce@FreeBSD.org>; Sun, 11 Oct 2009 09:25:36 GMT
	(envelope-from pgj@FreeBSD.org)
Received: (from perforce@localhost)
	by repoman.freebsd.org (8.14.3/8.14.3/Submit) id n9B9PaEU096842
	for perforce@freebsd.org; Sun, 11 Oct 2009 09:25:36 GMT
	(envelope-from pgj@FreeBSD.org)
Date: Sun, 11 Oct 2009 09:25:36 GMT
Message-Id: <200910110925.n9B9PaEU096842@repoman.freebsd.org>
X-Authentication-Warning: repoman.freebsd.org: perforce set sender to
	pgj@FreeBSD.org using -f
From: Gabor Pali <pgj@FreeBSD.org>
To: Perforce Change Reviews <perforce@FreeBSD.org>
Cc: 
Subject: PERFORCE change 169379 for review
X-BeenThere: p4-projects@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: p4 projects tree changes <p4-projects.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/p4-projects>,
	<mailto:p4-projects-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/p4-projects>
List-Post: <mailto:p4-projects@freebsd.org>
List-Help: <mailto:p4-projects-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/p4-projects>,
	<mailto:p4-projects-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Oct 2009 09:25:37 -0000

http://perforce.freebsd.org/chv.cgi?CH=169379

Change 169379 by pgj@beehive on 2009/10/11 09:24:54

	IFC

Affected files ...

.. //depot/projects/docproj_hu/www/en/news/status/report-2009-04-2009-09.xml#2 integrate
.. //depot/projects/docproj_hu/www/hu/administration.sgml#21 integrate

Differences ...

==== //depot/projects/docproj_hu/www/en/news/status/report-2009-04-2009-09.xml#2 (text+ko) ====

@@ -2,7 +2,7 @@
 <!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status
 Report//EN"
 "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
-<!-- $FreeBSD: www/en/news/status/report-2009-04-2009-09.xml,v 1.6 2009/10/07 19:52:24 gabor Exp $ -->
+<!-- $FreeBSD: www/en/news/status/report-2009-04-2009-09.xml,v 1.13 2009/10/09 13:19:54 danger Exp $ -->
 <report>
   <date>
     <month>April-September</month>
@@ -16,10 +16,11 @@
     <p>This report covers FreeBSD related projects between April and
     September 2009.  During that time a lot of work has been done on
     wide variety of projects, including the Google Summer of Code
-    projects. The BSDCan and EuroBSDCon conferences were held in Ottawa,
-    CA, and Cambridge, UK which were both very successful.
+    projects.  The BSDCan conference was held in Ottawa, CA, in May.
+    The EuroBSDCon conference was held in Cambridge, UK, in September.
+    Both events were very successful.
     A new major version of FreeBSD, 8.0 is to be released soon.
-    If you are wondering what's new in this long awaited release, read
+    If you are wondering what's new in this long-awaited release, read
     Ivan Voras' excellent <a
     href="http://ivoras.sharanet.org/freebsd/freebsd8.html">summary</a>.</p>
 
@@ -28,7 +29,7 @@
 
     <p>Please note that the next deadline for submissions covering
     reports between October and December 2009 is January 15th,
-    2011.</p>
+    2010.</p>
   </section>
 
   <category>
@@ -68,12 +69,6 @@
   </category>
 
   <category>
-    <name>bin</name>
-
-    <description>Userland Programs</description>
-  </category>
-
-  <category>
     <name>arch</name>
 
     <description>Architectures</description>
@@ -97,8 +92,8 @@
     <contact>
       <person>
         <name>
-	  <given>Gábor</given>
- 	  <common>Páli</common>
+	  <given>G&aacute;bor</given>
+ 	  <common>P&aacute;li</common>
         </name>
 
         <email>pgj@FreeBSD.org</email>
@@ -111,7 +106,7 @@
     </links>
 
     <body>
-      <p>libnetstat(3) provides a user-space library API to monitor
+      <p>The libnetstat(3) project provides a user-space library API to monitor
         networking functions with the following benefits:</p>
 
       <ul>
@@ -129,12 +124,12 @@
       <p>The supported abstractions are as follows:</p>
 
       <ul>
-        <li>Active sockets and socket buffers.</li>
-        <li>Network interfaces and multicast interfaces.</li>
-        <li>mbuf(9) statistics.</li>
-        <li>bpf(4) statistics.</li>
-        <li>Routing statistics, routing tables, multicast routing.</li>
-        <li>Protocol-dependent statistics.</li>
+        <li>Active sockets and socket buffers</li>
+        <li>Network interfaces and multicast interfaces</li>
+        <li>mbuf(9) statistics</li>
+        <li>bpf(4) statistics</li>
+        <li>Routing statistics, routing tables, multicast routing</li>
+        <li>Protocol-dependent statistics</li>
       </ul>
 
       <p>There is a sample application, called nettop(8), which provides a
@@ -178,11 +173,11 @@
 
     <body>
       <p>Pefs is a kernel level filesystem for transparently encrypting
-      files on top of other filesystems (like zfs or ufs). It adds no
+      files on top of other filesystems (like zfs or ufs).  It adds no
       extra information into files (unlike others), doesn't require
       cipher block sized io operations, supports per directory/file keys
       and key chaining, uses unique per file tweak for encryption.
-      Supported algorithms: AES, Camellia, Salsa20. The code is ready for
+      Supported algorithms: AES, Camellia, Salsa20.  The code is ready for
       testing.</p>
     </body>
 
@@ -223,12 +218,12 @@
       <p>During the past year, the BSD# Team continued to track the Mono
       development and the lang/mono port have almost always been
       up-to-date (we however had to skip mono-2.2 because of some
-      regression issues in this release). Most of our patches have been
+      regression issues in this release).  Most of our patches have been
       merged in the mono trunk upstream, and should be included in the
       upcoming mono-2.6 release.</p>
 
       <p>In the meantime, a few more .NET related ports have been updated
-      or added to the FreeBSD ports tree. These ports include:</p>
+      or added to the FreeBSD ports tree.  These ports include:</p>
 
       <ul>
         <li>www/xsp and www/mod_mono that make it possible to use FreeBSD
@@ -249,9 +244,9 @@
     </body>
 
     <help>
-      <task>Test mono ports and send feedback (a special attention to
-      environments where NOPORTDOCS / WITH_DEBUG is set has to be
-      taken).</task>
+      <task>Test mono ports and send feedback (we are especially
+      interested in tests where NOPORTDOCS / WITH_DEBUG is
+      enabled).</task>
 
       <task>Port the mono-debugger to FreeBSD.</task>
 
@@ -285,13 +280,13 @@
 
     <body>
       <p>Some time ago I started writing a new driver for the FreeBSD
-      kernel called vt(4), which is basically a replacement for Syscons.
-      There is still a lot of work that needs to be done, but it is
-      probably useful to mention what it does (and what not).</p>
+      kernel called vt(4), which is basically a replacement of syscons.
+      There is still a lot of work that needs to be done but it is
+      probably useful to mention what it does (and what does not).</p>
 
       <p>Right now there are just two graphics drivers for vt(4), namely
       a VGA driver for i386 and amd64 and a Microsoft Xbox graphics
-      driver (because it was so easy to write). I still have to figure
+      driver (because it was so easy to implement).  I still have to figure
       out what I am going to do with VESA, because maybe it is better to
       just ignore VESA and figure out how hard it is to extend DRM to
       interact with vt(4).</p>
@@ -331,35 +326,74 @@
     </contact>
 
     <links>
-      <url href="http://svn.freebsd.org/viewvc/base/projects/libprocstat/">libprocstat's repository</url>
+      <url href="http://svn.freebsd.org/viewvc/base/projects/libprocstat/">libprocstat repository</url>
     </links>
 
     <body>
-      <p>Libprocstat is an ongoing effort to develop a library that can
-        be used to retrieve the information about running processes and
+      <p>The libprocstat project is an ongoing effort to develop a library that can
+        be used to retrieve information about running processes and
 	open files in the uniform and platform-independent way both from
 	a running system or from core files.  This will facilitate the
-	implementation of files/process monitoring applications like
-	lsof/fstat/fuser/etc. The libprocstat repository contents the
-	preliminary version of the library as well as fstat and fuser
-	utilities ported to use this library instead of retriving all
-	the required information by hand via kvm(3) interface, which
-	makes them ABI independent as the result.</p>
+	implementation of file- or process-monitoring applications like
+	lsof(1), fstat(1), fuser, etc.  The libprocstat repository contains a
+	preliminary version of the library.  It also includes rewrites
+	of the fstat and the fuser
+	utilities ported to use this library instead of retrieving all
+	the required information via the kvm(3) interface; one of the
+	important advantages of the versions that use libprocstat is
+	that these utilities are ABI independent.</p>
     </body>
 
     <help>
       <task>
         Implement KVM-based namecache lookup to retrieve filesystem paths
-	associated with file descriptors/VM objects.
+	associated with file descriptors and VM objects.
       </task>
       <task>
-        Ananlyze possible ways of exporting files/processes information
-	from the kernel in the extensible ABI-independend way.
+        Analyze possible ways of exporting file and process information
+	from the kernel in an extensible and ABI-independent way.
       </task>
     </help>
   </project>
 
   <project cat='proj'>
+    <title>New BSD licensed debugger</title>
+
+    <contact>
+      <person>
+	<name>
+	  <given>Doug</given>
+	  <common>Rabson</common>
+	</name>
+      </person>
+    </contact>
+
+    <links>
+      <url href="http://wiki.freebsd.org/TheBsdDebugger">Wiki page</url>
+      <url href="http://people.freebsd.org/~dfr/ngdb.git">Repository</url>
+      <url href="http://wiki.freebsd.org/200909DevSummit?action=AttachFile&amp;do=view&amp;target=NGDB-200909.pdf">Slides</url>
+    </links>
+
+    <body>
+      <p>I have been working recently on writing a new debugger,
+	primarily for the FreeBSD platform.  For various reasons, I have
+	been writing it in a relatively obscure C-like language called
+	D.</p>
+
+      <p>So far, I have a pretty useful (if a little raw at the edges)
+	command line debugger which supports ELF, Dwarf debugging
+	information and (currently) 32 bit FreeBSD and Linux.  The
+	engine includes parsing and evaluation of arbitrary C expressions
+	along with the usual debugging tools such as breakpoints, source
+	code listing, single-step etc.  All the code is new and BSD
+	licensed.  Currently, the thing supports userland debugging of
+	i386 targets via ptrace and post-mortem core file debugging of
+	the same.  I will be adding amd64 support real soon (TM) and
+	maybe support for GDB's remote debugging protocol later.</p>
+    </body>
+  </project>
+
+  <project cat='proj'>
     <title>Clang replacing GCC in the base system</title>
 
     <contact>
@@ -410,8 +444,7 @@
 
     <body>
       <p>The clang@FreeBSD team presents the status of clang/LLVM being
-      able to compile FreeBSD system. The situation as of today (early
-      October) is:</p>
+      able to compile FreeBSD system.  The current status is:</p>
 
       <ul>
         <li>i386 - kernel boots, world needs little hacks but works</li>
@@ -425,27 +458,103 @@
 
       <p>All other platforms are untested.</p>
 
-      <p>A lot has happened over the spring/summer - amd64 got proper
-      mcmodel=kernel support, compiler-rt was introduced (paving the way
-      for libgcc replacement), we ran two experimental ports build to see
-      how clang does there, C++ support is able to parse devd.cc without
-      warnings, we got kernel working with -O2, we promoted FreeBSD to be
-      officially supported plaform in LLVM, many parts of FreeBSD sources
-      that we could not compile before we can compile now etc.</p>
+      <p>A lot has happened over the spring/summer: amd64 got proper
+      mcmodel=kernel support, compiler-rt has been introduced (paving the way
+      for libgcc replacement), we have run two experimental port builds to see
+      how clang does there.  The C++ support is able to parse devd.cc without
+      warnings.  We have got the kernel working with -O2.  FreeBSD has been promoted
+      to be an officially supported plaform in LLVM.  As a result of all this
+      work, many parts of FreeBSD that did not compile before now build
+      without problems.</p>
     </body>
 
     <help>
-      <task>ClangBSD branch of FreeBSD got a little stale and has not
+      <task>The "ClangBSD" branch of FreeBSD got a little stale and has not
       been updated for a while.</task>
+
       <task>We also need to get some important fixes
       into LLVM to get libc compiling and some other smaller issues.</task>
-      <task>We
-      can still appreciate more testers on minor platforms (arm, ppc and
-      mips mostly).</task>
+
+      <task>We can still appreciate more testers on minor platforms (mostly on
+      ARM, PPC and MIPS, but testing on other platforms is also welcome).</task>
     </help>
   </project>
 
   <project cat='proj'>
+    <title>Grand Central Dispatch - FreeBSD port</title>
+
+    <contact>
+      <person>
+	<name>
+	  <given>Robert</given>
+	  <common>Watson</common>
+	</name>
+	<email>rwatson@FreeBSD.org</email>
+      </person>
+      <person>
+	<name>
+	  <given>Stacey</given>
+	  <common>Son</common>
+	</name>
+	<email>sson@FreeBSD.org</email>
+      </person>
+      <person>
+	<name>
+	  <given>libdispatch mailing list</given>
+	</name>
+	<email>libdispatch-dev@lists.macosforge.org</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="http://libdispatch.macosforge.org/">GCD / libdispatch web page</url>
+    </links>
+
+    <body>
+      <p>We have ported libdispatch, Apple's Grand Central Dispatch event
+	and concurrency framework to FreeBSD:</p>
+
+      <ul>
+	<li>Added new kqueue primitives required to support GCD, such
+	  as EVFILT_USER and EV_TRIGGER</li>
+	<li>Created autoconf and automake build framework for libdispatch</li>
+	<li>Modified libdispatch to use POSIX semaphores instead of
+	  Mach semaphores</li>
+	<li>Adapted libdispatch to use portable POSIX time routines</li>
+      </ul>
+
+      <p>Jordan Hubbard has also prepared a blocks-aware clang compiler
+	package for FreeBSD.  When compiled with clang, libdispatch
+	provides blocks-based, as well as function-based callbacks.</p>
+
+      <p>The port was presented at the FreeBSD Developer Summit in
+	Cambridge, UK in September, and slides are online on the devsummit
+	wiki page.  A FreeBSD port is now available in the Ports Collection.
+	After FreeBSD 8.0-RELEASE has shipped, the new kqueue primitives will be
+	MFC'd so that libdispatch works out of the box on FreeBSD 8.1-RELEASE.</p>
+    </body>
+
+    <help>
+      <task>
+	Complete porting of libdispatch test suite to FreeBSD.
+      </task>
+      <task>
+	Investigate pthread work queue implementation for FreeBSD.
+      </task>
+      <task>
+	Evaluate performance impact of some machine-dependent and
+	OS-dependent optimizations present in the Mac OS X version of
+	libdispatch to decide if they should be done for other
+	platforms and OS's.
+      </task>
+      <task>
+	Explore whether FreeBSD base operating system tools would benefit
+	from being modified to use libdispatch.
+      </task>
+    </help>
+  </project> 
+
+  <project cat='proj'>
     <title>VirtualBox on FreeBSD</title>
 
     <contact>
@@ -491,11 +600,11 @@
     </links>
 
     <body>
-      <p>VirtualBox has been committed to the Ports tree and synced
-        with the latest trunk version from SUN. A lot of known 
-        problems are already fixed and some new features have been 
+      <p>VirtualBox has been committed to the Ports tree and synchronized
+        with the latest trunk version from Sun.  Several known
+        problems are already fixed and some new features have been
         added:</p>
-      
+
       <ul>
         <li>VT-x support</li>
         <li>Bridging support (Big Thanks to Fredrik Lindberg)</li>
@@ -504,9 +613,11 @@
         <li>Host DVD/CD access</li>
         <li>SMP Support</li>
       </ul>
-         
-      <p>We would like to say thanks to all helpers/reporters and of course
-        to the VirtualBox developers.</p>
+
+      <p>We would like to say thanks to all the people who helped us by
+      reporting bugs and submitting fixes.  We also thank the VirtualBox
+      developers for their help with the ongoing effort to port
+      VirtualBox on FreeBSD.</p>
     </body>
   </project>
 
@@ -542,7 +653,7 @@
 
     <body>
       <p>The current translations (Handbook and some articles) are kept
-      up to date with the English versions. Some parts of the website
+      up to date with the English versions.  Some parts of the website
       have been 
       <url href="http://www.freebsd.org/nl">translated</url>, more work
       is in progress.</p>
@@ -599,25 +710,25 @@
     <body>
       <p>In May 2009, Benedict Reuschling received his commit bit to the
       www/de and doc/de_DE.ISO8859-1 trees under the mentorship of Johann
-      Kois. Since then, he has been working primarily on the Handbook, updating
-      existing chapters and translating new ones. Most notably, the
-      filesystems and DTrace chapters have been recently translated. Bugs found
+      Kois.  Since then, he has been working primarily on the Handbook, updating
+      existing chapters and translating new ones.  Most notably, the
+      filesystems and DTrace chapters have been recently translated.  Bugs found
       in the original documents along the way were reported back so that
       the other translation teams could incorporate them, as well.</p>
 
       <p>Christoph Sold has put his time in translating the wiki pages of
-      the BSD Certification Group into the German language. This is a
-      great help for German people, who want to take the exam and like to read
-      the information about it in their native language. Daniel Seuffert
-      has sent valuable corrections and bugfixes. Thanks to both for
+      the BSD Certification Group into the German language.  This is very
+      helpful for all German people who want to take the exam and like to read
+      the information about it in their native language.  Daniel Seuffert
+      has sent valuable corrections and bugfixes.  Thanks to both of them for
       their time and efforts!</p>
 
-      <p>The website is translated and updated constantly. Missing parts
+      <p>The website is translated and updated constantly.  Missing parts
       will be translated as time permits.</p>
 
       <p>We appreciate any help from volunteers in proofreading
-      documents, translating new ones and keeping them up to date. Even
-      small error reports are of great help for us. You can find
+      documents, translating new ones and keeping them up to date.  Even
+      small error reports are of great help for us.  You can find
       contact information at the above URL.</p>
     </body>
 
@@ -627,14 +738,14 @@
 
       <task>Translate more articles to German.</task>
 
-      <task>Read the translations. Check for problems/mistakes. Send
+      <task>Read the translations.  Check for problems and mistakes.  Send
       feedback.</task>
     </help>
   </project>
 
   <project cat="team">
     <title>The FreeBSD Foundation Status Report</title>
-   
+
     <contact>
       <person>
 	<name>
@@ -654,23 +765,204 @@
 	<a href="http://www.freebsdfoundation.org/donate/">http://www.freebsdfoundation.org/donate/</a>.</p>
 
       <p>We were a sponsor for EuroBSDCon 2009, and provided travel
-	grants to 8 FreeBSD developers and users. We sponsored Kyiv BSD
-	2009, in Kiev Ukraine. We were also a sponsor of BSDCan, and
-	sponsored 7 developers. We funded three new projects, New Console
+	grants to 8 FreeBSD developers and users.  We sponsored Kyiv BSD
+	2009, in Kiev Ukraine.  We were also a sponsor of BSDCan, and
+	sponsored 7 developers.  We funded three new projects, New Console
 	Driver by Ed Schouten, AVR32 Support by Arnar Mar Sig, and
 	Wireless Mesh Support by Rui Paulo, which has completed.
 	We continued funding a project that is making improvements to the
-	FreeBSD TCP Stack by Lawrence Stewart. The project that made
+	FreeBSD TCP Stack by Lawrence Stewart.  The project that made
 	removing disk devices with mounted filesystems on them safe, by
-	Edward Napierala, completed.</p>
+	Edward Napierala, is now complete.</p>
 
       <p>We recognized the following FreeBSD developers at EuroBSDCon
-	2009: Poul-Henning Kamp, Bjoern Zeeb, and Simon Nielsen. These
+	2009: Poul-Henning Kamp, Bjoern Zeeb, and Simon Nielsen.  These
 	developers received limited edition FreeBSD Foundation vests.</p>
 
       <p>Follow us on <a
-	href="https://twitter.com/freebsdfndationTwitter">Twitter</a> now!</p>
+	href="https://twitter.com/freebsdfndation">Twitter</a> now!</p>
+    </body>
+  </project>
+
+  <project cat='team'>
+    <title>FreeBSD Bugbusting Team</title>
+
+    <contact>
+      <person>
+	<name>
+	  <given>Gavin</given>
+	  <common>Atkinson</common>
+	</name>
+	<email>gavin@FreeBSD.org</email>
+      </person>
+      <person>
+	<name>
+	  <given>Mark</given>
+	  <common>Linimon</common>
+	</name>
+	<email>linimon@FreeBSD.org</email>
+      </person>
+      <person>
+	<name>
+	  <given>Remko</given>
+	  <common>Lodder</common>
+	</name>
+	<email>remko@FreeBSD.org</email>
+      </person>
+      <person>
+	<name>
+	  <given>Volker</given>
+	  <common>Werth</common>
+	</name>
+	<email>vwe@FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="http://www.FreeBSD.org/support.html#gnats" />
+      <url href="http://wiki.FreeBSD.org/BugBusting" />
+      <url href="http://people.FreeBSD.org/~linimon/studies/prs/" />
+      <url href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html" />
+    </links>
+
+    <body>
+      <p>We continue to classify PRs as they arrive, adding 'tags' to
+	the subject lines corresponding to the kernel subsystem
+	involved, or man page references for userland PRs.  These tags,
+	in turn, produce lists of PRs sorted both by tag and by
+	manpage.</p>
+
+      <p>The list of PRs recommended for committer evaluation by the
+	Bugbusting Team continues to receive new additions.  This list
+	contains PRs, mostly with patches, that the Bugbusting Team
+	feel are probably ready to be committed as-is, or are probably
+	trivially resolved in the hands of a committer with knowledge
+	of the particular subsystem.  All committers are invited to take
+	a look at this list whenever they have a spare 5 minutes and
+	wish to close a PR.</p>
+
+      <p>A full list of all the automatically generated reports is also
+	available at one of the cited URLs.  Any recommendations for
+	reports which not currently exist but which would be
+	beneficial are welcomed.</p>
+
+      <p>Gavin Atkinson gave a presentation on "The PR Collection
+	Status" at the EuroBSDCon 2009 DevSummit, and discussed with
+	other participants several other ideas to make the PR database
+	more useful and usable.  Several good ideas came from this, and
+	will hopefully lead to more useful tools in the near future.
+	Discussions also took place on how it may be possible to
+	automatically classify non-ports PRs with a view towards
+	notifying interested parties, although investigations into this
+	have not yet begun.</p>
+
+      <p>Mark Linimon also continues attempting to define the general
+	problem and investigating possible new workflow models, and
+	presented work on this at BSDCan 2009.</p>
+
+      <p>Since the last status report, the number of open bugs has
+	increased to around the 5900 mark, partially because of an
+	increased focus on getting more information into the existing
+	PRs, in an attempt to make sure all the information required is
+	now available.  As a result, although the number of open PRs has
+	increased, they are hopefully of better quality.</p>
+
+      <p>As always, more help is appreciated, and committers and
+	non-committers alike are always invited to join us on
+	#freebsd-bugbusters on EFnet and help close stale PRs or commit
+	patches from valid PRs.</p>
+    </body>
+
+    <help>
+      <task>
+	Work on suggestions from developers who were at the EuroBSDCon
+	DevSummit.
+      </task>
+      <task>
+	Try to find ways to get more committers helping us with closing
+	the PRs that the team has already analyzed.
+      </task>
+    </help>
+  </project>
+
+  <project cat='team'>
+    <title>FreeBSD Ports Management Team</title>
+
+    <contact>
+      <person>
+	<name>
+	  <given>Mark</given>
+	  <common>Linimon</common>
+	</name>
+	<email>linimon@FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="http://www.freebsd.org/ports/">The FreeBSD Ports
+	  Collection</url>
+      <url href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/">
+	  Contributing to the FreeBSD Ports Collection</url>
+      <url href="http://portsmon.FreeBSD.org/index.html">The FreeBSD
+	  ports monitoring system</url>
+      <url href="http://www.freebsd.org/portmgr/index.html">The
+	  FreeBSD Ports Management Team</url>
+      <url href="http://tinderbox.marcuscom.com">marcuscom Tinderbox</url>
+    </links>
+
+    <body>
+      <p>The ports count has soared to over 20,700.  The PR count had
+	been driven below 800 by some extraordinary effort, but once
+	again is back to its usual count of around 900.</p>
+
+      <p>We are currently building packages for amd64-6, amd64-7,
+	amd64-8, i386-6, i386-7, i386-8, sparc64-7, and sparc64-8.
+	There have been preliminary runs of i386-9; however, to be able
+	to continue builds on -9, we will either need to find places to
+	host a number of new machines, or drop package building for -6.
+	The mailing list discussion of the latter proved quite
+	controversial.</p>
+
+      <p>We have added some new i386 machines to help speed up the
+	builds, but this only makes up for the disk failures on some
+	of our older, slower, i386 nodes.</p>
+
+      <p>We also appreciate the loan of more package build machines from
+	several committers, including pgollucci@, gahr@, erwin@, Boris
+	Kochergin, and Craig Butler.</p>
+
+      <p>The portmgr@ team has also welcomed new members Ion-Mihai Tetcu
+	(itetcu@) and Martin Wilke (miwi@).  We also thank departing
+	member Kirill Ponomarew (krion@) for his long service.</p>
+
+      <p>Ion-Mihai has spent much time working on a system that does
+	automatic Quality Assurance on new commits, called QATty.
+	This has helped us to fix many problems, especially those
+	involving custom LOCALBASE settings, and documentation inclusion
+	options.</p>
+
+      <p>Between pav and miwi, over 2 dozen experimental ports runs have
+	been completed and committed.</p>
+
+      <p>We have added 5 new committers since the last report, and 2
+	older ones have rejoined.</p>
     </body>
+
+    <help>
+      <task>We are currently trying to set up ports tinderboxes that
+	can be made available to committers for pre-testing.</task>
+      <task>Most of the remaining ports PRs are "existing port/PR
+	assigned to committer".  Although the maintainer-timeout policy
+	is helping to keep the backlog down, we are going to need to do
+	more to get the ports in the shape they really need to be
+	in.</task>
+      <task>Although we have added many maintainers, we still have
+	almost 4,700 unmaintained ports (see, for instance, the list on
+	portsmon).  (The percentage is down to 22%.)  We are always
+	looking for dedicated volunteers to adopt at least a few
+	unmaintained ports.  As well, the packages on amd64 and sparc64
+	lag behind i386, and we need more testers for those.</task>
+    </help>
   </project>
 
   <project cat='team'>
@@ -718,20 +1010,20 @@
 
     <body>
       <p>Since the spring, the FreeBSD KDE team has been busy upgrading
-      KDE from 4.2.0 up through to 4.3.1. As part of the ongoing
+      KDE from 4.2.0 up through to 4.3.1.  As part of the ongoing
       maintenance of KDE, the team also updated Qt4 from 4.4.3 through to
       4.5.2</p>
 
       <p>We added two new committers/maintainers to the team, Kris Moore
-      (kmoore@) and Dima Panov (fluffy@). We also granted enhanced area51
+      (kmoore@) and Dima Panov (fluffy@).  We also granted enhanced area51
       access to contributors Alberto Villa and Raphael Kubo da Costa.
       Alberto has been our key contributor updating and testing Qt
-      4.6.0-tp1. Raphael is a KDE developer, who has become our Gitorious
+      4.6.0-tp1.  Raphael is a KDE developer, who has become our Gitorious
       liaison, he has been responsible for getting FreeBSD Qt patches
       merged in upstream.</p>
 
       <p>Markus Br&uuml;ffer (markus@) spent a lot of time patching widgets
-      and system plugins so they would work under FreeBSD. We would like
+      and system plugins so they would work under FreeBSD.  We would like
       to thank him for all his effort!</p>
     </body>
 
@@ -746,6 +1038,40 @@
   </project>
 
   <project cat='misc'>
+    <title>FreeBSD Developer Summit, Cambridge UK</title>
+
+    <contact>
+      <person>
+	<name>
+	  <given>Robert</given>
+	  <common>Watson</common>
+	</name>
+	<email>rwatson@FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="http://wiki.FreeBSD.org/200909DevSummit" />
+    </links>
+
+    <body>
+      <p>Around 70 FreeBSD developers and guests attended the FreeBSD
+	developer summit prior to EuroBSDCon 2009 in Cambridge, UK.
+	Hosted at the University of Cambridge Computer Laboratory, the
+	workshop-style event consisted of prepared presentations, as well
+	as group hacking and discussion sessions.  Talks covered topics
+	including 802.11 mesh networking, virtual network stacks and
+	kernels, a new BSD-licensed debugger, benchmarking, bugbusting,
+	NetFPGA, a port of Apple's GCD (Grand Central Dispatch) to
+	FreeBSD, security policy work, cryptographic signatures,
+	FreeBSD.org system administration, time geeks, a new console
+	driver, and the FreeBSD subversion migration.  Slides for many
+	talks are now available on the wiki page.  A good time was had by
+	all, including a punting outing on the River Cam!</p>
+    </body>
+  </project>
+
+  <project cat='misc'>
     <title>EuroBSDcon 2009</title>
 
     <contact>
@@ -778,13 +1104,12 @@
 
     <body>
       <p>EuroBSDcon 2009 happened in Cambridge, with over 160 users,
-      developers, friends and others. Slides, papers and audio are now up
-      on the website for those who could not make it to Cambridge. Next
+      developers, friends and others.  Slides, papers and audio are now up
+      on the website for those who could not make it to Cambridge.  Next
       year's event in 2010 will take place in Karlsruhe from 8 to 10 October
-      2010. If you are interested in what you missed in 2009, or to join
-      the mailing list so you do not miss out next year, visit 
-      <a href="http://2009.eurobsdcon.org/">
-      http://2009.eurosbsdcon.org</a>.
+      2010.  If you are interested in what you missed in 2009, or to join
+      the mailing list so you do not miss out next year, visit
+      <a href="http://2009.eurobsdcon.org/">http://2009.eurosbsdcon.org</a>.
 
       </p>
     </body>
@@ -822,31 +1147,31 @@
     <body>
       <p>Since their public launch in November 2008, the FreeBSD Forums
       (the most recent addition to the user community and support
-      channels for the FreeBSD Operating System), have witnessed a
+      channels for the FreeBSD Operating System) have witnessed a
       healthy and steady growth.</p>
 
       <p>The user population is now at over 8,000 registered users, who
       have participated in over 6,000 topics, containing over 40,000
-      posts in total. The sign-up rate hovers between 50-100 each week.
+      posts in total.  The sign-up rate hovers between 50-100 each week.
       The total number of visitors (including 'guests') is hard to gauge
       but is likely to be a substantial multiple of the registered
       userbase.</p>
 
       <p>New topics and posts are actively 'pushed out' to search
-      engines. This in turn makes the Forums show up in search results
+      engines.  This in turn makes the Forums show up in search results
       more and more often, making it a valuable and very accessible
       source of information for the FreeBSD community.</p>
 
-      <p>One of the contributing factors to the Forum's success is its
+      <p>One of the contributing factors to the Forums' success is their
       'BSD-style' approach when it comes to administration and
-      moderation. The Forums have a strong and unified identity, they are
+      moderation.  The Forums have a strong and unified identity, they are
       neatly divided into sub-forums (like 'Networking', 'Installing
       &amp; Upgrading', etc.), very actively moderated, spam-free, and
       with a core group of very active and helpful members, dispensing
       many combined decades' worth of knowledge to starting, intermediate
       and professional users of FreeBSD.</p>
 
-      <p>We expect the Forums te be, and to remain, a central hub in
+      <p>We expect the Forums to be, and to remain, a central hub in
       FreeBSD's community and support efforts.</p>
     </body>
   </project>
@@ -887,24 +1212,28 @@
       <p>Problem: Over the years the FreeBSD locale database
       (share/colldef, share/monetdef, share/msgdef, share/numericdef,
       share/timedef) has accumulated a total of 165 definitions (language
-      - country-code - character-set triplets). The contents of the files
-      is for Western European languages often low-ASCII but for Eastern
-      European and Asian languages partly or fully high-ASCII. Without
+      - country-code - character-set triplets).  The contents of the files
+      for Western European languages are often low-ASCII but for Eastern
+      European and Asian languages partly or fully high-ASCII.  Without
       knowing how to display or interpret the character-sets, it is
       difficult to make sure by the general audience that the local
-      languages (language - country-code) definitions is displayed
-      properly in various character-sets. Suggested approach: With the
-      combination of the data in the Unicode project (which goal is to
+      language (language - country-code) definitions are displayed
+      properly in various character-sets.</p>
+
+      <p>Suggested approach: With the
+      combination of the data in the Unicode project (whose goal is to
       define all the possible written characters and symbols on this
-      planet) and the Common Locale Data Repository (which goal is to
+      planet) and the Common Locale Data Repository (whose goal is to
       document all the different data and definitions needed for the
       locale database), we can easily keep track of the data, without the
       need of being able to display the data in the required
-      charactersets or understand them fully when updates are submitted
-      by third parties. Current status: Conversion of share/monetdef,
+      character sets or understand them fully when updates are submitted
+      by third parties.</p>
+
+      <p>Current status: Conversion of share/monetdef,
       share/msgdef, share/numericdef, share/timedef to the new design is
-      completed. The Makefile infrastructure is converted. Regression
-      checks are done. Most of the tools are in place, waiting on the
+      completed.  The Makefile infrastructure is converted.  Regression
+      checks are done.  Most of the tools are in place, waiting on the
       import of bsdiconv to the base system.</p>
     </body>
 
@@ -912,9 +1241,9 @@
       <task>At this moment the system is not self-hosted yet, because of
       the lack of an iconv-kind of program in the base operating system.
       Gabor@ is working on bsdiconv as a GSoC project and once that has been
-      imported we will be able to clean install from the definitions in
+      imported we will be able to perform a clean install from the definitions in
       Unicode text format to the required formats and
-      charactersets.</task>
+      character sets.</task>
     </help>
   </project>
 
@@ -945,9 +1274,9 @@
 	(foo -&gt; UTF-32) are compatible with GNU but the reverse ones
 	are not so accurate because of GNU's advanced transliteration.
 	Some extra encodings have also been added.  There are two modules,
-	which segfault, they need some debugging.  I can keep working on this
+	which segfault; they need some debugging.  I can keep working on this
 	project as part of my BSc thesis, so I hope to be able to solve
-	the remaining issues.  An improved GNU compatibility is also very
+	the remaining issues.  Improved GNU compatibility is also very
 	desired (extra command line options for iconv(1), iconvctl(),
 	private interfaces, etc.).</p>
     </body>
@@ -968,7 +1297,7 @@
   </project>
 
   <project cat="soc">
-    <title>Ext2fs Status report (Summer of Code 2009)</title> 
+    <title>Ext2fs Status report (Summer of Code 2009)</title>
 
     <contact>
       <person>
@@ -1048,7 +1377,7 @@
       <p>In the last months, we have not added new translations, although we
 	have been working on the existing ones to have them updated.  We need
 	more translators and volunteers to keep the amount of the translated
-	documentation growing, so feel free to contribute, every line of
+	documentation growing, so feel free to contribute.  Every line of
 	submission or feedback is appreciated and highly welcome.</p>
 
       <p>If you want to join our work, please read the <a
@@ -1111,7 +1440,6 @@
 	existing translations have not been updated, though.  We need
 	more human resources to keep up with the work and keep the
 	translations up-to-date.</p>
-
     </body>
 
     <help>
@@ -1121,8 +1449,8 @@
     </help>
   </project>
 
-  <project cat='bin'>
-    <title>BSD-licensed text-processing tools</title>
+  <project cat='soc'>
+    <title>BSD-licensed text-processing tools (Summer of Code 2008)</title>
 
     <contact>
       <person>
@@ -1141,12 +1469,13 @@
 
     <body>
       <p>This project was started as part of Google Summer of Code 2008 but
-	there is still an ongoing work to complete some missing parts.
+	there is still a bit of work to complete some missing parts.
 	The BSD-licensed grep implementation is feature-complete and
-	has a good level of GNU compatibility.  The only concern is the
+	has a good level of GNU compatibility.  Our only current concern about
+	the BSD-licensed version is to improve its
 	performance.  The GNU variant is much more complex, has about
 	8 KSLOC, while BSD grep is tiny, has only 1.5 KSLOC.  GNU uses
-	some shortcuts and optimizations to trick out the regex library,
+	some shortcuts and optimizations to speed-up calls to the regex library;
 	that is why it is significantly faster.  My point of view is that
 	such optimizations must be implemented in the regex library,
 	keeping the dependent utilities clean and easy to read.  BSD
@@ -1173,7 +1502,6 @@
       <p>The bc/dc utilities have been ported from OpenBSD.  They pass
 	OpenBSD's and GNU's regression tests but they arrived too late to
 	catch 8.X, so they will go to HEAD after the release.</p>
-
     </body>
 
     <help>
@@ -1186,6 +1514,83 @@
   </project>
 
   <project cat='net'>
+    <title>Network Stack Virtualization</title>
+
+    <contact>
+      <person>
+	<name>
+	  <given>Bjoern A.</given>
+	  <common>Zeeb</common>
+	</name>
+	<email>bz@FreeBSD.ORG</email>
+      </person>
+      <person>
+	<name>
+	  <given>Marko</given>
+	  <common>Zec</common>
+	</name>
+	<email>zec@FreeBSD.ORG</email>
+      </person>
+      <person>
+	<name>
+	  <given>Robert</given>
+	  <common>Watson</common>
+	</name>
+	<email>rwatson@FreeBSD.ORG</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="http://wiki.freebsd.org/Image">Wiki VImage overview
+	page (incl. TODO).</url>
+      <url href="http://wiki.freebsd.org/200909DevSummit">FreeBSD
+	Developer Summit, 2009, Cambridge, UK.</url>
+    </links>
+
+    <body>
+      <p>The network stack virtualization project aims at extending the
+	FreeBSD kernel to maintain multiple independent instances of
+	networking state.  This allows for networking independence
+	between jail environment, each maintaining its private network
+	interfaces, IPv4 and IPv6 network and port address space, routing
+	tables, IPSec configuration, firewalls, and more.</p>
+
+      <p>During the last months the remaining pieces of the VIMAGE work
+	were merged by Marko, Julian and Bjoern.  Robert Watson developed
+	a vnet allocator to overcome ABI issues.  Jamie Gritton merged
+	his hierachical jail framework that now also is the management
+	interface for virtual network stacks.</p>
+
+      <p>During the FreeBSD Developer Summit that took place at
+	EuroBSDCon 2009 in Cambridge, UK, people virtualized more code.
+	As a result SCTP and another accept filter were virtualized and
+	more people became familiar with the design of VImage and the underlying concepts.
+	Finally getting more hands involved was a crucial first step for
+	the long term success of kernel virtualization.</p>
+
+      <p>The next steps will be to finish the network stack
+	virtualization, generalize the allocator framework before
+	thinking of virtualizing further subsystems and to update the related
+	documentation.  Along with that a proper jail management
+	framework will be worked on.  Long term goals, amongst others,
+	will be to virtualize more subsystems like SYS-V IPC, better
+	privilege handling, and resource limits.</p>
+
+      <p>In the upcoming FreeBSD 8.0 Release, vnets are treated as an
+	experimental feature.  As a result, they are not yet recommended for use in
+	production environments.  There was lots of time spent to
+	finalize the infrastructure for vnets though, so that further
+	changes can be merged and we are aiming to have things
+	production ready for 8.2.</p>
+
+      <p>In case you want to help to achieve this goal, feel free to
+	contact us and support or help virtualizing outstanding parts
+	like two firewalls, appletalk, netipx, ... as well as generating

>>> TRUNCATED FOR MAIL (1000 lines) <<<