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.

97 lines
3.6KB

  1. <?xml version="1.0" encoding="UTF-8" ?>
  2. <html>
  3. <head>
  4. <title>PDFreaders - Sprint Guide</title>
  5. </head>
  6. <body>
  7. <p id="category"><a href="pdfreaders.html">Free Software PDF Readers</a></p>
  8. <h1>PDF Readers Sprint Guide</h1>
  9. <h2>Equipment</h2>
  10. <h3>Required</h3>
  11. <ol>
  12. <li>Web-enabled computers, one per attendee, for finding adverts online</li>
  13. <li>GNU/Linux compatible printer (capable of printing envelopes) check whether
  14. you need letters to include the envelope as the first page of the .odt document,
  15. or whether you need the letters and envelopes to be separate documents from the
  16. letter, for easier printing</li>
  17. <li>Sufficient ink to print a letter and envelope for each 'bug'</li>
  18. <li>Printer paper</li>
  19. <li>Envelopes</li>
  20. <li>Access to whatever email account or mailing list that reported bugs are sent
  21. to</li>
  22. <li>Working script for processing email reports generated by web form (available
  23. in FSFE's <a href="https://fsfe.org/contribute/web/web.html">web SVN</a>)</li>
  24. <li>Template ODT letter adapted to your local contact details and language (in SVN)</li>
  25. <li>Approved expense request, or agreement with country team coordinator to cover
  26. postage costs</li>
  27. </ol>
  28. <h3>Desirable</h3>
  29. <ol>
  30. <li>Refreshments for attendees</li>
  31. <li>Projector for showing examples of adverts, demonstrating bug reporting
  32. page, and projecting identi.ca / chat room feed for remote participants</li>
  33. <li>A small prize for the person who finds the most adverts (eg. box of
  34. chocolates)</li>
  35. <li>FSFE leaflets and booth materials for promoting FSFE to attendees</li>
  36. <li>Assistance transporting materials to the event venue</li>
  37. <li>A list or directory of websites of local councils in your country / area for
  38. attendees to work through (this makes hunting faster)</li>
  39. <li>Speakers for background music</li>
  40. <li>Playlist of Creative Commons music</li>
  41. </ol>
  42. <h2>Activities</h2>
  43. <p>Assemble a group of Free Software activists and:</p>
  44. <ol>
  45. <li>Find adverts for proprietary PDF readers on government websites in your
  46. country/area</li>
  47. <li>Send letters to the institutions responsible asking them to remove or
  48. replace the adverts</li>
  49. <li>A model letter can be found on the PDF Readers campaign page, and another in
  50. web SVN (see above). You can modify the letter for easier printing, or to make it more
  51. relevant to your country/area.</li>
  52. </ol>
  53. <p>Don't forget to microblog about what you're doing, and use the #pdfreaders tag
  54. when you do so. You may also want to use tags like #openstandards or #opengov.</p>
  55. <h2>Optional</h2>
  56. <ol>
  57. <li>Publish a press release in the run up to the event (ask your country
  58. coordinator about access to your national/regional FSFE press contacts list)</li>
  59. <li>Organise an interview with local radio or podcast in the run up to the event</li>
  60. <li>Send a copy of petition signatures from people in your country/area in
  61. addition to the letter regarding the specific bug to each institution (more costly
  62. in terms of paper and postage)</li>
  63. <li>Email the institutions a copy of the printed letter and optional list of
  64. signatures</li>
  65. <li>Send follow up letters to institutions that have been contacted in the past
  66. and failed to comply</li>
  67. </ol>
  68. <h2>Note on scripts</h2>
  69. <p>A PHP script is available in the web SVN which generates .odt files directly from the XML
  70. bug reports which are generated by the web form on the PDF Readers campaign page. See readme
  71. file located with the script for additional instructions. This script is designed to be easy
  72. to set up and use (send feedback to web@lists.fsfe.org mailing list).</p>
  73. </body>
  74. <timestamp>$Date: 2011-10-11 13:30:29 +0200 (Fri, 15 Oct 2010) $ $Author: st $</timestamp>
  75. </html>