Thanks again for your answers, everyone. I agree that my best bet would be to change the name. When I started this project, it was an independent study computer science project - just something I was doing for fun. I figured at the time that the name wouldn't matter too much. But then I decided to go further with it, and the trademark issue has been nagging at me ever since.

Still, I have no real attachment to the name. The only reasons I hesitate to give it up are:

• The domain name milkbone.org is pretty nice to have. None of the other names I'm considering have available domain names.
• The few people who are actively using milkbone are a bit offended at changing the name. Ultimately, though, if it comes down to their feelings about the name and possible legal action, the name will have to be dropped anyway.

So I guess the only reason I'm hanging onto this name is the domain name issue. I could tweak one of the other names I'm considering (e.g. www.mercuryim.com or www.mercuryhq.com), but ultimately I think milkbone.org is a lot easier to remember than some other name combined with an abbreviation.

I suppose my best bet would be to contact Milk-Bone and ask their opinion. If they say no, then I'll have to get mercuryhq.com or something to that effect. But if they say yes, then it's all good. I can only hope, though, that my letter doesn't simply bring the project to their attention and incite legal action. :)

Thanks again.