COmanage-Dev Call 24-Jul-09
*Attending*
Heather Flanagan, Stanford (chair)
Digant Kasundra, Stanford
Ian Young, JISC
Jim Leous, Penn State
Tom Barton, U. Chicago
Steven Carmody, Brown
John Spadaro, Brown
Ken Klingenstein, Internet2
Michael Gettes, MIT
R.L. "Bob" Morgan, U. Washington
Dan Pritts, Internet2
Renee Frost, Internet2
George Brett, Internet2
Steve Olshansky, Internet2
Emily Eisbruch, Internet2 (scribe)
*New Action Items*
[AI] (Ken) will forward to the list notes from his recent discussion with Dutch partners.
[AI] (Steven) will coordinate a project management group for Nate's upcoming work of creating a preproduction pilot. This project management group will have an Action Item to tell Dan how many VMs are requested, and their required specs.
[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] (Ken) will contact Leif, Niels, Thomas, and Ian to set up timing for a low-tech COmanage conference call for about 3-4 weeks from now to build consensus and do story boarding.
*Carry Over Action Items*
[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.
*International Report from Ken*
We welcome Ian to the call. Ian has been assigned by JISC to the COmanage project.
Concerning the Dutch involvement, Ken and Leif have had several meetings, some using Adobe Connect. While there have been some video issues, it is worth continuing to explore Adobe Connect, since it's a possible target for future domestication. Dutch partners are initially interested in deploying a non-production COmanage service offering.
[AI] Ken will forward to the list notes from his recent discussion with Dutch partners.
*COmanage Framework*
Nate will put together a service instance of COmanage as a skunkworks project. The hope is to demo it at FMM as a framework, with hints of an appliance.
The demo (or pre-production pilot) will show:
- how various classes of users are engaged with COmanage.
- end users going directly to collaboration apps
- collabmin managing the collaboration
- the PI easily adding a colleague to the collaboration
It was noted that Michael has already demonstrated these capabilities, currently available at http://co.internet2.edu/
Possibly Nate will simply need to integrate the latest Grouper and Ldappc instances with the existing demo.
Optionally, Nate will bring the originally installed applications (Bedework, Drupal, Sympa, Dimdim, and Confluence) up to the latest version. Steven suggested consulting with an expert at Brown on which Bedework version to use.
*Using the Demo or Pre-Production Pilot in Real Situations*
When Nate's work is done, can a working group use this service for their own collaborations?
Ken stated that TSG has asked that this not be a production service. TSG is concerned about lack of a satisfactory IdP for the "orphans," i.e. users affiliated with organizations not running a federated IdP. Also, TSG prefers that COmanage be shown to be supportable for long-term adoption before being made widely available as core infrastructure.
Heather noted that it's not beneficial to continue with demos indefinitely - we hope to move to the next level to something real.
TomB suggested that in the near-term we should only put short-lived projects on the COmanage pre-production pilot. The group agreed with this approach.
[AI] (Ken) will iterate with Mike and Dan re: moving the preproduction pilot toward some production use for projects of limited duration.
VMs
Michael suggested having one VM that's running some of the components, e.g. Login and Grouper and Directories and another VM that runs Confluence and Sympa and another running Bedework and Dimdim. Dan stated it would be possible to get multiple VMs from Internet2.
Dan stated that the pre-production pilot will be running on a reasonable VM infrastructure, and it will be backed up.
*Project Management*
It was suggested that a project management structure be put in place to oversee Nate's work, and possibly to do some storyboarding. Project management group may include Steven, Michael, a Grouper representative, Heather and others.
[AI] (Steven) will coordinate a project management group for Nate's upcoming work of creating a preproduction pilot. This project management group will have an Action Item to inform Dan how many VMs are requested, and their required specs.
[AI] (Ken) will ask the Dutch if they want to participate in the project management group for the preproduction pilot.
*COmanage Email Lists*
The possibility was discussed of creating new email lists to include the expanding COmanage community.
The decision was to keep using the COmanage-dev list and add all new participants to that.
*Upcoming Calls*
Primary focus on the Friday, 7-Aug-09 COmanage call will be the preproduction pilot. Ken will not be on that call.
Ken will coordinate a call in 3 or 4 weeks out for the larger community.
[AI] (Ken) will contact Leif, Niels, Thomas, and Ian to set up timing for a low-tech COmanage conference call for about 3-4 weeks from now to build consensus and do story boarding.
*Next COmanage Call: Friday, Aug 7, 2009, 2pm ET