This commit fixes missing li tags, unescaped characters in URLS,
incorrect placement of p tags, and missing DOCTYPEs in the
gsoc directory, as reported by the html tidy tool.
$ tidy -q -e gsoc/2008final.html
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 23 column 1 - Warning: missing <li>
line 169 column 1 - Warning: inserting implicit <p>
line 51 column 1 - Warning: <a> escaping malformed URI reference
line 190 column 1 - Warning: <a> escaping malformed URI reference
line 14 column 1 - Warning: trimming empty <p>
line 23 column 1 - Warning: trimming empty <p>
line 23 column 1 - Warning: trimming empty <li>
line 169 column 1 - Warning: trimming empty <p>
$ tidy -q -e gsoc/2009final.html
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 322 column 8 - Warning: missing </a>
line 324 column 1 - Warning: discarding unexpected </a>
line 17 column 1 - Warning: trimming empty <p>
line 35 column 1 - Warning: trimming empty <p>
line 47 column 1 - Warning: trimming empty <p>
$ tidy -q -e gsoc/2009.html
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 322 column 8 - Warning: missing </a>
line 324 column 1 - Warning: discarding unexpected </a>
line 17 column 1 - Warning: trimming empty <p>
line 35 column 1 - Warning: trimming empty <p>
line 47 column 1 - Warning: trimming empty <p>
Change-Id: Id901d1b03355debaa9e41af5172dc1c1de464b42
Reviewed-on: https://gerrit.openafs.org/13552
Reviewed-by: Cheyenne Wills <cwills@sinenomine.net>
Reviewed-by: Stephan Wiesand <stephan.wiesand@desy.de>
Tested-by: Stephan Wiesand <stephan.wiesand@desy.de>
+<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Language" content="en-us">
<h1>OpenAFS Projects from Google Summer of Code 2008</h1>
<h2>Outcome</h2>
<p>OpenAFS applied for the second time to be part of the Google Summer of Code, and this year was accepted. Ultimately Google opted to fund 6 projects for OpenAFS; Two more were funded with the same rules using other money including that granted by Google to a sponsoring organization per student.
-<p>
+</p>
<ul>
<li><A HREF="#mmc">Microsoft Management Console Snap-ins, Client and Server</A></li>
<li><A HREF="#kafs">Implementing OpenAFS features into RedHat's kafs kernel module</A></li>
<li><A HREF="#discon">Read/Write Disconnected AFS</A></li>
<li><A HREF="#shellex">Windows Explorer Shell UI extension updates</A></li>
<li><A HREF="#winserv">OpenAFS servers for Windows</A></li>
-<p>
+
<li><A HREF="#website">Redesigning the OpenAFS project website</A></li>
<li><A HREF="#ptsext">Extensions for multiple authentication types to the OpenAFS ptserver</A></li>
<li><A HREF="#ports">Porting OpenAFS to new platforms</A></li>
should be configured using the Microsoft Management Console (MMC). This
project is to implement a MMC Add-on for the OpenAFS Cache Manager. </p>
<p>Mockups of a proposed MMC user interface can be found at
-<a href="http://www.secure-endpoints.com/openafs-windows-roadmap.html#client service mmc">
+<a href="http://www.secure-endpoints.com/openafs-windows-roadmap.html#client%20service%20mmc">
http://www.secure-endpoints.com/openafs-windows-roadmap.html#client service mmc</a>.
This project consists of multiple components that can be successfully
implemented one at a time. The successful completion of this project does
kernel and some implemented pioctls for the kAFS call are available.
<p>
The goal of this project would be to bring the Linux kernel kAFS client as close to feature-parity with the existing OpenAFS port as possible. Examples include:
+</p>
<ul>
<li>DNS AFSDB being able to obtain cell server location without using configuration files.</li>
<li>A common pioctl implementation between kafs and OpenAFS to allow sharing of userspace binaries.</li>
<li>A way for OpenAFS and kafs to be running on the same machine using different port numbers.</li>
<li>Complete the kafs callback interface.</li>
</ul>
-</p>
+
<p>Estimated difficulty: <i>moderate to hard</i></p>
<A NAME="winserv"><h3>Project: Updates AFS servers for Windows</h3></A>
<h4>Mentor: Jeffrey Altman</h4>
has the appropriate permissions. All in all, the user should not notice
that AFS is not a native part of the operating system and the user interface.</p>
<p>Mockups of proposals for the Explorer Shell extension can be found at
-<a href="http://www.secure-endpoints.com/openafs-windows-roadmap.html#shell extensions">
+<a href="http://www.secure-endpoints.com/openafs-windows-roadmap.html#shell%20extensions">
http://www.secure-endpoints.com/openafs-windows-roadmap.html#shell extensions</a>.
This project consists of multiple components that can be successfully
implemented one at a time. The successful completion of this project does
+<!DOCTYPE html>
<html>
<head>
IBM AFS commercial offering as of 1 November 2000. Since IBM released the
source code OpenAFS has thrived adding support for new platforms while enhancing
its overall performance, scalability and usability. </p>
-<p>
+
<h2>GSoC 2009</h2>
For 2009, OpenAFS has been granted 4 slots. The projects which we accepted for 2009 are:
<ol><li>
This project seeks to change the way the servers in the list are ordered based on network conditions between the client and the possible servers. Rx peer statistics can help provide information about these network conditions. Parts of these statistics can be used to indicate which servers are closest, proximity-wise, to the client as well as create an estimated throughput capacity for the server. These factors can be analyzed to represent performance between the cache manager client and the servers. This will allow for server prioritization based on the best performance of the server and the server's network connection, which subsequently can increase access times. This project will implement this prioritization on both Windows and Unix platforms, taking into account the statistics mechanisms. The Unix implementation will port relatively simply to other Unix implementations (AIX, HP-UX, etc.).
</li><li>
Project #4: Implementing OpenAFS features into the Linux kafs kernel module: kafs is a Linux implementation of the AFS protocols. While kafs has been maturing, many features contained in OpenAFS are still missing from kafs. This project aims to add some of those features.
-<p>
+
<ul><li>
DNS AFSDB support. Sharing the mechanism used by CIFS will be investigated.
</li><li>
</ul>
</li>
</ol>
-<p>
+
<h3>GSoC 2009 recruiting</h3>
<p>
It is now 2009, the world economy is collapsing, the U.S. dollar has regained
<p>More detail on this project can be found
<a href="http://www.openafs.org/pages/gsoc/acls.txt">here</a>.</p>
<h3>8. <a name="kafs">Implementing OpenAFS features into RedHat's kafs kernel
-module</h3>
-</a>
+module</a></h3>
+
<p>The goal of this project would be to bring the Linux kernel kAFS client as
close to feature-parity with the existing OpenAFS port as possible. Examples
include: </p>
+<!DOCTYPE html>
<html>
<head>
IBM AFS commercial offering as of 1 November 2000. Since IBM released the
source code OpenAFS has thrived adding support for new platforms while enhancing
its overall performance, scalability and usability. </p>
-<p>
+
<h2>GSoC 2009</h2>
For 2009, OpenAFS has been granted 4 slots. The projects which we accepted for 2009 are:
<ol><li>
This project seeks to change the way the servers in the list are ordered based on network conditions between the client and the possible servers. Rx peer statistics can help provide information about these network conditions. Parts of these statistics can be used to indicate which servers are closest, proximity-wise, to the client as well as create an estimated throughput capacity for the server. These factors can be analyzed to represent performance between the cache manager client and the servers. This will allow for server prioritization based on the best performance of the server and the server's network connection, which subsequently can increase access times. This project will implement this prioritization on both Windows and Unix platforms, taking into account the statistics mechanisms. The Unix implementation will port relatively simply to other Unix implementations (AIX, HP-UX, etc.).
</li><li>
Project #4: Implementing OpenAFS features into the Linux kafs kernel module: kafs is a Linux implementation of the AFS protocols. While kafs has been maturing, many features contained in OpenAFS are still missing from kafs. This project aims to add some of those features.
-<p>
+
<ul><li>
DNS AFSDB support. Sharing the mechanism used by CIFS will be investigated.
</li><li>
</ul>
</li>
</ol>
-<p>
+
<h3>GSoC 2009 recruiting</h3>
<p>
It is now 2009, the world economy is collapsing, the U.S. dollar has regained
<p>More detail on this project can be found
<a href="http://www.openafs.org/pages/gsoc/acls.txt">here</a>.</p>
<h3>8. <a name="kafs">Implementing OpenAFS features into RedHat's kafs kernel
-module</h3>
-</a>
+module</a></h3>
+
<p>The goal of this project would be to bring the Linux kernel kAFS client as
close to feature-parity with the existing OpenAFS port as possible. Examples
include: </p>
git://git.openafs.org / openafs-web.git / commitdiff