Dave
You seem to have an interest in Mailman being accessible.
Care to share some requirements/requests/tips/pointers for the various people
who are writing user interface code that talks to Mailman.
I’d like to take this sort of thing into account early in the process if
possible so now is a
At 01:51 AM 3/25/2015, Ana Badescu wrote:
Hello,
While writing my proposal I came across 2 important issues related to the
Javascript Client for the Mailman project that have yet to be raised:
2. I'd also like to make part of the project, a node.js application that
uses the Mailman Javascr
Hi guys,
I have updated my proposal for "A Dashboard for Admins/Owners/Moderators"
project.
I have tried to address the issues raised. Reviews on it are welcome.
Regards,
Shreyas Lakhe
___
Mailman-Developers mailing list
Mailman-Developers@python.org
htt
> I'm already using the "jobs" infrastructure provided by the
> django-extensions package:
> http://django-extensions.readthedocs.org/en/latest/jobs_scheduling.html
Cool. I didn't know about this extension, but it looks like it does what we
need. So the background process would be its own file in
Hello Sir,
My name is Aneesh Anil, and I'm very much interested in contributing to
Mailman 3 project. But because I don't have any prior experience in any
real world projects I am confused as to what to select.
But since I have knowledge of javascript/html with python I think I would
do better if I
> In my proposal I suggested using any of several asynchronous job queue
> libraries, such as Celery or Huey. These all use redis as a back-end.
> Because I have no experience with asynchronous job queues, I'm not sure if
> this is too much baggage for our purposes. Maybe we just don't want the
> e
