volunteers to prepare and maintain packages, because the priority of the
Cygwin Team is Cygwin itself.
-There's a Cygwin Contributor's Guide on the project web page available
-here @file{http://cygwin.com/setup.html}, which details everything you'll
-need to know about being a package maintainer. If you need any extra
-help you can ask on cygwin-apps @emph{at} cygwin @emph{dot} com mailing
-list, or alternatively you can search the cygwin-apps archives
-(start at @file{http://http://cygwin.com/lists.html}), as your question
-may well have been asked before. Charles Wilson posted a short recipe
-of what's involved, using texinfo as an example, available at
+The Cygwin Package Contributor's Guide is at
+@file{http://cygwin.com/setup.html}, which details everything you need
+to know about being a package maintainer. Use the cygwin-apps mailing
+list (start at @file{http://cygwin.com/lists.html}) for
+questions about package maintenance, @emph{after} searching and browsing the
+cygwin-apps list archives, of course. Charles Wilson posted a short
+recipe of what is involved, using texinfo as an example, available at
@file{http://cygwin.com/ml/cygwin-apps/2000-11/msg00055.html}. This
should give you an idea of what is required.
The home page for the Cygwin project is @file{http://cygwin.com/}.
There you should find everything you need for Cygwin, including links
-for download and setup, a current list of ftp mirror sites,
-a User's Guide, an API Reference, mailing lists and archives, and
-additional ported software.
+for download and setup, a current list of mirror sites, a User's
+Guide, an API Reference, mailing lists and archives, and additional
+ported software.
You can find documentation for the individual GNU tools at
@file{http://www.fsf.org/manual/}. (You should read GNU manuals from a