Lessons from open source in the Mexican government

I found this part interesting:<p>&gt; González Waite said that all of the large proprietary software companies &quot;&quot;are big bullies&quot;&quot;. He has been called into the US embassy and been threatened because Mexico was using technology that was not from the US; those threats were dialed back when he explained that the government also used software and services from Amazon, Google, and Microsoft. Various companies use the US government to bully other countries, but they also use license audits as a reaction to projects that move to open-source software. Every time a successful switch happened, &quot;&quot;six months later there was an audit&quot;&quot;; having the right legal team helps defend against those tactics, he said.<p>It matches also what I heard from someone working for the Dutch government. He said that whenever they needed a new software system, that Microsoft would send multiple consultants for &quot;free&quot; which all could &quot;help&quot; the transition to a new service from Microsoft.

Economic network theory:<p>&quot;Economists who have studied the software industry concluded that the value of a software business is about equal to the total costs of its customers switching out to the competition; both are equal to the net present value of future payments from the customers to the software vendor. This means that an incumbent in a maturing market, such as Microsoft with its Office product, can grow faster than the market only if it can find ways to lock in its customers more tightly. There are some ifs and buts that hedge this theory around, but the basic idea is well known to software industry executives. This explains Bill G&#x27;s comment that `We came at this thinking about music, but then we realized that e-mail and documents were far more interesting domains&#x27;.&quot;

The article uses the phrase &quot;no brainer&quot; but then explains why it very much requires brainer when making IT decisions.<p>License costs are a factor, yes, but they are not the only cost, and in most cases not the significant one.<p>In some cases the offerings are similar enough that it moves the needle. PostgreSQL for example is a good candidate- Oracle is expensive, and the number of people interacting with it is limited. Plus the fundamentals of Oracle and PostgreSQL are more-or-less the same.<p>On the other extreme the cost of training and support dwarfs the license cost. If all staff come with knowing how to use say Windows and Excel,but require training and support for say Linux Desktop and Libre Office, then the &quot;free&quot; thing costs more.<p>It&#x27;s no accident that OSS has done better on the backend than the front end.<p>Success for OSS means putting the right product in the right place, taking all things (not just license cost) into account.<p>(Aside: corruption is a red herring, corrupt officials and companies can be corrupt regardless of software license.)

&gt; Another part of the project was to move away from Oracle and to PostgreSQL. That change led to various threats and intimidation from the company when it learned of the change, González Waite said. &quot;They told me that the entire passport system of the country was going to fall down&quot; and that it would be his fault that Mexico could not let anyone into or out of the country. &quot;Guess what? That didn&#x27;t happen.&quot;<p>Larry Ellison, never change. It&#x27;ll be interesting to see how they ruin TikTok if their bid succeeds.

I think at this moment all governments should start funding the open source foundations so that the foundations can train as well as retain good programming talent to keep the important open source software maintained. I think it will serve better in the long term to the government departments as well as the citizens.

This was a pleasant and encouraging article to read.<p>I do think that open source is slowly growing in traditional enterprises, although I think recent interest in cloud computing and artificial intelligence has pushed a lot of software contracting out of the company. Open source migrations might become harder in the future when the enterprise no longer controls their own databases and models.

My slogan for using FOSS for govt is &quot;citizen owned software&quot;.<p>At one time, I anticipated the rise of FOSS consortiums. Jurisdictions with similar needs would join together to share the cost and risks.<p>Canada, Mexico, USA each have 1,000s of juridictions. Surely at any one time there&#x27;s a handful planning a technology refresh of some domain.<p>One easy example I know of is property tax administration. There&#x27;s a bunch of counties of similar size all doing the same thing, but all running off in separate directions. Vendor options are complicated, expensive, and have lock-in. Surely it&#x27;d be beneficial to pool their resources and own their stack?<p>Another is election administration. US counties used to do all it themselves. Candidate filings, voter registration, poll books, yadda, yadda. Now it&#x27;s all outsourced. Lower service for higher prices. (The &quot;certification&quot; process was captured, serving to protect incumbents. Natch.)<p>Any way.<p>I was a grunt for a member of a consortium FOSS project. It was awful. &quot;The Logic of Collective Action&quot; explained a great deal of the pathology. Also, Byran Cantrill&#x27;s quote (wrt Open Solaris) about &quot;having the freedom but not the power to fork&quot; was spot on for our project.<p>Any way.<p>Does any one have examples or game plan or vision for realizing more FOSS in govt? I&#x27;m not quite ready to give up on the dream.

&gt; It turned out that various contracted companies had corruptly put the software licenses they bought for the government into their own names, leading to a lock-in for their services.<p>This is a dirty trick I ran into in [US] state procurement, in a state known for widespread corruption. It&#x27;s basically a no-show job where you just hold a bunch of long-term contracts for the state, and claim a monthly &quot;support&quot; fee for doing it. Even worse, you got to negotiate those contracts (and set up your kickbacks or self-dealing.) Bonus points for needing to call the contractor in order to have the contractor call support, and the contractor taking a fee for doing it.<p>Endless avenues for corruption with a setup like this.

Damn. I was aware US technology companies were parasitic, but this article really sheds light on the extent of it. No wonder they hate free software so much.

&gt; The team took advantage of the shift to restructure the database &quot;because we found that our storage provider was being a little bit naughty&quot;, storing the data three or four times in order to charge more money.<p>This is the worst kind of graft and should result in criminal charges. The software development industry is still in a nascent stage and our tools are great but professional standards are still undeveloped.<p>&gt; Technology is often seen as the problem, he said, but he generally found that the problems were due to using obsolete technology and a lack of knowledge about the data being handled. There is often no documentation of the data and its structure, coupled with no understanding of that by the people in charge of it. Poor leadership in the agencies is another barrier; there needs to be a champion for a change of this sort, who understands what needs to be done and properly assigns people to work on it.<p>Oh. Well. Precisely.

Question I ask my self a lot, how much my government spends a month for Microsoft stuff. This money could go to education and health care, which both are in terrible shape. Friend who works for government tell me that it’s almost impossible to find out this number. That’s how “transparent” it is.

I live near the Pasadena&#x2F;LA area and wish I had heard of SCALE22x earlier!

&gt; The team took advantage of the shift to restructure the database &quot;&quot;because we found that our storage provider was being a little bit naughty&quot;&quot;, storing the data three or four times in order to charge more money<p>Uh... Without knowing the exact details, my first thought that &quot;a little knowledge is a dangerous thing&quot;