You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#84 needs extracting the definition of sapi_globals_struct from php-src/main/SAPI.h, and this file is licensed under the PHP license.
And the 4th clause of this license forbids the use of names like "PHP Foo" or "phpfoo" without permission.
Currently, the name of this tool is "php-profiler", so this tool cannot use the definition from files licensed under the PHP license.
There are some options.
a. Changing the name of this tool
b. Getting written permission from [email protected]
c. Avoiding the license problem through binary analysis
It seems that phpspy uses the plan c.
I'm not sure whether this is a legit solution.
I've already sent an email to [email protected] asking the permission. But it seems that the mail doesn't appear in any public mailing lists available, so I guess only a limited number of people can read it, thus it unlikely guides the consensus from the community.
So the last option I have to speed up the tool (via #84) is changing the name of this tool.
Currently, I can't think of a good name for it though. :(
The text was updated successfully, but these errors were encountered:
#84 needs extracting the definition of sapi_globals_struct from php-src/main/SAPI.h, and this file is licensed under the PHP license.
And the 4th clause of this license forbids the use of names like "PHP Foo" or "phpfoo" without permission.
Currently, the name of this tool is "php-profiler", so this tool cannot use the definition from files licensed under the PHP license.
There are some options.
a. Changing the name of this tool
b. Getting written permission from [email protected]
c. Avoiding the license problem through binary analysis
It seems that phpspy uses the plan c.
I'm not sure whether this is a legit solution.
I've already sent an email to [email protected] asking the permission. But it seems that the mail doesn't appear in any public mailing lists available, so I guess only a limited number of people can read it, thus it unlikely guides the consensus from the community.
So the last option I have to speed up the tool (via #84) is changing the name of this tool.
Currently, I can't think of a good name for it though. :(
The text was updated successfully, but these errors were encountered: