Slashdot Mirror

← Back to Stories (view on slashdot.org)

Firebird Database Project Admin on Name Clash

Posted by CmdrTaco on from the stuff-to-read dept.

CapnKirk writes "Ann Harrison weighs in on the "Firebird--database or browser?" name clash. Her take on things: our users feel threatened. We're responding to their concerns. AOL lawyers said it's ok, so the Mozilla team isn't interested in negotiating, but that's ok because we've gotten a lot of publicity and name recognition. And no, we don't plan on going to court." As always, a small group of users are being real asses about the whole thing. Yay.

2 of 562 comments (clear)

  1. "Firebird" is a dumb name for a browser... by _xeno_ · · Score: 5, Interesting
    Personally, I think Mozilla should change the name - not so much because FirebirdSQL was first, but because Firebird is a dumb name for a browser :)

    In keeping with the fire and lizard themes, how about "Salamander" for the browser?

    I think we need a /. poll on this issue - let the Slashdot croud weigh in! Here's my suggestion:

    Should Mozilla change Firebird's name?

    • Yes, Firebird (the database) was first
    • Yes, Firebird's a car, not a browser
    • No, Firebird Browser and Firebird Database can coexist
    • No, FirebirdSQL should forfeight the name
    • Who cares? I don't use either!
    • Name the browser CowboyNeal and the database Hemos
    --
    You are in a maze of twisty little relative jumps, all alike.
  2. Yay? by sevensharpnine · · Score: 5, Interesting

    And what type of editorializing would we have if some no-name database project stole the name of an established browser? Just because you like the phoenix/firebird project doesn't automatically make them right.

    If they want to maintain clarity, all of the established firebird developers now have the wonderful repsonsibility of qualifying their projects as firebird-db or somesuch nonsense because the phoenix team picked a name for their software that was already taken.

    I can't understand if this naming issue is just some publicity stunt or if the moz developers are really this oblivious to the inconvenience they're causing. I would expect this sort of insane behavior from a pair of firms with an over-imaginative PR departments trying to brand themselves. But watching this shit come from open-source developers? Depressing.

    --
    "God is a comedian playing to an audience too afraid to laugh." -Voltaire