community,

open source, gpl, tld's..

these are long, long discussions, some pertinent, though not to
this valuable list. i've read many opinions, respect some,
but these are for lawyers, not hackers (in linus' sense of
the word). nevertheless, there is a message for us nerds:
let's keep it open!!! our greatest allies will be our peers,
not some guys from legal. so, write decent code, open it wide,
and rejoice.

when this all started, i waited anxiously for monty's post. took
me a while to digest it (may i suggest all of the involved in
the whole discussion do so as well). my humble conclusion is:
i'm really glad mysql ab is focused on development and training,
and not on courts and deals. i believe many in our programming
community feel the same.

monty, keep it up!!!
as north americans would say: mysql kicks some serious a**.
btw: thank you so very much.

warm regards to all

mauricio portasio
[EMAIL PROTECTED]

sao paulo - brazil




> On Sat, Jul 14, 2001 at 03:10:34AM -0400, Britt Johnston wrote:
>
> > Well, what a mess.  It is regretable that this legal issue needs to
> > be aired so publically that was certainly not my preference.  I also
> > will not get into a flame war, it is not in the best interest of
> > mysql. I appreciate all the email I've received with advice and/or
> > support - thanks.
>
> It is good to see some discussion taking place here.  Perhaps it will
> help make the issues a bit clearer to the folks who have been
> wondering what they heck is going on (that's the majority of the
> community).
>
> > As far as NuSphere's contribution to MySQL, it is disappointing to
> > see our efforts discounted so quickly.
>
> I don't think that folks are discounting your efforts.  In many cases,
> folks knew little of what NuSphere had really done to date.
>
> > The Gemini table handler itself is already part of MySQL and is
> > licensed under the GPL - go find ha_gemini.cc and you will see it we
> > checked it in long ago in V4 and again in 3.23 when V4 was late.
> > The Gemini component itself will be released via mysql.org as GPL as
> > previously announced - note that Gemini itself is not a derivative
> > of MySQL in any way - it's roots date back to long before MySQL
> > existed.
>
> There's another source of confusion for people.  The difference
> between the Gemini table handler and the "Gemini component itself".
> What is the difference?  (I think I might know, but I suspect that
> it's not clear to folks who haven't heard you talk about Gemini in
> person.)
>
> > Finally independent of the rest of this.  I have the highest respect
> > for Monty and what he has done creating MySQL.
>
> A sentiment we all share.
>
> And some (many?) of us realize that NuSphere has a done some
> incredible work in an effort to take MySQL up a notch.  NuSphere's
> talent and responsiveness was clear to me during the Gemini beta
> program.
>
> > I'm certain we can move beyond this and make MySQL an even stronger
> > open source project and I encourage everyone move to a constructive
> > dialog.
>
> I suspect that in the short term, the legal battles are likely to
> become less interesting to this community than:
>
>   * Being presented with the mysql.org site and not understanding
>     where it came from, who runs it, and why they should go there.
>
>   * The affects that this will have on the community.  Are there going
>     to be separate mysql.org hosted mailing lists which overlap in
>     funtionality and audience with those hosted here?
>
>   * Will it become less clear where users should go for information,
>     documentation, downloads, and so on?
>
>   * Understanding the differences between NuSphere's MySQL and MySQL
>     AB's MySQL distributions.  I know that they are relatively few
>     now, but will that continute to be the case?  Who knows.
>
> Those are the sort of concerns which motivated my statements in the
> MySQL press release a few days ago.  I think that the MySQL community
> today is excellent--one of the best surrounding any piece of Open
> Source software today: Linux, FreeBSD, Perl, Apache, PHP, Python,
> MySQL, etc.  They all have great communities.
>
> None of us want to see the community sidetracked, fragmented, or
> otherwise damaged as a result of this.  Having read about the old
> XEmacs fork from GNU Emacs, that sort of stuff doesn't sound pleasant.
>
> We have a great forum for discussion right here.  I'd suggest that
> when feasible, folks should talk to the community.  Find out what
> folks here think about having a new/different web site, forked code,
> or whatever may be brewing.  Unlike slashdot, folks here are apt to
> think before writing the first thing that pops into their heads.
>
> Given that this mailing list has been a large part of the MySQL
> community, it'd be great to see folks from NuSphere on it in a while.
>
> Jeremy (trying not to fuel any fires)
> --
> Jeremy D. Zawodny, <[EMAIL PROTECTED]>
> Technical Yahoo - Yahoo Finance
> Desk: (408) 349-7878   Fax: (408) 349-5454   Cell: (408) 685-5936 <-- NEW
>
> MySQL 3.23.29: up 28 days, processed 213,565,627 queries (88/sec. avg)
>
>
> ---------------------------------------------------------------------
> Before posting, please check:
>    http://www.mysql.com/manual.php   (the manual)
>    http://lists.mysql.com/           (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail
<[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
>


---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to