I completely agree that you have made the API and the main library usable, and thanks for that work.

You seem to be tone-deaf when it comes to my appreciation of your work. It certainly is partly due to my ability to use the fruits of your work. But it also is technical appreciation, and even personal appreciation.

However, the question here is one of authority. You simply do not have the authority to decide all by yourself, for all other Csound developers, what is the appropriate level of dependency or cleanness, or even whether C++ is OK or not OK in Csound.

Sincerely,
Mike


-----Original Message-----
From: Istvan Varga 
Sent: Oct 21, 2005 11:29 AM
To: csound-devel@lists.sourceforge.net
Subject: Re: [Cs-dev] Re: More unasked for changes

Michael Gogins wrote:

> Any Csound developer has the right to make contributions as long as they 
> compile and run and do not interfere with the contributions of others. 

Now what if you consider it a contribution to have a clean API library
with as few dependencies as possible (that is, preferably nothing more
than sndfile) ? Sometimes it may be possible to "interfere" by adding
something in a particular way.

> However, I don't think an objective observer would say that I have been 
> "lazily sitting around". I created the Csound API in the first place. I 
> created the improved Csound 5 scons build system. I fixed a number of 
> bugs. I contributed the C++ STK opcodes, fixed up the Loris opcodes for 
> Csound 5, and contributed to the Fluidsynth opcode. I also developed the 
> midiiinterop opcodes and the mixer opcodes. I contributed the Python 
> wrappers and, of course, I contributed CsoundVST, which some people use 
> as a GUI front end for Csound. CsoundVST contains an algorithmic 
> composition system that is unique in computer music.

Of course, this is all true, and by the way I also contributed quite a
few opcodes and even more bug fixes, as well as some language improvements,
but this is not what is really relevant.
It was in large part me who made the main library - the only place where
I actually care at all about what is added and what is not - usable by
(mostly, there is still some work to be done) completing the API, adding
missing functionality, turning stubs into actual functions, making it run
in multiple instances by removing countless static variables, improving
modularity, and cleaning up all the old cruft (remember macros like
#define ksmps cenviron.ksmps_ ?).

> And of course, for years I agitated for making Csound open source - so 
> that if Istvan does fork Csound, it will be legal for him to do it! 
> Though I don't think that would be wise.

It surely could have been wise if I did that instead of joining Csound 5
development; imagine a fork that has most of the contributions of the
current CVS sources, alongside with a canonical version that is not much
different from what it was a year ago. Of course, it is less attractive
to fork now given the maturity of Csound 5 now - it would be harder, but
not impossible to have competitive advantage. Anyway, I do not want to do
that, but if others force to do so by physically locking me out of
developlment, then, well, I have no choice other than doing my best to
beat something that has become much better due to my own work. How ironical.

> As I said in an earlier email, I think it is important to be able to 
> tell the difference between anger at an action and anger at a person. I 
> am angry at what Istvan did, but I am not so angry at Istvan personally 
> that I do not credit or value his achievements.

I do not doubt that you value whatever achievements by taking advantage
of them. This is understandable.

> If Istvan will stop meddling with my contributions, then I very much 
> want him to continue as a Csound developer. If, however, he does not 
> stop meddling with my contributions, then I do want his access to Csound 
> CVS removed.

I am not responding to threats of this type.


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel





-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net