There are a couple topics here. One is FileMaker Pro vs. Open source, and the other is how to develop FileMaker solutions and release them as open source projects. For the first topic, you can listen to the related episode on my podcast with Matt Petrowsky, FileMaker Talk.
It's the latter that I'm thinking about: Releasing FileMaker solutions to the world, for free, creating a community around the product, and integrating code from the members of the community into the master.
First off, FileMaker doesn't lend itself to this as well as other platforms, since all the code, layouts, scripts, reports, etc, are all in one file. This makes it harder to be modular. That said though, this is really primarily a philosophy decision, and I think it comes down to this in many cases:
A commercial company owns the code, but take nearly all the direction from the customers. An open source project makes the code public, so the customers themselves must become programmers. Neither approach is perfect, and each will be successful in the right set of circumstances.
Mostly, I'm interested in vertical market FileMaker solutions, so let's consider what it would look like in a relatively small community, where there are maybe 1000 potential organizations that will use the software. The economics are very different for software that is used by a million people.
No programmer works for free, and all models for development must compensate the people who do the work. In the commercial model, it's the owner of the code that pays the programmers. People who buy the software only have to make feature requests to make future versions better. In the open source model, each company that wants to improve the system must pay their own people to gain expertise in that technology, and to develop code for their version, and hopefully submit that code to the master so other customers (their competitors?) may also benefit.
I think this is a bit less likely to happen for a vertical market. For open source to be successful here, a large organization probably needs to fund the initial development, and may need to continue funding development over time. In this model, it looks quite a bit like a commercial product.
Both commercial and open source get funding from support, maintenance, training, etc. In the open source world, this is possibly the only source of funding. For commercial software, it's a small source at first, and becomes the primary source of funds as the company grows and matures.
These are some of my thoughts on the subject. I'd love to hear your comments.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment