|
|
|
|
|
by MadnessASAP
644 days ago
|
|
The problem almost always comes down to how governments do procurement. In the name of fairness and preventing a variety of immoral acts it is extremely difficult for a government to point at an existing product and say "we'll take that". Instead they must create a list of requirements, debate said list of requirements, pass the list around various departments completely separated from the original procurement, and finally of you're lucky it'll be sent out for suppliers to bid on. Obviously any attempt, perceived or real, to write the requirements against an existing product will result in lawsuits.[1] The result is that the product almost always ends up being some bespoke pile of scraps built to a years old list of requirements that only vaguely aligns to the original problem. It's a market that requires extreme patience and a building full of lawyers, it's not something that many companies are interested in participating in directly and pretty much impossible for a open-source organization, not that they'd even want to. [1] I've watched a company dream-up a non-existent solution just so they could sue the government for an "unfair" competition and be compensated. I almost wish the courts had forced the government go with the imaginary product just to watch the company collapse trying to deliver something they had no intention of and would not be able to actually provide. |
|
The obvious solution here is for the town to give the open source software an initial try on their own, then include it in the requirements as a preexisting use. In any case, the bid and contract then is not for a new product but for integration instead.