Date: 07/21/01
- Next message: Arno A. Karner: "[phplib] php where to go next"
- Previous message: giancarlo pinerolo: "Re: [phplib] [RFC] Future of phplib"
- Next in thread: Björn Schotte: "Re: [phplib] phplib - what is the point?"
- Reply: Björn Schotte: "Re: [phplib] phplib - what is the point?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
ok,
We have several issues to solve with phplib: (let's talk about the main ones)
1) various bugs not fixed
2) no new release for a while.
So we need more developers with an access to the CVS server to apply the
patches. More people to work on it, and a maintenor (one by part ?) with a
lot of free time to do his job.
If sourceforge can help for that, I think everybody agrees that we need to
go forward.
I think that at the first stage, we need to release a new version with
every patches.
Then, we will be able to decide:
- if we keep our database layer, or use the one from pear
- same thing for the templates
- what about the forms? to put them in PEAR
- and so on
Rigth now, there is not so much examples/documentation about how to use the
functions from Pear. That is an advantage for PHPLIB. For the rest, I don't
want to get in the debate.
Stephan
-- Abbestellen mit Mail an: phplib-unsubscribe <email protected> Kommandoliste mit Mail an: phplib-help <email protected>
- Next message: Arno A. Karner: "[phplib] php where to go next"
- Previous message: giancarlo pinerolo: "Re: [phplib] [RFC] Future of phplib"
- Next in thread: Björn Schotte: "Re: [phplib] phplib - what is the point?"
- Reply: Björn Schotte: "Re: [phplib] phplib - what is the point?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

