Re: [Mailman-Developers] Google Summer of Code: Integration of Search Code

[Shayan Md]

On Fri, Mar 30, 2012 at 10:48 AM, Stephen J. Turnbull wrote:

> On Fri, Mar 30, 2012 at 12:24 PM, Shayan Md  wrote:
> > On Fri, Mar 30, 2012 at 5:05 AM, Stephen J. Turnbull  >wrote:
>
> >> And (2) search and retrieval may
> >> do a *lot* of message access, for example if you want to do data
> >> mining (see Ana from Spain's thread).
>
> > Isn't it the purpose of index?
>
> Yes, of course, but possibly it's not good enough.  Yes, when you know
> what "features" (eg, author)  you want to index.  Then you can use an
> online algorithm, indexing messages as they come in.  However, many
> data mining methods are adaptive, meaning that they discover features
> of the corpus over time (eg, through "Bayesian" algorithms) and then
> wish to go back and reindex or cross-reference previously examined
> messages based on more accurate feature specifications.
>
> As I say, if that's not your purpose, then you don't have to worry
> about it.  But in some cases it will matter (eg, pretend you're
> Google, not just a GSoC student!)
>

Okay then, can you please tell me how we can put this search code in best
use of mailman3? I have a proposal to write, I am getting unsure of things
day by day. Can you also tell me who is the mentor of this project?

> ___
> Mailman-Developers mailing list
> Mailman-Developers@python.org
> http://mail.python.org/mailman/listinfo/mailman-developers
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Searchable Archives:
> http://www.mail-archive.com/mailman-developers%40python.org/
> Unsubscribe:
> http://mail.python.org/mailman/options/mailman-developers/mdoshayan%40gmail.com
>
> Security Policy: http://wiki.list.org/x/QIA9
>
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Developers] Google Summer of Code: Integration of Search Code

[Shayan Md]

On Fri, Mar 30, 2012 at 5:05 AM, Stephen J. Turnbull wrote:

> On Fri, Mar 30, 2012 at 3:55 AM, Shayan Md  wrote:
>
> > Assuming that we have something like this(object-ID-addressable, If I am
> > not wrong, mailman3 made it possible but not yet implemented as it's part
> > of archiver), is it over ambitious to plan to implement indexer/searcher
> > for mailman3 and a REST API to use this searcher, extend client to use
> this
> > api,
> > and django search form along with this client api? All this independent
> of
> > archiver. Because the only part common with archiver is message retrieval
> > part,
> > If we implement whole searcher, and rest of the client code, later when
> > archiver is implemented message retrieval code can used in searcher. When
> > archiver is completely mature may we can even merge them together. Is it
> > possible? Or this plan has any 'non-sense' parts?
>
> Hi, Shayan.  It's not nonsense, but (1) how do you propose to test if
> you have no archives to run it on?  And (2) search and retrieval may
> do a *lot* of message access, for example if you want to do data
> mining (see Ana from Spain's thread).  In that case, you may find that
> maildir imposes too many stats, which are very expensive on some
> platforms (and not cheap on any that I know of) and mbox requires too
> large memory.  So for some purposes a summary/index/search engine may
> want an optimized message store.
>
Isn't it the purpose of index? I mean, when we search for something we
don't have stat all the messages, search the index return the best matching
message IDs. If you wish to see the message then retrieve it(may be through
archiver). Probably we can index messages through cron every night.

>
> Those may not be your purposes, of course, in which case a simple mbox
> accessor and a download of a couple of mboxes from any public Mailman
> list will give you test fodder.
>
> Testing itself is not really a matter of personal preference.
> Although Mailman is not a 100% test-driven shop, Mailman 3 already has
> a *lot* of tests and Barry would like to see any new modules covered,
> I'm sure.  Also, this area is fraught with pitfalls for the developer.
>  See this thread, for example:
> http://thread.gmane.org/gmane.comp.python.devel/131395/focus=131406.
> ___
> Mailman-Developers mailing list
> Mailman-Developers@python.org
> http://mail.python.org/mailman/listinfo/mailman-developers
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Searchable Archives:
> http://www.mail-archive.com/mailman-developers%40python.org/
> Unsubscribe:
> http://mail.python.org/mailman/options/mailman-developers/mdoshayan%40gmail.com
>
> Security Policy: http://wiki.list.org/x/QIA9
>
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Developers] Google Summer of Code: Integration of Search Code

[Shayan Md]

