From 23ed6ac8c03997f6b4e3c9dc1b018f18b12fbdd4 Mon Sep 17 00:00:00 2001 From: Arne Babenhauserheide Date: Fri, 1 Jun 2012 10:12:33 +0200 Subject: started “how I write a qoth” MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- community/weblogs/ArneBab/how-i-write-a-qoth.mdwn | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 community/weblogs/ArneBab/how-i-write-a-qoth.mdwn diff --git a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn new file mode 100644 index 00000000..adee5e68 --- /dev/null +++ b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn @@ -0,0 +1,5 @@ +I just read on the hurd IRC channel (chat: #hurd at irc.freenode.net), that people consider my work valuable (I knew that, and I think that myself, but it is still nice to hear), so I want to dispell any possible myth about it :) + +What I do is not hard - at least not anymore, since I created a simple structure for it. + + -- cgit v1.2.3 From d21b7f54c58ec15ca26abf7162f0374f5985f93a Mon Sep 17 00:00:00 2001 From: Arne Babenhauserheide Date: Fri, 1 Jun 2012 11:16:26 +0200 Subject: Blog-entry: How I write a qoth. --- community/weblogs/ArneBab/how-i-write-a-qoth.mdwn | 43 ++++++++++++++++++++++- 1 file changed, 42 insertions(+), 1 deletion(-) diff --git a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn index adee5e68..b0018320 100644 --- a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn +++ b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn @@ -1,5 +1,46 @@ I just read on the hurd IRC channel (chat: #hurd at irc.freenode.net), that people consider my work valuable (I knew that, and I think that myself, but it is still nice to hear), so I want to dispell any possible myth about it :) -What I do is not hard - at least not anymore, since I created a simple structure for it. +What I do is not hard - at least not anymore, since I created a simple structure for it (But it still takes time). +First I open up the relevant mailing lists for the quarter. I get them from [[contributing/web_pages/writing_the_qoth]]. Normally I just use the following: + * + * + +Then I copy them 3 times and use M-x replace-string (in emacs) to adjust them to the correct months. + +Additionally I open the Arch Hurd news: + + * + * + +Having all those news at hand, I read every thread-starter and every news-item. For each of them I first check if I understand them (no use trying to explain something I don’t get myself) and if they provide a way for people to test what they improved (however complex that might be), then I + +* note the name of the main contributor(-s), +* write a line of text what it does (often partly copied from the news-item) +* add a link to the news-item, a code-repo or a patch and +* a note how that new development helps achieve the goals_of_the_Hurd (see [[contributing/web_pages/writing_the_qoth]] for details). + +With that list of short news I go into [[contributing/web_pages/qoth-next]]. + +Now I identify 2 to 4 main news items by some kind of “helps the Hurd most when more people know it”, “biggest change” and similar fudgery :) + +Finally I sort all the news items by intuition, crude logic I develop on-the-fly writing and the goal of making the qoth read somewhat like nice prose. + +On the way to that I commit every little to medium step. I never know when I have to abort due to an interruption (I’m sure tschwinge loves my super-non-atomic horrible-to-review commits - but better that than losing work == time, and I try to prefix the commit-messages with “news:” so he knows that it’s useless to review them as in-flight-patches…). + +Having finished the text (usually after 3 to 6 hours of overall work), I send it by mail to bug-hurd: + +After about a week I incorporate the comments from there and publish the qoth as described in [[contributing/web_pages/writing_the_qoth]]. + +Then tschwinge reviews it, does some last-minute changes and pushes it from the staging wiki to the website. + +And that’s it. + +I hope this small insight was interesting to you! + +Happy hacking and have fun with the Hurd! + +-- Arne Babenhauserheide + +PS: Writing this blog entry took about 20 minutes. The raw text is longer than a qoth, but it is much faster to write, because it avoids the main time-eater: Gathering the info with the necessary references to make sure that people can test what’s in here. -- cgit v1.2.3 From 6436b1d94f44085e5810d5566316778f2de8c285 Mon Sep 17 00:00:00 2001 From: Arne Babenhauserheide Date: Fri, 1 Jun 2012 12:49:54 +0200 Subject: fix syntax --- community/weblogs/ArneBab/how-i-write-a-qoth.mdwn | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn index b0018320..05637702 100644 --- a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn +++ b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn @@ -4,15 +4,15 @@ What I do is not hard - at least not anymore, since I created a simple structure First I open up the relevant mailing lists for the quarter. I get them from [[contributing/web_pages/writing_the_qoth]]. Normally I just use the following: - * - * +* +* Then I copy them 3 times and use M-x replace-string (in emacs) to adjust them to the correct months. Additionally I open the Arch Hurd news: - * - * +* +* Having all those news at hand, I read every thread-starter and every news-item. For each of them I first check if I understand them (no use trying to explain something I don’t get myself) and if they provide a way for people to test what they improved (however complex that might be), then I -- cgit v1.2.3 From a0620188c736f355e943a1e0ce97438707888191 Mon Sep 17 00:00:00 2001 From: Arne Babenhauserheide Date: Fri, 1 Jun 2012 13:25:23 +0200 Subject: fix links --- community/weblogs/ArneBab/how-i-write-a-qoth.mdwn | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn index 05637702..c98f3354 100644 --- a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn +++ b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn @@ -2,7 +2,7 @@ I just read on the hurd IRC channel (chat: #hurd at irc.freenode.net), that peop What I do is not hard - at least not anymore, since I created a simple structure for it (But it still takes time). -First I open up the relevant mailing lists for the quarter. I get them from [[contributing/web_pages/writing_the_qoth]]. Normally I just use the following: +First I open up the relevant mailing lists for the quarter. I get them from [[contributing/web_pages/news/writing_the_qoth]]. Normally I just use the following: * * @@ -19,9 +19,9 @@ Having all those news at hand, I read every thread-starter and every news-item. * note the name of the main contributor(-s), * write a line of text what it does (often partly copied from the news-item) * add a link to the news-item, a code-repo or a patch and -* a note how that new development helps achieve the goals_of_the_Hurd (see [[contributing/web_pages/writing_the_qoth]] for details). +* a note how that new development helps achieve the goals_of_the_Hurd (see [[contributing/web_pages/news/writing_the_qoth]] for details). -With that list of short news I go into [[contributing/web_pages/qoth-next]]. +With that list of short news I go into [[contributing/web_pages/news/qoth-next]]. Now I identify 2 to 4 main news items by some kind of “helps the Hurd most when more people know it”, “biggest change” and similar fudgery :) @@ -31,7 +31,7 @@ On the way to that I commit every little to medium step. I never know when I hav Having finished the text (usually after 3 to 6 hours of overall work), I send it by mail to bug-hurd: -After about a week I incorporate the comments from there and publish the qoth as described in [[contributing/web_pages/writing_the_qoth]]. +After about a week I incorporate the comments from there and publish the qoth as described in [[contributing/web_pages/news/writing_the_qoth]]. Then tschwinge reviews it, does some last-minute changes and pushes it from the staging wiki to the website. -- cgit v1.2.3 From 87dc82cd0445f4868f8be88cd5e7cc03f38ebcbd Mon Sep 17 00:00:00 2001 From: Arne Babenhauserheide Date: Fri, 1 Jun 2012 13:26:13 +0200 Subject: missing smiley --- community/weblogs/ArneBab/how-i-write-a-qoth.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn index c98f3354..74dab6a9 100644 --- a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn +++ b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn @@ -27,7 +27,7 @@ Now I identify 2 to 4 main news items by some kind of “helps the Hurd most whe Finally I sort all the news items by intuition, crude logic I develop on-the-fly writing and the goal of making the qoth read somewhat like nice prose. -On the way to that I commit every little to medium step. I never know when I have to abort due to an interruption (I’m sure tschwinge loves my super-non-atomic horrible-to-review commits - but better that than losing work == time, and I try to prefix the commit-messages with “news:” so he knows that it’s useless to review them as in-flight-patches…). +On the way to that I commit every little to medium step. I never know when I have to abort due to an interruption (I’m sure tschwinge loves my super-non-atomic horrible-to-review commits :-) - but better that than losing work == time, and I try to prefix the commit-messages with “news:” so he knows that it’s useless to review them as in-flight-patches…). Having finished the text (usually after 3 to 6 hours of overall work), I send it by mail to bug-hurd: -- cgit v1.2.3 From 723524af82c1dbe703d914868f147f9a95f06ef8 Mon Sep 17 00:00:00 2001 From: Arne Babenhauserheide Date: Fri, 1 Jun 2012 13:28:05 +0200 Subject: fix link --- community/weblogs/ArneBab/how-i-write-a-qoth.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn index 74dab6a9..77882619 100644 --- a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn +++ b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn @@ -21,7 +21,7 @@ Having all those news at hand, I read every thread-starter and every news-item. * add a link to the news-item, a code-repo or a patch and * a note how that new development helps achieve the goals_of_the_Hurd (see [[contributing/web_pages/news/writing_the_qoth]] for details). -With that list of short news I go into [[contributing/web_pages/news/qoth-next]]. +With that list of short news I go into [[contributing/web_pages/news/qoth_next]]. Now I identify 2 to 4 main news items by some kind of “helps the Hurd most when more people know it”, “biggest change” and similar fudgery :) -- cgit v1.2.3 From 71d2a2361d5a98c725315f6423360ed31f97ff20 Mon Sep 17 00:00:00 2001 From: Arne Babenhauserheide Date: Fri, 1 Jun 2012 13:29:46 +0200 Subject: news: writing the qoth was missing a link to the qoth. --- contributing/web_pages/news/writing_the_qoth.mdwn | 1 + 1 file changed, 1 insertion(+) diff --git a/contributing/web_pages/news/writing_the_qoth.mdwn b/contributing/web_pages/news/writing_the_qoth.mdwn index 6aea5f4d..88542255 100644 --- a/contributing/web_pages/news/writing_the_qoth.mdwn +++ b/contributing/web_pages/news/writing_the_qoth.mdwn @@ -11,6 +11,7 @@ License|/fdl]]."]]"""]] # Short Guide for Writing the QotH +The not yet published next Quarter of Hurd the can found at [[contributing/web_pages/news/qoth_next]]. ## Individual News Items -- cgit v1.2.3 From df8da81ffb61371b71e384bff41708896888a282 Mon Sep 17 00:00:00 2001 From: Arne Babenhauserheide Date: Fri, 1 Jun 2012 13:30:37 +0200 Subject: blog-entry: polish --- community/weblogs/ArneBab/how-i-write-a-qoth.mdwn | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn index 77882619..2ba6ac9e 100644 --- a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn +++ b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn @@ -37,9 +37,7 @@ Then tschwinge reviews it, does some last-minute changes and pushes it from the And that’s it. -I hope this small insight was interesting to you! - -Happy hacking and have fun with the Hurd! +I hope this small insight was interesting to you. Happy hacking and have fun with the Hurd! -- Arne Babenhauserheide -- cgit v1.2.3 From f3efa40dd18bd9f7f6254c668d2af79d63f40ac5 Mon Sep 17 00:00:00 2001 From: Arne Babenhauserheide Date: Fri, 1 Jun 2012 13:31:25 +0200 Subject: blog-entry: missing comma --- community/weblogs/ArneBab/how-i-write-a-qoth.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn index 2ba6ac9e..87b1f07d 100644 --- a/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn +++ b/community/weblogs/ArneBab/how-i-write-a-qoth.mdwn @@ -17,7 +17,7 @@ Additionally I open the Arch Hurd news: Having all those news at hand, I read every thread-starter and every news-item. For each of them I first check if I understand them (no use trying to explain something I don’t get myself) and if they provide a way for people to test what they improved (however complex that might be), then I * note the name of the main contributor(-s), -* write a line of text what it does (often partly copied from the news-item) +* write a line of text what it does (often partly copied from the news-item), * add a link to the news-item, a code-repo or a patch and * a note how that new development helps achieve the goals_of_the_Hurd (see [[contributing/web_pages/news/writing_the_qoth]] for details). -- cgit v1.2.3