Minutes, Grouper Call 14-March-2012
Tom Barton, University of Chicago (chair)
Chris Hyzer, University of Pennsylvania
Shilen Patel, Duke
Lynn Garrison, PSU
Jim Fox, U. Washington
Tom Zeller, Unicon
Steve Olshansky, Internet2
Emily Eisbruch, Internet2
New Action Items (related to the 2.1 release)
[AI] (Chris) initiate release notes for Grouper 2.1
[AI] (TomZ and Shilen) send bullets for release notes to Chris
[AI] (Chris) edit the wiki page regarding the release
[AI] (Chris) will ask (Emily) to do some QA on the documentation when the release notes are ready
[AI] (SteveO) send out news on the Grouper 2.1 release to the appropriate lists
Carry Over Action Items
[AI] (TomZ and Emily) will update the documentation to reflect the terminology change from LDAPPC-NG to PSP (in progress)
[AI] (TomB and Emily) will outline a plan for getting community input to the new Grouper UI
[AI] (Mike) will review and contribute to the Grouper UI Planning wiki pagehttps://spaces.at.internet2.edu/display/Grouper/Grouper+UI+redesign+v2.2
[AI] (Shilen) will review and contribute to the Grouper UI Planning wiki page
[AI] (TomZ) will put test data in the Grouper demo to show using an LDAP source might be waiting for demo server
[AI] (TomZ) will review the Grouper LDAP Loader doc and provide feedback to Chris, possibly with lessons learned from LDAPPC work.https://spaces.at.internet2.edu/display/Grouper/Grouper+-+Loader+LDAP
[AI] (Rob) will follow up with Danno on obtaining the server for the Continuous Integration Environment.
[AI] (Everyone) review Rob's chapters and give him feedback on the Grouper Users List.
Release of Grouper 2.1.0
-Testing has been going well.
- Hope the release will be ready in a few days.
- The previous decision had been to have the initial public release be a 2.1.0, that is like a Release Candidate, and then after a while we'd make fixes for errors found and have a 2.1.1 release
Q: Should this release be the 2.1.1 release, since some pre-testing has already been done by PSU and others?
A: Some gray area since we never announced a finalized 2.1.0 on the list
Q: Chris: If we release 2.1.0 and there are no problems, then do we release a 2.1.1 that is the same as 2.1.1?
- Problem: if we make this release sound too experimental no one will use it.
Decision: this release will be Grouper 2.1.0, with no special caveats about being a candidate
- Lynn has not picked up the latest build
- But things working well , except for a few issues with the PSP
TomZ will wait for Chris to finish before dealing with the demo server issues
- Then TomZ will add an LDAP subject source to sources.xml
- TomZ will put PSP LDAP UI on the demo server, with a limited number of people, so it's more responsive
Q: Chris is that linked from the index page?
A: TomZ: yes it will be
Q: will that be protected by Shib?
Q: do we control who has access
A: any valid user. It is read only
[AI] Chris initiate release notes for Grouper 2.1
[AI] TomZ and Shilen send bullets for release notes to Chris
Chris will edit the wiki page regarding the release
[AI] (Chris) When the release notes are ready, ask Emily to do some QA on the documentation.
[AI] (SteveO) will send out news on the Grouper 2.1 release to the appropriate lists
UI Planning for Grouper 2.2
For the UI redesign planned for Grouper 2.2, Chris suggested a new rich UI and also a separate, simpler UI that is accessible.
See Chris's write- up in the "Architecture" section at https://spaces.at.internet2.edu/display/Grouper/Grouper+UI+redesign+v2.2
Advantage of this approach is will lead to more flexibility for the "rich" UI
Jim noted there are many special considerations for mobile UIs.
Chris: would try to have the rich UI be mobile-friendly if possible
Must be easy to get from one UI to the other. Possibly a splash page without rich controls
Ability to set favorites would be good.
TomB: U-Chicago has user experience people who are eager to get involved / provide input.
Next Grouper Call: Wed. 28-March-2012 at noon ET