Logistics
Time: Thursday, August 26 @ 12:00 pm Eastern (11:00 am Central) (9:00 am Arizona)
(Rescheduled from Monday August 23 @ noon Eastern, due to conference call line quality / connectivity / technical issues experienced in trying to run that meeting)
Attendees:
Absent:
Note Taker:
Conference call bridge
The conference call is organized by Unlicensed user via Calliflower:
http://apps.calliflower.com/conf/show/117504
Each steerer should have received an individual invite with your own PIN code. You can dial in via a local phone number in your area and potentially save money by doing so from a landline phone without having to call long distance. You can also connect via Skype.
If you need a generic dial in, you can use: +1 218 936 6581 with PIN 21697 but you should use your own PIN instead so that the advanced Calliflower features work better.
All committee members are designated as "moderators", so even if Andrew can't join, anyone else on the committee is empowered to run the call.
Backup
If the Calliflower line above doesn't work, the fallback solution is Unlicensed user's Unicon ATConference line:
Dial in: 866-625-9936
Participant code: 1726190
This solution requires Unlicensed user or someone else to dial in with his host code.
Agenda
- Roll Call; Choose Note Taker
- Thanks to Outgoing Members
- Welcome New Members
- Prior Action Items
- Proposed Developer Calls
- Documentation (Briefly discuss Documentation Stewardship Group)
- Community Call
- Regional Meet-Ups
- Server Status
- 3.5
- MFA
- Potential Integration with 3rd Party
- Unicon's Help with the UI
- Clients
- OWA Support / .NET Client
- Yale CAS Client is still hanging around (see Email thread)
- UnConference
- Jasig Sustainability (bringing value to Jasig CAS users to entice them to become members)
- Leveraging things like Spring Security book with CAS support in it.
- Choose Steering Committee Chair / Who has the 1 year term
Notes
Proceed on dev calls. Ensure we have agenda with objectives. Remove barriers to participation.
Need to discuss how roles are filled in doc proposal. Steering Committee will attempt to fill DC and DL positions. May need to break out responsibilities into actionable items if can't fill whole position, then solicit volunteers.
Regional meet ups shaping up for NYC and Central Fla.
Throw out question re warn box to cas-user regarding removal and replacement with splash page. Bill noted that originally was designed for wide-open CAS server. Service management may have mitigated.
Floated idea of combining OWA and .NET clients by Bill and he is open. .NET client hopefully will release 1.0 version in next month.
Yale client containing multiple clients may need to be repackaged to remove deprecated clients, Java, mod_cas.
Demo CAS and CAS client systems would be helpful both for developers and deployers. May be larger than just CAS – all Jasig products: Bedework, uPortal, etc.
Will table electing Committee Chair and 1-year term person until next meeting or handle on list.
Action Items
- Andrew will follow up w/Spring Security book and create news item on Jasig Web site.