IRC log for #ldstech on 20111108

00:14.54*** join/#ldstech mailman0 (~mailman0@ip72-201-159-66.ph.ph.cox.net)
00:17.13*** join/#ldstech JohnGalt2600 (~john@71-36-70-244.slkc.qwest.net)
00:22.39*** join/#ldstech marilynwaswiley (~textual@66.243.229.173)
00:26.16*** join/#ldstech smootar (~smootar@207.239.115.78)
00:26.16*** mode/#ldstech [+o smootar] by ChanServ
00:27.26*** join/#ldstech marquicus (~mrojas@200.13.124.36)
00:27.51smootarscgallafent, how are things going for you?
00:36.53smootarmacnewbold, thanks for coming on Friday.  That was a great help.
00:39.57smootar~seen TimRiker
00:39.58infobottimriker <~tim@bzflag/projectlead/TimRiker> was last seen on IRC in channel #ldstech, 6h 41m 44s ago, saying: 'better log off before they complain. =-)'.
00:40.20smootar~seen scgallafent
00:40.20infobotscgallafent is currently on #ldstech. Has said a total of 1 messages. Is idling for 5h 55m 10s, last said: 'Yes. Going to send some more emails today.'.
00:40.43smootar~seen tdeforest
00:40.43infobottdeforest <~tdeforest@cpe-74-78-85-69.maine.res.rr.com> was last seen on IRC in channel #ldstech, 2h 47m 19s ago, saying: 'you can just close the window to leave the channel'.
00:43.12macnewboldsmootar: my pleasure
01:09.58*** join/#ldstech TimRiker-NC (~TimRiker@bzflag/projectlead/TimRiker)
01:09.59*** mode/#ldstech [+o TimRiker-NC] by ChanServ
01:27.14*** join/#ldstech TimRiker| (~TimRiker@bzflag/projectlead/TimRiker)
01:27.14*** mode/#ldstech [+o TimRiker|] by ChanServ
01:37.15*** join/#ldstech TimRiker-NC (~TimRiker@bzflag/projectlead/TimRiker)
01:37.16*** mode/#ldstech [+o TimRiker-NC] by ChanServ
01:47.16*** join/#ldstech TimRiker| (~TimRiker@bzflag/projectlead/TimRiker)
01:47.17*** mode/#ldstech [+o TimRiker|] by ChanServ
02:27.23*** join/#ldstech TimRiker-NC (~TimRiker@bzflag/projectlead/TimRiker)
02:27.24*** mode/#ldstech [+o TimRiker-NC] by ChanServ
02:57.30*** join/#ldstech TimRiker| (~TimRiker@bzflag/projectlead/TimRiker)
02:57.31*** mode/#ldstech [+o TimRiker|] by ChanServ
04:48.03*** join/#ldstech mailman0 (~mailman0@ip72-201-159-66.ph.ph.cox.net)
05:55.19*** join/#ldstech TimRiker-NC (~TimRiker@bzflag/projectlead/TimRiker)
05:55.19*** mode/#ldstech [+o TimRiker-NC] by ChanServ
07:00.57*** join/#ldstech TimRiker| (~TimRiker@bzflag/projectlead/TimRiker)
07:00.58*** mode/#ldstech [+o TimRiker|] by ChanServ
11:15.38*** join/#ldstech smootar (~smootar@207.239.115.78)
11:15.39*** mode/#ldstech [+o smootar] by ChanServ
13:06.48*** join/#ldstech JohnGalt26001 (~john@71-36-70-244.slkc.qwest.net)
13:10.09*** join/#ldstech coderjeff (~chatzilla@c-174-52-245-33.hsd1.ut.comcast.net)
14:08.20*** join/#ldstech dbkjar (~kjar@sharedserver.org)
15:13.24*** join/#ldstech tdeforest (~tdeforest@pool-71-173-87-119.ptldme.east.myfairpoint.net)
15:13.24*** mode/#ldstech [+o tdeforest] by ChanServ
15:16.22*** join/#ldstech macnewbold (~Adium@76.8.223.101)
15:24.31*** join/#ldstech JohnGalt2600 (~john@71-36-70-244.slkc.qwest.net)
16:02.44macnewboldponders if the meeting will be at 9am MST or 9am PST today… :)
16:02.56macnewboldor none of the above
16:11.40*** join/#ldstech TimRiker (~tim@bzflag/projectlead/TimRiker)
16:11.40*** mode/#ldstech [+o TimRiker] by ChanServ
16:12.24TimRikerV1smootar chad and I are in a presentation.
16:12.55TimRikerV1no official meeting now. anything we need to know?
16:18.44*** join/#ldstech josephscott (~josephsco@104.2.233.72.static.reverse.ltdomains.com)
16:20.26josephscottTimRikerV1: how was Oakland yesterday?
16:21.51TimRikerV1moin
16:22.08TimRikerV1hanging out in Walnut Creek
16:22.41TimRikerV1small turn out, interesting discussions
16:24.04josephscotthopefully the san jose/sf locations will have some good turn out
16:24.34josephscottnot sure how much was done to promote it directly to the tech community
16:26.07TimRikerV1yep. we'll see. having fun. =P
16:34.19*** join/#ldstech johnsonth (~JohnsonTH@proxy.lds.org)
16:36.32*** join/#ldstech marquicus (~mrojas@200.13.124.36)
16:37.12*** join/#ldstech tdeforest (~tdeforest@cpe-74-78-85-69.maine.res.rr.com)
16:37.12*** mode/#ldstech [+o tdeforest] by ChanServ
17:47.25*** join/#ldstech tdeforest (~tdeforest@cpe-74-78-85-69.maine.res.rr.com)
17:47.25*** mode/#ldstech [+o tdeforest] by ChanServ
18:23.47*** join/#ldstech aamonson (80bb6105@gateway/web/freenode/ip.128.187.97.5)
18:23.47*** mode/#ldstech [+o aamonson] by ChanServ
18:46.14*** join/#ldstech marquicus (~mrojas@200.13.124.36)
18:46.18*** join/#ldstech johnsonth (~JohnsonTH@proxy.lds.org)
18:46.18*** join/#ldstech dbkjar (~kjar@sharedserver.org)
19:09.31aamonsonI came looking for Tim, but I don't see him on here
19:10.32tdeforestaamonson: Tim is in SF for the week. he might check in here from time to time
19:11.41aamonsontdeforest: ah... I just wanted to get the names of various Jira plugins, as my new employment situation is changing to jira
19:12.21josephscottaamonson: curious, what are they moving from?
19:12.27tdeforestgotcha. he'll probably respond if you send him an email.
19:12.54aamonsonThey are moving off of version 1
19:13.12josephscottoh, so they are just updating their jira install
19:13.56josephscotthaha, sorry, didn't realize someone made product called "version 1" http://www.versionone.com/
19:13.56aamonsonWe also use turtoiseSVN, so I was hoping to get the plugin that associates commits with tickets
19:14.11josephscottthat must get confusing name wise :_)
19:14.15josephscott:-)
19:14.19aamonsonsure is
19:14.40josephscottnotes never to name a software product "Version X"
19:15.20aamonsonthere already is a www.version-x.com/
19:15.40aamonsonits not code related though
19:17.08josephscotthaha
19:18.12tdeforestversion one is a terrible name. i can just imagine the board room conversations. "does version 1.3 of version 1 have the bug or version 2 of version 1?" :)
19:18.55josephscottjust avoid using 'version' in a name, period
19:19.27tdeforestso true
19:20.06josephscottso if you wake up evil one day you'll start a software project called "Version 1 Release 2 Beta 4"
19:20.14aamonson"version pi"
19:22.15aamonsonor rather, "Version pi Release e Beta delta mu"
19:22.28tdeforesthehe
19:24.08aamonsonwe could throw some gamma radiation in there too
19:37.29*** join/#ldstech marilynwaswiley (~textual@66.243.229.173)
19:41.02marilynwaswileyTimRiker: I'm still new to this method of chat.  I see that it states "contact TimRiker for new #ldstech-* channels.  Can you tell me more?
19:42.02*** join/#ldstech marilynwaswiley (~textual@66.243.229.173)
19:52.22tdeforesttim is out of town this week. he'll be on intermittently.
20:13.45*** join/#ldstech josephscott (~josephsco@104.2.233.72.static.reverse.ltdomains.com)
20:25.12macnewboldmarilynwaswiley: i can elaborate a little on that I think - if an ldstech project has so much chat traffic that it has become a problem to have it happen in #ldstech, TimRiker can set up another room, #ldstech-projectname to use instead
21:17.06marilynwaswileythank you
21:17.38marilynwaswileyI was hoping to catch Tom Johnson, but that doesn't look like a doable today
21:18.14tdeforestjohnsonth is tom johnson
21:19.15marilynwaswileyOdd - I thought I saw his name as tomjohnson yesterday, but I do suffer from TBI
21:19.35tdeforestit may differ on his location
21:19.41johnsonthyes, johnsonth is me.
21:19.55johnsonthI'm available.
21:20.30marilynwaswileyjohnsonth: do you happen to know who designs the tech.lds.org website? or decides what links are attached to Get Help using technology in your calling?
21:21.09johnsonthTom DeForest designs the site.
21:21.26johnsonthAs far as the content on that page, I can update that as needed.
21:21.40marilynwaswileyI am Marilyn Howard, serving as Stake and Ward Website Administrator and a Family History Center Director
21:22.05johnsonthGreat to meet you.
21:22.34marilynwaswileyMy concern is that I happen to be tenacious when it comes to technology - not all members who serve in positions needing to use technologies are as bold as I
21:23.09marilynwaswileyI have found EVERY link that pertains to my callings by coming through back doors
21:24.09marilynwaswileyI am curious why there is ONLY Clerks and Stake Technology Specialists linked in the "Get Help…." link on the homepage of tech.lds.org
21:25.48marilynwaswileyIn fact, using this IRC format is new to me as of yesterday.  I downloaded the Textual app on my iMac after texting my son in Orem to find out which of the choices I found on the tech.lds.org website
21:26.12johnsonthis this the link you're referring to? http://screencast.com/t/6LQwQjkCZh
21:26.55marilynwaswileyRight!
21:27.59johnsonthI think the layout was designed before we had four separate wiki portals.
21:28.16johnsonthIf you go to https://tech.lds.org/wiki/Main_Page, you'll see four separate portal indexes to the wiki.
21:28.25johnsonthI could actually use your help with something, if you're interested.
21:28.50johnsonthI want to create an index of all Church technology products. Each product should have a link that points to information about it.
21:28.59johnsonthAre you interested in helping out with this?
21:29.03marilynwaswileyI am
21:29.14johnsonthCan you join the LDSTech Blog project? I run that one.
21:29.58johnsonthFrom the Projects tab on the top menu, sign in and navigate down to the LDSTech Blog project. Click it, and then click Join.
21:30.08marilynwaswileyI can - I do need to let you know that I am a little hampered
21:30.23johnsonthby hampered do you mean busy?
21:30.48marilynwaswileyNo - I suffer from Traumatic Brain Injury and sometimes get confused or "stuck"
21:31.23johnsonthI'm sorry to hear that. Would it prevent you from helping out?
21:31.30marilynwaswileyI Joined yesterday in a brave moment while you were doing a workshop or something that Brother Terry was attending
21:32.07marilynwaswileyI have never allowed my brain damage to keep me from serving the Lord.  You saw what callings I serve in.
21:32.26johnsonthI don't recall doing a workshop. Maybe you're thinking of someone else?
21:32.52tdeforestmarilynwaswiley might be referring to the service day on friday
21:32.56johnsonthI'm glad to hear that you're able to work and fulfill your callings despite the difficulties.
21:33.08johnsonthWe could certainly use your help with this product index.
21:33.21johnsonthRight now information for different products is scattered.
21:34.10marilynwaswileyBrother Terry of Riverton, UT told me that he was going to a workshop or meeting or something (brain damage affects happening right now!) yesterday when he called me back about repairing the disaster that had happened to the calendars we had in place in our stake and my ward
21:34.20johnsonthYour disability may even be beneficial in this work since it will help us make the content more accessible.
21:35.14johnsonthAh, the upcoming calendar webinars. Yes, they are going to be held this Thursday, and I am giving them. Here's more info: http://bit.ly/sw1qcG
21:35.23tdeforestjohnsonth: this is a great idea. it could really help improve navigation and information architecture on the site.
21:35.39johnsonthFeel free to help us get the word out about the webinars.
21:35.41tdeforesti actually started making a list of products today
21:35.41marilynwaswileyHe said that Tom Johnson was who would be at this meeting or leading the meeting or something like that.  I mentioned your name because I was hopeful to find out from him more about what we are speaking about right now
21:36.55johnsonthtdeforest, that's good to hear. I was talking with people in the awareness group in curriculum, and they expressed how difficult it can be to find info about various tech products. The info seems to be scattered.
21:37.26marilynwaswileyI am in the middle of collecting e-mail addresses for those in our Stake who will be invited to join in on the Webinars.  I found that like everything else I've discovered - bumping around, lurking, crawling in through back windows
21:37.46johnsonthHow would you prefer to get tech news?
21:38.35johnsonthI'm trying to make LDSTech a resource for all tech news from the Church, regardless of the department or product.
21:38.44marilynwaswileyDue to my brain damage, I am not employable.  I do find that Heavenly Father never fires me, He extends me beyond my abilities.  So, I am available almost everyday, all day long.
21:38.49tdeforestjohnsonth: i agree. it is a bit scattered. the forum and wiki allow content to develop quickly which is good. it would be good if we could come in behind this content and give it some organization
21:39.02marilynwaswileyI am 61 at home alone all day with my technologies
21:39.23johnsonthtdeforest: If you want to send me the product index list you started, I can add to it.
21:39.42marilynwaswileyI like this thread of thought!
21:40.15johnsonthMarilyn, why don't you email me and we can continue the conversation. https://tech.lds.org/wiki/User:Johnsonth
21:40.36johnsonthEmail might allow for more detail sharing. Though with IRC, everyone is kept in the loop.
21:40.46tdeforestsent
21:41.02johnsonthThanks Tom.
21:41.08marilynwaswileyI teach so many members how to use newFamilySearch and the updated Church Websites and I know that it is too dificult to find things for those with technology fears.  I will e-mail you.
21:41.38johnsonthmarilynwaswiley: Thanks.
21:41.48tdeforestjohnsonth: thank you for getting this ball rolling. i am excited that it will make things better for our users
21:42.21marilynwaswileyAbsolutely!  Thank you both!
21:43.35johnsonthTom, one thing we should do, perhaps, is an affinitiy diagram for LDSTech. Check out the latest post to see more details about the affinity diagramming technique.
21:43.55tdeforestthat term is new to me. i'll go check it out
21:44.08johnsonthWe are merging with mhtech, and they will want us to consider how to make their mhtech stuff more visible.
21:44.26johnsonthI need to set up a meeting about this from a discussion I had with Alan, Jacob Stark, and Derek Hays last week.
21:44.42johnsonthWe're going to start funnelling mhtech news into the stream of regular ldstech news.
21:44.42tdeforestis good. i haven't forgotten jacob stark and co. i'm sure they feel ignored though
21:44.50johnsonthEventually we'll merge brands and just call it ldstech, I think.
21:47.01johnsonthOur discussion ended with the conclusion that we needed to better understand our users before we could make site redesign decisions to accommodate mhtech more visibly.
21:47.17johnsonthI said we should engage User Research to help us gather some user data to help us make that decision.
21:47.44johnsonthI'll set up that meeting with Ted from User Research, and then he can steer us in the right direction to get the data we need. Maybe he can even collect the data for us.
21:47.57tdeforesttotally agree. wish i had been in that meeting.
21:49.51marilynwaswileyI would like to interject that I believe I have a really great view of end user prospectives.  I did this at Novell back in `96
21:50.26marilynwaswileyProgrammers were making changes that were flying over the head of the end users because of lack of feedback
21:52.05marilynwaswileyMost members who use the LDS technologies don't even notice the Feedback links on the websites and are usually fearful of making remarks for fear of revealing ignorance.  I am not afraid to reveal my ignorance - so that I can diminish that ignorance!
21:53.08johnsonthI think we need to create a new volunteer group called LDSTech Wiki.
21:53.42johnsonthThere are a lot of wiki needs that aren't really being addressed. It doesn't quite fall into the LDSTech Blog or the LDSTech projects.
21:55.10tdeforestjohnsonth: are you referring to organizing wiki content?
21:55.19johnsonthyes, not style or design.
21:55.42johnsonthThere needs to be some governance and guidance about categories and subcategories for the pages.
21:55.59johnsonthAnd some standards about sidebars.
21:56.10johnsonthThere is a lot of outdated content that needs to be vetted.
21:57.10tdeforestI see. like i was saying the organic growth is good for quick development but it needs some shepherding once created.
21:58.50tdeforestlike you were saying things were structured for our they were used previously. the usage seems to be changing. getting feedback from our audience will help us keep the site relevant to their needs
21:59.09tdeforests/for our/for how/
22:00.36tdeforestanyway, johnsonth thanks for heading this up. please keep me in the loop and let me know what i can do to help.

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