Presence and IntComm WG

["Ben Chinowsky" <>]

*Action Items as of January 22*

[ACTION] (1/17) Rodney will document hardware requirements for the demo and
production versions of PIC.edu (in progress; see
https://mail.internet2.edu/wws/arc/wg-pic/2008-01/).
[ACTION] (1/17) Tim will launch an email discussion of what to call the 
PIC.edu
service, in context of how we want to present the demo.
[ACTION] (12/6) Tim will contact Dorothy Williams and Ed Humphrey about 
working
on PIC.edu server documentation.
[ACTION] (12/6) Tim will send wg-pic a proposal for which features the initial
PIC.edu client table should cover.
[ACTION] (11/1) Tim will put the draft PIC.edu project objectives on the wiki
and invite people to start contributing there.
[ACTION] (11/1) Tim will ask SIP.edu participants for their insights on how to
proceed with PIC.edu, and in particular how to handle user generation and
management.
[ACTION] (10/4) Peter will find out if Horizon Wimba can interoperate with 
other
XMPP services, in particular whether it can do server-to-server federation.
[ACTION] (7/12) Mark will prepare a simple demo of anonymous and non-anonymous
versions of moderated and unmoderated Jabber chatrooms, for a PIC call in 
early
2008.

*Attendees*

Tim Callahan (chair) - Michigan
Deke Kassabian - Penn
Jorj Bauer- Penn
Rodney McDuff - Queensland
Ben Chinowsky (scribe) - Internet2

*Discussion*

The group reviewed Tim's proposal for a demo at the April Member Meeting (see
https://mail.internet2.edu/wws/arc/wg-pic/2008-01/msg00006.html).

It was agreed that we want to use an on-site server (not, e.g., the
voice.internet2.edu machine in Ann Arbor). [ACTION] Rodney will document
hardware requirements for the demo and production versions of PIC.edu.

Deke noted that Penn can provide configuration support, but not hardware 
support
or end-user support. There was general agreement that good, concise
documentation for end users will be key to the success of the demo.

The group also discussed possible names for the demo service. There was 
general
agreement that we don't want to have to change the name in order to transition
to a production service, so names like pic-demo.internet2.edu are out. It was
also noted that the question of what to call the service is closely related to
the question of how we want to present it. Which of the system's uses -- 
e.g., facilitating informal conversations at conferences, preserving a record 
of
online conversations -- do we want to emphasize in the pitch for 
participation?
[ACTION] Tim will launch an email discussion of what to call the PIC.edu
service, in context of how we want to present the demo.

Jorj reminded the group that it's not yet possible to Shibbolize a Jabber
server, so if Shibboleth support is provided, it will be for account creation
only. Rodney noted that using http://www.protectnetwork.org/ or
https://www.openidp.org/ makes this easy; nonetheless, we should encourage
potential participants in the PIC.edu demo to get Shib credentials and
familiarize themselves with the Shib login process ahead of time.