IRC log for #ldstech on 20140324

05:46.37*** join/#ldstech mailman0 (~mailman0@ip70-171-196-244.tc.ph.cox.net)
06:03.23*** join/#ldstech mailman0 (~mailman0@ip70-171-196-244.tc.ph.cox.net)
07:10.11*** join/#ldstech mailman0 (~mailman0@ip70-171-196-244.tc.ph.cox.net)
07:16.31*** join/#ldstech zulugrid_ (jacob@cpe-72-179-187-224.satx.res.rr.com)
12:38.48*** join/#ldstech TyDon (~TyDon@proxy.lds.org)
13:42.08*** join/#ldstech wad (~wad@199-58-199-98.acedc.net)
14:08.19*** join/#ldstech cpitt (~cpitt@2605:6400:2:fed5:22:c569:52ec:4fa7)
14:08.19*** mode/#ldstech [+o cpitt] by ChanServ
14:25.49*** join/#ldstech josephscott (~josephsco@proxy.iad.automattic.com)
14:34.08*** join/#ldstech jonmull (~clbj@proxy.lds.org)
15:27.07*** join/#ldstech joshrees (d831b5fe@gateway/web/freenode/ip.216.49.181.254)
15:27.24*** join/#ldstech ekeating (~Dennis@99-54-46-12.lightspeed.snjsca.sbcglobal.net)
15:28.00*** part/#ldstech zulugrid (jacob@cpe-72-179-187-224.satx.res.rr.com)
15:28.24*** join/#ldstech tiwula (~lane@107-1-184-110-ip-static.hfc.comcastbusiness.net)
15:30.14ekeating~meetstart <LDSTech Dev Scrum>
15:30.15infobot********** Start of the <LDSTech Dev Scrum> Meeting on 2014.03.24 15:30:15 **********
15:30.19ekeatingGood Morning.  I hope everyone had a good weekend.  Mine went way too fast.
15:30.40ekeatinghow are you today jonmull
15:30.46jonmullgood
15:30.59*** join/#ldstech TimRikerS4 (~timr@bzflag/projectlead/TimRiker)
15:31.00*** mode/#ldstech [+o TimRikerS4] by ChanServ
15:31.03ekeatingassume you'll be testing today, true?
15:31.43ekeatingjoshrees, let's go ahead and start with you this morning.
15:32.02jonmulltrue
15:32.24ekeatingmoin TimRikerS4
15:33.18TimRikerS4moin
15:33.44joshreesWorking on swarm still. No blocking issues. End of report.
15:33.56ekeatingshort and sweet.  thanks
15:34.15ekeatingTimRikerS4, let's move on to your report for today.
15:34.59*** join/#ldstech LDSTech (~LDSTech@proxy.lds.org)
15:34.59*** mode/#ldstech [+o LDSTech] by ChanServ
15:35.22LDSTechouch. dropped and could not get back on.
15:35.55TimRikersso on crm now tracks ldsaccountid. we're not handling nick changes at present, but we could move that direction in the future.
15:36.01ekeatingI know that feeling
15:36.14TimRikerwill be testing today. hopefully deploying this week, right?
15:36.32TimRikertomorrow after staff mtg? thoughts?
15:36.47ekeatingright! Will we have a problem being within the Conference window?
15:37.31ekeatingtomorrow sounds good to me.
15:37.36TimRikertechnically, yes. but actually this involves no changes to conf related infrastructure. thoughts?
15:38.09ekeatingIt seems to me we deployed once during the window.
15:38.13TimRikerI would not want to do it the week of conf, but I'm comfortable with this.
15:38.19ekeatingso I think we'll be okay.
15:38.43TimRikerthis will put the crm up live. need to decide how to setup groups and permissions on the live install.
15:38.45ekeatingI am too.  do you think we should pass it by smootar?
15:39.03TimRikerurpd data may live there as well as ldstech missionary tracking data.
15:39.28TimRikerwe've not looked into how-can-I-only-see-and-edit-my-own-info or similar.
15:39.31*** join/#ldstech anderwest (~anderwest@proxy.lds.org)
15:39.38ekeatinggetting crm up live would be great.
15:39.43TimRikersure. I'll look for him today.
15:40.11TimRikerNot sure if elder bottorf [sp?] ever got it checked out locally or tried cdev.
15:40.45ekeatingI don't think it will be a problem, but just feel better with his blessing.  If you want I can contact him.
15:41.00TimRikeranyway, point is there is still a lot of work to do there, and we're not sure what is next exactly. but at least putting it live is a step in the right direction.
15:41.15TimRikerI'll poke my head in today and ask.
15:41.19ekeatingagreed
15:41.31ekeatingokay, thanks
15:41.35ekeatingmoin anderwest
15:42.12ekeatinganderwest, are you ready with your report?
15:42.14*** join/#ldstech GvzEvxre (~TimRiker@bzflag/projectlead/TimRiker)
15:42.14*** mode/#ldstech [+o GvzEvxre] by ChanServ
15:42.41ekeatingGvzEvxre, ? TimRiker
15:42.59TimRiker~rot13 TimRiker
15:42.59infobotGvzEvxre
15:43.03TimRiker~rot13 ekeating
15:43.03infobotrxrngvat
15:43.11TimRikeralter ego
15:43.19ekeatingokay, thanks
15:43.42ekeatinganderwest, ?
15:43.50TimRiker~+help rot13
15:43.57anderwestSorry, I'm here, nothing to report
15:44.23ekeatingokay, will you have time to test some of the resolved issues on 1.4?
15:44.39TimRiker1.4?
15:45.17ekeatingsorry 4.0  don't know what I was thinking
15:45.25TimRikerjust 4. :)
15:45.36ekeatingjust 4   ;)
15:45.42anderwestYes, I'll look at them
15:45.58anderwestwhat I can figure out anyway
15:45.59ekeatinggood.  I'm  glad we got through that  :)
15:46.35ekeatingUnfortunately we're out of time so I'll end this meeting if there isn't anything else we need to discuss.
15:47.46ekeatingAlright. Thank you, again, for all that you're doing. Have a productive day and “see” you tomorrow
15:47.48ekeating~meetend <LDSTech Dev Scrum>
15:47.48infobot********** End of the <LDSTech Dev Scrum> Meeting on 2014.03.24 15:47:48 **********
15:47.55*** join/#ldstech wad (~wad@199-58-199-98.acedc.net)
15:48.01ekeating~help
15:48.07ekeatinghelp
15:48.54TimRikernormally the bot responds in private chat to help and other requests.
15:49.01TimRikeryou can address it like this:
15:49.05TimRikerinfobot, hello
15:49.05infobotHowdy Bub
15:49.18ekeatingcute
15:49.28ekeatingthanks TimRiker
15:49.31TimRikeror ~ is the short char in this channel. other bots and other channels may set different addressing characters.
15:49.34TimRiker~hello
15:49.34infobotHowdy Bub
15:49.56TimRikerrot13 means "rotate 13 characters" so:
15:50.13TimRiker~rot13 abcdefghijklmnopqrstuvwzyz
15:50.13infobotnopqrstuvwxyzabcdefghijmlm
15:50.35TimRikera->n b->o etc.
15:50.45ekeatingah I see
15:50.53TimRikerso doing it again gets the test back. simple obfuscation.
15:51.01TimRiker~rot13 nopqrstuvwxyzabcdefghijmlm
15:51.01infobotabcdefghijklmnopqrstuvwzyz
15:51.02ekeatingmakes sense but not sure why it would be used.
15:51.33TimRikerrot13 so you can put a hint in an email or on a web page that is not immediately viewable. things like that.
15:51.37TimRiker~rot13 so you can put a hint in an email or on a web page that is not immediately viewable. things like that.
15:51.37infobotfb lbh pna chg n uvag va na rznvy be ba n jro cntr gung vf abg vzzrqvngryl ivrjnoyr. guvatf yvxr gung.
15:51.38ekeatingI'm confused enough on this team.  :D
15:52.05TimRikersolution to a riddle, etc.
15:52.17TimRikerdoes not work for numbers.
15:52.33ekeatingI be thinking you have way too much time on your hands.  :)
15:52.33TimRiker~rot13 try and hide my phone# 800-555-1212
15:52.33infobotgel naq uvqr zl cubar# 800-555-1212
15:52.52TimRikerit's a silly thing. geek humor.
15:53.01TimRikerbot does any # of rot.
15:53.02ekeatingso it doesn'e deal with numbers?
15:53.09TimRiker~rot1 abcde
15:53.09infobotbcdef
15:53.21TimRikereven the silly:
15:53.27TimRiker~rot26 abcde
15:53.27infobotabcde
15:53.40ekeating~rot2 1234
15:53.40infobot1234
15:53.48TimRiker"twice as secure as rot13 we have rot26!" lol
15:54.09TimRikerrot13 just "rotates" letters.
15:54.26ekeatingso it doesn't hide your phone number
15:54.49TimRikernor puntuation, etc. just letters.
15:55.01TimRikerbot does other silly things
15:55.13ekeatingsuch as?
15:55.19TimRiker~reverse can be used to reverse text. Not very useful, just fun.
15:55.32ekeatingcool
15:55.45TimRikernot sure if this one if working...
15:56.51TimRiker~upsidedown Let's see if upsidedown works at present. It has UTF-8 issues.
15:57.02TimRikeryay. :)
15:57.15ekeatingwhoa, impressive
15:57.49TimRikersilly unicode tricks. :)
15:58.03ekeatinggeeky but cool
15:58.21TimRiker~convert 60 miles/hour to kilometers/hour
15:58.34TimRiker~convert 60 miles/hour to inches/second
15:58.47TimRiker~123123 * 1231231
15:58.47infobot151592854413
15:58.47ekeatingamazing
15:59.15TimRiker~convert 60 miles/hour to barleycorns/nanosecond
15:59.16ekeatingI can use that every time I have to deal with metrics.
15:59.45ekeatingbarleycorns is new to me
16:00.00TimRikerheh. anchient measurement before inches.
16:00.11TimRiker~spell anchient
16:00.36ekeatingwow, I'm amazed at your depth of trivia.  :)
16:00.52TimRikerlol
16:01.03TimRiker~seen wearnshaw
16:01.10infobotwearnshaw <~William@proxy.lds.org> was last seen on IRC in channel #ldstech, 2d 18h 52m 14s ago, saying: 'And there are no infinite redirect loops? :D'.
16:01.27ekeatingsame to ya buddy.   ;)
16:02.41ekeatingI better go and let you get back to work.  Kooks like anderwest  could use some help testing.
16:03.16TimRikerk. :)
16:03.16ekeatings/Kooks/Looks/
16:03.44ekeatingthanks for your help TimRiker .  I really appreciate it.
16:13.52*** join/#ldstech wearnshaw (~William@proxy.lds.org)
16:13.52*** mode/#ldstech [+o wearnshaw] by ChanServ
17:09.00*** join/#ldstech anderwest_ (~anderwest@proxy.lds.org)
19:18.45*** join/#ldstech tiwula (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net)
19:39.28*** join/#ldstech cpitt (~cpitt@2605:6400:2:fed5:22:c569:52ec:4fa7)
19:39.36*** mode/#ldstech [+o cpitt] by ChanServ
20:33.56*** join/#ldstech robotarmy347 (~robotarmy@68.69.166.209)
23:06.40*** join/#ldstech pdayton (~Adium@63.251.sfcn.org)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.