Change module name?

What about "Task Tracker"?

Though I am not a lawyer, it doesn't make sense to change the name of one module because of trademark infringement. JobTrack is a plain english word, and moreover it is not a product by itself.

Having said that, it is okay to change the name as it is not describing what it does. TicketSystem, Support, IncidentTracker, etc., can be considered, but we have to add letter "Q", "Z" at the end and see if there are any similar products around. Who knows, we may have to change again. :(

Jeremy, appreciate the balanced approach and your stand on resolving the issue.

Thanks,

One thought on "support" is that presently apropos things come up for searching for "drupal support" like the official Drupal '/support' page and commercial support providers. In other words, having a "Drupal Support Module" might be parsed wrongly by people needing help as "(drupal support) module" instead "drupal (support module)" ... which could mislead them if that makes sense.

I notice that the word "job", by the way, doesn't show up even in the module summary. "Ticket" shows up a great many times, and seems like an agnostic way to describe it (whether it's a support ticket, helpdesk ticket, or even a job-tracking ticket). If the name change is deemed unnecessary, then why bother?, but if it is, then I'd recommend "ticket-something" over "support".

I think module can be use rather than support issues also. The word of "ticket" explaining well what module is covering. So, "ticket-tracker" seems pretty good name in my opinion.

I stand with keeping the name as is, but if a change was deemed necessary, I would recommend on of the following:
1. support
2. helpdesk
3. ticket
4. helper
5. jobtracker
6. tasker
7. taskmaster

I don't care what the module is called, but that being said my concerns is about the underlying tables and associated modules. If the underlying tables change then the other modules written that depend on the "jobtrack" module name and schema will probably have to be changed also for consistency. What a pain.

My preference would be to call it what it does instead of what it is used for
That would be a name like "jobtrack" "jobtracking" or "jobtracker" instead of "support" or "helpdesk"

Just a word of advice if the name does change: Using a word found in the dictionary like "jobtracking" make it harder for trademark monkeys to start flinging poo.

Ah I see my last comment and yours came at the same time. :) The new name is fine with me. I've built a related module that is in Beta that I thought would make a nice addition to the jobtr^?^?^?^?^? support module. I'll wait until the new module is ready before I release it.

Jeremy,

I respect your decision but would just like to offer my thoughts on this very useful module.

Personally, I would have voted for Jobtracker if the pressure to change was deemed sufficient. Partially because it is using plain language as does the original name Jobtrack and because I have found it useful for both a help desk and also as a mini project tracker system. The name Jobtrack(er) is more generic and in my opinion more in keeping with the versatile use of this module.

I realize you can't please everyone but you've made one more dude out here happy to have your module available.

Thanks,

Izzy

When the issue first came up, I thought that SUPPORT would be a fair description, but I think that a trend is starting to show on the http://drupal.org/project/support page. With the generic name of SUPPORT, several issues are already there that have nothing to do with what this module is actually doing. As time goes by, I feel that a lot of people will not take the time to read the description of this module and just post general questions, which will add to the administration and support time that development work like this takes.

The growth of confusion is definitely not something we need to be aiding. I stay confused enough already.

For what its worth, I dont think that 'support' is the best option.

Just looking at the newly created module http://drupal.org/project/issues/support?text=&status=All&priorities=All... already shows that 3 out of the 4 requests are not related to the module. OK, its not enough of a sample group, but thats pretty indicative in my opinion.

Its probably going to get worse as time goes on.

We have similarly found with various projects that the percentage of original problems while not good statistical technique is a good sign of the problems to come and worth attending too.

For what its' worth, I am not a lawyer, but personally, I think the original name Jobtrack or a slight variation, Jobtracker would be best. Or possibly Tasktracker.

Again, thanks for creating this module.

Izzy