Debian Codegraph @

www/consortium.html

raw
1 <!DOCTYPE html>
2 <html><head>
3 <meta name="viewport" content="width=device-width, initial-scale=1.0">
4 <meta http-equiv="content-type" content="text/html; charset=UTF-8">
5 <link href="sqlite.css" rel="stylesheet">
6 <title>SQLite Consortium</title>
7 <!-- path= -->
8 </head>
9 <body>
10 <div class=nosearch>
11 <a href="index.html">
12 <img class="logo" src="images/sqlite370_banner.svg" alt="SQLite" border="0">
13 </a>
14 <div><!-- IE hack to prevent disappearing logo --></div>
15 <div class="tagline desktoponly">
16 Small. Fast. Reliable.<br>Choose any three.
17 </div>
18 <div class="menu mainmenu">
19 <ul>
20 <li><a href="index.html">Home</a>
21 <li class='mobileonly'><a href="javascript:void(0)" onclick='toggle_div("submenu")'>Menu</a>
22 <li class='wideonly'><a href='about.html'>About</a>
23 <li class='desktoponly'><a href="docs.html">Documentation</a>
24 <li class='desktoponly'><a href="download.html">Download</a>
25 <li class='wideonly'><a href='copyright.html'>License</a>
26 <li class='desktoponly'><a href="support.html">Support</a>
27 <li class='desktoponly'><a href="prosupport.html">Purchase</a>
28 <li class='search' id='search_menubutton'>
29 <a href="javascript:void(0)" onclick='toggle_search()'>Search</a>
30 </ul>
31 </div>
32 <div class="menu submenu" id="submenu">
33 <ul>
34 <li><a href='about.html'>About</a>
35 <li><a href='docs.html'>Documentation</a>
36 <li><a href='download.html'>Download</a>
37 <li><a href='support.html'>Support</a>
38 <li><a href='prosupport.html'>Purchase</a>
39 </ul>
40 </div>
41 <div class="searchmenu" id="searchmenu">
42 <form method="GET" action="search">
43 <select name="s" id="searchtype">
44 <option value="d">Search Documentation</option>
45 <option value="c">Search Changelog</option>
46 </select>
47 <input type="text" name="q" id="searchbox" value="">
48 <input type="submit" value="Go">
49 </form>
50 </div>
51 </div>
52 <script>
53 function toggle_div(nm) {
54 var w = document.getElementById(nm);
55 if( w.style.display=="block" ){
56 w.style.display = "none";
57 }else{
58 w.style.display = "block";
59 }
60 }
61 function toggle_search() {
62 var w = document.getElementById("searchmenu");
63 if( w.style.display=="block" ){
64 w.style.display = "none";
65 } else {
66 w.style.display = "block";
67 setTimeout(function(){
68 document.getElementById("searchbox").focus()
69 }, 30);
70 }
71 }
72 function div_off(nm){document.getElementById(nm).style.display="none";}
73 window.onbeforeunload = function(e){div_off("submenu");}
74 /* Disable the Search feature if we are not operating from CGI, since */
75 /* Search is accomplished using CGI and will not work without it. */
76 if( !location.origin || !location.origin.match || !location.origin.match(/http/) ){
77 document.getElementById("search_menubutton").style.display = "none";
78 }
79 /* Used by the Hide/Show button beside syntax diagrams, to toggle the */
80 function hideorshow(btn,obj){
81 var x = document.getElementById(obj);
82 var b = document.getElementById(btn);
83 if( x.style.display!='none' ){
84 x.style.display = 'none';
85 b.innerHTML='show';
86 }else{
87 x.style.display = '';
88 b.innerHTML='hide';
89 }
90 return false;
91 }
92 var antiRobot = 0;
93 function antiRobotGo(){
94 if( antiRobot!=3 ) return;
95 antiRobot = 7;
96 var j = document.getElementById("mtimelink");
97 if(j && j.hasAttribute("data-href")) j.href=j.getAttribute("data-href");
98 }
99 function antiRobotDefense(){
100 document.body.onmousedown=function(){
101 antiRobot |= 2;
102 antiRobotGo();
103 document.body.onmousedown=null;
104 }
105 document.body.onmousemove=function(){
106 antiRobot |= 2;
107 antiRobotGo();
108 document.body.onmousemove=null;
109 }
110 setTimeout(function(){
111 antiRobot |= 1;
112 antiRobotGo();
113 }, 100)
114 antiRobotGo();
115 }
116 antiRobotDefense();
117 </script>
118
119
120
121 <h1 align=center>The SQLite Consortium</h1>
122
123 <p>
124 The SQLite Consortium is a membership association dedicated to
125 insuring the continuing vitality and independence of SQLite.
126 SQLite is high-quality, public domain software. The goal of
127 the SQLite Consortium is to make sure it stays that way.
128 </p>
129
130 <p>
131 Consortium members contribute funding to support the ongoing
132 development and maintenance of SQLite and in return receive
133 enterprise-level technical support and legal assurances that
134 SQLite will remain independent and open-source. Consortium
135 members have direct access to
136 the SQLite developers and receive priority consideration for
137 any bug fixes or feature requests. However, technical control
138 and direction of SQLite remains with the SQLite architect and
139 developers. An important goal of the SQLite Consortium, after
140 all, is to make sure that SQLite does not fall under the governance
141 of any single company but remains independent and fully under the
142 control of the SQLite developers.
143 </p>
144
145 <p>
146 Companies that use SQLite as a critical component in their
147 products or infrastructure may want to consider becoming
148 SQLite Consortium Members as inexpensive insurance
149 in the future vitality and independence of SQLite. The SQLite Consortium
150 membership fee is a fraction of the cost of devoting internal
151 staff to supporting the SQLite code base. Benefits of
152 membership include:
153 </p>
154
155 <ul>
156 <li><p>
157 Consortium members have the guaranteed, undivided attention of the SQLite
158 developers for 23 staff-days per year and for as much additional time
159 above and beyond that amount that the core developers have available.
160 There are no arbitrary limits on contact time.
161 The consortium will never be over-subscribed. New SQLite developers
162 will be recruited and trained as necessary to cover the 23 day/year
163 support commitment.
164 </p></li>
165
166 <li><p>
167 Consortium members can call any developer at any time, day or
168 night, and expect to get their full and immediate attention.
169 Consortium members have access to the home telephone numbers
170 and cellphone numbers and work schedules of the core developers
171 so that the developers can be tracked down quickly in a crisis.
172 </p></li>
173
174 <li><p>
175 The SQLite developers are eager and happy to write new code
176 or debug existing code for consortium members.
177 Consortium members can request and expect to receive significant
178 new enhancements to the public SQLite code base. Consortium
179 members can also request their own private, proprietary extensions
180 and enhancements.
181 </p></li>
182
183 <li><p>
184 Consortium members can receive support for any
185 version of SQLite no matter how old.
186 Bug fixes will be back ported to older versions of SQLite upon
187 request.
188 </p></li>
189
190 <li><p>
191 Consortium members can receive private
192 email and/or telephone notifications and briefings covering
193 new bugs or recently added features.
194 The core developers are constantly watching out for the
195 interests of consortium members and will attempt to protect
196 those interests in every way possible and alert members
197 when their interests are threatened in any way.
198 </p></li>
199
200 <li><p>
201 The SQLite developers will set up customized regression tests
202 to fully and completely test SQLite as configured by consortium
203 members. Normally, only the standard SQLite configuration is fully
204 tested at each release. Consortium members that use a non-standard
205 configuration can request that their configuration be tested to the
206 same level of detail.
207 </p></li>
208
209 <li><p>
210 Support requests are accepted from any employee or contractor working
211 for a consortium member.
212 Support is not limited to a single development
213 team as it is with a maintenance subscription or technical support
214 agreement.
215 </p></li>
216
217 <li><p>
218 Support requests, comments, and suggestions for future
219 changes to SQLite coming from consortium members take priority
220 over requests from all other sources.
221 Consortium members go to the front of the line.
222 </p></li>
223
224 <li><p>
225 We will be happy to
226 <a href="index.html#sponsors">recognize consortium members</a>
227 on the SQLite website
228 with a logo and/or a brief acknowledgement of their contribution to the
229 project. This is an opportunity for companies to build good will by
230 demonstrating that they are giving back to the community. Or, members
231 can remain anonymous.
232 </p></li>
233
234 </ul>
235
236
237 <h2>How To Become A Consortium Member</h2>
238
239 <p>
240 Membership in the SQLite Consortium is via
241 contract with <a href="https://www.hwaci.com/">Hipp, Wyrick &amp; Company, Inc.</a>.
242 Send email to <a href="mailto:[email protected]">[email protected]</a> or phone
243 +1.704.948.4565 during US east-coast business hours
244 for additional information.
245 </p>
246
247
248
249 </body></html>
250 <p align="center"><small><i>This page was last updated on 2026-02-24 23:35:46Z </small></i></p>
251