The future of futurechurch The futurechurch project as it is does not have a future In the article below I indicated that the future of this project was uncertain, and depended on a response from the Methodist Church to a new contract. Unfortunately the Methodist Church could not find a way to continue to support it. Structurally they just could not find a way of responding or relating to the project. I have not even had a response to my letter posted in December last year, in which time there has been three meetings.

In November last year i gave a presentation to Methodist Conference about the need for lighter more flexible structures to support innovation and change. It was well received, and if I had asked for a show of support for the project, I am sure I would have got it. Despite valuing its contribution, they seem content institutionally to watch it die. so now its my job to put it to sleep forever... or maybe not.

Jesus of Montreal as a metaphor for giving it another life: My aim is to find away of taking the website, some money, a network and a dream, and seeing if the bits, like the organs of Jesus of Montreal, can live again in another place, with another name, but with the same dream or hope. The futurechurch website is an excellent resource. The guts of it - it's data base for adding and deleting articles and groups could be transferred and rebranded for very little cost and could enhance many of your websites. There is also some $$ to share around.

Perhaps there is even someone who wants to take over the project as it is. Think Jesus of Montreal - how can the bits be helpful in a new body to keep a dream alive. Dream on. Let me know if this sparks something in you, I look forward to being in touch.

What now? Within a month or so, I hope we can have a final mailing to let you know what is happening with the project and what 'organs' have been saved and what next. If you do not want your name/email details handed over to anyone who might continue this networking, please let me know, and I will delete them from the data base.

More >>