Hi everyone, My name is Swastik, and I've been contributing to Mailman over the past few weeks to get a hang of the codebase. I currently have 5 open MRs across different components (hyperkitty!701, django-mailman3!345, mailman!1439, postorius!1065, and mailmanclient!197).
I'm planning to submit a proposal for the User Profile Tool project for GSoC 2026. I’ve been looking into the bottom-up fallback logic (Subscription -> Address -> User). I wanted to share my initial thoughts on solving the main UX bottlenecks and see if I am heading in the right direction. The project idea mentions showing a map of the scopes where preferences are set to non-default values. I was exploring the idea of building an intuitive, unified "Preference Matrix" UI in Postorius - a single view where users can see their user-wide, per-address, and per-subscription settings side-by-side to easily understand the fallback logic. Does this align with the kind of UX required for the project? Currently, if a user modifies a global setting after having set custom list-specific preferences, the old list preferences still take precedence. This may cause confusion if the user expects the change to be applied everywhere (e.g., if a user wants to set "receive own postings" for all lists at once). I am thinking of adding a check here: upon updating global settings, the user also gives a confirmation if they want to override their previous list-specific settings globally or not. Does this sound like the right approach? >From a security standpoint, I believe an admin's access should be strictly >limited to their list. If they are the admin for List A, they should only be >allowed to view and modify the user's settings relevant to List A, instead of >being able to change a user's global preferences or other list preferences. >Would this approach be the right way to handle admin access? Thanks! Swastik https://gitlab.com/swastikiscoding _______________________________________________ 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
