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
Any thoughts on how we could integrate with LDAP?
I’d be happy to authenticate against LDAP but that leaves the open question of
how to synchronize the Mailman user database with the LDAP server.
Maybe of Mailman had some sort of event notification hook system for when users
add/edit/delete. O
Andrew Stuart writes:
> LDAP seems like a pretty configuration heavy thing to put in to a
> standlone Mailman system. I’m currently researching to find some
> sort of minimla/lightweight LDAP integration approach.
IMHO, what we really want (besides a pony, do you raise ponies?) is
"enterprise
> Oops. Looks like I'd forgotten to push them. They should now be
> available in
> lp:~barry/mailman/subpolicy
>
Got it.
OK, the SubscriptionWorkflow seems correct in implementation but it has
almost no tests, so I'll write some.
But there's something else: the SubscriptionWorkflow class does no
On Mar 23, 2015, at 12:17 PM, Aurelien Bompard wrote:
>But there's something else: the SubscriptionWorkflow class does not seem to
>be used anywhere except in the current unit test. Am I missing something ?
Nope. It needs to be hooked up. The branch wasn't merged because it was
incomplete.
Che
> Nope. It needs to be hooked up. The branch wasn't merged because it was
> incomplete.
Ah alright, I'm just adding some tests but it would probably be better you
did the hooking up... (or I'll need a good amount of guidance)
Thanks
Aurélien
___
Mailma
> > Nope. It needs to be hooked up. The branch wasn't merged because it was
> > incomplete.
Oh, and the _send_confirmation method is also not implemented. Could
you briefly explain how does the confirmation system work? (or point
me to the doc, I didn't find it)
Thanks
Aurélien
Hi
My name is Akshay Shah. I'm currently pursuing my undergraduate degree at
PES University, Bangalore (India). I have 2 years of experience with python
and 3 years of experience with Javascript and HTML.
I am interested in contributing to the Postorius Web UI. Some of the ideas
on the 'Ideas Page
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.
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
> As for the `password` key: It's recognized by mailman.client and
> exposed within the mlist instance's `requests` property. But it's used
> nowhere in postorius and I would be surprised if it's used anywhere in
> hyperkitty (Aurélien...?). I guess it can go away.
No problem, I don't use pending
Hi
My name is Akshay Shah. I'm currently pursuing my undergraduate degree at
PES University, Bangalore (India). I have 2 years of experience with python
and 3 years of experience with Javascript and HTML.
I am interested in contributing to the Postorius Web UI. Some of the ideas
on the 'Ideas Page
Akshay Shah writes:
> My name is Akshay Shah.
Pleased to meet you, Akshay. Welcome to Mailman!
> 1. Can the Dashboard and Subscriber profile page be done together
> within the GSoC timeline?
I think this would not be useful as the users' tasks are quite
different. It's better to pick
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
I haven’t really worked on an open source project before.
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 fit
with project goals.
So at what point do I know that if I write some code that the
On 2015-03-22 10:23 PM, David Udelson wrote:
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 pl
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
Hi Andrew,
For starters, make sure you check
https://pythonhosted.org/mailman/src/mailman/docs/STYLEGUIDE.html and
https://google-styleguide.googlecode.com/svn/trunk/pyguide.html.
Cheers,
Ana
On Tue, Mar 24, 2015 at 5:38 AM, Andrew Stuart <
[email protected]> wrote:
> I haven’t
On 2015-03-23 8:38 PM, Andrew Stuart wrote:
I haven’t really worked on an open source project before.
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 fit
with project goals.
So at what poin
Thanks Terri,
>>Unfortunately, it is true that the lack of process has led people to put a
>>lot of work into stuff that never got merged.
I’m mainly just trying to avoid this - writing stuff that doesn’t get merged.
I figure step one is to get a quick nod from one of the architects/project
l
On 2015-03-23 10:38 PM, Andrew Stuart wrote:
The question is, who do I ask for confirmation that the idea is solid and will
be merged assuming all requirements are met for code
quality/testing/documentation?
For core stuff you particularly want Barry's blessing, for Hyperkitty it's
Aurelian,
@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
22 matches
Mail list logo
