Re: [phplib] [RFC] Future of phplib From: Jason Belich (phpliblist <email protected>)
Date: 07/21/01

Nate,

Sign me up to help. My work has brought me back into a position where
I'm writing more classes which can be useful to the PHPLib community.
I've already got a few classes (XML & shmop related) which can go into
CVS. Also I have mapped out (but not coded) an auth replacement which
is an implementation of ACLs but is backward compatible with the current
auth, and modified the login stuff so that it A) uses templates and B)
returns a meaningful error message.

KK is right, the best thing to do is to put out a new version of PHPLib.
My vote is the best way to do that is to have all the great tools over
at Sourceforge at our disposal. But let's be reminded that Sourceforge
is a set of tools, nothing more. Building PHPLib beyond the great tools
we've all been using is going to take everyone's participation, from
planning to coding to testing!

I've been using PHPLib for around 3 years now. I watched the
discussions back in March, and I'm distressed nothing's come of it. I
don't intend to just let it die in the face of PEAR's dogmatic regime. 

--
Jason E Belich
Director of Product Development
and Technology
Third Level Media, Inc.

----- Original Message -----
From: "nathan r. hruby" <nathan <email protected>>
To: <phplib <email protected>>
Sent: Saturday, July 21, 2001 12:07 AM
Subject: [phplib] [RFC] Future of phplib

> I love PHPLib.  It's fast, flexible and fairly elegant.  It is
> pleasant to work with.  The PHPLib community is smart, and forgiving
> of my ranting and raving here.  I hope you will all continue that
> trend after reading this.  :)
>
> I hate the fact that there hasn't been a release in over a year.
> Kristian and Ulf have abandoned PHPLIB for new ventures -- that
> was evident last year and made official at the start of this year.
> I wish them luck in their new ventures.  They have created something
> great with PHPLib.
>
> In an attempt to let PHPLib down slowly Kris and Ulf tried to get
> PHPLib ported into PEAR.  As we all know (or at least should know)
> PHPLib won't be ported to PEAR in any form that will be usable with
> the current body of code that exists for it.  Some of the HTML bits
> might make it in if someone makes them PEAR-ified.  Session, Auth,
> Perm, DB_Sql, Template and such will die.
>
> Giancarlo's posts about both the recent security hole and questions
> about making a standard method of implementation went, for the most
> part, unanswered or with little discussion.  This is something,
> even six months ago, which would have elicited a much larger response
> from this audience.  So the question is:  Is there a PHPLib community
> anymore?  Are there people out there who want to see PHPLib continue?
> Do *YOU* care, or have you just started modifying PHPLib to your
> taste without sending patches or anything back?
>
> Max has done some work on PHPLib-ifying PHP4 native sessions and
> Ulf has been poking away at a much needed and promised
re-implementation
> of OOForms.  I've worked on the web site, Chris has fixed some
> bugs, but really I think that we feel a little lost, lacking in
> direction from both the community and the previous developers.
> Has PHPLib reached the end of its life cycle?  Two people fooling
> with projects they need for their own work does not a library make.
>
> I personally have a lot of time invested into PHPLib and would like
> to see it continue.  Not just for phpSlash, but for my other projects
> and as an alternative to PEAR.  Yes, I have my complaints about
> PEAR, but they are mine.  I do feel, however, that a lightweight
> alternative such as PHPLib still needs to exist.
>
> So I propose we move PHPLib to SourceForge.  Infrastructure-wise
> it can't be beat and it will hopefully attract some of you all to
> contribute a little more.  Maybe it will attract a few more others
> from outside the PHPLib world.  Furthermore, it will allow many
> people to keep track of PHPLib, not just the one or two that are
> doing it now.
>
> Part of this proposal is a call for help.  I would not want to see
> PHPLib move to SourceForge and have it languish as it is here.  So
> I am asking other members of the community volunteer a little time
> and help out with stuff.  If you have patches, send them in.  If
> you have time, request to be a part of the group and verify / commit
> patches.  Develop stuff, make things work the PHP4 way, document
> things, whatever, but please help!
>
> To start it off, if there is agreement, I will volunteer the next
> week or so to getting the SourceForge account set up, getting CVS
> imported, making new mailing lists, moving the web site, making an
> announcement, releasing a new PHPLib with a fix for the security
> hole, etc.  I ask that before this happens some other folks could
> volunteer for being a patch wrangler, or to beautify their favorite
> class, or to volunteer their own classes, etc.  Or else there will
> be no one to maintain the moved PHPLib and thus the move will be
> pointless.
>
> If there is no agreement I will simply release the patched version
> on the PHPLib web site, and hand over the admin of the site to
> someone else.
>
> -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>
>
>

-- 
Abbestellen mit Mail an:   phplib-unsubscribe <email protected>
Kommandoliste mit Mail an: phplib-help <email protected>