I think it’s occasionally interesting to look back at what people wrote about things while they were happening, especially after big changes (founder and CEO leaving, for example). Here’s a blog post from May of 2008, by Henrik Ingo and Ignacio Torres, about MySQL’s business model. No commentary — just the link.

One might have thought Microsoft was back rattling the patented software sabres against Linux and open source this week, reading some of the recent reports regarding Redmond’s patent infringement suit against automotive navigation and GPS player TomTom. However, upon further review, it seems that Microsoft is making a point to say that these suits are not aimed at the Linux OS or open source. In response to my own query, the company offered this:

First, to answer your earlier question on how the suit with TomTom involves the Linux Operating System, three of the infringed patents read on the Linux kernel as implemented by TomTom. However, open source software is not the focal point of this action. …

If you would like to contribute to MySQL development, you can read the relevant top-level page on the MySQL Forge.

This page has some useful links to various forms of contributing to MySQL, including contribution of code to MySQL. (The MySQL|Sun team have recently simplified some of these pages in order to make them more useful to community members and potential contributors.)

Note that after some simple paperwork submitted to Sun ("Sun Contributor Agreement" or "SCA"), any signatory can contribute to any Sun-sponsored …

If you would like to contribute to MySQL development, you can read the relevant top-level page on the MySQL Forge.

This page has some useful links to various forms of contributing to MySQL, including contribution of code to MySQL. (The MySQL|Sun team have recently simplified some of these pages in order to make them more useful to community members and potential contributors.)

Note that after some simple paperwork submitted to Sun ("Sun Contributor Agreement" or "SCA"), any signatory can contribute to any Sun-sponsored …

If you would like to contribute to MySQL development, you can read the relevant top-level page on the MySQL Forge.

This page has some useful links to various forms of contributing to MySQL, including contribution of code to MySQL. (The MySQL|Sun team have recently simplified some of these pages in order to make them more useful to community members and potential contributors.)

Note that after some simple paperwork submitted to Sun ("Sun Contributor Agreement" or "SCA"), any signatory can contribute to any Sun-sponsored …

Yesterday Sun introduced Glassfish Portfolio. Its a new stack of open source middleware products including Glassfish Enterprise Server, Glassfish ESB, Glassfish Web Space Server, and the new Glassfish Web Stack, which includes support for projects such as Tomcat, Memcached, Apache, PHP, Ruby and Python and a copy of MySQL Community.

It’s a pretty complete infrastructure stack. What it is not, however, is an integrated LAMP stack, despite Sun’s reference to it as such not once but twice on its press announcement.

Glassfish Portfolio runs on Linux of course, as well as Solaris, but it does not contain Linux (integrated or otherwise) or Linux services (although that is available …

I just got news that Marten Mickos, former MySQL CEO, is to depart Sun amid a reorganisation of its infrastructure and database business units. Don’t expect an announcement from Sun on this, but the news is confirmed.

It seems that Sun is combining its Software Infrastructure organization with its Database Group to form a unified open source product group under the leadership of Karen Tegan Padir, vice president of MySQL & Software Infrastructure.

Marten will be transitioning out of Sun by the end of the company’s (current) third quarter.

Marten’s departure is a big loss for Sun and follows quickly after the departures of Monty Widenius and …

There are some basic, golden rules when it comes to having a vibrant community of contributors.

The following are rules I have extracted and learned based on my experience managing and working with engineers actively involved and participating in the Apache/Derby, PostgreSQL and MySQL open-source communities. These rules are also based on extensive discussions with many folks involved with the MySQL community, with the PostgreSQL community and with the Apache/Derby (Java DB) community, over many years.

Before I go through these rules, I would like to thank Marten Mickos for having suggested some of the headings for these rules. (I originally had much longer headings for all of them.) I would also like to thank many of MySQL, PostgreSQL and Java DB colleagues, as well as to many other colleagues involved in open-source development, for having contributed to the ideas and practices behind these rules.

A) …

There are some basic, golden rules when it comes to having a vibrant community of contributors.

The following are rules I have extracted and learned based on my experience managing and working with engineers actively involved and participating in the Apache/Derby, PostgreSQL and MySQL open-source communities. These rules are also based on extensive discussions with many folks involved with the MySQL community, with the PostgreSQL community and with the Apache/Derby (Java DB) community, over many years.

Before I go through these rules, I would like to thank Marten Mickos for having suggested some of the headings for these rules. (I originally had much longer headings for all of them.) I would also like to thank many of MySQL, PostgreSQL and Java DB colleagues, as well as to many other colleagues involved in open-source development, for having contributed to the ideas and practices behind these rules.

A) …

There are some basic, golden rules when it comes to having a vibrant community of contributors.

The following are rules I have extracted and learned based on my experience managing and working with engineers actively involved and participating in the Apache/Derby, PostgreSQL and MySQL open-source communities. These rules are also based on extensive discussions with many folks involved with the MySQL community, with the PostgreSQL community and with the Apache/Derby (Java DB) community, over many years.

Before I go through these rules, I would like to thank Marten Mickos for having suggested some of the headings for these rules. (I originally had much longer headings for all of them.) I would also like to thank many of MySQL, PostgreSQL and Java DB colleagues, as well as to many other colleagues involved in open-source development, for having contributed to the ideas and practices behind these rules.

A) …