I’ve submitted my GSoC proposal for the *"Per-List Backup and Restore"* project.
Building on my work in *MR !1453*, I’ve focused this proposal on using ZCA interfaces to ensure database integrity during the backup and the restore lifecycle. However I really would like recheck and assurance on these topics: - The Restore Engine logic (the is_subscribed() precheck to avoid session poisoning. I want to ensure my approach to transaction management aligns perfectly with Mailman's architectural standards. - the JSON schema field coverage- if there are any mailing list state attributes or archiver settings that are being overlooked for complete restore? I'm currently auditing the codebase for further "quality of life" fixes to work on while the review period is active. If there are specific priority areas that need attention, I’m happy to take them on. Best, Navya Khanna GitLab: @Naveeeya <https://gitlab.com/Naveeeya> _______________________________________________ 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
