-- Federico Cargnelutti <[EMAIL PROTECTED]> wrote (on Thursday, 08 May 2008, 05:01 PM +0100): > > Ultimately, the onus is on developers (consumers) to investigate and > understand what they're using. > > Yes, adding a URL to the T&C and/or license in the docblock would be ideal.
I could argue that since the links are in the manual, there's no need to do this. However, not everyone reads the manual, and it *would* be good to have this in the code. Please place an issue in the tracker requesting links to each service (note: not just AudioScrobbler) in the class docblocks. > On Thu, May 8, 2008 at 4:33 PM, <[EMAIL PROTECTED]> wrote: > > > >> And if this is the case, who is responsible of informing me? > > >> Regards, > >> Federico. > > > In my opinion, you are. > > Personally, I've never been in a position where I didn't check T&C > and/or license agreement of a service that I was consuming. I've never > simply "assumed" that I could use at will. > > I think putting the URL for the service in the component's docblock is > more than sufficient. Ultimately, the onus is on developers (consumers) > to investigate and understand what they're using. > > > > -- Matthew Weier O'Phinney Software Architect | [EMAIL PROTECTED] Zend - The PHP Company | http://www.zend.com/
