www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/server tasks.html


From: John Sullivan
Subject: www/server tasks.html
Date: Thu, 08 Feb 2007 19:55:50 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     John Sullivan <johnsu01>        07/02/08 19:55:50

Modified files:
        server         : tasks.html 

Log message:
        Remove ancient cruft and reformat to template.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/tasks.html?cvsroot=www&r1=1.33&r2=1.34

Patches:
Index: tasks.html
===================================================================
RCS file: /web/www/www/server/tasks.html,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -b -r1.33 -r1.34
--- tasks.html  26 Apr 2006 11:55:09 -0000      1.33
+++ tasks.html  8 Feb 2007 19:55:41 -0000       1.34
@@ -1,269 +1,210 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
-<TITLE>Tasks to Do for www.gnu.org - GNU Project - Free Software Foundation 
(FSF)</TITLE>
-<link rel="stylesheet" type="text/css" href="/gnu.css" />
-<LINK REV="made" HREF="mailto:address@hidden";>
-</HEAD>
-<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#1F00FF" ALINK="#FF0000" 
VLINK="#9900DD">
-
-<p>
-<a href="#translations">Translations</a> of this page.</p>
+<!--#include virtual="/server/header.html" -->
 
+<title>Tasks to Do for www.gnu.org - GNU Project - Free Software Foundation 
(FSF)</title>
 
-<H3>Tasks to Do for www.gnu.org</H3>
-<A HREF="/graphics/atypinggnu.html"><IMG SRC="/graphics/gnu-type-sm.jpg"
-   ALT=" [image of the typing GNU] "
-   WIDTH="137" HEIGHT="114"></A>
-<HR>
-<P>
+<!--#include virtual="/server/banner.html" -->
 
-Here are many possible tasks for improving the GNU web pages.
-If you would like to help with one of them, please e-mail
-<A HREF="mailto:address@hidden";>&lt;address@hidden&gt;</A>
-BEFORE you do any work on them.<P>
+<h2>Tasks to do for www.gnu.org</h2>
 
-<UL>
+<p>
+  Here are many possible tasks for improving the GNU web pages.
+  If you would like to help with one of them, please e-mail
+  <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>
+  BEFORE you do any work on them.<P>
+</p>
 
-  <LI>Investigate how www.gnu.org could provide better accessibility to
+<ul>
+  <li>Investigate how www.gnu.org could provide better accessibility to
       all regardless of disability.
-       <UL>
-        <LI>A good place to start is the
-             <A HREF="http://www.w3.org/WAI/";>Web Accessibility
-             Initiative (WAI)</A>.
-        <LI>Other resources on and off the web could also be checked.
-        <LI>People at or near MIT could check with MIT's
-             <A HREF="http://web.mit.edu/atic/www/";>Adaptive Technology for
-             Information and Computing</A> in person.
-        <LI>People who have access to similar centers at other schools,
-             organizations, and companies could check with them.
-        <LI>Disabled users of the web could also be interviewed, and perhaps
-             even added to the <CODE>address@hidden</CODE>
-             team for this task and others.
-       </UL>
+  <ul>
+    <li>A good place to start is the
+    <a href="http://www.w3.org/WAI/";>Web Accessibility
+    Initiative (WAI)</a>.</li>
+    <li>Other resources on and off the web could also be checked.</li>
+    <li>People at or near MIT could check with MIT's
+    <a href="http://web.mit.edu/atic/www/";>Adaptive Technology for
+    Information and Computing</a> in person.</li>
+    <li>People who have access to similar centers at other schools,
+    organizations, and companies could check with them.</li>
+    <li>Disabled users of the web could also be interviewed, and perhaps
+    even added to the webmasters team for this task and others.</li>
+  </ul>
+  </li>
   <li>Improve the existing ht://dig search facility and/or install
