[Mailman-Developers] Mailman search function (was?? Re: Like to participate in GSOC 2013 (GNU Mailman) - Like some ideas proposed in the list (Django, Python))

[Mark Sapiro]

On 06/29/2013 07:12 PM, Chris Cargile wrote:

> I'm not sure where things stand regarding search for mailman-
> however, I found Ian
> Hicks<http://lists.whatwg.org/pipermail/commit-watchers-whatwg.org/>'
> approach (of applying the HT-Dig capabilities to enhance a MM v2.0 instance
> interesting, but perhaps overkill and/or not quite right) but a good
> case-in-point for ideas.


It appears the archive at the above URL employs the indexing and htdig
patches for Mailman 2,1 originally developed by Richard Barrett
<http://www.openinfo.co.uk/mm/index.html> and now maintained by me
<http://www.msapiro.net/mm/>.


> I resolved my need for making 'search' on my lists practically achievable
> but in terms of overall integration into the fabric of mailman code, it is
> insufficient.


What more do you want?


> If you want to see my search implementation, check out a prototype from me
> on my AWS instance<http://ec2-54-224-162-128.compute-1.amazonaws.com/pipermail/mailman/>
> .
> 
> Please share your thoughts here or directly to me ;)


Your prototype looks fine, but what's behind /cgi-bin/search.py ?

Don't look for anything to be released for MM 2.1. The patches for htdig
are available and other methods are referenced in the FAQ. If anything
were to be released, it would be the htdig patches because that's what I
use, but it's problematic because of the htdig dependency.

For Mailman 3 the intent is that archivers will be "plugable", and the
defaults will be <http://www.mail-archive.com> and
<https://fedorahosted.org/hyperkitty/>

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan