*Action Items*

New
[AI] {Jill, Darrell and John-Paul} will summarize middleware integration points and other discussion points for Mailman conversation.
[AI] {Jim} will spearhead the group’s development of the common taxonomy of terms and send it to the list for group participation in its development.
[AI] {Jim} will set up a wiki for common taxonomy of terms.

Carry Over
[AI] {Jill} will request a working group side-session at the Spring I2 Member Meeting if the track session proposal is not accepted. Jill is waiting of follow up from Internet2 staff.
[AI] [SteveO} will create a ‘wishlist’ section on the WG’s website. This first item posted to the ‘wishlist’ will be a solicitation seeking an individual interested in packaging and maintaining Sympa for Fedora Core.
[AI] {Group} will review charter, objectives and deliverables to determine WG’s next steps.
[AI] {Paul, Serge and Olivier} will develop a list of generic topics addressing spam and mailing list management software.
[AI] {SteveO} will gather email policy links from survey responses and incorporate them on the WG’s web site.
[AI] {Jill} will notify EDUCAUSE of Mailing List survey results to be placed in the EDUCAUSE library.
[AI] {Jim} will incorporate Sympa developers’ comments into the WG’s models.
[AI] {Jim and John-Paul} will discuss local-interface preference storing of attributes. And, will send a brief summary of the discussion to the WG via the list.
[AI] {SteveO and Jill} will gain a better understanding of Sympa documentation and translation requests and coordinate follow up w/ Renee and Jill.
[AI] {Jill} will develop VO survey distribution list, and will follow up with NSF and DOE for possible VO survey candidates.

*Attendees*
Jill Gemmill, University of Alabama at Birmingham (Chair)
John-Paul Robinson, University of Alabama at Birmingham
Jim Phelps, University of Wisconsin, Madison
Darrell Fuhriman, Portland State University
Terrie Clark, Internet2
Lisa Hogeboom, Internet2
Steve Olshansky, Internet2

*Discussion*

The groups discussed a possible dialogue with Mailman developers. It was decided that the group would develop documentation to facilitate proposed middleware integration of Mailman. This well-timed documentation coincides with the initial development phases of Mailman’s v3. A Mailman developer meeting is scheduled for March 19 – 22 in Washington, DC. The group would like to have this documentation prepared in time for the meeting. And, the group is considering sending a MACE-Mlist representative to the Mailman developer’s meeting.
http://www.gnu.org/software/mailman/

The “Message Flow with Middleware Interaction Points” diagram has been updated to include recent comments. Further revisions will include providing a common taxonomy of terms, highlighting areas where data is required and/or stored for middleware integration, providing one area for identity management with both local and external sources of rules and data, and sources of attributes. The moderator approval mailbox is actually a message acceptance-processing queue as opposed to an end delivery point. This will become a message authority activity describing the multiple decision points relying on data for middleware integration. A web based interface to a message archive, using the same identity and attribute authority provider to determine who is allowed to access the message or data, could be illuminated in this section. The incentive for integrating applications with middleware is that a larger system environment can be developed and leveraged. The overall system relies on the common infrastructure for identity and attribute management.

The “Middleware Interaction Focus” document has been posted to the WG’s website. Page five of this document will be replaced with the Message Flow with Middleware Interaction Points’ diagram. The group will develop a common taxonomy of terms for all WG documents and models.

Possible VO survey participants include NIH, CERN, DOE’s ESnet, NSF TeraGrid, UAB-related VOs and Internet2 working groups. This list of recipients reflects varying sizes, disciplines and functions for VOs.

The next call is Wednesday, March 2, 2005 at 12:00PM ET. The call in number will be distributed with the agenda prior to the call.