1. 17 December 2015 MACE-MLIST Working Group Jill Gemmill, UAB (chair) John-Paul Robinson, UAB Jim Phelps, UWisc Paul Russell, Notre Dame Serge Aumont, CRU

2. MACE-MLIST CHARTER  Research the issues surrounding middleware- enablement of mailing list services. document how to perform this integration provide forums where people can learn and help each other in addressing these integration issues within campus contexts. collaborate with open source communities enterprise/federation.  The WG will consider and implement a survey of current university mailing list users  The WG will include persons who are actively working on integration with the enterprise/federation using non- proprietary technology; experiences will be shared regarding application designs best supporting infrastructure. Working group members will test-drive pilot/prototype solutions.

3. Outline 1.Summary of MACE-MLIST Accomplishments since Fall 2004 MM  Mailing List Administrator Survey Results  Domain Model and Sympa  NMI R6 contribution: Middleware Integration with Existing Applications: Current Design Issues, with a Focus on Mailing Lists NMI R6 contribution 2.Summary of myVOCS (my Virtual Organization Collaboration Suite) 3.Mailing list software in the war against spam

4. Mailing List Administrator Survey  Survey Results Summary Survey Results Summary  Conclusions Conclusions

5. Domain Model and Sympa  http://middleware.internet2.edu/mlist/do cs/SympaModel2.pdf http://middleware.internet2.edu/mlist/do cs/SympaModel2.pdf (thanks to Jim Phelps, UWisc and CRU)

6. NMI R6 contribution:  Middleware Integration with Existing Applications: Current Design Issues, with a Focus on Mailing Lists Middleware Integration with Existing Applications: Current Design Issues, with a Focus on Mailing Lists

7. myVOCS Summary of myVOCS (my Virtual Organization Collaboration Suite) Survey of VO’s planned in near future.

8. Mailing list software in the war against spam 1. Learn about new approaches proposed to controlling SPAM 2. Would it be nice to have a common technical approach among (open source) mailing list developers? What would be benefits to end users? What would be benefits to developers? 3.“best practices” ? “standard”? Other suggestions?