On May 31, 2013, at 04:45 PM, Stephen J. Turnbull wrote:
Barry Warsaw writes:
Here's where it gets interesting. Rosters are not modeled as rows in a table, they are modeled as queries. [...]
One of the use cases for rosters that I've always had in mind are a better way to do MM2-style umbrella lists. Let's say you have one mailing list for all of your band's New York fans, and another for all of your band's San Francisco fans. It should be very easy to compose a parent (i.e. umbrella) list which had a roster combining the New York and San Francisco rosters,
Meta: It would be nice if you would distinguish between the meanings of "should" in this kind of discussion. Do you mean
- One requirement for a good admin interface it to make it easy to
compose umbrella lists.
- This architecture is expected to make it easy for an admin
interface to compose umbrella lists.
#2 mostly. I'd rather not call them umbrella lists in Mailman 3, because I think they'll operate differently and better-ly than in MM2. The current architecture allows for easy composability, although there isn't much support for this in the current code base. I.e. it would mostly be hand-coding right now, but I think the hooks are there.
As to #1 - it would be nice! But probably not a requirement. :)