LSARC/2008/059 - SQLite

[Darren J Moffat]

John Plocher wrote:

> Contract or not, since your team is putting it into Solaris, you
> are already committed to work with them to help avoid problems
> on the upgrade.  Changing Committed to Contracted Volatile doesn't
> actually change the amount and type of work that you already are
> going to need to perform...

Speaking from experience with OpenSSL a Contracted interface has a 
HIGHER burden on the supplier because they not only does the supplier 
need to do the analysis on wither and when to upgrade they also need to 
work with the contractees.  It also brings in a management and ARC 
member burden to sign all the new contracts.

For something that does not have a stable ABI and API, like OpenSSL, it 
might almost be worth it (I'm starting to doubt even that for OpenSSL 
now though); however for something that is known to be very stable and 
has explicit goals and past history in this area, like SQLite, Volatile 
and thus ARC contracts are an added and unnecessary burden on consumers.

If SQLite is Volatile then I'll expect a contract between Firefox 3.x 
and SQLite and that IIRC becomes a contract where (currently) the 
supplying and consuming manager are the same person (and should start to 
show the overhead of this).

"Simplify our business"

-- 
Darren J Moffat