2011-01-27 Steering Committee Call

Owned by Andrew Petro
Last updated: Feb 01, 2011 by Marvin AddisonVersion comment
2 min read

Logistics

Rescheduled to 2011-02-01, noon Eastern, Calliflower.

The "quick PIN" 2227 should work in a pinch, though it's always better to use your own PIN.

Agenda

  • Status of FreeNode #cas-dev channel
  • More CAS session proposals for Jasig 2011
    • Marvin and Andrew and Susan joint "What's new in CAS?" proposal? Flavor? Scott's "State of the CAS" idea? Tactical triage and identification of what to take offline with whom.
  • Reflecting Password Policy in CAS login experience
    • In CAS 3.4.5
    • In CAS 4
  • February CAS Community Call?
    • See Topics
    • .NET client presentation ready for Feb?
  • Determine CAS documentation policy re ICLA requirement
  • Status of CAS Projects & Sub Projects
  • Meet Up Status

Minutes

Discussed licensing strategy. CASUM -> curated experience, CAS -> community-contributed content.
Editors need to watch CAS space and be responsible for evaluating fitness of content for inclusion for CASUM. Need formal solution to correcting mistakes in CASUM – file CASW Jira issues. Allow anyone to post comments in CASUM. Editors need to review comments as well. Do comments need licensing guidelines? CC? Comments should be editorialized – only value-added comments shall be kept. Comments will not be included in printed/reprinted material based on CASUM. Attempt best effort to get ICLA from past CASUM contributors.

Andrew will serve as backup for Feb community call if Scott Holodak falls through. Proxy CAS talk. Andrew pitched rehashing intro to CAS talk to solicit feedback for improvement. Possibly market differently to recruit active devs to attend. March? Pitch Spring conference CAS opportunities at both Feb and March.

Discussed "What's New with CAS" presentation proposal. ClearPass and LDAP Password Policy extensions. Discuss new server framework/API w/r/t server. Diagram/document that maps old API to new. Andrew suggested avoiding excessive detail in server API. CAS4 documentation may naturally be very technical. A more technical treatment should probably be the topic of a community call to be lead by Scott. Scott suggested waiting until CAS4 M1 is ready to indicate concrete progress toward 4.0. Shooting for April.

Developer IRC channel meetings will happen on #cas-dev at 1400EST Fridays.

Andrew suggested moving forward with adopting cas-server-support-ldap-pwd-expiration as an official extension. Move to sandbox and move forward with development/analysis. May require hooks in cas-server-core to properly support.

Action Items

  • Scott will lock down CASUM so only ICLA-signers can edit. There may be existing Confluence group for this. Post new editorial policy on wiki and announce on cas-user.
  • Marvin will contact Bill re Scott Holodak .NET talk for Feb community call.
  • Marvin will follow up with Eric Dalquist to set up Confluence logger bot.
  • Andrew will move cas-server-support-ldap-pwd-expiration into Jasig svn sandbox.