Re: something I noticed re:licenses.

> No offense Alex, but I think 13 emails from you in the last 45 minutes > is getting a bit silly. I compose them and send them in a burst, so I do all the pear stuff once a day (if possible) But there's a lot going on, and a lot of it involves binarycloud, so I'm active on this list. If you think that's "silly" then I think you are "silly" :) > First, read the earlier posts (mostly from Rasmus) about licensing > and PEAR. I have asked some direct questions, hoping they will be answered in context, but I will go through the archive and read 'em. > Second, I don't know about the copyright issue, but I imagine that > the general consensus is if you "have no intention of ever releasing > copyright on the binarycloud code", then you simply won't be making that > code part of PEAR. that is patently ridiculous. Opensource licenses under _no_ circumstances preclude the copyright holder from retaining that copyright. That is a huge, huge issue. Anyone who contributes to binarycloud retains their copyright and they may license their code however they please. I have _never_ever_ seen any other opensource project run that way. I'm hoping that you are mistaken, i.e. that it is not the intent of the PEAR founders to force contributors to relinquish copyright. If your statement is true, i.e. I must sign over my copyright to the PHP Group, it is impossible for my company to ever contribute any code to PEAR. > I sensing that we're all beating a dead horse here. Most people seem > to think that PEAR should be a repository of useful code classes. They > don't (won't?) dictate the way users should program their end applications. > Larger applications -- and framework applications that let you develop > other applications -- should build upon PEAR classes, but shouldn't > be a *part* of PEAR. I agree, but unlike the template thing this horse is far from being dead. What I would really like to see is some sort of concrete statements from those that control the direction of PEAR. I haven't gotten that yet. > It's not quite analagous, but all Perl modules don't have to be part of > CPAN. I'm know there are companies that release proprietary modules > that follow the standard format (in terms of installation, documentation, > etc.). Absolutely. But as I stated a while ago, the entire purpose of releasing binarycloud under the GPL was to foster cooperation and improvement of the opensource, free PHP codebase. Going our own separate ways, while it is _possible_ in my opinion is foolish. > Just like you aren't going to contribute binarycloud code, I'm not about > to contribute all of the work I've done for easyDNS to PEAR. However, I there is a huge difference there: binarycloud was released (and will continue to be released) under the GPL, and the copyright holder for (most of) the code will be the turing studio, inc. other code mixed in is credited to the authors. I'm specifically asking if I must relinquish copyright to the PHP Group for any code I contribute to pear. if the answer is "yes you must relinquish copyright" this conversation is over. if the answer is "no, you don't have to" the conversation continues :) > will contribute some of it, because a) I think it's useful to others and > b) I'd like to "share the burden" of maintaining it ... or atleast get > other people's opinions on how to improve it. Apart from all this, I may > choose to use PEAR's standard format when coding my own applications. > And I certainly will use other PEAR modules to build my apps. As I intent to use some pear libraries in binarycloud. > PEAR should be this "standard format", but whatever high-quality code > people want to contribute to the cause. > > I think we are all saying the same thing. My 2.5 cents. We kind of are, but it's all a little fuzzy and foggy right now, I'm seeking some clarity. Can anyone provide it? > -- > Colin Viebrock > Co-Founder, easyDNS Technologies > http://www.easyDNS.com/ > > > -- > PHP Extension and Add-on Repository (PEAR) mailing list. > Documentation can be found at http://pear.php.net/doc/pear.html > To unsubscribe, e-mail: php-pear-unsubscribe@lists.php.net from the > mail address you subscribed with. >