The best use of Announcement lists @ apache (draft)


尚、Apache には何個も Announcement 用のメーリングリスト(日本人的に言えば「メルマガ」と言ったほうが良い….この「文化の違い」を吸収するのは密かに大変だったりする)がありますが、一番大きいのはHTTP Server 専用リスト(17700人近くいます)で、次がASF全体のアナウンスリスト(9000人近く)、次がJakarta(7000人近かったはず)です。XMLが2200人くらいですが「全然」増減しません。Jakarta / ASF-Wide は、毎日 5 – 10 人近い「新規加入」があります。

ASF-Wide の Announcement List がもっと活性化すれば News Items とかを「ひろいやすく」なるのになあ、と思いつつ、賢い利用方法が周知されていなかったりします。ここら辺の「Let it be」的なところは極めて「オープンソース・チック」で親しみを覚えたりもしますが、反面、「悪習をそのままにしておく」というのは限度が過ぎると「人をバカにしている」ようにも見える場合があるので(あくまで、限度が過ぎれば、の話….口うるさいとまた「choke the innovations in embryo」だな…)、<バランス>は必要でしょう — ねえ 🙂

ASF 全体の Announcement List に、「Howdy! (よっ)」とかいうメッセージでメールを送ったら、すぐに「Subscriber」の数が減ってしまったりするので(SPAMと勘違いされるし…そりゃそうですね、自動でAppendされる[] タグも無いし海外は「メーリングリスト」対応のリテラシが相対的に低いので。この「激減」transitionは見ててすごく笑える…苦笑に近い)、そういう点で「Cultivation」「Civilization」が必要かナ、と思っていたりはしますが。

Written by Tetsuya Kitahata

Just a memo for The best use of announcement lists in — for future references

– What is –

“news and announcements about The Apache Software Foundation and its projects. Announcements of major software releases, new projects, and other important news are included.”

Note: Major software releases – exclude alpha, beta, R.C. release (preferable!?)

– Purpose –

The original intention of the setup of list was to use the archives of this list to create an apache-news webpage that would list all the important events of The Apache Software Foundation.
Important release news from various projects/subprojects in would be highly expected to be noticed in, as well as important notices from The Apache Software Foundation such as “Update to Apache License Version 2.0“.

– Who can use? –

Members and Committers in The Apache Software Foundation.

– Format? –


Subject: [ANN] (Apache|$TLP|Apache-$TLP)? $SubProject Team released (Apache|$TLP|Apache-$TLP)? $SubProject X.Y.Z.


Subject: [ANN] (Apache|$TLP|Apache-$TLP)? $SubProject X.Y.Z. Released


The Apache Software Foundation, The $TLP Project Management Committee
and The (Apache|$TLP|Apache-$TLP)? $SUBPROJECT Project Team are pleased
to announce the release of version X.Y.Z of (Apache|$TLP|Apache-$TLP)

~~~~Blah, Blah, Blah (3-5 lines nice blurb on $SubProject etc.)~~~~
~~~~Blah, Blah, Blah … see other announcement samples ~~~~

— By (Apache|$TLP|Apache-$TLP) $SubProject Development Team —
URL: http://$$SubProject/

GIVEN $TLP (Top Level Project Name), $SubProject (Project Name)

– How to subscribe? –

Visit here:


– Other announcement lists? –

Apache HTTP Server Project, Apache Jakarta Project, Apache XML Project etc. have their own announcement lists.

Apache HTTP Server Announcement List – subscribe
Jakarta Project Announcement List – subscribe
XML Project Announcement List – subscribe
ApacheCon Announcement List – subscribe
etc. etc….

alpha, beta, R.C., final release -> each $TLP mailing lists
final release -> as well
would be preferable, perhaps. — by Tetsuya Kitahata

Garbled Characters @ planetapache

Do you know why we encounter Mojibake (garbled-characters) phoenomena in

When setting encodings to “Unicode (UTF-8)” on my/your browser, it’s okay. not-garbled.
But I/you have to set the encodings on my/your browser to “Unicode (UTF-8)” *WHENEVER* accessing to

> C:\cygwin\bin>wget -S
> --16:36:45--
>            => `index.html'
> Resolving done.
> Connecting to[]:80... connected.
> HTTP request sent, awaiting response...
>  1 HTTP/1.1 200 OK
>  2 Date: Thu, 25 Mar 2004 07:37:01 GMT
>  3 Server: Apache/2.0.48 (Unix) DAV/2 mod_python/3.1.3 Python/2.3.2 SVN/1.0.0
>  4 Last-Modified: Thu, 25 Mar 2004 07:06:22 GMT
>  5 ETag: "2256c9-14b98-48d89780"
>  6 Accept-Ranges: bytes
>  7 Content-Length: 84888
>  8 Vary: Accept-Encoding,User-Agent
>  9 Keep-Alive: timeout=15, max=100
> 10 Connection: Keep-Alive
> 11 Content-Type: text/html; charset=ISO-8859-1

This is the root of the problem. Perhaps it would be possible for this line (#11) to be simplified to be “Content-Type: text/html;” – or – “Content-Type: text/html; charset=utf-8”.

I now have planetplanet powered sites running — in Japanese. In my server, it does not specify charset field in HTTP Header, so it appears to be working well for now. — using UTF-8 — e.g.
This means that each browsers can choose charsets specified in the line
<meta http-equiv=”Content-Type” content=”text/html; charset=*****” />
— meta tag information included in each HTML pages —

If my memory serves me correctly, I saw the same thing in eyebrowse @ in the past. Now, fixed.


> C:\cygwin\bin>wget -S
> --17:28:28--
>            => `index.html.3'
> Resolving done.
> Connecting to[]:80... connected.
> HTTP request sent, awaiting response...
>  1 HTTP/1.1 200 OK
>  2 Date: Thu, 25 Mar 2004 08:29:21 GMT
>  3 Server: Apache Coyote/1.0
>  4 Content-Type: text/html; charset=UTF-8
>  5 Content-Length: 28328
>  6 Connection: close

Look at line #4. — Goooooooood. Perfect!

Oh, forgot to mention. Perhaps, even *normal* Japanese characters might be perceived as “garbled” for those who do not know (nor appreciate) Kanji/Hiragana/Katakana …. Whether garbled or not — Very RELATIVE and PHILOSOPHICAL issue, indeed 🙂