On May 26, 2015, at 01:26 PM, Stephen J. Turnbull wrote:
>I really think we should reserve 3.1 for fixing major problems (and I expect
>to have a lot of user-noticable problems, starting with lots of Mailman 2
>functionality that went unimplemented for one reason or another).
+1.
I do intend to
Hi !
On Tue, May 26, 2015 at 6:20 AM, Barry Warsaw wrote:
>Bhavesh, can you describe why a task model in the core is a better way to
> go?
>
>
I thought of implementing the model in core in the first place because I
thought it may
would have been good to have the user tasks available on hand eve
Barry Warsaw writes:
> On May 25, 2015, at 05:27 PM, Abhilash Raj wrote:
>
> >I think a better idea would be to keep everything in Postorius.
+1 I really think we should reserve 3.1 for fixing major problems (and
I expect to have a lot of user-noticable problems, starting with lots
of Mailman
On May 25, 2015, at 05:27 PM, Abhilash Raj wrote:
>I think a better idea would be to keep everything in Postorius. Held messages
>and subscription requests are already available through the REST API, and
>hence can easily be used to create the `Tasks` model in Postorius. Barry,
>Florian thoughts?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 25 May 2015 17:19:17 +0530
Bhavesh Goyal wrote:
> Widget Specifications:
>
> The Tasks widget gives the admin, a list of pending tasks which
> require his immediate attention on the dashboard. The tasks
> particularly include those of 'Hel
Widget Specifications:
The Tasks widget gives the admin, a list of pending tasks which require his
immediate attention on the dashboard. The tasks particularly include those
of 'Held Messages' (pending for moderation) and 'Subscription Requests'.
A Task is added to the To - Do List for admin autom
