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

news-20171219-01.en.xhtml 2.7KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <html newsdate="2017-12-19">
  3. <head>
  4. <title>FSFE releases refreshed set of REUSE practices and a tool to help developers comply</title>
  5. </head>
  6. <body>
  7. <h1>FSFE releases refreshed set of REUSE practices and a tool to help developers comply</h1>
  8. <p newsteaser="yes">
  9. The REUSE Initiative has received an updated set of practices that simplify
  10. the process of declaring copyright and licence information. To help
  11. facilitate developers with updating their projects, the FSFE has also
  12. published a tool that verifies whether a project is compliant.
  13. </p>
  14. <div class="captioned" style="width:80%; margin: 1.5em auto;">
  15. <a href="https://reuse.software/">
  16. <img src="/picturebase/miscellaneous/2017-12-14-reuse-header.png" />
  17. </a>
  18. </div>
  19. <p>
  20. Copyright and licensing is difficult. Finding out the exact copyright and
  21. licence of a piece of code is often times more difficult than it should be.
  22. Missing or scattered licence information makes it very labour-intensive to
  23. verify whether you can legally use a piece of code. For a thorough legal
  24. review, you have to manually check every file for licence information, and
  25. every file has a different way of declaring its copyright and licence.
  26. </p>
  27. <p>
  28. But what if we could automate this? That is what
  29. the <a href="https://reuse.software/">REUSE Initiative</a> postulates. By
  30. defining a standard for copyright and licence declaration, the legal process
  31. of complying with licences becomes a lot easier. Simply include a standard,
  32. computer-readable header tag to every file, and extracting the licence
  33. information should be as simple as running a parser.
  34. </p>
  35. <p>
  36. Earlier in October, we released a set of practices towards that end. Now,
  37. we have <a href="https://reuse.software/practices/2.0/">updated those
  38. practices</a> to streamline them some. To accompany the streamlined
  39. changes, we have published
  40. <a href="https://git.fsfe.org/reuse/reuse">a tool</a> for developers to
  41. check whether they comply with our recommendations.
  42. </p>
  43. <p>
  44. The primary change between the old version and the new is that you no longer
  45. need to declare two tags; only one. 'License-Filename' has been deprecated,
  46. and instead its functionality has been rolled into
  47. 'SPDX-License-Identifier'. This is more in line with existing projects, and
  48. is less effort to boot.
  49. </p>
  50. <p>
  51. Complying with the REUSE recommendations is very simple. Why not give it a
  52. spin? We would love to hear from you.
  53. </p>
  54. </body>
  55. <tags>
  56. <tag>front-page</tag>
  57. <tag>reuse</tag>
  58. </tags>
  59. <author id="carmenbianca" />
  60. </html>