Re: mysql.org

[Bob Hall]

On Wed, Jul 18, 2001 at 11:10:20AM -0700, Michael Collins wrote:
> It seems to me that the bottom line is that any outcome that results 
> in there being a fork in the development of MySQL (with the result 
> being two completely different types of MySQL), or in NuSphere 
> retaining control of the mysql.org domain should be vehemently 
> rejected by the MySQL community. No matter what agreement may or may 
> not have been created, since MySQL AB has made it clear that this is 
> not what they want or intended. So to me it is obvious that any 
> agreement that may have been made is either being misinterpreted by 
> NuSphere or was not entered in good faith.
> 
> NuSphere, if what you want is an improved MySQL and if you have 
> anything to contribute to the betterment of MySQL, hand over the 
> code. If you want a "non-profit" Web site first turn over MySQL.org 
> to MySQL AB and either register NuSphere.org for your non-profit site 
> or help MySQL AB to get it started. If you want to make money on 
> MySQL, follow the guidelines of GPL to the letter and to the approval 
> of MySQL or pay the per-copy license.
> 
> I guess the solution seems so simple for an outsider.
> -- 
> Michael

I think I've made it clear that I'm not enamored of NuSphere's 
recent actions, which I think are remarkably bone-headed. At 
the same time, a NuSphere-controlled mysql.org doesn't strike me 
as a disaster, provided they can do it with out shooting 
themselves in the foot, as they are doing now.

I have two concerns about the present conflict. First is the 
obvious problem that MySQL AB lacks the resources to develop 
table types with extended functionality, as NuSphere, 
SleepyCat, and InnoDB are doing. MySQL AB has a comparative 
advantage in SQL interfaces, core DBMS functionality, and 
porting MySQL to as many OSs as possible. If they try to 
do more than that, they'll probably be too overextended to 
do any single thing well. 

NuSphere has a comparative advantage in providing extended 
functionality. Because they don't have to deal with the 
problems that MySQL AB is solving, and because they have an 
existing code base that they can modify, they can bring a 
relatively mature product to market that makes the overall 
MySQL package more attractive. Even if you discount the 
marketing hype, the word from the beta testers is good.

My second concern is the fact that NuSphere has made a 
large investment in converting their table to use with 
MySQL, and that investment was made after undergoing a 
formal agreement. If the investment fails and the 
agreement ends in lawsuits, it will discourage further 
investment and more agreements involving other companies.

On the other hand, if the present disagreement can be 
resolved without recourse to legal remedy and NuSphere 
makes a nice profit on its investment, it will encourage 
other companies to make agreements with MySQL AB and make 
investments that further extend MySQL's capabilities. 

It's in everone's interests for NuSphere to make a profit, 
and it's in everone's interests for MySQL AB to have 
a reputation as a reasonable business partner. The 
developer community needs both the complementary capabilities 
of NuSphere and MySQL AB, and useful tools from other 
companies. The tools won't come unless other companies invest, 
and they won't invest unless they think they can make a 
profit. Disagreements between partners raise costs and reduce 
profit. I don't want to discourage either side from defending 
their interests or what they see as their rights. An agreement 
that leaves one side or the other feeling ripped off is not 
going to encourage more agreements or more investment. On the 
other hand, failure to come to agreement will poison the 
communal well.

In the end, the details of an agreement will be less important 
than the fact of an agreement, provided the agreement promotes 
both parties' interests. NuSphere doesn't need mysql.org in 
order to make a profit, and MySQL AB can allow some use, perhaps 
temporarily, of the MySQL trademark without surrendering the 
crown jewels. MySQL AB's primary assets are its leadership 
in the MySQL community and the company's comparative advantage 
in the kinds of development mentioned above. 

The real issues are: How is NuSphere going to market 
their product, what is MySLQ AB going to contribute that both 
helps NuSphere and helps create the perception of an atmosphere 
that welcomes outsiders, and what is the value of MySQL AB's 
contribution (i.e. how much is NuSphere going to pay for an 
agreement, either in cash or otherwise). 

-- 
Bob Hall
mysql list incantation: sql table databse query