public inbox for cygwin-licensing@cygwin.com
 help / color / mirror / Atom feed
From: "Dave Sweetser" <dave@sweetser.com>
To: <cygwin-licensing@cygwin.com>
Subject: Use of cygwin man pages in my manual ?
Date: Thu, 08 Apr 2010 07:27:00 -0000	[thread overview]
Message-ID: <921B755088CE43A4A3DAF86A0C4EDF35@DAVEDV8000> (raw)

Hi,

I'm a technical writer and am developing documentation that will be used by
a number of my customers to develop web services.  This documentation will
include a number of example web service implementations that use tools like
Cygwin's OpenSSL tool.  However, I will only be providing documentation to
my customers. If my customers want to actually use OpenSSL themselves, they
would need to download the OpenSSL software from cygwin.com and comply with
the licensing terms.

My question is: Can my manual incorporate documentation that I download from
cygwin.com, such as the OpenSLL man page?  In performing my due diligence, I
read the Cygwin Licensing Page but I didn't find any copyright information
there.  I also looked through the mail archives and likewise didn't find
this question addressed there.

Can you let me know if my manual can incorporate documentation such as man
pages downloaded from Cygwin.com?  If this is acceptable, do I need to
include a copyright statement referencing Cygwin?

Thank you very much for your help with my question.

Sincerely,

Dave Sweetser

             reply	other threads:[~2010-04-08  7:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08  7:27 Dave Sweetser [this message]
2010-04-08  9:23 ` Corinna Vinschen

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=921B755088CE43A4A3DAF86A0C4EDF35@DAVEDV8000 \
    --to=dave@sweetser.com \
    --cc=cygwin-licensing@cygwin.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).