/server/tasks.html-diff

<!--#include virtual="/server/header.html" -->
<!-- Parent-Version: 1.77 1.98 -->
<!-- This page is derived from /server/standards/boilerplate.html -->
<title>Tasks to do for www.gnu.org
- GNU Project - Free Software Foundation</title>
<!--#include virtual="/server/po/tasks.translist" -->
<!--#include virtual="/server/banner.html" -->
<h2>Tasks to do for www.gnu.org</h2>

<p>
  Here are many possible

<p>This page used to list some important tasks for improving which we need help.
Please follow the GNU web pages.
  If you would like to help with one of them, please e-mail
  <a href="mailto:webmasters@gnu.org"><webmasters@gnu.org></a>
  BEFORE you do any work on them.
</p>

<h3 id="accessibility">Accessibility</h3>

<p>
  Investigate how www.gnu.org could provide better accessibility to
  all regardless of disability.
</p>
<ul>
  <li>A good place links 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 specific areas where they 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> been
moved.</p> 

<h3 id="conversions">Format Conversions</h3>

<ul>
  <li>We are looking for people to volunteer to convert documentation
  from various formats to the
  <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:gvc@gnu.org"><gvc@gnu.org></a>.</li>
  <li>Rewrite the various philosophy pages in
  <a href="/software/texinfo/texinfo.html">Texinfo</a>
  and
  convert id="accessibility">Accessibility</h3>

<p>Moved 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>
    subdirectory of <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>
</ul> 
href="/accessibility/accessibility.html#recommendations">Accessibility</a>.</p>

<h3 id="writing">Writing Web Pages</h3>

<ul>
  <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> as a
  template. Also read our

<p>Moved to <a
  href="/server/standards/README.software.html">software page
  standards</a>.</li>
</ul>
href="/server/standards/README.webmastering.html#gnupackages">GNU 
Webmastering Guidelines</a>.</p>

<h3 id="valid">Broken Links</h3>

<ul>
  <li>
    Help is needed 
    <a href="/server/standards/README.webmastering.html#deadlink">repairing 
    broken links</a>.  There are numerous 
    <a href="/server/standards/README.webmastering.html#symlinks">symlinks</a>,
    so please do not break these

<p>Mentioned 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#addlink">linking</a> the <a href="/server/standards/README.webmastering.html#pollinking">policy</a> 
    is followed in finding replacements.  
  </li>
</ul>
href="/server/standards/README.webmastering.html#deadlink">
GNU Webmastering Guidelines</a>.</p>

<h3 id="l10n">Localization</h3>

<p>Help

<p>A call for help with <a href="/server/standards/README.translations.html">translate 
href="/server/standards/README.translations.html">translations</a> is 
present in the footer of all non-software GNU web pages</a> from English into other languages.  You can either
join an existing translation team, or form a new one.  Check the
<a href="/server/standards/README.translations.html#TranslationsUnderway">existing
translation teams</a>.</p> pages.</p>

</div><!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.html" -->
<div id="footer"> id="footer" role="contentinfo">
<div class="unprintable">

<p>Please send general FSF & GNU inquiries to
<a href="mailto:gnu@gnu.org"><gnu@gnu.org></a>.
There are also <a href="/contact/">other ways to contact</a>
the FSF.  Broken links and other corrections or suggestions can be sent
to <a href="mailto:webmasters@gnu.org"><webmasters@gnu.org></a>.</p>

<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
        replace it with the translation of these two:

        We work hard and do our best to provide accurate, good quality
        translations.  However, we are not exempt from imperfection.
        Please send your comments and general suggestions in this regard
        to <a href="mailto:web-translators@gnu.org">
        <web-translators@gnu.org></a>.</p>

        <p>For information on coordinating and submitting translations of
        our web pages, see <a
        href="/server/standards/README.translations.html">Translations
        README</a>. -->
Please see the <a
href="/server/standards/README.translations.html">Translations
README</a> for information on coordinating and submitting translations
of this article.</p>
</div>

<!-- Regarding copyright, in general, standalone pages (as opposed to
     files generated as part of manuals) on the GNU web server should
     be under CC BY-ND 3.0 US. 4.0.  Please do NOT change or remove this
     without talking with the webmasters or licensing team first.
     Please make sure the copyright date is consistent with the
     document.  For web pages, it is ok to list just the latest year the
     document was modified, or published.
     
     If you wish to list earlier years, that is ok too.
     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
     years, as long as each year in the range is in fact a copyrightable
     year, i.e., a year in which the document was published (including
     being publicly visible on the web or in a revision control system).
     
     There is more detail about copyright years in the GNU Maintainers
     Information document, www.gnu.org/prep/maintain. -->

<p>Copyright © 1996, 1997, 1998, 2001, 2004, 2005, 2006, 2007,
2008, 2013, 2014 2014, 2023, 2024 Free Software Foundation, Inc.</p>

<p>This page is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
Commons Attribution-NoDerivs 3.0 United States Attribution-NoDerivatives 4.0 International License</a>.</p>

<!--#include virtual="/server/bottom-notes.html" -->

<p class="unprintable">Updated:
<!-- timestamp start -->
$Date: 2024/06/29 11:01:33 $
<!-- timestamp end -->
</p>
</div>
</div>
</body>
</html>