I bought a car by sending out a document and evaluating salespeople’s written responses

Actually I didn’t because that would be an utterly ridiculous way to buy I car. The last time I bought one, I looked at it, I test drove it, I got a mechanic to look at it. You can do all of these things with Free and Open Source software, including getting a good look at the engine. This is much harder and sometimes not even possible with proprietary software. So why would you use an RFP process to purchase software, when you have the opportunity to actually evaluate it in a meaningful way instead.

If you are hoping for me to have an answer to this I am afraid I don’t. What I do know is that a typical RFP process discriminates against Free and Open Source software, mostly because we can’t lie. I am not saying that I know for sure proprietary ILS vendors lie, (although there are documented cases of their employees lying about Open Source before) but if people can’t see your code, you can say it does whatever you like. When talking about Koha, there isn’t this option. The code is there for everyone to see, the bugs are logged publicly, we have publicly archived lists, publicly logged IRC channels. What you see is exactly what you get, we can’t say “Koha will make your coffee” because you can check if that is true or not. So I guess this is a long winded way of saying, choose Free and Open Source software … we can’t lie to you.

Posted on November 21, 2012 at 8:08 pm by Chris · Permalink
In: Koha · Tagged with: ,

6 Responses

Subscribe to comments via RSS

  1. Written by Chabanon
    on November 21, 2012 at 9:58 pm
    Permalink

    Very nice wording !
    Thanks to you, we highly appreciate !
    Chab

  2. Written by Nate
    on November 22, 2012 at 4:54 am
    Permalink

    LOVE this post.

  3. […] commentary on RFPs I wanted to share this post originally posted by Chris Cormack on Korerorero with you all because we couldn’t agree […]

  4. Written by Gbengaadara
    on November 22, 2012 at 8:33 am
    Permalink

    Very nice.

  5. Written by Stu
    on November 22, 2012 at 8:59 am
    Permalink

    How exactly does being able to see the code affect an RFP response, or even the evaluation of the RFP response. The written responses are important as it allows you to shortlist based on functionality, and then a decent evaluation will actually look at the running product in a proof of concept to verify the statements. They won’t look at the code, they’ll look at the execution of the product. It doesn’t matter at all whether the code is open or closed, all that matters is “does it fit our requirements?”

    • Written by Chris
      on November 22, 2012 at 9:53 am
      Permalink

      Exactly, they will read written statements, base a shortlist on that, then trial something without looking under the hood.

Subscribe to comments via RSS