Hi, I completely agree with all the comments posted here, this is something that we need to take care internally. I've already added a new rule to our deployment script. To be honest, I skipped the entire Zend_Service_* part of the manual, so I wasn't familiar with these components and because we have plenty of space on our servers, storing them was never an issue. I think they are great components and it doesn't make sense to have them as a separate download, a link in the code should be more than enough.
Thanks for your help and solutions. Regards, Federico. On Fri, May 9, 2008 at 5:18 PM, Matthew Ratzloff <[EMAIL PROTECTED]> wrote: > I agree; a link in the code is a good compromise. > > Beyond that, this is a training issue if this is truly relevant to your > company, Federico. Otherwise, you can create a deployment script that > removes these components. > > -Matt > > On Fri, May 9, 2008 8:23 am, Matthew Weier O'Phinney wrote: > > Let's be crystal clear here: it is up to your organization and > > developers to use a service according to the terms of the service > > provider. Zend Framework simply provides classes to access these > > services should you find that you are compliant. > > > > As noted, we already link to the service provider in the manual; at > > most, I feel we may need to add those links into the class docblocks. > > It makes no sense to separate these components out to separate downloads > > or releases, and would only complicate our story, and make things less > > clear for other ZF users. > >
