The plugin should be able to synchronize the configuration in two directions. That means When changes are detected in the SCM, they should be applied to Hudson. In addition, there is the issue, that the config was changed in the file system, what should happen then?

config changed in SCM:

• when to detect?
• The plugin checks the scm periodically (configurable interval) or manually (button in "Manage Hudson")
• On Hudson start up
• When committing a new config
• What action when change detected (should be configurable)
• SCM always rules (update local config, trigger a reload of config). If a change requires a restart notify admin or display a message (automatically restart ??)
• local always rules -> Revert/update the scm
• notify admin or display a message in Hudson

config on disc changed:

• When to detect?
• NO periodic check required. Change would have needed to be manually loaded anyway (restart or load config).
• When reloading the config was triggered
• When Hudson starts up
• What action when change detected (should be configurable)
• SCM always rules (revert the local changes.
• local always rules (commit changes to SCM)
• newer copy rules (only one changed)
• newer copy rules (even if both changed)
• if scm & local changed - ask (email to admin or message in Hudson)
• always ask (email to admin or message in Hudson)

The nice-to-have bonus:
when both configs changed and asking whether to use local or scm config use

• local
• scm
• newest version (timestamp)
  until the changes are confirmed.
  If the local version changed and asking whether to accept the changes, use the scm config until the change is confirmed.