Page Comparison

...

1. Elections
   1. New terms begin in September, however newly elected representatives will be invited to the August call.
   2. Chair of the steering committee is currently the technical representative. Jonathan proposed that the steering committee selected chair instead.
   3. Vote for the technical representative needs to happen ASAP.
2. RFCs
   1. CASShib - stalled
   2. Status of the RFCs should be reviewed at the next community call.
3. Renaming CAS
   1. We should come up with a specific recommendation or recommendations for potential new name, and analyze what impacts the new name might have, before presenting a recordation to the board.
4. August 2009 Community Call is August 12 at 2pm.
5. Clients
   1. Is the steering committee OK with the grid attributes?
6. Marketing
   1. Scott talked to Jim LaneLayne, they're working on it, will try to have it addressed soon.
7. CASifying Outlook
   1. Still need documentation to recommend an alternative.
   2. Sacramento State might have CASified Outlook, but unclear if they have time to write it up or if they're even using it at all.
8. mod_cas
   1. CCCI has updated wiki.
   2. Yale says don't use mod_cas anymore.
9. Conferences
   1. Items for CAS development at the unconference?
10. ClearPass
    1. How much support is CampusEAI willing to provide?
    2. What we want: a committer willing to commit to timely releases of bugs, patches, fixes, and any changes needed to work with CAS server updates. Maintenance, not development.
11. CAS Positions/Roles
    1. Potential roles include documentation coordinator, documentation writer (including both the webpages and the wiki), marketing, UI developers, CAS client community liaison, release engineer, testing/QA, technical lead, committer, steering committee member.
    2. Jonathan can add language to help institutions justify this work.

...