Stake-Specific IT Wiki

So you have the BIG idea that the Church or community needs to develop. Discuss that idea here. Maybe you just want to make a suggestion on a new forum topic. Let us know.
minertbd
New Member
Posts: 1
Joined: Sun Jun 05, 2011 7:09 pm

Stake-Specific IT Wiki

Postby minertbd » Sun Jun 05, 2011 7:14 pm

Every building is wired, configured, and provisioned differently. We need a repository that won't disappear when someone's stake calling ends. We would like the LDSTech wiki to provide a stake-specific section where we can document the networks, where the equipment is stored, and add "how to" sections for broadcasting Church training, transmitting stake conference between buildings, etc.
If we could do the same with Jira, we could have a central project-planning capability as well.

User avatar
aebrown
Community Administrator
Posts: 14693
Joined: Tue Nov 27, 2007 8:48 pm
Location: Sandy, Utah

Postby aebrown » Sun Jun 05, 2011 7:29 pm

minertbd wrote:Every building is wired, configured, and provisioned differently. We need a repository that won't disappear when someone's stake calling ends. We would like the LDSTech wiki to provide a stake-specific section where we can document the networks, where the equipment is stored, and add "how to" sections for broadcasting Church training, transmitting stake conference between buildings, etc.


Although I am sympathetic to your goal, I don't think the LDSTech wiki is a good choice. For one thing, some of the information that is important to pass on is a variety of passwords. Those certainly couldn't be put in a public place. I've documented all these things in a variety of files. Most are on the stake administrative computer, in an obvious place, which gets backed up. The passwords are on paper in the stake president's confidential files, which will certainly get passed on to the next stake president. That password document also notes the location of the electronic files. So even if I were to be hit by a truck tomorrow, all the information can be recovered easily so that someone else could pick up where I left off.

I guess I don't see why putting it in a public place provides any significant benefits over putting it in a well-known place within the stake's local system.

And although I'm a big fan of Jira, it seems a bit heavy for a stake's IT needs. I'm the stake technology specialist, and anyone who has a technology request sends it to me. We don't do enough IT projects that exceed the capacity of a few email exchanges.
Questions that can benefit the larger community should be asked in a public forum, not a private message.


Return to “Ideas & Suggestions”

Who is online

Users browsing this forum: No registered users and 1 guest