public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: DJ Delorie <dj@delorie.com>
To: cygwin@sourceware.cygnus.com
Subject: Things you can do with Cygwin
Date: Mon, 01 May 2000 20:22:00 -0000	[thread overview]
Message-ID: <200005020322.XAA20934@envy.delorie.com> (raw)

Just to avoid panic, here is a list of things you *can* do with
Cygwin...

--- if you don't purchase the proprietary-use license ---

[Note that these assume you're still meeting the terms of the GPL,
specifically, you distribute sources with any binaries]

You can...

* give copies to your friends (or enemies, if you like).

* install it on as many computers as you like.

* sell exact copies of what's on sourceware.

* modify it and sell it.

* charge a fee to do custom changes, which you don't tell
  anyone else about.

* charge a fee to do changes which you contribute to the
  official sources.

* change it and not tell anyone.

* start a new group of cygwin developers, and distribute your
  own version publically.

* write programs (apps) that use cygwin.

* use those apps yourself for whatever you want.

* give those apps to friends (or enemies).

* charge a fee for those apps (even though you're distributing
  sources too).

* choose an alternate "open source" license for the app (the
  cygwin dll remains GPLd).

* do any of the above without asking our permission.

--- if you DO purchase the proprietary-use license ---

* Any of the above

* distribute (sell, give away, whatever) an app without sources.

--- and, for completeness, things you do NOT have to do with cygwin ---

You do NOT have to...

* tell anyone about your changes, if you don't want to.

* give sources to people without binaries (unless you use GPL clause
  3b, there are some loopholes in 3b to be aware of), if you don't
  want to.

---

I probably missed some, but you get the idea.  I hope.

DJ

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

             reply	other threads:[~2000-05-01 20:22 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-01 20:22 DJ Delorie [this message]
2000-05-02  5:42 ` Doug Wyatt
2000-05-02  8:55   ` DJ Delorie
2000-05-02 10:42     ` Charles Hixson
2000-05-02 11:20       ` DJ Delorie
2000-05-02 12:29         ` Kendall Bennett
2000-05-02 12:45           ` DJ Delorie
2000-05-02 12:57             ` Mo DeJong
2000-05-02 13:20               ` DJ Delorie
2000-05-03  8:31                 ` Charles Hixson
2000-05-03  8:50                   ` Larry Hall (RFK Partners, Inc)
2000-05-03  9:23                   ` DJ Delorie
2000-05-02 13:38             ` Kendall Bennett
2000-05-02 16:34               ` DJ Delorie
2000-05-02 17:08               ` Suhaib M. Siddiqi
2000-05-02 12:30         ` Norman Vine
2000-05-02 12:53           ` DJ Delorie
2000-05-02 13:16             ` Norman Vine
2000-05-02 13:32               ` DJ Delorie
2000-05-02  5:09 Earnie Boyd
2000-05-03  1:59 Bernard Dautrevaux
2000-05-03  5:05 ` DJ Delorie
2000-05-03  7:33 13mb80000-HallM(10053584)37x10
2000-05-03  7:47 ` DJ Delorie
2000-05-03  8:05 13mb80000-HallM(10053584)37x10
2000-05-03  8:09 ` DJ Delorie
2000-05-03  8:23 ` David Lane
2000-05-03  9:19 David Robinow
2000-05-03 10:45 Earnie Boyd
2000-05-03 11:04 ` Larry Hall (RFK Partners, Inc)
2000-05-03 11:33   ` Chris Faylor
2000-05-03 11:53 David Robinow
2000-05-03 11:59 ` Chris Faylor
2000-05-03 21:34 Bernard Dautrevaux

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=200005020322.XAA20934@envy.delorie.com \
    --to=dj@delorie.com \
    --cc=cygwin@sourceware.cygnus.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).