Grouper Developers Forum

["Jessica Bibbee" <>]

Grouper Working Group Meeting
October 17, 2007

 

*Attendees*
Tom Barton, U. Chicago (chair)

Gary Brown, Bristol U.

Shilen Patel, Duke U.

Celeste Copeland, Duke U.

Klara Jelinkova, Duke U.

Bill Kasenchar, U. Pennsylvania

Joy Veronneau, Cornell U.

James Cramton, Brown U.

Michael Gettes, Internet2

Steve Olshansky, Internet2

Jessica Bibbee, Internet2 (scribe)

 

New *Action Items*

[AI] {Shilen} will send email to the list asking for input on GRP-48.

[AI] {Shilen} will re-execute a database from {Gary} in their environment and provide feedback on GRP-7.

[AI] {Gary} will propose a workaround for the UI on GRP-7 for feedback from Duke.

 

*Agenda*

1. Status -Status of Project Staffing, Contributors, and Funding
2. Immediate Priority: Performance Fixes for v1.2.1, focused discussion of GRP-7. C.f. attached v1.2.1-issues.jpg, or go to < https://bugs.internet2.edu/jira/browse/GRP >, choose "Road Map", select "1.2.1", click on "Pr" table column to sort in priority order.
3. Grouper Roadmap. Recap of Fall Internet2 Member Meeting WG meeting last week. Decision Process for Next Steps.
cf. < https://wiki.internet2.edu/confluence/display/GrouperWG/Priorities+for+Functional+Enhancements >

 

*Discussion*

 

-Status of Project Staffing, Contributors, and Funding-

{Tom} announced that {Blair Christensen} will no longer be contributing as a core developer, though he may participate in other ways as time allows. {Tom} also informed the Group that there are funds for ongoing work, which will be available to contracting as needed. {Gary} will be picking up several of the API-oriented issues in JIRA for the upcoming Grouper v1.2.1 release.

 

There may also be additional contributors to the core project, though no names were specified. Questions and concerns around these staffing matters are welcomed and may be directed to {Tom}.

 

-Immediate Priority: Performance Fixes for v1.2.1, focused discussion of GRP-7-
{Tom} explained that more than half of the items listed for the v1.2.1 are being addressed, in terms of effort. Cf. attached 1.2.1-issues.jpg, or go to < https://bugs.internet2.edu/jira/browse/GRP >, choose "Road Map" and click on "Pr" table column to sort in priority order. There are still 5 items left unresolved for wrapping up v1.2.1. While the original goal was for an early November release, those on the call said it would be acceptable for a late-November call, given that it included more features and fixes.

 

{Shilen} noted that he had recently resolved GRP-34, Error Initializing Oracle database with Grouper v1.2.1, and is now working on GRP-48, Performance of GroupAttributeFilter.getResults(). [AI] {Shilen} will send email to the list asking for input on GRP-48.

 

{Gary} is working on a couple of items: 1) GRP-7, Simplify UI Browsing and 2) GRP-52, Interface to conditionally veto UI menu items. His main concern is to find better ways of navigating the hierarchy for someone who has privileges over thousands of groups. The Group discussed ways of, e.g., replacing individual searches with a single search, but API considerations lead to scaling issues.

 

Profiling work and related feedback has led to many improvements, but there is still more work to do. There was much discussion on whether issues lie with the configuration of a particular database, such as Duke's use of Oracle, or whether there exist API issues that will affect the use of any database and it should be made to be more efficient can be made to be more efficient. The Group decided to work on parallel paths, isolating issues on both sides, in efforts that it will lead to an overall better package for anyone using Grouper.

 

{Michael} suggested the use of a windowing technique, which would allow a person to view just the desired items from a search. The challenge would be to do so without limiting the results of the search. {Celeste} said there needs to be structure and understanding, so that there is more browsing, instead of limited searching. What is the best way to limit the display for performance maximizing, without actually adding limits? The first goal should be to improve the user experience.

 

There was another suggestion to deny the 'manage groups' tab, such that it would serve as a dynamic removal of a task. If the there are too many results, the user is asked to refine the search.

 

[AI] {Shilen} will re-execute a database from {Gary} in their environment and provide feedback on GRP-7. AI] {Gary} will propose a workaround for the UI on GRP-7 for feedback from Duke. The Group will return to this discussion on the next conference call and review the progress on both sides. If there is a sufficient workaround for GRP-7, it will be included in v1.2.1 – otherwise, work will continue for the next release.

 

- Grouper Roadmap. Recap of Fall Internet2 Member Meeting WG meeting last week. Decision Process for Next Steps-
{Tom} worked the discussion from the Signet/Grouper Combined Working Group session (at the Member Meeting in San Diego) into the roadmap document in the Grouper Wiki: c.f.  < https://wiki.internet2.edu/confluence/display/GrouperWG/Priorities+for+Functional+Enhancements >

For more details, read the minutes from this meeting, found here: < http://middleware.internet2.edu/signet/minutes/Signet-Grouper-8-October-2007.html >.

 

{Leif Johansson} of Stockholm U. had several ideas for Grouper. He also advised that Grouper continue to focus on Groups, and not expend energy and efforts on ideas that would detract from the core functionality.

 

{James} also suggested that the Signet and Grouper Working Groups pause to see what can more efficiently be addressed as common issues, so as not to duplicate efforts. This would also lower the entry level and reduce effort for people looking at these products. He said that overlaps between Grouper/Signet/Subject API/Ldappc should be addressed sooner than later, and those fixes that would have a wider impact ought to be targeted before items of smaller scope are worked on.

The next Grouper Working Group conference call will be held on Wednesday, October 31, 2007 at 12pm EDT.

-- 
Jessica Bibbee, Technical Analyst
Internet2

mobile: +1-734-255-6644

The Internet2 Dynamic Circuit Network:
Unleash your Interdomain Imagination
http://www.internet2.edu/network/dc/