Reintroduce intentional informality in the last Python task. Other

assorted fixes in the rest of the document, including spelling and
titles.
This commit is contained in:
Warren Block 2014-07-14 21:40:50 +00:00
parent 34ca01b15d
commit d6fe48e405
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=45294

View file

@ -132,7 +132,7 @@
</project>
<project cat='proj'>
<title>RPC/NFS and CTL/iSCSI performance optimizations.</title>
<title>RPC/NFS and CTL/iSCSI Performance Optimizations</title>
<contact>
<person>
@ -267,7 +267,7 @@
</links>
<body>
<p>The <tt>vt(4)</tt> (a.k.a. <tt>Newcons</tt>) project provides
<p>The <tt>vt(4)</tt> (aka <tt>Newcons</tt>) project provides
a replacement for the legacy <tt>syscons</tt> system console.
It brings a number of improvements, including better
integration with graphics modes and broader character set
@ -366,7 +366,7 @@
</project>
<project cat='proj'>
<title>QEMU bsd-user enabled ports building</title>
<title>QEMU <tt>bsd-user</tt>-Enabled Ports Building</title>
<contact>
<person>
@ -562,8 +562,8 @@
<task>More tasks can be found on the team's wiki page (see
links).</task>
<task>To get involved, interested people can say hello on IRC
and let us know their areas of interest!</task>
<task>To get involved, come and say "hi" on IRC and let us know
what you are interested in!</task>
</help>
</project>
@ -661,26 +661,26 @@
<p>In May, a new release policy was published as well as being
presented at the BSDCan developer conference by John Baldwin.
The idea is that each major release branch (eg. 10.x) is
guarranteed to be supported for at least five years, but
individual point releases on each branch (eg. 10.0-RELEASE)
The idea is that each major release branch (for example, 10.X) is
guaranteed to be supported for at least five years, but
individual point releases on each branch, like 10.0-RELEASE,
will be issued at regular intervals and only the latest point
release will be supported.</p>
<p>Another significant change did not receive approval. When
the change to the Bylaws reforming the core team election
process was put to the vote of all &os; developers it failed
process was put to the vote of all &os; developers, it failed
to reach a quorum.</p>
<p>June saw the culmination of a long running project to replace
the project's bug tracking system. As of 3rd June the &os;
the project's bug tracking system. As of June 3, the &os;
project has switched to Bugzilla as its bug tracking system.
All of the history of Gnats PRs has been preserved, so there
All of the history of GNATS PRs has been preserved, so there
is no need to re-open old tickets. Work is still going on to
replicate some of the integration tweaks that had been applied
to Gnats, but all necessary functionality has been implemented
to GNATS, but all necessary functionality has been implemented
and the project is already seeing the benefits of the new
capabilities bought by Bugzilla.</p>
capabilities brought by Bugzilla.</p>
<p>An election to select core members for the next two year term
of office took place during this period. We would like to
@ -688,7 +688,7 @@
The new core team provides continuity with previous core
teams: about half are incumbents from the previous team, and
several former core team members have returned after a hiatus.
core now includes two members of the &os; Foundation board and
Core now includes two members of the &os; Foundation board and
one other Foundation staff member, aiding greater coordination
at the top level of the project. At the same time the
core-secretary role was passed on to a new volunteer.</p>
@ -703,7 +703,7 @@
</project>
<project cat='misc'>
<title>&os; host support for OpenStack and OpenContrail.</title>
<title>&os; Host Support for OpenStack and OpenContrail</title>
<contact>
<person>
@ -909,7 +909,7 @@
</project>
<project cat='kern'>
<title>SDIO driver</title>
<title>SDIO Driver</title>
<contact>
<person>
@ -945,8 +945,8 @@
<p>WiFi driver is able to load a firmware onto the card and
initialize it. A rewrite of the MMC stack as a transport
layer for CAM framework is in progress. This will allow to
utilize the well-tested CAM locking model and debug features.</p>
layer for CAM framework is in progress. This will allow
utilization of the well-tested CAM locking model and debug features.</p>
</body>
<help>
@ -1016,8 +1016,8 @@
</project>
<project cat='kern'>
<title>Running &os; as an application on top of Fiasco.OC
microkernel</title>
<title>Running &os; as an Application on Top of the Fiasco.OC
Microkernel</title>
<contact>
<person>
@ -1042,13 +1042,13 @@
provides a bare minimum of services to the applications
running on top of it, unlike traditional kernels that
incorporate a complex code like IP stacks and device drivers.
This allows to dramatically decrease the amount of code
This allows a dramatic decrease in the amount of code
running in the privileged mode of the CPU, achieving higher
security while still providing an acceptable level of
performance.</p>
<p>Running an operating system kernel on top of the microkernel
allows to leverage any software that was developed for that
allows leveraging any software that was developed for that
operating system. The OS kernel runs in user-mode side-by-side
with other microkernel applications such as real-time
components. Multiple OSes, each with their userland
@ -1059,7 +1059,7 @@
<p>The project aims to create a port of &os; to Fiasco.OC
microkernel, which is a high performance L4 microkernel
developed by TU Dresden. The existing ports of OpenBSD and
Linux are used as a reference. This will allow to use the
Linux are used as a reference. This will allow the use of
unique &os; features like ZFS in L4-based projects.</p>
</body>