>As far as I can tell, all the relevant list attributes are already
>defined in mailman/model/mailinglist.py. As noted there, they should
>probably be added to mailman/interfaces/mailinglist.py.
Yes, and I have done that (WIP actually) in the latest
On 6/18/19 11:06 AM, Aaryan Bhagat wrote:
>
> So according to Mark's idea, we should create attributes in the mailing list
> model and the attributes like bounce score in the member model as it will
> just evaluate the bounce score for that mailing list and disable the email
> from that list
>Looking at the suggestion from Mark, how about you continue working on
>the simplified implementation for now., and then once we have completed
>that and we still have time left in your GSoC period, we can talk about the
>enhanced proposal?
Ok, I understand.
>I think the only
>relevant thing
On Sun, Jun 16, 2019, at 9:20 PM, Aaryan Bhagat wrote:
> >I think your approach is probably valid, but it adds complexity to the
> >process. Complexity is not necessarily bad, but unnecessary complexity
> >is bad because it makes things more fragile and bug prone and more
> >difficult to maintain.
