<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Mt. Gilead&#8217;s Experience with Google Apps for Domains &#8211; Part II</title>
	<atom:link href="http://churchtechmatters.com/2009/04/27/mt-gileads-experience-with-google-apps-for-domains-part-ii/feed/" rel="self" type="application/rss+xml" />
	<link>http://churchtechmatters.com/2009/04/27/mt-gileads-experience-with-google-apps-for-domains-part-ii/</link>
	<description>A site for tech volunteers written by tech volunteers</description>
	<lastBuildDate>Thu, 11 Mar 2010 12:46:29 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Interesting Church Tech Links for May 3, 2009 &#171; Web Ministry Thoughts</title>
		<link>http://churchtechmatters.com/2009/04/27/mt-gileads-experience-with-google-apps-for-domains-part-ii/comment-page-1/#comment-33255</link>
		<dc:creator>Interesting Church Tech Links for May 3, 2009 &#171; Web Ministry Thoughts</dc:creator>
		<pubDate>Mon, 04 May 2009 03:52:40 +0000</pubDate>
		<guid isPermaLink="false">http://churchtechmatters.com/?p=1079#comment-33255</guid>
		<description>[...] Mt. Gilead’s Experience with Google Apps for Domains – Part I and Part&#160;II [...]</description>
		<content:encoded><![CDATA[<p>[...] Mt. Gilead’s Experience with Google Apps for Domains – Part I and Part&nbsp;II [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paschott</title>
		<link>http://churchtechmatters.com/2009/04/27/mt-gileads-experience-with-google-apps-for-domains-part-ii/comment-page-1/#comment-33248</link>
		<dc:creator>paschott</dc:creator>
		<pubDate>Fri, 01 May 2009 19:37:27 +0000</pubDate>
		<guid isPermaLink="false">http://churchtechmatters.com/?p=1079#comment-33248</guid>
		<description>I can definitely see where you&#039;re coming from. My pastor doesn&#039;t even use e-mail, which I find kind of amusing. He mailed something to me that I got the next day, but would have gotten same day had someone e-mailed it to me.

For people like that, I find a proof of concept phase is usually worthwhile with any change. I had to go through this a little before committing our e-mail servers over to Google Apps by forwarding a copy of all e-mails from the POP provider to the corresponding Google Apps addresses. People could then test out reading e-mails before we ever converted.  We worked out the kinks there and moved on.  But I&#039;m definitely open to continuing the discussion offline.

I&#039;d also still say that this solution isn&#039;t for everyone. It works for us - we&#039;re small and can&#039;t really afford any full time e-mail admins or to pay for hosted e-mail. We get quite a bit of value for our purposes, but not everyone will get that same value. I know that larger churches will have issues just due to the sending restrictions.</description>
		<content:encoded><![CDATA[<p>I can definitely see where you&#8217;re coming from. My pastor doesn&#8217;t even use e-mail, which I find kind of amusing. He mailed something to me that I got the next day, but would have gotten same day had someone e-mailed it to me.</p>
<p>For people like that, I find a proof of concept phase is usually worthwhile with any change. I had to go through this a little before committing our e-mail servers over to Google Apps by forwarding a copy of all e-mails from the POP provider to the corresponding Google Apps addresses. People could then test out reading e-mails before we ever converted.  We worked out the kinks there and moved on.  But I&#8217;m definitely open to continuing the discussion offline.</p>
<p>I&#8217;d also still say that this solution isn&#8217;t for everyone. It works for us &#8211; we&#8217;re small and can&#8217;t really afford any full time e-mail admins or to pay for hosted e-mail. We get quite a bit of value for our purposes, but not everyone will get that same value. I know that larger churches will have issues just due to the sending restrictions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart</title>
		<link>http://churchtechmatters.com/2009/04/27/mt-gileads-experience-with-google-apps-for-domains-part-ii/comment-page-1/#comment-33244</link>
		<dc:creator>Stuart</dc:creator>
		<pubDate>Fri, 01 May 2009 10:46:27 +0000</pubDate>
		<guid isPermaLink="false">http://churchtechmatters.com/?p=1079#comment-33244</guid>
		<description>Peter - here isn&#039;t the best place to fully answer your question (forum?) but the main battle I have is in convincing the pastor. He is a complete techno-phobe despite being younger than myself.</description>
		<content:encoded><![CDATA[<p>Peter &#8211; here isn&#8217;t the best place to fully answer your question (forum?) but the main battle I have is in convincing the pastor. He is a complete techno-phobe despite being younger than myself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Golden</title>
		<link>http://churchtechmatters.com/2009/04/27/mt-gileads-experience-with-google-apps-for-domains-part-ii/comment-page-1/#comment-33242</link>
		<dc:creator>Tim Golden</dc:creator>
		<pubDate>Wed, 29 Apr 2009 01:46:55 +0000</pubDate>
		<guid isPermaLink="false">http://churchtechmatters.com/?p=1079#comment-33242</guid>
		<description>thanks for another great/informative post.. i just got off the phone with another local church  looking to use google apps for their church.. this post will help them understand a bit more in depth that i explained...you save me the effort ;)

We at http://www.DurhamE.org  have been using gapps since last Nov and have been very successful with many of the tools, the calendar powers our events section of the our website as well as internal calendars for sharing meetings, 

email.. let&#039;s just say it&#039;s one less exchange server i need to support.. thanks gapps! 

Our ministry teams have been using gdocs for collaboration, and gsites for the youth website and while the worship other ministry teams and uses gsites for an internal team communication tool.

so many tools at their disposal and all for free with little support on my end.

Tim Golden
http://twitter.com/goldeneye
www.DurhamE.org</description>
		<content:encoded><![CDATA[<p>thanks for another great/informative post.. i just got off the phone with another local church  looking to use google apps for their church.. this post will help them understand a bit more in depth that i explained&#8230;you save me the effort <img src='http://churchtechmatters.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>We at <a href="http://www.DurhamE.org" rel="nofollow">http://www.DurhamE.org</a>  have been using gapps since last Nov and have been very successful with many of the tools, the calendar powers our events section of the our website as well as internal calendars for sharing meetings, </p>
<p>email.. let&#8217;s just say it&#8217;s one less exchange server i need to support.. thanks gapps! </p>
<p>Our ministry teams have been using gdocs for collaboration, and gsites for the youth website and while the worship other ministry teams and uses gsites for an internal team communication tool.</p>
<p>so many tools at their disposal and all for free with little support on my end.</p>
<p>Tim Golden<br />
<a href="http://twitter.com/goldeneye" rel="nofollow">http://twitter.com/goldeneye</a><br />
<a href="http://www.DurhamE.org" rel="nofollow">http://www.DurhamE.org</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Calabrese</title>
		<link>http://churchtechmatters.com/2009/04/27/mt-gileads-experience-with-google-apps-for-domains-part-ii/comment-page-1/#comment-33240</link>
		<dc:creator>Michael Calabrese</dc:creator>
		<pubDate>Tue, 28 Apr 2009 18:05:03 +0000</pubDate>
		<guid isPermaLink="false">http://churchtechmatters.com/?p=1079#comment-33240</guid>
		<description>A few things that I would point out.  I have switch our church to using Google Apps for email.  Our big motivator was spam.  After moving to Google Apps that was no longer an issue as they have a great spam filter.

The transition was very smooth, even for our non-technical users.  Those using outlook noticed no real change (they where using POP to download to their machines already).  Those using the web interface like Google&#039;s version better.

One note about the send bulk emails.  I would suggest not to send bulk emails with every one in a To, CC or BCC.  This is not polite as some people may not really want their email known to every one else.  Small groups is fine (5-10) but I would not do any larger.

I personally would setup a Linux server application to do that.  The email would be sent directly from the server and not through Google.  I know that it may be less convenient for the sender but it is better for the receiver.</description>
		<content:encoded><![CDATA[<p>A few things that I would point out.  I have switch our church to using Google Apps for email.  Our big motivator was spam.  After moving to Google Apps that was no longer an issue as they have a great spam filter.</p>
<p>The transition was very smooth, even for our non-technical users.  Those using outlook noticed no real change (they where using POP to download to their machines already).  Those using the web interface like Google&#8217;s version better.</p>
<p>One note about the send bulk emails.  I would suggest not to send bulk emails with every one in a To, CC or BCC.  This is not polite as some people may not really want their email known to every one else.  Small groups is fine (5-10) but I would not do any larger.</p>
<p>I personally would setup a Linux server application to do that.  The email would be sent directly from the server and not through Google.  I know that it may be less convenient for the sender but it is better for the receiver.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CindyK</title>
		<link>http://churchtechmatters.com/2009/04/27/mt-gileads-experience-with-google-apps-for-domains-part-ii/comment-page-1/#comment-33238</link>
		<dc:creator>CindyK</dc:creator>
		<pubDate>Tue, 28 Apr 2009 14:46:59 +0000</pubDate>
		<guid isPermaLink="false">http://churchtechmatters.com/?p=1079#comment-33238</guid>
		<description>Very good article!  Very fair.  My church - a mid sized church with about 70 email addresses now, uses Google Apps, and at this point we all love it.  

We made the switch when I first came on board here at the Church.  The Sr. Pastor was all for it.  

I admit that the learning curve was steep, and it was difficult for some of the staff who are not tech savvy.  But we held training classes and I sat with some of the staff one on one to get them up to speed first on Email, then Calendars, then Apps.

I have not found a better or easier solution for shared calendars.  Some of our shared calendars include the Main Event Calendar, Room Scheduling Calendar, Vacation Calendar, and Operations Calendar.  Then of course everyone has their own personal calendars that are shared between staffers for ease of creating appointments.

We finally share documents in Google Apps all the time. They don&#039;t have to be prepared in Google Docs, you can just upload them for sharing.

I know that some of you may not agree, but I have full faith in Google for backups of email and all our docs.  In fact I believe that they can do a much better job of backups than I can, with our current equipment and budget.

I love Google Apps!</description>
		<content:encoded><![CDATA[<p>Very good article!  Very fair.  My church &#8211; a mid sized church with about 70 email addresses now, uses Google Apps, and at this point we all love it.  </p>
<p>We made the switch when I first came on board here at the Church.  The Sr. Pastor was all for it.  </p>
<p>I admit that the learning curve was steep, and it was difficult for some of the staff who are not tech savvy.  But we held training classes and I sat with some of the staff one on one to get them up to speed first on Email, then Calendars, then Apps.</p>
<p>I have not found a better or easier solution for shared calendars.  Some of our shared calendars include the Main Event Calendar, Room Scheduling Calendar, Vacation Calendar, and Operations Calendar.  Then of course everyone has their own personal calendars that are shared between staffers for ease of creating appointments.</p>
<p>We finally share documents in Google Apps all the time. They don&#8217;t have to be prepared in Google Docs, you can just upload them for sharing.</p>
<p>I know that some of you may not agree, but I have full faith in Google for backups of email and all our docs.  In fact I believe that they can do a much better job of backups than I can, with our current equipment and budget.</p>
<p>I love Google Apps!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paschott</title>
		<link>http://churchtechmatters.com/2009/04/27/mt-gileads-experience-with-google-apps-for-domains-part-ii/comment-page-1/#comment-33236</link>
		<dc:creator>paschott</dc:creator>
		<pubDate>Tue, 28 Apr 2009 13:30:44 +0000</pubDate>
		<guid isPermaLink="false">http://churchtechmatters.com/?p=1079#comment-33236</guid>
		<description>Thanks, Jason. That was the link to the discussion I was thinking about. There is a great list of the pros and cons over there.  I think for the smaller churches, it&#039;s a great solution. For the larger ones, I think I&#039;d tend to agree that it&#039;s not quite ready.</description>
		<content:encoded><![CDATA[<p>Thanks, Jason. That was the link to the discussion I was thinking about. There is a great list of the pros and cons over there.  I think for the smaller churches, it&#8217;s a great solution. For the larger ones, I think I&#8217;d tend to agree that it&#8217;s not quite ready.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
