Summary (mostly as a working theory for now): Seeding/Unseeding: - we would only select and fully support the core mailman3 (to keep things reviewable and supportable) - all the web bits pulled in by mailman3-full via mailman3-web and hyperkitty would not get into main - once migrated mailman2 would be demoted (another nail in the python2 coffin) Ownership: - flufl*, lazr.*, python-*, nose as listed are generic python libraries which I'd ask foundations to own - zope.* as listed would be on Server Team - mailman3 itself would be on Server Team
next: I will talk to various people to get some acks on that approach -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775427 Title: [MIR] mailman3 to replace mailman, or drop mailman to universe and off server iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flufl.bounce/+bug/1775427/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
