TechWiki - User contributions [en]

User:Cognifloyd

2011-05-20T22:25:12Z

Techgurufloyd: /* Jacob Floyd */

==Jacob Floyd==


I love LDSTech!

{| border="1" cellspacing="0" cellpadding="2"
! colspan="2" | Communicate with me
|-
| Cell || 801-613-8776 (Call or Text)
|-
| Email || [mailto:techgurufloyd@gmail.com techgurufloyd@gmail.com]
|-
| Facebook || [http://facebook.com/techgurufloyd techgurufloyd]
|-
| Twitter || [http://twitter.com/techgurufloyd techgurufloyd]
|-
| LinkedIn || [http://linkedin.com/in/techgurufloyd techgurufloyd]
|-
| Google Profile || [http://google.com/profiles/techgurufloyd techgurufloyd]
|-
| Google Talk || techgurufloyd
|-
| Skype || techgurufloyd
|-
| AIM || techgurufloyd
|-
| Yahoo || techgurufloyd
|-
| MSN || techgurufloyd@live.com
|-
| ICQ || 603419816
|-
! colspan="2" | <small><small>If you see "techgurufloyd" anywhere on the internet, it's me.</small></small>
|}

==Design documentation==
The purpose of LDSTech includes helping people to "Learn about how the Church is using technology" and "Contribute to Church technology projects". Learning about what is already developed will help community members to contribute more effectively and reuse existing projects. In these pages, I am trying to help people understand the design of various church products/websites and how they can reuse or include the design in the community projects. Please enjoy this documentation, tear it apart (to make it better), and help me to fill in the blanks. Discussion is welcome!

* [[User:Techgurufloyd/Design of lds.org]]

===ToDo===
Here's some of the documentation I would like to create or see made available to the community.

# Document how to use/integrate with various apps (and other parts of lds.org) in other community projects. Note that there is already some great docs for [[Community Services List of Services|many of these services]]. The docs may need to be expanded (possibly here instead of there) to take into account the visual design of some parts of lds.org.
#* [[User:Techgurufloyd/LDSUniversalPlayer|LDSUniversalPlayer]]
#* [http://lds.org/study-tools/folders notebook]
#* [http://lds.org/church-calendar/?lang=eng calendar]
#* [https://lds.org/directory?lang=eng directory]
#* [http://lds.org/maps?lang=eng maps]
# Add a section in [[User:Techgurufloyd/Design of lds.org]] or a new page that describes the unique visual styles in the following sections of lds.org:
#* [http://lds.org/plan/our-eternal-life?lang=eng ohfp]
#* [http://lds.org/family/happiness?lang=eng family]
#* [https://lds.org/handbook/handbook-2-administering-the-church?lang=eng Handbook 2]
#* [http://lds.org/church/organization?lang=eng organization]
#* [https://lds.org/church/news?lang=eng news]
#* [http://lds.org/study-tools/folders notebook]
#* [http://lds.org/church-calendar/?lang=eng calendar]
#* [https://lds.org/directory?lang=eng directory]
#* [http://lds.org/maps?lang=eng maps]
# Other sites that could potentially use some documentation down the road (or sites that I want to see [better] ways to integrate with them):
#* [https://tech.lds.org LDSTech]
#* [http://beta-newsroom.lds.org/ Newsroom]
#* [http://store.lds.org Online Store]
#* [https://familysearch.org/ FamilySearch]
#* [http://simpleacts.lds.org/ The Vineyard]
#* Seminary & Institutes sites
#** [https://beta.lds.org/si/?lang=eng beta.lds.org/si]
#** [http://institute.lds.org/ institute.lds.org]
#* [http://radio.lds.org/eng/ Mormon Radio]
#* Employment sites
#** [https://www.ldsjobs.org/ LDS Employment Resource Services]
#** [http://lds.jobs lds.jobs] has the standard lds.org design (church section)
#** [https://careers.ldschurch.org careers.ldschurch.org] An app to search for employment at the church
#* [http://mormon.org mormon.org]: [[User:Techgurufloyd/Design of mormon.org]]
#** There isn't documentation on mormon.org for now as it is seems that projects won't be using the visual layout of mormon.org for the forseeable future.
#** However, [http://lds.org/plan/our-eternal-life?lang=eng ohfp] has an element called "sashy" that seems to get content from mormon.org. Documentation on how to use quotes from mormon.org would be beneficial if it really is a service and not just static copies.
#* Various [[Church Websites]]
#** A list of lots of websites, some of which have old designs. When a site gets a facelift, I might document it if it seems it might be beneficial at some point for the community.
# new document on [http://en.wikipedia.org/wiki/XQuery XQuery] and [http://www.marklogic.com/ MarkLogic]
#* lds.org uses Marklogic to store all of the content. If a community project ever needs a more intimate integration with lds.org, [http://en.wikipedia.org/wiki/XQuery XQuery] might be just the ticket to success.

Sharing the gospel online

2011-05-02T23:15:17Z

Techgurufloyd: /* Quotes that could apply to Social Media */ Fix reference to Gospel Doctrine

With a little effort anyone can help share the Gospel online. Here you will find quick tips, howtos, and suggestions on ways you can use social media and how you can use it to better share the Gospel, or any message in the most effective manner to your friends and family. Please contribute and add your own!

== Facebook ==
* [[Understanding Facebook]]
* [[How to set up a Facebook page]]
* [[Moderating Facebook comments]]
* [[Formulating a successful posting strategy]]
* [[Understanding and using Facebook insights]]
* [[Building a Facebook ad strategy]]
* [[Using Facebook places and deals]]
* [[Understanding Facebook Credits]]
* [[Facebook Social Plugins and OpenGraph Protocol]]
* [[Basics of Facebook Graph API]]

== Twitter ==
Cool success story: [http://cleveraccounts.posterous.com/twitter-finds-a-missing-child-in-3-hours-via Twitter finds a missing child in 3 hours (via @BradMcCarty)]

== Mixi ==

== Youtube ==

== Flickr ==

== Google Local ==

== Yelp ==

== Foursquare ==

== Gowalla ==

== Foreign language blogging ==

== Social bookmarking ==
Want to share the Book of Mormon online? Use your social bookmarking account (Digg, Delicious, StumbleUpon) to bookmark the [http://mormon.org/book-of-mormon Book of Mormon page] on Mormon.org.

==Plain ol' blogging==

* [[Free blogging tool options]]
* [[How to set up a blog]]
* [[Basic blog features]]
* [[Basic posting tips]]
* [[Tips and tricks for helping people find your blog]]

==Quotes that could apply to Social Media==
Of course, social media is not for everyone. But if you are in the group of people that can use it (eg your Bishop hasn't told you not to, or your employment doesn't prohibit your using it) these quotes might be helpful.
<blockquote>
President Joseph F. Smith counseled, “Let every man’s life be so that his character will bear the closest inspection, and that it may be seen as an open book, so that he will have nothing to shrink from or be ashamed of” (''Gospel Doctrine'' 5th ed. [1939], 252).
<br>
[https://lds.org/manual/gospel-principles/chapter-31-honesty Gospel Principles - Chapter 31: Honesty]
</blockquote>
Brethren, the Lord has inspired men to invent these great tools. Now if we don’t use them to teach his gospel, Satan will use them to lead the people astray (Elder LeGrand Richards)

<blockquote>

</blockquote>

[[Category:Social networking]]

User:Cognifloyd

2011-04-22T19:30:10Z

Techgurufloyd: Add note and smile!

==Jacob Floyd==

I'm doing an internship at the Church right now. As part of that, I'm the Community Manager for social media related projects.

I love LDSTech!

{| border="1" cellspacing="0" cellpadding="2"
! colspan="2" | Communicate with me
|-
| Cell || 801-613-8776 (Call or Text)
|-
| Email || [mailto:techgurufloyd@gmail.com techgurufloyd@gmail.com]
|-
| Email || [mailto:jfloyd@ldschurch.org jfloyd@ldschurch.org]
|-
| Facebook || [http://facebook.com/techgurufloyd techgurufloyd]
|-
| Twitter || [http://twitter.com/techgurufloyd techgurufloyd]
|-
| LinkedIn || [http://linkedin.com/in/techgurufloyd techgurufloyd]
|-
| Google Profile || [http://google.com/profiles/techgurufloyd techgurufloyd]
|-
| Google Talk || techgurufloyd
|-
| Skype || techgurufloyd
|-
| AIM || techgurufloyd
|-
| Yahoo || techgurufloyd
|-
| MSN || techgurufloyd@live.com
|-
| ICQ || 603419816
|-
! colspan="2" | <small><small>If you see "techgurufloyd" anywhere on the internet, it's me.</small></small>
|}

==Design documentation==
The purpose of LDSTech includes helping people to "Learn about how the Church is using technology" and "Contribute to Church technology projects". Learning about what is already developed will help community members to contribute more effectively and reuse existing projects. In these pages, I am trying to help people understand the design of various church products/websites and how they can reuse or include the design in the community projects. Please enjoy this documentation, tear it apart (to make it better), and help me to fill in the blanks. Discussion is welcome!

* [[User:Techgurufloyd/Design of lds.org]]

===ToDo===
Here's some of the documentation I would like to create or see made available to the community.

# Document how to use/integrate with various apps (and other parts of lds.org) in other community projects. Note that there is already some great docs for [[Community Services List of Services|many of these services]]. The docs may need to be expanded (possibly here instead of there) to take into account the visual design of some parts of lds.org.
#* [[User:Techgurufloyd/LDSUniversalPlayer|LDSUniversalPlayer]]
#* [http://lds.org/study-tools/folders notebook]
#* [http://lds.org/church-calendar/?lang=eng calendar]
#* [https://lds.org/directory?lang=eng directory]
#* [http://lds.org/maps?lang=eng maps]
# Add a section in [[User:Techgurufloyd/Design of lds.org]] or a new page that describes the unique visual styles in the following sections of lds.org:
#* [http://lds.org/plan/our-eternal-life?lang=eng ohfp]
#* [http://lds.org/family/happiness?lang=eng family]
#* [https://lds.org/handbook/handbook-2-administering-the-church?lang=eng Handbook 2]
#* [http://lds.org/church/organization?lang=eng organization]
#* [https://lds.org/church/news?lang=eng news]
#* [http://lds.org/study-tools/folders notebook]
#* [http://lds.org/church-calendar/?lang=eng calendar]
#* [https://lds.org/directory?lang=eng directory]
#* [http://lds.org/maps?lang=eng maps]
# Other sites that could potentially use some documentation down the road (or sites that I want to see [better] ways to integrate with them):
#* [https://tech.lds.org LDSTech]
#* [http://beta-newsroom.lds.org/ Newsroom]
#* [http://store.lds.org Online Store]
#* [https://familysearch.org/ FamilySearch]
#* [http://simpleacts.lds.org/ The Vineyard]
#* Seminary & Institutes sites
#** [https://beta.lds.org/si/?lang=eng beta.lds.org/si]
#** [http://institute.lds.org/ institute.lds.org]
#* [http://radio.lds.org/eng/ Mormon Radio]
#* Employment sites
#** [https://www.ldsjobs.org/ LDS Employment Resource Services]
#** [http://lds.jobs lds.jobs] has the standard lds.org design (church section)
#** [https://careers.ldschurch.org careers.ldschurch.org] An app to search for employment at the church
#* [http://mormon.org mormon.org]: [[User:Techgurufloyd/Design of mormon.org]]
#** There isn't documentation on mormon.org for now as it is seems that projects won't be using the visual layout of mormon.org for the forseeable future.
#** However, [http://lds.org/plan/our-eternal-life?lang=eng ohfp] has an element called "sashy" that seems to get content from mormon.org. Documentation on how to use quotes from mormon.org would be beneficial if it really is a service and not just static copies.
#* Various [[Church Websites]]
#** A list of lots of websites, some of which have old designs. When a site gets a facelift, I might document it if it seems it might be beneficial at some point for the community.
# new document on [http://en.wikipedia.org/wiki/XQuery XQuery] and [http://www.marklogic.com/ MarkLogic]
#* lds.org uses Marklogic to store all of the content. If a community project ever needs a more intimate integration with lds.org, [http://en.wikipedia.org/wiki/XQuery XQuery] might be just the ticket to success.

User:Cognifloyd

2011-04-22T19:12:33Z

Techgurufloyd: Test edit to check out how wiki edits are colored by CIA-17

==Jacob Floyd==

I'm doing an internship at the Church right now. As part of that, I'm the Community Manager for social media related projects.

{| border="1" cellspacing="0" cellpadding="2"
! colspan="2" | Communicate with me
|-
| Cell || 801-613-8776 (Call or Text)
|-
| Email || [mailto:techgurufloyd@gmail.com techgurufloyd@gmail.com]
|-
| Email || [mailto:jfloyd@ldschurch.org jfloyd@ldschurch.org]
|-
| Facebook || [http://facebook.com/techgurufloyd techgurufloyd]
|-
| Twitter || [http://twitter.com/techgurufloyd techgurufloyd]
|-
| LinkedIn || [http://linkedin.com/in/techgurufloyd techgurufloyd]
|-
| Google Profile || [http://google.com/profiles/techgurufloyd techgurufloyd]
|-
| Google Talk || techgurufloyd
|-
| Skype || techgurufloyd
|-
| AIM || techgurufloyd
|-
| Yahoo || techgurufloyd
|-
| MSN || techgurufloyd@live.com
|-
| ICQ || 603419816
|-
! colspan="2" | <small><small>If you see "techgurufloyd" anywhere on the internet, it's me.</small></small>
|}

==Design documentation==
The purpose of LDSTech includes helping people to "Learn about how the Church is using technology" and "Contribute to Church technology projects". Learning about what is already developed will help community members to contribute more effectively and reuse existing projects. In these pages, I am trying to help people understand the design of various church products/websites and how they can reuse or include the design in the community projects. Please enjoy this documentation, tear it apart (to make it better), and help me to fill in the blanks. Discussion is welcome!

* [[User:Techgurufloyd/Design of lds.org]]

===ToDo===
Here's some of the documentation I would like to create or see made available to the community.

# Document how to use/integrate with various apps (and other parts of lds.org) in other community projects. Note that there is already some great docs for [[Community Services List of Services|many of these services]]. The docs may need to be expanded (possibly here instead of there) to take into account the visual design of some parts of lds.org.
#* [[User:Techgurufloyd/LDSUniversalPlayer|LDSUniversalPlayer]]
#* [http://lds.org/study-tools/folders notebook]
#* [http://lds.org/church-calendar/?lang=eng calendar]
#* [https://lds.org/directory?lang=eng directory]
#* [http://lds.org/maps?lang=eng maps]
# Add a section in [[User:Techgurufloyd/Design of lds.org]] or a new page that describes the unique visual styles in the following sections of lds.org:
#* [http://lds.org/plan/our-eternal-life?lang=eng ohfp]
#* [http://lds.org/family/happiness?lang=eng family]
#* [https://lds.org/handbook/handbook-2-administering-the-church?lang=eng Handbook 2]
#* [http://lds.org/church/organization?lang=eng organization]
#* [https://lds.org/church/news?lang=eng news]
#* [http://lds.org/study-tools/folders notebook]
#* [http://lds.org/church-calendar/?lang=eng calendar]
#* [https://lds.org/directory?lang=eng directory]
#* [http://lds.org/maps?lang=eng maps]
# Other sites that could potentially use some documentation down the road (or sites that I want to see [better] ways to integrate with them):
#* [https://tech.lds.org LDSTech]
#* [http://beta-newsroom.lds.org/ Newsroom]
#* [http://store.lds.org Online Store]
#* [https://familysearch.org/ FamilySearch]
#* [http://simpleacts.lds.org/ The Vineyard]
#* Seminary & Institutes sites
#** [https://beta.lds.org/si/?lang=eng beta.lds.org/si]
#** [http://institute.lds.org/ institute.lds.org]
#* [http://radio.lds.org/eng/ Mormon Radio]
#* Employment sites
#** [https://www.ldsjobs.org/ LDS Employment Resource Services]
#** [http://lds.jobs lds.jobs] has the standard lds.org design (church section)
#** [https://careers.ldschurch.org careers.ldschurch.org] An app to search for employment at the church
#* [http://mormon.org mormon.org]: [[User:Techgurufloyd/Design of mormon.org]]
#** There isn't documentation on mormon.org for now as it is seems that projects won't be using the visual layout of mormon.org for the forseeable future.
#** However, [http://lds.org/plan/our-eternal-life?lang=eng ohfp] has an element called "sashy" that seems to get content from mormon.org. Documentation on how to use quotes from mormon.org would be beneficial if it really is a service and not just static copies.
#* Various [[Church Websites]]
#** A list of lots of websites, some of which have old designs. When a site gets a facelift, I might document it if it seems it might be beneficial at some point for the community.
# new document on [http://en.wikipedia.org/wiki/XQuery XQuery] and [http://www.marklogic.com/ MarkLogic]
#* lds.org uses Marklogic to store all of the content. If a community project ever needs a more intimate integration with lds.org, [http://en.wikipedia.org/wiki/XQuery XQuery] might be just the ticket to success.

Sharing the gospel online

2011-04-17T18:02:06Z

Techgurufloyd: add some quotes applicable to social media

With a little effort anyone can help share the Gospel online. Here you will find quick tips, howtos, and suggestions on ways you can use social media and how you can use it to better share the Gospel, or any message in the most effective manner to your friends and family. Please contribute and add your own!

== Facebook ==
* [[Understanding Facebook]]
* [[How to set up a Facebook page]]
* [[Moderating Facebook comments]]
* [[Formulating a successful posting strategy]]
* [[Understanding and using Facebook insights]]
* [[Building a Facebook ad strategy]]
* [[Using Facebook places and deals]]
* [[Understanding Facebook Credits]]
* [[Facebook Social Plugins and OpenGraph Protocol]]
* [[Basics of Facebook Graph API]]

== Twitter ==
Cool success story: [http://cleveraccounts.posterous.com/twitter-finds-a-missing-child-in-3-hours-via Twitter finds a missing child in 3 hours (via @BradMcCarty)]

== Mixi ==

== Youtube ==

== Flickr ==

== Google Local ==

== Yelp ==

== Foursquare ==

== Gowalla ==

== Foreign language blogging ==

== Social bookmarking ==
Want to share the Book of Mormon online? Use your social bookmarking account (Digg, Delicious, StumbleUpon) to bookmark the [http://mormon.org/book-of-mormon Book of Mormon page] on Mormon.org.

==Plain ol' blogging==

* [[Free blogging tool options]]
* [[How to set up a blog]]
* [[Basic blog features]]
* [[Basic posting tips]]
* [[Tips and tricks for helping people find your blog]]

==Quotes that could apply to Social Media==
Of course, social media is not for everyone. But if you are in the group of people that can use it (eg your Bishop hasn't told you not to, or your employment doesn't prohibit your using it) these quotes might be helpful.
<blockquote>
President Joseph F. Smith counseled, “Let every man’s life be so that his character will bear the closest inspection, and that it may be seen as an open book, so that he will have nothing to shrink from or be ashamed of” ( 5th ed. [1939], 252).
<br>
[https://lds.org/manual/gospel-principles/chapter-31-honesty Gospel Principles - Chapter 31: Honesty]
</blockquote>
Brethren, the Lord has inspired men to invent these great tools. Now if we don’t use them to teach his gospel, Satan will use them to lead the people astray (Elder LeGrand Richards)

<blockquote>

</blockquote>

[[Category:Social networking]]

Talk:Sharing the gospel online

2011-04-10T07:15:47Z

Techgurufloyd: /* Instructure */ I forgot my signature

== Instructure ==

Call it brainstorming in the open. A lot of what this is (sharing the gospel online), is teaching people how to do something. What if we used something like [http://www.instructure.com/ Instructure] to build lessons people could take - they could learn whatever/however they'd like. Whether they prefer the how-to's with a smattering of principles or a simple list of principles to apply, there should be a way to handle that.
--[[User:Techgurufloyd|Techgurufloyd]] 07:15, 10 April 2011 (UTC)

Talk:Sharing the gospel online

2011-04-10T07:13:28Z

Techgurufloyd: Instructure

== Instructure ==

Call it brainstorming in the open. A lot of what this is (sharing the gospel online), is teaching people how to do something. What if we used something like [insructure.com Instructure] to build lessons people could take - they could learn whatever/however they'd like. Whether they prefer the how-to's with a smattering of principles or a simple list of principles to apply, there should be a way to handle that.

Sharing the gospel online

2011-04-07T21:03:51Z

Techgurufloyd: /* Twitter */ quick link to a cool twitter success story

Tech Projects

2011-04-01T20:59:06Z

Techgurufloyd: Fix link to "Serving the Needy Online" Page

<div style="margin: 10px 0px 0px 0px;">
<div style="text-align: center;">
==Welcome to the LDSTech Projects Wiki==
</div>
<div style="font-size: 1.15em;">The purpose of this wiki is for the Church and community members to collaborate on various documents and technology projects sponsored by the Church. We invite all to participate. '''New users''', please review the [[Requirements for Participation]] and [[Guidelines|Wiki Guidelines]] pages.</div>
<br />
<br />
<table width="100%" cellspacing="10" cellpadding="0">
<tr valign="top">
<td width="50%">
<div style="margin: 0px 5px 0px 0px; border: 1px solid #656550;">
<div style="text-align: center;">
=== Project Wiki Menu ===
</div> 
<table width="100%" cellspacing="10" cellpadding="0" border="0">

<tr valign="top">
<td width="50%"><div style="background-color: #D1D3BA; padding-left: 10px; font-size: 1.25em;">
=====Announcements=====
</div>
* [[file:New.gif]][http://new.lds.org/pages/mobile-apps/mobile-blackberry.xqy Beta version of Gospel Library for BlackBerry now available]
* [[file:New.gif]][[Mormon_Channel_BlackBerry_Application#Version_1.0 | Mormon Channel for BlackBerry version 1.0 is released]]
* [[Subversion Change to Dev | Subversion has changed locations]]
* [[LDS_Java_Stack | LDS Java Stack Documentation]]
* [[General_Announcements#Where_is_Subversion | Subversion URL]]
* [[General_Announcements#Syntax_Highlighting | Syntax Code Highlighting in Wiki]]
</td>

<td><div style="background-color: #D1D3BA; padding-left: 10px; font-size: 1.25em;">
=====Participation & Current Needs=====
</div>
* [[LDSTech:About | New to the LDSTech Wiki?]]
* [[Requirements for Participation | Requirements for Participation]]
* [http://www.mediawiki.org/wiki/Help:Formatting Help with Formatting Documents]
* [[Current Needs]]
* [[Getting Involved with Projects | How to get involved]]
* [[Community Development Best Practices | Dev Best Practices]]
</td>
</tr>
<tr valign="top">
<td><div style="background-color: #D1D3BA; padding-left: 10px; font-size: 1.25em;">
===== Current Projects =====
</div>
* [[Community Projects | A listing of all of our community projects]]
* [[LDS_Tools_application | LDS Tools - Mobile Membership]]
* [[Local Unit Website Project | Local Unit Website Project]]
* [[Mormon Channel | Mormon Channel Mobile Applications]]
* [[Mobile Gospel Library Project | Mobile Gospel Library Applications]]
* [[Social Prototyping]]
</td>
<td><div style="background-color: #D1D3BA; padding-left: 10px; font-size: 1.25em;">
===== Feedback & Suggestions =====
</div>
* [[MLS:_Feedback_and_Suggestions | MLS (Member and Leader Services)]]
* [[LUWS:_Feedback_and_Suggestions | LUWS (Local Unit Web Sites)]]
* [[Online_Scriptures:_Feedback_and_Suggestions | Online Scriptures]]
</td>
</tr>

<tr>
<td><div style="background-color: #D1D3BA; padding-left: 10px; font-size: 1.25em;">
===== Internet & Family Safety =====
</div>
* [[Internet (Family Safety) | Internet Safety]]
* [[Cell Phones (Family_Safety) | Cell Phone Safety]]
* [[Sharing the Gospel Online]]
* [[Serving the Needy Online]]
* [[Family Safety | more...]]
</td>

<td><div style="background-color: #D1D3BA; padding-left: 10px; font-size: 1.25em;">
===== Services Deployed to Community =====
</div>

* [[Community_Services_Service_Access | Accessing Services]]
* [[Community_Services_List_of_Services | List of Services]]
* [[Community_Services_version_2_Overview | more...]]
</td>
</tr>

</table>
</div> 
</td>

</tr>
</table>
__NOTOC__
__NOEDITSECTION__

[[Category:Projects| ]]

User:Cognifloyd

2011-03-21T22:42:49Z

Techgurufloyd: Add church email

==Jacob Floyd==

I'm doing an internship at the Church right now. As part of that, I'm the Community Manager for social media related projects.

{| border="1" cellspacing="0" cellpadding="2"
! colspan="2" | Communicate with me
|-
| Cell || 801-613-8776 (Call or Text)
|-
| Email || [mailto:techgurufloyd@gmail.com techgurufloyd@gmail.com]
|-
| Email || [mailto:jfloyd@ldschurch.org jfloyd@ldschurch.org]
|-
| Facebook || [http://facebook.com/techgurufloyd techgurufloyd]
|-
| Twitter || [http://twitter.com/techgurufloyd techgurufloyd]
|-
| LinkedIn || [http://linkedin.com/in/techgurufloyd techgurufloyd]
|-
| Google Profile || [http://google.com/profiles/techgurufloyd techgurufloyd]
|-
| Google Talk || techgurufloyd
|-
| Skype || techgurufloyd
|-
| AIM || techgurufloyd
|-
| Yahoo || techgurufloyd
|-
| MSN || techgurufloyd@live.com
|-
! colspan="2" | <small><small>If you see "techgurufloyd" anywhere on the internet, it's me.</small></small>
|}

==Design documentation==
The purpose of LDSTech includes helping people to "Learn about how the Church is using technology" and "Contribute to Church technology projects". Learning about what is already developed will help community members to contribute more effectively and reuse existing projects. In these pages, I am trying to help people understand the design of various church products/websites and how they can reuse or include the design in the community projects. Please enjoy this documentation, tear it apart (to make it better), and help me to fill in the blanks. Discussion is welcome!

* [[User:Techgurufloyd/Design of lds.org]]

===ToDo===
Here's some of the documentation I would like to create or see made available to the community.

# Document how to use/integrate with various apps (and other parts of lds.org) in other community projects. Note that there is already some great docs for [[Community Services List of Services|many of these services]]. The docs may need to be expanded (possibly here instead of there) to take into account the visual design of some parts of lds.org.
#* [[User:Techgurufloyd/LDSUniversalPlayer|LDSUniversalPlayer]]
#* [http://lds.org/study-tools/folders notebook]
#* [http://lds.org/church-calendar/?lang=eng calendar]
#* [https://lds.org/directory?lang=eng directory]
#* [http://lds.org/maps?lang=eng maps]
# Add a section in [[User:Techgurufloyd/Design of lds.org]] or a new page that describes the unique visual styles in the following sections of lds.org:
#* [http://lds.org/plan/our-eternal-life?lang=eng ohfp]
#* [http://lds.org/family/happiness?lang=eng family]
#* [https://lds.org/handbook/handbook-2-administering-the-church?lang=eng Handbook 2]
#* [http://lds.org/church/organization?lang=eng organization]
#* [https://lds.org/church/news?lang=eng news]
#* [http://lds.org/study-tools/folders notebook]
#* [http://lds.org/church-calendar/?lang=eng calendar]
#* [https://lds.org/directory?lang=eng directory]
#* [http://lds.org/maps?lang=eng maps]
# Other sites that could potentially use some documentation down the road (or sites that I want to see [better] ways to integrate with them):
#* [http://tech.lds.org LDSTech]
#* [http://beta-newsroom.lds.org/ Newsroom]
#* [http://store.lds.org Online Store]
#* [https://familysearch.org/ FamilySearch]
#* [http://simpleacts.lds.org/ The Vineyard]
#* Seminary & Institutes sites
#** [https://beta.lds.org/si/?lang=eng beta.lds.org/si]
#** [http://institute.lds.org/ institute.lds.org]
#* [http://radio.lds.org/eng/ Mormon Radio]
#* Employment sites
#** [https://www.ldsjobs.org/ LDS Employment Resource Services]
#** [http://lds.jobs lds.jobs] has the standard lds.org design (church section)
#** [https://careers.ldschurch.org careers.ldschurch.org] An app to search for employment at the church
#* [http://mormon.org mormon.org]: [[User:Techgurufloyd/Design of mormon.org]]
#** There isn't documentation on mormon.org for now as it is seems that projects won't be using the visual layout of mormon.org for the forseeable future.
#** However, [http://lds.org/plan/our-eternal-life?lang=eng ohfp] has an element called "sashy" that seems to get content from mormon.org. Documentation on how to use quotes from mormon.org would be beneficial if it really is a service and not just static copies.
#* Various [[Church Websites]]
#** A list of lots of websites, some of which have old designs. When a site gets a facelift, I might document it if it seems it might be beneficial at some point for the community.
# new document on [http://en.wikipedia.org/wiki/XQuery XQuery] and [http://www.marklogic.com/ MarkLogic]
#* lds.org uses Marklogic to store all of the content. If a community project ever needs a more intimate integration with lds.org, [http://en.wikipedia.org/wiki/XQuery XQuery] might be just the ticket to success.

Talk:IMPLook

2010-12-27T06:35:49Z

Techgurufloyd: LDS.org Design Document

== LDS.org Design Document ==

Just a thought. If you need help incorporating the lds.org design, I've tried to [[User:Techgurufloyd/Design of lds.org|document it]] and make it easier to integrate with projects like this. Is there something I can do to make that doc more useful?

User:Cognifloyd

2010-12-27T06:07:05Z

Techgurufloyd: /* ToDo */ Add todo about marklogic

==Jacob Floyd==
My Website: [http://ldstech.cognifire.com/ ldstech.cognifire.com]

{| border="1" cellspacing="0" cellpadding="2"
! colspan="2" | Communicate with me
|-
| Cell || 801-613-8776 (Call or Text)
|-
| Email || [mailto:techgurufloyd@gmail.com techgurufloyd@gmail.com]
|-
| Facebook || [http://facebook.com/techgurufloyd techgurufloyd]
|-
| Twitter || [http://twitter.com/techgurufloyd techgurufloyd]
|-
| LinkedIn || [http://linkedin.com/in/techgurufloyd techgurufloyd]
|-
| Google Profile || [http://google.com/profiles/techgurufloyd techgurufloyd]
|-
| Google Talk || techgurufloyd
|-
| Skype || techgurufloyd
|-
| AIM || techgurufloyd
|-
| Yahoo || techgurufloyd
|-
| MSN || techgurufloyd@live.com
|-
! colspan="2" | <small><small>If you see "techgurufloyd" anywhere on the internet, it's me.</small></small>
|}

==Design documentation==
The purpose of LDSTech includes helping people to "Learn about how the Church is using technology" and "Contribute to Church technology projects". Learning about what is already developed will help community members to contribute more effectively and reuse existing projects. In these pages, I am trying to help people understand the design of various church products/websites and how they can reuse or include the design in the community projects. Please enjoy this documentation, tear it apart (to make it better), and help me to fill in the blanks. Discussion is welcome!

* [[User:Techgurufloyd/Design of lds.org]]

===ToDo===
Here's some of the documentation I would like to create or see made available to the community.

# Document how to use/integrate with various apps (and other parts of lds.org) in other community projects. Note that there is already some great docs for [[Community Services List of Services|many of these services]]. The docs may need to be expanded (possibly here instead of there) to take into account the visual design of some parts of lds.org.
#* [[User:Techgurufloyd/LDSUniversalPlayer|LDSUniversalPlayer]]
#* [http://lds.org/study-tools/folders notebook]
#* [http://lds.org/church-calendar/?lang=eng calendar]
#* [https://lds.org/directory?lang=eng directory]
#* [http://lds.org/maps?lang=eng maps]
# Add a section in [[User:Techgurufloyd/Design of lds.org]] or a new page that describes the unique visual styles in the following sections of lds.org:
#* [http://lds.org/plan/our-eternal-life?lang=eng ohfp]
#* [http://lds.org/family/happiness?lang=eng family]
#* [https://lds.org/handbook/handbook-2-administering-the-church?lang=eng Handbook 2]
#* [http://lds.org/church/organization?lang=eng organization]
#* [https://lds.org/church/news?lang=eng news]
#* [http://lds.org/study-tools/folders notebook]
#* [http://lds.org/church-calendar/?lang=eng calendar]
#* [https://lds.org/directory?lang=eng directory]
#* [http://lds.org/maps?lang=eng maps]
# Other sites that could potentially use some documentation down the road (or sites that I want to see [better] ways to integrate with them):
#* [http://tech.lds.org LDSTech]
#* [http://beta-newsroom.lds.org/ Newsroom]
#* [http://store.lds.org Online Store]
#* [https://familysearch.org/ FamilySearch]
#* [http://simpleacts.lds.org/ The Vineyard]
#* Seminary & Institutes sites
#** [https://beta.lds.org/si/?lang=eng beta.lds.org/si]
#** [http://institute.lds.org/ institute.lds.org]
#* [http://radio.lds.org/eng/ Mormon Radio]
#* Employment sites
#** [https://www.ldsjobs.org/ LDS Employment Resource Services]
#** [http://lds.jobs lds.jobs] has the standard lds.org design (church section)
#** [https://careers.ldschurch.org careers.ldschurch.org] An app to search for employment at the church
#* [http://mormon.org mormon.org]: [[User:Techgurufloyd/Design of mormon.org]]
#** There isn't documentation on mormon.org for now as it is seems that projects won't be using the visual layout of mormon.org for the forseeable future.
#** However, [http://lds.org/plan/our-eternal-life?lang=eng ohfp] has an element called "sashy" that seems to get content from mormon.org. Documentation on how to use quotes from mormon.org would be beneficial if it really is a service and not just static copies.
#* Various [[Church Websites]]
#** A list of lots of websites, some of which have old designs. When a site gets a facelift, I might document it if it seems it might be beneficial at some point for the community.
# new document on [http://en.wikipedia.org/wiki/XQuery XQuery] and [http://www.marklogic.com/ MarkLogic]
#* lds.org uses Marklogic to store all of the content. If a community project ever needs a more intimate integration with lds.org, [http://en.wikipedia.org/wiki/XQuery XQuery] might be just the ticket to success.

User:Cognifloyd

2010-12-27T05:57:40Z

Techgurufloyd: Fix regression by reinserting deleted section - I was editing the whole page instead of just the section

User:Cognifloyd

2010-12-27T05:55:26Z

Techgurufloyd: Add ToDo Section

==Design documentation==
The purpose of LDSTech includes helping people to "Learn about how the Church is using technology" and "Contribute to Church technology projects". Learning about what is already developed will help community members to contribute more effectively and reuse existing projects. In these pages, I am trying to help people understand the design of various church products/websites and how they can reuse or include the design in the community projects. Please enjoy this documentation, tear it apart (to make it better), and help me to fill in the blanks. Discussion is welcome!

* [[User:Techgurufloyd/Design of lds.org]]

===ToDo===
Here's some of the documentation I would like to create or see made available to the community.

# Document how to use/integrate with various apps (and other parts of lds.org) in other community projects. Note that there is already some great docs for [[Community Services List of Services|many of these services]]. The docs may need to be expanded (possibly here instead of there) to take into account the visual design of some parts of lds.org.
#* [[User:Techgurufloyd/LDSUniversalPlayer|LDSUniversalPlayer]]
#* [http://lds.org/study-tools/folders notebook]
#* [http://lds.org/church-calendar/?lang=eng calendar]
#* [https://lds.org/directory?lang=eng directory]
#* [http://lds.org/maps?lang=eng maps]
# Add a section in [[User:Techgurufloyd/Design of lds.org]] or a new page that describes the unique visual styles in the following sections of lds.org:
#* [http://lds.org/plan/our-eternal-life?lang=eng ohfp]
#* [http://lds.org/family/happiness?lang=eng family]
#* [https://lds.org/handbook/handbook-2-administering-the-church?lang=eng Handbook 2]
#* [http://lds.org/church/organization?lang=eng organization]
#* [https://lds.org/church/news?lang=eng news]
#* [http://lds.org/study-tools/folders notebook]
#* [http://lds.org/church-calendar/?lang=eng calendar]
#* [https://lds.org/directory?lang=eng directory]
#* [http://lds.org/maps?lang=eng maps]
# Other sites that could potentially use some documentation down the road (or sites that I want to see [better] ways to integrate with them):
#* [http://tech.lds.org LDSTech]
#* [http://beta-newsroom.lds.org/ Newsroom]
#* [http://store.lds.org Online Store]
#* [https://familysearch.org/ FamilySearch]
#* [http://simpleacts.lds.org/ The Vineyard]
#* Seminary & Institutes sites
#** [https://beta.lds.org/si/?lang=eng beta.lds.org/si]
#** [http://institute.lds.org/ institute.lds.org]
#* [http://radio.lds.org/eng/ Mormon Radio]
#* Employment sites
#** [https://www.ldsjobs.org/ LDS Employment Resource Services]
#** [http://lds.jobs lds.jobs] has the standard lds.org design (church section)
#** [https://careers.ldschurch.org careers.ldschurch.org] An app to search for employment at the church
#* [http://mormon.org mormon.org]: [[User:Techgurufloyd/Design of mormon.org]]
#** There isn't documentation on mormon.org for now as it is seems that projects won't be using the visual layout of mormon.org for the forseeable future.
#** However, [http://lds.org/plan/our-eternal-life?lang=eng ohfp] has an element called "sashy" that seems to get content from mormon.org. Documentation on how to use quotes from mormon.org would be beneficial if it really is a service and not just static copies.
#* Various [[Church Websites]]
#** A list of lots of websites, some of which have old designs. When a site gets a facelift, I might document it if it seems it might be beneficial at some point for the community.

TechWiki:New wiki content requests

2010-09-13T20:17:56Z

Techgurufloyd: /* New wiki features */ Interwiki linking with FamilySearch wiki

Anyone can add to this page any '''requests for new content''' on the LDSTech wiki. This wiki is always a work in progress. Sometimes contributors will notice that something is missing, or think of a new topic that would be very helpful. This page provides a place to quickly capture those ideas, especially when the person with the idea can't make the changes personally for any reason.

People who have time and expertise to contribute content are welcome to come here and help fulfill some of these requests. Once a topic has been added to the wiki, it should be removed from this page.

Feel free to discuss the merits of any of these suggestions on the [[LDSTech_talk:New Content Requests|discussion page]].

== New clerk content ==
Add bullet points below regarding new topics that should be added to the wiki.

* [[Language]] issues in MLS: [[Changing the Language Setting in MLS]] explains how to run MLS in a different language, but we should also explain how to print forms and certificates in a different language (without changing the MLS language). This could go in that same article (but broaden the title), or in a separate article. There may also be some language-specific issues related to MLS Exports (see {{LDSTech|post=35775}}).
* [[Local Unit Website]]: Break this article into a user-oriented page and an administrator page. The administration page could then spawn additional detailed articles. For example, resource scheduling could be its own topic, as well as [http://tech.lds.org/forum/showthread.php?t=3105 How to get members to use LUWS].
* [[Stake President]] and [[Bishop]] currently redirect to [[Leaders' responsibilities for record keeping]]. But there have been discussions on LDSTech forums such as [http://tech.lds.org/forum/showthread.php?t=1244 New Stake Presidency] about what clerks need to do, especially in the technology realm, to help get new stake presidencies and bishops acquainted with Church systems and get the proper access. This would apply to new clerks as well. It would be helpful to capture this "getting started" information.
* [[Executive secretary]] article contains only a brief outline of responsibilities. There is a surprising dearth of training information for executive secretaries. It would be nice to flesh out some information that would be much more helpful to new executive secretaries. One particular item would be explaining the MLS Action and Interview List.
* [[Members without callings]]: This MLS report has several options, and how to use it is not clear to all clerks. See {{LDSTech|thread=3690|title=Members Without Callings List}}.
* [[Agent ward expenses]]: Document how financial clerks might account for expenses when wards share a building.

== New projects ==
* [[iPhone App]] for Ward Directory and Calendar.
* [[Subversion]] article could gather the information on SVN scattered throughout the [[:Category:Projects]] pages. Then it would be a simple link in each project page that tells how to check out source code so we wouldn't have to repeat that info. It could combine or reference the following:
*# Little note in [[Mobile_Scriptures_Windows_Mobile#How to check out and build the project]]
*# [[Checking_Out_a_LDS_Java_Stack_Project_with_Eclipse#Install_the_Subclipse_plugin]]
*# [[Subversion_Change_to_Dev]]
* [[Jira]] article would be similar to the [[Subversion]] article in that it would explain what Jira is (with link to the Atlassian site), how to get authorization, distinction between internal Jira and external. Then project pages wouldn't have to duplicate that information -- they could just link to the [[Jira]] article and provide the specific URL.
* Downloadable Church Magazines for iPad that can be read offline, even for a subscription fee.

== New wiki features ==
Add bullet points below regarding changes to the structure of the wiki, or guidelines or procedures, such as templates or categories.

* Add template for references to the CHI
* Add [http://www.mediawiki.org/wiki/Extension:InterWiki InterWiki] [[Wikipedia:Wikipedia:InterWikimedia_links|linking]] between https://wiki.familysearch.org/en/ using something like: <code><nowiki>[[FamilySearch:]]</nowiki></code> or <code><nowiki>[[FS:]]</nowiki></code>.

== Other ==
Add bullet points below for any other suggestions that do not fit the above topics.

[[Category:LDSTech Administration|New Content Requests]]

TechWiki talk:Copyrights

2010-09-13T20:00:05Z

Techgurufloyd: /* Are there any requirements about licensing contributions to the LDSTech Wiki? */ Respond

== Are there any requirements about licensing contributions to the LDSTech Wiki? ==

I don't know what the license is for info that's already on the wiki. I don't know if there's a default license for stuff here. Comments? What should go in that section?
-- [[User:Techgurufloyd|Techgurufloyd]] 05:07, 13 September 2010 (UTC)

: The question you are asking above is indeed the heart of the matter. I asked Tom Welch many months ago to clarify this, and I believe he has submitted the question to the Church's legal department, but I have heard no resolution. Although I appreciate you getting this started, the content you added seems to me to be mostly irrelevant to the topic that should be covered. The purpose of the page is to explain the copyright issues for this wiki, not to explain copyright principles. So I really think the bulk of the content of this page is a distraction and should be removed. The page should focus only on the copyright issues for this wiki; for a model, see what was done on the [https://wiki.familysearch.org/en/FamilySearch_Wiki:Copyrights FamilySearch wiki copyright page]. I'd love to have a page similar to that one, but the legal department has to sign off on it. -- [[User:Aebrown|Aebrown]] 16:10, 13 September 2010 (UTC)

:: I should clarify that I am talking only about the Copyrights page in the LDSTech namespace. That page has a very specific purpose: to help users know the copyright status of contributions they make to this wiki, and of wiki information they may want to use elsewhere. However, the content on this page that has been created about basic copyright principles may well belong in the [[Family Safety]] section of this wiki to give people guidance on avoiding legal problems when posting content to various sites, or using such content for other purposes. -- [[User:Aebrown|Aebrown]] 16:14, 13 September 2010 (UTC)

::: OK, so would this go somewhere like: [[File & music sharing (Family Safety)]]? Or perhaps somewhere else? If this doesn't go well for the [[LDSTech:Copyrights]] page, that's fine. Perhaps just a simple notice instead that says that it is pending legal department direction or something. Perhaps draft it up like we'd like (maybe copy the one from [https://wiki.familysearch.org/en/FamilySearch_Wiki:Copyrights FamilySearch Wiki:Copyrights]) and put the draft template on it until it's reviewed by the legal department? Right now, it's just in limbo, I think a draft would be better than nothing. What do you think?

TechWiki talk:Copyrights

2010-09-13T05:07:58Z

Techgurufloyd: Are there any requirements about licensing contributions to the LDSTech Wiki?

TechWiki:Copyrights

2010-09-13T05:06:40Z

Techgurufloyd: First Version: Comments welcome. See the talk page to discuss the "reuse of content from the LDSTech wiki".

Whenever you edit a page on the LDSTech wiki, you see the following notice:
Please note that all contributions to LDSTech may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see [[LDSTech:Copyrights]] for details). Do not submit copyrighted work without permission!

==Copyright law==
[[wikipedia:copyright|Copyright laws]] are an important part of society. The Church strives to obey all laws. Church members should do the same.

{{scripturebox|
"We believe in being subject to kings, presidents, rulers, and magistrates, in obeying, honoring, and sustaining the law." [http://new.lds.org/scriptures/pgp/a-of-f/1.12#11 Articles of Faith 12]}}

In all you do on LDSTech, be honest and respect Copyright laws. Remember, the Lord saw fit to protect the Book of Mormon using a Copyright (The heading to [http://new.lds.org/scriptures/dc-testament/dc/14 Doctrine and Covenants 14] mentions getting that copyright).

==Definitions==
; Copyright : "Copyright is a set of exclusive rights granted to the author or creator of an original work, including the right to copy, distribute and adapt the work."<ref>[[wikipedia:copyright]]</ref>

; Copyleft : "Copyleft is a play on the word copyright to describe the practice of using copyright law to offer the right to distribute copies and modified versions of a work and requiring that the same rights be preserved in modified versions of the work. In other words, copyleft is a general method for making a program (or other work) free, and requiring all modified and extended versions of the program to be free as well."<ref>[[wikipedia:copyleft]]</ref>

; Public Domain : "Works are in the public domain if they are not covered by intellectual property rights at all, if the intellectual property rights have expired, and/or if the intellectual property rights are forfeited. ... Works of the United States Government and various other governments are excluded from copyright law and may therefore be considered to be in the public domain in their respective countries."<ref>[[wikipedia:Public domain]]</ref>

==Use of existing works==
How do you know when it is OK to copy, or reuse, something from somewhere else?

The [http://new.lds.org/manual/gospel-principles Gospel Principles] manual explains: "Copying music, movies, pictures, or written text ''without the permission of the copyright owners'' is dishonest and is a form of theft."<ref>[http://new.lds.org/manual/gospel-principles/chapter-31-honesty Gospel Principles: Honesty] Emphasis added</ref> Many [[wikipedia:copyright|copyright]] owners are very generous in licensing, or giving permission to use, their works. Using material from [[wikipedia:copyleft|Copyleft-licensed]] works is appropriate, provided you follow the terms of that license (such as attributing where you got it from). If something that might fit well in the LDSTech wiki is in the [[wikipedia:Public domain|Public Domain]], feel free to reuse it's contents on the LDSTech wiki. It's still a good idea to say where you got the material, even if it is in the Public Domain. Please, cite your sources.

In the [http://tech.lds.org/index.php?option=com_content&view=article&id=204:terms-of-use&catid=11:community-guidelines&Itemid=14 LDSTech Terms of Use], you have agreed to indemnify the church if you post something that breaks copyright law.

==Reuse of content from the LDSTech wiki==
{{stub}}


==References==
<references/>

==Additional Resources==
* [[wikipedia:Wikipedia:Copyrights|Wikipedia's policy about copyrights]] is very informative. It can help you to understand some of the ramifications of copyright laws.

* [https://wiki.familysearch.org/en/FamilySearch_Wiki:Copyrights FamilySearch Wiki:Copyrights] details the FamilySearch wiki's policies on Copyrights.

User talk:Aebrown

2010-08-06T15:46:21Z

Techgurufloyd: /* User:Techgurufloyd/Design of lds.org */ new section

Could you update the [[MLS export language dependencies]] excel spreadsheet and do you happen to also have the equivalent to the "&" english character used in the different foreign languages for the HT household name (it combines the husband and wife in english using the & character). I am working on the Ward Tools application for a Blackberry Edition and need this to help make it multi-lingual. -- [[User:Awilbourn|Awilbourn]] 22:12, 9 May 2010 (UTC)

: I'll try to update the spreadsheet in the next week or so. But regarding your specific question, I can tell you that the household name (whether for Home Teaching or anywhere else) seems to use the ampersand (&) to connect husband and wife in every language, even languages such as Chinese and Japanese. I really doubt that it is correct in all those languages to use an ampersand, but that particular character doesn't seem to be localized in the current versions of MLS. -- [[User:Aebrown|Aebrown]] 04:01, 10 May 2010 (UTC)

: I have uploaded a new version of [[File:MLS-Export-Languages.xls]] that now corresponds to MLS 3.1.5. -- [[User:Aebrown|Aebrown]] 22:08, 10 May 2010 (UTC)

== User:Techgurufloyd/Design of lds.org ==

I liked the edits you did on [[User:Techgurufloyd/Design of lds.org]]. Feel free to do more on the page itself. Also, I would love your input on a question I put up in [[User talk:Techgurufloyd/Design of lds.org]]. Thanks. --[[User:Techgurufloyd|Techgurufloyd]] 15:46, 6 August 2010 (UTC)

User:Cognifloyd

2010-08-05T16:16:57Z

Techgurufloyd: /* Design documentation */ Fix list

User:Cognifloyd

2010-08-05T16:16:27Z

Techgurufloyd: /* User pages */ Add pages, rename section to Design documentation

User:Cognifloyd

2010-08-05T02:50:32Z

Techgurufloyd: add User pages section

Priesthood Line of Authority

2010-08-03T16:31:23Z

Techgurufloyd: /* Definition of Line of Authority */ add link to beta site

A '''Priesthood Line of Authority''' shows who ordained an individual and who in turn ordained them and so on back to the Lord.

Thousands of ordinances are performed weekly throughout the Church. These ordinances are to be performed by priesthood holders who have been properly ordained and properly authorized by one who has the keys to authorize the ordinance under the direction of the prophet. Therefore, a priesthood authority line traces a priesthood holder's authority from the person ordaining him back to the Lord ([http://scriptures.lds.org/en/dc/42/11#11 D&C 42:11]).

== Definition of Line of Authority ==
The line of authority is traced through the office held at the time of the ordination:<ref>See ''Ensign'', August 1976, [http://lds.org/ldsorg/v/index.jsp?vgnextoid=2354fccf2b7db010VgnVCM1000004d82620aRCRD&locale=0&sourceId=2e93fd758096b010VgnVCM1000004d82620a____&hideNav=1 Priesthood Line of Authority]. Also on the beta site: [https://beta.lds.org/ensign/1976/08/church-policies-and-announcements?lang=eng Priesthood Line of Authority]</ref>

<blockquote>If a priesthood bearer desires to trace his own line of authority, he should pursue his current office in the priesthood — not former offices. Bishops and patriarchs should trace their line of authority as high priests. In completing an authority line, each step should go back through the office held by the person at the time he performed the ordination. It is not appropriate to trace the line of authority in cases of setting apart or for other ordinances.</blockquote>

== How to request a copy of a Priesthood Line of Authority ==
=== Methods of contacting ===
Contact Church headquarters in one of the following ways:

* '''Email''': [mailto:lineofauthority@ldschurch.org lineofauthority@ldschurch.org] with PLA in the subject line. In return you'll receive a form to fill out and return (this is an automated reply to any message that contains "PLA" in the subject line).

* '''Phone''': 800-453-3860 ext 23500 then choose option 6, then option 3. After the message and tone leave a voice mail message with your fax number or mailing address. The form will be mailed to you.

=== Helpful information ===
Be prepared with as much of the following information as possible (your [[Ward Clerk|ward clerk]] MAY be able to help you with some of this information):

# Full name of the priesthood holder
# Date of birth
# Current ward and stake
# Address and Zip Code
# Elder ordination date
# Who performed the Elder ordination
# Ward and stake where Elder ordination was performed
# High Priest ordination date if applicable
# Who performed the High Priest ordination
# Ward and stake where High Priest ordination was performed
# Any Melchizedek Priesthood ordination performed by the priesthood holder

== See also ==
[[Recording ordinances]]

== References ==
<references />

[[Category:Membership]]

Talk:Community Projects

2010-08-03T03:23:47Z

Techgurufloyd: Tagging Projects

== Tagging Projects ==

Alot of these projects are inactive. Someone somewhere has decided not to support them, so nothing is going on. It would be helpful to somehow tag projects as active or inactive - so that people can see where help would be accepted instead of ignored.
-- [[User:Techgurufloyd|Techgurufloyd]] 03:23, 3 August 2010 (UTC)

TechWiki:Guidelines

2010-05-09T04:36:31Z

Techgurufloyd: /* Use templates to flag questionable or incomplete content */ Add templates: Delete, Merge, Split

These '''guidelines''' will create consistency for additions and corrections to the LDSTech wiki.

== Creating new articles ==
An '''article''' in this wiki should be similar to an encyclopedia article. It should cover a single topic, and should stand on its own (although it may and generally should link to other articles). Topics may be very broad, or quite specific.

=== Article title ===
The '''title''' of the article should be chosen carefully. It should describe the content well, and be a term that others would naturally apply to this content. A user of the wiki can type a title in the '''search box''' of the wiki and click '''Go''' (or press '''Enter''') and go directly to an article if an article with that title exists. Words in titles should not be capitalized, except for the first word and any proper nouns.

=== Before creating a page ===
Before you create a new page, make sure that
* The content is not already covered on another page
* The content is appropriate to the LDSTech wiki
* You have chosen an appropriate title

== Editing pages ==
The content of the wiki makes progress because many users make contributions, from making simple spelling corrections to adding new articles. Be bold so that you move the project forward, but don't be hasty -- sloppy edits will just create more work for others and lower the quality of the wiki.

=== Use Preview ===
Before you click '''Save page''' to save your changes, use the '''Show preview''' button to see how your changes will actually appear. This can help save you from posting content with obvious errors.

=== Make changes at one time ===
Use the preview button liberally as you are creating a page or making edits. Whenever possible, make all your changes to a page in a single session. If you save the page often, you will needlessly clutter the history of the page and fill up the '''recent changes''' log with many entries. This makes it more difficult for other users to discover what has actually changed.

=== Headings ===
The [http://meta.wikimedia.org/wiki/Help:Section#Creation_and_numbering_of_sections MediaWiki style guide] suggests avoiding H1 level headings (i.e., <code>= This is an incorrect article heading =</code>) in your articles, as those type of headings are used for the article titles. We prefer all article sub-headings to begin with H2 level headings (i.e., <code>== This is a correct article heading ==</code>) and then go downwards from there. Words in headings should not be capitalized, except for the first word and any proper nouns.

=== Links ===
Links (both wikilinks and external links) should be attached to text that is a natural part of the article. Avoid the common blog practice of putting links around the word "here."
* '''Incorrect''': Read the MediaWiki Handbook [http://meta.wikimedia.org/wiki/Help:Contents here].
* '''Correct''': Read the [http://meta.wikimedia.org/wiki/Help:Contents MediaWiki Handbook].

=== Minor edits ===
As you save your changes after editing a page, there is a check box labeled "This is a minor edit." As explained in the [http://en.wikipedia.org/wiki/How_to_edit#Minor_edits Wikipedia article on minor edits], these are to be used only for "typo corrections, formatting and presentational changes, rearranging of text without modifying content, etc. A minor edit is a version that the editor believes requires no review and could never be the subject of a dispute." Any addition of new content can never be a minor edit, even if it is not a lot of text.

=== Style guide ===
For consistent formatting and usage of common words and concepts, please reference the [[LDSTech:Manual of Style|style guide]].

=== Changing the title ===
If you need to change the title of an article, do not simply create a new article and copy the content from the old page to the new page. Instead, use the MediaWiki '''[http://en.wikipedia.org/wiki/Wikipedia:How_to_rename_(move)_a_page Move]''' feature (one of the top tabs). '''Move''' lets you specify a new title for the page, then moves the content and the associated talk page to the new page, and finally edits the old page to be a redirect to the new page. This is far easier than doing it manually. It also keeps the discussion page with the new title, which is generally desirable, and leaves a clearer history of the actual title change.

== Discussion pages ==
Each article has a '''discussion page''' or '''talk page'''. These pages provide a forum for the community to come to a consensus as to the direction a particular article should take. If there is anything at all controversial about a change you have made or think ought to be made, start a discussion using the discussion pages.

You should '''never''' put discussion, questions, or comments in the body of articles. Discussion should be limited to the discussion page.

=== Topics ===
Discussion pages can be organized into topics. This is particularly helpful for articles that have multiple sections and thus may have ongoing discussion related to different sections.

If you are responding to a particular question, use one or more colons to indent your response so that it is clear what comment or question you are responding to.

=== Sign your name ===
You can easily sign your name by adding four tildes to the end of your comment. This will add your username and a time stamp. You can use three tildes for just your name or five tildes for just the timestamp, but the preferred signature uses four tildes to include both. The appearance of your username is determined by the preferences you have set. Comments in discussion pages should always be signed, but signatures should not be placed in articles.

== Syntax Highlighting ==
We have Syntax Highlighting on the wiki so that if you paste source code snippets, they will show up with highlights. The [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi MediaWiki SyntaxHighlight extension documentation] explains how to use syntax highlighting for your source code (including Java, HTML, SQL, XML, and many more). Here's a simple example:

{| border=1
! WikiText !! Result
|-
|<pre><source lang="java">
public static void main(final String[] args)
{
// Here is a comment
System.out.println("Hello, World!");
int m = 3 * 4;
}
</source>
</pre>
|<source lang="java">
public static void main(final String[] args)
{
// Here is a comment
System.out.println("Hello, World!");
int m = 3 * 4;
}
</source>
|-
|}

== Use templates to flag questionable or incomplete content ==
If you come across an article that needs to be edited or should be deleted, you can flag the article by inserting a template. To do this, simply edit the article and insert the text '''<nowiki>{{Template_Name|Parameter}}</nowiki>'''. The parameters for a template are documented on the template page, which you can examine by going to the appropriate template page: '''<nowiki>Template:Template_Name</nowiki>'''.

=== Template:Edit ===
Use the {{tl|Edit}} template if you find a page that requires editing, but you don't have the time or skill to edit it. This template may be inserted at the top of the page if it applies to the entire page, or at the beginning of a section if it only applies to that section. It has a parameter that is a brief description of what needs to be corrected. For example, the annotation
<pre>{{Edit|Eliminate first person from this section}}</pre>
would result in a box appearing in the text as follows:
{{Edit|Eliminate first person from this section|category=}}

=== Template:Delete ===
Use the {{tl|Delete}} template to flag a page for deletion. For example, the annotation
<pre>{{Delete|This page is spam}}</pre>
would result in a box appearing in the text as follows:
{{Delete|This page is spam|category=}}

=== Template:Draft ===
Use the {{tl|Draft}} template for policy or guideline pages that are in a draft stage. This template should be inserted at the top of the page. It has a parameter that is a brief description of the reason for the draft status. For example, the annotation
<pre>{{Draft|Waiting for approval from Tom Welch}}</pre>
would result in a box appearing in the text as follows:
{{Draft|Waiting for approval from Tom Welch|category=}}

=== Template:Need Input ===
Use the {{tl|Need Input}} template when a particular issue in an article or discussion requires additional information, clarification, or collaboration. Indicate what is needed with a brief description of the issue or ask a question. For example, the annotation
<pre>{{Need Input|Should Bishops be able to assign responsibility for a household to a quorum?}}</pre>
would result in a box appearing in the text as follows:
{{Need Input|Should Bishops be able to assign responsibility for a household to a quorum?|category=}}

=== Template:Unresolved ===
Use the {{tl|Unresolved}} template for marking a question or concern as currently unresolved in discussions on Talk Pages. This template should be inserted at the top of an unresolved discussion. It has a parameter that is a brief description of the issue. For example, the annotation
<pre>{{Unresolved|This database architecture is too complicated}}</pre>
would result in a box appearing in the text as follows:
{{Unresolved|This database architecture is too complicated|category=}}

=== Template:Resolved ===
Use the {{tl|Resolved}} template for marking a question or concern as resolved in discussions on Talk Pages. This template should be inserted at the top of a resolved discussion. It has a parameter that is a brief summary of the resolution and resultant action. For example, the annotation
<pre>{{Resolved|Added to the Use Cases}}</pre>
would result in a box appearing in the text as follows:
{{Resolved|Added to the Use Cases|category=}}

=== Template:Stub ===
Use the {{tl|Stub}} template to indicate that an article is only a stub and needs to be fleshed out. This template takes no parameter, and appears as:
{{stub}}

=== Template:ToDo ===
Use the {{tl|ToDo}} template to indicate tasks that need to be performed on an article. It has a parameter that is a brief summary of the tasks requiring action. For example, the annotation
<pre>{{ToDo|Create a detailed instructions page to show how to configure this application}}</pre>
would result in a box appearing in the text as follows:
{{ToDo|Create a detailed instructions page to show how to configure this application|category=}}

=== Template:Merge ===
Use the {{tl|Merge}} template to indicate that two or more pages contain duplicate content and should be merged into one. It has a parameter that you should use to include links to each of the pages in question. For example, the annotation
<pre>{{Merge|Merge this page with the [[Main Page]]}}</pre>
would result in a box appearing in the text as follows:
{{Merge|Merge this page with the [[Main Page]]|category=}}

=== Template:Split ===
Use the {{tl|Split}} template to indicate that the current page is too long, and needs to be split into multiple pages. For example, the annotation
<pre>{{Split}}</pre>
would result in a box appearing in the text as follows:
{{Split|category=}}

== Add sources ==
Although opinions and personal ideas can be helpful, statements purported to be official Church policy will be more effective if backed up from [[official sources]].

[[Category:Help]]
[[Category:LDSTech Administration]]

TechWiki:Guidelines

2010-05-09T03:59:23Z

Techgurufloyd: Add the syntax highlighting tidbit from the announcements page.

These '''guidelines''' will create consistency for additions and corrections to the LDSTech wiki.

== Creating new articles ==
An '''article''' in this wiki should be similar to an encyclopedia article. It should cover a single topic, and should stand on its own (although it may and generally should link to other articles). Topics may be very broad, or quite specific.

=== Article title ===
The '''title''' of the article should be chosen carefully. It should describe the content well, and be a term that others would naturally apply to this content. A user of the wiki can type a title in the '''search box''' of the wiki and click '''Go''' (or press '''Enter''') and go directly to an article if an article with that title exists. Words in titles should not be capitalized, except for the first word and any proper nouns.

=== Before creating a page ===
Before you create a new page, make sure that
* The content is not already covered on another page
* The content is appropriate to the LDSTech wiki
* You have chosen an appropriate title

== Editing pages ==
The content of the wiki makes progress because many users make contributions, from making simple spelling corrections to adding new articles. Be bold so that you move the project forward, but don't be hasty -- sloppy edits will just create more work for others and lower the quality of the wiki.

=== Use Preview ===
Before you click '''Save page''' to save your changes, use the '''Show preview''' button to see how your changes will actually appear. This can help save you from posting content with obvious errors.

=== Make changes at one time ===
Use the preview button liberally as you are creating a page or making edits. Whenever possible, make all your changes to a page in a single session. If you save the page often, you will needlessly clutter the history of the page and fill up the '''recent changes''' log with many entries. This makes it more difficult for other users to discover what has actually changed.

=== Headings ===
The [http://meta.wikimedia.org/wiki/Help:Section#Creation_and_numbering_of_sections MediaWiki style guide] suggests avoiding H1 level headings (i.e., <code>= This is an incorrect article heading =</code>) in your articles, as those type of headings are used for the article titles. We prefer all article sub-headings to begin with H2 level headings (i.e., <code>== This is a correct article heading ==</code>) and then go downwards from there. Words in headings should not be capitalized, except for the first word and any proper nouns.

=== Links ===
Links (both wikilinks and external links) should be attached to text that is a natural part of the article. Avoid the common blog practice of putting links around the word "here."
* '''Incorrect''': Read the MediaWiki Handbook [http://meta.wikimedia.org/wiki/Help:Contents here].
* '''Correct''': Read the [http://meta.wikimedia.org/wiki/Help:Contents MediaWiki Handbook].

=== Minor edits ===
As you save your changes after editing a page, there is a check box labeled "This is a minor edit." As explained in the [http://en.wikipedia.org/wiki/How_to_edit#Minor_edits Wikipedia article on minor edits], these are to be used only for "typo corrections, formatting and presentational changes, rearranging of text without modifying content, etc. A minor edit is a version that the editor believes requires no review and could never be the subject of a dispute." Any addition of new content can never be a minor edit, even if it is not a lot of text.

=== Style guide ===
For consistent formatting and usage of common words and concepts, please reference the [[LDSTech:Manual of Style|style guide]].

=== Changing the title ===
If you need to change the title of an article, do not simply create a new article and copy the content from the old page to the new page. Instead, use the MediaWiki '''[http://en.wikipedia.org/wiki/Wikipedia:How_to_rename_(move)_a_page Move]''' feature (one of the top tabs). '''Move''' lets you specify a new title for the page, then moves the content and the associated talk page to the new page, and finally edits the old page to be a redirect to the new page. This is far easier than doing it manually. It also keeps the discussion page with the new title, which is generally desirable, and leaves a clearer history of the actual title change.

== Discussion pages ==
Each article has a '''discussion page''' or '''talk page'''. These pages provide a forum for the community to come to a consensus as to the direction a particular article should take. If there is anything at all controversial about a change you have made or think ought to be made, start a discussion using the discussion pages.

You should '''never''' put discussion, questions, or comments in the body of articles. Discussion should be limited to the discussion page.

=== Topics ===
Discussion pages can be organized into topics. This is particularly helpful for articles that have multiple sections and thus may have ongoing discussion related to different sections.

If you are responding to a particular question, use one or more colons to indent your response so that it is clear what comment or question you are responding to.

=== Sign your name ===
You can easily sign your name by adding four tildes to the end of your comment. This will add your username and a time stamp. You can use three tildes for just your name or five tildes for just the timestamp, but the preferred signature uses four tildes to include both. The appearance of your username is determined by the preferences you have set. Comments in discussion pages should always be signed, but signatures should not be placed in articles.

== Syntax Highlighting ==
We have Syntax Highlighting on the wiki so that if you paste source code snippets, they will show up with highlights. The [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi MediaWiki SyntaxHighlight extension documentation] explains how to use syntax highlighting for your source code (including Java, HTML, SQL, XML, and many more). Here's a simple example:

{| border=1
! WikiText !! Result
|-
|<pre><source lang="java">
public static void main(final String[] args)
{
// Here is a comment
System.out.println("Hello, World!");
int m = 3 * 4;
}
</source>
</pre>
|<source lang="java">
public static void main(final String[] args)
{
// Here is a comment
System.out.println("Hello, World!");
int m = 3 * 4;
}
</source>
|-
|}

== Use templates to flag questionable or incomplete content ==
If you come across an article that needs to be edited or should be deleted, you can flag the article by inserting a template. To do this, simply edit the article and insert the text '''<nowiki>{{Template_Name|Parameter}}</nowiki>'''. The parameters for a template are documented on the template page, which you can examine by going to the appropriate template page: '''<nowiki>Template:Template_Name</nowiki>'''.

=== Template:Edit ===
Use the {{tl|Edit}} template if you find a page that requires editing, but you don't have the time or skill to edit it. This template may be inserted at the top of the page if it applies to the entire page, or at the beginning of a section if it only applies to that section. It has a parameter that is a brief description of what needs to be corrected. For example, the annotation
<pre>{{Edit|Eliminate first person from this section}}</pre>
would result in a box appearing in the text as follows:
{{Edit|Eliminate first person from this section|category=}}

=== Template:Draft ===
Use the {{tl|Draft}} template for policy or guideline pages that are in a draft stage. This template should be inserted at the top of the page. It has a parameter that is a brief description of the reason for the draft status. For example, the annotation
<pre>{{Draft|Waiting for approval from Tom Welch}}</pre>
would result in a box appearing in the text as follows:
{{Draft|Waiting for approval from Tom Welch|category=}}

=== Template:Need Input ===
Use the {{tl|Need Input}} template when a particular issue in an article or discussion requires additional information, clarification, or collaboration. Indicate what is needed with a brief description of the issue or ask a question. For example, the annotation
<pre>{{Need Input|Should Bishops be able to assign responsibility for a household to a quorum?}}</pre>
would result in a box appearing in the text as follows:
{{Need Input|Should Bishops be able to assign responsibility for a household to a quorum?|category=}}

=== Template:Unresolved ===
Use the {{tl|Unresolved}} template for marking a question or concern as currently unresolved in discussions on Talk Pages. This template should be inserted at the top of an unresolved discussion. It has a parameter that is a brief description of the issue. For example, the annotation
<pre>{{Unresolved|This database architecture is too complicated}}</pre>
would result in a box appearing in the text as follows:
{{Unresolved|This database architecture is too complicated|category=}}

=== Template:Resolved ===
Use the {{tl|Resolved}} template for marking a question or concern as resolved in discussions on Talk Pages. This template should be inserted at the top of a resolved discussion. It has a parameter that is a brief summary of the resolution and resultant action. For example, the annotation
<pre>{{Resolved|Added to the Use Cases}}</pre>
would result in a box appearing in the text as follows:
{{Resolved|Added to the Use Cases|category=}}

=== Template:Stub ===
Use the {{tl|Stub}} template to indicate that an article is only a stub and needs to be fleshed out. This template takes no parameter, and appears as:
{{stub}}

=== Template:ToDo ===
Use the {{tl|ToDo}} template to indicate tasks that need to be performed on an article. It has a parameter that is a brief summary of the tasks requiring action. For example, the annotation
<pre>{{ToDo|Create a detailed instructions page to show how to configure this application}}</pre>
would result in a box appearing in the text as follows:
{{ToDo|Create a detailed instructions page to show how to configure this application|category=}}

== Add sources ==
Although opinions and personal ideas can be helpful, statements purported to be official Church policy will be more effective if backed up from [[official sources]].

[[Category:Help]]
[[Category:LDSTech Administration]]

User:Anthonywhite

2010-04-23T05:17:45Z

Techgurufloyd: add contact info from ysa project

==Anthony White==

{| border="1" cellspacing="0" cellpadding="2"
! colspan="2" | Communicate with me
|-
| Phone ||
|-
| Email || anthonywhite04 [at] gmail.com
|-
| Facebook ||
|-
| Twitter ||
|-
| LinkedIn ||
|-
| Google Talk ||
|-
| Skype ||
|-
| AIM ||
|-
| Yahoo ||
|-
| MSN ||
|}

User:Jessestay

2010-04-23T05:15:44Z

Techgurufloyd: add contact info from ysa project

Social Media

{| border="1" cellspacing="0" cellpadding="2"
! colspan="2" | Communicate with me
|-
| Phone ||
|-
| Email || jesse [at] staynalive.com
|-
| Facebook || http://facebook.com/jessestay
|-
| Twitter || http://twitter.com/jesse
|-
| LinkedIn ||
|-
| Google Talk ||
|-
| Skype ||
|-
| AIM ||
|-
| Yahoo ||
|-
| MSN ||
|}

User:Ryanlf

2010-04-23T04:24:51Z