<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
On 08/09/2009 04:39 AM, Raymond Martin wrote:
<blockquote cite="mid:200908081439.54486.laseray@gmail.com" type="cite">
<pre wrap="">On Saturday 08 August 2009 14:25:37 you wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 08/09/2009 04:27 AM, Raymond Martin wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Saturday 08 August 2009 14:06:52 you wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 08/09/2009 03:36 AM, Raymond Martin wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Yes this would apply for the commercial product against any others that
are sold. It won't apply against free software because nothing is sold.
</pre>
</blockquote>
<pre wrap="">Does it really matter? Do you really need to keep the name? If your fork
of the project continues active development while the institute
continues to develop their version then there will definitely be
confused users at some point down the line.
</pre>
</blockquote>
<pre wrap="">There is no fork. I am wondering how many times do I have to write that.
</pre>
</blockquote>
<pre wrap="">I think you may have confused the issue by stating at the very start of
this set of thread that you were going to fork the project and that you
had reverse engineered the binaries.
</pre>
</blockquote>
<pre wrap=""><!---->
I would have to look back to see if I actually wrote "fork the project"
or if I wrote fork Impro-Visor. In any case, it is the application that
is important, not the idea of a project.
</pre>
</blockquote>
<br>
<br>
What is the difference?<br>
<br>
<br>
<blockquote cite="mid:200908081439.54486.laseray@gmail.com" type="cite">
<pre wrap=""></pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">There is no fork, it does not exist. There is only a project with
a similar name, and packages of the original version, no forked program,
no forked code, nada. Except I did make a couple of minor changes in the
Impro-Visor packages I put up. Those were just to make it better for
others so they would not end up violating the GPL.
</pre>
</blockquote>
<pre wrap="">Sorry but how exactly is this different from a fork? Is there a guide
that you have read somewhere that explains the exact steps required for
making a fork? Why have you now decided that you are not actually
forking the project when you originally declared that was the intended
result of your efforts?
</pre>
</blockquote>
<pre wrap=""><!---->
A fork of an application is an application. What else could it be?
All I am saying, very clearly I might add, is that there is no application
that could be considered a fork and that is what all the discussions
are about.
</pre>
</blockquote>
<br>
So you have distributed a binary and the code that goes with as well as
making (minor) changes to the code including attributing copyright to
the various original authors in a way that wasn't done with the version
of the application that you reverse engineered and that is not a fork?<br>
<br>
What is a fork if not all the above?<br>
<br>
<br>
<br>
<br>
<br>
<pre class="moz-signature" cols="72">Patrick Shirkey
Boost Hardware Ltd</pre>
<br>
<br>
<br>
<blockquote cite="mid:200908081439.54486.laseray@gmail.com" type="cite">
<pre wrap=""></pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">I guess that was selfish.
</pre>
</blockquote>
<pre wrap="">You are putting the words in your own mouth here. There's no need to
suggest this even as a joke. I certainly haven't suggested it is the case.
</pre>
</blockquote>
<pre wrap=""><!---->
I better not use sarcasm, only others are allowed to do that to me.
Raymond
_______________________________________________
Linux-audio-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Linux-audio-dev@lists.linuxaudio.org">Linux-audio-dev@lists.linuxaudio.org</a>
<a class="moz-txt-link-freetext" href="http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev">http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev</a>
</pre>
</blockquote>
</body>
</html>