IRC log for #ldstech on 20120430

00:28.35*** join/#ldstech chrxn_ (~chrxn@pool-71-189-228-162.lsanca.fios.verizon.net)
01:18.23*** join/#ldstech chrxn_ (~chrxn@pool-71-189-228-162.lsanca.fios.verizon.net)
02:06.31*** join/#ldstech hackman42 (~Adium@69.169.128.17.provo.static.broadweavenetworks.net)
03:26.02*** join/#ldstech J_Voracek (~J_Voracek@cpe-70-123-106-75.tx.res.rr.com)
03:47.31*** join/#ldstech chrxn_ (~chrxn@pool-71-189-228-162.lsanca.fios.verizon.net)
05:48.11*** join/#ldstech chrxn_ (~chrxn@pool-71-189-228-162.lsanca.fios.verizon.net)
11:13.28*** join/#ldstech eldergunn (~eldergunn@02de72fa.bb.sky.com)
12:38.39*** join/#ldstech eldergunn (~eldergunn@02de72fa.bb.sky.com)
13:20.22cpittback
13:37.00*** join/#ldstech eldergunn (~eldergunn@02de72fa.bb.sky.com)
13:47.56*** join/#ldstech hackman42 (Adium@nat/novell/x-bwitsraalhyrwvfj)
14:40.29*** join/#ldstech coderjeff (~chatzilla@c-174-52-245-33.hsd1.ut.comcast.net)
14:45.20*** join/#ldstech tdeforest (tdeforest@conference/ldstech/x-vmhvptoqzmafqofq)
14:45.20*** mode/#ldstech [+o tdeforest] by ChanServ
14:50.44*** join/#ldstech ekeating (~Dennis@99-54-46-12.lightspeed.snjsca.sbcglobal.net)
14:51.26tdeforestwaves
15:00.32*** join/#ldstech zakzakattack (zakzakatta@conference/ldstech/x-wmqkiduvinmfkuvw)
15:00.48ekeating~meetstart <LDSTech Dev Scrum>
15:00.49infobot********** Start of the <LDSTech Dev Scrum> Meeting on 2012.04.30 15:00:49 **********
15:00.56smootarmoin
15:01.00ekeatingGood Morning
15:01.08ekeatingWho's made it through the weekend and is here today?
15:01.26tdeforestmade it
15:01.32zakzakattackHere
15:01.34cpittpresent
15:01.52*** join/#ldstech KFitz (KFitz@conference/ldstech/x-syeqzabggxjtxeer)
15:02.08*** join/#ldstech jdavid26 (~Adium@63-248-90-196.static.sdyl0420.digis.net)
15:02.35ekeatingGreat.  I'm sure the rest will be wandering in soon.
15:02.39ekeatingFullmercb won't be with us today but sent the following report
15:02.39ekeatingNot much to report except meetings with ICS solution managers are going well and will bring us new qa and csm opps. (possibly new project work too)
15:02.54*** join/#ldstech TimRiker (TimRiker@bzflag/projectlead/TimRiker)
15:03.10*** mode/#ldstech [+o TimRiker] by ChanServ
15:03.10ekeatingAs you report please include when you think the issues will be complete
15:03.10ekeatingWe want to try and set a release date for 2.6.3
15:04.09ekeatingLet's start with cpitt.  Any staus update on
15:04.11ekeatinghttps://tech.lds.org/jira/browse/LDSTECH-701
15:04.55cpittI'm pretty sure it's all done, it counts all the words in blog posts and reports them accordingly
15:05.34cpittthe only question I had that I was going to ask before I closed it was are blog posts the only thing we're counting?
15:06.00cpittif so it's done
15:06.08TimRikerticket mentions wiki too.
15:06.38cpittif that's the case i need to incorporate the wiki into and then it will be done
15:06.45TimRikerI suggest we edit this one to mention blog only, then close it. open another for just the wiki.
15:07.39ekeatingWould that stay in 2.6.3 or the next release
15:07.55cpittThe reporting section states "Wrote 'X' words since blog project began middle of this year." so I wasn't sure
15:08.01TimRikerI think we ought to test and release what we have.
15:08.17tdeforestagrees with TimRiker
15:08.47ekeatingsounds good to me...I like releases  :-)
15:09.46ekeatingWe can move the new one to the 2.6 backlog and include it in the new sprint
15:10.43TimRikernods
15:11.00ekeatingthe remaining open issues are assigned to scgallafent
15:11.09ekeatinghttps://tech.lds.org/jira/browse/LDSTECH-531
15:11.09ekeatinghttps://tech.lds.org/jira/browse/LDSTECH-688  
15:11.09ekeatinghttps://tech.lds.org/jira/browse/LDSTECH-712
15:11.23ekeatingAnyone have any info on these?
15:11.24TimRikerI closed 688
15:11.46TimRikeroh, sry wrong issue...
15:12.09smootarStepping away to let in scgallafent...
15:12.27TimRikerI closed 229 which was scgallafent but is resolved with the google groups integration.
15:12.40ekeatingThanks TimRiker
15:12.55ekeatingI'll take it off my list
15:13.28TimRiker688 is marked closed. scgallafent split it up into different issues.
15:13.42ekeatingzakzakattack: Need any help on the resolved issues?
15:14.10*** join/#ldstech JoshBang (JoshBang@conference/ldstech/x-uehenuetpwylawaz)
15:14.13zakzakattackum.... not for now... i might have some questions later on but for now i dont
15:14.47ekeatingWhen do you think they'll be closed?
15:14.59TimRikerI don't see omniture loading for forum or wiki.
15:16.22zakzakattackI closed 2 on friday the rest i have no Idea what to do on them like  LDSTECH-675,217,703
15:16.23TimRikermoved https://tech.lds.org/jira/browse/LDSTECH-715 to 2.6.3. probably want to bump it out, but it was not assigned a release.
15:18.01TimRikermoved the other omniture tickets in too. need to decide which to bump. perhaps all of them.
15:20.20TimRikerhttps://tech.lds.org/jira/browse/LDSTECH-620 closed as a dupe of 609
15:22.08ekeatingWhen scgallafent gets on lets talk about the omniture issues and see what we want to do with them
15:22.09TimRikeroverview: https://tech.lds.org/jira/secure/IssueNavigator.jspa?jqlQuery=fixVersion+%3D+%222.6.3%22+AND+project+%3D+LDSTECH
15:22.44tdeforestTimRiker, link doesn't work
15:23.02TimRikerhmm
15:23.23TimRikerhttps://tech.lds.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=fixVersion+%3D+%222.6.3%22+AND+project+%3D+LDSTECH ?
15:25.54TimRikerhttps://tech.lds.org/jira/browse/LDSTECH-284 is resolved, moved to 2.6.3
15:27.12cpittquick question about https://tech.lds.org/jira/browse/LDSTECH-541 is 60 chars acceptable with everyone.... if so we can mark it as resolved
15:27.57*** join/#ldstech johnsonth (JohnsonTH@conference/ldstech/x-nffswksakdqudyog)
15:28.11TimRikercpitt, I'm good.
15:28.28ekeatingseems reasonable to me.  Anyone else have a thought
15:29.02tdeforestcpitt, iz good
15:29.20cpittwell if there is no objections marking it as resolved
15:29.21ekeatingOkay, cpitt go ahead and resolve it.  Thanks
15:30.02cpittshould I assign it to zakzakattack ?
15:30.10ekeatingyes
15:30.23zakzakattackok cool
15:31.07ekeatinglooks like scgallafent won't be with us today so are there any other items you want to discuss?
15:31.45ekeatingTimRiker can you get with him and discuss the omniture issues?
15:32.12TimRikerhe's just getting plugged in here. we'll talk sometime today.
15:32.23ekeatingWe'll try to pin them down tomorrow.
15:32.29TimRikerHe may be able to read the big screen between smootar and I
15:32.52jdavid26How's https://tech.lds.org/jira/browse/LDSTECH-531 ?
15:34.29tdeforestjdavid26, i haven't heard but i know scgallafent is juggling several Omniture tasks at the moment.
15:34.52tdeforestjohnsonth, do you know the answer to jdavid26 's question above?
15:35.08johnsonthscgallafent is working on that one.
15:35.12johnsonththe skin is totally finished.
15:35.20johnsonthit's just a matter of whether it integrates with the environment.
15:35.23johnsonthgiven all our customizations.
15:35.31johnsonthbut it now works with 1.18.
15:35.38jdavid26awesome
15:35.42johnsonthbtw, the newsletter went out this weekend. If you missed it, here's the link: http://t.co/X5lTv4Ql
15:35.42johnsonthWe should make it easier to sign up for this thing.
15:36.14johnsonthmost feedback/comments is about Maps 3.0.
15:36.28tdeforestnods at johnsonth
15:37.15johnsonthThanks for sending that out, tdeforest.
15:37.32tdeforestyou're welcome!
15:37.58ekeatingI would like to see the “Issues” screen sorted by key # when you first go in.  
15:37.58ekeatingOtherwise I have to sort it, find what I'm looking for, then do a back arrow
15:37.59ekeatingwhich takes me to the unsorted list and another back arrow to get where I came from.
15:37.59ekeatingDo I need to set that up as an issue?
15:38.46TimRikerI don't understand...
15:38.51tdeforestekeating, you might be able to save that as a filter or predefined query
15:39.10ekeatingIt doesn't matter much except on the closed issues when trying to see what's closed
15:39.32*** join/#ldstech J_Voracek (~J_Voracek@cpe-70-123-106-75.tx.res.rr.com)
15:39.39J_Voracek<PROTECTED>
15:40.28ekeatingTimRiker go  to https://tech.lds.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+LDSTECH+AND+fixVersion+%3D+%222.6.3%22+AND+status+%3D+Closed+ORDER+BY+priority+DESC&mode=hide
15:40.57TimRikerok. then?
15:41.13ekeatingnotice the key (issue) numbers are not sorted so to find a particular issue I first sort them
15:41.33ekeatingthen when I hit the back arrow it takes me to the unsorted list again
15:41.36TimRikerthe link you posted DOES sort them.
15:41.49ekeatingI have to hit it one more time to get where I came from
15:41.54TimRikerit just sorts by priority. if that's not what you want, then don't sort by that. :)
15:42.14TimRiker.... ORDER+BY+priority+DESC ....
15:43.11ekeatingHow do I filter it to sort by number?
15:43.39ekeatingI'll work on it, thanks
15:43.44ekeatingI have another small quirk that irritates me every time I see it.  I would change it if I knew how.
15:43.44ekeatingUnder “Security Level:” It states
15:43.44ekeatingPublic (Access is granted to everyone, if the project is set to anonymous access includes the outside would.)
15:43.44ekeating“would”???
15:44.10ekeatingfor now we'll close this meeting thank you everyone
15:44.14smootarwonders if TimRiker upgraded the LDSTech version of php.
15:44.26TimRikersmootar, nope
15:44.31smootarnods
15:44.31ekeating~meetend <LDSTech Dev Scrum>
15:44.31infobot********** End of the <LDSTech Dev Scrum> Meeting on 2012.04.30 15:44:31 **********
15:44.59TimRikerhttps://tech.lds.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+LDSTECH+AND+fixVersion+%3D+%222.6.3%22+AND+status+%3D+Closed&mode=hide
15:44.59ekeatingBTW our next scrum meeting will be Wed.
15:45.20TimRikerekeating, then save that as a filter if you want it later.
15:46.04ekeatingThanks Tim
15:46.28TimRikersome spaces are redundant... https://tech.lds.org/jira/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project%3DLDSTECH+AND+fixVersion%3D%222.6.3%22+AND+status%3DClosed&runQuery=true&clear=true
15:46.51TimRikerwell, perhaps not redundant. unnecessary
15:47.10ekeatingThat works best for me, especially on closed issues
15:47.21TimRikerkewel
15:51.41*** join/#ldstech scgallafent (scgallafen@conference/ldstech/x-kxtbfxtmcwxefhph)
15:51.41*** mode/#ldstech [+o scgallafent] by ChanServ
16:00.31*** join/#ldstech johnsonth (JohnsonTH@conference/ldstech/x-rkrchheuxqukvbvk)
16:04.23*** join/#ldstech eldergunn (~eldergunn@02de72fa.bb.sky.com)
16:23.27*** join/#ldstech scgallafent- (scgallafen@conference/ldstech/x-tqsaneiuicdwjkxi)
16:23.27*** mode/#ldstech [+o scgallafent-] by ChanServ
16:25.15*** join/#ldstech jdavid26 (~Adium@63-248-90-196.static.sdyl0420.digis.net)
16:31.38*** join/#ldstech tiwula (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net)
16:36.51*** join/#ldstech rpflo (~rpflo@216.51.73.6)
16:39.04*** join/#ldstech zakzakattack (zakzakatta@conference/ldstech/x-dpfmphilibpmwboc)
16:39.06*** join/#ldstech tdeforest (tdeforest@conference/ldstech/x-acxddbsazuicjjao)
16:39.06*** mode/#ldstech [+o tdeforest] by ChanServ
16:44.47eldergunnhi someone asked me on sunday, a member of the stake presidency infact and we also got an e-mail about it on tech shared does anyone survey what tools on lds.org people use the most because their words was "there is a lot that none uses" so just a thought
16:45.47eldergunnand do the keep a track on how many people use other related lds sites eg mormon channel?
16:46.55eldergunnone last question as well i know its family indexing but still techy why on mobile apps dont your indexing class towards your stake numbers do anyone know?
16:59.53tdeforesteldergunn, i peeked at the source code on the calendar app. it appears they're using Omniture to collect site traffic
17:08.56*** join/#ldstech Jazzee8845 (~Jazzee884@host86-144-138-157.range86-144.btcentralplus.com)
17:09.10Jazzee8845hello all
17:13.37tdeforestwaves
17:24.46eldergunnthanks tdeforrest
17:43.02tdeforestsure
17:49.33tdeforestTimRiker, the following tickets are assigned to you. are you really the one to work on these or should they be assigned to PK: https://tech.lds.org/jira/browse/SWARM-396
17:49.33tdeforesthttps://tech.lds.org/jira/browse/SWARM-397
17:49.33tdeforesthttps://tech.lds.org/jira/browse/SWARM-398
17:49.33tdeforesthttps://tech.lds.org/jira/browse/SWARM-399
17:50.13tdeforestsame with 401 and 402
18:01.33tdeforestscgallafent, TimRiker smootar, cpitt, fullmercb , i'm headed to the cafeteria to warm up my lunch. care to join?
18:01.52scgallafentthinks that sounds like a great idea
18:02.08TimRikerI'm hungry. cpitt?
18:16.10*** join/#ldstech chrxn_ (~chrxn@pool-71-189-228-162.lsanca.fios.verizon.net)
19:13.20eldergunndoes anyone know how do download vso image resize while on sophos all i get is blocked website have been asked to download it to shrink images for guides but global services said when i phoned dont worry about sizes of image you have access to filesend
19:24.37TimRikerbroke tech
19:27.43smootar:[
19:28.36TimRikerand we're back...
19:33.22TimRikerer, mostly.
19:42.16TimRikerphp upgrade broke memcached as sles 10.3 does not have a working memcached
19:42.27TimRikernot sure what that breaks...
19:42.48TimRikerwell, php "downgrade" I suppose
19:56.35tdeforestTimRiker, i'm going to put a note on the homepage about the forum being down.
20:02.23johnsonthtdeforest, A lot of people who should have received the newsletter  -- that is, project leads of LDSTech community projects -- didn't receive it.
20:02.45johnsonthDo you know who the list included? I thought it included everyone who has the right Subscriptions check boxes selected on their LDS Account.
20:02.52tdeforesthmmm...
20:02.52johnsonthAs well as anyone who has ever logged into LDSTech before.
20:03.00johnsonthWhich would include project leads.
20:03.13tdeforestthe list does not automatically include project leads
20:03.50tdeforestit _does_ (or should) include those that have the appropriate box checked on their ldsaccount
20:04.23tdeforesthave you identified people that have received it in the past and have not received it this time?
20:05.31tdeforestin the past we have not exported our LDSTech email list for use with the newsletter
20:06.43tdeforesti don't know if the agreement includes privileges for that.
20:06.59TimRikerforums were broken without php-memcache.
20:07.15johnsonthI checked my wife's email account just now. She has the right subscription check boxes selected, but she did not receive the e-mail.
20:07.20TimRikerforums are back.
20:08.03TimRikerI don't know for sure who it includes and who it does not.
20:09.51tdeforestjohnsonth, has your wife opted-out of the email?
20:09.57johnsonthno
20:10.17johnsonthdo you mean opted out of receiving emails through the joomla project interface?
20:10.26tdeforestno
20:10.31TimRikerk. is anything on the main site broken now?
20:10.42tdeforesti mean clicking on 'unsubscribe' on a previous email
20:11.06johnsonthtdeforest, I don't think she ever clicked unbuscribe.
20:11.19TimRiker~spell unbuscribe
20:11.24tdeforesthaha
20:11.27johnsonthtdeforest, do you know how many people the newsletter went out to?
20:11.35tdeforest90000+
20:12.19tdeforestjohnsonth, this sounds like it could be an issue. can you document the issue in an email and i'll follow up with kurt.
20:12.32TimRikertdeforest, might want to remove the forum down post now.
20:12.34johnsonthsure
20:12.43tdeforestTimRiker, will do. thanks
20:12.52johnsonthour whole newsletter sign up process is cryptic and hard for people to understand, in my opinion.
20:13.33TimRikerhttps://tech.lds.org/swarm/ is up. anyone want to create real test cases?
20:13.45tdeforestTimRiker, sweetness!
20:13.59TimRikerI added swarm and ldstech to swarm
20:14.20tdeforestjohnsonth, do we have a newsletter sign up process?
20:14.52johnsonthWe documented it in a post, and then I put the information on the wiki here: http://tech.lds.org/wiki/LDSTech_Newsletter
20:15.10johnsonthCan you link to this wiki page in the sidebar of the ldstech homepage?
20:15.20tdeforestjohnsonth, hey look, i can sign up for our newsletter. but i already get it at two of my email addresses so I don't think i'll sign up :)
20:15.43tdeforestjohnsonth, the link to the sign up form is on the homepage already
20:15.44johnsonthAlso, those links under "Community" in the sidebar need to be adjusted. Do you know where those are stored?
20:15.55tdeforestjohnsonth, in a module
20:16.01johnsonthwhere?
20:16.19tdeforestin the joomla administration panel
20:17.00johnsonth"the link to the sign up form is on the homepage already" -- I don't see this, even though I've looked three times. Am I just blind?
20:17.18tdeforestit's labeled 'email'
20:17.29tdeforestis that not it?
20:17.44TimRikerwhat homepage?
20:17.50johnsonththat's not it. that gives you an email every time a new post is added to the site.
20:17.59johnsonthit's Feedburner's email method of subscribed to a feed.
20:18.24tdeforestwe need to sort out our mailing list management before we add a link to it to the homepage
20:18.25johnsonthso you see, it's hard for people to know how to sign up for this.
20:18.31TimRikerhttp://feedburner.google.com/fb/a/mailverify?uri=ldstech gives me a 404
20:19.08johnsonthThe feedburner link works for me.
20:19.16tdeforestjohnsonth, works for me too
20:19.30TimRikersame link I just posted?
20:19.40johnsonthre mailing list management, that's fine. But I think we need to provide some information about how people can currently sign up for the newsletter right now.
20:19.45tdeforestyes
20:19.57johnsonthyes, TimRiker.
20:20.09TimRikerwierd. I get a 404. even if I try reloading
20:20.17tdeforest?
20:20.20tdeforeststrage
20:20.28tdeforests/strage/strange/
20:20.33TimRiker~spell strage
20:20.48tdeforestst rage, nice!
20:20.59tdeforestThe saint of postal workers
20:23.11johnsonthtdeforest, back to updating the "Community" section of links in the sidebar, do you know where this is done in the joomla admin interface?
20:23.47johnsonthI looked in Extensions > Module Manager but didn't see it.
20:24.17johnsonthSome of the links in that menu are really old -- e.g., Employee Spotlight.
20:25.57tdeforestjohnsonth, hmmm….i guess it is a menu and not a module
20:29.53tdeforestjohnsonth, i have kurt olsen on the phone. can you send me your wife's email address
20:34.09johnsonthtdeforest, her ldsaccount is shannonj11. i'm on the phone right now but can respond more later.
20:38.05tdeforestjohnsonth, it looks like your email address is listed as her email address
20:38.23tdeforestaccording to ldsaccount info
20:40.29johnsonthinteresting.
20:40.38johnsonthDavid Sierakowski says he didn't receive the newsletter either.
20:40.57tdeforestdo you have his email address and ldsaccount
20:44.28johnsonthone sec. phone call is over.
20:45.57tdeforestif you email matt hyer, kurt olsen and me his ldsaccount and email address, we can check for his account. be sure to have Elder Sierakowski verify that he has the appropriate box checked on his ldsaccount
20:47.58johnsonthtdeforest, I pinged him just now to ask this info. For some reason I couldn't find his name in Joomla.
20:48.14*** join/#ldstech chrxn_ (~chrxn@pool-71-189-228-162.lsanca.fios.verizon.net)
21:18.22cpittoops i'm not done I forgot I have to add the db name and what not to the parameters options
21:32.15*** join/#ldstech rpflo (~rpflo@216.51.73.6)
21:36.04scgallafentcpitt, there are some values attached to the value of forum posts and blog words in the report view page. Where do those come from? We should probably document the reasoning behind those numbers in the code.
21:40.43TimRikerreviews old jira tickets and rolls some over in to 2.6.3
21:41.25TimRikerneato. jira went down
21:42.06*** join/#ldstech chrxn_ (~chrxn@pool-71-189-228-162.lsanca.fios.verizon.net)
21:42.42tdeforestTimRiker, now it's back
21:42.57TimRikersure enough. thx
21:54.09cpittscgallafent, the numbers were there already, don't know where they came from
21:54.36scgallafentOK. I was looking at the page itself and some of that is documented in the HTML content.
21:57.54cpittscgallafent, it should all be good to go now
21:58.15scgallafentOK. I'm testing now. I ran into one issue that I added to JIRA.
21:58.52scgallafentcpitt, new item is https://tech.lds.org/jira/browse/LDSTECH-718
22:00.49scgallafenttdeforest, https://tech.lds.org/jira/browse/LDSTECH-719 is probably yours.
22:03.17cpittThat's odd that your getting that on LDSTECH-719 works fine on ff11 on ubuntu
22:04.35*** join/#ldstech rpflo (~rpflo@216.51.73.6)
22:04.59*** join/#ldstech johnsonth (JohnsonTH@conference/ldstech/x-kxdrufgqgcqxwsac)
22:11.08scgallafentcpitt, JavaScript was disabled. That accounts for the graceful degration on the accordion functionality.
22:11.20cpittahh I see
22:11.33scgallafenttdeforest, I'm not sure if you want to fix the floats based on that or leave them as-is.
22:13.28tdeforestscgallafent, does the float issue only occur with JS turned off?
22:13.39scgallafentChecking ....
22:13.49scgallafentYes.
22:13.55tdeforestok
22:14.21tdeforesti like to be bulletproof so i'll keep the ticket but i won't worry about it for this release
22:15.59scgallafenttdeforest, I checked in Chrome and get the same float errors. I'll add a comment and move it to the backlog.
22:16.13scgallafentUnless you've already moved it. :)
22:16.33tdeforesthmmm…maybe it does need to be fixed in this version.
22:17.03scgallafentI think moving it to the backlog is OK.
22:17.14scgallafentIt only occurs if JavaScript is disabled.
22:17.47tdeforestoh ok
22:17.55tdeforestgracias!
22:19.45*** join/#ldstech eldergunn (~eldergunn@02de72fa.bb.sky.com)
22:20.54tdeforestaccording to my email inbox, this is going to be our biggest release ever :)
22:22.10TimRikerscgallafent, "fixed" https://tech.lds.org/jira/browse/LDSTECH-718 by removing security like in production.
22:22.27scgallafentI saw that. You're all over "fixes" and "upgrades" today. :)
22:24.38scgallafentTimRiker, on https://tech.lds.org/jira/browse/LDSTECH-544, right now I get SOAP warnings when the WSDL doesn't load. Is there a JIRA item to provide a friendlier warning? Do we care on this page if the warning isn't friendly?
22:25.46TimRikerif jiraBase is empty, there are no warnings, right? that's enough for me.
22:27.10scgallafentIf jiraBase is empty, there are no warnings. If the WSDL fails to load for some reason, you get a series of SoapClient warnings. I'd say they're trivial at best since this is an internal page.
22:28.01TimRikerfine with me
22:35.21cpittShould I mark 717 resolved then, and pass it on to ? scgallafent?
22:35.58scgallafentcpitt, yes. Go ahead and pass it on to me and I'll finish testing.
22:36.36*** join/#ldstech J_Voracek (~J_Voracek@cpe-70-123-106-75.tx.res.rr.com)
22:42.14scgallafenttdeforest, can you look at https://tech.lds.org/jira/browse/LDSTECH-398 and close if it is OK?
22:42.17*** join/#ldstech tccastaldo (ae7e1880@gateway/web/freenode/ip.174.126.24.128)
22:42.43*** mode/#ldstech [+o tccastaldo] by ChanServ
22:43.28tdeforestscgallafent, looking...
22:44.44tdeforest…and closed
22:45.07scgallafentThank you.
22:47.30tdeforestyou're welcome :)
23:32.58*** join/#ldstech Spennig (~Spennig@pool-173-67-138-140.hrbgpa.fios.verizon.net)
23:57.51*** join/#ldstech chrxn_ (~chrxn@pool-71-189-228-162.lsanca.fios.verizon.net)

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