diff options
author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-05-05 17:28:19 +0000 |
---|---|---|
committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-05-05 17:28:19 +0000 |
commit | 18657a960e125336f704ea058e25c27bd3900dcb (patch) | |
tree | 17b438b680ed45a996d7b59951e6aa34023783f2 /www/consortium.html | |
parent | Initial commit. (diff) | |
download | sqlite3-18657a960e125336f704ea058e25c27bd3900dcb.tar.xz sqlite3-18657a960e125336f704ea058e25c27bd3900dcb.zip |
Adding upstream version 3.40.1.upstream/3.40.1upstream
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'www/consortium.html')
-rw-r--r-- | www/consortium.html | 251 |
1 files changed, 251 insertions, 0 deletions
diff --git a/www/consortium.html b/www/consortium.html new file mode 100644 index 0000000..b028ab9 --- /dev/null +++ b/www/consortium.html @@ -0,0 +1,251 @@ +<!DOCTYPE html> +<html><head> +<meta name="viewport" content="width=device-width, initial-scale=1.0"> +<meta http-equiv="content-type" content="text/html; charset=UTF-8"> +<link href="sqlite.css" rel="stylesheet"> +<title>SQLite Consortium</title> +<!-- path= --> +</head> +<body> +<div class=nosearch> +<a href="index.html"> +<img class="logo" src="images/sqlite370_banner.gif" alt="SQLite" border="0"> +</a> +<div><!-- IE hack to prevent disappearing logo --></div> +<div class="tagline desktoponly"> +Small. Fast. Reliable.<br>Choose any three. +</div> +<div class="menu mainmenu"> +<ul> +<li><a href="index.html">Home</a> +<li class='mobileonly'><a href="javascript:void(0)" onclick='toggle_div("submenu")'>Menu</a> +<li class='wideonly'><a href='about.html'>About</a> +<li class='desktoponly'><a href="docs.html">Documentation</a> +<li class='desktoponly'><a href="download.html">Download</a> +<li class='wideonly'><a href='copyright.html'>License</a> +<li class='desktoponly'><a href="support.html">Support</a> +<li class='desktoponly'><a href="prosupport.html">Purchase</a> +<li class='search' id='search_menubutton'> +<a href="javascript:void(0)" onclick='toggle_search()'>Search</a> +</ul> +</div> +<div class="menu submenu" id="submenu"> +<ul> +<li><a href='about.html'>About</a> +<li><a href='docs.html'>Documentation</a> +<li><a href='download.html'>Download</a> +<li><a href='support.html'>Support</a> +<li><a href='prosupport.html'>Purchase</a> +</ul> +</div> +<div class="searchmenu" id="searchmenu"> +<form method="GET" action="search"> +<select name="s" id="searchtype"> +<option value="d">Search Documentation</option> +<option value="c">Search Changelog</option> +</select> +<input type="text" name="q" id="searchbox" value=""> +<input type="submit" value="Go"> +</form> +</div> +</div> +<script> +function toggle_div(nm) { +var w = document.getElementById(nm); +if( w.style.display=="block" ){ +w.style.display = "none"; +}else{ +w.style.display = "block"; +} +} +function toggle_search() { +var w = document.getElementById("searchmenu"); +if( w.style.display=="block" ){ +w.style.display = "none"; +} else { +w.style.display = "block"; +setTimeout(function(){ +document.getElementById("searchbox").focus() +}, 30); +} +} +function div_off(nm){document.getElementById(nm).style.display="none";} +window.onbeforeunload = function(e){div_off("submenu");} +/* Disable the Search feature if we are not operating from CGI, since */ +/* Search is accomplished using CGI and will not work without it. */ +if( !location.origin || !location.origin.match || !location.origin.match(/http/) ){ +document.getElementById("search_menubutton").style.display = "none"; +} +/* Used by the Hide/Show button beside syntax diagrams, to toggle the */ +function hideorshow(btn,obj){ +var x = document.getElementById(obj); +var b = document.getElementById(btn); +if( x.style.display!='none' ){ +x.style.display = 'none'; +b.innerHTML='show'; +}else{ +x.style.display = ''; +b.innerHTML='hide'; +} +return false; +} +var antiRobot = 0; +function antiRobotGo(){ +if( antiRobot!=3 ) return; +antiRobot = 7; +var j = document.getElementById("mtimelink"); +if(j && j.hasAttribute("data-href")) j.href=j.getAttribute("data-href"); +} +function antiRobotDefense(){ +document.body.onmousedown=function(){ +antiRobot |= 2; +antiRobotGo(); +document.body.onmousedown=null; +} +document.body.onmousemove=function(){ +antiRobot |= 2; +antiRobotGo(); +document.body.onmousemove=null; +} +setTimeout(function(){ +antiRobot |= 1; +antiRobotGo(); +}, 100) +antiRobotGo(); +} +antiRobotDefense(); +</script> + + + +<h1 align=center>The SQLite Consortium</h1> + +<p> +The SQLite Consortium is a membership association dedicated to +insuring the continuing vitality and independence of SQLite. +SQLite is high-quality, public domain software. The goal of +the SQLite Consortium is to make sure it stays that way. +</p> + +<p> +Consortium members contribute funding to support the ongoing +development and maintenance of SQLite and in return receive +enterprise-level technical support and legal assurances that +SQLite will remain independent and open-source. Consortium +members have direct access to +the SQLite developers and receive priority consideration for +any bug fixes or feature requests. However, technical control +and direction of SQLite remains with the SQLite architect and +developers. An important goal of the SQLite Consortium, after +all, is to make sure that SQLite does not fall under the governance +of any single company but remains independent and fully under the +control of the SQLite developers. +</p> + +<p> +Companies that use SQLite as a critical component in their +products or infrastructure may want to consider becoming +SQLite Consortium Members as inexpensive insurance +in the future vitality and independence of SQLite. The SQLite Consortium +membership fee is a fraction of the cost of devoting internal +staff to supporting the SQLite code base. Benefits of +membership include: +</p> + +<ul> +<li><p> +Consortium members have the guaranteed, undivided attention of the SQLite +developers for 23 staff-days per year and for as much additional time +above and beyond that amount that the core developers have available. +There are no arbitrary limits on contact time. +The consortium will never be over-subscribed. New SQLite developers +will be recruited and trained as necessary to cover the 23 day/year +support commitment. +</p></li> + +<li><p> +Consortium members can call any developer at any time, day or +night, and expect to get their full and immediate attention. +Consortium members have access to the home telephone numbers +and cellphone numbers and work schedules of the core developers +so that the developers can be tracked down quickly in a crisis. +</p></li> + +<li><p> +The SQLite developers are eager and happy to write new code +or debug existing code for consortium members. +Consortium members can request and expect to receive significant +new enhancements to the public SQLite code base. Consortium +members can also request their own private, proprietary extensions +and enhancements. +</p></li> + +<li><p> +Consortium members can receive support for any +version of SQLite no matter how old. +Bug fixes will be back ported to older versions of SQLite upon +request. +</p></li> + +<li><p> +Consortium members can receive private +email and/or telephone notifications and briefings covering +new bugs or recently added features. +The core developers are constantly watching out for the +interests of consortium members and will attempt to protect +those interests in every way possible and alert members +when their interests are threatened in any way. +</p></li> + +<li><p> +The SQLite developers will set up customized regression tests +to fully and completely test SQLite as configured by consortium +members. Normally, only the standard SQLite configuration is fully +tested at each release. Consortium members that use a non-standard +configuration can request that their configuration be tested to the +same level of detail. +</p></li> + +<li><p> +Support requests are accepted from any employee or contractor working +for a consortium member. +Support is not limited to a single development +team as it is with a maintenance subscription or technical support +agreement. +</p></li> + +<li><p> +Support requests, comments, and suggestions for future +changes to SQLite coming from consortium members take priority +over requests from all other sources. +Consortium members go to the front of the line. +</p></li> + +<li><p> +We will be happy to +<a href="index.html#consortium_members">recognize consortium members</a> + on the SQLite website +with a logo and/or a brief acknowledgement of their contribution to the +project. This is an opportunity for companies to build good will by +demonstrating that they are giving back to the community. Or, members +can remain anonymous. +</p></li> + +</ul> + + +<h2>How To Become A Consortium Member</h2> + +<p> +Membership in the SQLite Consortium is via +contract with <a href="https://www.hwaci.com/">Hipp, Wyrick & Company, Inc.</a>. +Send email to <a href="mailto:drh@sqlite.org">drh@sqlite.org</a> or phone ++1.704.948.4565 during US east-coast business hours +for additional information. +</p> + + + +</body></html> +<p align="center"><small><i>This page last modified on <a href="https://sqlite.org/docsrc/honeypot" id="mtimelink" data-href="https://sqlite.org/docsrc/finfo/pages/consortium.in?m=ad2c94214ceb26239">2020-08-28 15:34:44</a> UTC </small></i></p> + |