I'm writing to find out the state of and philosophy surrounding pipermail
in mailman, to see if there is a productive way to provide some
code/development-time to that part of mailman.
I know there are several decent third-party archivers out there, but many
of the mailing list archives I browse r
On Mon, Mar 26, 2012 at 5:11 PM, Toshio Kuratomi wrote:
> We'd love to have work done on the archier! I know that we're ditching
> pipermail entirely and that archivers are becoming separate from the core
> mailman. What I don't know is whether mailman3 will eventually have
> a standard archive
> So if you have already developed some stuff, I
> certainly would love to see you put it on the table
> as a candidate for the Mailman 3 default
> archive web UI.
Yes. My CSLA code is on the table for MM2 or 3. It's python, and it's BSD.
More than that, if you folks want it, I'm happy to retool/r
I brought up a quick CSLA injest of some mailman-dev posts to show off some
basic features. I'm having a little trouble with the swish-e code, so the
features that depend on text-indexing arn't working at the moment (search,
author search). The current UI uses user-cookies to choose between a
2-pa
On Mar 27, 2012 5:32 AM, "Stephen J. Turnbull" wrote:
> If the archiver/web UI is going to be distributed
> *with* Mailman, Barry would probably prefer
> Storm + Django because that's what
> Mailman/Protorius (core and admin web UI, resp.) are
> using. But I imagine that's negotiable as long as
>
Thanks for the super-detailed replies... I'm separating these discussions,
so here I have some questions about licensing and bundling..
> So in some sense, CSLA needn't become *the* Mailman archiver, but it should
> definitely be *a* Mailman archiver. Then you can make all the engineering
> and
>
On Mar 27, 2012 8:47 PM, "Barry Warsaw" wrote:
> but that we're pretty far away from being
> able to bless an archiver right now.
I just want to be clear, that I'm obviously not asking for anyone to bless
a specific archiver and roll it into the distribution.
I'm trying to get some idea wha
> - Stable URLs, RFC 5064 + X-Message-ID-Hash.
> See the above links. If you can implement the
> `IArchiver.permalink()` method and ensure that even if
> completely wiped and regenerated from the
> underlying raw messages, your URLs
> will remain stable, I think you will have won. :)
This is re
On Thu, Mar 29, 2012 at 9:16 AM, Stephen J. Turnbull wrote:
> I would say you should try to retain copyright, and have the Mailman
> project distribute it with the S-BSD license under the "mere
> aggregation" clause of the GPL.
This agrees with my view of the situation as well. Which leads to th
On Apr 2, 2012 3:07 PM, "Terri Oda" wrote:
>> This agrees with my view of the situation as well. Which leads to the
>> question, is the above approach interesting/viable for Mailman-team?
>> (assuming the code does something awesome that people want)
>
> If the question is just "would you like ano
On Apr 3, 2012 8:14 PM, "Bob Puff" wrote:
> > I think it would be a mistake to bundle any archiver with mailman3.
> > Listing the available archiver options and their features and
> > shortcomings would be a better way to go.
>
> -1
>
> I think the majority of MM users will be simply using the RPM
On Apr 3, 2012 11:58 AM, "Toshio Kuratomi" wrote:
> > The question is "would you BUNDLE another archiver even if the licenses
> > don't match?"
> Where could your archiver fit into that sequence of impressions? I'm not
> entirely sure. I think that it probably couldn't be bundled into the same
This thread is slowing down my coding! :)(it's been really helpful
though all, thanks for the many perspectives!)
On Tue, Apr 3, 2012 at 11:19 PM, Terri Oda wrote:
> It occurs to me that it's perfectly reasonable to assume that people who
> *package* mailman for different distributions may c
On Apr 5, 2012 6:42 AM, "Pierre-Yves Chibon" wrote:
> So I changed to use the Message-ID of the first email of the Thread as
ThreadID.
> Problem is of course, if the admin removes the first email of a thread
> for x or y reasons, then when reloading the archives (for z or a
> reasons), we will loo
On Apr 6, 2012 10:49 AM, "Toshio Kuratomi" wrote:
> > 1) don't publish thread-ids, but just message-ids... for example, a
thread
> > URL could be allowed to reference the message-id of 'any' message in the
> > thread They could then include more than one message-id, making them
> > resiliant t
I think the last several messages covered whats-what pretty well.
Summarizing what already seems to have been reclarified a few times
excellently by others... ClearSilver List Archive is S-BSD, and will remain
so. That license allows you folks to wrap it in GPLv3 if you wish, but I
won't be doing s
Are you expecting this direct python configuration import to actually "be"
an archiver, or simply to be a configuration shim to get data to an
archiver?
Python imports are not version-dependent (like C-shlibs are), so it seems
dubious to expect an external archiver to necessarily be compatible wit
On Monday, April 9, 2012, Barry Warsaw wrote:
> So I can turn this question around and ask, what's the best way to get
> messages into ClearSilver?
>
Drop it into a Maildir, so that the version of Python we use for CSLA isn't
locked to the version of Python for MM3.
Perhaps the MM3 CSLA "handler
urse it already has
a Python wrapper, as much of eGroups.com (and some of Yahoo Groups) is
written in Python.
http://www.clearsilver.net/
--
David Jeske (N9LCA) + http://www.chat.net/~jeske/ + [EMAIL PROTECTED]
___
Mailman-Developers mailing li
On Fri, Apr 05, 2002 at 10:19:09AM -0500, Barry A. Warsaw wrote:
> >>>>> "DJ" == David Jeske <[EMAIL PROTECTED]> writes:
>
> DJ> Also, in fishing through the TODO list, I notice that adding
> DJ> some kind of templating system is still on
20 matches
Mail list logo
