Quoting Elliot Noss <[EMAIL PROTECTED]>: Elliot,
Thanks for your explanation and I am aware of what happened and am sure that everyone's intentions were the best. If I were to make a guess as to why the project wasn't successful, it would be that most all opensource projects are "grass roots", altruistic and based on community needs. They don't start with approval of boards of directors, banks, etc. It wasn't my intention to suggest that CCS change to opensource short term. My suggestion was that applying successful, opensource, "grass roots" methods to a very small, well defined task could well benefit both the community and OpenSRS with little or no risk. Who knows, applying TLC, to this small seed, we could all very well be marching down 5th Ave. with joey not just developers but RSP's, OpenSRS and developers, arm in arm. ( We agree that Joey is the man, just not how to get him to polka.) Thanks again for your point of view. I promise to be quiet and wait for support even though I can't get an email to them yet. ed > ed, one thing to note here that certainly influenced our decision. > > when we first released open source client code in 2000 we had grand > visions of a successful opensource project that would lead to support > in multiple languages, extensions for other services and, like any > good open source project, a whole host of wonderful things that we > couldn't even imagine. > > in fact in 2000 this is what I presented to staff, to the board, to > bankers and to anyone who would listen! remember we have long roots > in open source through our large-scale distribution of linux and > other open source bits, bob young is an old friend and former board > member, blah blah blah (I could bore you here with all sorts of > shaggy dog stories). > > none of it came to pass. none of it. to be clear, I am NOT blaming > here. merely observing. our conclusion was/is that client code for > our customers is a very practical means of getting things done. good > deal. we understand that. > > accordingly, while we are supportive of code being completely visible > for all of the good reasons why that is the case, we really tried > here to focus on the practical. I think we have struck a nice balance. > > believe me we agree on the value of community participation. we would > love nothing better than for that to bloom around CCS. the thought of > a successful open source project with joey as bandleader is sweet > (picture joey leading merry band of developers down 5th avenue > playing the accordion in a sort of polka-samba line). let's see what > happens. > > meanwhile, I really feel this version of CCS is our delivery on a > number of promises that we have made, that I have made, dating back a > number of years. better late than never! > > if you use the RCL, try CCS! > > I am going to post separately, hopefully this weekend, on what I see > as the best thing about this release that I don't think we have > talked about enough. more later. > > Regards > > [EMAIL PROTECTED] wrote: >> Quoting Zeljko Dimic <[EMAIL PROTECTED]>: >> >> >>> Also feel free to contact support at Tucows. While discuss list is >>> great for >>> sharing experiences, anything that may be a real issue will get more >>> attention through support. >>> >> >> Thanks again for your support although we may not agree completely >> on community participation for product enhancement that benefits all. >> >> ed >> >> _______________________________________________ >> domains-gen mailing list >> [email protected] >> http://discuss.tucows.com/mailman/listinfo/domains-gen > > > -- > Elliot Noss > Tucows Inc. > 416-538-5494 > > _______________________________________________ domains-gen mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-gen
