summaryrefslogtreecommitdiff
path: root/contributing/web_pages/news.mdwn
blob: 39d9dbde9642d1134757a9c4b744d46025ee4743 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
[[!meta copyright="Copyright © 2009, 2010 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
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
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
month"""]]

We prepare *A Month of the Hurd* in the file [[contributing/web_pages/news/news_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.

* At the end of the month: prepare for publishing the news

    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

        $ git cp contributing/web_pages/news/news_moth_next news/yyyy-mm
        $ git commit -m "Added 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]]