On Wed, Mar 28, 2012 at 6:59 AM, Stephen J. Turnbull wrote:

> On Wed, Mar 28, 2012 at 4:21 AM, Terri Oda  wrote:
>
> >> Looks like archiver for mm3 is still in development stage. As far as I
> >> understand searcher depends on the srchiver, right? Not completely but
> it
> >> somewhat depends on archiver. I am not sure if searcher can be
> implemented
> >> without archiver. If possible I can implement for mm3 also.
> >
> > Searcher and archiver are interdependent *if* we want to share caches and
> > data stores, which we probably do for any installation with larger
> archives
> > where storing 2 copies vs 4 of each message would make a difference.
>  Plus,
> > many archive views may be basically searches "messages in the last month"
> > "messages which are replies to messageid $foo" etc.
>
> Actually, as far as I can see, the summary/search/index/retrieval
> functions depend only on the API for the message store.  If you
> want, you can split this into the database layer and a presentation
> layer, of course.  However, the database layer is surely going to
> have its own schema optimized for the kinds of retrieval its
> designer considers important.  If the designer emphasizes
> threads, however, she is *not* going to try to store messages in
> thread order or anything like that.  Rather, any reasonable store
> will be message-ID-addressable.
>
> The only tricky issue is that we *do* have to worry about
> message-ID collisions of truly different messages and about
> messages without message IDs, especially for converted
> historical archives.  So the API needs to be able to deal
> with these issues, probably by returning a set or sequence
> of messages.
>
> Oh, and we probably ought to have a more general notion
> of retrievable "object" rather than just messages, as some
> archive/retrieval backends may store some types of MIME
> part separately.  Hopefully these would be presented to
> us as MIME parts with external bodies and content IDs.
>
> I would guess she'll probably store messages in
> YY-MM/MSGID, or as git does in "unpacked"
> XX/... format, where XX are the first two digits
> of the hash ID, and YY... are the remaining ones).  But it
> could easily be backed by an IMAP store or something
> more specialized; we don't really care as long as it's
> object-ID-addressable.
>

Assuming that we have something like this(object-ID-addressable, If I am
not wrong, mailman3 made it possible but not yet implemented as it's part
of archiver), is it over ambitious to plan to implement indexer/searcher
for mailman3 and a REST API to use this searcher, extend client to use this
api,
and django search form along with this client api? All this independent of
archiver. Because the only part common with archiver is message retrieval
part,
If we implement whole searcher, and rest of the client code, later when
archiver is implemented message retrieval code can used in searcher. When
archiver is completely mature may we can even merge them together. Is it
possible? Or this plan has any 'non-sense' parts?


> And that's all we want to say about the archiver and the
> associated message-retrieval logic, I think.  (In fact, it occurs to
> me that maybe we should say "RFC 3501" and be done with
> it.  I don't mean that we necessarily implement IMAP protocol
> per se, but some subset of its functionality probably is what we
> need from an archiver.)
>
> Then the schema-specific stuff will use hash IDs to represent
> message objects in a portable but schema-specific way.  As
> it's schema-specific, I don't really see how data structures
> can be shared by different searchers.
>
> So I would say not to worry about the archiver side at all.  If
> large installations want to implement specialized message-
> retrieval, bully for them.  But we can go with simple backends,
> maildir, mbox, and maybe IMAP, I think.
> ___
> Mailman-Developers mailing list
> Mailman-Developers@python.org
> http://mail.python.org/mailman/listinfo/mailman-developers
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Searchable Archives:
> http://www.mail-archive.com/mailman-developers%40python.org/
> Unsubscribe:
> http://mail.python.org/mailman/options/mailman-developers/mdoshayan%40gmail.com
>
> Security Policy: http://wiki.list.org/x/QIA9
>
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1

[Shayan Md]

On Thu, Mar 29, 2012 at 1:07 PM, Odhiambo Washington wrote:

