Why do CFP use open source software?

• Every client has a unique view and requires a unique response; the open source environment offers the developer freedom to choose how the solutions are manipulated, so the client always gets the maximum return on time/investment.

This independent approach breaks free from the constraints of developing in more rigid environments. The open source developer community are constantly evolving code variants and pushing the boundaries further, keeping the build concepts fresh and exciting and the implementation process dynamic and robust.

In addition, using GPL licensed software means that you can avoid the pitfalls of the traditional software model that invites vendor lock in.

Open source software comes in many flavours:

• desktop software such as OpenOffice (the open source version of the Microsoft Office suite),
• whole operating systems (the many flavours of Linux, for example),
• software such as WordPress, designed to be a ‘blog in a box’, built on the popular (and open) PHP programming language

These all share 1 common theme: customization by others (you, me, them, anyone) is thoroughly encouraged.

In our build process, we look carefully at your business plan for the website or application that you want to build. Our wealth of experience in this field will make sure that we can guide you towards the correct plan to make sure your business is future proof.

Common pitfalls when using open source software is as follows:

• changing your business plan to meet the demands of the open source software

This inevitably means you aren’t, or only partly, solving the problem you set out to.

• chooosing the wrong open source project to utilise and develop

The lifecycle of a website or application build can sometimes outlast the open source effort that it was based on. Open source projects can be looked on as companies. In the same way as a company might go out of business, change hands or metamorph into something else, so do open source projects. Where do you go for support if this happens?

We only ever choose mature, proven open source projects that have a historical release record over years, and a solid developer base.

• taking a sledgehammer to crack a nut.

Just because the software is free doesn’t mean that it is the answer to all your problems. If you are building a website that will be largely static in the future, with few, if any updates, then why use a blog package (which will inevitably require maintenance) to build it?

On a sidenote, whitehouse.gov now runs Drupal