grouper-dev - Draft Minutes: Grouper Call 1-Oct-08
Subject: Grouper Developers Forum
List archive
- From: Emily Eisbruch <>
- To: Grouper Dev <>
- Subject: Draft Minutes: Grouper Call 1-Oct-08
- Date: Fri, 3 Oct 2008 10:54:28 -0400
*Grouper Call 1-Oct-08**
*Attending*
Tom Barton, Chair Gary Brown, Bristol U. Shilen Patel, Duke Chris Hyzer, U. Penn Bill Kasenchar, U. Penn Tom Zeller, U. Memphis Dave Donnelly, Stanford Bert Bee-Lindgren, Georgia Tech Joy Veronneau, Cornell U. Ann West, EDUCAUSE/Internet2 Steve Olshansky, Internet2 Emily Eisbruch, Internet2 (scribe)
New Action Items
[AI] (Chris) will communicate with Dave on changes to Subject API.
[AI] (Chris) will capture Subject API changes in JIRA.
[AI] (Group) will provide Chris feedback on the moving of usdu and findBadMemberships to GSH.
[AI] (TomB) will test using a build target to make a binary distribution of Grouper.
[AI] (TomZ) will investigate wisdom in the Spring Framework for binary release and directory structure.
[AI] (TomB) will talk to Carnagie Mellon people about adapting End-to-End Diagnostic Discovery (EDDY) for audit/notification.
Carry Over Action Items [AI] (TomZ) will record membership problems discovered at U. Memphis as Jira items.
[AI] (MikeO) and (TomB) will send out roadmap information to the Grouper-dev and Signet-dev lists in preparation for the I2 FMM combined working group meeting.
[AI] (Kathryn) will do background research on a messaging system to be used as a test/example case for hooks.
Discussion
- Subject API
Dave experienced some confusion regarding Subject API status when he needed a Subject API version to use for Signet 1.3.1. There were outstanding changes in the head version of Subject API that were not in Subject API 0.4, and Dave had not been aware that work was still being done on it.
Dave created a 0.4.1. version of Subject API . Chris plans another change to the Subject API, to detect Subject API configuration errors on startup. Chris will create a Subject API version 0.4.2 for this change. TomB will set up Subject API in JIRA so changes can be tracked.
[AI] (Chris) will communicate with Dave on changes to Subject API.
[AI] (Chris) will capture Subject API changes in JIRA.
- Grouper 1.4.0 status
Chris moved the find bad memberships utility and usdu to GSH in preparation for the binary release. [AI] (Group) will provide Chris feedback on the moving of usdu and findBadMemberships to GSH.
Chris noted that the binary build is designed to be performed in the CVS box rather than locally. This will lead to a consistent Java and Ant version. Chris requested that anyone let him know if they have issues with that, since he has only tested it from his own account. [AI] (TomB) will test using a build target to make a binary distribution of Grouper.
Shilen is working on a couple of membership bugs, such as
Chris reported that GRP-86 (improve and make consistent the checkout and build process of grouper, grouper-ui, and grouper-ws) is tricky to address when development is ongoing since it involves moving the directory structure. Time is needed before or after coding a release in order to work with build scripts and do the merge; possibly at the end of development work on Grouper 1.5. https://bugs.internet2.edu/jira/browse/GRP-86
The group discussed the degree of consistency desired for checkout of UI and web services components; should they be tightly coupled or independent? TomB raised the question of how Spring handles this. [AI] (TomZ) will investigate wisdom in the Spring Framework for binary release and directory structure.
The decision was to hold off on GRP-86 until Grouper 1.5 to allow time to decide the best approach and to gain experience with the binary release.
October 31 is the target release date for Grouper 1.3.1.
- Fall Member Meeting
Topics at the combined Signet/Grouper WG session at I2 FMM will include:
- privilege management survey (Rob Carter), - possible micro-demo of Signet metadata management capabilities -what’s new in Grouper and Signet (with a short report from each developer) - roadmaps
- Audit and Notification
TomB stated that now that the hooks infrastructure is in place it’s time to take up audit and notification again.
Bert noted the desirability of being able to look at point-in-time status data rather than just log files.
Chris suggested that a way to better understand and discuss auditing and notification issues is to break out: 1. user auditing (similar to an event log) 2. notifying/system auditing 3. point in time (to know who was in what group when) TomB still hopes that it might be possible to reply on a third-party system for some of these functions. One avenue to explore is working with the Eddy project at Carnagie Mellon.
[AI] (TomB) will talk to Carnagie Mellon people about adapting End-to-End Diagnostic Discovery (EDDY) for audit/notification.
Next meeting: Monday, 13-Oct-08 at 3pm at the Internet2 Fall Member Meeting in New Orleans. This will be the combined Signet/Grouper Working Group Session.
Next Call: Wed., 29-Oct-08 at noon ET |
- Draft Minutes: Grouper Call 1-Oct-08, Emily Eisbruch, 10/03/2008
Archive powered by MHonArc 2.6.16.