Thank you for the guidance on exploring the rule chain and handler pipeline. Since then I’ve spent some time reading through the mailman core architecture docs and related materials (including the AOSA chapter by Barry), and am digging through the code around rules, actions, handlers, and queues to understand how delivery decisions are made and how metadata flows through the processing pipeline at a lower level.
I’ve also continued contributing while getting familiar with the codebase: so far I ave submitted two PRs for existing issues and opened another PR addressing an old TODO comment. At this point I feel I have a reasonable grasp of the core processing flow, so I had a couple of questions about next steps: For Dynamic Sublists, would it make sense to start discussing possible design approaches on the mailing list now, or is that better left for the formal proposal stage? For that project, how important is familiarity with the Postorius or HyperKitty codebases? From my understanding most of the core logic would live in mailman-core, with the others mainly involved for configuration/UI. Would you reccomend I get comfortable with their codebases and contribute to them to develop understanding? And also, now that I have worked on a few smaller fixes, I’d like to start contributing in larger ways. Would it be helpful to begin reviewing other PRs, opening issues I notice, or working on some of the “wishlist” issues , or are those generally too large for new contributors to pick up? Thanks again for all the help and for maintaining Mailman. Best regards, Tanmay (pecpo) _______________________________________________ Mailman-Developers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
