Hi Barry,
>The point of this break down is because some things (and it's not a perfect
>separation) really won't be shared between mailing lists. OTOH, you might
>want site-wide bounce settings that all lists will inherit and shouldn't be
>able to change. Other sub-styles give the list its "flav
On Mar 13, 2016, at 03:01 AM, Harshit Bansal wrote:
>Sorry, I think I have used wrong terminology here. By 'copying' I
>actually meant 'inheriting'.
Just a quick follow up to my previous comment about multiple inheritance. I
was thinking about the way it's done in the Python code now, but even t
Hi,
On 3/12/16, Stephen J. Turnbull wrote:
> > Basically, a style will be having three levels of viewability:
> > 1: System wide : A style having this level of viewability will be
> > visible to all the domains as well as the lists. It will be available
> > to all the list owners for copying
Harshit Bansal writes:
> Basically, a style will be having three levels of viewability:
> 1: System wide : A style having this level of viewability will be
> visible to all the domains as well as the lists. It will be available
> to all the list owners for copying however the site owners will
Hi everyone,
First of all, I would like to thank Barry and Steve for giving their
valuable comments due to which I have been able to workout the
"Permission model" from the very scratch, the details of which are as
follows:
Basically, a style will be having three levels of viewability:
1: System wi
Barry Warsaw writes:
> It's likely that the permissions would only be enforced in
> Postorius, although we can think about how the core would enforce
> the permissions.
I don't insist on core enforcement, though I think it desirable. I do
ask that this functionality not be called "permission"
Harshit Bansal writes:
> 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 creat
Thanks for following up here Harshit. Here are some of my thoughts/ramblings.
On Mar 09, 2016, at 10:51 PM, Harshit Bansal wrote:
>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 Post
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 styl
On 02/10/2016 10:03 AM, Harshit Bansal wrote:
> Hi Abhilash,
> In our previous discussion you mentioned that :
>
>> Permissions should also consider if the user wants to make his new style
>> public or keep it private. And should public styles be editable by
>> anyone or just read-only?
>
> I am
Hi Abhilash,
In our previous discussion you mentioned that :
> Permissions should also consider if the user wants to make his new style
> public or keep it private. And should public styles be editable by
> anyone or just read-only?
I am unable to think of a use case in which it will be useful to
Abhilash Raj writes:
> I *think* we have had a discussion before about what should be a better
> default value for member.moderation_action and
> nonmeember.moderation_action. Instead of just copying them to the field,
> we could set it to defer in which it case the lookup automatically picks
On 01/30/2016 11:11 AM, Harshit Bansal wrote:
> Hi Steve,
>
> On 1/27/16, Stephen J. Turnbull wrote:
>> Harshit Bansal writes:
>>
>> > Figure out how to store and access the styles as some of them are
>> > defined in the source code and the ones created by the by users would
>> > have to be
Hi Steve,
On 1/27/16, Stephen J. Turnbull wrote:
> Harshit Bansal writes:
>
> > Figure out how to store and access the styles as some of them are
> > defined in the source code and the ones created by the by users would
> > have to be stored in databases?
>
> You also need a read/print repr.
Harshit Bansal writes:
> Figure out how to store and access the styles as some of them are
> defined in the source code and the ones created by the by users would
> have to be stored in databases?
You also need a read/print repr. A Python dict may be a reasonable
one, but JSON, YAML, init, et
Hi Abhilash,
I liked your idea of providing the users the capability to copy and
customize the existing styles very much. Additionally, when the users
are presented with an interface to customize the style, we could
provide them with two views, one 'simple' and another 'advanced'. The
'simple' one
Hi Harshit,
On 01/17/2016 09:22 AM, Harshit Bansal wrote:
> Hi everybody,
> I was looking at GSOC 2016 wiki page and I found "Preset List Settings
> Templates" project quite interesting.
>
> After reading out the project description and the discussion on the
> project from the mail archives I hav
17 matches
Mail list logo
