I'm interested in contributing to the Hyperkitty archiver. Specifically,
it looks like some requested features for Hyperkitty include rss syndication
for entire mailing lists/specific users/specific threads, and the ability
to view entire threads as plaintext and download that plaintext.
We
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
On Mar 24, 2015, at 02:38 PM, Andrew Stuart wrote:
I haven’t really worked on an open source project before.
You're fitting right in though! :)
It wouldn’t make sense to come up with an idea, write some code, submit it
and have it rejected because it’s not OK with the project owners and doesn’t
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
I have submitted a proposal on Google Melange. Any feedback I could get
about my project constraints would be great!
Thanks,
David
On Tue, Mar 24, 2015 at 8:23 AM, Aurelien Bompard aurel...@bompard.org
wrote:
I'm interested in contributing to the Hyperkitty archiver. Specifically,
it looks
Barry Warsaw writes:
Keep feature and bug branches small if possible, and concise, such
that they only implement the feature your working on or fix the
reported bug. A little bit of extraneous stuff might be okay if it
improves readability, but don't go overboard.
I'd like to gloss this
On Mar 23, 2015, at 08:39 PM, Andrew Stuart wrote:
Any thoughts on how we could integrate with LDAP?
The intent is that the user database could be backed by, or augmented by LDAP,
although that is currently a goal, not reality.
Maybe of Mailman had some sort of event notification hook system
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
(Sorry Stephen)
-- Forwarded message --
From: Akshay Shah y1dot...@gmail.com
Date: Wed, Mar 25, 2015 at 12:21 AM
Subject: Re: [Mailman-Developers] GSoC 15 - Interested in contributing to
Postorius
To: Stephen J. Turnbull step...@xemacs.org
I wanted to work on Feature request:
On Mar 25, 2015, at 01:02 PM, Stephen J. Turnbull wrote:
(1) Suppose you change a small function whose formatting is not PEP 8
conformant (or otherwise so ugly you can't help fixing it -- of
course, check blame first, if Barry committed those lines, have
your eyes checked instead :-).
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
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
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
Sent this email to Aurélien's personal email by mistake the first time
(sorry Aurélien!). I'll get used to the mailing list evenually
There's always been demand for a way to download a list archive as an
mbox file
This is a feature I am interested in pursuing. From a very (very) high
level,
@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
@barry, @stephen, @terri
I know this is a wall of text (sorry) but if you have time I’d be interested
to hear your thoughts as Dynamic Sublists are in the GSOC projects list for
this year.
as
On 20 Mar 2015, at 9:53 am, Andrew Stuart andrew.stu...@supercoders.com.au
wrote:
Refer to the
16 matches
Mail list logo
