TechWiki - User contributions [en]

Sharing the gospel online

2022-06-03T00:38:03Z

Davebailey: Removing obsolete information and fixing links

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]]
* [https://www.twitter.com Twitter]
* [[Youtube]]
* [[Flickr]]
* [https://www.yelp.com Yelp]
* [https://foursquare.com/ Foursquare]
* [https://en.wikipedia.org Wikipedia]
* [[Blogging]]
* [[Helpful quotes related to social media]]
* [[Talking about online missionary work at church]]
* [[Helpful articles and tutorials for sharing the gospel online]]

[[Category:Social networking]]

Sharing the gospel online

2022-06-03T00:34:44Z

Davebailey: Social bookmarking is essentially obsolete.

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]]
* [[Twitter]]
* [[Mixi]]
* [[Youtube]]
* [[Flickr]]
* [[Google Local]]
* [[Yelp]]
* [[Foursquare]]
* [[Gowalla]]
* [[Wikipedia]]
* [[Blogging]]
* [[Helpful quotes related to social media]]
* [[Talking about online missionary work at church]]
* [[Helpful articles and tutorials for sharing the gospel online]]

[[Category:Social networking]]

User:Davebailey

2014-01-23T20:20:04Z

Davebailey: /* Focus on articles */

==David Bailey==
[[image:davebailey.jpg | right | border | 150px]]
'''Security consultant''' 
'''Technology safety advocate''' 
'''Network whiz''' 
'''Linux guru''' 
'''Python tinkerer'''

{| border="1" cellspacing="0" cellpadding="2" class="collapsible"
! colspan="2" | Communicate with me
|-
| LinkedIn || [http://linkedin.com/in/davebailey David Bailey on Linkedin]
|}

===Focus on articles===
* [[Identity theft (Family Safety)]]
* [[Social engineering (Family Safety)]]
* [[Software updates (Family Safety)]]
* [[Password security]]
* [[Recreation Properties risk assessment]]
* [[Meeting Bulletin Application]]

===Proposed articles/projects===
* [[User:Davebailey/Security|Information Security]]
* [[User:Davebailey/Meeting Bulletin|Meeting Bulletin]]

File:Imbox notice.png

2012-09-11T15:49:18Z

Davebailey: File in public domain from Wikipedia

File in public domain from Wikipedia

Template:Notice

2012-09-11T15:29:51Z

Davebailey: Creating notice template - copied from Wikipedia

{{ mbox
| name = Notice
| style = {{{style|}}}
| textstyle = {{{textstyle|}}}
| subst = <includeonly>{{subst:</includeonly><includeonly>substcheck}}</includeonly>
| demospace = {{{demospace|}}}
| image = {{#if:{{{image|}}}|[[file:{{{image}}}|40px|Notice]]}}
| small = {{{small|}}}
| smallimage = {{#if:{{{image|}}}|[[file:{{{image}}}|30px|Notice]]}}
| text = {{#if:{{{header|}}}|<div style="text-align: center">'''{{{header}}}'''</div>}}{{{text|{{{1}}}}}}

}}<noinclude>{{documentation}}</noinclude>

Local Unit Directory

2012-08-05T14:04:06Z

Davebailey: /* Creating redirection to Directory */

#REDIRECT [[Directory]]

User:Davebailey

2012-08-05T12:09:59Z

Davebailey: /* Focus on articles */

==David Bailey==
[[image:davebailey.jpg | right | border | 150px]]
'''Security consultant''' 
'''Technology safety advocate''' 
'''Network whiz''' 
'''Linux guru''' 
'''Python tinkerer'''

{| border="1" cellspacing="0" cellpadding="2" class="collapsible"
! colspan="2" | Communicate with me
|-
| LinkedIn || [http://linkedin.com/in/davebailey David Bailey on Linkedin]
|}

===Focus on articles===
* [[Identity theft (Family Safety)]]
* [[Social engineering (Family Safety)]]
* [[Software updates (Family Safety)]]
* [[Password security]]
* [[Recreation Properties risk assessment]]

===Proposed articles/projects===
* [[User:Davebailey/Security|Information Security]]
* [[User:Davebailey/Meeting Bulletin|Meeting Bulletin]]

User:Davebailey

2011-09-27T14:16:18Z

Davebailey:

==David Bailey==
[[image:davebailey.jpg | right | border | 150px]]
'''Security consultant''' 
'''Technology safety advocate''' 
'''Network whiz''' 
'''Linux guru''' 
'''Python tinkerer'''

{| border="1" cellspacing="0" cellpadding="2" class="collapsible"
! colspan="2" | Communicate with me
|-
| LinkedIn || [http://linkedin.com/in/davebailey David Bailey on Linkedin]
|}

===Focus on articles===
* [[Identity theft (Family Safety)]]
* [[Social engineering (Family Safety)]]
* [[Software updates (Family Safety)]]
* [[Password security]]
* [[User:Davebailey/Security|Information Security]]
* [[Recreation Properties risk assessment]]

User:Davebailey

2011-09-27T14:16:04Z

Davebailey:

==David Bailey==
[[image:davebailey.jpg | right | border | 150px]]
'''Security consultant''' 
'''Technology Safety Advocate''' 
'''Network whiz''' 
'''Linux guru''' 
'''Python tinkerer'''

{| border="1" cellspacing="0" cellpadding="2" class="collapsible"
! colspan="2" | Communicate with me
|-
| LinkedIn || [http://linkedin.com/in/davebailey David Bailey on Linkedin]
|}

===Focus on articles===
* [[Identity theft (Family Safety)]]
* [[Social engineering (Family Safety)]]
* [[Software updates (Family Safety)]]
* [[Password security]]
* [[User:Davebailey/Security|Information Security]]
* [[Recreation Properties risk assessment]]

User:Davebailey

2011-09-27T14:13:31Z

Davebailey: /* David Bailey */

==David Bailey==
[[image:davebailey.jpg | right | border | 150px]]
'''Security consultant''' 
'''Network whiz''' 
'''Linux guru''' 
'''Python tinkerer'''

{| border="1" cellspacing="0" cellpadding="2" class="collapsible"
! colspan="2" | Communicate with me
|-
| LinkedIn || [http://linkedin.com/in/davebailey David Bailey on Linkedin]
|}

===Focus on articles===
* [[Identity theft (Family Safety)]]
* [[Social engineering (Family Safety)]]
* [[Software updates (Family Safety)]]
* [[Password security]]
* [[User:Davebailey/Security|Information Security]]
* [[Recreation Properties risk assessment]]

Template:FamilySafetyIndex

2011-04-15T15:25:53Z

Davebailey: Adding Cyber Bullying

{{Box
| float=right
| color=ldstech
| width=252px
| title=[[Family safety]]
| content=<div style="font-size:90%;">
* [[Family safety with technology]]
* [[Internet (Family Safety)|The Internet]]
* [[Mobile devices (Family Safety)|Mobile devices]]
* [[Social Networking (Family Safety)|Social networking]]
* [[Internet filtering (Family Safety)|Content filtering]]
----
<center>'''Media Choices'''</center>
* [[TV, movies & music (Family Safety)|TV, movies & music]]
* [[Video Games (Family Safety)|Video games]]
* [[Online Games (Family Safety)|Online games]]
----
<center>'''Common Concerns'''</center>
* [[Pornography (Family Safety)|Pornography]]
* [[Malicious software (Family Safety)|Malicious software]]
* [[File & music sharing (Family Safety)|File & music sharing]]
* [[Identity theft (Family Safety)|Identity theft]]
* [[Social engineering (Family Safety)|Social engineering]]
* [[CyberBullying (Family Safety)|Cyber Bullying]]
----
<center>{{navbar|{{{template-name|FamilySafetyIndex}}}}}</center>
</div>
}}
<includeonly>
[[Category:Family safety]]</includeonly><noinclude>

== Documentation ==
Use this template to include an index of the major '''Family safety with technology''' articles within the wiki. This index will appear in the top right corner of the article page.

=== Categorization ===
Pages that include this template will be automatically included in the [[:Category:Family safety]]

=== Usage ===
Simply insert the template near the top of the article by typing '''<nowiki>{{FamilySafetyIndex}}</nowiki>'''.

Template:FamilySafetyIndex

2011-04-11T20:18:48Z

Davebailey: Adding social engineering

{{Box
| float=right
| color=ldstech
| width=252px
| title=[[Family safety]]
| content=<div style="font-size:90%;">
* [[Family safety with technology]]
* [[Internet (Family Safety)|The Internet]]
* [[Mobile devices (Family Safety)|Mobile devices]]
* [[Social Networking (Family Safety)|Social networking]]
* [[Internet filtering (Family Safety)|Content filtering]]
----
<center>'''Media Choices'''</center>
* [[TV, movies & music (Family Safety)|TV, movies & music]]
* [[Video Games (Family Safety)|Video games]]
* [[Online Games (Family Safety)|Online games]]
----
<center>'''Common Concerns'''</center>
* [[Pornography (Family Safety)|Pornography]]
* [[Malicious software (Family Safety)|Malicious software]]
* [[File & music sharing (Family Safety)|File & music sharing]]
* [[Identity theft (Family Safety)|Identity theft]]
* [[Social engineering (Family Safety)|Social engineering]]
----
<center>{{navbar|{{{template-name|FamilySafetyIndex}}}}}</center>
</div>
}}
<includeonly>
[[Category:Family safety]]</includeonly><noinclude>

== Documentation ==
Use this template to include an index of the major '''Family safety with technology''' articles within the wiki. This index will appear in the top right corner of the article page.

=== Categorization ===
Pages that include this template will be automatically included in the [[:Category:Family safety]]

=== Usage ===
Simply insert the template near the top of the article by typing '''<nowiki>{{FamilySafetyIndex}}</nowiki>'''.

Church Security Risk Assessment Process

2010-10-25T16:03:43Z

Davebailey:

The '''Church Security Risk Assessment & Testing Process''' is designed to assist [[Community Security Engineer]]s in identifying, communicating, and assisting the project team in mitigating high-security-risk issues in [[Community Development Best Practices|community projects]].

The Church Security Risk Assessment Process is outlined in its simplest form as:

# During the community development planning stage, review the project for potential security risks.
#:
# During the planning stage, write and issue the Security Risk Assessment for the project. During a project team meeting, review the risk assessment with the team. Communicate the security imperatives to the team to help them mitigate the most critical risks. Report the results of the risk assessment and related meeting to the Church IT Security Risk Liaison.
#:
# Work with the project manager to put the security imperatives into the project plan.
#:
# During the create or development stage of the project, communicate with the project team and perform testing to ensure the security imperatives are being met.
#:
# When the project creation phase is nearing completion, perform final testing and analysis of the project. Ensure the security imperatives have been met, and record any additional critical risks that need to be addressed before completion of the creation phase of the project.
#:
# Meet with the project team to share the results of the security testing. Ensure that confirmed vulnerabilities and unmet security imperatives are recorded and tracked as bugs. Report the results of the security testing to the Church IT Security Risk Liaison.
#:
# Work with the project manager and project team to assist with questions in how to resolve any remaining unmet security risk mitigation imperatives and critical security vulnerabilities. Report any concerns and final status to the Church IT Security Risk Liaison.

== Security Risk Assessment Template ==
The Security Risk Assessment template is an outline for the CSE to perform a security risk assessment on community developed projects. This is typically done during the planning stage for a project.

== Security Testing ==
Security testing is an important part of making sure that the security imperatives are met and critical vulnerabilities are resolved prior to putting the project into operation or production.

[[Category:Security]]

Church Security Risk Assessment Process

2010-10-25T16:02:44Z

Davebailey:

The '''Church Security Risk Assessment & Testing Process''' is designed to assist [[Community Security Engineer]]s in identifying, communicating, and assisting the project team in mitigating high-security-risk issues in [[Community Development Best Practices|community projects]].

The Church Security Risk Assessment Process is outlined in its simplest form as:

# During the community development planning stage, review the project for potential security risks.

# During the planning stage, write and issue the Security Risk Assessment for the project. During a project team meeting, review the risk assessment with the team. Communicate the security imperatives to the team to help them mitigate the most critical risks. Report the results of the risk assessment and related meeting to the Church IT Security Risk Liaison.

# Work with the project manager to put the security imperatives into the project plan.

# During the create or development stage of the project, communicate with the project team and perform testing to ensure the security imperatives are being met.

# When the project creation phase is nearing completion, perform final testing and analysis of the project. Ensure the security imperatives have been met, and record any additional critical risks that need to be addressed before completion of the creation phase of the project.

# Meet with the project team to share the results of the security testing. Ensure that confirmed vulnerabilities and unmet security imperatives are recorded and tracked as bugs. Report the results of the security testing to the Church IT Security Risk Liaison.

# Work with the project manager and project team to assist with questions in how to resolve any remaining unmet security risk mitigation imperatives and critical security vulnerabilities. Report any concerns and final status to the Church IT Security Risk Liaison.

== Security Risk Assessment Template ==
The Security Risk Assessment template is an outline for the CSE to perform a security risk assessment on community developed projects. This is typically done during the planning stage for a project.

== Security Testing ==
Security testing is an important part of making sure that the security imperatives are met and critical vulnerabilities are resolved prior to putting the project into operation or production.

[[Category:Security]]

Church Security Risk Assessment Process

2010-10-25T16:02:30Z

Davebailey:

The '''Church Security Risk Assessment Process''' is designed to assist [[Community Security Engineer]]s in identifying, communicating, and assisting the project team in mitigating high-security-risk issues in [[Community Development Best Practices|community projects]].

The Church Security Risk Assessment Process is outlined in its simplest form as:

# During the community development planning stage, review the project for potential security risks.

# During the planning stage, write and issue the Security Risk Assessment for the project. During a project team meeting, review the risk assessment with the team. Communicate the security imperatives to the team to help them mitigate the most critical risks. Report the results of the risk assessment and related meeting to the Church IT Security Risk Liaison.

# Work with the project manager to put the security imperatives into the project plan.

# During the create or development stage of the project, communicate with the project team and perform testing to ensure the security imperatives are being met.

# When the project creation phase is nearing completion, perform final testing and analysis of the project. Ensure the security imperatives have been met, and record any additional critical risks that need to be addressed before completion of the creation phase of the project.

# Meet with the project team to share the results of the security testing. Ensure that confirmed vulnerabilities and unmet security imperatives are recorded and tracked as bugs. Report the results of the security testing to the Church IT Security Risk Liaison.

# Work with the project manager and project team to assist with questions in how to resolve any remaining unmet security risk mitigation imperatives and critical security vulnerabilities. Report any concerns and final status to the Church IT Security Risk Liaison.

== Security Risk Assessment Template ==
The Security Risk Assessment template is an outline for the CSE to perform a security risk assessment on community developed projects. This is typically done during the planning stage for a project.

== Security Testing ==
Security testing is an important part of making sure that the security imperatives are met and critical vulnerabilities are resolved prior to putting the project into operation or production.

[[Category:Security]]

Church Security Risk Assessment Process

2010-10-25T16:01:15Z

Davebailey: Adding security risk assesment template

The '''Church Security Risk Assessment Process''' is designed to assist [[Community Security Engineer]]s in identifying, communicating, and assisting the project team in mitigating high-security-risk issues in community projects.

The Church Security Risk Assessment Process is outlined in its simplest form as:

# During the community development planning stage, review the project for potential security risks.

# During the planning stage, write and issue the Security Risk Assessment for the project. During a project team meeting, review the risk assessment with the team. Communicate the security imperatives to the team to help them mitigate the most critical risks. Report the results of the risk assessment and related meeting to the Church IT Security Risk Liaison.

# Work with the project manager to put the security imperatives into the project plan.

# During the create or development stage of the project, communicate with the project team and perform testing to ensure the security imperatives are being met.

# When the project creation phase is nearing completion, perform final testing and analysis of the project. Ensure the security imperatives have been met, and record any additional critical risks that need to be addressed before completion of the creation phase of the project.

# Meet with the project team to share the results of the security testing. Ensure that confirmed vulnerabilities and unmet security imperatives are recorded and tracked as bugs. Report the results of the security testing to the Church IT Security Risk Liaison.

# Work with the project manager and project team to assist with questions in how to resolve any remaining unmet security risk mitigation imperatives and critical security vulnerabilities. Report any concerns and final status to the Church IT Security Risk Liaison.

== Security Risk Assessment Template ==
The Security Risk Assessment template is an outline for the CSE to perform a security risk assessment on community developed projects. This is typically done during the planning stage for a project.

== Security Testing ==
Security testing is an important part of making sure that the security imperatives are met and critical vulnerabilities are resolved prior to putting the project into operation or production.

[[Category:Security]]

Church Security Risk Assessment Process

2010-10-25T15:15:29Z

Davebailey:

Church Security Risk Assessment Process

2010-10-25T15:15:14Z

Davebailey:

Church Security Risk Assessment Process

2010-10-25T15:14:46Z

Davebailey: Initial creation of article

The '''Church Security Risk Assessment Process''' is designed to assist [[Community Security Engineers]] in identifying, communicating, and assisting the project team in mitigating high-security-risk issues in community projects.

[Category:Security]

Category:Security

2010-10-25T15:11:18Z

Davebailey: Created page with 'This is the main category for all community development security pages on the LDSTech wiki. Category:Security'

This is the main category for all community development security pages on the LDSTech wiki.

[[Category:Security]]

User talk:Davebailey

2010-09-22T16:19:51Z

Davebailey: /* STS article change */

== STS article change ==
I noticed that you added a responsibility to the [[stake technology specialist]] article: "Coordinate, but not necessarily lead, training such as adult firesides on using technology safely in the home." While I have no problem with an STS doing this if he were asked to do so by his stake president, I can find no documentation that would lead me to believe that this is an actual responsibility of the STS. I'm pretty sure that every other point listed as a responsibility is actually documented somewhere. If it is not a documented responsibility, then I think it should be in a separate section that describes other ways an STS can be helpful, but not be listed as a "responsibility." What do you think? -- [[User:Aebrown|Aebrown]] 19:47, 21 September 2010 (UTC)
:Hmm, my link is a bit tenuous, however- "You support all users of Church technology in your stake, including the stake presidency, bishoprics, auxiliary leaders, family history consultants, seminary and institute instructors, and others who use such technology in Church meetinghouses." suggests a responsibility to those who use these technologies outside the meetinghouses as well as in it. I'm fine with moving it out of responsibilities into suggestions. [[User:Davebailey|David Bailey]] 16:19, 22 September 2010 (UTC)

User:Davebailey

2010-09-09T16:58:49Z

Davebailey: /* Focus on articles */

==David Bailey==
[[image:davebailey.jpg | right | border | 150px]]
'''Security consultant''' 
'''Network whiz''' 
'''Linux guru''' 
'''Python tinkerer'''

{| border="1" cellspacing="0" cellpadding="2" class="collapsible"
! colspan="2" | Communicate with me
|-
| Phone || 801-769-6320
|-
| Email || [mailto:dr@baileynet.org dr@baileynet.org]
|-
| LinkedIn || [http://linkedin.com/in/davebailey David Bailey on Linkedin]
|}

===Focus on articles===
* [[Identity theft (Family Safety)]]
* [[Social engineering (Family Safety)]]
* [[Software updates (Family Safety)]]
* [[Password security]]
* [[User:Davebailey/Security|Information Security]]
* [[Recreation Properties risk assessment]]

User:Davebailey

2010-09-04T15:02:25Z

Davebailey: /* Focus on articles */

==David Bailey==
[[image:davebailey.jpg | right | border | 150px]]
'''Security consultant''' 
'''Network whiz''' 
'''Linux guru''' 
'''Python tinkerer'''

{| border="1" cellspacing="0" cellpadding="2" class="collapsible"
! colspan="2" | Communicate with me
|-
| Phone || 801-769-6320
|-
| Email || [mailto:dr@baileynet.org dr@baileynet.org]
|-
| LinkedIn || [http://linkedin.com/in/davebailey David Bailey on Linkedin]
|}

===Focus on articles===
* [[Identity theft (Family Safety)]]
* [[Social engineering (Family Safety)]]
* [[Software updates (Family Safety)]]
* [[User:Davebailey/Security|Information Security]]
* [[Recreation Properties risk assessment]]

User:Davebailey

2010-09-04T14:08:56Z

Davebailey:

==David Bailey==
[[image:davebailey.jpg | right | border | 150px]]
'''Security consultant''' 
'''Network whiz''' 
'''Linux guru''' 
'''Python tinkerer'''

{| border="1" cellspacing="0" cellpadding="2" class="collapsible"
! colspan="2" | Communicate with me
|-
| Phone || 801-769-6320
|-
| Email || [mailto:dr@baileynet.org dr@baileynet.org]
|-
| LinkedIn || [http://linkedin.com/in/davebailey David Bailey on Linkedin]
|}

===Focus on articles===
* [[Identity theft (Family Safety)]]
* [[Social engineering (Family Safety)]]
* [[User:Davebailey/Security|Information Security]]
* [[Recreation Properties risk assessment]]

User:Davebailey

2010-09-04T13:34:30Z

Davebailey:

==David Bailey==
[[image:davebailey.jpg | right | border | 150px]]
'''Security consultant''' 
'''Network whiz''' 
'''Linux guru''' 
'''Python tinkerer'''

{| border="1" cellspacing="0" cellpadding="2" class="collapsible"
! colspan="2" | Communicate with me
|-
| Phone || 801-769-6320
|-
| Email || [mailto:dr@baileynet.org dr@baileynet.org]
|-
| LinkedIn || [http://linkedin.com/in/davebailey David Bailey on Linkedin]
|}

===Focus on articles===
* [[Identity theft (Family Safety)]]
* [[User:Davebailey/Security|Information Security]]
* [[Recreation Properties risk assessment]]

User:Davebailey

2010-05-07T17:29:11Z

Davebailey:

==David Bailey==
[[image:davebailey.jpg | right | border | 150px]]
'''Security consultant''' 
'''Network whiz''' 
'''Linux guru''' 
'''Python tinkerer'''

{| border="1" cellspacing="0" cellpadding="2" class="collapsible"
! colspan="2" | Communicate with me
|-
| Phone || 801-769-6320
|-
| Email || [mailto:dr@baileynet.org dr@baileynet.org]
|-
| LinkedIn || [http://linkedin.com/in/davebailey David Bailey on Linkedin]
|}

'''Articles in progress
* [[User:Davebailey/Security|Information Security]]
* [[Recreation Properties risk assessment]]

User:Davebailey

2010-05-07T17:07:47Z

Davebailey:

==David Bailey==
[[image:davebailey.jpg | right | border | 150px]]
'''Security consultant''' 
'''Network whiz''' 
'''Linux guru''' 
'''Python tinkerer'''

{| border="1" cellspacing="0" cellpadding="2" class="collapsible"
! colspan="2" | Communicate with me
|-
| Phone || 801-769-6320
|-
| Email || [mailto:dr@baileynet.org dr@baileynet.org]
|-
| LinkedIn || [http://linkedin.com/in/davebailey David Bailey on Linkedin]
|}

'''Articles in progress
* [[User:Davebailey/Security|Security]]
* [[User:Davebailey/Recreational Properties Risk Assessment|Recreational Properties Risk Assessment]]

User:Davebailey

2010-05-07T16:44:37Z

Davebailey:

==David Bailey==
[[image:davebailey.jpg | right | border | 150px]]
'''Security consultant''' 
'''Network whiz''' 
'''Linux guru''' 
'''Python tinkerer'''

{| border="1" cellspacing="0" cellpadding="2" class="collapsible"
! colspan="2" | Communicate with me
|-
| Phone || 801-769-6320
|-
| Email || [mailto:dr@baileynet.org dr@baileynet.org]
|-
| LinkedIn || [http://linkedin.com/in/davebailey David Bailey on Linkedin]
|}

'''Articles in progress
* [[User:Davebailey/Security|Security]]
* [[User:Davebailey/Recreational Properties|Recreational Properties Risk Assessment]]

User:Davebailey

2010-04-27T01:11:31Z

Davebailey:

==David Bailey==
[[image:davebailey.jpg | right | border | 150px]]
'''Security consultant''' 
'''Network whiz''' 
'''Linux guru''' 
'''Python tinkerer'''

{| border="1" cellspacing="0" cellpadding="2" class="collapsible"
! colspan="2" | Communicate with me
|-
| Phone || 801-769-6320
|-
| Email || [mailto:dr@baileynet.org dr@baileynet.org]
|-
| LinkedIn || [http://linkedin.com/in/davebailey David Bailey on Linkedin]
|}

'''Articles in progress
* [[User:Davebailey/Security|Security]]

User:Davebailey

2010-04-27T01:11:12Z

Davebailey: Adding link to security section

==David Bailey==
[[image:davebailey.jpg | right | border | 150px]]
'''Security consultant''' 
'''Network whiz''' 
'''Linux guru''' 
'''Python tinkerer'''

{| border="1" cellspacing="0" cellpadding="2" class="collapsible"
! colspan="2" | Communicate with me
|-
| Phone || 801-769-6320
|-
| Email || [mailto:dr@baileynet.org dr@baileynet.org]
|-
| LinkedIn || [http://linkedin.com/in/davebailey David Bailey on Linkedin]
|}

'''Articles in progress
* [[User:Davebailey/Security Security]]

User:Davebailey

2010-04-19T17:54:46Z

Davebailey: Adding LinkedIn link

User:Davebailey

2010-04-19T17:52:29Z

Davebailey: resizing profile photo

==David Bailey==
[[image:davebailey.jpg | right | border | 150px]]
'''Security Consultant''' 
'''Python tinkerer''' 
'''Linux guru'''

{| border="1" cellspacing="0" cellpadding="2" class="collapsible"
! colspan="2" | Communicate with me
|-
| Phone || 801-769-6320
|-
| Email || [mailto:dr@baileynet.org dr@baileynet.org]
|}

File:Davebailey.jpg

2010-04-19T17:51:29Z

Davebailey: User:davebailey photo

User:davebailey photo

User:Davebailey

2010-04-19T17:50:34Z

Davebailey: Creating profile

==David Bailey==
[[image:davebailey.jpg | right | border]]
'''Security Consultant''' 
'''Python tinkerer''' 
'''Linux guru'''

{| border="1" cellspacing="0" cellpadding="2" class="collapsible"
! colspan="2" | Communicate with me
|-
| Phone || 801-769-6320
|-
| Email || [mailto:dr@baileynet.org dr@baileynet.org]
|}