-      additional search facilities for the FSF/GNU web site.  Coordinate with
-      Jonas Öberb, Loïc Dachary, and Bradley Kuhn on this matter.</li>
-
-<!-- Removed the link to manual-indexing.txt for the "email -->
-<!-- exchange" below.  The file never existed in the /server -->
-<!-- directory.  Anyone know where it is, so the link can be -->
-<!-- fixed? -->
+  additional search facilities for the FSF/GNU web site.</li>
+  <!-- Removed the link to manual-indexing.txt for the "email -->
+  <!-- exchange" below.  The file never existed in the /server -->
+  <!-- directory.  Anyone know where it is, so the link can be -->
+  <!-- fixed? -->
   <li>Set up manual indexing using the system proposed by Miloslav Nic.
       See the email exchange for more details on what is to be done.</li>
-
   <li>Find a way that the
       <code>fp:/gd/gnuorg/EventAndTravelInfo/announce-events.plx</code> script
        can make it so that our <a href="/server/whatsnew.html">What's New</a>
        page can list new events when they are added.  One simple way to do
       this is to have it simply email webmasters every time a new event is
-      added, and ask them to add it manually.  If you are interested in this
-      task, please write to <a
-      href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</li>
-  <LI>Turn the <a href="/copyleft/gpl-faq.html">GPL FAQ</a> from an HTML
-      document into a canonical XML format, that we can easily generate
-      HTML from.  One possibility would be to use DocBook, since it has
-      some tags for handling FAQ lists.  If you are interested in this
-      task, please write to <a
-      href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.  (This task
-       is currently awaiting someone to add <CODE>&lt;qanda&gt;</CODE>
-       tag support in
-      the DocBook to Texinfo translators.)</li>
-  <LI>On our <a href="/help/help.html">help page</a>:
-       <UL>
-        <LI>Expand the
-       <A HREF="/help/help.html#gnutasklist">entry</A> for the
-       <a href="/prep/tasks_toc.html">GNU Task List</a> by adding
-      the @chapter sections of the task list.  This would make it quicker for
-      people to go to various parts of the task list.  A script would
-      probably be needed that read in tasks.texi and modified the help
-      page accordingly.
-        <LI>Similarly, expand the
-             <A HREF="/help/help.html#savannahhelpwanted">entry</A>
-             to have links to the listings under each category on the
-             <a href="http://savannah.gnu.org/people/";>Savannah
-             Help Wanted</a> page.
-       </UL>
-       If you are interested in either task, please write to <a
-      href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</li>
-  <LI>Write web pages for GNU programs that lacks web pages on our
+  added, and ask them to add it manually.</li>
+  <li>Turn the <a href="/copyleft/gpl-faq.html">GPL FAQ</a> from an HTML
+  document into a canonical XML format, that we can easily generate HTML from.
+  One possibility would be to use DocBook, since it has some tags for handling
+  FAQ lists. (This task is currently awaiting someone to add
+  <code>&lt;qanda&gt;</code> tag support in the DocBook to Texinfo
+  translators.)</li>
+  <li>Write web pages for GNU programs that lacks web pages on our
       server or whose web pages are obsolete using our
-      <A HREF="/software/boilerplate_software.html">software boilerplate</A>
+  <a href="/software/boilerplate_software.html">software boilerplate</A>
       as a template. Also read our
-      <A HREF="/server/standards/README.software.html">software page 
standards</A>.</li>
+  <a href="/server/standards/README.software.html">software page 
standards</a>.</li>
   <li>Work on improving our
-       <A HREF="/server/sitemap.html">sitemap</A>.
-       <UL>
-        <LI>Design a better sitemap that helps people find all places on the
+  <a href="/server/sitemap.html">sitemap</a>.
+  <ul>
+    <li>Design a better sitemap that helps people find all places on the
       website easily.  The sitemap should highlight particularly important
       parts of sub-pages.  (For example, the philosophy listing on the site
       map should have under it links to some particularly useful essays on the
-      philosophy page).
-        <LI>Come up with several different ways of presenting the sitemap,
+    philosophy page).</li>
+    <li>Come up with several different ways of presenting the sitemap,
              that consider both the differences in
