From: Julian F. <ju...@be...> - 2002-12-22 09:23:42
|
I'm going to take this opportunity to raise this issue because I keep wondering about it. Are we happy with the config variable names? I realized that we don't want to rename them all if we can avoid it because it makes more work for people upgrading. But maybe we should at least give it some thought. There are at least 23 new config options since our last release and we are adding them at a fast rate. We are moving towards having standard prefixes for api functions... should we try to do something similar for config options (at least for now ones)? For example, relating to the bug reminder stuff, we now have: bug_reminder_threshold store_reminders reminder_recipents_monitor_bug We have both singular and plural forms of reminder. In two cases we mention bugs, but not in the others. The order is inconsistent. Should we, for example have these names instead: bug_reminder_send_threshold bug_reminder_store (or bug_reminder_add_bugnote) bug_reminder_recipients_monitor It seems to me that something like this would make config options easier to find and easier to remember (I know I can never remember any of the names when people ask questions on IRC... I have to look them up every time). But should we group all the thresholds together or group them with what they do? Anyway, I think it would be worth discussing this. Even if we don't want to change them all now or ever, we could at least try to make all the new ones we are adding follow some pattern. Every time I create a new config option I have no idea what to call it. And I think everyone else does the same. They just make something up and commit it. Julian -- ju...@be... Beta4 Productions (http://www.beta4.com) |