Navya Khanna via Mailman-Developers writes: > For GSoC, I'm interested in proposing the *Per-list Backup* > project. Before investing time in a detailed proposal, I wanted to > confirm it's still open
It is. > and ask: is there an existing export/import mechanism in the > codebase I should study as a reference, or is this greenfield from > the storage layer up? Not yet. There's no reason to use anything but a plain text serialization, there are no complex binary objects in Mailman. There are a couple of JSON-based mechanisms (for list or user configurations) from previous GSoCs, but for various reasons they did not get integrated. I will see if I can find the repos and cite them here. However, in the meantime, Mailman doesn't try to store complex internal objects like pickles (I think regexps are the worst) in the database. So for your purpose assuming the "obvious" Python dict/object to JSON mappings is probably the way to go. More precisely, there are JSON schema for this kind of thing, you should use one of them. Starting from there and the principle that readable exports are good exports should get you going. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan _______________________________________________ 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
