Re: an HTML_Template_IT[X] fork is available
| From: | Markus Wolff | Date: | Tue, 11 Feb 2003 16:57:44 +0000 |
| Subject: | Re: an HTML_Template_IT[X] fork is available | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-13117@lists.php.net to get a copy of this message | ||
Okay guys, cool down. Both parties have some points where they are
right and some where they are not. Time to settle down and look at the
issue objectively.
This is what Bertrand wrote:
> le 11/02/03 17:06, Pierre-Alain Joye à paj@pearfr.org a écrit :
>
> > On Tue, 11 Feb 2003 18:58:29 +0300
> > Alexey Borzov <borz_off@cs.msu.su> wrote:
> >
> > To be clear, quick and full of irrespect as you are.
> >
> > Feel free to propose your work as an alternative or whatever you want,
> > but forget to commit anything there.
>
> I don't see why you should decide for all of us.
>
> After all, when Alexey first posted his fork, you have had some time to look
> at it and reply to him. You never did, even after having said you would. I
> found your behavior quite irresponsible and impolite.
>
> Personally, I contributed more to ITX than you ever did...
> If the addBlockFile() method worked in the first place, it's because I took
> some time to fix it:
[...]
> IMO, you shouldn't even be allowed to give your opinion on this fork !
I would certainly not go this far. What would you say if you´d have to
invest so much time into a project at work that you can´t develop your
own packages any further for some time, someone else takes over in the
meantime and then states that you don´t have anything to decide
anymore?
Also: Not actively developing a package does not mean that you´ve
abandoned it - every project needs someone who will look over it and
coordinate efforts of developers who are willing to work on it (well,
if there´s more than one working on it at the same time, that is).
Christian Dickmann seems to be with me on this one:
> > 'Cause here we have a person, who is named "lead developer", yet have done
> > nothing to actually develop
>
> IT is widely used and stable. Changes should be done carefully.
> The lead developer has to manage this process, so that no newcomer
> comes and changes IT by just passing by.
>
> > and is now clearly saying that he will not allow
> > outside contributions from persons whom he does not like.
>
> He is the lead developer, he has all the right to say "no" to your
> work! Fork and choose a diffrent Package name or an other
> repository if needed.
> If he likes you or not is just no point of discussion.
Another thing: Copyright. Please correct me if I´m wrong here (I´m not
that much into legalese), but I´ve always had the impression that if
someone writes code and publishes it under a public license, he
technically still owns the copyright (which gives him the possibilty
to approve/disapprove changes and/or change the license if he wants -
something that has happened before in other projects). So technically,
no one else but the initial "inventor" will ever be able to "force"
anything to go into the _original_ project.
Okay, enough of that. Every coin has two sides, and I also think that
Pierre-Alain _might_ have judged too quickly. As Christian has pointed
out in the meantime, while there are some disadvantages in the new
version, there also are some cool additions in there.
Why reject additions that make sense just because some features don´t?
A possible solution could be the introduction of a factory method in
IT[X] - you could then choose if you want the cached version or not.
There was some talk about a PECL extension for fast template parsing
that could be used to seriously speed up IT[X], which has raised the
idea of introducing a factory method before (btw. does anyone know
what became of this extension?).
On the other hand, if the new version differs from the existing IT[X]
too much (both in code and in BC), then it won´t do any good to try
and merge the two - you´d either have to make two packages or rewrite
the good additions for the existing package.
Still, Pierre-Alain as lead developer, project manager, copyright
owner or however you wish to call his position, should have the final
word on this one - but it should be made clear for what reasons the
changes are not accepted, a simple "no" is not enough IMHO.
Regards,
Markus
--
*21st Media* | Consulting, Konzeption, Produktion für die Bereiche:
Markus Wolff | Internet, Intranet, eCommerce, Content Management,
Hamburg,Germany | Softwareentwicklung, 3D-Animation, Videostreaming
http://21st.de | Tel. [+49](0)40/6887949-0, Fax: [+49](0)40/6887949-1