gnu_bulletin_9401_10.html 3.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960
  1. <TITLE> - Free Software Support</TITLE>
  2. <P>Go to the <A HREF="gnu_bulletin_9401_9.html">previous</A>, <A HREF="gnu_bulletin_9401_11.html">next</A> chapter.<P>
  3. <H1><A NAME="SEC10" HREF="gnu_bulletin_9401_toc.html#SEC10">Free Software Support</A></H1>
  4. <P>
  5. The Free Software Foundation does not provide any technical support.
  6. Although we create software, we leave it to others to earn a living
  7. providing support. We see programmers as providing a service, much as
  8. doctors and lawyers now do; both medical and legal knowledge are freely
  9. redistributable entities for which the practitioners charge a distribution
  10. and service fee.
  11. <P>
  12. We maintain a list of people who offer support and other consulting
  13. services, called the GNU Service Directory. It is in the file
  14. <TT>`etc/SERVICE'</TT> in the GNU Emacs distribution, <TT>`SERVICE'</TT> in the
  15. GCC distribution and <TT>`/pub/gnu/GNUinfo/SERVICE'</TT> on anonymous FTP host
  16. <CODE>prep.ai.mit.edu</CODE>. Contact us if you would like a printed copy
  17. or wish to be listed in it.
  18. <P>
  19. If you find a deficiency in any GNU software, we want to know. We have
  20. many Internet mailing lists for bug reports, announcements and questions.
  21. They are also gatewayed into USENET news as the <CODE>gnu.*</CODE> newsgroups.
  22. You can request a list of the mailing lists from either
  23. address on the front cover.
  24. <P>
  25. When we receive a bug report, we usually try to fix the problem. While
  26. our bug fixes may seem like individual assistance, they are not. Our
  27. task is so large that we must focus on that which helps the community as
  28. a whole; we do not have the resources to help individuals. We may send
  29. you a patch for a bug that helps us test the fix and ensure its quality.
  30. If your bug report does not evoke a solution from us, you may still get
  31. one from another user who reads our bug report mailing lists.
  32. Otherwise, use the Service Directory.
  33. <P>
  34. Please do not ask us to help you install software or figure out how to use
  35. it--but do tell us how an installation script does not work or where
  36. documentation is unclear.
  37. <P>
  38. If you have no Internet access, you can get mail and USENET news via
  39. UUCP. Contact a local UUCP site, or a commercial UUCP site such as:
  40. <P>
  41. <PRE>
  42. UUNET Technologies, Inc. <CODE>info@uunet.uu.net</CODE>
  43. 3110 Fairview Park Drive - Suite 570 Phone: 1-800-4UUNET4
  44. Falls Church, VA 22042 USA or (703) 204-8000
  45. Fax: (703) 204-8001
  46. </PRE>
  47. <P>
  48. A long list of commercial UUCP and Internet service providers is posted
  49. periodically to USENET in the newsgroup <CODE>news.announce.newusers</CODE>
  50. with <TT>`Subject: How to become a USENET site'</TT>.
  51. <P>
  52. When choosing a service provider, ask those you are considering how
  53. much they do to assist free software development, e.g. by contributing
  54. money to free software development projects or by writing free software
  55. improvements themselves for general use. By basing your decision partially
  56. on this factor, you can help encourage those who profit from free software
  57. to contribute to its growth.
  58. <P>
  59. <P>Go to the <A HREF="gnu_bulletin_9401_9.html">previous</A>, <A HREF="gnu_bulletin_9401_11.html">next</A> chapter.<P>