summaryrefslogtreecommitdiff
path: root/contributing/web_pages/news.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'contributing/web_pages/news.mdwn')
-rw-r--r--contributing/web_pages/news.mdwn43
1 files changed, 19 insertions, 24 deletions
diff --git a/contributing/web_pages/news.mdwn b/contributing/web_pages/news.mdwn
index 4edd491a..54fa788d 100644
--- a/contributing/web_pages/news.mdwn
+++ b/contributing/web_pages/news.mdwn
@@ -1,4 +1,5 @@
-[[!meta copyright="Copyright © 2009, 2010 Free Software Foundation, Inc."]]
+[[!meta copyright="Copyright © 2009, 2010, 2011 Free Software Foundation,
+Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -8,34 +9,28 @@ Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]
-[[!meta title="""How to prepare and publish "a month of the Hurd" for the last
+[[!meta title="""How to prepare and publish a "Month of the Hurd" for the last
month"""]]
-We prepare *A Month of the Hurd* in the file [[contributing/web_pages/news/news_moth_next]]. The idea is
+We prepare a *Month of the Hurd* in the file [[moth_next]]. The idea is
to record to-be-published changes in that file at they time they arise, and
-then publish them en bloc at the end of the month.
+then publish them en bloc at the end of the month. There are instructions for
+[[writing_the_moth]].
-* At the end of the month: prepare for publishing the news
+ * At the end of the month: prepare for publishing the MotH, then send the raw
+ Markdown text to the mailing list, asking for feedback.
- Edit the news entry's *meta date* value to the timestamp when the news
- entry is [[published|news]]. We have to set that one manually, as
- otherwise the timestamp of the news entry file's creation will be taken,
- which is (much) earlier, and not what we want. We do not set the *meta
- updated* value, as it's correct to update that one upon further
- modifications of the news entries.
-
-* Then send it to the mailing list, include all feedback ...
+ * ..., and publish.
-* ... and publish
+ $ git mv contributing/web_pages/news/moth_next.mdwn news/YYYY-MM.mdwn
- $ git cp contributing/web_pages/news/news_moth_next.mdwn news/yyyy-mm.mdwn
- $ git commit -m "Added MotH yyyy-mm"
+ Edit the news entry's *meta date* value to the timestamp when the news
+ entry is published. We have to set that one manually, as otherwise the
+ timestamp of the news entry file's creation will be taken, which is (much)
+ earlier, and not what we want. We do not set the *meta updated* value, as
+ it's correct to update that one upon further modifications of the news
+ entries.
+
+ $ git cp contributing/web_pages/news/skeleton.mdwn contributing/web_pages/news/moth_next.mdwn
+ $ git commit -m 'MotH YYYY-MM.'
$ git push origin master
-
-## Information for *writing* the Month of the Hurd
-
-[[!inline
-pages="contributing/web_pages/news/*"
-show=5
-feeds=no
-actions=yes]]