1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
3
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
4
<title>SQLite Consortium</title>
5
<style type="text/css">
8
font-family: Verdana, sans-serif;
13
a:visited { color: #734559 }
15
.logo { position:absolute; margin:3px; }
31
.toolbar a { color: white; text-decoration: none; padding: 6px 12px; }
32
.toolbar a:visited { color: white; }
33
.toolbar a:hover { color: #044a64; background: white; }
35
.content { margin: 5%; }
36
.content dt { font-weight:bold; }
37
.content dd { margin-bottom: 25px; margin-left:20%; }
38
.content ul { padding:0px; padding-left: 15px; margin:0px; }
41
.se { background: url(images/se.gif) 100% 100% no-repeat #044a64}
42
.sw { background: url(images/sw.gif) 0% 100% no-repeat }
43
.ne { background: url(images/ne.gif) 100% 0% no-repeat }
44
.nw { background: url(images/nw.gif) 0% 0% no-repeat }
46
/* Things for "fancyformat" documents start here. */
47
.fancy img+p {font-style:italic}
48
.fancy .codeblock i { color: darkblue; }
49
.fancy h1,.fancy h2,.fancy h3,.fancy h4 {font-weight:normal;color:#044a64}
50
.fancy h2 { margin-left: 10px }
51
.fancy h3 { margin-left: 20px }
52
.fancy h4 { margin-left: 30px }
53
.fancy th {white-space:nowrap;text-align:left;border-bottom:solid 1px #444}
54
.fancy th, .fancy td {padding: 0.2em 1ex; vertical-align:top}
55
.fancy #toc a { color: darkblue ; text-decoration: none }
56
.fancy .todo { color: #AA3333 ; font-style : italic }
57
.fancy .todo:before { content: 'TODO:' }
58
.fancy p.todo { border: solid #AA3333 1px; padding: 1ex }
59
.fancy img { display:block; }
60
.fancy :link:hover, .fancy :visited:hover { background: wheat }
61
.fancy p,.fancy ul,.fancy ol { margin: 1em 5ex }
62
.fancy li p { margin: 1em 0 }
63
/* End of "fancyformat" specific rules. */
69
<div><!-- container div to satisfy validator -->
72
<img class="logo" src="images/sqlite370_banner.gif" alt="SQLite Logo"
74
<div><!-- IE hack to prevent disappearing logo--></div>
75
<div class="tagline">Small. Fast. Reliable.<br>Choose any three.</div>
77
<table width=100% style="clear:both"><tr><td>
78
<div class="se"><div class="sw"><div class="ne"><div class="nw">
79
<table width=100% style="padding:0;margin:0;cell-spacing:0"><tr>
82
<a href="about.html">About</a>
83
<a href="sitemap.html">Sitemap</a>
84
<a href="docs.html">Documentation</a>
85
<a href="download.html">Download</a>
86
<a href="copyright.html">License</a>
87
<a href="news.html">News</a>
88
<a href="support.html">Support</a>
91
gMsg = "Search SQLite Docs..."
92
function entersearch() {
93
var q = document.getElementById("q");
94
if( q.value == gMsg ) { q.value = "" }
95
q.style.color = "black"
96
q.style.fontStyle = "normal"
98
function leavesearch() {
99
var q = document.getElementById("q");
100
if( q.value == "" ) {
102
q.style.color = "#044a64"
103
q.style.fontStyle = "italic"
108
<div style="padding:0 1em 0px 0;white-space:nowrap">
109
<form name=f method="GET" action="http://www.sqlite.org/search">
110
<input id=q name=q type=text
111
onfocus="entersearch()" onblur="leavesearch()" style="width:24ex;padding:1px 1ex; border:solid white 1px; font-size:0.9em ; font-style:italic;color:#044a64;" value="Search SQLite Docs...">
112
<input type=submit value="Go" style="border:solid white 1px;background-color:#044a64;color:white;font-size:0.9em;padding:0 1ex">
116
</div></div></div></div>
118
<div class=startsearch></div>
123
<h1 align=center>The SQLite Consortium</h1>
126
The SQLite Consortium is a membership association dedicated to
127
insuring the continuing vitality and independence of SQLite.
128
SQLite is high-quality, public domain software. The goal of
129
the SQLite Consortium is to make sure it stays that way.
133
Consortium members contribute funding to support the ongoing
134
development and maintenance of SQLite and in return receive
135
enterprise-level technical support and legal assurances that
136
SQLite will remain independent and open-source. Consortium
137
members have direct access to
138
the SQLite developers and receive priority consideration for
139
any bug fixes or feature requests. However, technical control
140
and direction of SQLite remains with the SQLite architect and
141
developers. An important goal of the SQLite Consortium, after
142
all, is to make sure that SQLite does not fall under the governance
143
of any single company but remains independent and fully under the
144
control of the SQLite developers.
148
Companies that use SQLite as a critical component in their
149
products or infrastructure may want to consider becoming
150
SQLite Consortium Members as inexpensive insurance
151
in the future vitality and independence of SQLite. The SQLite Consortium
152
membership fee is a fraction of the cost of devoting internal
153
staff to supporting the SQLite code base. Benefits of
159
Consortium members have the guaranteed, undivided attention of the SQLite
160
developers for 23 staff-days per year and for as much additional time
161
above and beyond that amount that the core developers have available.
162
There are no arbitrary limits on contact time.
163
The consortium will never be over-subscribed. New SQLite developers
164
will be recruited and trained as necessary to cover the 23 day/year
169
Consortium members can call any developer at any time, day or
170
night, and expect to get their full and immediate attention.
171
Consortium members have access to the home telephone numbers
172
and cellphone numbers and work schedules of the core developers
173
so that the developers can be tracked down quickly in a crisis.
177
The SQLite developers are eager and happy to write new code
178
or debug existing code for consortium members.
179
Consortium members can request and expect to receive significant
180
new enhancements to the public SQLite code base. Consortium
181
members can also request their own private, proprietary extensions
186
Consortium members can receive support for any
187
version of SQLite no matter how old.
188
Bug fixes will be back ported to older versions of SQLite upon
193
Consortium members can receive private
194
email and/or telephone notifications and briefings covering
195
new bugs or recently added features.
196
The core developers are constantly watching out for the
197
interests of consortium members and will attempt to protect
198
those interests in every way possible and alert members
199
when their interests are threatened in any way.
203
The SQLite developers will set up customized regression tests
204
to fully and completely test SQLite as configured by consortium
205
members. Normally, only the standard SQLite configuration is fully
206
tested at each release. Consortium members that use a non-standard
207
configuration can request that their configuration be tested to the
208
same level of detail.
212
Support requests are accepted from any employee or contractor working
213
for a consortium member.
214
Support is not limited to a single development
215
team as it is with a maintenance subscription or technical support
220
Support requests, comments, and suggestions for future
221
changes to SQLite coming from consortium members take priority
222
over requests from all other sources.
223
Consortium members go to the front of the line.
228
<a href="index.html#consortium_members">recognize consortium members</a>
229
on the SQLite website
230
with a logo and/or a brief acknowledgement of their contribution to the
231
project. This is an opportunity for companies to build good will by
232
demonstrating that they are giving back to the community. Or, members
233
can remain anonymous.
239
<h2>How To Become A Consortium Member</h2>
242
Membership in the SQLite Consortium is via
243
<a href="consortium_agreement-20071201.html">contract</a> with
244
<a href="http://www.hwaci.com/">Hipp, Wyrick & Company, Inc.</a>.
245
Please call +1.704.948.4565 during US east-coast business hours
246
for additional information.
added
removed
consortium.html
