Source files of fsfe.org, pdfreaders.org, freeyourandroid.org, ilovefs.org, drm.info, and test.fsfe.org. Contribute: https://fsfe.org/contribute/web/ https://fsfe.org
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

useful-tips-for-users.en.xhtml 2.8KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495
  1. <?xml version="1.0" encoding="UTF-8" ?>
  2. <html>
  3. <head>
  4. <title>Useful Compliance Tips For Users - FSFE Legal</title>
  5. <link rel="stylesheet" media="all" href="/style/grid.css" type="text/css" />
  6. <link rel="stylesheet" media="all" href="ftf.css" type="text/css" />
  7. </head>
  8. <body>
  9. <p id="category"><a href="/activities/ftf/ftf.html">Legal</a></p>
  10. <h1>Useful Compliance Tips For Users</h1>
  11. <p id="introduction">
  12. These tips can help you locate some common issues in software that
  13. contains code under the GNU GPL licence. For detailed and
  14. authoritative information about the GNU GPL you should read the <a
  15. href="http://www.fsf.org/licensing/licenses/gpl-faq.html">FSF's
  16. GNU GPL FAQ</a>.
  17. </p>
  18. <p>
  19. This is not legal advice. If you have doubts consult a legal
  20. advisor.
  21. </p>
  22. <h2>Basic guidelines</h2>
  23. <ol>
  24. <li>
  25. Check if a copy of the GNU GPL licence comes with the software.
  26. </li>
  27. <li>
  28. Check if a copy of the source code comes with the software or
  29. there is a written offer to provide the source code on a
  30. physical media like a CD ROM for no more than the cost of
  31. production and shipping.
  32. </li>
  33. <li>
  34. Check that distributor does not claim sole copyright on the
  35. software if the software also contains code created by others.
  36. </li>
  37. </ol>
  38. <h2>More Detailed guidelines</h2>
  39. <ol>
  40. <li>
  41. Check if the correct version of the source code is available.
  42. The source code has to be exactly the same version as the
  43. executable (object) code provided.
  44. </li>
  45. <li>
  46. Check if the source code includes the source for any derivative
  47. works of the GNU GPL code, not just of the third-party GNU GPL
  48. components themselves.
  49. </li>
  50. <li>
  51. Check if the source code includes the scripts used to control
  52. compilation and installation.
  53. </li>
  54. <li>
  55. If the toolchain is released and contains tools under the GNU
  56. GPL (like the GCC compiler), check if the source code for those
  57. tools is also available.
  58. </li>
  59. </ol>
  60. <p>
  61. If you are worried that some software you got received is not
  62. adhering to the terms of the GNU GPL licence you can review the <a
  63. href="http://www.fsf.org/licensing/licenses/gpl-faq.html">FSF's
  64. GNU GPL FAQ</a> and the <a
  65. href="http://www.fsf.org/licensing/licenses/gpl-howto.html">FSF's
  66. HOW-TO for using the GNU GPL</a>. If you suspect there has been a
  67. violation of the GNU GPL you can <a href="contact.html">contact</a> the
  68. FTF and we will help you resolve the issue.
  69. </p>
  70. </body>
  71. <timestamp>$Date$ $Author$</timestamp>
  72. </html>
  73. <!--
  74. Local Variables: ***
  75. mode: xml ***
  76. End: ***
  77. -->