Re: PHP Extension authors - please join the PECL community
| From: | Wez Furlong | Date: | Fri, 19 Sep 2003 13:31:32 +0000 |
| Subject: | Re: PHP Extension authors - please join the PECL community | ||
| References: | 1 2 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-15@lists.php.net to get a copy of this message | ||
One of the policies I'd like to keep for PECL is not to be over-organized.
Too many rules and too much red-tape gets in the way of people doing useful
things.
So, I don't think we really need any rules or proposals on how to name the
extensions - provided the name is logical, that should be fine. If you are
worried about possible conflicts with your extension, just pick a name that
isn't likely to collide - use your common sense.
I don't want to see 20 message long threads where people are discussing the
pro's and con's of foo vs libfoo, or bar vs baz. Not only does it waste
time, it generates noise and reduces the usefulness of the mailing list.
Just pick one and commit it :)
There is magic that can be done in the CVS repository if a major naming
problem arises - so its not a big deal.
If you haven't already, sign up for PHP CVS account here:
http://www.php.net/cvs-php.php (yes, it's really
difficult to find that
page!) and we can get the ball rolling for your extension.
--Wez.
----- Original Message -----
From: "Xavier Noguer" <xnoguer@xavier-noguer.com>
To: "Wez Furlong" <wez@thebrainroom.com>; <pecl-dev@lists.php.net>
Sent: Friday, September 19, 2003 2:11 PM
Subject: Re: [PEAR-DEV] PHP Extension authors - please join the PECL
community
Wez Furlong <wez@thebrainroom.com> escribió
> - Can *anyone* host their project in PECL?
> Sure. The only proviso is that the project is useful for something. If
> you already have karma, just go ahead and commit it. If you don't, or
> you don't have a CVS account, you need to apply for one. This requires
> intervention from "big brother" - he is generally a nice guy, but might
> decide not to allow your project if there is a valid reason for that.
Hi, I was wondering if a proposal should be made, at least for extensions
that are not a wrapper around a library. An extension for libfoo will be
named
foo of course, but if it is not a wrapper there could be a conflict of
names.
In particular I want to add valkyrie (VALidation Kit for Your Request Input
Extension) to pecl (see the pear-dev thread here:
http://marc.theaimsgroup.com/?t=106382304000002&r=1&w=2).
Is there any
possible future name conflict anyone is aware of?
Xavier
http://www.xavier-noguer.com/