Subject: Grouper Developers Forum
- From: Steve Olshansky <>
- To: Grouper Dev <>
- Subject: Draft Minutes: Grouper Call 30-Apr-08
- Date: Wed, 30 Apr 2008 11:04:52 -0600
**Grouper Call 30-Apr-08**
Gary Brown, U. Bristol (stand-in chair)
Shilen Patel, Duke
Bill Kasenchar, U. Penn
Bert Bee-Lindgren, Georgia Tech U.
Kathryn Huxtable, independent
Dave Donnelly, Stanford
Chris Hyzer, U. Penn
RL "Bob" Morgan, U. Washington
Joy Veronneau, Cornell U.
Steve Olshansky, Internet2 (scribe)
**New Action Items**
[AI] (All interested) Review the Grouper and I2MI-Common roadmaps (links below), and discuss on the list, with a particular focus on whether the loader should be included in Grouper 1.4
*Carryover Action Items*
[AI] (All interested) Test functionality in the Jira 1.3.0-tagged components as you are able, and report to the list as appropriate.
[AI] (anyone interested in contributing to the documentation) contact SteveO and TomB to coordinate before making any substantive changes, if you have not already done so.
There was discussion about experiences to date with 1.3.0-tagged components. What is remaining in the critical path for the 1.3.0 RC2 release? If there are no further changes after RC2 we will roll that into the official 1.3.0 release.
Further improvements in the UI are still underway, particularly related to CSS and display issues in some browsers, following up on relevant discussion on the list.
Improvements in the API were discussed, as well as compile-time procedures to enable line numbers to appear in stack traces.
There was a report of build problems on Solaris, which were addressed in CVS. GrouperShell (GSH) was also discussed, and recent work has led to improved error messages.
- Internet2 Member Meeting combined Grouper/Signet session - Debrief
Notes from that meeting are posted on both the Grouper and Signet websites. There was discussion of faster provisioning, and of potentially combining Grouper and Signet.
Consensus was that it made sense for now to keep them as separate projects. I2MI-Common may not be working well to date as a cross-project repository -- Ldappc and the Subject API are shared, but Grouper and Signet are still not sync'd in some important ways, in terms of common code.
How can we support tighter collaboration between Signet and Grouper, short of merging the projects?
There was also discussion of the merits of Maven v. Ant…
- Development Roadmaps
What is missing? What should be in Grouper 1.4 that is not yet included? Suggestions included:
- The approach for DDL?
- A generic 'loader'? Are we converged on a common definition? See <https://wiki.internet2.edu/confluence/display/GrouperWG/Grouper+-+Loader>
Is there anything missing? Are the priorities correct?
There was discussion about potential interest in a "subject provisioner" for LDAP. If a subject doesn't exist, and you are provisioning membership data for it, an error would be triggered. Would this be a logical addition to Ldappc? Would support for dynamic groups be a factor?
Hooks and plug-ins were noted as a logical area of overlap between Signet and Grouper… Chris and Dave have been collaborating on this, and continue to do so, and all interested are encouraged to discuss this on the list.
Next call: Wed 14-May Noon EDT
Internet2 Middleware & Security Flywheel
- Draft Minutes: Grouper Call 30-Apr-08, Steve Olshansky, 04/30/2008
Archive powered by MHonArc 2.6.16.