Article written by Ted Carnahan

I am passionate about the missional church, technology, and music. I love my call, my family, and my God!

25 responses to “Three steps to Open Source in the Church”

  1. chris

    Nice thought!
    I must admit that proprietary software do pose a risk, but as far as i can gather that we need a format, a format that will be used by all, no matter open source or proprietary.
    So the on-going battle b/w MS and ODT is all about this, but what will happen if one wins?what will happen to the other docs in the other format?
    So my thought is uniformity, and true to core, we cannot guess what technology will be after 20 years! so its better churches start storing everything in papyrus only! :)
    At least that does not reqiures a format to open and read…

  2. chris

    Nice thought!
    I must admit that proprietary software do pose a risk, but as far as i can gather that we need a format, a format that will be used by all, no matter open source or proprietary.
    So the on-going battle b/w MS and ODT is all about this, but what will happen if one wins?what will happen to the other docs in the other format?
    So my thought is uniformity, and true to core, we cannot guess what technology will be after 20 years! so its better churches start storing everything in papyrus only! :)
    At least that does not reqiures a format to open and read…

  3. Mark

    “but why should I pay a second time to access my data?”

    Because you were forced to pay the first time. It’s called capitalism. It’s where companies like Microsoft talk any old rubbish to sell you any old rubbish.

    I’ve seen that before somewhere….

  4. Mark

    “but why should I pay a second time to access my data?”

    Because you were forced to pay the first time. It’s called capitalism. It’s where companies like Microsoft talk any old rubbish to sell you any old rubbish.

    I’ve seen that before somewhere….

  5. Scott

    I just started a series of posts on my blog on why churches should be using open source. Great to see others talking about it too.

  6. Scott

    I just started a series of posts on my blog on why churches should be using open source. Great to see others talking about it too.

  7. Another Post on Open Source in the Church « The Country Parson

    [...] January 3, 2008 by countryparson I saw this post about churches moving to open source this morning. [...]

  8. Byron

    I would like to convert our Church to open source, but what about accounting packages that require Microsoft. The Software developers have to support opensource also. Not just about sermons, Church is a big business and requires many programs to run on their computer systems.

  9. WMarkH

    Good points. However, this advice may not go far enough. As someone has pointed out, “The great thing about standards is that there are so many to choose from.” This applies in the open source arena as well. Sure, I might not have to “pay” for document conversion, but if a standard I depend on never really catches on and is decremented ten years from now, is my grandmother ready to do the software engineering necessary to convert those old documents?

    Whenever the opportunity arises, I try to educate users toward the principles of simplicity and proven endurance. For instance, ASCII is forever. It has obvious limitations for true documents, but by saving with minimal formatting (for instance, line feeds only at the end of paragraphs), it imports easily back into any word processor for reformatting as needed. So I encourage people to save any copies of any enduring documents in text format, regardless of what other format they use.

    After ASCII, consider RTF (Rich Text Format) or HTML. Either of these are broadly supported, and will allow enough formatting for all but the most complex documents.

    Last on the list should be proprietary or relatively new standards. I cannot emphasize enough that, regardless of anything else, standards endure by popularity far more than technical merit. Lotus Word Pro 97 was a great example. Because of its limited sales and use, new applications don’t see any need to support this format in their conversion modules.

    For more advanced software (spreadsheets, project management, databases, etc.), as much as it hurts to say this, users with limited technical abilities may be best advised to go with Microsoft. They will pay more, but trust me, MS Word 2007 has no problems reading MS Word 97 (or older) documents.

    Finally, if an organization is far-sighted, they can save the money they would have spent on software and re-invest a small portion of it in open source software and periodic technical / operational reviews. Most churches are in far more danger of losing ten years of documents because they keep them on old computers with no backups than because of standards obsolescence.

  10. Byron

    I would like to convert our Church to open source, but what about accounting packages that require Microsoft. The Software developers have to support opensource also. Not just about sermons, Church is a big business and requires many programs to run on their computer systems.

  11. WMarkH

    Good points. However, this advice may not go far enough. As someone has pointed out, “The great thing about standards is that there are so many to choose from.” This applies in the open source arena as well. Sure, I might not have to “pay” for document conversion, but if a standard I depend on never really catches on and is decremented ten years from now, is my grandmother ready to do the software engineering necessary to convert those old documents?

    Whenever the opportunity arises, I try to educate users toward the principles of simplicity and proven endurance. For instance, ASCII is forever. It has obvious limitations for true documents, but by saving with minimal formatting (for instance, line feeds only at the end of paragraphs), it imports easily back into any word processor for reformatting as needed. So I encourage people to save any copies of any enduring documents in text format, regardless of what other format they use.

    After ASCII, consider RTF (Rich Text Format) or HTML. Either of these are broadly supported, and will allow enough formatting for all but the most complex documents.

    Last on the list should be proprietary or relatively new standards. I cannot emphasize enough that, regardless of anything else, standards endure by popularity far more than technical merit. Lotus Word Pro 97 was a great example. Because of its limited sales and use, new applications don’t see any need to support this format in their conversion modules.

    For more advanced software (spreadsheets, project management, databases, etc.), as much as it hurts to say this, users with limited technical abilities may be best advised to go with Microsoft. They will pay more, but trust me, MS Word 2007 has no problems reading MS Word 97 (or older) documents.

    Finally, if an organization is far-sighted, they can save the money they would have spent on software and re-invest a small portion of it in open source software and periodic technical / operational reviews. Most churches are in far more danger of losing ten years of documents because they keep them on old computers with no backups than because of standards obsolescence.

  12. Noel

    Here’s a church which has taken the “open” to their own content, allowing anyone to use what they create for free – how cool. http://open.lifechurch.tv/

  13. Noel

    Here’s a church which has taken the “open” to their own content, allowing anyone to use what they create for free – how cool. http://open.lifechurch.tv/

  14. Marco Fioretti

    The point that religious organizations have even more reasons than others has been already raised. Please check out:

    http://www.linux.com/feature/49533
    http://www.linux.com/feature/53644
    http://www.eleutheros.it (suggested reading: home page, manifesto and faq, in this order)

    I look forward to hear from you if there are further developments.

    Happy 2008,
    Marco Fioretti

  15. Marco Fioretti

    The point that religious organizations have even more reasons than others has been already raised. Please check out:

    http://www.linux.com/feature/49533
    http://www.linux.com/feature/53644
    http://www.eleutheros.it (suggested reading: home page, manifesto and faq, in this order)

    I look forward to hear from you if there are further developments.

    Happy 2008,
    Marco Fioretti

  16. D.C. Parris

    Here are some earlier thoughts on this theme:

    http://www.linuxjournal.com/article/7653
    http://www.linux.com/articles/38595
    http://searchenterpriselinux.techtarget.com/originalContent/0,289142,sid39_gci990899,00.html

    http://www.lulu.com/dcparris or
    http://matheteuo.org/download.php?view.1

    And, of course…
    http://matheteuo.org/download.php?view.2

    The book (PitP) points to a larger community of Christians geared toward fostering FOSS usage.

    Blessings,
    Don

  17. D.C. Parris

    Here are some earlier thoughts on this theme:

    http://www.linuxjournal.com/article/7653
    http://www.linux.com/articles/38595
    http://searchenterpriselinux.techtarget.com/originalContent/0,289142,sid39_gci990899,00.html

    http://www.lulu.com/dcparris or
    http://matheteuo.org/download.php?view.1

    And, of course…
    http://matheteuo.org/download.php?view.2

    The book (PitP) points to a larger community of Christians geared toward fostering FOSS usage.

    Blessings,
    Don

  18. Boycott Novell » OOXML: Forced Upgrades, Forced Obsolescence

    [...] Here is another serious complaint about this forced upgrade stunt, followed by some suggestions. The solution is simple: open standards. [...]

  19. ikaruga

    @Byron@ – there are various open-source softwares for accounting. For example: GNU-cash. (However, I don’t really use accounting software so I can’t recommend it.) If you unfortunately think of a church as a business, requiring professional quality software, there are various open-source (and both free and hi-quality) alternatives out there. For example, instead of PhotoShop, why not try the Gimp? There are also guides out in the web to help someone make the transition…

  20. ikaruga

    @Byron@ – there are various open-source softwares for accounting. For example: GNU-cash. (However, I don’t really use accounting software so I can’t recommend it.) If you unfortunately think of a church as a business, requiring professional quality software, there are various open-source (and both free and hi-quality) alternatives out there. For example, instead of PhotoShop, why not try the Gimp? There are also guides out in the web to help someone make the transition…

  21. Perché è importante usare standard aperti (ed essere contrari a OOXML) « Com’è dura la professione!

    [...] Perché è importante usare standard aperti (ed essere contrari a OOXML) Archiviato in: Microsoft, Open Source, cosi’ va il mondo — lbell @ 23:26 La fine del supporto a certi tipi di “vecchi” formati di file decretata da Microsoft, fa riflettere sull’utilità di impiegare formati proprietari per memorizzare i documenti. In un altro blog leggo che decine di documenti religiosi e scolastici a causa di questa decisione rischiano di essere perduti perché fra qualche tempo non esisteranno più programmi in grado di leggerli, mentre gli atti più vecchi scritti su carta possono essere tranquillamente consultati. [...]

  22. Why Open Source Software is like Church Coffee Beans » Ted Carnahan

    [...] « Three steps to Open Source in the Church [...]

  23. “Freedom Software” versus “Free Software” | Ted Carnahan

    [...] Three steps to Open Source in the Church [...]

  24. BE!

    Scott McCluskey mentioned your interest in open software and your background in programming as well as your participating in discussions about WTS computing. Keep up the good work. I have keen interest in open software. One area I find useful is web-based collaborative software and my current favorite is mindmeister.com which allows free limited usage for mapping on the web and links to freemind (among others). I have created a MM for open/free software. I will send you an invitation which allows you to contribute and modify the map. I would be interested in any additions you may have and also your classifying freedomware and freeware the various sites if you have time.
    I have yet to read all your blogs but I will be doing so.

  25. BE!

    Scott McCluskey mentioned your interest in open software and your background in programming as well as your participating in discussions about WTS computing. Keep up the good work. I have keen interest in open software. One area I find useful is web-based collaborative software and my current favorite is mindmeister.com which allows free limited usage for mapping on the web and links to freemind (among others). I have created a MM for open/free software. I will send you an invitation which allows you to contribute and modify the map. I would be interested in any additions you may have and also your classifying freedomware and freeware the various sites if you have time.
    I have yet to read all your blogs but I will be doing so.