Logistics

Time: Monday, July 26 @ 12:00 pm Eastern (11:00 am Central) (9:00 am Arizona)
Conference Bridge: (641) 715-3200 640123#
Attendees: Andrew Petro, Jonathan Markow, Scott Battaglia, Marvin Addison, Eric Pierce
Absent: None
Note Taker: Andrew Petro

Agenda

Roll Call; Choose Note Taker
Prior Action Items
Recap Community Call
- What Worked, Didn't
- Soliciting Presentations
Documentation Working Group
- Creation of
- New Documentation Rules
Test Plans / Test App Contributions / Lowering Barrier to Entry
Getting Those Pesky Client Apps Under Control!
- Matrix
- Releases
- Interaction with Community
- Coordinated Releases
UnConference
Jasig Sustainability (bringing value to Jasig CAS users to entice them to become members)
Leveraging things like Spring Security book with CAS support in it.
Reminder: Election Year!
- Susan's question of expanding membership.

Notes

Notes:
Committee tried to determine most important agenda items to address.
JJM inquired as to resolution status of latest CAS security issue. Scott recaps resolution of that issue.
JJM asks Scott to ACTION ITEM email security working group advising of resolution of issue.

Identified priorities:

Documentation working group
Client apps
Feature matrix
Updates for community call
Lowering barrier to entry test plans
Following up on Jasig sustainability
Delegation
Susan's question about expanding steering committee membership count

JJM articulates importance of planning for and prep for UnConference.

CAS meetup idea

Andrew Petro volunteered to take notes.

Starting meeting in ernest:

Documentation working group:

Scott relates push to properly license contributions to documentation to assure that Jasig has the right to distribute its own documentation. Tradeoffs in barrier to entry. Less with the random thoughts, more with the serious thoughtful contributions.

We had a documentation coordinator volunteer position but that didn't work out. Marvin and Scott have been effectively leading and doing the actual work on documentation.

Idea: create working group to formalize and improve documentation. Cf. efforts in uPortal, admirable volunteer efforts of Laura McCord. JJM relates uPortal's progress on this.

Marvin expresses concern about differences between uPortal and CAS documentation needs.

Eric points out there's much of CAS that isn't used in any given deployment. E.g., many adopters aren't using SPNEGO.

Discussion of whether coordinator role would be useful, whether we're defining a position that any person can fill, level of expectation, what activities would be involved.

Scott articulates: most important thing is to identify a Documentation Coordinator who wants to succeed.

In a fit of maturity and uncharacteristic understanding of his available bandwidth, Andrew Petro did not at this juncture volunteer to be the CAS product documentation coordinator.

Marvin expresses interest in structure of documentation working group and in participating directly in that working group.

Marvin expresses need for an executive role, someone who sees the big picture and is aware of the nature of CAS and its features and needed scope of documentation and organization. Marvin suggests Scott Battaglia is the right person for this role.

Scott references community roles page and specific roles: https://wiki.jasig.org/display/CASST/CAS+Community+Positions https://wiki.jasig.org/display/CASST/Documentation+Coordinator

Susan plug for breaking documentation into bite-size pieces.

Susan expresses wish to get more participants on community calls.

Discussion of community call, purpose of call, tradeoffs between using community calls as venue for broadcasting information and informing on what's up versus using community calls for richer, more interactive activities.

Susan articulates value in presentations from actual CAS adopters of what they're doing with CAS.

Scott articulates value in creating community call momentum.

Andrew suggest Yale / Howard volunteers to present on community call what Yale's doing with JBossCache for clustered CAS ticket state.

Scott mentions importance of having content for established CAS deployers on the community call.

Scott: do we fork the calls? Have a CAS developers call in addition to a community call?

Marvin articulates desirability of such a "CAS developers" weekly conference call.

Scott recaps:
Documentation working group is a good idea
Need to define structure of WG ACTION ITEM to Marvin
Community calls, how to attract more CAS deployers to that call
Forking out Developer call

Scott articulates need for ACTION ITEM defining vision of, proposal for best way to structure community calls.

JJM expresses need to discuss UnConference.

Need for more conference call time for CAS Steering committee? Out of time for today's call.

Browser not supported