PHP (PSR-2, anyway) recommends using the vendor name as the root namespace for projects. At face value, this seems to mean we should use the current name of our company. But I work for an enterprise that has been involved in multiple M&As over the years; the name keeps changing, and the old name often still belongs to someone else. I suppose we could just ignore the recommendation and invent some root namespace that is unlikely to conflict with any future strategic forks in the road, but there is value to the recognition that customers have with the name. The problem is, there's also value to the old name from a marketing perspective, too.
On the legal side, sooner or later we will certainly be obligated not to use the old name. But on the technical side, changing the name introduces some risk, too.
I have to change the root namespace of some of our products, eventually. The question is, should I really keep using our (new, at the time) company name as the "vendor" namespace, or is there a better option that can survive future company name changes (ideally, one that doesn't stray too far from the intent of PSR-2)?