[RFC] Change the name to avoid confusion with the CMS named Bolt. about blt HOT 9 CLOSED

Thanks to the BoltCMS community for raising this issue. I'd like to assure you all that the namespace collision was purely coincidental and I apologize for the ruckus that it's caused. I believe we're all working toward the same ultimate goals--to provide great open source software for the benefit of everyone. It's not in anyone's interest for there to be confusion.

In the spirit of community, Acquia has renamed our Build & Launch Tool to Acquia BLT. We hope that this will allay any concerns that our tool will be confused with the BoltCMS.

We are in the process of updating all associated code and documentation. Please bear with us as we make the transition. There's a bit of work to do!

from blt.

I am an existing Bolt user and use Google/DuckDuckGo a lot on "Bolt Symfony Twig Etc."-related words. I agree that renaming your product while it's still fresh is the way to go to avoid confusion.

from blt.

Drupal and Bolt are in the same category, however Bolt the CMS and bolt the tool to support best practices in Drupal are as different as all these other tools known as bolt:

• https://github.com/boltdb/bolt
• https://github.com/HSA-Libraries/Bolt
• https://github.com/juxt/bolt
• https://github.com/firebase/bolt
• https://github.com/liexusong/bolt

Each of the above has an entirely different purpose so surely confusion is only limited to those who can't see past the fact that the order of letters in the name is the same.

from blt.

To add a little to @damontgomery's point, naming things is hard. We actually discussed the name for a very long time (more than I care to admit), and we evaluated a large number of names. There are precious few words in the known English language that are not already used by some project or another, so we basically chose Bolt since it seemed to have the fewest conflicts with similar tools (e.g. 'project template builders'), yet still fit in with the naming conventions Acquia's been using for other similar tooling.

(And note, I'm not saying I'm opposed to a name change... just that almost any other name we can think of is also a name of another project that has some level of community uptake already. So changing the name to something else == choosing among evils.)

Just tossing ideas out there... maybe 'Acquia Bolt' officially, but the machine name/namespace could still be bolt, or maybe 'Drupal Bolt'.

from blt.

Why not rename this to lightning bolt, to align with the existing product

from blt.

This project is not a product, it is an open source tool. Bolt doesn't use Symfony, it's based on Phing alongside primarily markdown documentation.

Would an official longer name of Acquia Bolt or Lightning Bolt address the issue?

Can you clarify the negative impact that you perceive from the stated confusion? evertalbers states his personal challenges with watching keywords. If we can understand the negative impacts, we can discuss viable options to address those impacts.

The name Bolt is in no way intending to benefit from claimed confusion with Bolt CMS. Again, Bolt is not a product.

from blt.

I respectfully disagree on that. The ones we're talking about are both related to PHP CMS'es that share quite a bit of the same used technologies, so it's different than the examples you've listed.

from blt.

This issue was automatically closed due to a merged pull request. Feel free to continue commenting if you'd like.

from blt.

Thank you! I am glad this could be resolved this quickly! Much appreciated!

Best of luck With BLT! 👍

from blt.