>> How can a developer check whether his/her code has been removed ? You can > claim whatever >> you want to claim... >> That's the big problem : you're using other people's code and then you claim > you've >> removed it. It might just as well still be in there, without their copyright >> information. Since it's closed source, we have no way of checking that. > > So then you take Idaya to court, and get them to prove that they don't > distribute any of the modifications that you believe are in the code. > It could be expensive.
Well if Idaya thinks that the they wont have any problem because non of us will spend money into a lawyer battler... Thats basically stupid, and could be another reason to stop supporting the project as an open source community member. >> And if people want to help out in development, like I did, you are more eager > to turn >> away than to accept them. All I asked for was for a general structure of > FreeVSD, so >> that I could understand how it was built. I need a system like FreeVSD, but I > also >> wanted to change it for clustering purposes and to get 100% availability. > Instead of >> embracing people, you tell them to get lost, because their questions are > stupid. Well, >> so be it... > > I think it is more to do with not having the time or inclination to write > such documentation. Certainly that is the reason why I won't explain it. > Plus I don't want the hassle of the follow up questions, which usually > amounts to: Please write full documentation or an RPM script to set up > a full clustering solution for me because I don't want to do any of the > work myself. Nick, people like you and Wim and me and lot of more want to contribute, but wont do it until we see some warranties that the code will be kept GPLed and that the company will put back into the project some effort into the community response... Wim will probably write a document, I will probably write some rpms, that NOT the problem, but the way the project will be handled from the copyright holding company. > Even with casual scan through the history of this list, you can attribute > more questions to setting up Apache, PHP, MySQL or Postgres, or some IRC > bot or some other crap like that than there is anything about FreeVSD > itself ! And those questions are not answered... :) Here goes again : ****************************************************************** * How do i enable the +chrtftp user right into the ftp service ? * ****************************************************************** I think thats enough readable, isnt ? > Setting up a clustering solution is a non-trivial task and I don't see > why such stuff should be documented by the FreeVSD project. If you Wim is saying he might provide that, he isnt requesting that document from Idaya... Not the way i read it... >> What you may not realize yet, is that you'll now have to change the way your > company >> works completely. You're no longer a company offering add-on services for a > free >> project. You won't be able to say : "Oh, that's a bug in FreeVSD. Someone in > the >> community wrote bad code.". If something goes wrong, you'll be to blame. If a > company >> has 50 servers with ProVSD running and they crash, you'll be to blame. > > That's just silly. If I installed a Red Hat linux system for a customer > and after a few days Emacs broke. They what do I say to the customer ? > "Oh sorry, one of the emacs programmers hasn't got a clue what he's > doing. It's not my fault, blame them !". Yeah, I'm sure the customer > would be happy. First, the customer will have to know about how Open Sourced license works. If you got a customer which complains about a broken Emacs to YOU, then basically, WHAT KIND OF CUSTOMER do you have ??? Is that the right market?? > Surely there's the concept of a support contract or something similar ? > Where you fix the problems that are raised by your customers. You can't > expect the community to fix them, becuase they may never trigger them. You can either submit a bug report or fix it since you have the latest working and distributed source code ;-) >> As a hosting company, we've studied the software and found >> it to be insufficient in terms of reliability. So we want guarantees that it > will be >> made more reliable. > > Well why should anybody guarantee this ? It's Free Software and it comes > with "NO MERCHANTABILITY or FITNESS FOR PURPOSE". All code comes like that, but the goal is to make it better, isnt ? >> With FreeVSD, making it more reliable is something we could do >> ourselves. > > Yeah, but are you going to even try. Or are you just going to sit there > and compain that there's no documentation and so you don't have a clue > how it works. You aren't going to stand any chance of making the system > any more reliable unless you know how to read and understand source code. > Which you seem to either not be able to achieve, or even want to attempt. > Understanding FreeVSD is only a tiny part of understanding why there > are reliability problems with the system. The fact is that right now there is a "political" issue, which stops people (like me) to contribute directly to the project. Regards, _______________________________________________________ Urivan Saaib Presidente CiberNET Mexico Email: [EMAIL PROTECTED] Tel/Fax: (646) 175.71.95 ------------------------- The freeVSD Support List -------------------------- Subscribe: mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support Archives: http://freevsd.org/support/mail-archives/freevsd-support -----------------------------------------------------------------------------
