Re: Debian request to change the PHP license for Extensions

> Hi! > >> Who would benefit from filing a lawsuit on the basis of that part of the >> license? If not enforcing it anyway, is it useful? Removing a rule would >> certainly make it easier to understand. > > Nobody's filing any lawsuits so far. We're just asking if you're > developing some software based on PHP, please do not call it PHP, > because we've already got one PHP. Call it something else. Why do you > think it's not a reasonable thing to ask? > > I agree that this rule is somewhat vague and not always enforced since > there are tons of "Foobar PHP SDK" - which has to be "Foobar SDK for > PHP" (which btw Facebook got right as this is exactly how they call it, > but not everybody is so nice) - but changing license is a big > undertaking and I'm not sure it's worth going there just so somebody > could call their extension "PHP" and cause lots of confusion. I think it would be reasonnable to leave that to a trademark registration, and out of the software license. At the same time, I don't think I've seen anyone start a project called Python, Java, Perl, or anything like this in the last 10 years. I get your point (and Pierre's), and I understand Debian people are a bit extreme, and that they should have mentioned that before. I'm just trying to see if there is a way to avoid some stuff that might not be necessary.