public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fabio Riccardi <fabio@chromium.com>
To: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Christopher Smith <x@xman.org>,
	Andrew Morton <andrewm@uow.edu.au>,
	"Timothy D. Witham" <wookie@osdlab.org>,
	David_J_Morse@Dell.com, Ingo Molnar <mingo@elte.hu>,
	"David S. Miller" <davem@redhat.com>,
	dean gaudet <dean-list-linux-kernel@arctic.org>,
	Zach Brown <zab@zabbo.net>
Subject: License Clarification [X15 beta 1 - source release]
Date: Sun, 27 May 2001 19:59:12 -0700	[thread overview]
Message-ID: <3B11BF00.398100E3@chromium.com> (raw)
In-Reply-To: <3B0F018B.A9823BD4@chromium.com>

Some people pointed out that I misused the term "Open Source" wrt our Source
License.

Our license doesn't meet the required criteria of the OSI since we restrict
the usage of our sources for personal use only. As was already pointed out in
my previous message people will have to buy a license for commercial
exploitation of the code (i.e. running a commercial web site).

Sorry for the inconvenience,

 - Fabio

Fabio Riccardi wrote:

> Dear all,
>
> I finally managed to package the X15 web accelerator for the first
> source release.
>
> The current release includes a CGI module, an Apache configuration
> module and several salability improvements. It is a beta 1, quite stable
> but it may/will still contain a few bugs. The README is a bit outdated
> and the code could use more comments... :)
>
> The code It is released under an Open Source license very much in the
> spirit of Sun/Solaris, Apple/Darwin, etc., but less restrictive.
>
> Basically (for what I have been explained by our lawyers :) the license
> says that:
>
>  1) you can peruse the code for your own use and/or research in any way
> you like,
>
>  2) you can use X15 for your own non commercial use (i.e., you can have
> the fastest family reunion pictures website of the planet),
>
>  3) if you want to use the software for any commercial exploitation you
> have to buy a license from Chromium Communications,
>
>  4) if you make changes they belong to you, but if you send them back to
> us than you agree to not claim anything for them.
>
> You can get the sources from:
> http://www.chromium.com/cgi-bin/crosforum/YaBB.pl
>
> or (when the DNS gets propagated) from: http://source.chromium.com/
>
> Our source site sports one of those nifty sourceforge-like interfaces
> for discussions, bug reports and whatever, I'd prefer you to use that
> instead of sending email directly to me or to this list.
>
> I'll build a proper "product" web page and add more documentation in the
> next few days.
>
>  - Fabio
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


      reply	other threads:[~2001-05-28  2:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-26  1:06 X15 beta 1 - source release Fabio Riccardi
2001-05-28  2:59 ` Fabio Riccardi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3B11BF00.398100E3@chromium.com \
    --to=fabio@chromium.com \
    --cc=David_J_Morse@Dell.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrewm@uow.edu.au \
    --cc=davem@redhat.com \
    --cc=dean-list-linux-kernel@arctic.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=wookie@osdlab.org \
    --cc=x@xman.org \
    --cc=zab@zabbo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox