[Systers-dev] No User-Interface Support for Mailman3

[Anne Gunn]

Kanika,

I'm not sure this is as big a problem as it at first appears.

I am assuming that mailman is written to be 'loosely coupled' between the UI and the commandline engine -- that is, the UI is used to gather information from the user that is then pulled together to drive one or more commandline interactions with the engine.  That way, everything in the engine can be tested (and, eventually, tested in a automated way) without either waiting for the UI to be written or wading through the UI time after time.

It is fairly common, with implementations like this, if the commandline/api is changing a lot, to get everything sorted out and working via the commandline interface before implementing or changing the UI.

At the same time, it is possible, using a specification of the new engine to re-tool a UI in order to emit the new commandline syntax even if that commandline interface isn't actually working yet.

So, do you think this is a timing issue?  That is, the mailman group is getting the 3.0 engine working and then will come out with a reference UI implementation?

Or do you think this is a decision that they are going to get out of the business of supplying a UI implementation altogether?

In either case, it should be possible to proceed with the integration project by modifying the existing UI to emit 3.0 syntax.  Then, if the mailman group eventually delivers the 'official' UI, we push our features into it.  Or, if they are out of the business of presenting a UI, we offer ours as a reference implementation.

Does that make sense?  Or am I completely off base?

ag

--- kanika.krikan at gmail.com wrote:

From: kanika vats <kanika.krikan at gmail.com>
To: systers-dev+userinterfac at systers.org
Subject: [Systers-dev] No User-Interface Support for Mailman3
Date: Tue, 20 Apr 2010 22:10:53 +0530

Hi,
While going through the Mailman repository on launchpad,I got to know that
the latest Beta release of Mailman3 has no User-Interface support.Thus at
present it consists of core Mailman engine that can be run only via command
line.

Our Dlist feature on the other hand depends on various customized additions
to User Interface (like 'other incoming email address' and 'Subscribe to new
mails' option at member configuration page and similar other options added
by Systers for Dlist like Essays etc on listinfo page and listcreation
page.)

Now my question is that when Mailman people have not decided on their user
interface for Mailman3 yet then how are we suppose to proceed with the
integration process that depends hugely on customizing the web interface to
suit the Dlist needs.

Thanks,

-- 
Best Regards
Kanika Vats


To unsubscribe from this conversation, send email to <systers-dev+userinterfac+unsubscribe at systers.org> or visit <http://systers.org/mailman/options/systers-dev?override=107&preference=0>
To contribute to this conversation, use your mailer's reply-all or reply-group command or send your message to systers-dev+userinterfac at systers.org
To start a new conversation, send email to <systers-dev+new at systers.org>
To unsubscribe entirely from systers-dev, send email to <systers-dev-request at systers.org> with subject unsubscribe.