Suggested by rob.stryker to avoid having situations where jobs are disabled because no one is maintaining the code & we end up with something like JBIDE-20041, where last year's Freemarker is included in JBT 4.3.0.Beta1 instead of the latest stuff.

[10:36:50 AM] Rob Stryker: would it be possible to make a script that runs once a week checking for commits and firing emails indicating the jobs should be re-enabled?
[10:37:50 AM] Rob Stryker: if job is enabled, dont even bother to check/notify
[10:37:57 AM] Rob Stryker: if job is disabled, then check for new commits