diff options
| author | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
|---|---|---|
| committer | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
| commit | 0ea5fc66924303d1bf73ba283a383e2aadee02f2 (patch) | |
| tree | 2568e71a7ccc44ec23b8bb3f0ff97fb6bf2ed709 /pipermail/nel/2001-June/000452.html | |
| download | nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip | |
Initial commit
Diffstat (limited to 'pipermail/nel/2001-June/000452.html')
| -rw-r--r-- | pipermail/nel/2001-June/000452.html | 72 |
1 files changed, 72 insertions, 0 deletions
diff --git a/pipermail/nel/2001-June/000452.html b/pipermail/nel/2001-June/000452.html new file mode 100644 index 00000000..752c22ea --- /dev/null +++ b/pipermail/nel/2001-June/000452.html @@ -0,0 +1,72 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Nel] Congratulations + concerns</TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:x5101920%40fedro.ugr.es"> + <LINK REL="Previous" HREF="000451.html"> + <LINK REL="Next" HREF="000453.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Nel] Congratulations + concerns</H1> + <B>x5101920@fedro.ugr.es</B> + <A HREF="mailto:x5101920%40fedro.ugr.es" + TITLE="[Nel] Congratulations + concerns">x5101920@fedro.ugr.es</A><BR> + <I>Sun, 01 Jul 2001 00:51:13 +0200 (MET DST)</I> + <P><UL> + <LI> Previous message: <A HREF="000451.html">[Nel] Congratulations + concerns</A></li> + <LI> Next message: <A HREF="000453.html">[Nel] Congratulations + concerns</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#452">[ date ]</a> + <a href="thread.html#452">[ thread ]</a> + <a href="subject.html#452">[ subject ]</a> + <a href="author.html#452">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Mensaje citado por: Michael Warnock <<A HREF="mailto:michael@in-orbit.net">michael@in-orbit.net</A>>: + +><i> By way of introduction, I am working on a couple of games making use of +</I>><i> nel- commercial games. In addition to selling our content and service, +</I>><i> we consider our game rules our ip and there are a couple reasons why +</I>><i> they can be implemented without violating the gpl (which i consider +</I>><i> scripture). First of all our rules will be in a brand new specification +</I>><i> language in +</I>><i> their own files or database tables and wont be compiled or linked at +</I>><i> all. But should we run into speed problems for not hardcoding +</I>><i> everything, we're still not required to release anything- you can quite +</I>><i> legally use gpl'ed code in your own, unreleased programs- and why should +</I>><i> we release the server side code? +</I> +I would love that you reply to this answer to me and to Nel guys that are so +hard working on such a good project. + +IMO In the same moment that you make public your server you are making it public +and you should release it. But I am not a lawyer. + +Regards, + Miguel Angel Blanch Lardin + +nuclear cia fbi spy password code encrypt president bomb iran irak korea cuba +Ala yihad mosad kgb free freedom human rights yugoslavia kosovo ebola dna + + -- Echelon must die -- + +</pre> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI> Previous message: <A HREF="000451.html">[Nel] Congratulations + concerns</A></li> + <LI> Next message: <A HREF="000453.html">[Nel] Congratulations + concerns</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#452">[ date ]</a> + <a href="thread.html#452">[ thread ]</a> + <a href="subject.html#452">[ subject ]</a> + <a href="author.html#452">[ author ]</a> + </LI> + </UL> +</body></html> |