<?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: Shared Calendar</title> <atom:link href="http://www.churchtechy.com/2009/01/shared-calendar/feed/" rel="self" type="application/rss+xml" /><link>http://www.churchtechy.com/2009/01/shared-calendar/</link> <description>where Tech meets church</description> <lastBuildDate>Tue, 31 Jan 2012 17:17:56 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=</generator> <item><title>By: mike</title><link>http://www.churchtechy.com/2009/01/shared-calendar/comment-page-1/#comment-1570</link> <dc:creator>mike</dc:creator> <pubDate>Wed, 15 Sep 2010 00:45:29 +0000</pubDate> <guid
isPermaLink="false">http://www.churchtechy.com/?p=172#comment-1570</guid> <description>Convenient Calendar </description> <content:encoded><![CDATA[<p>Convenient Calendar</p> ]]></content:encoded> </item> <item><title>By: Stuart</title><link>http://www.churchtechy.com/2009/01/shared-calendar/comment-page-1/#comment-268</link> <dc:creator>Stuart</dc:creator> <pubDate>Mon, 05 Oct 2009 11:41:14 +0000</pubDate> <guid
isPermaLink="false">http://www.churchtechy.com/?p=172#comment-268</guid> <description>I&#039;ve come round a bit to the data not being stored locally. So long as mine doesn&#039;t get out there then ok :)
Will definitely take another look - hopefully the website will be finished real soon now and I can get them back to looking at what they need out of this type of thing. But at least I now have a few options. </description> <content:encoded><![CDATA[<p>I&#039;ve come round a bit to the data not being stored locally. So long as mine doesn&#039;t get out there then ok :)</p><p>Will definitely take another look &#8211; hopefully the website will be finished real soon now and I can get them back to looking at what they need out of this type of thing. But at least I now have a few options.</p> ]]></content:encoded> </item> <item><title>By: Jeff</title><link>http://www.churchtechy.com/2009/01/shared-calendar/comment-page-1/#comment-266</link> <dc:creator>Jeff</dc:creator> <pubDate>Mon, 05 Oct 2009 03:30:16 +0000</pubDate> <guid
isPermaLink="false">http://www.churchtechy.com/?p=172#comment-266</guid> <description>Hi Stuart- you may want to take another look at iZoca.com.  It does basically everything you need it to do except store data on your own servers. You can get an iCal feed to other devices and applications such as iPhone, outlook, etc. Each group on iZoca has a unique calendar that rolls up to members&#039; personal calendar. Groups also have discussions, shared photos, RSVP to events...  I think it would be worth checking out- and it&#039;s free! </description> <content:encoded><![CDATA[<p>Hi Stuart- you may want to take another look at iZoca.com.  It does basically everything you need it to do except store data on your own servers. You can get an iCal feed to other devices and applications such as iPhone, outlook, etc. Each group on iZoca has a unique calendar that rolls up to members&#039; personal calendar. Groups also have discussions, shared photos, RSVP to events&#8230;  I think it would be worth checking out- and it&#039;s free!</p> ]]></content:encoded> </item> <item><title>By: Stuart</title><link>http://www.churchtechy.com/2009/01/shared-calendar/comment-page-1/#comment-152</link> <dc:creator>Stuart</dc:creator> <pubDate>Fri, 12 Jun 2009 11:19:21 +0000</pubDate> <guid
isPermaLink="false">http://www.churchtechy.com/?p=172#comment-152</guid> <description>Hi David - unfortunately nothing did become of this. I did lots of research even went so far as downloading lots of stuff to try, etc. Even installed sharepoint for a while - however, time and the credit crunch got in the way.
Me - I just couldn&#039;t allocate enough time in my personal life and the church put a spending freeze on which would preclude any form of paid solution. I forget its name now, but there is a paid solution of &lt;$30 per machine that would suit in our case - still $300 is $300! </description> <content:encoded><![CDATA[<p>Hi David &#8211; unfortunately nothing did become of this. I did lots of research even went so far as downloading lots of stuff to try, etc. Even installed sharepoint for a while &#8211; however, time and the credit crunch got in the way.</p><p>Me &#8211; I just couldn&#039;t allocate enough time in my personal life and the church put a spending freeze on which would preclude any form of paid solution. I forget its name now, but there is a paid solution of &lt;$30 per machine that would suit in our case &#8211; still $300 is $300!</p> ]]></content:encoded> </item> <item><title>By: David</title><link>http://www.churchtechy.com/2009/01/shared-calendar/comment-page-1/#comment-151</link> <dc:creator>David</dc:creator> <pubDate>Fri, 12 Jun 2009 05:29:46 +0000</pubDate> <guid
isPermaLink="false">http://www.churchtechy.com/?p=172#comment-151</guid> <description>What ever came of this? Did you find a solution?  Thanks. </description> <content:encoded><![CDATA[<p>What ever came of this? Did you find a solution?  Thanks.</p> ]]></content:encoded> </item> <item><title>By: Simon</title><link>http://www.churchtechy.com/2009/01/shared-calendar/comment-page-1/#comment-132</link> <dc:creator>Simon</dc:creator> <pubDate>Sat, 25 Apr 2009 17:05:28 +0000</pubDate> <guid
isPermaLink="false">http://www.churchtechy.com/?p=172#comment-132</guid> <description>Thanks Stuart I knew of problems of this coming from the actual church leadership, didn&#039;t know some of the IT people were still fighting against it too.  Hopefully we can eventually change your mind on internet based applications.  Calling them all cloud computing is a little too buzz wordy for me. </description> <content:encoded><![CDATA[<p>Thanks Stuart I knew of problems of this coming from the actual church leadership, didn&#039;t know some of the IT people were still fighting against it too.  Hopefully we can eventually change your mind on internet based applications.  Calling them all cloud computing is a little too buzz wordy for me.</p> ]]></content:encoded> </item> <item><title>By: Stuart</title><link>http://www.churchtechy.com/2009/01/shared-calendar/comment-page-1/#comment-131</link> <dc:creator>Stuart</dc:creator> <pubDate>Sat, 25 Apr 2009 09:56:00 +0000</pubDate> <guid
isPermaLink="false">http://www.churchtechy.com/?p=172#comment-131</guid> <description>Apologies Simon - I managed to delete your other post, doh!
To answer your query though ... There are several reasons ... 1. The external Church infrastructure is not 100% guaranteed to stay up (link to ISP / cabling / power) and getting these sorted are not quick easy or cheap. 2. I am not a fan of cloud computing - though in my professional life it goes against the grain as my job exists to support the underlying interconnectivity for cloud computing. 3. Some of the data is sensitive and its easier to keep in house than teach old dogs ....! </description> <content:encoded><![CDATA[<p>Apologies Simon &#8211; I managed to delete your other post, doh!</p><p>To answer your query though &#8230; There are several reasons &#8230; 1. The external Church infrastructure is not 100% guaranteed to stay up (link to ISP / cabling / power) and getting these sorted are not quick easy or cheap. 2. I am not a fan of cloud computing &#8211; though in my professional life it goes against the grain as my job exists to support the underlying interconnectivity for cloud computing. 3. Some of the data is sensitive and its easier to keep in house than teach old dogs &#8230;.!</p> ]]></content:encoded> </item> <item><title>By: Simon</title><link>http://www.churchtechy.com/2009/01/shared-calendar/comment-page-1/#comment-130</link> <dc:creator>Simon</dc:creator> <pubDate>Sat, 25 Apr 2009 04:18:34 +0000</pubDate> <guid
isPermaLink="false">http://www.churchtechy.com/?p=172#comment-130</guid> <description>Interested to know why it has to run locally? </description> <content:encoded><![CDATA[<p>Interested to know why it has to run locally?</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Served from: www.churchtechy.com @ 2012-02-10 10:14:01 by W3 Total Cache -->
