Re: proposal: HTML_Template_ReIT, round 2

Sorry, but I've got to say -1 here. It's been said already, but Alexey why not just humour Pierre-Alain and create patches? This is the one thing he's asked for all along. Who cares if they're large, that's what he has asked for because that's what he feels is easiest for him to integrate into IT. Now I know Alexey has done an awful lot of work on IT in the past months, including a much needed test suite (way to go, btw). Perhaps if a merge was to happen in stages it could happen more peacefully? What if we outlined a series of changes that would gradually take place, for the sake of IT, its users, and both Pierre-Alain's and Alexey's time? Something like this: 1) Add the test suite to IT. Since there wasn't one before, there's no need for patches. Any changes necessary here should be made without thought to the rest of the changes. The test suite should reflect the *intended* behaviour -- strange or not -- of IT. This would also pave the way for proof that the rest of the changes do not break B/C. 2) The changes that fix supposed bugs should go first. These should be small, and patch-able. Whether all these make it or not, that is of course up to Pierre-Alain right now, and assuming they pass the new tests I don't see why they wouldn't be accepted. 3) The larger changes can then be done one-at-a-time, and any changes that Pierre-Alain does not feel should be part of the main IT package can always be integrated via an extended package. That would be a win for everybody. People who don't need caching, for example, or who are content with Cache_Lite or something else, or already wrote their code with another Cache package, don't get the extra unused lines of code, even if it's only 15-30 lines. That's beside the point. Choice is the key here, and we're talking about the *user's* choice. That's what Pierre-Alain's concern is and has to be -- the users of IT. If IT is to remain small and light, then let's do away with any built-in functionality that not everyone wants. Extended packages can easily be loaded when the extra features are wanted. I have no personal problem with caching being in IT, but some do and they happen to be the most vocal users. Other packages have no problems dividing themselves into basic/full, so why can't IT be the same way? That's my view of it, and I'm not even an IT user (at the moment). :) So Pierre-Alain, Alexey, what do you say? Lux On Wednesday, February 26, 2003, at 11:39 PM, Alexey Borzov wrote:

Greetings! As Pierre-Alain Joye managed to drown Yet Another thread in useless flames, I'll start a new one. Please vote for my proposal to add a fork of HTML_Template_IT into PEAR as HTML_Template_ReIT. And please just vote, do not try to reason anyone. There is a +1 already, 4 to go. Now, on to some background: 1. The biggest problem in "cooperating" is that Pierre-Alain does not have time/knowledge/whatever to work on IT[X] himself and does not want to let me work on it. Well, I don't like him either, so this is somewhat understandable. 2. Pierre-Alain is writing bullshit and (unfortunately) knows it. I already created unit tests to check for BC. And after that I not only fixed some incompatibilities, but found several bugs in stock package. If Pierre-Alain was not busy writing bullshit, but actually coding, he could have fixed them by now. I sincerely doubt that "careful review" of patches would add a lot to BC. 3. On to small patches bullshit. I don't want to "make small patches" for three reasons: a. It is impossible to make them small b. I doubt that they will ever be applied; c. If they do, I don't want _my_ work to bear _only_ Pierre-Alain's name, sorry (see 1. for reference). I have time/wish to work on IT[X] now, but please remember, that PEAR is not my fulltime job either. I already proposed my changes 5 months ago and Pierra-Alain promised to review/integrate/whatever them. Guess what? He never actually bothered. I am sure that as soon as you stop pestering him, my proposed patches will go to /dev/null Thus I want to have a separate package, so I wouldn't _have_ to cooperate with people not wanting to cooperate. -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

-- John Luxford President and Chief Developer ______________________________ SIMIAN systems Driving Web Content Management ______________________________ web : http://www.simian.ca/ email : lux@simian.ca phone : 204.452.8537