November 2008 Conference Call

Owned by Benn Oshrin
Last updated: Nov 19, 2008 by ScottSVersion comment
2 min read

Logistics

Time: Nov 19 2008, 10am
Conference Bridge: 218-486-7200 #167964

Attendees

Agenda

  1. Notes from the Unconference
    1. Steering Committee update
  2. Development Processes
    1. Process for deciding if something is part of core
    2. Standard place for patches/contributions that aren't going to be included in the core
    3. How does the protocol evolve? For example:
      1. Requirements from the community
      2. Discussion with the community (RFC, Email, Conference Calls)
      3. Recommendations by committers
      4. Approval by steering committee
  3. Regular (biweekly?) roadmap calls?
    1. Each focused on one or two items for discussion

Notes

  • Steering Committee Overview: Questions about deprecating CAS protocol? NO! Any conversation would include Yale
  • Steering Committee Overview: Moving to SAML
  • Development Process: Separate out protocol evolution (i.e. CAS1 or 2 evolution) vs. software evolution
  • Question: Who actually "owns" the CAS protocol?
  • Why are we having this discussion? Possibly have a clarification of protocol / errata?
  • Fix mistakes, clarify ambiguities, and officially bless new features?
  • Yale potentially interested in continuing to maintain the CAS protocol document but willing to defer to CAS Steering Committee.
  • Protocol document was an afterthought; made so that people knew what the protocol would be if they wanted to implement it in another language
  • Steering Committee responsible for software: definitely; CAS protocol? probably
  • Use creation of new features in CAS4 to vet out development process
  • Overall, in general sense, development process seems okay
  • Request for Comment via email, etc. Recommendation via Phone.
  • Because of holiday, one call. Probably have one call per month for now. May add more if necessary.

Action Items

  • Send mail to CAS lists about potentially scope-creeping CAS Steering Committee from software to software and protocol
  • Howard: Check with Andy on whether he is okay with having Steering Committee take over protocol evolution
  • Howard & Scott: Come up with proposal about contributions (official, unofficial, random, contrib, Maven2 repository, etc.) - technical
  • Steering Committee: Add scope-creeping CAS Steering Committee to agenda of Steering Committee
  • Howard & Susan, Scott & Ben: procedures around contributions - talk to Incubation Working Group
  • Benn: draft of development process
  • Scott: seed list with roadmap discussion items