Re: Re: Bundling third-party libraries

On 6/7/06, Derick Rethans <derick@php.net> wrote:

Lukas Smith wrote: Derick Rethans wrote:

This is not to say that eZ components are bad per se, its just that it means that there will be difference that will make it harder for users to adopt the packages.

That is a bit of a weak point in this case. As PHPUnit is a tool and not a general use code package. So users don't really see the difference here.

It is an important point though since a lot of people want to be able to mess around with the source in order to check, extend or simply read the source. Also our QA team might need to pickup things (lets say eZ drops support for its current stuff because PHP6 is out and you guys decide that you want to be PHP6 E_STRICT compliant). That is hypotetical ofcourse :) We have no control over this. However we put a lot of effort into committing to our users and making sure that the entire code is maintained and/or there is a clear and reasonable upgrade path. This is what Pierre was talking about in regards to QA. Sure, but in that case the package maintainer can decide whatever he wants to do. In this case it would be Sebastian's reponsibility to find a good alternative and or solution for example.

You're also assuming that Sebastian will be around. He may have left PEAR for other things or even left PHP altogether to do something else. We have had abandoned packages before and we, as PEAR members, try to keep all packages maintained whether or not there is an active maintainer for them. The QA team especially is supposed to be doing this. To import external packages with a different coding style, different packaging, etc allows for much harder matinenance in the case of the package being abandoned. -- Justin Patrin