*Attendees*
Tom Barton, U. Chicago
Lynn McRae, Stanford U.
Dave Donnelly, Stanford U.
Gary Brown, U. Bristol
Andrea Beesing, Cornell U.
Joy Veronneau, Cornell U.
Tom Parker, Cornell U.
Bill Turner, Cornell U.
Tom Poage, U. California, Davis
James Cramton, Brown U.
John Wagner, Princeton U.
Anne Marie Alexander, Duke U.
Monica Crawford, U. Wisconsin-Madison
Andrew Tristan, U. California, Riverside
Russ Harvey, U. California, Riverside
Stephen Hock, U. California, Riverside
Will Norris, USC
Brendan Bellina, USC
Albert Wu, UCLA
Warren Leung, UCLA
Todd Piket, MTU
Bob Landsparger, MTU
Nate Klingenstein, Internet2
Ann West, EDUCAUSE/Internet2
Renee Frost, Internet2
Jessica Bibbee, Internet2 (scribe)

*Action Items*
[AI] {Tom and Will, et al} will hold a design call to discuss where the hooks will go and how.
[AI] {Joy} will share posters on the wiki.
[AI] {Joy} will share namespace solution.
[AI] {Joy} will start discussion on ldap.
[AI] {Monica} will share link to kite/sea/fish studies.

*Agenda*
1. Intros
2. Gap Analysis
3. Developer Roadmap
4. Campus Development Plans
5. Transport of group & privilege information
6. Configuration of LDAP provisioner (privacy)

*Discussion*

Request for Developer documentation for those wanting to help with core development:
- needs better/more on database, etc.
- easier way to view code
- Dave will be publishing uml overview diagrams...

Progress on Dynamic Groups:
- Provisioning to downstream Directories
- pointer to groups in LDAP elsewhere
- ask Grouper or ask the source?
- Tom P. will share a write up of his ideas
- state transitions for a group without need to manually copy
- Grouper needs to find a way to coordinate dynamic groups with group math... Ideas?

MACE blessed representation of something larger than [permissions] in LDAP:
- strings & related concerns
- interface specifications - in one package
- Signet/Grouper to be attribute authorities? No.
- sub-interface for integrating for programmer end
- Yale CAS as example of client presentation of standard interfaces for accessing external authority sources or something like that.

Request for Hooks into various core Grouper functions:
- pre- and post-callbacks, e.g., pre-commit (vetoes)
- hooks for specific pieces without replacing full implementation
[AI] {Tom and Will, et al} will hold a design call to discuss where the hooks will go and how.

Request for a Way to merge Signet/Grouper components in same interface for users:
- at API and UI level, both?
- Possibly as simple as navigation links
- SOAP interfaces for integration of Signet/Grouper
- Demo/QuickStart for Signet/Grouper interface
- What to call it?
- Strategy - How to sell it to CIOs?

Subject API has no plan for write/update capabilities - read only.

Uploading lists and downloading into groups:
- interface for batch loading
- upload xml

Lifecycle, aging of memberships

Case studies for identifying (and sharing) real world scenarios / states of campus:
- per audience
- template pages already in wiki, ready for use
- mini-case-studies of real/overcome problems (from requirements document)
- value-add of services not yet in-demand/understood (Signet)
- documentation for campus management
- documentation/support for the user - contribution-lead templates

Use cases - problem/solution set:
- envisioning documentation [Ann]

Request for a Systems diagram with features/requirements

The Signet/Grouper Early Adopters will next meet for discussion at the Fall Internet2 Member Meeting in Chicago, on Monday, December 4, 2006. http://events.internet2.edu/2006/fall-mm/