Andrew Stuart writes:
> What does "batteries included" mean in this context?
That you shouldn't need to fetch the archivers from a separate archive
or repo to configure them. Sure, you *could* register them as plugins
and have a button to fetch them from PyPI (or just do it if the user
selects
Agreed Stephen.
It would be good if only configuration was required to drive the archivers even
though they are only examples/provisional/contrib whatever.
I’m hoping that projects like Hyperkitty and my server won’t need installers to
touch the Mailman source code at all to get data flowing f
On Mar 25, 2015, at 01:07 PM, Stephen J. Turnbull wrote:
>A nice option would be that in the admin interface, the admin could
>tick a box saying "show me contrib archivers" and then tick and
>configure the appropriate one. The instructions for contrib
>configurations would say that Mailman is not
Barry Warsaw writes:
> These [example? archivers] are all pretty interesting. We'd have
> to think about whether we'd want some, any, or all them in the main
> tree, which essentially means we're committing to supporting them.
>
> Alternatively, we can create a contrib directory or repo
Ba
On Mar 24, 2015, at 05:01 PM, Andrew Stuart wrote:
>@barry - would you mind confirming please you’re OK with this please?
These are all pretty interesting. We'd have to think about whether we'd want
some, any, or all them in the main tree, which essentially means we're
committing to supporting t
> Would you mind if I used the Hyperkitty POST code as the basis for an example
> POST archiver for Mailman?
Sure, no problem.
Aurélien
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-de
@barry - would you mind confirming please you’re OK with this please?
I’m going to implement some very simplistic, working, example archivers. As
discussed with Stephen, although functional, these will be “working examples”,
much like prototype.py is currently, and won’t be presented as complete
Thanks Aurélien
Would you mind if I used the Hyperkitty POST code as the basis for an example
POST archiver for Mailman?
i.e. this:
https://github.com/hyperkitty/mailman-hyperkitty/blob/master/mailman_hyperkitty/__init__.py
I’m happy to rewrite from scratch but it seems to make sense to use wha
Andrew Stuart writes:
> So do you think it might make sense to just expand the range of
> “working example archivers” i.e. like the “prototype” archiver
> currently does, instead of trying to provide something that would
> be a maintenance burden?
Yes, that sounds like an excellent plan to me
> Aurelien I’d be interested to hear your thoughts on this topic.
Well, the implementation of the archiver for HyperKitty does POST to
archive emails :
https://github.com/hyperkitty/mailman-hyperkitty/blob/master/mailman_hyperkitty/__init__.py
However, there are a few things specific to HyperKitty
So do you think it might make sense to just expand the range of “working
example archivers” i.e. like the “prototype” archiver currently does, instead
of trying to provide something that would be a maintenance burden?
That way people can see the archivers, can use them if they want but they’re
Aurelien I’d be interested to hear your thoughts on this topic.
as
On 22 Mar 2015, at 10:13 am, Andrew Stuart
wrote:
As I understand it, currently there are a few default archivers including
prototype, mhonarc and mailarchive. New archivers can be plugged in by
implementing an archiver whic
Andrew Stuart writes:
> Specifically if would be good if a Mailman admin could define in
> the Mailman config file a set of destination email addresses and
> POST urls that archive messages are sent to. This would meet many
> common archiving needs via configuration instead of code.
I think t
As I understand it, currently there are a few default archivers including
prototype, mhonarc and mailarchive. New archivers can be plugged in by
implementing an archiver which complies to the archiver interface. Not hard
but still requires coding skills.
Specifically if would be good if a Mail
14 matches
Mail list logo
