svn commit: r41575 - head/en_US.ISO8859-1/htdocs/news/status
Gabor Pali
pgj at FreeBSD.org
Thu May 9 13:39:39 UTC 2013
Author: pgj
Date: Thu May 9 13:39:38 2013
New Revision: 41575
URL: http://svnweb.freebsd.org/changeset/doc/41575
Log:
- Add the first quarterly status report of 2013. Note that it is not
yet linked to the web site, probably it will be done soon -- around the
same time when it is officially pbulished (i.e. this week).
Added:
head/en_US.ISO8859-1/htdocs/news/status/report-2013-01-2013-03.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 Thu May 9 09:21:26 2013 (r41574)
+++ head/en_US.ISO8859-1/htdocs/news/status/Makefile Thu May 9 13:39:38 2013 (r41575)
@@ -58,6 +58,7 @@ XMLDOCS+= report-2012-01-2012-03
XMLDOCS+= report-2012-04-2012-06
XMLDOCS+= report-2012-07-2012-09
XMLDOCS+= report-2012-10-2012-12
+XMLDOCS+= report-2013-01-2013-03
XSLT.DEFAULT= report.xsl
Added: head/en_US.ISO8859-1/htdocs/news/status/report-2013-01-2013-03.xml
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2013-01-2013-03.xml Thu May 9 13:39:38 2013 (r41575)
@@ -0,0 +1,1616 @@
+<?xml version="1.0" encoding="iso-8859-1" ?>
+<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" "http://www.FreeBSD.org/XML/www/share/xml/statusreport.dtd" >
+<!-- $FreeBSD$ -->
+<report>
+ <date>
+ <month>January-March</month>
+
+ <year>2013</year>
+ </date>
+
+ <section>
+ <title>Introduction</title>
+
+ <p>This report covers &os;-related projects between January and
+ March 2013. This is the first of four reports planned for 2013.</p>
+
+ <p>Highlights from this status report include the busy preparations
+ of 8.4-RELEASE, steady progress of several porting efforts, like
+ work on the &os; ports of xorg, GNOME, KDE, and Xfce, bringing
+ &os; to Cubieboard and Hackberry boards, development of ARM and
+ AMD GPU support, improving performance of UFS/FFS and callouts,
+ and introducing a multipath TCP implementation for the network
+ stack.</p>
+
+ <p>Thanks to all the reporters for the excellent work! This report
+ contains 30 entries and we hope you enjoy reading it.</p>
+
+ <p>The deadline for submissions covering the period between April
+ and June 2013 is July 14th, 2013.</p>
+ </section>
+
+ <category>
+ <name>proj</name>
+
+ <description>Projects</description>
+ </category>
+
+ <category>
+ <name>team</name>
+
+ <description>&os; Team Reports</description>
+ </category>
+
+ <category>
+ <name>kern</name>
+
+ <description>Kernel</description>
+ </category>
+
+ <category>
+ <name>docs</name>
+
+ <description>Documentation</description>
+ </category>
+
+ <category>
+ <name>arch</name>
+
+ <description>Architectures</description>
+ </category>
+
+ <category>
+ <name>ports</name>
+
+ <description>Ports</description>
+ </category>
+
+ <category>
+ <name>misc</name>
+
+ <description>Miscellaneous</description>
+ </category>
+
+ <project cat='team'>
+ <title>&os; Core Team</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Core Team</given>
+ </name>
+ <email>core at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links/>
+
+ <body>
+ <p>The Core Team approved using Google Analytics on the Project
+ web site to enable the Documentation Engineering Team to collect
+ statistics on its usage for better profiling.</p>
+
+ <p>Due to some debates around the political correctness of quotes
+ added for the fortune(6) utility, the corresponding data file
+ has been removed from the base system in -CURRENT.</p>
+
+ <p>In light of the security incident, the liaison role between the
+ Core Team and the Security Team has been restored, with Gavin
+ Atkinson assuming this role. The Core Team works hard on
+ resolving the current situation of the binary package building
+ cluster and the associated security problems in tight
+ cooperation with the Ports Management Team, Cluster
+ Administators, and the &os; Foundation Board. The <a
+ href="http://www.FreeBSD.org/news/2012-compromise.html">compromise page</a>
+ is kept updated on the results.</p>
+
+ <p>The &os; Project submitted an application for Google Summer of
+ Code this year again.</p>
+
+ <p>In the first quarter, the Core Team granted access for 2 new
+ committers and took 1 commit bit for safekeeping.</p>
+ </body>
+ </project>
+
+ <project cat='team'>
+ <title>&os; Port Managers</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Thomas</given>
+ <common>Abthorpe</common>
+ </name>
+ <email>portmgr-secretary at FreeBSD.org</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Port</given>
+ <common>Management Team</common>
+ </name>
+ <email>portmgr at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://www.FreeBSD.org/ports/"/>
+ <url href="http://www.freebsd.org/doc/en/articles/contributing-ports/"/>
+ <url href="http://portsmon.freebsd.org/"/>
+ <url href="http://www.freebsd.org/portmgr/"/>
+ <url href="http://blogs.freebsdish.org/portmgr/"/>
+ <url href="http://www.twitter.com/freebsd_portmgr/"/>
+ <url href="http://www.facebook.com/portmgr"/>
+ </links>
+
+ <body>
+ <p>The ports tree contains approximately 24,300 ports, while the
+ PR count still is close to 1600.</p>
+
+ <p>In the first quarter we added 4 new committers, took in 1
+ commit bit for safe keeping, and re-instated 1 commit bit.</p>
+
+ <p>In February, Mark Linimon (linimon) stepped down from his
+ duties in the team. Mark had been the longest serving member of
+ the team. Mark had spent many long hours refactoring and
+ documenting the portbuild software to ensure that pointyhat
+ services could be restored.</p>
+
+ <p>After a security review, redports.org was turned back on,
+ restoring Tinderbox services to contributors, along with post
+ commit QATs. In addition, pointyhat infrastructure had also
+ undergone a review and work begain on restoring the package
+ build system.</p>
+
+ <p>Erwin Lansing (erwin) and Martin Wilke (miwi) took on the
+ principle roles of getting the portbuild software intalled and
+ running on pointyhat. As a result of all their hard work,
+ portmgr@ was finally able to resume doing -exp runs, preparing
+ packages for the upcoming 8.4 release, as well as getting a set
+ of 9.1 packages retroactively prepared.</p>
+
+ <p>After many long years of being the defacto standard for the
+ Project, CVS support for the ports tree officially ended on
+ February 28.</p>
+
+ <p>The ports tree was tagged with <tt>RELEASE_7_EOL</tt>, to
+ coincide with the end of life for &os; 7.X.</p>
+
+ <p>Beat Gaetzi (beat) stepped down from his duties on portmgr@ in
+ March. Among his notable contributions, was the task of migrating
+ the Ports Tree from the old CVS repo to Subversion.</p>
+
+ <p>Bryan Drewery (bdrewery) joined the Ports Management team in
+ March, bringing with him his wealth of knowledge and skill from
+ maintaining portupgrade, portmaster, assisting with pkgng, as
+ well as co-developing poudriere.</p>
+ </body>
+
+ <help>
+ <task>Most ports PRs are assigned, we now need to focus on
+ testing, committing and closing.</task>
+ </help>
+ </project>
+
+ <project cat='docs'>
+ <title>The &os; Japanese Documentation Project</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Hiroki</given>
+ <common>Sato</common>
+ </name>
+ <email>hrs at FreeBSD.org</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Ryusuke</given>
+ <common>Suzuki</common>
+ </name>
+ <email>ryusuke at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://www.FreeBSD.org/ja/">Japanese &os; Web Page</url>
+ <url href="http://www.jp.FreeBSD.org/doc-jp/">The &os; Japanese Documentation Project Web Page</url>
+ </links>
+
+ <body>
+ <p>Web page (<tt>htdocs</tt>): Newsflash and some other updates in
+ the English version have been translated to keep them up-to-date.
+ Specifically, the release related contents were updated in this
+ period.</p>
+
+ <p>Books: &os; Handbook has constantly been updated since the last
+ report; particularly, "ports", "desktop" section were largely
+ updated. Some progress has been made in the
+ "advanced-networking" section, contributed by a new
+ translator.</p>
+
+ <p><q>Writing &os; Problem Reports</q> article is now in sync with
+ the English version.</p>
+ </body>
+
+ <help>
+ <task>Further translation work of outdated documents in
+ ja_JP.eucJP subtree.</task>
+ </help>
+ </project>
+
+ <project cat='arch'>
+ <title>&os; on Cubieboard</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Ganbold</given>
+ <common>Tsagaankhuu</common>
+ </name>
+ <email>ganbold at FreeBSD.org</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Oleksandr</given>
+ <common>Tymoshenko</common>
+ </name>
+ <email>gonzo at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links/>
+
+ <body>
+ <p>Initial support of Allwinner A10 SoC is committed to -CURRENT.
+ &os; is now running on boards such as Cubieboard, Hackberry and
+ it supports following peripherals:</p>
+
+ <ul>
+ <li>USB EHCI</li>
+ <li>GPIO</li>
+ </ul>
+ </body>
+
+ <help>
+ <task>Get EMAC Ethernet driver working. Need more help from
+ network driver experts.</task>
+ <task>Implement more drivers.</task>
+ </help>
+ </project>
+
+ <project cat='kern'>
+ <title>Multipath TCP (MPTCP) for &os;</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Nigel</given>
+ <common>Williams</common>
+ </name>
+ <email>njwilliams at swin.edu.au</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Lawrence</given>
+ <common>Stewart</common>
+ </name>
+ <email>lastewart at swin.edu.au</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Grenville</given>
+ <common>Armitage</common>
+ </name>
+ <email>garmitage at swin.edu.au</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://caia.swin.edu.au/urp/newtcp/mptcp/tools.html"/>
+ <url href="http://caia.swin.edu.au/newtcp/mptcp/"/>
+ <url href="http://caia.swin.edu.au/reports/130424A/CAIA-TR-130424A.pdf"/>
+ <url href="https://pub.allbsd.org/FreeBSD-snapshots/"/>
+ </links>
+
+ <body>
+ <p>We have been working to create a BSD-licensed implementation of
+ Multipath TCP — a set of TCP extensions that allow for
+ transparent multipath operation with multiple IP addresses as
+ specified in experimental RFC6824.</p>
+
+ <p>We made our first v0.1 public release on 2013-03-11 and
+ recently released v0.3 on 2013-04-16. The code is currently
+ considered to be of alpha quality. We are working towards
+ pushing the code into a &os; Subversion repository project
+ branch to continue the on-going development effort in a more
+ publicly accessible location. As part of this move, we hope to
+ begin releasing regular snapshot installer ISOs of the MPTCP
+ project branch courtesy of Hiroki Sato and the allbsd.org daily
+ snapshot infrastructure.</p>
+
+ <p>We are about to releas a CAIA technical report 130424A entitled
+ <q>Design Overview of Multipath TCP version 0.3 for
+ &os; 10</q> on 2013-04-24 which provides a high-level
+ design and architecture overview of the v0.3 code release.</p>
+
+ <p>Going forward, we expect to continue development and release
+ additional technical reports and academic papers covering topics
+ such as performance analysis and multipath congestion
+ control/scheduling.</p>
+ </body>
+
+ <help>
+ <task>The code is currently of alpha quality so we welcome all
+ testing feedback, but please familiarise yourself with the readme
+ file and "Known Limitations" section in particular before
+ jumping in.</task>
+ </help>
+ </project>
+
+ <project cat='kern'>
+ <title>TCP-AO Authentication Option</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>André</given>
+ <common>Oppermann</common>
+ </name>
+ <email>andre at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://svnweb.freebsd.org/base/user/andre/tcp-ao/">SVN branch</url>
+ </links>
+
+ <body>
+ <p>Work is under way to implement TCP-AO (TCP Authentication
+ Option) according to RFC5925 and RFC5926. TCP-AO is an
+ extension to TCP-MD5 signatures commonly used in routers to
+ secure BGP routing protocol sessions against spoofing attacks.
+ The work is under contract and sponsored by Juniper
+ Networks.</p>
+ </body>
+ </project>
+
+ <project cat='kern'>
+ <title>Atomic Close-on-exec</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Jilles</given>
+ <common>Tjoelker</common>
+ </name>
+ <email>jilles at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="https://wiki.freebsd.org/AtomicCloseOnExec"/>
+ </links>
+
+ <body>
+ <p>If threads or signal handlers call <tt>fork()</tt> and
+ <tt>exec()</tt>, file descriptors may be passed undesirably to
+ child processes, which may lead to hangs (if a pipe is not
+ closed), exceeding the file descriptor limit and security
+ problems (if the child process has lower privilege). One
+ solution is various new APIs that set the <q>close-on-exec</q>
+ flag atomically with allocating a file descriptor. Some
+ existing software will use the new features if present or will
+ even refuse to compile without them.</p>
+
+ <p>Various parts have been present for some time.</p>
+
+ <p>In first quarter of 2013, extensions to <tt>recvmsg()</tt>,
+ <tt>socket()</tt>, <tt>socketpair()</tt> and
+ <tt>posix_openpt()</tt> have been added.</p>
+ </body>
+ </project>
+
+ <project cat='misc'>
+ <title>BXR.SU — Super User's BSD Cross Reference</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Constantine A.</given>
+ <common>Murenin</common>
+ </name>
+ <email>cnst++ at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://bxr.su/">BXR.SU — Super User's BSD Cross Reference</url>
+ <url href="http://lists.freebsd.org/pipermail/freebsd-hackers/2013-April/042334.html"/>
+ </links>
+
+ <body>
+ <p>Super User's BSD Cross Reference (BXR.SU) is a new source-code
+ search engine that covers the complete kernel and non-gnu
+ userland source trees of &os;, NetBSD, OpenBSD and DragonFly
+ BSD.</p>
+
+ <p>BXR.SU is optimised to be very fast, has daily updates of all
+ the trees, and also acts as a deterministic URL shortener.</p>
+
+ <p>BXR.SU is based on an OpenGrok fork, but it is more than just
+ OpenGrok. We have fixed a number of annoyances, eliminated
+ features that just never worked right from the outright, and
+ provided integration with tools like CVSweb (including great
+ mirrors like allbsd.org), &os;'s ViewVC (SVN), as well as GitHub
+ and Gitweb from <tt>git.freebsd.your.org</tt>, plus a tad of
+ other improvements, including a complete rewrite of an mdoc
+ parser. Last, but definitely not least, is an extensive set of
+ nginx rewrite rules that makes it a breeze to use BXR.SU as a
+ deterministic URL compactor for referencing BSD source code.
+ For example, the <tt>http://bxr.su/f/kern/sched_ule.c</tt> URL
+ will automatically redirect to
+ <tt>http://bxr.su/FreeBSD/sys/kern/sched_ule.c</tt> through
+ nginx.</p>
+
+ <p>Note that according to the release schedule of BXR.SU, there is
+ no IPv4 glue until 2013-04-24; otherwise, the service is available
+ via both IPv4 and IPv6. See the 2013-04-01 announcement on the
+ freebsd-hackers mailing list for more details.</p>
+ </body>
+
+ <help>
+ <task>Find up-to-date git repositories (served with Gitweb) of
+ NetBSD and OpenBSD.</task>
+ <task>Find a Gitweb mirror of &os; that is faster than GitHub and
+ Gitorious.</task>
+ </help>
+ </project>
+
+ <project cat='team'>
+ <title>&os; Postmaster Team</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>David</given>
+ <common>Wolfskill</common>
+ </name>
+ <email>postmaster at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links/>
+
+ <body>
+ <p>In the first quarter of 2013, the &os; Postmaster Team has
+ implemented the following items that may be interest of the
+ general public:</p>
+
+ <ul>
+ <li>Changes in configuration of Mailman-managed lists: allow to
+ accept the <tt>application/pkcs7-signature</tt> MIME type (in
+ addition to the <tt>application/x-pkcs7-signature</tt> MIME
+ type), thus permitting S/MIME signatures on list mail.</li>
+
+ <li>New lists: <tt>freebsd-ops-announce</tt> —
+ announcements of infrastructure issues, and <tt>freebsd-pkg</tt>
+ — discussion of binary package management and package
+ tools.</li>
+ </ul>
+ </body>
+ </project>
+
+ <project cat='team'>
+ <title>&os; Bugmeister Team</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Eitan</given>
+ <common>Adler</common>
+ </name>
+ <email>eadler at FreeBSD.org</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Gavin</given>
+ <common>Atkinson</common>
+ </name>
+ <email>gavin at FreeBSD.org</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Oleksandr</given>
+ <common>Tymoshenko</common>
+ </name>
+ <email>gonzo at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links/>
+
+ <body>
+ <p>The &os; Bugmeister Team are continuing to evaluate options for
+ alternate bug trackers and have narrowed their choices to two
+ possibilities: Bugzilla and roundup.</p>
+
+ <p>The number of non-ports PRs have remained relatively static over
+ the last three months, with as many coming in as being closed.
+ The number of ports PRs have increased recently, largely due to
+ the ports freeze for the upcoming 8.4-RELEASE.</p>
+
+ <p>The Bugmeister team continue work on trying to make the contents
+ of the GNATS PR database cleaner, more accessible and easier for
+ committers to find and resolve PRs, by tagging PRs to indicate
+ the areas involved, and by ensuring that there is sufficient
+ info within each PR to resolve each issue.</p>
+
+ <p>As always, anybody interested in helping out with the PR queue is
+ welcome to join us in <tt>#freebsd-bugbusters</tt> on EFnet. We
+ are always looking for additional help, whether your interests
+ lie in triaging incoming PRs, generating patches to resolve
+ existing problems, or simply helping with the database
+ housekeeping (identifying duplicate PRs, ones that have already
+ been resolved, etc). This is a great way of getting more
+ involved with &os;!</p>
+ </body>
+
+ <help>
+ <task>Finalize the decision of which new bug tracker to
+ use.</task>
+
+ <task>Get more users involved with triaging PRs as they come
+ in.</task>
+
+ <task>Assist committers with closing PRs.</task>
+ </help>
+ </project>
+
+ <project cat='kern'>
+ <title>callout(9) Improvements</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Davide</given>
+ <common>Italiano</common>
+ </name>
+ <email>davide at FreeBSD.org</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Alexander</given>
+ <common>Motin</common>
+ </name>
+ <email>mav at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://people.freebsd.org/~davide/asia/callout_paper.pdf"/>
+ <url href="http://people.freebsd.org/~davide/asia/calloutng.pdf"/>
+ <url href="http://svnweb.freebsd.org/base?view=revision&revision=247777"/>
+ </links>
+
+ <body>
+ <p>In &os;, timers are provided by the callout facility, which
+ allows to register a function with an argument to be called at
+ specified future time. The subsystem suffered of some problems,
+ such as the impossibility of handling high-resolution events or
+ its inherent periodic structure, which may lead to spurious
+ wakeups and higher power consumptions. Some consumers, such as
+ high-speed networking, VoIP and other real-time applications
+ need a better precision than the one currently allowed. Also,
+ especially with the ubiquity of laptops in the last years, the
+ energy wasted by interrupts waking CPUs from sleep may be a
+ sensitive factor. Recent changes in the subsystem addressed
+ those long standing issues as well as introduced a new
+ programming interface to take advantage of the new features.</p>
+ </body>
+
+ <help>
+ <task>Evaluating if it's worth to migrate any of the other
+ callout(9) consumers to the new interface.</task>
+ <task>Move callout consumers still using the legacy
+ timeout()/untimeout() interface to callout_*() in order to get
+ rid of redundant code and clean up KPI.</task>
+ </help>
+ </project>
+
+ <project cat='ports'>
+ <title>&os; Haskell Ports</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Gábor</given>
+ <common>Páli</common>
+ </name>
+ <email>pgj at FreeBSD.org</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Ashish</given>
+ <common>Shukla</common>
+ </name>
+ <email>ashish at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://wiki.freebsd.org/Haskell">&os; Haskell wiki page</url>
+ <url href="https://github.com/freebsd-haskell/freebsd-haskell/">&os; Haskell ports repository</url>
+ </links>
+
+ <body>
+ <p>We are proud to announce &os; Haskell Team has updated existing
+ ports to their latest stable versions. We also added number of
+ new ports, which brings the count of Haskell ports in &os; ports
+ tree to more than 400, featuring many popular software, e.g.
+ <tt>xmonad</tt>, <tt>git-annex</tt>, <tt>pandoc</tt> or various
+ web framework implementations. All of these updates will be
+ available as part of the upcoming 8.4-RELEASE. We also came to
+ know that Haskell ports are also being used successfully on
+ DragonFlyBSD's dports tree.</p>
+
+ <p>In our development repository, there was some optional support
+ added for LLVM-based code generation using the GHC LLVM backend.
+ This works mostly on &os; too, though some of the ports would
+ need fixing so it is still considered experimental.</p>
+ </body>
+
+ <help>
+ <task>Try to build GHC with clang (as system compiler).</task>
+ <task>Commit pending Haskell ports to the &os; ports tree.</task>
+ <task>Add more ports to the Ports Collection.</task>
+ </help>
+ </project>
+
+ <project cat='proj'>
+ <title>FreeNAS</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Alfred</given>
+ <common>Perlstein</common>
+ </name>
+ <email>alfred at FreeBSD.org</email>
+ </person>
+
+ <person>
+ <name>
+ <given>Josh</given>
+ <common>Paetzel</common>
+ </name>
+ <email>jpaetzel at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://www.FreeNAS.org/"/>
+ </links>
+
+ <body>
+ <p>FreeNAS 8.3.1-RELEASE-p2 will hit Sourceforge the second week
+ of April, and should end up as the last FreeNAS release based on
+ &os; 8.X It's currently the only Free Open Source NAS
+ product available with any form of ZFS encryption (provided by
+ GELI).</p>
+ </body>
+
+ <help>
+ <task>The team is hard at work on getting a &os; 9.X-based
+ release of FreeNAS ready. Currently there are several nightly
+ snapshots available.</task>
+
+ <task>Add HAST to the webinterface.</task>
+
+ <task>Migrate to NFSv4.</task>
+
+ <task>Integrate foundation sponsored kernel iSCSI target.</task>
+ </help>
+ </project>
+
+ <project cat='docs'>
+ <title>Improving the Documentation Project Infrastructre</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Gábor</given>
+ <common>Kövesdán</common>
+ </name>
+ <email>gabor at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://svnweb.freebsd.org/doc/projects/xml-tools/">The xml-tools branch</url>
+ </links>
+
+ <body>
+ <p>There is an ongoing work to improve the documentation
+ infrastructure and modernize our documentation toolchain. The
+ work can be found in the xml-tools branch and is very near to
+ completion. The improvements include the following:</p>
+
+ <ul>
+ <li>Upgrade to DocBook 4.5.</li>
+ <li>Use XSLT instead of DSSSL to render XHTML-based output.</li>
+ <li>Generate PDF from PS and simplify image processing.</li>
+ <li>Fix make lint and validate the whole documentation set.</li>
+ <li>Fix rendering of TOC elements.</li>
+ <li>Fix misused link elements that resulted in a corrupt
+ rendering.</li>
+ <li>Use more human-friendly publication data and release info
+ rendering.</li>
+ <li>Add support for XInclude in DocBook documents.</li>
+ <li>Add support for profiling with attributes.</li>
+ <li>Add support for Schematron constraints.</li>
+ <li>Add experimental epub support.</li>
+ <li>Add experimental support for XSL-FO-based printed
+ output.</li>
+ <li>Clean up obsolete SGML constructs.</li>
+ <li>Clean up catalogs.</li>
+ <li>Drop HTML Tidy since it is not needed any more.</li>
+ </ul>
+
+ <p>The changes eliminate some dependencies and switch the doc
+ repository to a real XML toolchain with proper validation and
+ more advanced rendering tools. The only exceptions are Jade and
+ the DSSSL stylesheets, which are still needed for printed
+ output.</p>
+ </body>
+
+ <help>
+ <task>Fix rendering problems with images in printed
+ formats.</task>
+
+ <task>Update the Documentation Primer to reflect changes.</task>
+ </help>
+ </project>
+
+ <project cat='ports'>
+ <title>GNOME/&os;</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>&os; GNOME team</given>
+ </name>
+ <email>gnome at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://www.freebsd.org/gnome"/>
+ <url href="http://www.freebsd.org/gnome/docs/develfaq.html"/>
+ <url href="http://www.marcuscom.com:8080/viewvc/viewvc.cgi/marcuscom"/>
+ <url href="https://github.com/jlmess77/mate-ports"/>
+ </links>
+
+ <body>
+ <p>The GNOME/&os; Team has recently merged glib 2.34, Gtk+ 2.24.17
+ and Gtk+ 3.6.4 into ports, the C++ bindings also have got
+ updates. In additional "low-level" GNOME ports received
+ updates, like libsoup, gobject-introspection, atk and vala for
+ example. The telepathy stack and empathy where also
+ updated.</p>
+
+ <p>The <tt>USE_GNOME</tt> macro has received support for
+ <tt>:run</tt> and <tt>:build</tt> targets thanks to Jeremy
+ Messenger (mezz). Currently only libxml2 and libxslt support
+ these targets.</p>
+
+ <p><tt>USE_GNOME=pkgconfig</tt> is being deprecated in favor of
+ <tt>USE_PKGCONFIG=build</tt>. The former also adds a run
+ dependency on pkg-config, which is not required. A first pass
+ was done to get rid of this in the glib update to 2.34. In
+ cooperation with the X11 Team the usage of
+ <tt>USE_GNOME=pkgconfig</tt> in X components will be removed.
+ After the fallout from this is handled and stranglers are
+ converted the <tt>USE_GNOME</tt> option will be removed.</p>
+
+ <p>In addition <tt>USE_GNOME=gnomehack</tt> is deprecated and
+ should not be used. Please replace it with
+ <tt>USES=pathfix</tt>.</p>
+
+ <p>The GNOME development repository has switched from CVS to SVN.
+ CVS will not get any more updates. Uses can get a new version
+ of the <a
+ href="http://marcuscom.com/downloads/marcusmerge">marcusmerge</a>
+ script that supports SVN from its home page, and should remove
+ the old CVS checkout "ports" dir.</p>
+
+ <ul>
+ <li>SVN anonymous root: <a href="svn://creme-brulee.marcuscom.com/"/>
+ or <a href="svn://sushi.marcuscom.com/"/> (IPv6).</li>
+ <li>ViewVC: <a href="http://www.marcuscom.com:8080/viewvc/viewvc.cgi/marcuscom"/></li>
+ </ul>
+
+ <p>On-going efforts:</p>
+
+ <ul>
+ <li><tt>glib</tt> 2.36, <tt>pango</tt> 1.34.0, <tt>gtk</tt>
+ 3.8.0 and <tt>gobject-introspection</tt> 1.36.0 where updated in
+ the GNOME development repository.</li>
+
+ <li>Gustau Perez i Querol stepped up and started work on
+ updating the old GNOME 3.4 ports to 3.6. At the moment of
+ writing these are not available in the GNOME development
+ repository just yet. For his efforts, he was awarded a &os;
+ GNOME team membership.</li>
+
+ <li>Jeremy Messenger (mezz) has completed Mate 1.6 which will be arriving in
+ ports near you when deemed stable enough.</li>
+ </ul>
+
+ <p>If you want to help with keeping the documentation updated or
+ helping out in other ways, even if it only parts for the
+ Glib/Gtk/GNOME stack you are interested in, please contact
+ us!</p>
+ </body>
+
+ <help>
+ <task>Update the FreeBSD.org/gnome website, in particular the developer
+ information about USE_GNOME, maybe put that section in the porters handbook
+ instead.</task>
+
+ <task>Merge more updated ports from MC to ports.</task>
+
+ <task>Testing latest Glib/Gtk releases with existing ports, and import
+ it into ports when it is ready.</task>
+
+ <task>After porting GNOME 3.6 run tests and fix bugs.</task>
+ </help>
+ </project>
+
+ <project cat='ports'>
+ <title>KDE/&os;</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>KDE</given>
+ <common>&os;</common>
+ </name>
+ <email>kde at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="http://FreeBSD.kde.org">KDE/&os; home page</url>
+ <url href="http://FreeBSD.kde.org/area51.php">area51</url>
+ </links>
+
+ <body>
+ <p>The KDE/&os; Team is very proud to have Schaich Alonso (aschai)
+ joining the team. Welcome!</p>
+
+ <p>The KDE/&os; Team have continued to improve the experience of
+ KDE software and Qt under &os;. The latest round of improvements
+ include:</p>
+
+ <ul>
+ <li>Fix problems establishing UDP connections.</li>
+ </ul>
+
+ <p>The team has also made many releases and upstreamed many fixes
+ and patches. The latest round of releases include:</p>
+
+ <ul>
+ <li>KDE SC: 4.9.5, 4.10.1 (ports)</li>
+ <li>Qt: 5.0.0 (area51) and 4.8.4 (ports)</li>
+ <li>PyQt: 4.9.6 (ports); QScintilla 2.7 (ports); SIP: 4.14.2 (area51) and 4.14.3 (ports)</li>
+ <li>KDevelop: 4.4.1 (ports); KDevPlatform: 1.4.1 (ports)</li>
+ <li>Calligra: 2.5.5, 2.6.2 (ports)</li>
+ <li>Amarok: 2.7.0</li>
+ <li>CMake: 2.8.10.2</li>
+ <li>Digikam (and KIPI-plugins): 3.1.0 (area51)</li>
+ <li>QtCreator: 4.6.1 (ports)</li>
+ <li>KDE Telepathy 0.6.0 (area51)</li>
+ <li>many smaller ports</li>
+ </ul>
+
+ <p>As a result — according to PortScout — we have 431
+ ports, of which 93.5% (from 91%) are up-to-date.</p>
+
+ <p>The team is always looking for more testers and porters so
+ please contact us and visit our home page.</p>
+ </body>
+
+ <help>
+ <task>Updating out-of-date ports, see PortScout for a list.</task>
+ </help>
+ </project>
+
+ <project cat='kern'>
+ <title>UFS/FFS Performance Work</title>
+
+ <contact>
+ <person>
+ <name>
+ <given>Kirk</given>
+ <common>McKusick</common>
+ </name>
+ <email>mckusick at mckusick.com</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="www.mckusick.com/publications/faster_fsck.pdf">Paper describing this work</url>
+ </links>
+
+ <body>
+ <p>Some work on the performance of UFS/FFS has been recently
+ committed to HEAD. The purpose of the corresponding change to
+ the FFS layout policy is to reduce the running time for a full
+ file system check. It also reduces the random access time for
+ large files and speeds up the traversal time for directory tree
+ walks.</p>
+
+ <p>The key idea is to reserve a small area in each cylinder group
+ immediately following the inode blocks for the use of metadata,
+ specifically indirect blocks and directory contents. The new
+ policy is to preferentially place metadata in the metadata area
+ and everything else in the blocks that follow the metadata
+ area.</p>
+
+ <p>The size of this area can be set when creating a filesystem
+ using <tt>newfs(8)</tt> or changed in an existing filesystem using
+ <tt>tunefs(8)</tt>. Both utilities use the <tt>-k
+ held-for-metadata-blocks</tt> option to specify the amount of
+ space to be held for metadata blocks in each cylinder group. By
+ default, <tt>newfs(8)</tt> sets this area to half of minfree
+ (typically 4% of the data area).</p>
+
+ <p>As with all layout policies, it only affect layouts of things
+ allocated after it is put in place. So these changes will
+ primarily be noticable on newly created file systems.</p>
+
+ <p>File system checks has been sped up by caching the cylinder
+ group maps in pass1 so that they do not need to be read again in
+ pass5. As this nearly doubles the memory requirement for
+ <tt>fsck(8)</tt>, the cache is thrown away if other memory needs
+ in <tt>fsck(8)</tt> would otherwise fail. Thus, the memory
+ footprint of <tt>fsck(8)</tt> remains unchanged in memory
+ constrained environments. This optimization will be evident on
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
More information about the svn-doc-all
mailing list