Subject: Grouper Developers Forum
- From: Emily Eisbruch <>
- To: Grouper Dev <>
- Subject: Action Items: Grouper Call 14-Oct-09
- Date: Wed, 14 Oct 2009 14:38:44 -0400
**New Action Items**
[AI] (Gary and Shilen) will work on testing the UI for Grouper 1.5.
[AI] (Shilen and Chris) will work on implementing handling of change logs for effective memberships (preference on call was to include in change log the flattened changes as opposed to all changes)
[AI] (Chris) will verify which of these databases he will test the API for:
* MySQL windows
* MySQL unix with case sensitive table names
* MsSQL (new)
[AI] (Gary and Chris) will discuss what the new Lite UI should be called in the Grouper 1.5 release (end-user UI?, simple-UI?), and how expectations should be set in describing how experimental it is.
[AI] (TomZ) will document Ldappc in the wiki.
[AI] (Shilen) will document Grouper Loader, its new role, and how to monitor it in the wiki.
[AI] (Shilen) will document Upgrade Steps in the wiki.
[AI] Gary will document the Administrative UI and Audit in the wiki.
[AI] (Chris) will document the new Lite UI in the wiki.
[AI] (All) record information on release steps on release steps page.
**Carry Over Action Item**
[AI] (Everyone) will update JIRA to accurately reflect the work being done.
**Reminder of Key Questions discussed on call**
How configurable will the change notification be?
How should we structure the two UIs and one web app?
How should the operational architecture look ? (tied to questions about the Grouper Loader)
How will privilege management-related features be represented?
Emily Eisbruch, Technology Transfer Analyst
office: +1-734-352-4996 | mobile +1-734-730-5749
- Action Items: Grouper Call 14-Oct-09, Emily Eisbruch, 10/14/2009
Archive powered by MHonArc 2.6.16.