Dave Bettin wrote:
> Sorry, should have explained that statement a little
> better. What I intended to mean, was to allow users to
> pick up an application on the .Net port and move it to
> cocoon w/o much hassle and vice a versa.

Dave,

please be aware of the fact that Cocoon lives on the value of its name 
and its license protects it.

I'm personally happy if somebody ports Cocoon in other languages (people 
already did twice, for Perl and PHP) but I'll be personally pissed if 
they used 'cocoon' inside the name if they distribute something which is 
not coming *straight* from this project.

So, whatever you end up with, please, don't call it 'cocoon#' or 'Cocoon 
.NET' or "NCocoon" or anything that contains Cocoon in it, unless you 
want to donate your code to this project and then the community will 
decide if we want to maintain two independent codebases written in two 
different languages. [but it would be easy to guess the answer]

As far as C# goes, I think .NET does things better than java in a few 
circumstances, but for sure this is not a good reason to throw away 
those millions of lines of code we already have.

So, at the end, all I personally ask you is to be respectful of our work 
by not abusing the name cocoon for your work.

For anything else, expect great collaboration from me even if I'm not 
going to move my programming skills to C# just yet.

[and people, please, no language-flamewars, ok? the world is beautiful 
because it's diverse, we just have to be nice and respectful one another]

-- 
Stefano Mazzocchi                               <[EMAIL PROTECTED]>
--------------------------------------------------------------------



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to