Date: 07/24/01
- Next message: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Previous message: Chris Johnson: "RE: [phplib] [RFC] Future of phplib"
- In reply to: Chris Johnson: "RE: [phplib] [RFC] Future of phplib"
- Next in thread: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Reply: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Everybody, please shut up.
The Pear / PHPlib debate is over. PHPLib is not, as far as most of the
people on this list are concerned, migrating to PEAR in the near future.
I think it is clear to most here that there are issues with both PEAR and
PHPLib prgamatically and phliospohicly and those issues need time on both
sides to be addressed fully. Till then PHPLib will continue advancing and
doing it's thing, as will PEAR, both teams drawing from each others wisdom
and code. This is a happy caease-fire, please let's keep it that way.
Bjorn, if you feel you must fork PHPLib to PEAR becasue of some
over-zealous feelings about what *you personally* feel is right about
others people's code, do it; it's a free world and I can't stop you.
However, please do not continue this thread about migrating to PEAR,
please stop insulting a very large group of talented developers, please
stop trying to troll for a flame war. If you have nothing inteligent to
add to this list about PHPLib, it's use or advancement I would suggest
leaving it.
You evidently don't remember or didn't read / partcipate in the pervious
battles in the past months over this topic. You do not understand the
intrisincs that the two groups have (and the diffrences of them) or seem
to have a clear conception of the phplib codebase as a whole (and the
issues that the PEAR group has with that codebase). I would sugges, if
you are going to stay on this list, going back to the MARC archives for
php-pear and pear-dev and phplib and phplib-dev and re-reading those
threads to understand the history and to see some conrete specs about why
some of the migration wouldn't work.
For the rest of the list, I will ask you all to refrain from responding to
any other comments about this. Let's not perpetuate a bad vibe any
further.
-n
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- nathan hruby / digital statement nathan <email protected> http://www.dstatement.com/Public GPG key can be found at: http://www.dstatement.com/nathan-gpg-key.txt ED54 9A5E 132D BD01 9103 EEF3 E1B9 4738 EC90 801B -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-- Abbestellen mit Mail an: phplib-unsubscribe <email protected> Kommandoliste mit Mail an: phplib-help <email protected>
- Next message: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Previous message: Chris Johnson: "RE: [phplib] [RFC] Future of phplib"
- In reply to: Chris Johnson: "RE: [phplib] [RFC] Future of phplib"
- Next in thread: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Reply: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

