Message-ID: <49B6D176.8070200@nothome.org>
Date: Tue, 10 Mar 2009 16:45:42 -0400
From: Nathan Angelacos <nangel@nothome.org>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
Precedence: list
MIME-Version: 1.0
To: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] Alpine Linux infrastructure: communication
References: <1236343948.1916.318.camel@nc> <49B32F1C.4080807@nothome.org> <49B387E6.4030806@iki.fi> <49B6D115.5020303@nothome.org>
In-Reply-To: <49B6D115.5020303@nothome.org>
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable

Nathan Angelacos wrote:
> Timo Ter=E4s wrote:
>> Nathan Angelacos wrote:
>>> So, I guess I'm interested in knowing... what are the features that you
>>> view are necessary for the mail archives?  (besides the obvious we don't
>>> lose any more...)
>>
>> I think threading and monthly indexes are pretty important. Searching is
>> nice but not must.
>>
>> Many projects have just threaded indexes. Sometimes the searchable
>> archives are hosted somewhere else. Or maybe just outsource hosting
>> to google? Let it index the mail archives and make a search box google
>> search that limits the search to our site.
>>
>> Generally I'm pretty ok with Pipermail. E.g. see busybox or asterisk
>> archives. But if someone needs searching then it's not enough.
>>
>> - Timo
>>
>=20
> http://willow-lists.tetraec.net/

err.. http://willow-lists.tetrasec.net/

I kan't zpell




---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---