-             <UL>
-               <LI>how people perceive web pages, and
-               <LI>how people use the site.
-             </UL>
-        <LI>Also, the idea of creating a programatically generated sitemap
+    <ul>
+      <li>how people perceive web pages, and</li>
+      <li>how people use the site.</li>
+    </ul>
+    </li>
+    <li>Also, the idea of creating a programatically generated sitemap
              has been proposed; this would primarily be a tool to aid in
-             writing by hand a more easily navigated sitemap.
-       </UL>
-  <LI>Help
-      <a HREF="/server/standards/README.translations.html">translate
+    writing by hand a more easily navigated sitemap.</li>
+  </ul>
+  <li>Help
+  <a href="/server/standards/README.translations.html">translate
        GNU web pages</a> from English into other languages.
        You can either join an existing translation team,
-       or form a new one.
-  <LI>Remove JPEG artifacts
+  or form a new one.</li>
+  <li>Remove JPEG artifacts
       from all PNG pictures. You do this by removing "loose" pixels and
       turning them into 1bpp (in case of black/white drawings).</li>
-  <LI>Create new <A HREF="/graphics/graphics.html">graphics</A>
+  <li>Create new <A HREF="/graphics/graphics.html">graphics</A>
       for our web pages. We mostly want to have nicer drawings like the ones
       we already have and perhaps in more colors.</li>
-  <LI>We are looking for people to volunteer to convert documentation
+  <li>We are looking for people to volunteer to convert documentation
        from various formats to the
-       <A HREF="/software/texinfo/texinfo.html">Texinfo</A>
+  <a href="/software/texinfo/texinfo.html">Texinfo</a>
        format. This is something we need
       occasionally. We would like to have a list of people we could ask
       on these occasions. If you want to volunteer, please send mail to
-      <A HREF="mailto:address@hidden";>&lt;address@hidden&gt;</A>.</li>
-  <LI>Rewrite the various philosophy pages and bulletins in
-       <A HREF="/software/texinfo/texinfo.html">Texinfo</A>
+  <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</li>
+  <li>Rewrite the various philosophy pages and bulletins in
+  <a href="/software/texinfo/texinfo.html">Texinfo</a>
        and
       convert to HTML using texi2html.
       They could then be easily included in:
-      <UL>
-        <LI>the <A HREF="http://ftp.gnu.org/gnu/GNUinfo";>/gnu/GNUinfo</A>
+  <ul>
+    <li>the <a href="http://ftp.gnu.org/gnu/GNUinfo";>/gnu/GNUinfo</a>
              subdirectory of
-             <A HREF="http://ftp.gnu.org/";>ftp.gnu.org</A>
-        <LI>the etc/ subdirectory of the GNU Emacs distribution
-        <LI>in the GNU system's Info tree
-        <LI>other useful locations.
-      </UL></li>
-  <LI><A NAME="fun">in directory /fun/ include</A>
-       <UL>
-        <LI>cgi-bin scripts that
-             <UL>
-               <LI>conduct a dialog with GNU Emacs's doctor.el and
-                    convert it into HTML.
-               <LI>get a zippyism from GNU Emacs's yow.el and
-                    convert it into HTML.
-               <LI>feed
+    <a href="http://ftp.gnu.org/";>ftp.gnu.org</a></li>
+    <li>the etc/ subdirectory of the GNU Emacs distribution</li>
+    <li>in the GNU system's Info tree</li>
+    <li>other useful locations.</li>
+  </ul>
+  </li>
+  <li><a name="fun">in directory /fun/ include</a>
+  <ul>
+    <li>cgi-bin scripts that
+    <ul>
+      <li>conduct a dialog with GNU Emacs's doctor.el and
+      convert it into HTML.</li>
+      <li>get a zippyism from GNU Emacs's yow.el and
+      convert it into HTML.</li>
+      <li>feed
                     zippyisms to GNU Emacs's doctor and
