[Debian-NP-Commits] r168 - trunk/docs/report/report-docbook
Benjamin Hill
debian-np-devel@lists.alioth.debian.org
Mon, 12 Jul 2004 18:40:40 -0600
Author: mako
Date: Mon Jul 12 18:40:40 2004
New Revision: 168
Modified:
trunk/docs/report/report-docbook/accomplishments.xml
Log:
Fixed errors and bugs in the docbook formatting.
Modified: trunk/docs/report/report-docbook/accomplishments.xml
==============================================================================
--- trunk/docs/report/report-docbook/accomplishments.xml (original)
+++ trunk/docs/report/report-docbook/accomplishments.xml Mon Jul 12 18:40:40 2004
@@ -1,169 +1,176 @@
<?xml version="1.0" encoding='UTF-8'?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "docbookx.dtd">
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "docbookx.dtd">
-<sect1>
+<appendix>
<title>Accomplishments</title>
<para>On review of our accomplishments over the week, it is nothing
- short of impressive, this is a testament to the drive and work ethic
- of the people involved. Not only did we accomplish a great many
- technical feats, we also were able to organize our development work,
- learn many of the techniques of the internals of Debian, network with
- many developers, and develop the in-person social connections that
- make working together over vast distances remotely possible. All of
- this would have been extremely difficult if we were not together in
- person, the social connections that were made are difficult to
- document, but their worth cannot be overstated.</para>
+ short of impressive, this is a testament to the drive and work ethic
+ of the people involved. Not only did we accomplish a great many
+ technical feats, we also were able to organize our development work,
+ learn many of the techniques of the internals of Debian, network
+ with many developers, and develop the in-person social connections
+ that make working together over vast distances remotely possible.
+ All of this would have been extremely difficult if we were not
+ together in person, the social connections that were made are
+ difficult to document, but their worth cannot be overstated.</para>
<para>Most of what we were able to do, from making a specification
- for a Server version of Debian-NP, to creating the installer modules,
- to putting together our development environment, strategizing on
- collaboration methods, to enhancing the CDD infrastructure,
- significantly shape the future of Debian NP development.</para>
-
- <sect2>
- <title>Technical Accomplishments</title>
-
- <para>During the week that Debian-NP was able to spend together in
- Porto Alegre at Debconf4 we were able to accomplish a notable
- amount of technical advancements. We arrived in Porto Alegre with
- vague ideas, half-starts, and many divergences and reduplication
- of effort. We left with a technical framework, including agreed
- upon standards, a collaborative development environment and tools,
- an awareness of the next steps and a singular unifying vision.</para>
- </sect2>
+ for a Server version of Debian-NP, to creating the installer
+ modules, to putting together our development environment,
+ strategizing on collaboration methods, to enhancing the CDD
+ infrastructure, significantly shape the future of Debian NP
+ development.</para>
+
+ <simplesect>
+ <title>Technical Accomplishments</title>
+
+ <para>During the week that Debian-NP was able to spend together in
+ Porto Alegre at Debconf4 we were able to accomplish a notable
+ amount of technical advancements. We arrived in Porto Alegre with
+ vague ideas, half-starts, and many divergences and reduplication of
+ effort. We left with a technical framework, including agreed upon
+ standards, a collaborative development environment and tools, an
+ awareness of the next steps and a singular unifying vision.</para>
+ </simplesect>
- <sect2>
- <title>CDD Infrastructure adoption/improvements</title>
+ <simplesect>
+ <title>CDD Infrastructure adoption/improvements</title>
- <para>We were able to integrate the Debian-NP development into
- the CDD framework, while at the same time enhancing the CDD
- project overall. During the week we familiarized the whole group
- with the CDD framework, and focused on integrating Debian-NP
- into that framework while pushing out revisions and improvements
- to the CDD group, including an enhanced CDD infrastructure
- design. For a full detailed report on the CDD enhancements and
- work that we were able to complete over the week, please see the
- Appendix D: Customized Debian Distributions (CDD).</para>
+ <para>We were able to integrate the Debian-NP development into the
+ CDD framework, while at the same time enhancing the CDD project
+ overall. During the week we familiarized the whole group with the
+ CDD framework, and focused on integrating Debian-NP into that
+ framework while pushing out revisions and improvements to the CDD
+ group, including an enhanced CDD infrastructure design. For a full
+ detailed report on the CDD enhancements and work that we were able
+ to complete over the week, please see the Appendix D: Customized
+ Debian Distributions (CDD).</para>
- </sect2>
+ </simplesect>
- <sect2>
- <title>Installer success</title>
+ <simplesect>
+ <title>Installer success</title>
<para>We made remarkable progress in the short period that we were
- together in completing an installer for Debian-NP and the tools
- needed to ease and enhance this work. Through our proximity to
- Skolelinux developers, the Debian Installer developers and the
- developers who have worked on an installer for Debian-BR we were
- able to overcome technical hurdles easier. In the end we not only
- created an installer for Debian-NP as well as a CD installer
- framework but we were also able to improve the packages that aid
- in the creation of installation CDs, so all groups who create CDDs
- will benefit from our work. We are excited with the achievement of
- a beta bootable Debian-NP CD that has an installer built-in, and
- we now have the base to work with to improve in a modular fashion
- the installer and the methods for creating a bootable installation
- Debian-NP. Please see Appendix E: Debian-NP Installer for the full
- details of our hard work.</para>
- </sect2>
+ together in completing an installer for Debian-NP and the tools
+ needed to ease and enhance this work. Through our proximity to
+ Skolelinux developers, the Debian Installer developers and the
+ developers who have worked on an installer for Debian-BR we were
+ able to overcome technical hurdles easier. In the end we not only
+ created an installer for Debian-NP as well as a CD installer
+ framework but we were also able to improve the packages that aid in
+ the creation of installation CDs, so all groups who create CDDs
+ will benefit from our work. We are excited with the achievement of
+ a beta bootable Debian-NP CD that has an installer built-in, and we
+ now have the base to work with to improve in a modular fashion the
+ installer and the methods for creating a bootable installation
+ Debian-NP. Please see Appendix E: Debian-NP Installer for the full
+ details of our hard work.</para>
+ </simplesect>
- <sect2>
+ <simplesect>
<title>Uniform Schema</title>
<para>An exciting accomplishment that came out of our meeting was
-the result of the coming together of five different groups who have
-encountered similar user management challenges and have all
-individually researched solutions and come up with very similar
-results. At Debconf, we were able to harmonize our work in a
-cross-organizational security and permission framework, resulting in a
-uniform LDAP schema and strong beginnings on a fully configured LDAP
-meta-package that can be used for the Debian-NP server. This will
-allow us to move forward on designing a LDAP management tool to
-provide an abstracted user management administration and user
-configuration tool. The realization that we have been working
-separately on the same problems and coming to the same conclusions
-showed us how we should and can be collaborating together to save
-ourselves time and effort and benefit from each other's work.</para>
- </sect2>
+ the result of the coming together of five different groups who have
+ encountered similar user management challenges and have all
+ individually researched solutions and come up with very similar
+ results. At Debconf, we were able to harmonize our work in a
+ cross-organizational security and permission framework, resulting
+ in a uniform LDAP schema and strong beginnings on a fully
+ configured LDAP meta-package that can be used for the Debian-NP
+ server. This will allow us to move forward on designing a LDAP
+ management tool to provide an abstracted user management
+ administration and user configuration tool. The realization that we
+ have been working separately on the same problems and coming to the
+ same conclusions showed us how we should and can be collaborating
+ together to save ourselves time and effort and benefit from each
+ other's work.</para>
+ </simplesect>
- <sect2>
+ <simplesect>
<title>Mail server meta-package</title>
- <para>Building on the LDAP work we were able to also create a mail-server
-meta-package which is tied to the LDAP schema mentioned above. This
-meta-package is the mail-server component of the Debian-NP Server. We
-were able to draw on our years of experience managing high-traffic
-mail-server environments and bring together our various configurations
-into one configuration that we can all work on enhancing. This
-mail-server meta-package not only installs the mail server itself, but
-the spam and virus filtering that is part and parcel of a mail server
-on the Internet and also includes automatic SSL certificate generation
-for encrypted mail communications.</para>
- </sect2>
+ <para>Building on the LDAP work we were able to also create a
+ mail-server meta-package which is tied to the LDAP schema mentioned
+ above. This meta-package is the mail-server component of the
+ Debian-NP Server. We were able to draw on our years of experience
+ managing high-traffic mail-server environments and bring together
+ our various configurations into one configuration that we can all
+ work on enhancing. This mail-server meta-package not only installs
+ the mail server itself, but the spam and virus filtering that is
+ part and parcel of a mail server on the Internet and also includes
+ automatic SSL certificate generation for encrypted mail
+ communications.</para>
+ </simplesect>
- <sect2>
+ <simplesect>
<title>Other technical achievements</title>
+
<para>As if these were not enough, our team tirelessly worked on
-resolving many other technical challenges that will aid us in our
-future work. We experimented with debtags as an alternative automatic
-package selection methodology; we absorbed various relevant
-technologies such as debconf (the package configuration utility),
-cfengine, debian-installer, etc.; there was also many significant
-improvements to the Lessdisks LTSP package (packages were moved to be
-policy compliant, a 2.6 kernel version was generated, and the
-integration of Lessdisks into a LAN server module and into the
-installer was discussed and experimented with); the Free Geek Freekbox
-distribution was advanced to a more modern version and it was
-investigated how it could be merged in with the similar work being
-done at Praksys into a shared effort in a Debian-NP Workstation
-component.</par>
- </sect2>
+ resolving many other technical challenges that will aid us in our
+ future work. We experimented with debtags as an alternative
+ automatic package selection methodology; we absorbed various
+ relevant technologies such as debconf (the package configuration
+ utility), cfengine, debian-installer, etc.; there was also many
+ significant improvements to the Lessdisks LTSP package (packages
+ were moved to be policy compliant, a 2.6 kernel version was
+ generated, and the integration of Lessdisks into a LAN server
+ module and into the installer was discussed and experimented with);
+ the Free Geek Freekbox distribution was advanced to a more modern
+ version and it was investigated how it could be merged in with the
+ similar work being done at Praksys into a shared effort in a
+ Debian-NP Workstation component.</para>
+
+ </simplesect>
- <sect3>
+ <simplesect>
<title>Organizational Accomplishments</title>
<para>We were also able to throughout the week to create the
-necessary organizational infrastructure to organize our development
-work and be able to better work together in the future. Debian-NP
-created a Subversion version control repository at Debconf4, learned
-how to use it and rapidly began populating it with our work, and
-organizing its layout. Over the course of less than a week, there were
-nearly 400 commitments made to the subversion repository with
-code-fragments, documentation, meta-package work, installer work, and
-organization of the repository. We left the conference with a method
-of continuing our collaborative in-person work through using
-Subversion, and an impressive feeling of initiative manifested in the
-repository's contents which we took home and continue to work
-with. See Appendix C: Development Environment for a complete overview
-of Subversion, our layout, and how it is used.</para>
+ necessary organizational infrastructure to organize our development
+ work and be able to better work together in the future. Debian-NP
+ created a Subversion version control repository at Debconf4,
+ learned how to use it and rapidly began populating it with our
+ work, and organizing its layout. Over the course of less than a
+ week, there were nearly 400 commitments made to the subversion
+ repository with code-fragments, documentation, meta-package work,
+ installer work, and organization of the repository. We left the
+ conference with a method of continuing our collaborative in-person
+ work through using Subversion, and an impressive feeling of
+ initiative manifested in the repository's contents which we took
+ home and continue to work with. See Appendix C: Development
+ Environment for a complete overview of Subversion, our layout, and
+ how it is used.</para>
<para>Not only was there progress in the construction of our
-development environment, but we also built a technical plan, and
-strategy on how to do package selection; created a virtual machine for
-testing the server version; and established a shared Debian archive
-upload queue and repository.</para>
- </sect3>
+ development environment, but we also built a technical plan, and
+ strategy on how to do package selection; created a virtual machine
+ for testing the server version; and established a shared Debian
+ archive upload queue and repository.</para>
+
+ </simplesect>
- <sect4>
- <title>Social Accomplishments<title>
+ <simplesect>
+ <title>Social Accomplishments</title>
<para>Not everything that we accomplished at Debconf4 was purely
- technical. It was important to us to build the interpersonal
- relationships and international social network through working
- together in person, rather on-line, and living and eating with
- others over the course of the week. We networked with many Debian
- developers, including Skolelinux developers (Petter), CDD
- architects (Jonas and Kalfa), Progeny, and the Debian-Installer
- team (Joey Hess, and the localization and translation teams). We
- participated in the geek ritual of PGP key-signing and attended
- workshops on ethics and the involvement of women in Debian. We
- also came up with our social specifications and a reasonably
- comprehensive list of different user types and the packages that
- they require. </para>
+ technical. It was important to us to build the interpersonal
+ relationships and international social network through working
+ together in person, rather on-line, and living and eating with
+ others over the course of the week. We networked with many Debian
+ developers, including Skolelinux developers (Petter), CDD
+ architects (Jonas and Kalfa), Progeny, and the Debian-Installer
+ team (Joey Hess, and the localization and translation teams). We
+ participated in the geek ritual of PGP key-signing and attended
+ workshops on ethics and the involvement of women in Debian. We
+ also came up with our social specifications and a reasonably
+ comprehensive list of different user types and the packages that
+ they require. </para>
- </sect4>
-</sect1>
+ </simplesect>
+</appendix>
<!-- Keep this comment at the end of the file