>
>
> On Thu, Mar 29, 2012 at 10:33, Shayan Md  wrote:
>
>>
>>
>> On Thu, Mar 29, 2012 at 12:28 PM, Odhiambo Washington > > wrote:
>>
>>> On Wed, Mar 28, 2012 at 22:31, Florian Fuchs  wrote:
>>>
>>> > Hi Odhiambo,
>>> >
>>> > Am 28.03.12 18:47, schrieb Odhiambo Washington:
>>> > > One more thing:
>>> > >
>>> > > In settings.py, I have this:
>>> > >
>>> > > REST_SERVER = 'http://192.168.40.252:8001'
>>> > >
>>> > > However, this doesn't seem to be respected when I do runserver:
>>> > >
>>> > > [root@jaribu] /usr/home/wash/Tools/Mailman/MM3/postorius/dev_setup#
>>> > > python manage.py runserver
>>> > > Validating models...
>>> > >
>>> > > 0 errors found
>>> > > Django version 1.4, using settings 'dev_setup.settings'
>>> > > Development server is running at http://127.0.0.1:8000/
>>> > > Quit the server with CONTROL-C.
>>> > >
>>> > >
>>> > > [root@jaribu] /usr/home/wash# sockstat -l | grep 800
>>> > > root python 77906 3  tcp4   127.0.0.1:8000
>>> > > <http://127.0.0.1:8000>*:*
>>> > > root python 14108 43 tcp4   127.0.0.1:8001
>>> > > <http://127.0.0.1:8001>*:*
>>> > >
>>> > > Since I am not using the server as a Desktop, I need a way to access
>>> it
>>> > > remotely, not via 127.0.0.1
>>> >
>>> > The REST_SERVER setting defines the location of Mailman's rest API
>>> > (which is frequently accessed by postorius), *not* the address of
>>> > postorius itself. The API can only be accessed from localhost, so the
>>> > setting has to be 'http://localhost:8001'.
>>> >
>>> > If you'd like to access postorius from a different machine as the one
>>> > you're running it on, that's no problem:
>>> >
>>> > Just run the development server like this and you're good to go:
>>> >
>>> > python manage.py runserver 192.168.x.xxx:8000
>>> >
>>> > (Don't do that on a machine that is exposed to the web though, since
>>> > Django's dev server is not meant to be run in a production
>>> environment.)
>>> >
>>> > Hope that helps!
>>> >
>>> > Florian
>>> >
>>> >
>>>
>>> My current quest is to see what MM3 web UI looks like, but it appears I
>>> am
>>> still way behind.
>>> I get these errors in the backend when I run posturious and try to access
>>> it:
>>>
>>> http://bit.ly/H2rDuW
>>>
>> Looks like you didn't start mailman server. Go through this[1] page to
>> setup mailman3.
>>
>> [1]
>> http://wiki.list.org/display/DEV/A+5+minute+guide+to+get+the+Mailman+web+UI+running
>>
>>
> Maybe and maybe not, as I was following this very guide!
>
> [wash@jaribu ~/public_html]$ ps ax | grep mailman
> 70295  ??  Is  0:00.40 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/master
> 70298  ??  S   0:01.52 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner
> --runner=news:0:1
> 70299  ??  S   0:01.57 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=in:0:1
> 70300  ??  S   0:01.46 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner
> --runner=digest:0:1
> 70301  ??  S   0:01.49 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner
> --runner=pipeline:0:1
> 70302  ??  S   0:01.45 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner
> --runner=archive:0:1
> 70303  ??  S   0:01.46 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=out:0:1
> 70304  ??  I   0:00.41 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner
> --runner=retry:0:1
> 70305  ??  S   0:01.17 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner
> --runner=rest:0:1
> 70306  ??  S   0:01.46 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner
> --runner=bounces:0:1
> 70307  ??  S

Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1

[Shayan Md]

On Thu, Mar 29, 2012 at 1:07 PM, Odhiambo Washington wrote:

