[Mailman-Developers] Configurable options in Mailman 3

[Barry Warsaw]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Apr 5, 2008, at 4:04 PM, Stephen J. Turnbull wrote:
> Mark Sapiro writes:
>
>> What are you asking, and what is the issue?
>>
>> Upon rereading, I think your question is "is it possible to have
>> OLD_STYLE_PREFIXING = No in mm_cfg.py, but use the old style for
>> selected lists through some list setting". Unfortunately, the answer
>> to that is no.
>
> I don't understand why it should ever be the case that a configuration
> option that makes sense to configure per-list should be not
> configurable per-list.

Agreed.

> How is Mailman 3 handling this?

On several levels I think.  The style system is basically a way to  
organize the settings of MailingList attributes.  These attributes are  
defined in an interface and in the default storage backend, as columns  
on the MailingList table.  There is a default style that basically  
maps Defaults.py values (i.e the old mm_cfg.py/Defaults.py.in stuff)  
to attribute settings.  Ultimately I'd like to be able to get rid of  
Defaults.py entirely for per-list configuration defaults and use it  
just for site-wide settings.  Then the style system would be /the/ way  
to set values per-list.

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkf8H1QACgkQ2YZpQepbvXGPkQCgpelMjuCgUA1iFUZIEBXJseiS
89AAoKiMWJa46FnwmxoN2Rv30J9zEY3O
=WOw6
-----END PGP SIGNATURE-----