aboutsummaryrefslogtreecommitdiff
path: root/pipermail/nel/2001-February/000193.html
diff options
context:
space:
mode:
Diffstat (limited to 'pipermail/nel/2001-February/000193.html')
-rw-r--r--pipermail/nel/2001-February/000193.html104
1 files changed, 104 insertions, 0 deletions
diff --git a/pipermail/nel/2001-February/000193.html b/pipermail/nel/2001-February/000193.html
new file mode 100644
index 00000000..0917b88f
--- /dev/null
+++ b/pipermail/nel/2001-February/000193.html
@@ -0,0 +1,104 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Nel] Snowballs Data &amp; CVS</TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:archer%40nevrax.com">
+ <LINK REL="Previous" HREF="000192.html">
+ <LINK REL="Next" HREF="000210.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Nel] Snowballs Data &amp; CVS</H1>
+ <B>Vincent Archer</B>
+ <A HREF="mailto:archer%40nevrax.com"
+ TITLE="[Nel] Snowballs Data &amp; CVS">archer@nevrax.com</A><BR>
+ <I>Fri, 16 Feb 2001 17:48:57 +0100</I>
+ <P><UL>
+ <LI> Previous message: <A HREF="000192.html">[Nel] Snowballs Data &amp; CVS</A></li>
+ <LI> Next message: <A HREF="000210.html">[Nel] Snowballs Data &amp; CVS</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#193">[ date ]</a>
+ <a href="thread.html#193">[ thread ]</a>
+ <a href="subject.html#193">[ subject ]</a>
+ <a href="author.html#193">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Some quick answers, before we go further in detail.
+
+According to Zane:
+&gt;<i> Would it be possible to move the snowballs data into the CVS tree? I'm
+</I>&gt;<i> keeping current with the CVS updates and evidentally some changes made to
+</I>&gt;<i> NeL or the client/server portion have rendered the data package offered on
+</I>&gt;<i> the website obsolete.
+</I>
+Hmmm, that's odd. It shouldn't have, but we'll look at it.
+
+&gt;<i> Have you all looked at using sourceforge for your public CVS front end? The
+</I>&gt;<i> site can be designed to look exactly like your current site (but I believe
+</I>&gt;<i> would require a sourceforge graphic and link somewhere on the page) and
+</I>&gt;<i> offers all the services you currently offer as well as more bandwidth and
+</I>&gt;<i> will spare you from further slashdot type outages (at least to some degree
+</I>&gt;<i> :).
+</I>
+We could use Slashdot, yes. In fact, there's a NeL project registered
+on it &quot;in case&quot;. Why aren't we using Sourceforge? Well, apart from the
+current rumors of source forge growing beyond its possibilities of support,
+we'd lose some of the control we have on the current public system. It's
+a relatively gray area, and one on which we aren't saying much, except,
+&quot;well, right now we aren't&quot;.
+
+&gt;<i> I've read back through the mailing list archives and understand that you're
+</I>&gt;<i> using a plugin to 3DSMax to create NeL objects. Will you be releasing this
+</I>&gt;<i> any time soon? I know a few people that are not 3D developers (unable to
+</I>&gt;<i> write a plugin) but would be interested in starting to build content. I'm
+</I>&gt;<i> curious why you haven't released it already? (Yes, I'm nosy :)
+</I>
+License issues. Basically, we have a problem releasing a free plugin to
+a commercial non-source software package. The GPL poses a lot of problems
+(we can't give you a GPLed 3DSmax, can we?), and we haven't a satisfying
+license yet that allows to get as close to GPL as we can, while respecting
+the license from 3DS.
+
+&gt;<i> What about design documents for NeL? You have a lot of auto-generated
+</I>
+No comment :)
+
+We know we should :)
+
+&gt;<i> Are you actually interested in other developers making major contributions
+</I>&gt;<i> to this project pre-production or are you more interested in just offering
+</I>&gt;<i> your work to the community?
+</I>
+Both. Altough we haven't specifically announced things, we have a specific
+program and are opening CVS commit privileges to specific people, so we
+are looking for contributions, at all levels (from simple bug fixes to
+whole features).
+
+We don't guarantee we'll use everything, but if it &quot;fits&quot; within the
+NeL scope, we'll put it in, even if we don't use it ourselves (yet).
+
+--
+Vincent Archer Email: <A HREF="mailto:archer@nevrax.com">archer@nevrax.com</A>
+
+Nevrax France. Off on the yellow brick road we go!
+
+</pre>
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI> Previous message: <A HREF="000192.html">[Nel] Snowballs Data &amp; CVS</A></li>
+ <LI> Next message: <A HREF="000210.html">[Nel] Snowballs Data &amp; CVS</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#193">[ date ]</a>
+ <a href="thread.html#193">[ thread ]</a>
+ <a href="subject.html#193">[ subject ]</a>
+ <a href="author.html#193">[ author ]</a>
+ </LI>
+ </UL>
+</body></html>