Re: Criteria for inclusion of code into main-stream PHP
| From: | Jim Winstead | Date: | Fri, 21 May 1999 16:42:08 +0000 |
| Subject: | Re: Criteria for inclusion of code into main-stream PHP | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-5846@lists.php.net to get a copy of this message | ||
Right now, contributing code for inclusion in PHP3 is pretty easy --
either fill out the form at http://www.php.net/cvs.php3 to
get an
account on the CVS server to add the code yourself, or submit the
code to php-dev and find someone with CVS access who is willing to
commit it.
For PHP4, it will be much easier to distribute third-party extensions
to PHP, so it is likely that there will actually be fewer extensions
delivered with PHP, allowing extensions to follow their own release
schedules and be more closely associated with their "owner".
Jim
On May 21, Troels Arvin wrote:
> Hi,
>
> Our company participates in the development of a credit card clearance
> system. It's a library ("CashCow") under the LGPL license:
> http://www.cashcow.dk/
>
> We have written a PHP-function that uses the CashCow library to clear
> transactions with "Danish Payment Systems" (PBS); that part of the code
> is GPL, of course. Everything seems to work well. If you want to have a
> look at it, you may download the binary/source PHP-RPMs that we have
> created (combination of PHP, MySQL and CashCow as an Apache-plugin):
>
>
> http://download.cashcow.dk/source/mod_php3-mysql-cashcow-3.0.7-1.src.rpm
>
> http://download.cashcow.dk/rpm/mod_php3-mysql-cashcow-3.0.7-1.i386.rpm
>
> I can also post the relevant PHP code here (a c-file, a header file and
> some patching for ./configure, etc.), if you prefer it that way.
>
> More information about the project is available at
> http://www.cashcow.dk/
>
>
> Now, what are the criteria for code to be part of the main-stream PHP
> package? Is there any chance that our cashcow functions could be part of
> the code? - That would make it a bit easier for us to maintain RPMs,
> documentation, etc.
>
> At this time, CashCow is mainly of interest to programmers/web-masters
> that want to provide a Web-based cash register for Danish customers.
> However, the protocols that the CashCow library mediates, is based on an
> ISO standard; and it would surprise me a lot if little Denmark would
> have invented it's very own system for clearances. In other words: I
> hope and expect that the CashCow library could evolve into a more
> general, open source payment clearing system - not only for Danish
> consumers.
--
PHP Development Mailing List http://www.php.net/
To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net
For help: php-dev-help@lists.php.net