httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <>
Subject Re: ASF License vs GPL ... was... Re: [PATCH] ap_add_filter
Date Tue, 22 Aug 2000 17:13:24 GMT
Bill Stoddard wrote:
> >
> > ALL of Apache is already open-source and public anyway so why
> > should there ever be a concern about dumping GNU code
> > into Apache itself? You have nothing to lose. Or am I still
> > totally missing something about ASF license versus GNU?
> >
> Not really interested in starting a new thread on this topic,
> but....... yes, there is plenty you're missing if you believe the ASF
> license is compatable with the GPL. The big difference is that the ASF
> license allows you to derive a product based on Apache and not release
> the source code to that derived product. The GPL holds a figurative
> gun to your head to force you to comply with its terms.  If you think
> there is even the slightest chance that you will EVER need to release
> a closed source derivitive of a GPL'ed piece of code (for -any-
> reason, some of which may not be under your control), you better not
> use that code. Consider this... If Apache were GPL'ed, then one year
> ago it would have been impossible for any U.S. based firm to legally
> sell/give-away a secure (SSL) Apache.

I've been looking over, a lot, the way MySQL is handling using
GPL. Basically, it says that MySQL is under the GPL. If that's not
right for your application, then you can _purchase_ a _commercial_
license for it as well.

For some projects, this is a very nice solution. I'm not saying that
Apache should move that way, not at all, but there are ways to
"get around" GPL ;)
   Jim Jagielski   [|]   [|]
                "Are you suggesting coconuts migrate??"

View raw message