A few weeks ago the government published a report on an $80 million (or thereabouts) project for the BC Ministry of Education on BCeSIS. The report recommends that will have to be scrapped in the coming years and replaced after about six years, with a new off the shelf proprietary system.
Some of the things that interested me in the report:
On open source:
Although some attempts have been initiated to develop K-12 Open Source SIS solutions, there does not appear to be any formal, structured funding mechanism and approach to designing and developing a solution which would meet the future needs of the BC education sector, nor to scale to the extent required to provide a single, province-wide student database.BCeSIS report
Damn open source can a pain like that without "formal, structured funding mechanisms".
The UI is mentioned as:
Current user satisfaction with BCeSIS is low, particularly with respect to the following: User interface, System response/availabilityBCeSIS report
I added a screenshot from this video to see how bad the UI is. True enterprise consulting software at it's best, $16 million eh?
Continuing with BCeSIS and evolving and supporting the BCeSIS solutionBCeSIS report page 21
a. Acquiring the source code for eSIS
That's right folks. BC spent $16 million and then $11 million on it a year. But it does not own the source to the project.
That probably doesn't surprise many people, I bet it's quite common. For me, on almost all projects I've worked on or managed, the subject of who owns the code has come up quickly in the process. The answers vary, but it's normally something like a non-exclusive license on both ends. I.e. as a developer I can re-use libraries I built of out it and as the client you can do what you like with it.
I do remember one meeting with a large government and business clients and I brought up the license to the code and was shot down quickly "of course the client owns the code". Silly me.
What if BCeSIS was open source?
Why would have BC not have asked the consulting company not to develop this as open source software from the get go? Let's just imagine if BCeSIS had been developed as open source.
- We wouldn't have to acquire the license to a system we paid for.
- Any vendor could work on the project allowing competitive bidding around the support of the project.
- Other governments, school districts or agencies might have picked up the project
- There might just be an open source eSIS project with a "formal, structured funding mechanism".
If it was open source, BCeSIS might just be moving forward as other jurisdictions might have picked it up. It might be cheaper and easier to maintain. It won't be any worse.
Why isn't the government open source by default?
Let's just play devils advocate here and see why a large project wouldn't do open source. And by open source, we mean the software developed for a project like BCeSIS. You can still have an open source project and use Oracle.
- The business needs and intellectual property moat. But, the government is not trying to defend a business model. The goal should be to get other jurisdictions to work on this project and get as much input as possible.
- Security. We know that security by obscurity is bogus. We aren't asking you to put the usernames or passwords to your database in the public, just code. We don't even want you to do something silly like copy sensitive production data downstream.
- There are legal ramifications. I think those have been pretty much resolved these days, if you chose an appropriate license.
- It's too much effort. If you are open by default, it actually becomes quite easy. Making things closed becomes the hard and painful part, it's amazing how quickly and easily it flips around.
- The consulting company won't let us. Then the government needs to dictate to the consulting companies or find other ones. There's plenty of them.
The conclusion from the report is that there a few vendors who can provide and off the shelf solution and it will be backed by Oracle, Microsoft or Java technology. I bet it won't be open source code.
It's not a simple "I can throw that together using Rails for 5k on a weekend" project. It could be accomplished with an open source software stack and it could be done with all the code being open source. And that would present a much brighter future for the software and for the poor teachers and admininstrators who have to suffer it.
The brief informal poll of exactly one teacher, my wife, when I told her of the scrapping of BCeSIS was "woohoo, it sucks". I hope the new one is better.