Action Items
New
[AI] {Jim} will remind the University of Wisconsin mail manager to respond to the mail list manager survey.
[AI] {Jill} will send out a survey reminder to increase the number of respondents for the mail list manager survey.
[AI] {Jim} will add explanatory text to domain model and update the domain model.
[AI] {SteveO} will gain a better understanding of Sympa documentation and translation requests and coordinate follow up w/ Renee and Jill.
[AI] {Jill} will send the URL for the workshop presentation to the list when available.
[AI] {Jill} will send an invitation to Sympa workshop attendees to join Internet2 and MList if they are not already members. This invitation will also include information about the hied-emailadmin list.
[AI] {Paul} will send hied-emailadmin list subscription and info link to the list.
[AI] {Jim} and {John-Paul} will discuss the object and domain model intersection points.
[AI] {Anyone} having suggestions for follow up to the I2MM, please send them to the list.

Carry Over
[AI] {Jill} will develop VO survey distribution list.
[AI] {Jill} will follow up with NSF and DOE for possible VO survey candidates.

Participants
Jill Gemmill, University of Alabama at Birmingham (chair)
John-Paul Robinson, University of Alabama at Birmingham
Jim Phelps, University of Wisconsin - Madison
Jeff Eaton, Carnegie Mellon University
Paul Russell, University of Notre Dame
Renee Frost, Internet2
Steve Olshansky, Internet2
Terrie Clark, Internet2

Discussion
Thus far, six universities have responded to the mailing list survey. The respondents are using various mailing list software applications including Sympa. A better understanding of the integration aspect of outfacing applications is desired.

I2MM Debrief
The Sympa workshop is considered a success. The workshop was intended to give participants a thorough understanding of Sympa’s capabilities. Sympa as a mailing list manager incorporates many common mailing list requirements. It also has the ability to provide authentication and authorization data to other tools within collaborative systems. Since the MList domain model focuses on usage from a mail list manager’s perspective, then the domain model can be used as a discussion interface with Sympa developers. It was discussed that the domain model could benefit from explanatory text. The Sympa developers requested assistance with documentation from Internet2.

The group discussed how a mailing list system interfaces with other collaborative tools. This line of thought will be pursued in conjunction with the domain model. Is it reasonable to build a system that manages the interfaces to other collaborative tools? If we were to develop only mailing list software, then we would focus on only mailing list requirements and issues. However, if we were to develop a collaborative suite, then the requirements would be different. If mailing list software is the interface to collaborative effort, then the roadmap is somewhat defined. Then mailing list software developers could ascertain features that flow into other collaborative tools.

The object model is application specific. It is not designed to describe collaboration. It was discussed that the object model should converge with the domain model and subsequently highlight middleware interfaces. The intersecting points of the two models will illuminate middleware requirements of collaborative efforts.

It was discussed that at some point the group should facilitate communication of mailing list software requirements to mailing list software vendors. This may be accomplished through outreach from EDUCAUSE to corporate relations groups or via an EDUCAUSE magazine article focusing on what CIOs and mailing list managers require from mailing list software.

The next meeting is Wednesday, October 27, 2004 at 12:00 ET. John-Paul Robinson will chair the next meeting.