A few people have emailed me saying that "Traq" is too similar to "Trac" and it's easy to confuse the two.
I've been thinking of renaming Traq to something different, so the two projects wont be confused.
So far I've come up with nothing and was wondering if anyone here had any ideas.
Post your ideas and we'll take it from there.
Personally I like "Traq", it's simple yet catchy. I don't think it's too similar to "Trac". Maybe the name could be taken from one of the functions of Traq, like Bugzilla and Trac are both taken from bug-tracking. Maybe you could change tickets to issues and call Traq - Issuez
I'm not good with thinking up names, gonna shut up now
Strange, I can't edit my posts in this thread.
Maybe you could look here for some inspiration:
http://en.wikipedia.org/wiki/List_of_pro...t_software
http://en.wikipedia.org/wiki/Comparison_...ng_systems
AFAICT, Traq and Trac are used by programmers.
And programmers understand syntax errors and single alphabet differences quite well.
If the Trac community or the owners of Trac complain that it is misleading people and causing them problems, then it is a legitimate and understandable objection which would need us to change the name.
Otherwise, you should see the prevalence of this meme:
Apache Lucene ported from Java to PHP is Zend Lucene,
XSP(.Net) is the Mono version of ASP(.Net) which is Microsoft's answer to JSP from Sun,
Hibernate is ported to NHibernate,
Ant is ported to NAnt,
Junit is ported to Nunit,
MS Project is used for project management and DotProject is a PHP web app for project management,
and lots lots more.
In short, unless the Trac community really objects to "Traq" it is different and good enough.
Of course, that's my opinion.
If you have no choice but to change it, I suggest "tracphp" which is what it really is.
The other obvious options would be "phpbugtrack", "fasttrack", "squashbugs","nobugs", "bugger", "bugnuke", "bug--" and so on...
HTH
Trac should change its name, Traq is fine to me. No change needed.