I really, really fucking hate people using "Laravel {package-name}" for their packages when #TaylorOtwell said that you shouldn't.

If you have a package, use "My Package for Laravel". That's it.

It's fucking weird finding a package that you think is "official" when it's not.

#PHP #Laravel #Programming #Software #WebDevelopment #SoftwareDevelopment #Development #Technology

@darkghosthunter PHP gave up trying to enforce this same rule years ago.
@ramsey for extensions? Or composer packages?
@darkghosthunter For anything
@darkghosthunter It probably doesn’t seem like such an issue now, but long before dependency managers like Composer, most software written in PHP was distributed in zipped packages, and they were full applications that you’d unzip into the web root and run. Lots of them used names with PHP in them. Some still survive, like phpMyAdmin. None of them were official, but with PHP as part of the name, users thought they were maintained by the PHP project.
@darkghosthunter There are some similar problems today with the “official” PHP Docker images, which neither the PHP project nor the company Docker maintain.

@ramsey I have no problem with having a library that has PHP on its name like “Async for PHP”. Just don’t blame it “PHP Async” or else.

Eventually somebody will have a big problem and sue the wrong person/company. Sometimes shit must happen to change.

@darkghosthunter Good luck suing PHP. There’s no entity to sue! 🤣
@ramsey Lol I mean, a guy having a library with a name that sounds like maintained officially when it's not.
@darkghosthunter Ah, I misunderstood. I thought you were saying someone might try to sue PHP over problems from a package that sounds like it’s official because of its name.

@ramsey Yeah, it's kind of silly. I highly doubt it's going to happen with Laravel, but at some point someone will say "This uses a trademarked name as title, and assumes is associated to the trademark owner".

That's (partially) why I used Laragear for my packages instead of using "Laravel Passkeys" or "Laravel Subscriptions".

@darkghosthunter This is a bit harder with open source projects like PHP, since there’s no one to own or enforce the trademark. However, with Laravel, that’s IP that Taylor’s company owns, and they have the right and the legal obligation to protect their mark to avoid it falling into common use and confusing consumers.
@ramsey @darkghosthunter
Wouldn't be the case of PHP Foundation to own the PHP trademark? For example, the trademark for phpMyAdmin is owned by the Software Freedom Conservancy.
@mauriciofauth @darkghosthunter As far as I know, they do not own any of the PHP project assets.
@ramsey @darkghosthunter
Interesting. That made me think... Who owns the php.net domain?

@mauriciofauth @darkghosthunter I think @derickr might be able to answer who owns the domain.

The logo is by Colin Viebrock. https://www.php.net/download-logos.php

The elePHPant design is by Vincent Pontier. https://www.php.net/elephpant.php

PHP: Download Logos

PHP is a popular general-purpose scripting language that powers everything from your blog to the most popular websites in the world.

@ramsey @mauriciofauth @darkghosthunter AFAIK it's @rasmus who owns the domain. I also think at some point there was a trademark, maybe @jimw knows that.

@derickr @ramsey @mauriciofauth @darkghosthunter @rasmus Almost positive there’s never been action around a trademark. Rasmus probably controls the domain name, maybe the folks at EasyDNS have been picking up the tab.

This is one of those questions I’d been working towards.