>
>
> On Thu, Mar 29, 2012 at 10:33, Shayan Md  wrote:
>
>>
>>
>> On Thu, Mar 29, 2012 at 12:28 PM, Odhiambo Washington > > wrote:
>>
>>> On Wed, Mar 28, 2012 at 22:31, Florian Fuchs  wrote:
>>>
>>> > Hi Odhiambo,
>>> >
>>> > Am 28.03.12 18:47, schrieb Odhiambo Washington:
>>> > > One more thing:
>>> > >
>>> > > In settings.py, I have this:
>>> > >
>>> > > REST_SERVER = 'http://192.168.40.252:8001'
>>> > >
>>> > > However, this doesn't seem to be respected when I do runserver:
>>> > >
>>> > > [root@jaribu] /usr/home/wash/Tools/Mailman/MM3/postorius/dev_setup#
>>> > > python manage.py runserver
>>> > > Validating models...
>>> > >
>>> > > 0 errors found
>>> > > Django version 1.4, using settings 'dev_setup.settings'
>>> > > Development server is running at http://127.0.0.1:8000/
>>> > > Quit the server with CONTROL-C.
>>> > >
>>> > >
>>> > > [root@jaribu] /usr/home/wash# sockstat -l | grep 800
>>> > > root python 77906 3  tcp4   127.0.0.1:8000
>>> > > <http://127.0.0.1:8000>*:*
>>> > > root python 14108 43 tcp4   127.0.0.1:8001
>>> > > <http://127.0.0.1:8001>*:*
>>> > >
>>> > > Since I am not using the server as a Desktop, I need a way to access
>>> it
>>> > > remotely, not via 127.0.0.1
>>> >
>>> > The REST_SERVER setting defines the location of Mailman's rest API
>>> > (which is frequently accessed by postorius), *not* the address of
>>> > postorius itself. The API can only be accessed from localhost, so the
>>> > setting has to be 'http://localhost:8001'.
>>> >
>>> > If you'd like to access postorius from a different machine as the one
>>> > you're running it on, that's no problem:
>>> >
>>> > Just run the development server like this and you're good to go:
>>> >
>>> > python manage.py runserver 192.168.x.xxx:8000
>>> >
>>> > (Don't do that on a machine that is exposed to the web though, since
>>> > Django's dev server is not meant to be run in a production
>>> environment.)
>>> >
>>> > Hope that helps!
>>> >
>>> > Florian
>>> >
>>> >
>>>
>>> My current quest is to see what MM3 web UI looks like, but it appears I
>>> am
>>> still way behind.
>>> I get these errors in the backend when I run posturious and try to access
>>> it:
>>>
>>> http://bit.ly/H2rDuW
>>>
>> Looks like you didn't start mailman server. Go through this[1] page to
>> setup mailman3.
>>
>> [1]
>> http://wiki.list.org/display/DEV/A+5+minute+guide+to+get+the+Mailman+web+UI+running
>>
>>
> Maybe and maybe not, as I was following this very guide!
>
> [wash@jaribu ~/public_html]$ ps ax | grep mailman
> 70295  ??  Is  0:00.40 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/master
> 70298  ??  S   0:01.52 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner
> --runner=news:0:1
> 70299  ??  S   0:01.57 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=in:0:1
> 70300  ??  S   0:01.46 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner
> --runner=digest:0:1
> 70301  ??  S   0:01.49 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner
> --runner=pipeline:0:1
> 70302  ??  S   0:01.45 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner
> --runner=archive:0:1
> 70303  ??  S   0:01.46 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=out:0:1
> 70304  ??  I   0:00.41 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner
> --runner=retry:0:1
> 70305  ??  S   0:01.17 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner
> --runner=rest:0:1
> 70306  ??  S   0:01.46 /usr/local/bin/python
> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner
> --runne

Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1

[Shayan Md]

On Thu, Mar 29, 2012 at 12:28 PM, Odhiambo Washington wrote:

> On Wed, Mar 28, 2012 at 22:31, Florian Fuchs  wrote:
>
> > Hi Odhiambo,
> >
> > Am 28.03.12 18:47, schrieb Odhiambo Washington:
> > > One more thing:
> > >
> > > In settings.py, I have this:
> > >
> > > REST_SERVER = 'http://192.168.40.252:8001'
> > >
> > > However, this doesn't seem to be respected when I do runserver:
> > >
> > > [root@jaribu] /usr/home/wash/Tools/Mailman/MM3/postorius/dev_setup#
> > > python manage.py runserver
> > > Validating models...
> > >
> > > 0 errors found
> > > Django version 1.4, using settings 'dev_setup.settings'
> > > Development server is running at http://127.0.0.1:8000/
> > > Quit the server with CONTROL-C.
> > >
> > >
> > > [root@jaribu] /usr/home/wash# sockstat -l | grep 800
> > > root python 77906 3  tcp4   127.0.0.1:8000
> > > *:*
> > > root python 14108 43 tcp4   127.0.0.1:8001
> > > *:*
> > >
> > > Since I am not using the server as a Desktop, I need a way to access it
> > > remotely, not via 127.0.0.1
> >
> > The REST_SERVER setting defines the location of Mailman's rest API
> > (which is frequently accessed by postorius), *not* the address of
> > postorius itself. The API can only be accessed from localhost, so the
> > setting has to be 'http://localhost:8001'.
> >
> > If you'd like to access postorius from a different machine as the one
> > you're running it on, that's no problem:
> >
> > Just run the development server like this and you're good to go:
> >
> > python manage.py runserver 192.168.x.xxx:8000
> >
> > (Don't do that on a machine that is exposed to the web though, since
> > Django's dev server is not meant to be run in a production environment.)
> >
> > Hope that helps!
> >
> > Florian
> >
> >
>
> My current quest is to see what MM3 web UI looks like, but it appears I am
> still way behind.
> I get these errors in the backend when I run posturious and try to access
> it:
>
> http://bit.ly/H2rDuW
>
Looks like you didn't start mailman server. Go through this[1] page to
setup mailman3.

[1]
http://wiki.list.org/display/DEV/A+5+minute+guide+to+get+the+Mailman+web+UI+running

>
>
> --
> Best regards,
> Odhiambo WASHINGTON,
> Nairobi,KE
> +254733744121/+254722743223
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> I can't hear you -- I'm using the scrambler.
> Please consider the environment before printing this email.
>
> ___
> Mailman-Developers mailing list
> Mailman-Developers@python.org
> http://mail.python.org/mailman/listinfo/mailman-developers
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Searchable Archives:
> http://www.mail-archive.com/mailman-developers%40python.org/
> Unsubscribe:
> http://mail.python.org/mailman/options/mailman-developers/mdoshayan%40gmail.com
>
> Security Policy: http://wiki.list.org/x/QIA9
>
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Developers] Google Summer of Code: Integration of Search Code

