COmanage Call 30-Oct-09
*Attending*
Heather Flanagan, Stanford (chair)
RL "Bob" Morgan, U. Washington
Ken Klingenstein, Internet2
Michael Gettes, MIT
Steven Carmody, Brown U.
Tom Barton, U. Chicago
Dan Pritts, Internet2
Steve Olshansky, Internet2
Emily Eisbruch, Internet2 (scribe)
New Action Items
[AI] (Ken and SteveO) will continue to discuss separating the 2 groups and appropriate website updates.
[AI] (Heather) will resubmit the request for COmanage service for the Ivy+ Infrastructure.
[AI] (Michael, Heather, SteveO & StevenC) will work on solving issues with OpenMeetings.
[AI] (Michael) will work on integrating simpleSAMLphp and Foodle.
[AI] (Michael) will review the Dutch update Ken has forwarded.
Carry Over Action Items
[AI] (SteveO) will schedule the CollabIdM calls.
[AI] (SteveO, Ken, and Michael) will follow up on updating the WAYF to accommodate international participants.
*Discussion*
*OpenMeetings*
This working group session was conducted using OpenMeetings web conferencing within the co.internet2.edu environment. For the most part, eDial was used for the audio connection, though the group experimented briefly with the OpenMeetings audio capability.
Most participants were able to connect to the OpenMeetings environment and view the video image of other participants on the Whiteboard, along with the agenda.
Michael reported that he verified that OpenMeetings worked on the Camino, Firefox Safari, and Explorer platforms.
It was suggested that for those working at home, lower bandwidth to a residence (versus to an office setting) could be an issue leading to various video issues.
Michael stated that 9 people were on the call, and resource usage was low, at 50-100 kbps and 20 kbps on the uplink.
Dan said that server resource usage was 4 mbps out of the server and 1 - 1.5 mbps into the server. There was some increase in server usage with an increase in number of meeting participants.
The group briefly tested audio over OpenMeetings rather than eDial. The audio did not seem to work in all cases, but little time was spent investigating that.
Q: Is there an OpenMeetings users group?
A: Yes:
http://groups.google.com/group/openmeetings-user/topics
Michael's notes on OpenMeetings within COmanage can be found at:https://co.internet2.edu/confluence/pages/viewpage.action?pageId=2752550
*Conferencing Applications*
Does it makes sense to reconsider Adobe Acrobat Connect as the default conferencing application in the COmanage service, instead of OpenMeetings? Adobe Acrobat Connect has been Shibbolized by the Dutch and others, and Internet2 is expanding its use of it. The decision was made to stick with OpenMeetings for now. The open source architecture of OpenMeetings is an advantage.
Michael said there are other capabilities --not used for today's meeting -- that we can explore in OpenMeetings.
[AI] (Michael, Heather, SteveO & StevenC) will work on solving issues with OpenMeetings.
*COmanage Lists*
Ken and SteveO separated the COmanage-dev list into two overlapping groups:
1. People interested in COmanage development
2. People interested in more general collaboration platform discussions around domesticating apps etc.
Ken sent an email to the collaboration group asking people to register at co.internet2.edu. ProtectNetwork will be used for authentication to get started, until the WAYF can be appropriately enabled to accommodate other federations.
SteveO and Ken have another call planned to update the COmanage website.
[AI] (Ken and SteveO) will continue to discuss separating the two groups and appropriate website updates.
Michael, Scott Cantor, and SteveO are working to enhance the WAYF on CO.internet2.edu for international federation participants.
Q: To which list we should to add new people who are interested in COmanage from the community but are not in the COmanage developers group and also do not fit in the larger collaboration platform development group? Ken suggested waiting a few weeks to get an active community list going.
*Heather's Report from the Ivy Plus Meeting*
Heather discussed COmanage with attendees at the Ivy Plus meeting in Chicago last week. There was agreement to try COmanage for some of their interim meetings and for other collaborations.
Heather initiated a request from within COmanage to get an Ivy Plus CO instance set up. Apparently Michael did not receive it. Heather will resubmit the request.
[AI] (Heather) will resubmit the request for COmanage service for the Ivy+ Infrastructure.
*Next Steps*
Michael will work on integrating calendaring into the COmanage service. There is a new version of simpleSAMLphp and Michael will try to use that to get Foodle up and running in COmanage.
[AI] (Michael) will work on integrating simpleSAMLphp and Foodle.
Michael will also look at a recent email from the Dutch on their application integration work.
[AI] (Michael) will review the Dutch update Ken has forwarded.
*Potential COmanage Users and Support Issues*
Both ISOC and the NSF OCI Task Force have expressed interest in COmanage.
Ken will meet with the OCI task force and show COmanage on November 2.
Michael suggested that we promote COmanage as a service rather than as an appliance.
Heather and Michael stated that we should develop a support model/plan if we are going to offer COmanage as a service. Ken noted that we cannot support the user-facing apps, only collabmin issues.
Currently, setting up groups from COmanage is not straightforward. Some of the needed cues are missing. TomB suggested that Gary could help with this in the future. Possibly there are particular issues with setting up groups from COmanage that the new Grouper Lite UI will not entirely solve.
*NSF*
Ken noted there was a call with NSF yesterday. They are moving forward on an external wiki and looking at the issue of using both local and federated log ins.
Next Meeting: Friday, November 13 at 2 pm ET.