<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#ffffff">
Hi,<br>
<br>
So far, I have been able to run the basic functionalities of
archive-ui for mm3. Moving forward, I would like to discuss these
issues. Please give your feedback.<br>
<br>
<b>archive-ui</b> -> Yian’s work on archive-ui as part of last
year’s GSOC on mailman 2.1<br>
<b>pipermail</b> -> Pipermail on mailman 3<br>
<br>
1. In pipermail, all the static htmls generated for each
message(that goes into archives) are arranged in directories
corresponding to different months. <br>
Whereas in archive-ui, all the conversations are stored in a
single directory. The reason is that since a conversation can span
across months, it is somewhat ambiguous where to keep that
conversation.<br>
<br>
If any of you think that arranging conversations by months offers
advantage in any form, then I can do so. But in that case, the whole
conversation will be kept in the month when its first message
arrives.<br>
<br>
2. Readable urls: URL corresponding to a conversation can be created
from subject of the first message of a conversation (in the same way
as various blog sites do).<br>
<br>
Also, in archive-ui, when a message is archived, all the
conversations are generated again. Ideally, we should do minimum
amount of work on archiving a message. I am trying to work this out
too.<br>
<br>
Thanks, <br>
Dushyant<br>
<br>
<br>
<br>
</body>
</html>