Hello. I have a brief moment to type this. I'm sorry if it sounds bit 
rude, but I sincerely hope you consider my main point to this and 
forgive me for my hasty style. I have kind cut and paste this from an 
earlier post in my defense of open source.

I believe there are people who have used libsecondlife as an example 
before the fires and now are part of the witch hunt. I have seen signs 
posted at malls, "LibSL members are not welcome and will be banned." 
That basically puts those who have tried to promote libsecondlife, even 
if they never used it, at a disadvantage and and into a state of virtual 
liability.

CopyBot issues are dead as far as I am concerned. However, reputations 
have been changed in the aftermath.

If I publish a program that interfaces with libsl, I know right now I 
would have a hard time to convince everybody that the program is safe 
once potential users find out it uses libsl.

As far as I am concern, libsl also joins the ranks of open source. The 
witch hunt itself is not center on any single member of libsl. It is 
directed broadly at open source developers. The accusations fly far as 
such to make an example out of anybody who posts source code in a open 
source manner as someone who is an evil hacker. This is not good.

This has become worse than CopyBot.

I regard these attempts at a witch hunt to cause much more damage. This 
mockery ruins people's reputation. This mockery ruins people ability to 
sell. It seriously damages the economy worse.

No need to ruin people's reputation that have done sincere work. Mainly, 
people that are not even involved with libsl. What I have experience are 
many that don't even care if their involved with libsl. The witch hunt 
affects all open source developers.

Peoples lives get ruined.The witch hunt effort at times appears so 
routine that I get a gut reaction that the motive is not based on the 
affect of CopyBot at all. There is evidence that the witch hunt effort 
may even be an anti-trust movement. As an open source developer myself, 
I want to stop that movement before it even gets on the road. I've seen 
it happen to many times in my past. Let's not let that happen.

Sincerely, the best move for LibSL right now is to seperate *all* 
applications from its SVN sever except for the "library code" itself to 
interface the protocol and only that of the network protocol, SLproxy, 
and the utility scripts to build the package. The "library code" may be 
in the style of "libx11", and that would be acceptable. All other code, 
even if examples itself, do not meet a professional level for inclusion 
into the package as an interface to Second Life.

Developers of those separate applications may wish to use websites other 
than libsencondlife.com to host their work.

If this is done, I'll continue my full support of libSL. I have done 
what I can to defend it as open source software and a step toward open 
standards with SL. If an open standard is not the true vision of libsl, 
it has ruined my reputation as well.

If this cannot be done, I feel the next step is to... reverse 
engineer... libsecondlife into a clean professional open standard 
framework totally separate from the libsecondlife developers. I know 
this does not sound good. However, do consider your choices and the 
outside image that has happened.

Thank you for your time to read this. Best wishes...
-- 

_______________________________________________
Libsecondlife-dev mailing list
[EMAIL PROTECTED]
https://lists.berlios.de/mailman/listinfo/libsecondlife-dev

Reply via email to