[Systers-dev] bin/newlist cannot be used to create a new list from the command line [bug]

[Robin Jeffries]

1.  I would consider adding the CLI support to be a new feature, not a bug
fix.  For various reasons (one of them being that we create about 2 new
lists a year), we have prefered to use the GUI to create new lists.  So to
keep systers running, we need to be able to create new lists with the GUI.
 Svaksha is right that we will need to fix this before we can integrate with
mailman 3.0, but we are as much delayed by the slowness of mailman 3.0
coming out as we are delayed by this not being fixed.  As Jen says, it isn't
top priority.

2.  Just to get this recorded for posterity.  We changed the name of the
base list from mailman to systers-admin because users were confused (as were
spam filters) by mail from mailman at systers.org .  I'm pretty sure (and
events seem to have confirmed) that we didn't understand all the
ramifications of making that change :-)

I haven't completely followed this thread, but is the current issue that
once someone has messed up and created this as a visible list, things go
wrong (and we need to find a way to fix these mixed up installations)? or is
it that as various folk try to bring up mailman on their system, our lack of
complete, correct instructions is keeping them from getting it working?

Robin

On Wed, Jun 2, 2010 at 7:38 AM, Jennifer Redman <jenred at gmail.com> wrote:

> On Wed, Jun 2, 2010 at 7:15 AM, स्वक्ष <vid at svaksha.com> wrote:
>
> > On Wed, Jun 2, 2010 at 05:48, Kathy Richardson <kjr at casaveracruz.com>
> > wrote:
> > >
> > > The bug statement is correct, but I think it is missing some
> information.
> > >
> > > One still needs to use bin/newlist to create the MAILMAN_SITE_LIST. (At
> >
> > True, the admin cant create a pseudo list otherwise. From this list
> > other lists are created for regular subscriptions --> the part which
> > works only from the GUI and not the Cli.  Hence, at this point  I
> > would really appreciate folks giving feedback if they were able to use
> > the CLI to create a
> > newlist. Even if you have used the GUI earlier, you can now check via
> > the cli and confirm. This will help me close the the bug. So please
> > take a few minutes to check this and give feedback.
> >
>
> In the past we used bin/withlist to create dlist enabled lists - but last
> year we moved that functionality to the gui.
>
> Anna - thanks for looking in to see if there were any quick changes you
> could do to enable the cli feature -- I had completely forgotten about the
> previous withlist requirement to create the new lists.
>
> At this point, I think it's great that we have documentation on how new
> list
> creation does not work just using bin/newlist for anything other then the
> site list - that needs to be noted on the wiki and now we have the bug open
> as well.
>
> Great!  Let's move on.  It sounds like implementing the cli feature is not
> something that can be done easily and we have other priorities at the
> moment.
>
> Svaksha if you have time -- after the dev machine is installed and
> functional -- you can investigate using the withlist option and documenting
> how to use if you'd like to use -- but I think at this point the bug needs
> to stay open, marked low-priority  -- we can change to unassigned (or
> assign
> it to me).  I think it would be a much better use of  time to start testing
> the dev.systers.org install.
>
> I'm only available intermittently this week - but starting next Tuesday
> fully available for the rest of the summer.
>
> Thanks,
> Jen
>
>
> To unsubscribe from this conversation, send email to <
> systers-dev+binnewlist+unsubscribe at systers.org<systers-dev%2Bbinnewlist%2Bunsubscribe at systers.org>>
> or visit <
> http://systers.org/mailman/options/systers-dev?override=120&preference=0>
> To contribute to this conversation, use your mailer's reply-all or
> reply-group command or send your message to
> systers-dev+binnewlist at systers.org <systers-dev%2Bbinnewlist 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.
>