Yesterday Robert Accettura made an interesting post about the range of SQlite today titled “The Winner For Most Embedded Is: SQLite.” This reminds me I’ve been wanting to talk about SQLite Consortium for a while. Robert points out thatSQLite is an element of “Adobe Air, Mozilla Prism, Google Gears, Android, iPhone SDK (likely through Core Data API), Ruby On Rails (default DB in 2.0), PHP 5 (bundled but disabled in PHP.ini by default).” I personally would probably say Firefox as well as Prism. In addition, SQLite is an open source (actually, public domain) piece of software. At Mozilla we view SQLite as important both for our product and for advancing transparency, openness, innovation and participation in the Internet.
Last December Symbian and Mozilla became the charter members of the SQLite Consortium. Last week Adobe announced that it has joined the SQLite Consortium, demonstrating Adobe’s recognition of the importance of Sqlite and its participation in various open source projects. Hopefully other organizations that rely on SQLite will do the same.
Here’s a bit more on the history.
A while back Richard Hipp contacted Mozilla to see if we had some time to talk to him about sustainability models. He had a problem we at Mozilla were familiar with — difficulty in getting organizations to fund the development of the core. At Mozilla we have seen this repeatedly — many companies understand why it’s important for them to fund development of the particular aspects of Mozilla that specifically benefit their business. It was much harder to find companies that would fund the core development applicable to all users of Mozilla code.
Dr. Hipp was facing the same issue with SQLite. Many companies were willing — eager even — to enter into contracts to enhance SQLite to meet their needs. But few were funding the fundamental core of the offering. I was embarrassed to learn that Mozilla itself belonged to this group. We had entered a contract with Dr. Hipp some time before to do some work related to full-text indexing support. I knew about this of course but it never occurred to me to ask if the SQLite developers needed funding to maintain the core capabilities. (I should note that Richard didn’t raise this point with us; I asked directly and thus learned of my failing ). Fortunately the folks at Symbian were more perceptive. They had realized that providing stability and sustainability for long term development of the core of SQLite is important and were talking with Richard about how to do this. As a result Richard contacted Mozilla to see if any of our experiences could help him with his thinking.
Once I got over my embarrassment I spent some time talking to Richard to understand his goals for SQLite and to see how best Mozilla could support Richard and SQLite. Richard was clear about the main goals: keeping SQLite an independent project, and freely available for anyone to use. On behalf of Mozilla I expressed a strong interest in the current developers (Richard and his colleague Dan Kennedy) retaining technical direction over the SQLite project and in developing a sustainability model that does not diminish the effectiveness of the technical leadership. The Symbian folks agreed completely, and Symbian and Mozilla became charter members of the Consortium, which was launched on December 12, 2007. The Consortium is described in general terms on the SQLite website, and the form of Consortium Agreement is also available online.
The Consortium Agreement makes it clear that technical direction of SQLite remains solely in the hands of the developers. Consortium members receive access to the developers for support if desired. I noted that Mozilla would join without the support offering solely to provide support to the core developers to do what they think best (and I suspect the other early members might feel the same way). Dr. Hipp felt that it would be easier to attract additional members over time if the support component was retained. I don’t know that Mozilla will make use of this. But I hope that other organizations that use SQLite in their products will find this significant enough to help justify participating in the Consortium.
Joining the Consortium was an easy decision for Mozilla. We use the technology, it advances the Mozilla mission and — most importantly — the SQLite developers themselves are people who combine a fierce dedication to the openness and technical excellence of their work with discipline and structure. Like many great open source (here, public domain) and free software projects, the key developers have enormous commitment to their work. In my discussions with Richard I’ve come to understand that this commitment is combined with integrity, modesty, and an exceptional consistency of focus and quality.
It’s great to see the SQLite Consortium come to life. It’s great to see this grow out of Symbian’s very forward-looking thinking in supporting Dr. Hipp so early on; and great to see Adobe’s quick decision to join the Consortium. And I certainly hope that other companies who aren’t already supporting SQLite development will look closely at keeping SQLite independent and vibrant by becoming Consortium members.
