Hi all, My name is Tejas Pavan B, a third-year CS student from Bangalore. I'm interested in contributing to GNU Mailman for GSoC 2026, with a focus on Mailman Core, specifically the Dynamic Sublists project idea.
I've set up the Mailman 3 development environment locally and am currently working on HyperKitty issue #526, with an MR coming shortly. My background is in distributed systems. I've worked with Go, Redis, and Python in production contexts, and recently had a patch merged into opentelemetry-python (CNCF). I read Stephen's reply to Tanmay's question about the Dynamic Sublists architecture. The suggestion to derive a sublist interface from MailingList components makes sense to me. I started tracing through mailman/model/mailinglist.py and noticed membership is managed via ISubscriptionManager, my question is: would sublist membership be best modelled as an extension of ISubscriptionService, or does it warrant a new top-level interface entirely, given that sublists would need to inherit and filter the parent list's member set rather than manage their own? Also happy to take on any open issues in mailman core in the meantime if there are any suitable ones flagged for new contributors. Thanks, Tejas Pavan B [email protected] https://gitlab.com/tejaspavanb https://github.com/tejaspavanb _______________________________________________ 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
