Page 1 of 2

Best and worst of tech.lds.org

Posted: Thu Dec 30, 2010 2:57 pm
by tdeforest
Two quick questions:
  • What's the best part of tech.lds.org?
  • What's the worst part of tech.lds.org?
Feel free to answer both or only one. Thanks!

Posted: Thu Dec 30, 2010 3:01 pm
by techgy
tdeforest wrote:Two quick questions:

  • What's the best part of tech.lds.org?
  • What's the worst part of tech.lds.org?
Feel free to answer both or only one. Thanks!

What's the purpose of your inquiry?

Posted: Thu Dec 30, 2010 3:04 pm
by tdeforest
I'm hoping to understand how to improve tech.lds.org, if it needs it :)

Posted: Thu Dec 30, 2010 6:54 pm
by jdlessley
tdeforest wrote:I'm hoping to understand how to improve tech.lds.org, if it needs it :)
Could you be more specific. Are you a Church employee looking for some specific information that is not already available in these forums? Because there most certainly are a lot of threads devoted to both what people like about the classic lds.org as well as what they would like see changed.

However, with the release of the new lds.org people are already making recommendations throught site feedback. We also are aware that lds.org is in a state of development and that more content and structure is coming.

So if you are looking for something particular I would recommend some specific questions in specific areas. Forum users generally are not shy in responding when they are focussed on a particular aspect.

my short, but probably not useful answers

Posted: Fri Dec 31, 2010 7:12 am
by njpomeroy
Best part of tech.lds.org: That it exists at all. There is *somewhere* to find out about technology issues, solutions, and policies related to the church.

Worst part: that I disagree with about 90% of the solutions and policy decisions. :)
Seriously, I have a hard time finding good bug tracking and support info for church-produced apps, and this seems like I should be able to find it on tech.lds.org.

Posted: Fri Dec 31, 2010 11:42 am
by russellhltn
njpomeroy wrote:Seriously, I have a hard time finding good bug tracking and support info for church-produced apps, and this seems like I should be able to find it on tech.lds.org.
Are you talking about community apps or non-community apps? Because for community developed, church sponsored apps, there's Jira.

Posted: Fri Dec 31, 2010 12:20 pm
by idjeeper2
Best: That it exists and the collective knowledge of the people on here.

Worst: Not enough usage by leaders who could really enhance their own abilities and share what they know with the rest of us. And lately, the "too busy" time every Sunday (that seems to have resolved itself, maybe).

Posted: Fri Dec 31, 2010 1:00 pm
by Mikerowaved
I think the WIKI has to be right up there with the best the site has to offer. With a lot of hard work and dedication it has developed into an extremely useful resource.

I have to agree with idjeeper2:
idjeeper2 wrote:Worst: Not enough usage by leaders who could really enhance their own abilities and share what they know with the rest of us.
I can't tell you how many leaders I've mentioned tech.lds.org to and they just give me that puzzled look where I KNOW they have no clue what I'm talking about. I think if this site, and all it has to offer, was presented in a 10 minute priesthood session conference talk, it's value to the church would soar.

Posted: Thu Jan 06, 2011 7:51 pm
by gregwanderson
The worst part is that if you make a candid comment about something you dislike it might be inferred that you are criticizing the church as an institution or it's policies or doctrines. We're culturally taught to never criticize anything "done by the church." But I think it should be okay to offer feedback on something as doctrinally insignificant as tech issues. Still, I'm never quite sure who I'm offending.

Posted: Sat Jan 08, 2011 8:33 pm
by wrpdmd
Mikerowaved wrote:I think the WIKI has to be right up there with the best the site has to offer. With a lot of hard work and dedication it has developed into an extremely useful resource.

I have to agree with idjeeper2:

I can't tell you how many leaders I've mentioned tech.lds.org to and they just give me that puzzled look where I KNOW they have no clue what I'm talking about. I think if this site, and all it has to offer, was presented in a 10 minute priesthood session conference talk, it's value to the church would soar.

I'll second that; I came across it by accident.

If they don't want to spend time on it in priesthood session, maybe something in the Leadership session of Stake Conference?

A letter to the Stake Presidents would do, or maybe a video sent to the units?