-                    convert it into HTML.
-             </UL>
+      convert it into HTML.</li>
+    </ul>
 
-             <P>
-
-             Roland McGrath has done some of this on his
-
-             <A HREF="http://www.frob.com/~roland";>home pages</A>.
-             Ask him if you can copy his work over to
-             http://www.gnu.org
-
-             <P>
-
-             This would not work on mirror sites that don't have
-             GNU Emacs installed,
-             so it be good to have a link on the page to the page here
-             on http://www.gnu.org,  Something like:
-             <PRE>
-             If this didn't work on a GNU mirror site, please try it on
-             http://www.gnu.org.
-             </PRE>
-
-             <P>
-
-             Shell, PERL, and/or Java
-             implementations of yow and doctor might exist
-             or could be written and distributed from those pages.
-       </UL>
-  </LI>
-  <LI>
+    <p>
+      Roland McGrath has done some of this on his <a
+      href="http://www.frob.com/~roland";>home pages</a>. Ask him if you
+      can copy his work over to http://www.gnu.org.
+    </p>
+    </li>
+  </ul>
+  </li>
+  <li>
   Check all the web pages for well formedness, consistency with
-  our HTML style sheet, and webmaster guidelines.  Unfortunately,
-  there are an uncounted number of intermixing of standards: HTML
-  2.0 documents containing 3.2 formatting, HTML 4.01 or ISO HTML
-  documents containing XHTML formatting, and XHTML documents
-  containing HTML formatting.  All web pages need to be valid to
-  their specific DTD, (the <A href="http://validator.w3.org";>W3C
-  Validator</a> is a good place to start).  Please do not upgrade
-  &lsquo;valid&rsquo; pages, even if they are HTML 2.0: use your
-  time an energies to ensure the right standard is applied to
-  pages to ensure they are both valid, and the most easily
-  accessible to the public.
-  </LI>
-  <LI>
+    our HTML style sheet, and webmaster guidelines. All web pages need to be 
valid to
+    their specific DTD, (the <a href="http://validator.w3.org";>W3C
+    Validator</a> is a good place to start).  
+  </li>
+
+  <li>
   Help is needed 
-  <A href="/server/standards/README.webmastering.html#poldeadlink">repairing 
-  broken links</A>.  There are numerous 
-  <A href="/server/standards/README.webmastering.html#polsymlink">symlinks</A>,
+    <a href="/server/standards/README.webmastering.html#poldeadlink">repairing 
+    broken links</a>.  There are numerous 
+    <a 
href="/server/standards/README.webmastering.html#polsymlink">symlinks</a>,
   so please do not break these in your repair efforts.  Time and
   care is needed to track down broken links, and in most
   cases find suitable replacements.  Please ensure that our 
-  <A href="/server/standards/README.webmastering.html#poladdlink">linking</A>
-  <A href="/server/standards/README.webmastering.html#pollinking">policy</A> 
+    <a href="/server/standards/README.webmastering.html#poladdlink">linking</a>
+    <a href="/server/standards/README.webmastering.html#pollinking">policy</a> 
   is followed in finding replacements.  
-  </LI>
-</UL>
+  </li>
+</ul>
 
-<HR>
-
-<div class="translations">
-<p><a id="translations"></a>
-<b>Translations of this page</b>:<br />
-
-<!-- Please keep this list alphabetical, and in the original -->
-<!-- language if possible, otherwise default to English -->
-<!-- If you do not have it English, please comment what the -->
-<!-- English is.  If you add a new language here, please -->
-<!-- advise address@hidden and add it to -->
-<!--    - in /home/www/bin/nightly-vars either TAGSLANG or WEBLANG -->
-<!--    - in /home/www/html/server/standards/README.translations.html -->
-<!--      one of the lists under the section "Translations Underway" -->
-<!--    - if there is a translation team, you also have to add an alias -->
-<!--      to mail.gnu.org:/com/mailer/aliases -->
-<!-- Please also check you have the 2 letter language code right versus -->
-<!--     http://www.w3.org/WAI/ER/IG/ert/iso639.htm -->
-
-[
-  <a href="/server/tasks.html">English</a>
-| <a href="/server/tasks.es.html">Espa&ntilde;ol</a>   <!-- Spanish -->
-]
-</p>
 </div>
 
