Create a custom linter for //adapter code.

[ZackButcher]

We've created a framework with a lot of assumptions for adapter authors; things that are common patterns in go we don't actually want our adapter authors doing. We should look in to writing a custom linter that calls out anti-patterns in adapter code. Specifically, we should check for things like:

• Using go func() {...} rather than Env.ScheduleWork and Env.ScheduleDaemon
• Using glog rather than Env.Logger
• Use adapter.ConfigErrors for validation errors rather than errors.New or similar.

All of these patterns must also be documented in our adapter authors guide.

[douglas-reid]

Jury is still out on adapter.ConfigErrors, but in general I think this would be useful.