/
2009-01-26 Conference Call

2009-01-26 Conference Call

Jan 28, 2009

Logistics

Time: Jan 26 2009, 10:30am
Conference Bridge: 218-486-7200 #167964

Attendees

  • @ScottS

  • @Benn Oshrin

  • @Jonathan Markow

  • @Eric Pierce

Absent

  • @David L. Whitehurst

  • @Troy Bull

Agenda

  1. Review old Action Items

  2. Review and approve RFC Process

  3. Review and approve takeover of CAS protocol management

    1. determine who updates protocol document

  4. Review locating CAS3 maintainer while CAS4 development continues

  5. Feb/Mar calls vs Jasig Conference

  6. More Formal Strategy (i.e. uPortal)

Notes

  1. There will be no more Community Calls until after the Dallas conference

  2. Too many roadmap pages?

  3. Having trouble finding leads for service management and monitoring subgroups

  4. RFC Process

    1. Discussion of Howard's comment: We'll put a permanent link somewhere

    2. Contrib is independent of process

      1. Developers review contrib

      2. It's contrib unless someone starts the RFC

      3. RFC review could result in "it's contrib"

  5. Andy Newman was ok with CAS SC taking ownership of existing CAS protocol management, and SC voted its approval

    1. SC has final responsibility for protocol document, but updates to it could be delegated

  6. February call will be replaced with Dallas conference meeting (and call in)

  7. March call TBD

  8. We should have a high level vision statement for CAS (similar to uPortal)

    1. Where does CAS fit in, especially with I2 middleware?

    2. Future direction/roadmap

    3. CAS "info sheet"

    4. Positioning statement, vs I2 middleware, Sun, Oracle, etc

Action Items

  • Benn: Update RFC Process for Howard's comments

  • Scott: Write definitions for contrib, give to Benn to review against Incubation terminology (see also AI from January 2009 Conference Call

  • Scott: Poke around to see if anyone is interested in the subgroup lead positions, and/or in maintaining CAS 3.x

  • All: Discuss high level vision at Dallas

Carryover

  • Scott: Roadmap cleanup & updates, including

    • Add to JIRA

    • Add a column to the roadmap indicating who has committed to doing what

    • Sort roadmap items into the groups identified in the agenda and find leads for each

  • New Working Groups: Begin requirements gathering and prioritize decision

  • ?: Propose clear text password feature as test of new development process