Re: [PHP4BETA] PEAR (was: php and MS SQL Server....)
| From: | Paul DuBois | Date: | Fri, 03 Mar 2000 00:20:52 +0000 |
| Subject: | Re: [PHP4BETA] PEAR (was: php and MS SQL Server....) | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-11414@lists.php.net to get a copy of this message | ||
At 7:40 PM -0200 2000-03-02, Manuel Lemos wrote:
about. If people don't want to let others have access, they don't need toThey're not coercing anybody. No one is forced to contribute to PEAR. If they were, your argument might have some merit. If you don't like the arrangements, you don't submit code. Perhaps I'm wrong, but it seems as simple as that.put their code into PEAR. We won't force anybody.You and your Open Source mania. Just because you have put PHP in Open Source it doesn't mean that it is right to coerce people to do the same.
The way you you are putting it Open Source follow the communist model. Follow me and tell me where it doesn't match: If you want to be part of the community, you have to give in your code or else you won't be accepted in.Every community has rules or guidelines. As far as I can tell, you're saying you don't like those guidelines and that they should adopt the ones you prefer instead. In other words, you don't like the guidelines and don't want them imposed on you, so instead you want to impose yours on them. I guess I don't see how what you want is any different than what you are objecting to. What I don't get about this flurry of messages in which you're expressing your objections, is that you already have your own repository, and one that appears to be fairly successful. I assume that you intend to continue this repository, so why is it an issue whether or not PEAR exists?
a bad thing, and code can live in 2 trees rather easily. There is also noIs that the basic issue for you? You want control over your code. Here again, you want to make the rules - no one can contribute to the development of your code without your permission. So, basically, you're not really that interested in collaborative development unless you get to call the shots? -- Paul DuBois, paul@snake.netreal requirement to have all PEAR modules live in the PHP code base. You could for example make all your classes PEAR compatible and distribute them separately with a simple install script that sticks them into the right place so people can do a 'use blah'. This stuff is making your life easier, not harder. I really don't understand what you are bickering about.This is good. What I don't want is to have to give up the control of the development of my code to have it accepted in PHP code base.