Hi,
For those of you that don't know I am currently working on a archive
component for Mailman as part of my degree. The interface to the archive
shall be based on the ideas in Ka-Ping Yee's paper on his Zest
prototype. Over the past two weeks I have been looking at requirements
and have the f
On Mon, 27 Oct 2003, Iain Bapty wrote:
>6. allow for full-text searching of the archives.
>7. allow for filtering by date, author, and/or topic.
> The minimum I am planning on doing is the first 5 functional
> requirements
> Which of the functional requirements, 6 to 13, do you feel are t
I have the following at my current web hosting account:
MailMan Version 2.1.2
Pipermail 0.09
cPanel Version 7.4.2
MySQL Version 4.0.15
PHP Version 4.3.3
What do I need to do to control the look and feel of the Archives?
Specifically, I have private archival set on. I want to remove or
suppress th
On Mon, Oct 27, 2003 at 12:00:57PM +, Iain Bapty wrote:
> Any feedback is very much appreciated. Thanks in advance.
My requirement list is at http://www.amk.ca/ng-arch/ArchiverRequirements .
The ng-arch code is incomplete, but if it would be helpful (and you're
allowed to use it), let me know
Iain wrote:
5. provide an interface that threads discussions by e-mail replies.
We might already have some Python code that does this (albeit in a
format quite different from Unix mailbox), based on message-IDs.
Do you think you may be interested in it?
8. be MIME aware.
I would strongly sug
Iain said:
>1. store email discussions.
Iain,
To me, this is the single most important part. How do you intend to
store the messages?
Maybe others don't give a fig but I think that if archived messages were
to be stored in an easy-to-access database then life would be good. All
of the wond
On Mon, 2003-10-27 at 15:06, Kevin McCann wrote:
> To me, this is the single most important part. How do you intend to
> store the messages?
>
> Maybe others don't give a fig but I think that if archived messages were
> to be stored in an easy-to-access database then life would be good.
I agree
On Mon, 2003-10-27 at 15:12, Barry Warsaw wrote:
> On Mon, 2003-10-27 at 15:06, Kevin McCann wrote:
>
> > To me, this is the single most important part. How do you intend to
> > store the messages?
> >
> > Maybe others don't give a fig but I think that if archived messages were
> > to be stored
Barry Warsaw wrote:
On Mon, 2003-10-27 at 15:06, Kevin McCann wrote:
To me, this is the single most important part. How do you intend to
store the messages?
Undecided, I am only just starting the development stage now
(overlapping with the end of my requirements). This is a decision I will
On Mon, 2003-10-27 at 16:37, Kevin McCann wrote:
> I'd love to have these database fields in a messages table at my
> disposal:
>
> id (unique to system, not message-id)
How do we calculate this? It probably ought to be globally unique, or
at least locally unique to a Mailman installation. (T
On Mon, 2003-10-27 at 16:44, Iain Bapty wrote:
> Twisted eh? I will have to look into that.
Indeed. I'm using it in my Mailman3 experiments, and I think while
Twisted is a big package, it gives us a lot of bang for the buck.
> >Also, I really want the next generation archiver to do everything
>
On Mon, Oct 27, 2003 at 12:00:57PM +, Iain Bapty wrote:
> Which of the functional requirements, 6 to 13, do you feel are the most
> important?
I think they are all quite basic. I think personally 10 and 12 are
'should-haves' in my opinion.
Also have a look at the "SMART Archiver" project,
h
On Mon, 2003-10-27 at 17:08, PieterB wrote:
> Also have a look at the "SMART Archiver" project,
> http://sourceforge.net/projects/smartarchiver/
>
> A replacement for the standard GNU Mailman archiver that
> supports attachments, searching, date selection, message
> editing and
On Mon, Oct 27, 2003 at 05:28:50PM -0500, Barry Warsaw wrote:
> > Also have a look at the "SMART Archiver" project,
> > http://sourceforge.net/projects/smartarchiver/
> I didn't know about that one!
It's a similar university project of the Eindhoven University of
Technology. The project has just
On Mon, 2003-10-27 at 17:46, PieterB wrote:
> It's a similar university project of the Eindhoven University of
> Technology. The project has just been finished and I assume all
> sources are/will be available. I saw the author upload the code to
> sf.net, and probably our host gewis.nl will host
and I'm working on an update of that based on some new ideas I have.
stay tuned. (but don't hold your breath, not these days...)
FWIW, I vote for storing it in a database. By using MyISAM files and
splitting on listname/time, you can build lots of smaller files and use
merge tables to dynamical
PieterB wrote:
I think they are all quite basic. I think personally 10 and 12 are
'should-haves' in my opinion.
I may have underestimated the time it will take me to implement them,
but I am quite inexperienced in projects of this nature. The closest I
have done is some ASP.NET and VB.NET fro
Hi,
I should add
8. be MIME aware.
8'. be I18N.
Cheers,
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
On Mon, 2003-10-27 at 18:33, Chuq Von Rospach wrote:
> and I'm working on an update of that based on some new ideas I have.
> stay tuned. (but don't hold your breath, not these days...)
I can imagine, what with G5's, Windows iTunes and Panther. :)
> FWIW, I vote for storing it in a database. By
On Oct 27, 2003, at 3:47 PM, Barry Warsaw wrote:
MyISAM tables aren't transactional. Would we care? Probably not for
this application, but for my Mailman 3 experiments, I'm storing list
and
user data in transactional BerkeleyDB tables because I definitely think
we want that extra safety.
very
> exhaustion. Or you could store everything in an mbox file with a file
> offset index. Or perhaps store everything to an nntp server (Twisted
> would make a nice platform for this ).
> ...
> Also, I really want the next generation archiver to do everything
> through cgi (or equivalent programmat
On Mon, 2003-10-27 at 19:02, David Champion wrote:
> I'm hoping to get these materials better integrated and documented soon,
> maybe once I'm back from LISA. But in case anyone is interested in
> working with them, I've put them up on the web, linked from the above
> URL. If this were to be a sta
Chuq said:
> very unlikely for archives. And with mySQL 4, you can use one of the
> newer formats with row locking and transactions. they do intermingle
> nicely.
Yes. MySQL can handle transactions just fine. For more info:
http://www.mysql.com/doc/en/ANSI_diff_Transactions.html
- Kevin
___
On Mon, 27 Oct 2003 15:12:29 -0500
Barry Warsaw <[EMAIL PROTECTED]> wrote:
> On Mon, 2003-10-27 at 15:06, Kevin McCann wrote:
> There are a couple of ways I could see slicing things. You could
> store one message per file a la MH, with some elaboration to avoid
> inode exhaustion. Or you could
On Mon, 27 Oct 2003 17:28:50 -0500
Barry Warsaw <[EMAIL PROTECTED]> wrote:
> On Mon, 2003-10-27 at 17:08, PieterB wrote:
> When Mailman decorates a message for copying to the list, I want to be
> able to include a link to the archived message in the footer. The
> problem is that there is little
On Mon, 27 Oct 2003 19:16:35 -0500
Barry Warsaw <[EMAIL PROTECTED]> wrote:
> Which does point to an alternative direction -- maybe we don't need
> any direct connection to an html archive. Maybe the archiver should
> just be a separate process that reads messages from the NNTP interface
> a MM3
On Tue, 28 Oct 2003 00:44:43 -0500
J C Lawrence wrote:
> On Mon, 27 Oct 2003 19:16:35 -0500 Barry Warsaw <[EMAIL PROTECTED]>
> wrote:
>> Which does point to an alternative direction -- maybe we don't need
>> any direct connection to an html archive. Maybe the archiver should
>> just be a separa
27 matches
Mail list logo
