Add reusable XML files (slides/simplified DocBook DTD) that can be

included by other presentation documents to rapidly generate or change
the content of a presentation based on this shared data.

Each of these files contains either a single <foil> slide, or a
selection of slides on the specified subject inside a <foilgroup>.  In
either case, the XML for your presentation (slides.xml) can simply
include a few slides of content for each file with :

<xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
  href="../common/what-is-freebsd.xml"/>

HTML and PDF output formats work now.  It should be feasible to output
OpenOffice XML and then import it into that application for final
presentation tweaks.
This commit is contained in:
Murray Stokely 2004-09-07 12:15:12 +00:00
parent e94633c940
commit 666f378e4f
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=22264
6 changed files with 199 additions and 0 deletions

View file

@ -0,0 +1,34 @@
<!-- $FreeBSD$ -->
<foilgroup id="freebsd-5.3">
<foil id="freebsd-5.3-general"><title>What's new in FreeBSD 5.3</title>
<itemizedlist>
<listitem>NDIS Binary Compatibility allows Windows XP network
device drivers to be used with FreeBSD.</listitem>
<listitem>IP Fast Forwarding for dramatic speedups in FreeBSD
based routers.</listitem>
<listitem>Continued locking and performance improvements to take
advanced of SMPng architecture.</listitem>
</itemizedlist>
</foil>
<foil id="freebsd-5.3-net"><title>FreeBSD 5.3 Network Changes</title>
<para>FreeBSD (i386) can use binary Ethernet and WLAN network
drivers written to the Windows XP NDIS 5.1 specification. Windows
drivers are turned into FreeBSD Kernel Loadable Modules (KLDs) with
the <command>ndisvt</command> command :</para>
<screen># ndiscvt -O -i neti557x.inf -s neti557x.sys \
-n intel0
# kldload intel0</screen>
<para>More information is available in ndis(4), ndisapi(9), and
ndiscvt(8). This functionality was written by Bill Paul.</para>
</foil>
</foilgroup>

View file

@ -0,0 +1,67 @@
<!-- $FreeBSD$ -->
<foilgroup id="freebsd-dev-model">
<foil id="freebsd-dev-model-general">
<title>FreeBSD Development Model</title>
<itemizedlist>
<listitem>FreeBSD development continues along two parallel
branches; FreeBSD-CURRENT and FreeBSD-STABLE.</listitem>
<listitem>FreeBSD-CURRENT is the main trunk of our CVS
repository. All new development should happen
here.</listitem>
<listitem>FreeBSD-STABLE is the branch from which major releases
are made. Changes enter this branch at a different pace, and
with the general assumption that they have been well tested by
our user community running -CURRENT.</listitem>
</itemizedlist>
</foil>
<foil id="freebsd-dev-model-release-diagram">
<title>FreeBSD Release Diagram</title>
<para>Chart from releng paper goes here.</para>
</foil>
<foil id="freebsd-dev-model-organization">
<title>FreeBSD Development Model</title>
<itemizedlist>
<listitem>Thousands of developers around the world contribute
code to FreeBSD.</listitem>
<listitem>Only the <quote>committers</quote> have write access
to the CVS repository.</listitem>
<listitem>324 total committers in FreeBSD (includs source,
documentation, and ports committers).</listitem>
<listitem>212 active committers to src/ in the last 12
months.</listitem>
<listitem>165 active committers to src/sys in the last 12
months.</listitem>
</itemizedlist>
</foil>
<foil id="freebsd-dev-model-bugs">
<title>FreeBSD Development Model</title>
<itemizedlist>
<listitem>Users and external developers should submit bug fixes,
enhancements, or problem reports with GNATS.</listitem>
<listitem>Online submission forms, send-pr command installed by
default on FreeBSD systems, etc.</listitem>
</itemizedlist>
</foil>
</foilgroup>

View file

@ -0,0 +1,20 @@
<!-- $FreeBSD$ -->
<foil id="freebsd-organization">
<title>FreeBSD Organization</title>
<itemizedlist>
<listitem>A number of committees with special responsibilities
have been created within the FreeBSD Project to ensure that
the project continues to move in a positive
direction.</listitem>
<listitem>The FreeBSD <emphasis>Core Team</emphasis> is a group
of 9 developers elected by the committers for 2 year
terms.</listitem>
<listitem>The FreeBSD <emphasis>Release Engineering
Team</emphasis> is a small group of developers responsible for
managing the release process.</listitem>
</itemizedlist>
</foil>

View file

@ -0,0 +1,24 @@
<!-- $FreeBSD$ -->
<foil><title>Recent Releases</title>
<itemizedlist>
<listitem>FreeBSD 4.X-STABLE continues incremental feature,
performance, stability development.
<itemizedlist>
<listitem>FreeBSD 4.9 (October, 2003)</listitem>
<listitem>FreeBSD 4.10 (May, 2004)</listitem>
</itemizedlist>
</listitem>
<listitem>FreeBSD 5.X-CURRENT continues higher risk development,
approaches -STABLE.
<itemizedlist>
<listitem>FreeBSD 5.0 (January, 2003)</listitem>
<listitem>FreeBSD 5.1 (June, 2003)</listitem>
<listitem>FreeBSD 5.2 (January, 2004)</listitem>
<listitem>FreeBSD 5.2.1 (February, 2004)</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</foil>

View file

@ -0,0 +1,30 @@
<!-- $FreeBSD$ -->
<foil id="freebsd-release-process-general">
<title>FreeBSD Release Process</title>
<itemizedlist>
<listitem><quote>Stable</quote> releases are made from the
-STABLE development branch at approximately 4 month
intervals.</listitem>
<listitem>Major new versions (3.0, 4.0, 5.0, etc..) are released
at much longer intervals when the main goals for that release
have been realized.
<itemizedlist>
<listitem>3.0 - October 1998</listitem>
<listitem>4.0 - March 2000</listitem>
<listitem>5.0 - January 2003</listitem>
</itemizedlist>
</listitem>
<listitem>In periods of transition, point releases from the
previous branch are still released while the next major
release branch stabilizes. (e.g., 4.8, 4.9, and 4.10 were
released after 5.0)</listitem>
</itemizedlist>
</foil>

View file

@ -0,0 +1,24 @@
<!-- $FreeBSD$ -->
<foil><title>What is FreeBSD?</title>
<itemizedlist>
<listitem>FreeBSD is a production-quality operating system derived
from BSD UNIX.
<itemizedlist>
<listitem>Widely deployed as a component, and in its own right.
<itemizedlist>
<listitem>Workstation, server, and high-end embedded
markets.</listitem>
</itemizedlist>
</listitem>
<listitem>Berkeley permits broad commercial re-use in open and
closed source products.</listitem>
<listitem>i386, ia64, amd64, sparc64, alpha</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</foil>