Open Source Gospel Project
Contents
Outline
- Free as in Freedom
- Code as Architecture
- The Cathedral and the Bazaar
- Soft Security vs. Hard Security
- Benevolent Dictator For Life
- Forking a Project (reform & reconciliation)
- Viral Copyleft (great commision)
Preface
I am neither a trained theologian, nor a professional computer programmer. But this is altogether fitting, considering the subject of this book. Despite Martin Luther's proclamation of the "priesthood of all believers," the modern church (Protestant, Catholic, and Orthodox) has been dominated by elite professionals, properly credentialed by seminaries, bible colleges, and ministry training programs. Only in the emerging post-modern movement are the doors finally being thrown open to armchair theologians and amateur church planters. Perhaps this is in part of neccessity due to declining overall participation in institutional churches, and a decline in
Free Software Methodists, Open Source Baptists & FLOSS Presbyterians
I remember the first time I read the wikipedia entry for "emerging church." It was well written, balanced and thoughtful, and I was excited about the passion and harmony reflected among the words. And then I clicked on the link to the discussion page.
Contributors were squabbling over word choice, calling each other ugly names, threatening to erase each other's work, and generally making a huge deal about a 1,000 word encyclopedia article. And I thought, "Ahhh. Finally, here is the church I know.
Things aren't so different in open-source culture. In fact, the name "open source" is probably one of the longest running disputes and dividing lines. Coined in 1998 by ___, it was a deliberate break from the older term "Free Software."
