Re: [PHP4BETA] php and MS SQL Server....

> CVS? Why? AFAIK CPAN does not require contributors to put their code > under a CPAN managed CVS repository and I don't see a reason to have one. So when stuff breaks you have a chance of figuring out why it broke. Just because CPAN doesn't do it doesn't mean it isn't a good idea to do. PHP wouldn't be with us today without CVS. I don't see how PEAR modules would not get the same benefit. > I'm afraid that if you are requiring contributors to put their code in your > CVS repository, you are automatocally discarding many potential > contributors that a) don't know CVS and don't want to learn it to be able > to contribute b) already have their own CVS repository and don't want to > have somebody else to take over it. That's fine. > Unless you mean to put only PHP code of core developers in the PEAR, I > don't see much point in putting contributors code in a CVS repository. > A simple upload form would be much simpler and would leave out many of > the potential contributors as you only need a Web browser, not a properly > set CVS client. An upload form does not exclude the code ending up in CVS. > For instance my PHP classes repository, code is divided by packages. Each > author may upload one or more packages. Each package consists of one or > more files. Each package may be classified in one or more groups and each > author may change that classification any time. > > A good thing, and a reason for which I did not use PX to upload my code, is > that when a new class is added or changed, users subscribed to the site get > notifications by e-mail regarding the changes that were done. This saves a lot > of time to users looking for the latest version of their favourite classes, > and authors notifying everybody. Soon, I will have a page that lists the > lately uploaded classes for people that don't want to get the notifications > by e-mail. This also annoys a lot of people. We have discussed this before, but I refuse to register somewhere just to download code and as such your code repository is useless to me. PEAR will be widely mirrored as well as being on CD-Rom distributions. It is impossible to track every user, so there is no point trying. > Wouldn't it be more objective to first approach the authors of the existing > PHP repositories and suggest the necessary improvements? I have been > getting many improvement suggestions and as time as allowed I have been > implementing many of the good ideas that have been passed to me. Well, given that there is more than one, suggesting improvements to the various ones doesn't help anything when the goal is to have a single definitive one. The PX code is a repository of code snippets. The larger and more complete entries should eventually migrate to PEAR where they can be maintained and reviewed by a wider audience. I am sorry that you feel we are encroaching on your territory here, but we are simply responding to community feedback. People screamed for database abstraction and sessions even though various implementations were available elsewhere. Same goes for a centralized code repository. This doesn't mean that PHPLIB will go away, nor that your db abstraction layer nor your class repository will go away, it just means that the standard PHP distribution will now include basic session support, basic db abstraction and a basic code repository which allows people like you to do more interesting add-ons because you can now assume that people have a more capable base distribution. -Rasmus