[Meta] Build core component classes

[tarekdj]

• Admin Class (which is not User Class).
• Subscriber Class
• List/Campaign Class
• ...

Up to us to decide on which components we will keep on core.

[SaWey]

Most (if not all) of the classes in there right now should be part of the core.
There still is a lot of code which should not be in there and has to be cleaned out, but the core system has to be able to manage a mailinglist like below:

You guys agree?

[tarekdj]

@SaWey I like the direction it takes and 👍 for the diagram :-)

[michield]

Good diagram. Few more for consideration:

Attribute
Segment
Message (an instance of a campaign for a subscriber)
Bounce

I'm not sure to make Mailinglist a class. Maybe Segment is clearer. Because we want to segment the subscribers using both list-membership (outward) and attributes (inward).

Also, if we are on this, I'd split Admin into "Admin Role" (group) and "Admin" (person), so that you can build teams around things.

[SaWey]

It was just a quick diagram to get an overview, and not directly related to the classes.

What would be the benefit of using segments? Instead of a mailinglist, segments and attributes, why not throw them together and just go for attributes, like I said in the other discussion. We could then use all that to filter subscribers in a more advanced and convenient way I think.

I would even think about removing the admins from the core. This way admins could easily come from another data source as well. (I would then move this to the GUI project)

[oliverklee]

Closing this in favor of having a domain model (in the DDD sense).