Re: Payment_Process documentation is worthless

I am working on addressing the problem. I recently started my own company and we are finishing a contract for a eCommerce web site we built using a lot of PEAR packages: Payment_Process, and my yet proposed Services_Shipping being the bulk of work and time spent. I'm going through the AuthorizeNet part of Payment_Process, which is the only part we are going to use for the time being and will make some DocBook that at least flesh out how to get payments, AVS, and SSL figured out among some other basics. I will host the materials and make them public on my company website while I propose the changes and go through the motions. It should be done by the end of this week. I am not going to put out any documentation about how to use a credit card API without ensuring it's practices are safe for a production environment. (Read: I am not liable!) In specific I want to ensure that the documentation provides a safe way to authorize and capture as well as address verification (AVS). Kristopher Ives, Santiance Corporation On Mon, Aug 4, 2008 at 11:49 PM, till <klimpong@gmail.com> wrote: > On Mon, Aug 4, 2008 at 8:36 PM, Daniel O'Connor > <daniel.oconnor@gmail.com> wrote: > > On Mon, Aug 4, 2008 at 8:49 PM, Kristopher Ives > > <kristopher.ives@gmail.com>wrote: > > > >> The package also lacks tutorials, which is likely the first > >> the needed for this package. > >> > > > > Hey Kristopher, if you've got a specific tutorials you'd like to write, > > don't hesitate! I'm sure that if they ended up on a wiki or blog > somewhere > > else collaborative, we'd all love to help polish them into something > usable. > > > > I'll certainly lend a hand if you can get the ball rolling... > > Kristopher, > > I just wanted to add the same. > > If you write a tutorial/howto/whatever, I too can help to roll it into > the necessary XMLs to make it appear on pear.php.net. :) It would be > awesome if you contributed that to the package! > > Till >