[12:59:57 CDT(-0500)] <apetro> checking in
[13:00:35 CDT(-0500)] <wgthom> ditto
[13:02:36 CDT(-0500)] <apetro> set up a concurrent Google Talk hangout, just because. Dunno if this link works for that purpose. https://talkgadget.google.com/hangouts/97388902ec358689d2962671817c64eea6b6a862
[13:11:59 CDT(-0500)] <wgthom> bill and andrew on the g+ hangout...who's going to join us
[13:38:03 CDT(-0500)] <wgthom> hi scott
[13:38:09 CDT(-0500)] <apetro> battags how's that CAS audio book coming?
[13:38:57 CDT(-0500)] <battags> hey
[13:39:04 CDT(-0500)] <battags> still trying to find the right narrator for the job 
[13:39:10 CDT(-0500)] <battags> apparently people don't like my voice
[13:39:11 CDT(-0500)] <battags> ha
[13:45:06 CDT(-0500)] <apetro> hey
[13:45:16 CDT(-0500)] <wgthom> any chance we you can join us on g+ hangout
[13:46:10 CDT(-0500)] <wgthom> scott?
[13:47:26 CDT(-0500)] <battags> sure
[13:47:34 CDT(-0500)] <battags> is that preferable to IRC?
[13:48:46 CDT(-0500)] <apetro> richer communication better?
[13:48:47 CDT(-0500)] <wgthom> maybe...seems to working pretty swell
[13:48:49 CDT(-0500)] <apetro> more novel and fun?
[13:48:57 CDT(-0500)] <battags> I can't really do a video chat
[13:49:00 CDT(-0500)] <apetro> k
[13:49:04 CDT(-0500)] <wgthom> ah
[13:49:07 CDT(-0500)] <battags> didn't realize it was video
[13:49:18 CDT(-0500)] <apetro> ok
[13:49:26 CDT(-0500)] <wgthom> ok we hung up
[13:49:27 CDT(-0500)] <apetro> we were mostly chatting about unrelated things
[13:49:36 CDT(-0500)] <battags> has Marvin been in the room today?
[13:49:39 CDT(-0500)] <apetro> but the cas-dev piece was mostly about TGT timeout strategies
[13:49:50 CDT(-0500)] <apetro> haven't seen serac, but I've been here only briefly
[13:49:51 CDT(-0500)] <battags> looking for someone to validate the 3.4.9 pending code
[13:50:28 CDT(-0500)] <apetro> so, in particular, the infinitely-renewable-through-usage TGT expiration policy seems... like not what most would want
[13:50:34 CDT(-0500)] <wgthom> what needs to be done for validation?
[13:50:57 CDT(-0500)] <apetro> and even in the renewable-through-usage case, it would be good to have a hard timeout
[13:51:02 CDT(-0500)] <apetro> hmm
[13:51:08 CDT(-0500)] <apetro> two threads here. I'll pause mine 
[13:51:58 CDT(-0500)] <battags> everything needs to be validated
[13:52:07 CDT(-0500)] <wgthom> lol
[13:52:09 CDT(-0500)] <battags> it can't be released until there are some +1
[13:52:28 CDT(-0500)] <wgthom> sanity deploy test? build? code review?
[13:52:49 CDT(-0500)] <battags> whatever is needed for you to feel comfortable giving it a +1
[13:52:56 CDT(-0500)] <battags> I haven't done a deploy/functional test yet
[13:53:42 CDT(-0500)] <wgthom> is there an deployable rc available?
[13:54:45 CDT(-0500)] <wgthom> or do i have to build it
[13:56:06 CDT(-0500)] <wgthom> jira reports 3.4.9 still has an open issue: https://issues.jasig.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+CAS+AND+fixVersion+%3D+%223.4.9%22+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide
[13:57:04 CDT(-0500)] * yann2 really hopes you wont be replacing IRC with facebook/g+ or so 
bad for logging, need registration
[13:57:50 CDT(-0500)] <wgthom> prolly not...but g+hangout seems like it would be really useful for dev calls
[13:57:57 CDT(-0500)] <wgthom> or cas-steer calls
[13:58:37 CDT(-0500)] <wgthom> so back to the TGT Expiration policy?
[13:58:50 CDT(-0500)] <apetro> yeah
[13:58:52 CDT(-0500)] <wgthom> coming up on 3pm
[13:59:17 CDT(-0500)] <apetro> do we need a MultiPolicyTicketExpirationPolicy meta-policy?
[13:59:37 CDT(-0500)] <apetro> that takes as a dependency a Set of policies, polls them, and expires if any of them think the ticket should be expired?
[13:59:50 CDT(-0500)] <apetro> that would allow composing the existing Timeout and HardTimeout policies
[13:59:57 CDT(-0500)] <wgthom> maybe
[14:00:09 CDT(-0500)] <wgthom> prolly?
[14:00:13 CDT(-0500)] <apetro> it might also allow composing in the throttling / multi use
[14:00:22 CDT(-0500)] <wgthom> yep and others as they are identified
[14:00:36 CDT(-0500)] <apetro> currently there's MultiTimeUseOrTimeoutExpirationPolicy
[14:00:42 CDT(-0500)] <apetro> ThrottledUseAntTimeoutExpirationPolicy
[14:00:42 CDT(-0500)] <apetro> etc.
[14:00:59 CDT(-0500)] <wgthom> right...combinatorial explosion we need not
[14:01:24 CDT(-0500)] <apetro> i.e., there's already examples of combinatorialism, such that having one set-taking metapolicy might make this clearer
[14:01:47 CDT(-0500)] <apetro> or skip that and have the registry itself accept a Set rather than just a single policy, if there's only one consumer of these policies anyway
[14:01:56 CDT(-0500)] <apetro> I know I'm over prone to create meta objects
[14:02:07 CDT(-0500)] <apetro> cf PersonAttributeDAO implementations
[14:02:49 CDT(-0500)] <wgthom> well Java-land does like its nouns
[14:03:43 CDT(-0500)] <apetro> I've been having great fun reading about Tweedle Beetles with the six year old
[14:04:40 CDT(-0500)] <apetro> alright, I'll create a JIRA gesturing towards a meta-policy, the motivation specifically around infinite-renewabilty probably isn't in anyone's interest, and see where it goes from there.
[14:05:04 CDT(-0500)] <wgthom> sounds good. my time is up..i thank you for yours
[14:06:09 CDT(-0500)] <battags> that issue should be resolved now
[14:13:14 CDT(-0500)] <apetro> JIRA issue created: https://issues.jasig.org/browse/CAS-1003
[14:24:52 CDT(-0500)] <wgthom> i don't see a 3.4.9 tag in svn
[14:25:31 CDT(-0500)] <wgthom> is scott asking for verification on HEAD of https://source.jasig.org/cas3/branches/cas-3_4_x_maintenance/cas-server-3.4.2
[14:25:33 CDT(-0500)] <wgthom> ?
General
Content
Integrations