grouper-dev - Draft Minutes: Grouper WG call, 13-Jun-07
Subject: Grouper Developers Forum
List archive
- From: "Jessica Bibbee" <>
- To: Grouper-Dev <>
- Subject: Draft Minutes: Grouper WG call, 13-Jun-07
- Date: Thu, 14 Jun 2007 16:20:07 -0400
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; b=qdzmzcmdKi0hGc++M+7Wc0Evyd1Xm+FWhJUppbE/ORrossun50C2y7jMZv7qfa5xyU7OAQAoqKJIz+J/SB9zydRWcE69H9hKvyeUmN4CbMnzmkAF15BD38jXgoVimihZlv166OlPMzHUANuPlBw/mx6QVGopgr6jLnY1iRGo4FM=
Grouper Working Group Meeting
June 13, 2007
*Attendees*
Tom Barton, U. Chicago (chair)
Blair Christensen, U. Chicago
Dave Donnelly, Stanford U.
Gary Brown, U. Bristol
Joy Veronneau, Cornell U.
Bill Kasenchar, U. Pennsylvania
Ann West, EDUCAUSE/Internet2
Michael Gettes, Internet2
Steve Olshansky, Internet2
Jessica Bibbee, Internet2 (scribe)
New *Action Items*
[AI] {Jessica} will send links to {Blair} for the Grouper Archives and News
pages.
[AI] {Tom} will link in the latest javadocs for the upcoming release.
[AI] {Tom} will email [Jessica} with highlights or other notables of the new release.
[AI] {Ann and Jessica} will put together release announcement emails for the -dev, -users, and mw-announce lists.
[AI] {Jessica} will give better visibility to the UI Tutorial document in the current documentation.
[AI] {Blair} will update the hooks page in the project wiki.
[AI] {Blair and Jessica} will update the Archives and News pages in the wiki.
[AI] {Jessica} will send links to Michael regarding the Hooks discussion write-ups.
[AI] {Tom or Jessica} will email the Group with confirmation of the next WG call date.
*Agenda*
1.
Grouper v1.2.0
. outstanding issues
. documentation
. release target date & logistics
2. Community Contributions - how to share your campus' experience
3. Candidate Grouper API hook points
*Discussion*
-Grouper v1.2.0 Release-
Since the release of Grouper v1.2.0 RC3, neither {Blair nor Gary} have received feedback indicating a reworking of the core code. Therefore, code in the official release will be identical to the RC3 version, waiting only to be tagged and packaged, along with remaining documentation and an official announcement.
-Documentation-
The Group discussed several items of documentation awaiting finalization, including:
- Media Properties - Gary
- customization guide - Gary
- javadocs - Tom
- list archives -harvested items from {Michael and Steven Carmody} re: LDAPPC, etc. -Tom
- versioning advice on Grouper, Signet, and the Subject API - Tom
- note on transition between Grouper v1.1 and v1.2.0 – Tom, Jessica
- Release Notes – Jessica
- Archives and News document updates – Blair, Jessica
[AI] {Tom} will link in the latest javadocs for the upcoming release.
[AI] {Blair and Jessica} will update the Archives and News pages in the wiki.
[AI] {Jessica} will send links to {Blair} for the Grouper Archives and News pages.
< https://wiki.internet2.edu/confluence/display/GrouperWG/Release+Details+and+Previous+Releases/ >
< https://wiki.internet2.edu/confluence/display/GrouperWG/News/ >
{Tom} expected these items to be ready for updating in the wiki by the following Friday, 22-Jun. The –users list has provided good fodder for useful documentation, primarily those recent emails from {Michael and Steven}. {Jessica} will work with the developers to prepare the documents and ready the wiki.
{Michael} pointed out that a very good piece of documentation, the UI Tutorial for Grouper v1.0, was not outwardly visible and ought to be moved to a more easily found location. While the document was written for v1.0, the overall content and related screenshots have survived that version and continue to accurately reflect the UI. [AI] {Jessica} will give better visibility to the UI Tutorial document in the current documentation.
-Release Announcement-
Once the documentation is finished and wiki updated, an announcement will first be sent to the Grouper-dev and –users list. Thereafter, a modified announcement will be sent to the mw-announce mailing list. [AI] {Tom} will email [Jessica} with highlights or other notables of the new release. [AI] {Ann and Jessica} will put together release announcement emails for the -dev, -users, and mw-announce lists.
-Community Contributions – How to share your campus' experience-
{Steve} identified 2 categories of campus contributions: 1) those which are linked directly to the campus location of the file, offered for use by the community but without any formal ties to the Grouper product, and 2) those which have a tighter association with the core code and have been reviewed and accepted by the developer team as an official extension, etc. of the Grouper product. The former option recommends that the campus will include their own license when appropriate. The latter will require that the campus adhere to the Contributor License Agreement set forth by Internet2: < http://www.internet2.edu/wg/contributor-agreement.html/ >
Once the contributor has chosen one of the two paths above, {Jessica} will work with him/her to locate the link on the Contributions page of the Grouper wiki. If the campus does not already have their own progress page, {Jessica} will create a page where they can link to their various items and share updates beyond the mailing lists.
Most items contributed will be discussed on a case-by-case basis, and ultimately will be left to the decision of the contributors and the Grouper developers.
-Candidate Grouper API Hook Points-
{Tom and Blair} shared a page in the wiki proposing a candidate list for Grouper API hook points. One category of Group management operations included coverage of Groups and Stems (create/delete, etc.) Hooks for metadata management operations included Group Types, Fields, and Sessions. For details, refer to the wiki: < https://wiki.internet2.edu/confluence/x/vjk/ >.
{Tom} asked the Group to pay particular attention to how these items would be used on their campuses, as well as identifying other areas of need. {Gary} raised discussion of the differentiation between effective and direct changes. {Blair} advised further discussion regarding whether there ought to be different hooks for the two. [AI] {Blair} will update the hooks page in the project wiki.
{Dave} suggested that they consider having two types of listeners: those granular and those at a higher group level. The plugin would then decide which would register as the listener of choice, which would provide the ability to act at a granular level, even if thousands of transactions are happening.
{Michael} asked about the location of the write-ups for previous hooks discussions. [AI] {Jessica} will send links to Michael regarding the Hooks discussion write-ups.
< https://mail.internet2.edu/wws/arc/signet-dev/2007-05/msg00014.html/ >
< https://mail.internet2.edu/wws/arc/signet-dev/2007-05/msg00012.html/ >
The next Grouper Working Group call falls on the last day of CAMP Shibboleth: Flexible Web-Based Authentication and Authorization, so is only tentatively scheduled for the regular date of Wednesday, June 27, 2007 at 12pm EDT. [AI] {Tom or Jessica} will email the Group with confirmation of the next WG call date.
--
Jessica Bibbee, Technical Analyst
Internet2
mobile: +1-734-255-6644
Internet2 Workshops:
More fun than summer school
http://www.internet2.edu/workshops
- Draft Minutes: Grouper WG call, 13-Jun-07, Jessica Bibbee, 06/14/2007
Archive powered by MHonArc 2.6.16.