We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 34162
    • 1 Posts
    Two thoughts:

    * Names always live in a context, so don't feel like you have to bake the whole proposition into the name. I'd worry about brand personality when it comes to naming. Are we creating the right vibe? Think about some successful projects -- Firefox, (and before that -- Mozilla), lynx, apache, java, Ruby. Nothing endemic in the names. It's more about enabling the idea to spread and not getting in the way. We're looking for something to further differentiate the offering. Flickr. Technorati. Etc.

    * What's the real deadline to arrive at a name and start the brand seeding process? When will the build actually be ready? It's like we have everyone ready to make the cool t shirts and order the tradeshow giveaways. You have one chance to name it. Let the name bubble up.

    I'd back out a real date by which I needed a name, then I'd keep a running list of the most powerful. And I'd let the name standing on the top of the hill win out when I needed the name.

    Otherwise, I'm not sure why there is a rush to stop the iteration process and lobby for a particular name.
      • 28150
      • 155 Posts
      My only concern is that the assumption to run under the MODx name I feel is a mistake. MODx will always be closely identified with Etomite and I want to have something at least temporary before Dev Released 1 comes out. To me, the name, the logo, the coloring, the branding all go together.

      Like I said, I would be completely happy with a Project Name...just not anything to do with MODx. As someone else said, this is not simply an extension of an extension...this is breathing life into something that never was.
        • 25663 MODX Staff
        • 12,272 Posts
        I would definitely go for a project name, but I'm concerned that once we start down that path, we'll have to fight to change it. And in reality, we're probably under 30 days out from a very solid "real" release any way.
          Ryan Thrash, MODX Co-Founder
          Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
          • 22303 MODX Staff
          • 10,725 Posts
          My only concern is that the assumption to run under the MODx name I feel is a mistake. MODx will always be closely identified with Etomite and I want to have something at least temporary before Dev Released 1 comes out. To me, the name, the logo, the coloring, the branding all go together.

          Like I said, I would be completely happy with a Project Name...just not anything to do with MODx. As someone else said, this is not simply an extension of an extension...this is breathing life into something that never was.

          I disagree; we're already known as MODx, we are derived from Etomite, regardless of their behavior in that regard, and keeping Operation MODx as the interim project name makes perfect sense. Plus, I can't stand SiteStorm. I don't think I could work on a project called that; I'd rather have something like SiteRight, if we're going to be targeting the common man; storm just sounds too cheesy to me :-( Of course, I believe we decided to stay focused on PHP geeks until we have matured the core and could then work towards making Wizards to make everything dummy-proof.

          Besides I really do like Impress and Moxie a lot better.
            • 28150
            • 155 Posts
            I'm back to BrainStorm.

            I spent the last half an hour on CMSMatrix and I realized something, there are simply no catchy CMS names in the beginning of the alphabet.

            I think this has now reached the point of being over-analyzed. I reccomend that the decision be made privately by the two founders.

            I also disagree completely with keeping the name MODx even for the short term.
              • 34162
              • 1 Posts
              I also disagree completely with keeping the name MODx even for the short term.

              Ditto.

              Also:
              Plus, I can't stand SiteStorm. I don't think I could work on a project called that; I'd rather have something like SiteRight, if we're going to be targeting the common man; storm just sounds too cheesy to me :-(

              Please tell me that was a joke. :roll: