Have a volunteer question...

[Megra]

Along these same lines, I am wondering about those of you who work with a team of volunteers.

I have an AMAZING team of guys, all database/programmers types (which I am not!) who are just thrilled to be a part of the churches web team. While I do have certain guidelines for us to work with, one of our greatest challenges is working with their strengths and how it can fit into what our plans are.

Here is the dilemna I have - most of my team are true blue Cold Fusion guys. They are adament about using Cold Fusion, and it's the main language they know. However, there are a few of them who love PHP and would love to contribute their PHP skills. We have been throwing around the idea of having a mixed environment, using both languages. Which I know can be done, but my questions is, is this a good plan for the future?

I'm divided between wanting to stay with the same language but I also want to be somewhat flexible with my volunteers. Have any of you run into this problem and what did you do to solve it?

Thanks!

[mrbelfry]

Hi Megra

I kind of work on the website solo so I can't really comment on getting the team to work together altough I think your desire is great. Getting everything working to their strengths and what they are good at is a great way to ensure job satisfaction.

I am a big php fan so I may be biased but I think trying to mix the environments is gonna over complicate things. What if you need to fix some php but there are only coldfusion guys around? In the past I've sometimes used other people's php scripts to add to my site and having to have separate admin passwords etc was a proper nightmare. I personally would definitely recommend sticking to one or the other. I think it would also be great for your coldfusion guys to teach that to the php bods and vice versa so everyone benefits. Why not have the site in one language but maybe develop projects in the other language so that everyone keeps interested?

Just my 2 pennies worth although I'd hate to think you'd make a decision based on the opinion of some dope in a whole other country ;-)

[iamcam]

One thing to also consider is that PHP is FOSS (free open source software). It will be much easier to find various help resources for PHP than ColdFusion (one look at hotscripts.com shows just under 12,000 items for PHP vs just under 300 for CF).

PHP is also pretty easy to pick up, especially for people who are already familiar with another programming language. Plus, one thing to consider is what happens when people on your team leave and others come in? It's probably more likely new people will have PHP experience.

[David Gillaspey]

Hi Megra,

<< but my questions is, is this a good plan for the future? >>

I'm going to have to agree with Cameron.

ColdFusion is a powerful language, but in the long run, you'd be better off using the non-proprietary PHP.

Further, I'm unsure, but I'm guessing it to be so, that ColdFusion only runs on servers running ColdFusion server software, which will cost you more. By contrast, PHP and mySQL capabilities are widely available from hosters, usually without extra charge.

Sincerely,

David Gillaspey
President
Great Church Websites

[Megra]

Thanks everyone for all the input - it is a challenge to figure out what to do. PhP is most likely the way we will go, although I am trying to be somewhat flexible. We'll see how it goes.