MozillaZine

Phoenix and Minotaur to be renamed Firebird and Thunderbird

Monday April 14th, 2003

Asa Dotzler writes: "After months of discussion and further months of legal investigation, we're finally comfortable moving forward with new names. The new name for the Phoenix browser is 'Firebird'. The documentation and product strings will be updated soon. In addition to securing Firebird, we've also got the OK from those contributing legal resources to use the name 'Thunderbird' for a mail client. Hopefully this will be the end of naming legal issues for a while."


#83 The project will continue

by netdemon <netdemonz@yahoo.com>

Tuesday April 15th, 2003 4:00 PM

You are replying to this message

And I've had my own life to deal with, also. I don't get paid for what I do on this project, and the least people can do is at least give me credit. How would you like if someone said you don't do any work on the project, that all you have done is waste peoples' time? Let's imagine that Stuart Parmenter said that about you. Would you like it? I do realize you go about bashing each other in your blogs, but then again I'm a bit more sensitive than a lot of people.

> And yes, I think you're right. The "main developers" will get tired of the crap associated with this project and move on. And you will still be around. And then what?

And the project will continue. Its a lot bigger than the few main developers. I'm sorry I can't work on it more than just 6 hours a week, but that's the reality of life. To say I do nothing is unfair, at best. This project has hit a point where it has gained a lot of support, but needs to change quite a bit. I have been pushing for this for a long time, and I'm finally glad it happened.

I also congragulate you for finally getting to the point you are capable of documenting. Perhaps with the help of your documentation, I can get to the point where I feel comfortable doing it also. Up until now, though, I've wanted to but don't know enough about the inner workings nor have the time to sit there and figure it out. The time I have spent has been fixing bugs on a broad range of the source code. Because of that, I have never gotten familiar specifically with any component to write documentation for it. I could certainly fill in a skeleton documentation, though.