[:DebianWiki/EditorGuide#translation:Translation(s)]: none

(!) [:/Discussion:Discussion]


This page documents the current workflow used to draft, edit and send out issues if the [:ProjectNews:Debian Project News].

Please note, that the following states only the ideal workflow. Because of tome constrainst of the editors or due to expected but events (e.g. when one ftp-masters askes the issue to be delayed for a couple of hours, so the mail he is about to send out can be mentionend in the issue) the following timeline might be stretched.

Please also note, that this workflow is just what we curently use - we are well aware, that it isn't perfect, but we curently don't have the time for any drastic changes.

Current workflow

(As practiced more or less by Meike and Alexander.)

  1. After an issue has been sent out, the wiki page is "cleaned up".
    • [:ProjectNews/Issues/Current:] is renamed to the proper name (ProjectNews/Issues/$year/$number).
    • [:ProjectNews/Issues:] is update.
      • Add the just released issue with it's topics.
      • Calculate date for the next issue (14 days later).
    • A new issue is created at [:ProjectNews/Issues/Current:] based on the template at ?ProjectNewsTemplate.

  2. For the next ~10 days, stuff is added to the TODO of the current [:ProjectNews/Issues/Current:draf].

    • Interesting blog posts are added.
    • Links to interesting discussion on one of our mailing lists are added.
    • If an security advisorie is released, we consider adding it, roughly based on importance of package and guessed number of installations.
  3. On the weekend before the monday the issue is to be released, the texts actual texts are written.
  4. If a text isn't long enough, they are moved to the "other news" section.
  5. When we are done, we add the numbers to the WNPP paragraph.
  6. Since we are not the only group within Debian showing activity during weekends, we might need to add a lot of stuff, which hasn't been on the todo-list, yet.
  7. Theoretical it's now sunday evening; and we ask on the [http://lists.debian.org/debian-l10n-english/ debian-l10n-english] list for reviewers. (Practicaly we reach this point often just on Monday evening and try to catch some native english speakers via IRC.)

  8. At the same time, the current draft is added to the [http://alioth.debian.org/projects/dwn-trans/ DWN translation project] to give them more time transliting the news. (Again, we often skip that point, since we reach it to late.)

  9. After the issue has been reviewed it is transfered to wml, which is used for Debian's website. That roughly means:
    • Copying the last issue to a new file name and cleaning it up
    • Copy pasting the [http://wiki.debian.org/ProjectNews/Issues/Current?action=raw raw output] of the current draft into the new file

    • Replacing /^= /<strong><p>/

    • Replacing / =$/<\/strong><\/p>/

    • Replacing /[/<a href="/

    • Repalcing /]/<\/a>/}

    • Manually fixing links, adding <p> and </p> to the paragraphs; fixing quotation marks / replacing them with <q> and </q> where that's the proper form

    • The "new and noteworthy packages" are added by a script (newpkgs parsing http://packages.debian.org/unstable/main/newpkg

  10. At this point we most likely have a valid wml file; we test the build in an CVS checkout of Debians website
  11. Then we test the links, look for broken HTML etc.
  12. If everything works well, the wml-File is commited to CVS and the CURRENT-ISSUE-IS point is adjusted
  13. Now we use makemail.pl to generate a text version of the issue
  14. For some weird reason links get lost during that process when Alex uses the script
    • So he readds all the links into the text version
  15. When that is done, the text version is send to the [http://lists.debian.org/debian-news debian-news] mailing list

Problems with the current workflow


See also: