IRC log for #ldstech on 20130219

01:37.05*** join/#ldstech tiwula (~lane@63-248-12-52.static.sdyl0420.digis.net)
02:12.27*** join/#ldstech Kraytul (kraytul@reaver.cat.pdx.edu)
02:44.32*** join/#ldstech McAwesome (~McAwesome@97-123-0-176.albq.qwest.net)
06:47.16*** join/#ldstech mreeder_ (uid4425@gateway/web/irccloud.com/x-iqemqsyywhptynau)
08:31.31*** join/#ldstech marquicus (~mrojas@200.13.124.36)
08:50.52*** join/#ldstech rybob1 (1810e640@gateway/web/freenode/ip.24.16.230.64)
09:08.28*** join/#ldstech mailman0 (~mailman0@ip68-109-134-132.ph.ph.cox.net)
15:01.59*** join/#ldstech VickiHaws (~VickiHaws@proxy.lds.org)
15:15.30*** join/#ldstech TeddieSteiner (~steinerte@174-27-43-157.bois.qwest.net)
15:17.51*** join/#ldstech josephscott (~josephsco@208.95.156.134)
15:19.21*** join/#ldstech jonmull (~clbj@proxy.lds.org)
15:33.19*** join/#ldstech TeddieSteiner (~steinerte@174-27-43-157.bois.qwest.net)
15:46.52*** join/#ldstech JedBlack (~blackjf1@proxy.lds.org)
15:50.28*** join/#ldstech zakzakattack (~zakzakatt@proxy.lds.org)
15:55.56*** join/#ldstech smootar (~smootar@proxy.lds.org)
15:55.56*** mode/#ldstech [+o smootar] by ChanServ
15:57.47*** join/#ldstech TeddieSteiner (~steinerte@174-27-43-157.bois.qwest.net)
16:00.03*** join/#ldstech ekeating (~Dennis@99-54-46-12.lightspeed.snjsca.sbcglobal.net)
16:00.07ekeating~meetstart <LDSTech Dev Scrum>
16:00.07infobot********** Start of the <LDSTech Dev Scrum> Meeting on 2013.02.19 16:00:07 **********
16:00.18*** join/#ldstech TimRikerXoom (~TimRiker@bzflag/projectlead/TimRiker)
16:00.19*** mode/#ldstech [+o TimRikerXoom] by ChanServ
16:00.20ekeatingmorning all.  I trust you had a good weekend
16:00.30TimRikerXoommoin
16:00.43jonmullhi
16:00.48TeddieSteinerGood morning
16:00.50JedBlackhello
16:00.51ekeatinglet's go ahead and start with you TimRikerXoom
16:00.51zakzakattackhi
16:01.35*** join/#ldstech LDSTechMK802 (~LDSTech@proxy.lds.org)
16:01.36*** mode/#ldstech [+o LDSTechMK802] by ChanServ
16:02.41TimRikerXoommore profile cod8ng today.
16:02.44*** join/#ldstech KFitz (~Kevin@proxy.lds.org)
16:02.52TimRikerXoomchecking in on email etc.
16:02.56TimRikerXoomthat is all
16:03.09ekeatingthanks
16:03.22ekeatingzakzakattack, what are you working on today?
16:03.41TimRikerXoomstaff
16:03.51TimRikerXoommeeting today, right?
16:04.02ekeatingI assume so.
16:04.05zakzakattackWorking on Getting hours from missioanrys adn community and I think i have issue to work on. that is all for me
16:04.32ekeatingthanks zakzakattack jonmull any report for today?
16:04.36jonmulli have nothing to report
16:04.42ekeatingthank you
16:04.51ekeatingTeddieSteiner, ?
16:04.58smootarmoin
16:04.59TeddieSteinerThis weekend.  Contacted Bishop to see if I could work with the Ward to set up Lesson Schedules.  Making appointment with him to discuss.  Making good progress on creating test questions for Swarm.
16:05.00*** join/#ldstech TimRiker (~TimRiker@bzflag/projectlead/TimRiker)
16:05.00*** mode/#ldstech [+o TimRiker] by ChanServ
16:06.04ekeatingJedBlack, ?
16:06.09JedBlackworking learning calendar
16:06.17*** join/#ldstech scgallafentXfmr (~scgallafe@c-67-160-61-229.hsd1.wa.comcast.net)
16:06.18*** mode/#ldstech [+o scgallafentXfmr] by ChanServ
16:06.25JedBlackthats all
16:06.31ekeatingthank you
16:06.43ekeatinghere's cpitt's report from Friday
16:06.46ekeatingFriday:
16:06.47ekeatingWorked on righting Mikerowaved permission issues on the forum/
16:06.47ekeatingNext week:
16:06.47ekeatingWhatever tickets get assigned to me.
16:07.07ekeatingscgallafentXfmr, moin
16:07.14scgallafentXfmrSorry. Running late. Mn.
16:07.23TimRikerhmm. wonder what cpitt found with permissions
16:07.26scgallafentXfmrMoin
16:07.40ekeatingno idea TimRiker
16:07.52ekeatingare you ready to report scgallafentXfmr ?
16:08.53scgallafentXfmrSnapping in keyboard
16:09.06ekeatingwe'll wait
16:09.15ekeatingsmootar, do you have anything for today?
16:09.20scgallafentXfmrWorked on https://tech.lds.org/jira/browse/LDSTECH-885
16:09.41scgallafentXfmrSummarizing from Git is done. Working next on storing data and output functionality.
16:10.05scgallafentXfmrI'll be working on that today and prepping for CPAS release hopefully this week.
16:10.06scgallafentXfmrThat is all.
16:10.08smootarHad a nice long weekend.
16:10.08smootarChristian H. is becoming an LDSTech Service Missionary as he transitions from ICS to
16:10.10smootarReviewing plans today with John E.
16:10.11smootarWorking with Elder Eliason and meeting a new LDSTech Chapter Pres.
16:10.12smootarA few other meetings.
16:10.13smootarThat is all.
16:12.00smootarIs the GIT working in Dev only?  Does it need to be deployed in production?
16:12.05ekeatingthank you
16:12.16TimRikerdo we have git in dev yet?
16:12.22scgallafentXfmrStill have some pieces to finish before it's ready for production.
16:12.31scgallafentXfmrI haven't checked to see if we have a dev Git instance.
16:12.43scgallafentXfmrI'm running my stats against local repos right now.
16:12.53TimRikerseems git is there, but gitrm is not
16:13.20TimRikernor wgit
16:13.25scgallafentXfmrThis will be a little odd to implement because we need local copies of the Git repos to run the stats.
16:13.32TimRikernor gitstats
16:13.53scgallafentXfmrThe stat script will probably run on cdev as a cron job, since there are local copies of the repos there.
16:14.14scgallafentXfmrThat will need to feed data to the production server for reporting.
16:15.05TimRikeris not very comfortable with that.
16:15.43smootarFor SVN, we run the scripts in production, correct?
16:15.48TimRikerproduction has valid ldsaccount in front of git. cdev has fake accounts that should not be able to see production code for non-public projects.
16:16.12TimRikerfor svn we have access to the svn server. for git we've been told we cannot get access.
16:16.25TimRikerheh. can't get git access
16:16.25scgallafentXfmrWe should let ekeating finish the meeting before we head down this rabbit hole.
16:16.35smootarBut the scripts are running on svn production, correct?
16:16.51smootaragrees
16:17.46ekeatingokay we're over time wo we'll end this meeting and you can continue this conversation
16:18.04ekeatingmeetend <LDSTech Dev Scrum>
16:18.22ekeating~meetend <LDSTech Dev Scrum>
16:18.22infobot********** End of the <LDSTech Dev Scrum> Meeting on 2013.02.19 16:18:22 **********
16:18.39scgallafentXfmrOK. Back to our adventure....
16:19.06scgallafentXfmrHere are the issues with generating the stats:
16:19.26scgallafentXfmr* gitstats doesn't have detail we need to properly report employee vs volunteer contributions over time
16:19.45scgallafentXfmr* In order to run our own stats against Git, we have to run against a local copy of the repo
16:20.02scgallafentXfmr* We have a copy of the repos on cdev and can generate statistics from those
16:20.20scgallafentXfmr* If we want to generate statistics from somewhere else, we need to create a local copy of the repo on that server
16:20.23smootarIs the reason you have to do a local copy is that we don't have access to the production server?
16:20.33scgallafentXfmrNo. Git works differently than subversion.
16:20.43scgallafentXfmrActually, yes, I guess.
16:20.51scgallafentXfmrGit and Subversion work differently.
16:21.12scgallafentXfmrWith Subversion, we could run a local script and get data from a remote repository.
16:21.20scgallafentXfmrWith Git, we have to have a local copy of the repository.
16:21.51TimRikerhowever, for performance reasons we need to run svnstats on the local machine.
16:21.56smootarThe local copy is identical to the server copy.
16:22.03TimRikerrunning it remotely would take more than 24 hours to run through.
16:22.04smootarok
16:22.08scgallafentXfmrsmootar, correct.
16:22.33smootarHow long does it take to run on a local machine?
16:22.48scgallafentXfmrIf we could get SDS to run the stats script against their copy of the repo, that would be an option.
16:22.48TimRikerproduction "data" on development machines is a Bad Thing
16:23.20scgallafentXfmrThen we either convince SDS to add this script to their mix on the server or create another copy of the repo somewhere else for reporting.
16:23.38TimRikerI agree with any of those options
16:24.18scgallafentXfmrWe've already got a copy of the repos on cdev that we can use for reporting. I don't think the _results_ should stored on cdev, but I'm OK with running against the cdev copy to generate the data unless we want to create another set of repos.
16:24.23smootarLet's send the request to SDS to make that happen.  They can choose the option that is best for them.
16:24.52scgallafentXfmrlooks at old email
16:25.30TimRikerscgallafentXfmr, I'm not ok with it. it's fine for a short term while you're developing, but some projects in git will consider their code sensitive enough that protecting it only with well known fake accounts is not enough.
16:25.48smootarShould a copy of the production repo be in cdev?
16:26.12TimRiker<PROTECTED>
16:26.44TimRikercourse I'd rather they all open their code, but that's a different conversation. :)
16:27.33smootarok
16:27.53scgallafentXfmrFound the message I was looking for.
16:27.59smootarok
16:28.12scgallafentXfmrTimRiker, I agree that sensitive projects would be an issue on cdev.
16:28.23scgallafentXfmrWould we be reporting on sensitive projects?
16:28.44scgallafentXfmrI doubt we're going to be reporting community contributions on those projects.
16:28.53smootaragreed.
16:28.55scgallafentXfmrI looked at the message I had a while ago from Howard Olsen.
16:29.06scgallafentXfmrHe wasn't excited about it, but there is a possibility we could run it on their server.
16:29.22smootarWhat was his recommendation?
16:29.34scgallafentXfmrThey don't have enough disk space for another copy of the repos, but they could possibly run it if we didn't need another copy of the repos.
16:29.38scgallafentXfmr(We shouldn't.)
16:29.50scgallafentXfmrIt was easier for him if we took care of it ourselves, obviously.
16:30.10smootarWell, he said he would take care of our needs.
16:30.34smootarI would like to have him run it for us on the production server just like svn does today.
16:30.56scgallafentXfmrWith where the script ended up, I think they could run it on their machine. They would probably want to script it and run it on their schedule and then we would retrieve the data when we want itt.
16:31.03scgallafentXfmrs/itt/it/
16:31.39smootarHow long does it take to run?
16:32.06scgallafentXfmrI would rather not have them install it until it's done from end to end and I know we won't need to make any changes on the stats side.
16:32.26scgallafentXfmrIt takes a few minutes (don't remember exactly how much) to run for CPAS and Swarm.
16:33.13smootarOK
16:33.36scgallafentXfmrIf you start running against larger repos, it's going to take longer. I can pull one of the large ones and see how long it takes to run on my machine.
16:33.50smootarSo, to run it against all non sensitive projects, do you need rights?  Or what account will be used?
16:34.27scgallafentXfmrYou have to have a local copy of the repo. We have a service account that we use to clone the repo on cdev.
16:34.49scgallafentXfmrWe would use that same account to clone the repo and run against the cloned copy.
16:35.32smootarSo is the next step to run it against the whole repo?
16:35.37scgallafentXfmrThe question is whether we end up running against the SDS copy of each repo, against a copy on cdev, or another copy that we create somewhere else.
16:36.13smootarIt seems like cdev is the wrong place.
16:36.15scgallafentXfmrYou don't run against "the whole repo." We clone the code for projects that we are reporting on and run against the local copy of each of those.
16:36.47smootarDo we run against the all of the SVN repo today?
16:36.48scgallafentXfmrcdev isn't the best place, but it's where we have a copy of the data stored that we need to report on.
16:37.10smootars/the all/all/
16:37.21scgallafentXfmrSomeone would have to look and see if statsvn gets run against every project.
16:37.41smootarI thought it did, but maybe I'm wrong.  TimRiker ?
16:37.49scgallafentXfmrMy guess is that it does.
16:38.32smootarI would like to do the same against git.
16:38.50scgallafentXfmrThe big difference here is that you're not going to the server and asking for the log data to generate your statistics. Instead, you Git is generating the statistics by going through the local copy of the code.
16:39.28scgallafentXfmrIf we run it against every project, we need to have SDS run it or clone a local copy of the code for every project and run it against that local copy.
16:39.41scgallafentXfmrIn that case, we would probably need to dedicate a server to that process.
16:40.00scgallafentXfmrLooking at the email, SDS may be willing to run it based on where things have ended up.
16:40.09smootarI would like SDS to solve that issue, but maybe we could make sure it runs in cdev first.
16:40.21scgallafentXfmrThe biggest issue will be where to store data between when the script runs and when we collect it
16:40.24smootarHow hard is it to run against the repo in cdev?
16:40.39smootarWhere is the svn data stored  today?
16:40.48smootarIs that a good pattern to follow?
16:40.52scgallafentXfmrThe stat collection script can run against the cdev repo now.
16:41.20scgallafentXfmrThe svn data is stored at SDS. They're already running statsvn against the Subversion code.
16:41.31scgallafentXfmrWe call a statsvn summary script to get the data we need.
16:41.56smootarWould that same pattern work for git?
16:42.00scgallafentXfmrThey also run gitstats against Git projects, but gitstats doesn't give us what we need to report contributions.
16:42.42scgallafentXfmrPossibly, but it will require more involvement from them.
16:44.54smootarI would like them to do it, and if it gets too painful we can go another route.  But they have offered and I want to take them up on it.
16:45.51scgallafentXfmrI've managed to get the stat generation to the point where I don't think they won't have a problem running it. We'll need to figure out what and how to store it if we ask them to store data long term.
16:55.04smootarscgallafentXfmr: sounds good.
16:55.23smootarDo you want me to chat with Howard O., or do you want to contact him scgallafentXfmr ?
16:56.01*** join/#ldstech VickiHaws_ (~VickiHaws@proxy.lds.org)
16:56.03scgallafentXfmrI'm going to have to rethink where we went split that stat generation process and then I'll get back with him about it.
16:56.18scgallafentXfmrHe and I talked about it quite a bit a while ago.
16:56.32smootarscgallafentXfmr: sounds good.  Heading to staff meeting. See you in a minute.
16:56.50smootarTimRiker: Staff meeting reminder. :)
16:57.22*** join/#ldstech smootar_ (~smootar@proxy.lds.org)
16:57.24*** mode/#ldstech [+o smootar_] by ChanServ
16:59.15*** join/#ldstech scgallafent (~scgallafe@c-67-160-61-229.hsd1.wa.comcast.net)
16:59.15*** mode/#ldstech [+o scgallafent] by ChanServ
17:06.43*** join/#ldstech tiwula (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net)
17:42.44*** join/#ldstech JedBlack (~blackjf1@proxy.lds.org)
17:43.51*** join/#ldstech zakzakattack (~zakzakatt@proxy.lds.org)
19:03.56*** join/#ldstech smootar (~smootar@proxy.lds.org)
19:03.56*** mode/#ldstech [+o smootar] by ChanServ
19:05.14*** join/#ldstech VickiHaws_ (~VickiHaws@proxy.lds.org)
19:53.15*** join/#ldstech marquicus (~mrojas@200.13.124.36)
20:01.54*** join/#ldstech smootar (~smootar@proxy.lds.org)
20:01.54*** mode/#ldstech [+o smootar] by ChanServ
20:20.46*** join/#ldstech tiwula (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net)
21:36.19*** join/#ldstech TimRiker (~TimRiker@bzflag/projectlead/TimRiker)
21:36.20*** mode/#ldstech [+o TimRiker] by ChanServ
21:51.37*** join/#ldstech smootar_ (~smootar@proxy.lds.org)
21:51.37*** mode/#ldstech [+o smootar_] by ChanServ
22:21.36*** join/#ldstech smootar (~smootar@proxy.lds.org)
22:21.36*** mode/#ldstech [+o smootar] by ChanServ
23:05.33TimRikersmootar, what are the proposed dates for LDSTech/SORT 2013?
23:05.46smootarTimRiker: looking
23:10.33smootarI'm confirming, but I think the week is Oct 15-18, but I'm waiting for a reply.
23:12.21smootarYes, Oct 15-18 we have reservations, but I don't think we will be doing all 4 days.  It will be less than that.  Decisions still need to be made.  But that is the week.
23:19.38smootarTimRiker: is that what you need?
23:23.27TimRikerjust getting around to updating the entry on the scheduler
23:25.11smootarFor the scheduler, put Oct 16-17 for now while it is under discussion.
23:25.48smootarplease :)
23:44.45TimRikerdone

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