Re: name for "new" IT[X] package: HTML_Template_ReIT
| From: | Bertrand Mansion | Date: | Wed, 26 Feb 2003 16:54:19 +0000 |
| Subject: | Re: name for "new" IT[X] package: HTML_Template_ReIT | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-13933@lists.php.net to get a copy of this message | ||
<paj@pearfr.org> wrote :
> On Wed, 26 Feb 2003 11:15:04 -0500 (EST)
> "Adam Morton" <adam@tux.appstate.edu> wrote:
>
>> It may just be me, but I really don't like the proposed name
>> HTML_Template_ReIT. It seems illogical and unprofessional to declare
>> a package a rewrite of another existing package, when the existing one
>> is currently in use. The name suggests that it is a replacement for
>> the current system. Maybe I'm not understanding this thread at all,
>> but I thought this proposed package was an alternative to be used by
>> choice, not a replacement?
>
> I do not think PEAR is a script repository "a la" hotscript or CPAN. As
> I said, I will work on IT asap, to add the needed stuffs.
>
> We asked many times about small patches to add them to the current
> package faster, he never provided them and he does not want to.
>
> A competitive package is a good thing if it proposes a different
> approach to the same problem. This is not the case here. That's why I am
> strongly against this addition, for IT or any others PEAR packages.
>
> How to contribute to PEAR is clearly explained in the documentation and
> in the FAQ. I do not see any good reason to change it.
>
> As he did not provide patches, and it seems that some of the requests
> are needed (things I never said he was wrong, except the cache), that
> will be done soon, or later.
>
> As a sidenote, people may not forget we are not fulltime for PEAR, and
> not fulltime for a specific package.
Alexey is not "fulltime for PEAR" neither so please consider the work he has
done and re-done. Now you know his changes don't break BC so will you commit
these changes ?
Personally, I don't remember how and when it was decided you would be the
maintainer of IT. I don't really care but if the project is stuck because
you don't have time to commit the changes or make some tests, it might be
the right time to switch for a more active maintainer ?
There are other packages that you maintain and know better because you wrote
their code, with which you will probably be more at ease. Having too many
package to maintain is not easy and takes a lot of time, especially when
some are not complete.
Anyway, this situation is slowing my own developments with QuickForm because
I need to know which version of IT to use for the template bridge I want to
make. If you could at least give some time indication, that would be great
(instead of "that will be done soon, or later").
TIA
Bertrand Mansion
Mamasam