-<div class="copyright">
-<p>
-Return to the <a href="/home.html">GNU Project home page</a>.
-</p>
-
-<p>
-Please send FSF &amp; GNU inquiries to 
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
-There are also <a href="/home.html#ContactInfo">other ways to contact</a> 
-the FSF.
-<br />
-Please send broken links and other corrections (or suggestions) to
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
-</p>
-
-<p>
-Copyright (C) 1996, 1997, 1998, 2001, 2004, 2005, 2006 
-Free Software Foundation, Inc.,
-51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
-<br />
-Verbatim copying and distribution of this entire article is
-permitted in any medium, provided this notice is preserved.
-</p>
+<!--#include virtual="/server/footer.html" -->
 
-<p>
-Updated:
-<!-- timestamp start -->
-$Date: 2006/04/26 11:55:09 $ $Author: ramprasadb $
-<!-- timestamp end -->
-</p>
+<div id="footer">
+  <p>
+    Please send FSF &amp; GNU inquiries to 
+    <a href="mailto:address@hidden";><em>address@hidden</em></a>.
+    There are also <a href="http://www.fsf.org/about/contact.html";>other ways 
to contact</a> 
+    the FSF.
+    <br />
+    Please send broken links and other corrections (or suggestions) to
+    <a href="mailto:address@hidden";><em>address@hidden</em></a>.
+  </p>
+
+  <p>
+    Copyright &copy; 1996, 1997, 1998, 2001, 2004, 2005, 2006, 2007<br />
+    Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 
02110-1301, USA
+    <br />
+    Verbatim copying and distribution of this entire article is
+    permitted in any medium, provided this notice is preserved.
+  </p>
+
+  <p>
+    Updated:
+    <!-- timestamp start -->
+    $Date: 2007/02/08 19:55:41 $ $Author: johnsu01 $
+    <!-- timestamp end -->
+  </p>
+</div>
+<!-- All pages on the GNU web server should have the section about    -->
+<!-- verbatim copying.  Please do NOT remove this without talking     -->
+<!-- with the webmasters first. --> 
+<!-- Please make sure the copyright date is consistent with the document -->
+<!-- and that it is like this "2001, 2002" not this "2001-2002." -->
+
+<div id="translations">
+  <h4>Translations of this page</h4>
+
+  <!-- Please keep this list alphabetical, and in the original -->
+  <!-- language if possible, otherwise default to English -->
+  <!-- If you do not have it English, please comment what the -->
+  <!-- English is.  If you add a new language here, please -->
+  <!-- advise address@hidden and add it to -->
+  <!--    - in /home/www/bin/nightly-vars either TAGSLANG or WEBLANG -->
+  <!--    - in /home/www/html/server/standards/README.translations.html -->
+  <!--      one of the lists under the section "Translations Underway" -->
+  <!--    - if there is a translation team, you also have to add an alias -->
+  <!--      to mail.gnu.org:/com/mailer/aliases -->
+  <!-- Please also check you have the 2 letter language code right versus -->
+  <!--     http://www.w3.org/WAI/ER/IG/ert/iso639.htm -->
+
+  <ul class="translations-list">
+    <li><a href="/server/tasks.html">English</a></li>
+    <li><a href="/server/tasks.es.html">Espa&#x00f1;ol</a> <!-- Spanish 
--></li>
+  </ul>
+</div>
 </div>
-
 </body>
 </html>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]