Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Logistics

09:30 AM CDT (10:30 EDT)

Pyle Center Room 232

Toll Number: 608-316-0022
Toll Free Number: 888-677-9189
Passcode: 0760

Attendees

Agenda

  1. Introduction
  2. Quick Overview of Goals of Steering Committee
  3. Summary of Discussions at UnConference
  4. Roadmap Finalization
  5. Setup for Next Meeting
  6. Conclusion (Finalize Action Items)

Notes

  1. Steering Committee Logistics
    1. Modeled after uPortal
    2. Will need to meet with uPortal to bring up to date on roadmap
  2. Introductions
  3. Quick pverview of Goals of Steering Committee
  4. David asked about consistency of committment of resources to project
    1. CAS tends to get contributions according to the needs of participant institutions
    2. Jonathan: We need to figure out how to get more people to contribute, given how large the community is
    3. Scott: We need a model to figure out how to turn unknown contributors into core developers by building their credibility with non-core initial contributions
  5. Summary of Discussions at Unconference
    1. Scott Cantor (from I2/Shibboleth) on site, numerous conversations around Shib, SAML, Federation, CAS/Shib roadmaps and "cohabitation"
    2. CAS protocol discussion
      1. Leaning against new CAS protocol, will probably subset SAML
      2. Should we deprecate CAS 1 and 2 protocols?
        1. Not right now, since no compelling reason and CAS 1 & 2 are widely deployed
        2. Will revisit when client maintenance or something else becomes an issue
      3. SAML appears to be the leading option at the moment, OpenID doesn't seem to get as much traction and appears to have more holes
  6. Jonathan: Would be good to get more feedback from SC members as to activities we should be doing to encourage more feedback
    1. This should be on the agenda for the November meeting
  7. Roadmap Finalization
    1. Rutgers likely to sponsor work to add attribute support into CAS, probably via SAML
    2. Roadmap should be prioritized and outreach should be performed to find out who is willing to do what
      1. SC should wordsmith the roadmap off line or on the next call
    3. We should split up the work into teams/groups charged with specific areas
  8. Setup for Next Meeting
  9. Conclusion/Finalize Action Items

Action Items

  1. SC: Meet with uPortal to bring up to date on roadmap
  2. SC: Figure out contributor model
  3. Scott: Talk to Jim about setting up steering committee mailing list (tick)
  4. Benn: Set up regular monthly meeting time
  5. Scott: Look at SAML profiles for which ones to support in CAS and what might be missing (tick) - still need to send out detailed analysis that Eric and I did
  6. Scott, David: Set up groups charged with requirements and design for
    1. CAS 4 Architecture/Protocol (or determination that current architecture is sufficient)
    2. Monitoring and Metrics
    3. Configuration and Deployment Management
    4. Documentation and Translations
  7. SC: Review Roadmap and send comments to the new SC mailing list
  8. Benn: Set up next agenda, including items called out above
  • No labels