Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
en:philosophy:php_trademark [2023/08/22 22:12] throgh [What is the problem?] |
en:philosophy:php_trademark [2024/01/17 01:10] (current) throgh [Solutions] |
||
---|---|---|---|
Line 10: | Line 10: | ||
[...] | [...] | ||
- | 3. The name " | ||
- | | ||
- | | ||
- | |||
4. Products derived from this software may not be called " | 4. Products derived from this software may not be called " | ||
may " | may " | ||
Line 19: | Line 15: | ||
| | ||
it "PHP Foo" or " | it "PHP Foo" or " | ||
- | |||
- | 5. The PHP Group may publish revised and/or new versions of the | ||
- | | ||
- | | ||
- | Once covered code has been published under a particular version | ||
- | of the license, you may always continue to use it under the terms | ||
- | of that version. You may also choose to use such covered code | ||
- | under the terms of any subsequent version of the license | ||
- | | ||
- | the right to modify the terms applicable to covered code created | ||
- | under this License. | ||
[...] | [...] | ||
Line 37: | Line 22: | ||
Those restrictions specifically related to use of the PHP name. Ultimately, such licensing makes extra work for system-distributions and operating-systems and creates uncertainty for people wishing to modify PHP - as they navigate a license that awkwardly pulls in a trademark policy as part of it. | Those restrictions specifically related to use of the PHP name. Ultimately, such licensing makes extra work for system-distributions and operating-systems and creates uncertainty for people wishing to modify PHP - as they navigate a license that awkwardly pulls in a trademark policy as part of it. | ||
- | In the whole outcome and as result **PHP violates the freedom to redistribute without “explicit” approval**. | + | In the whole outcome and as result **PHP violates the freedom to redistribute without “explicit” approval**. |
- | < | + | So if we would do individual modifications corresponding our mission-statement, we would always |
- | Once covered code has been published under a particular version of the license, | + | ===== Solutions ===== |
- | you may always | + | |
- | </ | + | |
- | So if we would do individual modifications corresponding our mission-statement, we would always have to ask and have nevertheless | + | * **Rebranding** the entire language to avoid the trademark restriction. However, we would need **patches** |
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | |||
+ | Hyperbola has taken the decision to keep PHP complete out of the repositories, | ||
===== Outcome and decisions for Hyperbola ===== | ===== Outcome and decisions for Hyperbola ===== | ||
The Hyperbola-project decided to completely remove PHP from its packages since the release of version 0.4.3 for **Hyperbola GNU/ | The Hyperbola-project decided to completely remove PHP from its packages since the release of version 0.4.3 for **Hyperbola GNU/ |