Re: [Mailman-Developers] Discussion On Project Idea "Preset List Settings Templates" .

On 02/10/2016 10:03 AM, Harshit Bansal wrote:
Well, i agree there is nothing "private" in list styles. We could just make all styles read-only for everyone. But if someone wants to use the style created by other users, it would be better idea to first make them copy the style so that the behavior or their list doesn't change when the owner changes the style.
Barry: If you have some time, I would like to hear some of your thoughts on this thread? I believe you have some ideas of your own on how this is supposed to work.
Thanks, Harshit Bansal.
-- thanks, Abhilash Raj

Hi, As per previous discussions, it would be nice to support style hierarchies such that the list owners can compose them and defer settings to values higher up, that would allow the core to define some basic styles and then list owners can just tweak a few settings to modify one of those base styles but in this case should the changes in base-styles be propagated to all the styles that inherit it or not. If we allow the propagation of changes to inheriting styles, some list owners might be uncomfortable with this feature as then if any of the base-style changes their inheriting styles will change without any kind of prior notification.
I think the "Permissions Systems" would have nothing to do with the core. It would be related to Postorius. We will have to create a style model separately in Postorius which would store the style name and the user who created it. Then only the user who has created the style would be granted the permission to edit it.
Thanks, Harshit Bansal.
On 2/11/16, Abhilash Raj <raj.abhilash1@gmail.com> wrote:

Hi, As per previous discussions, it would be nice to support style hierarchies such that the list owners can compose them and defer settings to values higher up, that would allow the core to define some basic styles and then list owners can just tweak a few settings to modify one of those base styles but in this case should the changes in base-styles be propagated to all the styles that inherit it or not. If we allow the propagation of changes to inheriting styles, some list owners might be uncomfortable with this feature as then if any of the base-style changes their inheriting styles will change without any kind of prior notification.
I think the "Permissions Systems" would have nothing to do with the core. It would be related to Postorius. We will have to create a style model separately in Postorius which would store the style name and the user who created it. Then only the user who has created the style would be granted the permission to edit it.
Thanks, Harshit Bansal.
On 2/11/16, Abhilash Raj <raj.abhilash1@gmail.com> wrote:
participants (2)
-
Abhilash Raj
-
Harshit Bansal