From: pradeep singh <pradeep.rautela@gmail.com>
To: "Srinivas G." <srinivasg@esntechnologies.co.in>
Cc: kernelnewbies@nl.linux.org, linux-c-programming@vger.kernel.org,
linux-gcc@vger.kernel.org, linux-apps@vger.kernel.org
Subject: Re: The MIT License Modules
Date: Fri, 20 Feb 2009 14:56:09 +0530 [thread overview]
Message-ID: <a901b49a0902200126o24a1ed8gd0f33d146b66cb8c@mail.gmail.com> (raw)
In-Reply-To: <F5BA82141F7AA94885B9643C77EEA5F2104496@mail.esntechnologies.co.in>
I guess you should ask your lawyer, for a precise answer.
Please see http://en.wikipedia.org/wiki/MIT_License, it is pretty
simple enough I guess.
Thanks,
--Pradeep
On Fri, Feb 20, 2009 at 2:00 PM, Srinivas G.
<srinivasg@esntechnologies.co.in> wrote:
> Dear All,
>
> We have used software (freeglut) which comes under MIT License, in one
> of our applications. As far as I know, the MIT License is a very liberal
> software license that was originally developed at the Massachusetts
> Institute of Technology.
>
> My question is, if I use the MIT license software, should we be
> releasing our source code as well or can we still keep our source as
> proprietary and sell it. Please let us know so that we can make a
> decision whether to include the visualization features in our software
> or not.
>
> Thanks in advance.
>
> With Regards,
> Srinivas G
>
>
> --
> To unsubscribe from this list: send an email with
> "unsubscribe kernelnewbies" to ecartis@nl.linux.org
> Please read the FAQ at http://kernelnewbies.org/FAQ
>
>
--
Pradeep
prev parent reply other threads:[~2009-02-20 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 8:30 The MIT License Modules Srinivas G.
2009-02-20 9:26 ` pradeep singh [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=a901b49a0902200126o24a1ed8gd0f33d146b66cb8c@mail.gmail.com \
--to=pradeep.rautela@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-apps@vger.kernel.org \
--cc=linux-c-programming@vger.kernel.org \
--cc=linux-gcc@vger.kernel.org \
--cc=srinivasg@esntechnologies.co.in \
/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).