[Shayan Md]

On Tue, Mar 27, 2012 at 1:11 AM, Toshio Kuratomi  wrote:

> On Mon, Mar 26, 2012 at 04:57:44PM +0530, Shayan Md wrote:
> > Hi,
> >
> > I am Shayan, I am doing my masters from IISc Bangalore. I want to take
> part
> > in GSoC from mailman organization. I have fairly good experience in
> python.
> > I worked on whoosh library for my own project. I have experience with
> > django also.
> >
> > I am planning to work on integrating systers search code into mailman. I
> > believe for whole summer this task alone is very small. I'll include
> couple
> > of more tasks in the proposal.
> >
> > I went through search code. Code looks pretty standard. As far I
> understood
> >
> > mailman.Searcher.IndexSchema has whoosh schema
> > mailman.Seracher.Indexer contains indexing functions which are later used
> > in genindex.py
> > mailman.Seracher.Mailocate has search function for indexed content
> > generated by genindex.py
> >
> > mailman.bin.genindex.main() is the main function which indexes the
> archives
> >
> > I am still trying to figure out how mailman client library interacts with
> > mailman server. I know how to use client library but I couldn't
> understand
> > internal working of mailman server. I have been reading the code but I
> > wasn't able understand much. It would be awesome if you can point me to
> any
> > documentation to understand this. Some api documentation or anything to
> > understand code.
> >
> Is this integration to be done with mailman2 or mailman3?
>
> In mailman3, the archivers are separated from the mailman core.
>
I was working on mm3. But systers' indexer/searcher was implemented for
mailman2. So it must be easy for to integrate it with mm2.

Looks like archiver for mm3 is still in development stage. As far as I
understand searcher depends on the srchiver, right? Not completely but it
somewhat depends on archiver. I am not sure if searcher can be implemented
without archiver. If possible I can implement for mm3 also.

>
> -Toshio
>
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

[Mailman-Developers] Google Summer of Code: Integration of Search Code

[Shayan Md]

Hi,

I am Shayan, I am doing my masters from IISc Bangalore. I want to take part
in GSoC from mailman organization. I have fairly good experience in python.
I worked on whoosh library for my own project. I have experience with
django also.

I am planning to work on integrating systers search code into mailman. I
believe for whole summer this task alone is very small. I'll include couple
of more tasks in the proposal.

I went through search code. Code looks pretty standard. As far I understood

mailman.Searcher.IndexSchema has whoosh schema
mailman.Seracher.Indexer contains indexing functions which are later used
in genindex.py
mailman.Seracher.Mailocate has search function for indexed content
generated by genindex.py

mailman.bin.genindex.main() is the main function which indexes the archives

I am still trying to figure out how mailman client library interacts with
mailman server. I know how to use client library but I couldn't understand
internal working of mailman server. I have been reading the code but I
wasn't able understand much. It would be awesome if you can point me to any
documentation to understand this. Some api documentation or anything to
understand code.

Thanks

Shayan.
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9