[ENet-discuss] License question
Lee Salzman
lsalzman at gmail.com
Fri Mar 25 05:12:40 PDT 2011
All things considered, if it is only a binary distribution (no source
code included), I would prefer that at least my copyright is stated
somewhere in the documentation and a link to the license is provided as
well either directly at (http://enet.bespin.org/License.html) or state
that full licensing and other information can be found at the home page
(http://enet.bespin.org/). This doesn't necessarily have to be in a
prominent location, but it should be somewhere where people could
reasonably find the information amongst related such notices, and if it
is placed somewhere low key, then ensure that there is not information
elsewhere in the product or documentation that would misconstrue the
origin of the networking code. Or you could provide the full license
text if you want. Either is reasonable for the binary-only distribution
case, so long as it is clear that the copyright on the code belongs to
me and the terms of that copyright are accessible as above.
If source code is included, the full license text must be included with
the source code.
Lee
On 03/25/2011 07:21 PM, Philip Bennefall wrote:
> Hi Lee,
> I just had a quick question for you regarding the ENet license, to
> make sure I am doing things correctly. With the following statement:
>
> The above copyright notice and this permission notice shall be
> included in all copies or substantial portions of the Software.
>
> Do you refer to the source code, or must binary applications that use
> ENet include the license? Currently I have a statement like this in my
> documentation (including a link to the website):
>
> The ENet Project <http://enet.bespin.org/>
> ENet is a rock solid layer on top of the UDP protocol, optimized
> especially for high-speed games. This is what BGT uses to provide its
> networking capabilities.
>
> Is this acceptable? Or am I required to add the full legal text? I
> much prefer the above notice to the complete license.
>
> Thanks!
>
> Kind regards,
>
> Philip Bennefall
>
>
More information about the ENet-discuss
mailing list