COmanage-Dev Call 4-Sep-09
*Attending*
Heather Flanagan, Stanford (chair)
Digant Kasundra, Stanford
Ken Klingenstein, Internet2
Tom Barton, U. Chicago
Steven Carmody, Brown
Michael Gettes, MIT
R.L. "Bob" Morgan, U. Washington
Renee Frost, Internet2
Steve Olshansky, Internet2
*New Action Items*
[AI] (Everyone) review their carry over action items (see list below) and inform the group if their AIs are done, are still relevant or should be closed.
[AI] (Ken) will work on slides, including Steven's enhanced slides showing sequencing on the flows, and send them out to the list.
*Carry Over Action Items*
[AI] (Ken) will talk with Gwen to explore a COmanage demo geared to iPlant.
[AI] (Ken) and (Michael) will discuss a possible demo for Ken's Sept. 14 meeting.
[AI] (Ken) will speak to the French and Spanish regarding their potential work on collaboration tools.
[AI] (Ken) will forward to the list notes from his recent discussion with International partners.
[AI] (Ken) will ask the Dutch if they want to participate in the project management group for the preproduction pilot.
[AI] (Ken) will iterate with Mike LaHaye and Dan Pritts on moving the preproduction pilot toward some production use for projects of limited duration.
[AI] Tom and Michael will edit the PowerPoint diagrams to clarify issues.
[AI] (Ken) will work on COmanage scripting.
[AI] (Digant and SteveO) will put together a demo video.
[AI] (Digant) will register the Sympa bug in the COmanage JIRA for our reference, and follow up with Sympa developers/maintainers.
[AI] (Digant) will verify that Confluence is working with COmanage
[AI] (Digant) will incorporate the user dashboard that Steven designed into COmanage.
[AI] (Ken) will send an outline to Steven, Tom and Digant as a basis for talking to NSF about collaboration with HUBzero.
[AI] (Ken) will draft an email to interested parties who could be helpful in COmanage testing.
[AI] (Steven and Jim) will flesh out the existing developer domestication guidelines in the wiki.
[AI] (Ken) will ask his contact at the Norwegian Federation about Foodle.
[AI] (Bob) will provide to the list background on user stories.
[AI] (Ken) will talk with Lois about Fluid involvement in improving the COmanage GUI, scheduling it for later in the year.
[AI] (Chris) will contact Atlassian and try to obtain a timetable for Jira domestication. (Ken) will provide some wording for this communication with Atlassian.
[AI] (Bob) will send links to the group on the invitation problem.
[AI] (Ken) will send a note to his contact at OOI to explore their level interest (after the COmanage alpha is ready).
[AI] (Ken) will ping Frank Siebenlist from Argonne National Laboratory, who is interested in COmanage.
*Discussion*
*Report from Service Pilot WG*
Dimdim web conferencing hasn't been integrated into the service pilot due to audio and video problems. These issues are not a local problem, but are known Dimdim issues.
SteveO and Michael investigated OpenMeetings
(http://code.google.com/p/openmeetings/), another open source web conferencing package, but it currently lacks the hooks to allow for federated access. Michael may contact the OpenMeetings people to discuss how they can make integration with COmanage possible.
Michael has updated Drupal, and plans to work further on that. Michael has not had a chance to evaluate the LDAP module available for Drupal.
Integrating Bedework is harder than originally hoped. The information Peter D. from Brown sent to Michael was helpful. Seems that Peter's configuration depends on HSQL DB. Effort was required to get the schema right for MYSQL.
There is more work needed on the Guide to Domestication for application developers. Time is a limiting issue.
Ken: As we get more seriously into domestication, additional issues will arise about APIs. On the international phone call next week, we should talk about how to leverage each other in that process.
Q: Is there a need to name attributes consistently?
Michael: Attribute naming does not need to be consistent. From one CO to another CO, there are the federation and interfederation issues of how to map. ePPN can be used.
*Slides*
Ken thanked Steven for his slide on COmanage and the ecosystem. These had labeled sequencing on the flows and were very helpful.
Steven's slides did not go to the list. Ken will send a later version of them to the list.
Ken asked Steven if there are any other characteristics to bring out? Steven will take a look and may send something.
[AI] (Ken) will work on slides, including Steven's enhanced slides showing sequencing on the flows, and send them out to the list.
*Use Cases*
Decision was to delay creating slides on COmanage talking to COmanage until there is a use case for that. TomB noted that in the future, the Bamboo project may generate some use cases.
Steven noted there is no difference in COmanage communication between CO to CO versus CO to portal.
Steven stated that he believes the MDX work will handle interfederation trust on a technical level.
Q: Do COmanage instances have to live within federations?
A: Yes, unless bilateral agreements are used.
It was noted that some European countries, such as Norway, contain all students in a single IdP.
It could be interesting to explore interoperability questions between COmanage and the VO support platform being created by FIDA.
Andreas has envisioned that Feide would host a global instance of Foodle that works as an SP and users throughout the world could connect to that.
Ken: Perhaps it makes sense to build a list of second generation use cases, of situations we expect to have over next year.
*International Call 10-Sep-09*
There will be an international COmanage call on 10-Sep-09. Planned agenda includes:
- Report from Ian on UK
- Report from Leif on resources available
- Possibly discuss the new JISC solicitation out for software in the middleware space.
- Compare notes and roles
- Perhaps discuss joint work on a domestication guidebook.
*Other News*
Internet2 received an NSF Middleware Initiative (NMI) supplemental grant that will help fund middleware activities, including COmanage, through August 2010.
[AI] (Everyone) review their carry over action items (see list below) and inform the group if their AIs are done, are still relevant or should be closed.
*Next COmanage Call: Friday, Sep. 18, 2009, 2pm ET