Grouper WG Conference Call June 14, 2006
*Participants*
Tom
Barton, U. Chicago (chair)
Blair Christensen, U. Chicago
Joy Veronneau,
U. Cornell
Gary Brown, U. Bristol
Steve Olshansky, Internet2
Jessica Bibbee, Internet2 (scribe)
New *Action Items*
[AI]
Tom will send out a weekly updated link to an export of the
wiki in advance of the wiki going public.
[AI] Please give
feedback to {Jessica} regarding general content, format, and/or
navigation of the wiki pages.
[AI] {Jessica and Gary} will
set up a time to discuss authoring documents in the wiki.
Carry-Over
*Action Items*
[AI] {Blair} will send out an updated bug list
for the 3rd party libs. (31-May-06)
[AI] {Minh} will propose
a test for sorting, and/or write the code and send to the list
for discussion. (3-May-06)
*Discussion*
{Gary} provided initial
screenshots for how group math will be handled in the UI, with
example XML at the bottom of the following page: <http://portal.bris.ac.uk/grouper-ui-docs/composite/>.
He explained how it is possible to save groups that are saved
to the current session, and are then listed on the group summary
page. A wizard-like approach might be useful to prompt the
user through a series of tasks, but is too complex a feature
for inclusion in the upcoming v1.0. A code freeze is still
anticipated at the end of June.
The Grouper wiki is under construction, with a preview available at <http://home.uchicago.edu/~tbarton/GrouperWG-20060613-15_38_38.pdf>. [AI] Tom will send out a weekly updated link to an export of the wiki in advance of the wiki going public. [AI] Please give feedback to {Jessica} regarding general content, format, and/or navigation of the wiki pages. [AI] {Jessica and Gary} will set up a time to discuss authoring documents in the wiki.
{Tom} is looking for suggestions on an approach for deployment: develop vs. production – targets under the UI. How should deployment be advised in production documentation? Which requirements are imposed on getting a Grouper instance up for deployment? {Joy} commented that configuration files represent the majority of changes made. {Gary} suggested having a single file to update - the properties file could define various elements, such as configuration values, database names, etc.
The next scheduled MACE-Dir-Groups WG call will be Wednesday, 12-Jun at 12pm EDT.