Hi,
Now, I think we can get notifications pushed from the core to the ui if we
wanted, assuming the ui had some service to notify. See my previous message
on events.
Awesome! So the wui would implement a simple REST API for the core to talk to.
Ideally it should be possible to register more
On Feb 25, 2012, at 3:37 PM, Barry Warsaw wrote:
On Feb 21, 2012, at 08:10 AM, Richard Wackerbarth wrote:
On Feb 20, 2012, at 7:28 PM, Barry Warsaw wrote:
Yep, it's a big question. Something could clearly make sense in the core,
e.g. gpg keys for authentication or encryption. Other,
On Feb 21, 2012, at 08:10 AM, Richard Wackerbarth wrote:
On Feb 20, 2012, at 7:28 PM, Barry Warsaw wrote:
Yep, it's a big question. Something could clearly make sense in the core,
e.g. gpg keys for authentication or encryption. Other, specifically
ui-type data might not make as much sense in
On Wednesday, February 22, 2012 07:49 CET, Stephen J. Turnbull
step...@xemacs.org wrote:
Florian Fuchs writes:
Agreed. Django's User model most definitely covers all our
needs.
What version of Django's User model are you using? The vanilla User
is actually rather limited. Or
On Feb 23, 2012, at 4:46 PM, Florian Fuchs wrote:
Of course, if we implement such a custom backend we should do it in a
generic and reusable way. I just think making a full-blown django app for
what is usually just a .py file might be a bit overkill... But as I said:
debatable... ;-)
On Feb 22, 2012, at 03:49 PM, Stephen J. Turnbull wrote:
We do, I think. I think the core DB should be constant across
Mailman installations, and restricted to fields useful in forum
administration (ie, not restricted to mailing lists, although that
will be the main purpose of Mailman 3 at its
On Feb 23, 2012, at 5:43 PM, Barry Warsaw wrote:
The counter argument is that the core's database should only contain the data
that is needed to do its function.
Yet another argument would be:
The MM suite can be partitioned logically into a message handler, an archiver,
an
On Friday, February 17, 2012 20:41 CET, Florian Fuchs f...@state-of-mind.de
wrote:
[1] https://github.com/lloyd/myfavoritebeer.org/
[2] https://github.com/mozilla/django-browserid
[3] https://github.com/mozilla/django-browserid
Sorry, I posted the second link twice. That should be:
On Feb 17, 2012, at 1:41 PM, Florian Fuchs wrote:
1) Browserid is very convenient, but I wouldn't rely on it as the only means
to log into the MM web ui.
I agree. It is a reasonable scheme to support, but we need to have
authentication done on a plug-in basis. Structurally, the underlying
On Feb 16, 2012, at 10:23 PM, Aamir Khan wrote:
I was going through ideas page of mailman for GSoC 2012, and i found this
project of integrating the browser id with mailman. I guess, mailman
community members should already have some discussion about this
integration. Can you tell me some
10 matches
Mail list logo
