Grouper Developers Forum

["Jessica Bibbee" <>]

MACE-Dir-Groups Conference Call
May 31, 2006

*Participants*
Tom Barton, U. Chicago (chair)
Blair, U. Chicago
Joy Veronneau, U. Cornell
Gary Brown, U. Bristol
RL "Bob" Morgan, U. Washington
Brendan Bellina, USC
Will Norris, USC
Nate Klingestein, Internet2
Steve Olshansky, Internet2
Jessica Bibbee, Internet2 (scribe)

New *Action Items*
[AI] {Blair} will send out an updated bug list for the 3^rd party libs.

Carry-Over *Action Items*
[AI] {Minh} will propose a test for sorting, and/or write the code and send to the list for discussion.  (3-May-06)

*Discussion*
{Tom} raised discussion of how to smoothly incorporate the Grouper API into other 3^rd party applications. Efforts are being made so that file names will not overlap with the application files. Additionally, the 3^rd party libs are being reviewed to make sure an optimum list is available. [AI] {Blair} will send out an updated bug list for the 3^rd party libs.

The release date for grouper v1.0 has not been finalized; however, the developers are anticipating a feature freeze at the end of June. A beta release might sort out any remaining bugs before an official release.

{Gary and Blair} gave an update on the feature set to be included with the nearing Grouper v1.0 release: Group Math (composite groups), custom group types, attributes and lists,  basic XML export-and-import of Groups Registry, and improved query performance through caching.

Grouper v1.1 is expected to include the following features: Group Aging, Membership Aging, and XML Event Log. At some point, fields may belong to multiple groups.

A question regarding the XML import/export feature prompted {Tom} to forward an update from {Gary} (cf. email 31-May), which detailed a zip folder of docs, schemas, and XML examplesfor the XML import / export tool.

The Group discussed whether certain complementary tools to Grouper should be included as a part of the core product, or whether they should remain as separate components. {Tom} wants to ensure that software, which is not code, is still easy to use, e.g., CDG, CAS, etc. {Bob} commented that they should be separate from the main product unless it is Grouper specific. Pointers can lead folks directly from the Grouper download page to the extensions, with any necessary explanations.

More work needs to be done on the Subject API before it has full functionality for use with Grouper and Signet. The JDBC and JNDI connectors will also be improved for functionality. Contributions supporting the API to be available via web services are welcome.

The next scheduled MACE-Dir-Groups WG call will be Wednesday, 14-Jun at 12pm ET