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

[Anna Granudd]

Hi,
starting with the command line like Robin suggested seems like a great way
to go and something we'll need regardless if there's a new UI coming up or
not. As for the UI, like Kanika mentioned I've applied with a project
working on parts of this. Based on the research I did before submitting the
proposal, I think collaboration with the Mailman people (who btw are great
to discuss and co-operate with so listen to Terri - take the chance if you
get it!) is the what we want to do. The definition of a UI has just started
and there's plenty of things to do and decisions still to be made where we
can come with suggestions and make sure our changes can be added easily and
seamlessly. The UI will likely be build in Django with a DB storing some of
the information (such as for instance an essay or a picture maybe) and if we
can make sure this DB is an extension of ours that would make life so much
easier for us. Keeping two databases in sync might be a hassle (just keeping
the Mailman/Python pickle files and our db is sometimes a problem today)
whereas having one db for everything would simplify things. If we can
co-operate with Mailman on defining the UI I think all we within Systers
have to do is to talk to each other, discuss what we want/could do and try
to make sure this is feasible in the upcoming UI. It would be easier to make
sure our add-ons is easy to implement from the beginning than to define our
very own UI so I believe this is what we should try to do.

Thanks,
Anna

On Wed, Apr 21, 2010 at 5:03 AM, Robin Jeffries <robin at jeffries.org> wrote:

> I think it would be great to start by making all of the dlist additions
> command line callable, which would put us in good shape for future years.
>  After that (I hope this would not take all summer), proposing a UI for all
> or part of mailman (e..g., just for the admin interface, or just for the
> signup) would be a great thing.
>
> Robin
>
> On Tue, Apr 20, 2010 at 11:30 AM, Nandeep Mali <n9986.mali at gmail.com>
> wrote:
>
> > Hi,
> >
> > FWIW, I would just like to poke a bit in here!
> >
> > The best part about Mailman 3 is that it has a good separation of the
> > UI and code Mailman logic. You can use Mailman as a simple command
> > line tool, or make a fully customized 'add-on' UI through its RESTful
> > admin interface. The official Wiki mentions it:
> >
> > http://wiki.list.org/display/DEV/Web+Interface
> >
> > And the actual project at Launchpad:
> >
> > https://launchpad.net/mailmanweb
> >
> > This side project seems pretty official to me and builds on Django. Am
> > not sure how much progress has been made in it yet, but you could
> > consider using this as a  base.
> >
> > So as Anne says, best would be to get the command line support for
> > dlists in before the UI. After all, this is what the development model
> > of Mailman 3 seems like and best to stick to it. Everything should run
> > from command line with optional add on UIs. So if at all you do go
> > about building the UI, it would be nice to collaborate with this
> > "mailmanweb" project (its already using Django!).
> >
> > Kind Regards
> > Nandeep
> >
> >
> > To unsubscribe from this conversation, send email to <
> > systers-dev+userinterfac+unsubscribe at systers.org<systers-dev%2Buserinterfac%2Bunsubscribe at systers.org>
> <systers-dev%2Buserinterfac%2Bunsubscribe at systers.org<systers-dev%252Buserinterfac%252Bunsubscribe 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<systers-dev%2Buserinterfac at systers.org>
> <systers-dev%2Buserinterfac at systers.org<systers-dev%252Buserinterfac at systers.org>
> >
> > To start a new conversation, send email to <systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
> <systers-dev%2Bnew at systers.org <systers-dev%252Bnew at systers.org>>
> > >
> > To unsubscribe entirely from systers-dev, send email to <
> > systers-dev-request at systers.org> with subject unsubscribe.
> >
>
>
> To unsubscribe from this conversation, send email to <
> systers-dev+userinterfac+unsubscribe at systers.org<systers-dev%2Buserinterfac%2Bunsubscribe 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<systers-dev%2Buserinterfac at systers.org>
> To start a new conversation, send email to <systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
> >
> To unsubscribe entirely from systers-dev, send email to <
> systers-dev-request at systers.org> with subject unsubscribe.
>