~drizzle-trunk/drizzle/development : contents of docs/brief_history_of

~drizzle-trunk/drizzle/development : (revision 2350)

==========================
A Brief History Of Drizzle
==========================

Drizzle came into being for both social and technical reasons.

The Drizzle project began in 2008 when Brian Aker forked it from
MySQL, following Sun Microsystems' acquisition of MySQL. The Drizzle
project was announced in 2008 at the O'Reilly OSCOn Open Source
Conference.

In terms of technical goals, Drizzle is based on a micro-kernel design
that aims to be as pluggable as possible. Anyone should be able to
quickly extend the database for their database needs. Drizzle has been
designed for modern architectures and deployments. Drizzle does not
shy away from breaking with the past, many of the MySQL "Gotchas"
(features that work as advertised but not necessarily as expected)
have been removed.

Drizzle is open source software, designed in an organic manner by
developers that span different companies. The development process has
been geared to be more similar to the Linux Kernel where no single
company owns the source code, or provides all of the developers. In
stark difference to MySQL, the goal is to be as inclusive as possible
and provide stable releases. The social charter of Drizzle encourages
diversity and prizes respectful dialogue between all participating
parties.

Drizzle today is the most active fork of the MySQL server. At the time
of writing, core developers span five companies, with as many, and
sometimes more then, 30+ developers participating each month. Drizzle
provides releases every other week and is the most well-tested
database in the MySQL family tree.

More narrative on the project can be found on
`Wikipedia <http://en.wikipedia.org/wiki/Drizzle_(database_server)>`_

1900.2.3 by Stewart Smith fix docs warning: Title underline (and overline) is too short in brief_history_of_drizzle.rst	1	==========================
1838.2.1 by Brian Aker More docs.	2	A Brief History Of Drizzle
1900.2.3 by Stewart Smith fix docs warning: Title underline (and overline) is too short in brief_history_of_drizzle.rst	3	==========================
1838.2.1 by Brian Aker More docs.	4
	5	Drizzle came into being for both social and technical reasons.
	6
2222.2.1 by Mark Atwood documentation work	7	The Drizzle project began in 2008 when Brian Aker forked it from
	8	MySQL, following Sun Microsystems' acquisition of MySQL. The Drizzle
	9	project was announced in 2008 at the O'Reilly OSCOn Open Source
	10	Conference.
	11
	12	In terms of technical goals, Drizzle is based on a micro-kernel design
	13	that aims to be as pluggable as possible. Anyone should be able to
	14	quickly extend the database for their database needs. Drizzle has been
	15	designed for modern architectures and deployments. Drizzle does not
	16	shy away from breaking with the past, many of the MySQL "Gotchas"
	17	(features that work as advertised but not necessarily as expected)
	18	have been removed.
	19
	20	Drizzle is open source software, designed in an organic manner by
	21	developers that span different companies. The development process has
	22	been geared to be more similar to the Linux Kernel where no single
	23	company owns the source code, or provides all of the developers. In
	24	stark difference to MySQL, the goal is to be as inclusive as possible
	25	and provide stable releases. The social charter of Drizzle encourages
	26	diversity and prizes respectful dialogue between all participating
	27	parties.
	28
	29	Drizzle today is the most active fork of the MySQL server. At the time
	30	of writing, core developers span five companies, with as many, and
	31	sometimes more then, 30+ developers participating each month. Drizzle
	32	provides releases every other week and is the most well-tested
	33	database in the MySQL family tree.
	34
	35	More narrative on the project can be found on
	36	`Wikipedia <http://en.wikipedia.org/wiki/Drizzle_(database_server)>`_