Copyright Question

From: Date: Wed, 06 Jan 2016 01:07:31 +0000
Subject: Copyright Question
Groups: php.doc.license 
Request: Send a blank email to doc-license+get-384@lists.php.net to get a copy of this message
Hello, My name is Ryan Cantalupo. I wanted to inquire regarding copying and/or paraphrasing portions of information from the PHP Manual, in a commercial/corporate setting. For example, in describing a fix for a problem, I made mention of the php functions empty() and isset(), and in that mentioning I described how those functions worked by paraphrasing/rewording or copying parts of the descriptions of those functions from the PHP manual (http://php.net/manual/en/function.isset.php and http://php.net/manual/en/function.empty.php). There were a couple of comments/descriptions I wrote that mentioned these functions, and in some areas I put the two URLs I pasted in above to specify where I got that information. Since the Creative Commons Attribution 3.0 License requires more information than what I put, I was wondering how best to properly attribute the information I wrote (see an example? The descriptions I had written are not available to the general public or distributed within a product as far as I am aware, but are available to be seen by coworkers of mine. An example of one of my comments/descriptions: From http://php.net/manual/en/function.isset.php and http://php.net/manual/en/function.empty.php, isset() returns True if the variable exists (probably if it has been declared) and if it has a non-NULL value. The empty() function returns True if the variable either does not exist, has a value of NULL, "" (empty string), 0 as an integer, float (0.0), or string/character ('0'), or FALSE, is an empty array, or is declared but not initialized (no value). If the variable is both set and empty (exists and falls into one of the above categories other than NULL), .... I don't believe I have the ability to edit every comment/description previously written, but would it be acceptable if I created a new comment/description that addresses those prior ones that may not be able to be edited and post the proper attribution? If there are other areas in which I discover I did a similar thing, whether in code or in comments/descriptions outside of code like the above example, should I approach posting attributions in the same manner as I should approach the above example? Also, are there cases where a statement is general enough not to require the attribution? For example: "If the variable is empty but set (exists and not NULL), ..." Thank you for your help, Ryan Cantalupo

« previous php.doc.license (#384) next »